Locally denied and locally allowed network slice messaging and device configuration
By supporting some network slice registration in the 5G network, the problem of insufficient resource utilization during the network slice selection process within the registration area is solved, and a larger registration area and higher resource utilization efficiency are achieved.
Patent Information
- Application Number
- CN202380029434.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-26
- Filing Date
- 2023-03-27
- Publication Date
- 2024-11-08
AI Technical Summary
In 5G networks, in the process of network slicing selection in the registered area by user equipment (UE), the prior art is difficult to effectively utilize network slicing resources in multiple tracking areas, resulting in limited size of the registered area and the inability to accurately identify and utilize partial rejection. The availability of network slicing in other tracking areas.
By supporting partial network slice registration in a mobile communication network, the device can indicate unavailable network slices in the registration request and receive information that allows and denies network slices contained in the mobility management message, including the availability of each tracking area , allowing the device to request registration in other tracking areas and use denied but available network slicing.
A larger registration area support is implemented, allowing devices to use rejected but available network slices in other tracking areas, improving the efficiency of network resources and the quality of service of user equipment.
Smart Images

Figure CN118923138A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 63 / 324,070, filed on March 26, 2022, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0003] The present disclosure relates to wireless communications, and more particularly to communications devices registered to a mobile network core for network slicing. Background Art
[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may be further referred to as an eNode B (eNB), a next generation Node B (gNB), or other suitable terms. Each network communication device, such as a base station, may support wireless communications for one or more user communication devices, which may be further referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communications with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communications across various radio access technologies, including third generation (3G) radio access technologies, fourth generation (4G) radio access technologies, fifth generation (5G) radio access technologies, and other suitable radio access technologies other than 5G.
[0005] In 5G networks, network slicing allows network operators to divide communication networks into finer, smaller networks optimized for certain characteristics. The UE may be configured with network slicing related information, such as a network slice selection policy ("NSSP"), which is used to select a specific network slice. The UE may request registration with multiple network slices through the mobile network core that manages the registration area. The registration area may have multiple tracking areas, which may differ in the case where network slices are available. The mobile network core only registers the UE to network slices that are available in the entire registration area. Summary of the invention
[0006] The present disclosure relates to methods, apparatus and systems for supporting wireless communications by devices. The communication device is configured to support partial network slice registration, whereby the device is able to track and access network slices that are unavailable in all tracking areas of different tracking areas within a registration area. The core network is also configured to respond to a registration request of a device with this capability with additional information that allows the device to understand which network slices were rejected, the reason for the rejection of the network slice, and in which tracking areas within the registration area the rejected network slices are available / unavailable. By enabling / supporting partial network slice registration, the network is able to indicate to the device that (partial) rejected network slices may be available in another tracking area of the assigned registration area. This allows the device to initiate registration and use partially rejected network slices that were rejected in the first tracking area of the assigned registration area but may be available in another tracking area. Thus a larger registration area can be provided to the device.
[0007] Some implementations of the methods and apparatus described herein may also include: while the device is in the first tracking area, the device sending a registration request message to the mobile communication network. The registration request message includes: a core network capability indication that the device supports partial registration of at least one network slice that is not available in all tracking areas of the tracking areas in the registration area. The implementation also includes: receiving a mobility management message from the mobile communication network, the mobility management message including parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) a partial network slice registration, identifying at least one local network slice that is supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area. When the device is located in a tracking area that supports local network slices, configure the device to use the local network slice registered with the partial network slice.
[0008] In some implementations of the methods and apparatus described herein, the received mobility management message is one of a registration accept message or a device configuration update command. At least one local network slice is a partially allowed or partially rejected network slice. The partial network slice registration is provided within the mobility management message as one of: (i) a single parameter with at least one allowed slice; or (ii) a parameter separate from at least one allowed slice.
[0009] In some implementations of the methods and apparatus described herein, the capability indication indicates that the device supports partial rejection of network slices. The partial network slice registration includes: a partially rejected network slice that is not available in a first tracking area, and an associated list of tracking areas in which the partially rejected network slice is one of available or unavailable. Some implementations of the methods and apparatus described herein may also include: in response to one of the following items: (i) detecting that the device moves to a tracking area in which the partially rejected network slice becomes available, and (ii) an application requesting connectivity to the partially rejected network slice, sending a registration request for the partially rejected network slice to the mobile communication network.
[0010] Aspects of the present disclosure also relate to methods, apparatus, and systems for supporting wireless communications by a network device. Some implementations of the methods and apparatus described herein may also include: the network device receives a registration request message from a second device, the registration request message including: a core network capability indication that the second device supports partial registration to a network slice. In response to receipt of the core network capability indication, the network device identifies a registration area that includes more than one tracking area, and which network slices are not supported in all tracking areas in the registration area and in the more than one tracking areas. The network device sends a mobility management message to the second device, the mobility management message including: parameters for the registration area, a partial network slice registration identifying at least one local network slice that is unavailable in all tracking areas in the registration area, and an associated list of tracking areas in which the local network slice is allowed or denied.
[0011] Some implementations of the methods and apparatus described herein may also include generating a mobility management message by merging a partial network slice registration in the mobility management message, the partial network slice registration including: (i) at least one of a partially rejected network slice, and a partially allowed network slice; (ii) a rejection reason for each partially rejected network slice; and (iii) a tracking area list of one or more tracking areas, in which the identified network slices are partially rejected or partially allowed.
[0012] Some implementations of the methods and apparatus described herein may further include: identifying at least one additional tracking area that supports the requested slice, the at least one additional tracking area being located outside the registration area. The method includes: sending parameters of the at least one additional tracking area using a mobility management message to enable the second device to register to the at least one additional tracking area during a subsequent search for selecting a cell located outside the registration area and having the requested slice. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Various aspects of the present disclosure for enabling partial network slice registration by a communication device are described with reference to the following figures. The same numbering may be used throughout to reference similar features and components shown in the figures.
[0014] Figure 1 An example of a wireless communication system supporting partial registration to a network slice within a tracking area of a registration area according to aspects of the present disclosure is shown.
[0015] Figure 2 An example block diagram of a communication architecture having a network core supporting configuration of a UE for partial registration of a network slice within a registration area according to aspects of the present disclosure is shown.
[0016] Figure 3 An example communication system is illustrated in which a user equipment (UE) has a partially denied network slice that is unavailable locally in an assigned tracking area but available in other tracking areas within a registration area in accordance with aspects of the present disclosure.
[0017] Figure 4 An example communication system is depicted in which a UE has a network slice locally available in a tracking area but not available in other tracking areas within a registration area according to aspects of the present disclosure.
[0018] Figure 5 A signaling flow diagram for a registration process for Network Slice Selection Assistance Information (NSSAI) with partial rejection is depicted in accordance with aspects of the present disclosure.
[0019] Figure 6 Depicted is a signaling flow diagram for a registration process with partially accepted NSSAI in accordance with aspects of the present disclosure.
[0020] Figure 7 A block diagram example of a device including partial network slice registration capabilities according to aspects of the present disclosure is shown.
[0021] Figure 8 A block diagram example of a basic node supporting configuration of a UE for partial registration to a network slice within a resource area according to aspects of the present disclosure is shown.
[0022] Figures 9 to 10 A flowchart of a method for supporting partial network slice registration capabilities in UE and base nodes according to aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0023] Disclosed are methods, apparatus, and systems for addressing the problem of network slices being restricted or unavailable to user equipment (UE) registered within a registration area (RA) that may include those network slices.
[0024] According to the current 5G specifications, an allowed network slice (i.e., identified by an allowed NSSAI, network slice selection assistance information) is described as all S-NSSAIs (single NSSAI) of the allowed NSSAI being available in all TAs of the registration area (RA). Therefore, all adjacent tracking areas supporting the allowed NSSAI can be allocated to the same RA assigned to the UE. When the AMF creates a registration area (RA) with one or more TAs, all S-NSSAIs of the allowed NSSAI need to be available in all TAs of the RA. If the requested NSSAI contains an S-NSSAI that is only available in certain specific TAs, it will be difficult for the access and mobility management function (AMF) of the network node to create a RA of a reasonable size that takes into account the expected paging load and the load generated due to the mobility registration update (MRU) request. For example, if the UE requests an S-NSSAI that is available in the current TA but not in some other TAs, other TAs cannot be added to the RA due to current limitations. In addition, if the UE requests an S-NSSAI that is not available in the current TA, the network will reject the S-NSSAI for the RA and the UE is not allowed to request the S-NSSAI until the UE moves outside of the RA.
[0025] During the UE registration process, or in response to receiving a UE configuration update message, the 5th generation core network (e.g., 5GC, more specifically AMF) may send a registration accept message to the UE, the registration accept message having one or more of the following parameters / elements related to the network slice configuration of the UE: allowed NSSAI (i.e., a list of one or more S-NSSAIs); configured NSSAI; rejected NSSAI; or pending NSSAI. Although the rejected NSSAI indicates to the UE that one or more S-NSSAIs in the requested NSSAI are not supported, the network (e.g., AMF) provides the rejection reason to the UE and the UE is prohibited from using the rejected NSSAI. The UE does not receive information on how to initiate registration for a rejected S-NSSAI that is rejected in the first TA of the RA but may be available in another TA of the RA. With this conventional implementation, the UE receives an assignment of a large RA that restricts access to the S-NSSAI of the rejected NSSAI within the entire RA, or receives an assignment of a small RA including a single TA if the neighboring TA does not support one of the network slices of the local TA in which the UE completes registration.
[0026] Therefore, the present disclosure provides a partial network slice registration capability, by which the UE is able to request and receive additional information about the availability of network slices in surrounding tracking areas, which also allows the UE to be assigned a larger RA, which includes one or more TAs where network slices are not available, such as partially rejected network slices. The UE also understands in which TAs these rejected network slices are available, so that the UE can request to register those slices when in the associated TA, and use these network slices accordingly, that is, establish (multiple) protocol data unit (PDU) sessions. According to one aspect, while the UE is in a first tracking area, the UE sends a registration request message to a mobile communication network. The registration request message includes a core network capability indication that the device supports partial registration of at least one network slice that is not available in all tracking areas of the tracking areas in the registration area. The UE receives a mobility management message from the mobile communication network, including parameters for the following items: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) partial network slice registration, identifying at least one local network slice that is supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area. The partial network slice registration includes: (i) at least one of a partially rejected network slice, and a partially allowed network slice; (ii) a rejection reason for each partially rejected network slice; and (iii) a tracking area list of one or more tracking areas, in which the network slice identified is partially rejected or partially allowed. The UE is configured to use the local network slice registered with the partial network slice when the device is in a tracking area that supports local network slicing. The UE is also able to identify from the tracking area list when the rejected network slice is available in another TA in the assigned RA, and request registration to the partially rejected network slice.
[0027] According to an additional aspect, in response to receiving a registration request message including a core network capability indication that the UE supports partial registration to network slices, the core network (e.g., AMF and / or NSSF) identifies a registration area that includes more than one tracking area, and which network slices are not supported in all tracking areas of the more than one tracking areas in the registration area. The network sends a mobility management message to the UE, the mobility management message including parameters for the registration area, a partial network slice registration identifying at least one local network slice that is not available in all tracking areas within the registration area, and an associated list of tracking areas for which the local network slice is allowed or denied. Thus, the network enables the UE to operate within a larger RA with additional information about which TAs in the assigned RA include the partially denied network slices.
[0028] Aspects of the present disclosure relate to enabling finer-grained acceptance and rejection of network slices within tracking areas of a registration area for communication services. In response to a registration request message by a device to a mobile communication network, the mobile communication network sends a mobility management message including parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) a partial network slice registration, the partial network slice registration identifying at least one local network slice that is supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area. When the device is located in a tracking area that supports local network slices, the device is configured to use the local network slice registered with the partial network slice.
[0029] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts related to partial network slice registration for UEs within a RA.
[0030] Figure 1 An example of a wireless communication system 100 that supports network slicing within a tracking area that is partially registered to a registration area according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies above 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).
[0031] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more base stations 102 described herein may be, include, or may be referred to as a base transceiver station, an access point, a Node B, an eNode B (eNB), a next generation Node B (eNB), or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, the base station 102 and the UE 104 may wirelessly communicate via a Uu interface.
[0032] The base station 102 may provide a geographic coverage area 110, and the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, the base station 102 and the UE 104 may support wireless communications of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the base station 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 110 may be associated with different base stations 102. The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0033] One or more UEs 104 may be dispersed throughout the geographic area of the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.
[0034] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown in FIG. UE 104 may be able to communicate with various types of devices, such as base station 102, other UE 104, or network devices (e.g., core network 106, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, the UE 104 can support communications with other base stations 102 or UEs 104, which can act as relays in the wireless communication system 100.
[0035] The UE 104 may also support direct wireless communication with other UEs 104 via a communication link 112. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 112 may be referred to as a side link. For example, the UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.
[0036] The base station 102 may support communication with the core network 106, or with another base station 102, or both. For example, the base station 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, N3, or another network interface). The base stations 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).
[0037] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions to a data network 160, such as the Internet and private data networks. In some embodiments, the UE 104 communicates with a remote host 165 via a network connection to the core network 106. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for one or more UEs 104 served by one or more base stations 102 associated with the core network 106.
[0038] In one embodiment, the mobile core network 106 includes several network functions ("NFs") and multiple network slices 155. As shown, the mobile core network 106 includes at least one AMF 135, at least one session management function ("SMF") 140, at least one UPF 145, and at least one network slice selection function ("NSSF") 150. Figure 1 A specific number of NFs are depicted in FIG, but those skilled in the art will recognize that any number of NFs may be included in the mobile core network 106.
[0039] AMF 135 and SMF 140 are examples of control plane network functions of mobile core network 106. Control plane network functions provide services such as UE registration, UE connection management, UE mobility management, data session management, etc. UPF 145 provides user plane (e.g., data) services to UE 104. For example, a data connection between UE 104 and remote host 165 is managed by UPF 145.
[0040] The NSSF 150 selects the appropriate network slice 155 (and network slice instance) for a particular UE connection. The NSSF 150 can be a standalone NF or co-located with the AMF 135 or another NF (e.g., NRF or PCF). A network slice 155 is a logical network within the mobile core network 106. A network slice 155 is a partition of resources and / or services of the mobile core network 106. Different network slices 155 can be used to meet different service requirements (e.g., latency, reliability, and capacity). Examples of different types of network slices 155 include enhanced mobile broadband ("eMBB"), massive machine type communications ("mMTC"), and ultra-reliability and low-latency communications ("URLLC"). The mobile core network 106 may include multiple network slice instances of the same network slice type.
[0041] Although specific embodiments are shown and described herein, the present disclosure is not intended to be limited to implementation of any particular wireless communication system architecture or protocol.
[0042] Figure 2 An example block diagram of a communication system having a network core supporting provision of partially denied and partially allowed network slices within a registration area to a UE according to aspects of the present disclosure is shown. Specifically, Figure 2A network architecture 200 is depicted that is used to register a UE 104 and assign a RA including a TA with one or more partially denied and / or partially allowed network slices for the UE 104 according to an embodiment of the present disclosure. The network architecture 200 may be an embodiment of a wireless communication system 100. As shown, the network architecture 200 includes a UE 104, a 5G(R)AN 210, a first network slice (here, network slice instance 1 "NSI-1") 215, a second network slice (here, network slice instance 2 "NSI-2") 220, and a common control plane network function ("CCNF") set 225. The common control plane network function set 225 may include at least an AMF, an NSSF, and a UDM. Each network slice instance also has a dedicated network function. Here, the first network slice instance 215 includes a control plane 230 having a first SMF 235 ("SMF-a"), other dedicated network functions 240, and a first UPF 245 ("UPF-a"). Additionally, the second network slice instance 220 includes a control plane 230 having a second SMF 250 ("SMF-b"), other dedicated network functions 240, and a second UPF 255 ("UPF-b").
[0043] 5G(R)AN 210 may include one or more base stations 102 ( Figure 1 ). The first and second network slice instances 215, 220 may be embodiments of the network slice 155. Additionally, the first and second SMFs 235, 250, and the first and second UPFs 245, 255 may be embodiments of the SMF 140 and the UPF 145, respectively. The 5G(R)AN 210, the common control plane network function set 225, and the network slice instances 215, 220 (and their dedicated network functions) together form a mobile communication network with which the UE 104 communicates.
[0044] In the network architecture 200, the UE 104 can communicate with the 5G(R)AN 210 using the Uu interface, the 5G(R)AN 210 can communicate with the common control plane network function set 225 using the N2 interface, and communicate with the first and second UPFs 245, 255 using the N3 interface. The first SMF 235 and the first UPF 245 can communicate using the N4 interface. Similarly, the second SMF 250 and the second UPF 255 can also communicate using the N4 interface. The common control plane network function set 225 can communicate with the control plane 230 within the first and second network slice instances 215, 220 using the N11 interface. The UE 104 transmits a registration request 260 to the network slice via the RG(R)AN 210 and then to the CCNF 225. The CCNF 225 sends a partial registration message 265 to the UE 104 via the 5G(R)AN 210.
[0045] As shown, in response to the UE registration process, or in response to the UE configuration update process (described by the registration request 260), the CCNF (e.g., AMF, NSSF, UDM) of the 5GC can send a mobility management message 265 to the UE 104 in a registration accept message, or a UE configuration update command message, the mobility management message 265 including: parameters for the registration area, a partial network slice registration 270 identifying at least one local network slice that is unavailable in all tracking areas within the registration area, and an associated list 275 of tracking areas in which the local network slice is allowed or denied (or alternatively, available or unavailable). According to one embodiment, the mobility management message 265 includes one or more of the following units related to the network slice configuration of the UE: allowed network slice selection assistance information (NSSAI), configured NSSAI, rejected NSSAI, or pending NSSAI. In addition, according to one aspect, the partial network slice registration also includes: an identification of a partially rejected NSSAI, or a partially allowed NSSAI, and a list of TAs in which each of these partially allowed or partially rejected NSSAIs exists.
[0046] Figure 3 and Figure 4 A specific example of a partial network slice registration application for a UE is provided, where the mobile core network 106 ( Figure 1 ) assigns the requesting UE 104 a RA with three adjacent TAs (TA1, TA2, and TA3), 306a-306c and 406a-406c, respectively. Figure 3 and Figure 4 Continue to refer Figure 1 and Figure 2 The components in the reference Figure 3, illustrates an example communication system 300 in which a user equipment (UE) 104 is located in a first local tracking area TA2 306b. As shown, TA2 306b includes a single network slice S-NSSAI #1, which is locally available to the UE 104. TA1 and TA3 include a second network slice S-NSSAI #2, which is available within those TAs but not in TA2. According to one aspect of the present disclosure, the mobile core network 106 assigns RAs to the UE 104 with these three TAs. Figure 4 An example communication system 300 is depicted in which a UE 104 is in an assigned tracking area TA2 having two network slices locally available to the UE 104. However, one S-NSSAI #1 of the network slice is not available in the other tracking areas TA1 and TA3 within the assigned registration area.
[0047] exist Figure 3In the present invention, the communication system 300 includes a 5G communication network core (5GC) 302, which manages a registration area 304, which includes TA1 306a, TA2 306b, and TA3 306c. TA1 supports S-NSSAI#1 and S-NSSAI#2, TA2 306b supports S-NSSAI#1, and TA3 306c supports S-NSSAI#1 and S-NSSAI#2. UE 104 is located in TA2 306b and sends a requested NSSAI 310 to register with a network that can be used for network slicing. During the registration process, the 5GC (e.g., AMF and / or NSSF) creates and sends a mobility management message (or registration acceptance message) to the UE 104 to assign the RA 304 with network slice resources to the UE 104. Utilizing the new capability of partial network slice registration, the mobility management message received by UE 104 includes: (i) the registration area includes: TA1 306a, TA2 306b, and TA3 306c; (ii) the allowed NSSAI includes S-NSSAI#1; and (iii) the partially rejected NSSAI includes S-NSSAI#2, and the rejection cause value for the current RA. To simplify the presentation description, references herein to 5GC, or more specifically AMF or NSSF, and the functions provided by these components of the core network shall generally be described as "network" or, in some embodiments, as "access controller." By providing the partially rejected NSSAI, the access controller (302) provides UE 104 with location information for other network slices that are not supported within TA2 306b where UE 104 is located. This partial rejection functionality allows the UE 104 to be assigned a RA 304 with all three TAs 306a-306c, and the UE 104 is now also able to track the rejected slices and request registration to use S-NSSAI#2 in TA1 306a or TA3 306c when the UE 104 enters any of these other TAs 306a and 306c. In the case where the UE does not indicate the supported capability of partial network slice registration to the AMF, the AMF will not treat S-NSSAI#2 as a partial rejection, which means that the RA can include TA1, TA2 and TA3, and the rejected S-NSSAI#2 will be rejected for the entire RA.
[0048] In by Figure 4In the illustrated embodiment, the communication system 400 includes a 5G communication network core (5GC) 402, which manages a registration area 404, and the registration area 404 includes TA1 406a, TA2 406b, and TA3 406c. TA1 406a supports S-NSSAI#1, TA2 406b supports S-NSSAI#1 and S-NSSAI#2, and TA3 406c supports S-NSSAI#1. UE 104 is again located in TA2 406b and sends a registration request 410 for NSSAI, which includes a core network capability indication that UE 104 supports partial registration to a network slice. Based on the identification that TA2 406b (which is the local TA of UE 104) supports both S-NSSAI #1 and S-NSSAI #2, the access controller (402) creates and sends a different registration accept message to UE 104, which now includes: (i) the registration area includes: TA1, TA2, TA3; (ii) the allowed NSSAI includes S-NSSAI #1; and (iii) the partially allowed NSSAI includes S-NSSAI #2.
[0049] The access controller (302) considers that the UE 104 is currently located in TA2 406b, and that TA2 406b supports both S-NSSAI#1 and S-NSSAI#2, while the neighboring TA1 406a and TA3 406c only support S-NSSAI#1. Therefore, the AMF / NSSF may assign a RA 404 that includes all three TAs 406a-406c, but explicitly restricts the UE 104 to only access S-NSSAI#2 while in TA2 406b. Therefore, the assigned RA 404 is consistent with Figure 3 406b, but note that S-NSSAI#2 is only available within TA2 406b. If the UE has not indicated the supported capability of partial network slice registration to the AMF, the AMF will not consider S-NSSAI#2 as partially allowed, which means that the RA will include TA2, and the allowed NSSAI will include S-NSSAI#1 and S-NSSAI#2.
[0050] According to the first embodiment, when the access controller (402) rejects a network slice (identified by an S-NSSAI) that is not supported in the current / local TA from which the device sends a registration request (requested NSSAI 410), but the local TA is within a subset of TAs of the RA 404 assigned to the UE 104, the access controller (402) sends a partial network slice registration message to the UE indicating (a) that the S-NSSAI is rejected on a local or per-TA basis (i.e., partially rejected) and (b) in which TAs of the RA the rejected S-NSSAI can be supported. In an additional implementation of this embodiment, the list of TAs in which the partially rejected S-NSSAI can be supported may include other TAs adjacent to the RA.
[0051] According to the second embodiment, when the access controller (302) partially allows a network slice (S-NSSAI) that is supported in the current / local TA of the UE 104 and a subset of TAs of the RA, the access controller (402) sends a partial network slice registration message to the UE 104, indicating that the S-NSSAI of the partially allowed NSSAI is not supported in one or more TAs of the RA 404. The information includes: a list of TAs in which the partially allowed NSSAI is allowed (i.e., supported), or a list of TAs in which the partially allowed NSSAI is not allowed (i.e., not supported).
[0052] According to the first embodiment, a partially rejected S-NSSAI (single NSSAI) available in some TAs of the RA is associated with a TA in which the S-NSSAI is not available. The partially rejected NSSAI, which may also be referred to as a "locally rejected NSSAI", is sent to the UE to indicate that the S-NSSAI included in the indication is partially rejected in the RA and / or partially available in the RA. Each S-NSSAI in the partially rejected S-NSSAI is associated with a list of TAs in which the partially rejected S-NSSAI is not supported.
[0053] According to one aspect, the access controller sends a partially rejected NSSAI to the UE, and each S-NSSAI of the rejected NSSAI is associated with a rejection cause. The rejection cause indicates that the S-NSSAI is partially rejected in the RA (e.g., partially rejected for the current TA). Therefore, in response to receiving a core network capability indication for partially registering network slices from the UR, the access controller creates and sends a registration accept message to the UE, which indicates: (i) the registration area includes: TA1, TA2, and TA3; (ii) the allowed NSSAI includes S-NSSAI#1; and (iii) the rejected NSSAI includes S-NSSAI#2, whose cause value = partial rejection for the current RA, and an associated list of rejected TAs. The latter information set indicates to the UE that S-NSSAI#2 is not supported in certain TAs of the current RA, namely in TA2.
[0054] Figure 5 A signaling flow diagram 500 for a registration process by a UE with a partially rejected NSSAI is depicted. In the signal flow diagram 500, messages are sent between the UE and network components, including the radio access network (RAN) 210 and the 5GC components that support network slice allocation, namely the AMF 135 and the NSSF 150. The arrows indicate the direction of each transmission flow. The UE 104 initiates a registration process with the network by sending a NAS registration request message 510 to the network (e.g., to the AMF 135). The message is encapsulated in an access stratum signaling message to the access network (e.g., the RAN 210). The UE 104 includes a core network capability indication that the UE supports partial S-NSSAI rejection in the NAS registration request message. In one embodiment, the indication from the UE to the AMF can be sent in a 5GMM capability IE (or UE 5GMM core network capabilities). For example, the UE's 5GMM core network capabilities can be enhanced to include a new parameter called "partial network slice rejection in RA". Alternatively, in one embodiment, the indication from UE 104 to AMF 135 may be sent as a new parameter (or information element) in the Registration Request message. The new parameter may be referred to as "Partial Network Slice Rejection in RA".
[0055] According to one embodiment, the AMF stores the UE capabilities in the UE context (e.g., NAS context). According to one embodiment, the NSSF participates in the creation of RA, allowed NSSAI, and (partially) rejected NSSAI, and the AMF forwards the indication that the UE supports partial S-NSSAI rejection (i.e., the core network capability indication that the UE supports partial S-NSSAI rejection) to the NSSF. The AMF and / or NSSF shall take the indication that the UE supports partial S-NSSAI rejection when creating the RA, allowed NSSAI and / or rejected NSSAI to be assigned to the UE.
[0056] At step 2 of the signaling flow chart 500, the network performs additional steps for the registration process 515 (e.g., forming Figure 4 .Steps 2 to 19 in 2.2.2.2), except that the steps for exchange between AMF and NSSF can be enhanced as described above.
[0057] At step 3 of the signaling flow chart 500, the AMF (and / or together with the NSSF) determines the RA of the UE and the network slice configuration for the UE, which includes at least one of the allowed NSSAI and the (partially) rejected NSSAI. Figure 3 In the example of RA, the AMF determines that S-NSSAI#1 is included in the allowed NSSAIs, while S-NSSAI#2 is included in the rejected NSSAIs, because S-NSSAI#2 is not supported in the current TA2. However (optionally based on the UE capability of the partially rejected NSSAI indicated in step 1) the AMF determines to partially reject S-NSSAI#2 in the TA2 in which S-NSSAI#2 is not supported, where the partial rejection of S-NSSAI#2 is indicated by a specific rejection cause of partial / partial rejection that is valid in certain TAs (or TAIs) of the RA.
[0058] The AMF sends a NAS Registration Accept message 520 to the UE. The NAS Registration Accept message may contain a rejected NSSAI, the rejected NSSAI comprising a partially rejected S-NSSAI (e.g., S-NSSAI#2), whose rejection reason is partial rejection in the RA, and an associated list of one or more TAIs for which the partially rejected S-NSSAI (e.g., S-NSSAI#2) is supported. In an alternative embodiment, the AMF may instead include a list of one or more TAIs for which the partially rejected S-NSSAI (e.g., S-NSSAI#2) is not supported. According to an alternative embodiment, the AMF includes the partially rejected NSSAI in other NAS messages sent, for example, in the UE Configuration Update Command message part of the UE Configuration Update procedure.
[0059] In step 4 of the signaling flow chart 500, after receiving the NAS registration request message, the UE (particularly the NAS layer) stores the received network slice configuration information (e.g., containing allowed NSSAI, rejected NSSAI, and partially rejected NSSAI associated with the TAI list) in the NAS context. According to one aspect, the storage of such network slice configuration information occurs only when an update is received from the network or the UE enters a deregistered state. The UE stores an associated list of partially rejected NSSAIs and TAIs for which the S-NSSAI is supported (or not supported) for each partially rejected S-NSSAI. The UE creates information to be configured in the UE AS layer, such as idle state mobility and / or connected state mobility. The information may include a list of TAIs (e.g., TA1, TA2, TA3) corresponding to RAs in which the UE is allowed to move without triggering an MRU process.
[0060] According to one aspect, the UE NAS layer creates a "TAI of interest" list that includes the TAI from the partially rejected S-NSSAI. The UE AS layer indicates to the NAS layer: i) the TAI of the cell, and optionally ii) the cell ID. In such a configuration, the UE AS will only report the TAIs included in the "TAI of interest" list (i.e., when the UE enters the cell of the TAI). Alternatively, the UE NAS layer may request the UE AS layer to always report the TAI when the cell of the new TAI is reselected (in idle mode) or during the handover process (in connected state). In this embodiment, the AS layer reports TAI changes and / or the TAI itself.
[0061] At step 5 of the signaling flow chart 500, when the UE becomes mobile (whether in idle mode or in connected mode) and the new cell is part of a TAI of the "TAI of interest" list, the UE AS indicates to the UE NAS layer that the UE is entering a TAI included in the "TAI of interest" list and provides the TAI itself.
[0062] At block 525, the UE evaluates whether to perform an MRU in order to request registration to S-NSSAI#2. The trigger for the evaluation may be: a) due to mobility in a TAI where S-NSSAI#2 is supported, or b) due to an application requesting connectivity to a PDU session that includes S-NSSAI#2 (e.g., this may occur at any time). The UE evaluates (i) whether S-NSSAI#2 is rejected with a reject cause value of partial reject, and (ii) whether S-NSSAI#2 is supported in the TAI of the current location. Figure 3In the example of , if the UE moves to TA1 or TA3 and there is an application on the UE that wants to use S-NSSAI #2, the UE 104 can determine that S-NSSAI #2 is supported and can request registration.
[0063] Additionally, if the UE has registered to a previously partially rejected S-NSSAI, the S-NSSAI may be indicated as partially allowed, and if the UE further moves to a TAI of a RA in which the partially allowed S-NSSAI is not supported, the UE may stop using the partially allowed S-NSSAI (e.g., S-NSSAI#2). Thus, the UE may (i) trigger an MRU procedure to deregister from the partially rejected S-NSSAI or the network (e.g., AMF), (ii) trigger a UE configuration update procedure to update the allowed NSSAI and the rejected NSSAI by including the partially rejected S-NSSAI in the partially rejected NSSAI, or (iii) stop using the PDU session(s) associated with S-NSSAI#2, as described in the example of FIG. Figure 6 Additionally, the UE or the network may release the PDU session to a partially rejected S-NSSAI (e.g., S-NSSAI#2), or modify the state of the PDU session to suspended or inactive (e.g., suspending user plane transmission).
[0064] At step 6 of the signaling flow chart 500, in response to the UE determining in step 5 to request registration to S-NSSAI#2, the UE sends a registration request 530 with type "mobility registration" and may include a 5GMM core network function (e.g., partial S-NSSAI rejection) and the requested NSSAI (S-NSSAI#1, S-NSSAI#2). If S-NSSAI#2 is rejected with a cause value of partial rejection in the RA, the UE includes S-NSSAI#2. AMF 135 (and / or together with NSSF 150) determines whether to accept or reject S-NSSAI#1 or S-NSSAI#2, and the AMF / NSSF determines a new registration area for the UE. The AMF may send a registration accept message to the UE, the registration accept message including the new RA, the allowed NSSAI, the partially allowed NSSAI, the rejected NSSAI, and / or the partially rejected NSSAI.
[0065] According to one aspect, a benefit of the above solution is that the network is able to indicate to the UE that the rejected S-NSSAI may be available in another TA (e.g., TA1 or TA3) of the RA. This allows the UE to initiate a registration for a rejected S-NSSAI that was rejected in the first TA (e.g., TA2) of the RA but may be available in another TA (e.g., TA1 or TA3) of the RA, such as Figure 3as shown in the example.
[0066] In a second or alternative embodiment, a different parameter "Partially Allowed NSSAI" is sent to the UE to indicate that S-NSSAI is not supported in certain TAs of the RA. Figure 4 , the UE may request registration to S-NSSAI#1 and S-NSSAI#2 from TA2 that supports both network slices. However, the neighboring TA does not support S-NSSAI#2. According to this second embodiment, the AMF sends a parameter called partially allowed NSSAI (or locally allowed NSSAI) to the UE, which contains the associated TA (e.g., TA2) in which S-NSSAI#1 and S-NSSAI#2 are supported / allowed.
[0067] Figure 6 A signaling flow chart 600 is shown for completing a registration process with partially allowed NSSAI. Some steps of the signaling flow chart 600 are similar to Figure 5 , and for brevity, most of the details of those repeated steps are not reproduced. Figure 5 Different, in Figure 6 In step 1 of , UE 104 includes in the NAS Registration Request message an indication that the UE supports partial / local S-NSSAI Allowance (or partial / local Allowed NSSAI). Go to step 3 (similar in some aspects to Figure 5 Overlap), the AMF determines that S-NSSAI#2 is partially / locally allowed in TA2 in which S-NSSAI#2 is supported. AMF 135 sends a NAS registration accept message (i.e., a mobility management message) to the UE. The NAS registration accept message may contain any of the following items: (1) a single allowed NSSAI, including S-NSSAI#1 allowed in the entire RA and a partially / locally allowed S-NSSAI (e.g., S-NSSAI#2), with additional information that S-NSSAI#2 is locally allowed and a list of TAs in which it is supported; or (2) a parameter of allowed NSSAI, including S-NSSAI#1 allowed in the entire RA and a parameter of partially / locally allowed NSSAI. The partially / locally allowed NSSAI includes S-NSSAIs (e.g., S-NSSAI#2) allowed in certain TAs of the RA, and includes an associated list of one or more TAIs in which the partially allowed S-NSSAI (e.g., S-NSSAI#2) is supported. Alternatively, the list may provide one or more TAIs where some of the allowed S-NSSAIs (e.g., S-NSSAI #2) are not allowed.
[0068] Partially allowed S-NSSAI means that the UE is only allowed to establish and activate (or use) PDU sessions associated with partially allowed S-NSSAI in TAs where S-NSSA is allowed / supported. In TAs where S-NSSAI is not allowed / supported, the UE should not initiate PDU session establishment for partially allowed S-NSSAI. Step 4 is the same as the previous step. Figure 5 Similar to step 4 described in .
[0069] In step 5 of the signaling flow chart 600, when UE mobility (e.g., a device in idle mode) is detected and when a new cell is part of a TAI in the "TAI of interest" list, the UE AS indicates to the NAS layer that the UE is entering the TAI included in the list of "TAI of interest" and the TAI itself. The UE AS may send this indication to the UE NAS in an idle state or a connected state.
[0070] In step 6 of the signaling flow chart 600, after notifying the UE in step 5 that it enters a TA in which a partially allowed S-NSSAI is not supported, the UE may initiate a NAS procedure to update information about the 5GC in which the UE enters a TA in which a partially allowed S-NSSAI is supported or correspondingly not supported. For example, the NAS procedure may be a NAS Mobility Management (MM) procedure (e.g., sending an indication to the AMF), or a NAS Session Management (SM) procedure (e.g., sending a PDU Session Modification procedure to the SMF). The UE evaluates whether there is a PDU session established with this S-NSSAI (e.g., S-NSSAI#2). According to one embodiment, the UE may initiate a procedure to suspend a PDU session when entering a TA in which a partially allowed S-NSSAI is not supported. Alternatively, the UE may initiate a procedure to release the suspension of a PDU session when entering a TA in which a partially allowed S-NSSAI is not supported.
[0071] According to one embodiment, if a protocol data unit (PDU) session has been established in a TA in which a partially allowed S-NSSAI is supported, and the UE enters a TA in which the PDU session is not available, the UE may perform a signaling process to place the PDU session in an inactive or suspended state. In one example, the UE may send a PDU session modification request message to SMF 140, the PDU session modification request message including a new indication that the PDU session should be suspended. In another example, the UE may notify AMF 135 of information about the UE entering a TA in which a partially allowed S-NSSAI is not supported. If there are (multiple) established PDU sessions to this S-NSSAI, AMF 135 may notify one or more corresponding SMFs 140 serving (multiple) PDU sessions to suspend the PDU session. As described herein, the suspended / inactive state of a PDU session may refer to stopping or postponing data transmission on the user plane of the PDU session and / or releasing the corresponding radio bearers and N3 bearers of the PDU session. However, the PDU session context (e.g., for non-GBR QoS flows or bearers and associated traffic filters and signaling associations between UE NAS session management instances and SMFs) in the UE and SMF 235 or 250 (and, accordingly, in the anchor UPF, e.g., 245, 255) may be stored. For example, when a downlink packet arrives at the anchor UPF, the anchor UPF may buffer or discard the downlink packet, but the UPF will not send the downlink packet to the UE (and also proposes to release the N3 tunnel to the AN). Similarly, if the UE has an uplink packet to be sent, the UE will not send the uplink packet, but will indicate to the application that the connection is temporarily unavailable. Alternatively, the UE may use another PDU session associated with an allowed S-NSSAI (e.g., S-NSSAI#1). This suspended / inactive state of a PDU session is similar to the deactivated user plane resources of a PDU session.
[0072] According to another embodiment, if a PDU session has been established and therefore suspended in a TA in which partially allowed S-NSSAI is not supported, and the UE enters a TA in which S-NSSAI is supported, the UE may perform a signaling procedure to release the suspension of the PDU session. The process of releasing the suspension may be a PDU Session Modification Request message including a new indication of the PDU session suspension to be released. As another example, the process may be a NAS MM procedure that notifies the AMF of information that the UE has entered a TA in which partially allowed S-NSSAI is supported.
[0073] According to another embodiment, if the UE is in a connected state and (multiple) PDU sessions with partially allowed S-NSSAI are in use, and the UE moves to a TA in which the partially allowed S-NSSAI is not supported, the network (e.g., the source cell) will determine that the corresponding (multiple) PDU sessions are not supported in the target cell. The source cell will correspondingly notify the UE that the radio bearers associated with the (multiple) PDU sessions are not served in the target cell. The UE will take action accordingly to release or suspend the PDU session.
[0074] One of the advantages of this solution is that the UE is able to use S-NSSAI locally or partially in the RA, and there is no need to perform a registration procedure every time the UE enters or leaves a tracking area in which S-NSSAI is supported. Another advantage is that the UE can establish a PDU session to a partially allowed S-NSSAI from a TA in which S-NSSAI is supported, and when entering a TA in which S-NSSAI is not supported, the PDU session is suspended (i.e., suspended in the user plane so as not to send user data in the uplink or downlink).
[0075] It should be understood that although Figure 5 and Figure 6 The embodiments shown in are presented as separate signaling diagrams, but they can be used together in a single solution. Therefore, the UE can present the ability to indicate to the AMF that the UE supports both features, and the AMF can provide the UE with both parameters of partially rejected NSSAI and partially allowed NSSAI in the same NAS MM message (i.e., Registration Accept message or UE Configuration Update Command).
[0076] Reference again Figure 3 In the example of an embodiment using partially rejected network slicing, when the UE initiates a registration procedure from TA2, the AMF sends a partially / locally rejected S-NSSAI#2 to the UE. When the UE moves to TA1, the UE may initiate an MRU procedure to register to both S-NSSAI#1 and S-NSSAI#2. When applied to an embodiment providing partially allowed network slicing, the AMF may send a partially / locally allowed S-NSSAI#2 to the UE.
[0077] In each of the above signaling diagrams, the TAI list provided to the UE (in step 3) is described as including TAIs from the RA. However, according to an additional aspect, the access controller (e.g., AMF 135 and / or NSSF 150) may provide the UE with additional one or more TAIs outside the assigned RA. Providing this additional TAI list is beneficial for the UE when performing cell selection outside the RA, so as to select a cell from a TAI that supports the desired (or intentionally requested) (multiple) S-NSSAI. With this functionality implemented, the UE can search for several cells from different TAIs and ultimately select a cell from a TAI that supports the (multiple) S-NSSAI to be requested. As used herein, "(multiple) S-NSSAI to be requested" refers to the S-NSSAI for which a PDU session has been established in the old RA or the (multiple) S-NSSAI for which the UE wants to establish a new PDU session.
[0078] Figure 7 An example of a block diagram 700 of a device 702 supporting partial network slice registration according to aspects of the present disclosure is shown. The device 702 may be an example of a UE 104 described herein. The device 702 may support wireless communications with one or more base stations 102, UEs 104, or any combination thereof. The device 702 may include components for bidirectional communication, the components of the bidirectional communication including components for sending and receiving communications, such as a communication manager 704, a processor 706, a memory 708 storing a TA list 709, a receiver 710, a transmitter 712, and an I / O controller 714. These components may be in electronic communication or otherwise coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus). The tracking area list 709 includes at least one of the following: (i) a TA list in which partially allowed network slices exist, (ii) a TA list in which partially allowed network slices do not exist, (iii) a TA list in which partially rejected network slices exist, or (iv) a TA list in which partially rejected network slices do not exist. In one or more embodiments, the functionality of the transmitter and receiver may be collectively referred to as being provided by the transceiver 720. In one or more embodiments, the transceiver 720 communicates with a mobile communication network that manages network slices within more than one tracking area, each tracking area supporting one or more network slices.
[0079] The communication manager 704, the receiver 710, the transmitter 712, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the communication manager 704, the receiver 710, the transmitter 712, or various combinations thereof or components thereof may support methods for performing one or more functions described herein.
[0080] In some implementations, the communication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described in the present disclosure. In some implementations, the processor 706 and a memory 708 coupled to the processor 706 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 708 by the processor 706).
[0081] Additionally, or alternatively, in some implementations, the communication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be implemented in code executed by the processor 706 (e.g., as communication management software or firmware). If implemented in code executed by the processor 706, the functionality of the communication manager 704, the receiver 710, the transmitter 712, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supported for performing the functions described in the present disclosure).
[0082] In some implementations, the communication manager 704 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 710, the transmitter 712, or both. For example, the communication manager 704 may receive information from the receiver 710, send information to the transmitter 712, or be integrated with the receiver 710, the transmitter 712, or a combination of the two to receive information, send information, or perform various other operations described herein. Although the communication manager 704 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 704 may be supported or performed by the processor 706, the memory 708, or any combination thereof. For example, the memory 708 may store code that may include instructions executable by the processor 706 to cause the device 702 to perform various aspects of the present disclosure described herein, or the processor 706 and the memory 708 may be otherwise configured to perform or support such operations.
[0083] For example, the communication manager 704 may support wireless communication at a first device (e.g., device 702) according to an example as disclosed herein. The communication manager 704 may be configured to or otherwise enable or provide the following components: while the device is located in a first tracking area, send a registration request message to a mobile communication network, wherein the registration request message includes: a core network capability indication that the device supports partial registration of at least one network slice that is not available in all tracking areas of the tracking areas in the registration area; receive a mobility management message from the mobile communication network, the mobility management message including parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) partial network slice registration, identifying at least one local network slice that is supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area; and when the device is located in a tracking area that supports local network slices, configure the device to use the local network slice registered with the partial network slice.
[0084] The processor 706 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 706 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 706. The processor 706 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 708) to cause the device 702 to perform various functions of the present disclosure.
[0085] The memory 708 may include random access memory (RAM) and read-only memory (ROM). The memory 708 may store computer-readable, computer-executable code, including instructions, which, when executed by the processor 706, cause the device 702 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some implementations, the code may not be directly executable by the processor 706, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 708 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0086] I / O controller 714 can manage input and output signals for device 702. I / O controller 714 can also manage peripheral devices that are not integrated into device 702. In some implementations, I / O controller 714 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 714 can utilize a processor such as a 702. In some implementations, the I / O controller 714 may be implemented as part of a processor, such as the processor 706. In some implementations, a user may interact with the device 702 via the I / O controller 714 or via hardware components controlled by the I / O controller 714.
[0087] In some implementations, the device 702 may include a single antenna 716. However, in some other implementations, the device 702 may have more than one antenna 716, which may be able to concurrently send or receive multiple wireless transmissions. The receiver 710 and the transmitter 712 may communicate bidirectionally via one or more antennas 716, wired or wireless links as described herein. For example, the receiver 710 and the transmitter 712 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets, provide the modulated packets to one or more antennas 716 for transmission, and demodulate packets received from one or more antennas 716.
[0088] Figure 8 An example of a block diagram 800 of a device 802 supporting RA and assignment of network slices to UEs with partially allowed or partially denied network slices according to aspects of the present disclosure is shown. The device 802 may be an example of a base station 102 as described herein. The device 802 may support wireless communications with one or more base stations 102, UEs 104, or any combination thereof. The device 802 may include components for bidirectional communications, including components for sending and receiving communications, such as a communication manager 804, a processor 806, a memory 808 storing a list of network slice identifiers (NSIs) 809, a receiver 810, a transmitter 812, and an I / O controller 814. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0089] The communication manager 804, the receiver 810, the transmitter 812, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the communication manager 804, the receiver 810, the transmitter 812, or various combinations thereof or components thereof may support methods for performing one or more functions described herein.
[0090] In some implementations, the communication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described in the present disclosure. In some implementations, the processor 806 and a memory 808 coupled to the processor 806 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 808 by the processor 806).
[0091] Additionally, or alternatively, in some implementations, the communication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in code executed by the processor 806 (e.g., as communication management software or firmware). If implemented in code executed by the processor 806, the functionality of the communication manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).
[0092] In some implementations, the communication manager 804 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 810, the transmitter 812, or both. For example, the communication manager 804 may receive information from the receiver 810, send information to the transmitter 812, or be integrated with the receiver 810, the transmitter 812, or a combination of the two to receive information, send information, or perform various other operations described herein. Although the communication manager 804 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 804 may be supported or performed by the processor 806, the memory 808, or any combination thereof. For example, the memory 808 may store code that may include instructions executable by the processor 806 to cause the device 802 to perform various aspects of the present disclosure described herein, or the processor 806 and the memory 808 may be otherwise configured to perform or support such operations.
[0093] For example, the communication manager 804 may support wireless communication at a first device (e.g., device 802) according to examples disclosed herein. The communication manager 804 may be configured to or otherwise support a component for receiving a registration request message by a transceiver, the transceiver being communicatively connected to a second device, the second device registering with a network device for connectivity to a network, the registration request message including: a core network capability indication that the second device supports partial registration network slices. The communication manager 804 may be configured to or otherwise support a component for an access controller communicatively connected to the transceiver, in response to receiving the core network capability indication, configuring the network device to: identify a registration area including more than one tracking area, and in the registration area, the network slice is not supported in all tracking areas of the more than one tracking area within the registration area; and send a mobility management message to the second device, the mobility management message including: parameters for the registration area, a partial network slice registration identifying at least one local network slice that is not available in all tracking areas within the registration area, and an associated list of tracking areas in which the local network slice is one of allowed or denied.
[0094] The processor 806 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 806 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 806. The processor 806 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 808) to cause the device 802 to perform various functions of the present disclosure.
[0095] The memory 808 may include random access memory (RAM) and read-only memory (ROM). The memory 808 may store computer-readable, computer-executable code, including instructions, which, when executed by the processor 806, cause the device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 806, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 808 may include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0096] The I / O controller 814 can manage input and output signals for the device 802. The I / O controller 814 can also manage peripheral devices that are not integrated into the device 802. In some implementations, the I / O controller 814 can represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 814 can utilize a processor such as a 802. In some implementations, the I / O controller 814 may be implemented as part of a processor (e.g., the processor 806). In some implementations, a user may interact with the device 802 via the I / O controller 814 or via hardware components controlled by the I / O controller 814.
[0097] In some implementations, the device 802 may include a single antenna 816. However, in some other implementations, the device 802 may have more than one antenna 816, which may be able to concurrently send or receive multiple wireless transmissions. The receiver 810 and the transmitter 812 may communicate bidirectionally via one or more antennas 816, wired or wireless links as described herein. For example, the receiver 810 and the transmitter 812 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets, provide the modulated packets to one or more antennas 816 for transmission, and demodulate packets received from one or more antennas 816.
[0098] Fig. 9 A flowchart of a method 900 for supporting a UE requesting partial registration to a network slice according to aspects of the present disclosure is shown. The operations of method 900 may be implemented by an apparatus or component thereof as described herein. For example, the operations of method 900 may be implemented by an apparatus such as a reference Figures 1 to 6 The UE 104 or device 702 ( Figure 7 ) device to perform. In some implementations, the UE 104 can execute a set of instructions to control the functional elements of the device to perform the functions. In addition, or alternatively, the device can use dedicated hardware to perform aspects of the functions.
[0099] At 905, the method may include: while the device is located in the first tracking area, sending a registration request message to the mobile communication network, wherein the registration request message includes: a core network capability indication that the device supports partial registration of at least one network slice that is unavailable in all tracking areas of the tracking area in the registration area. The operations of 905 may be performed according to the examples described herein. In some implementations, aspects of the operations of 905 may be referred to as Figure 1 The device described performs the following.
[0100] At 910, the method may include: receiving a mobility management message from a mobile communication network, the mobility management message including parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) a partial network slice registration identifying at least one local network slice supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area. The operations of 910 may be performed according to the examples described herein. In some implementations, aspects of the operations of 910 may be performed by reference to Figure 1 The device performs.
[0101] At 915, the method may include: when the device is in a tracking area that supports local network slicing, configuring the device to use the local network slice registered with the partial network slice. The operations of 915 may be performed according to the examples described herein. In some implementations, aspects of the operations of 915 may be described with reference to Figure 1 The device performs.
[0102] In some implementations of the methods and apparatus described herein, the capability indication indicates that the device supports partially allowed network slices. The partial network slice registration includes: the partially allowed network slices available in the first tracking area, and an associated list of tracking areas in which the partially allowed network slices are allowed. Some implementations of the methods and apparatus described herein may also include: in response to determining to move to a second tracking area in which the partially allowed network slices are not available, reconfiguring the device to stop using the partially allowed network slices while in the second tracking area.
[0103] Some implementations of the methods and apparatus described herein may further include: reconfiguring a device in a second tracking area, comprising at least one of: (i) initiating a process of suspending a data session associated with the partially allowed network slice, wherein the process of suspending the data session is a PDU session modification process including an indication for session suspension; and (ii) releasing the data session associated with the partially allowed network slice.
[0104] Some implementations of the methods and apparatus described herein may also include: receiving a partial network slice registration within a mobility management message, the partial network slice registration including: (i) at least one of a partially rejected network slice, and a partially allowed network slice; (ii) a rejection reason for each partially rejected network slice; and (iii) a tracking area list of one or more tracking areas, the network slices identified in the tracking areas being partially rejected or partially allowed. The method includes: storing the received network configuration information in response to receiving an update from the network, or the device entering a re-registration state.
[0105] Some implementations of the methods and apparatus described herein may further include: in response to a partial network slice registration including a partially rejected slice, the method including: storing a tracking area list of the partially rejected slice with a rejection reason and one of the supported or unsupported tracking areas for the partially rejected slice. In response to a partial network slice registration including a partially allowed slice, the method including: storing a tracking area list of the partially allowed slice and one of the supported or unsupported tracking areas for the partially allowed slice.
[0106] Some implementations of the methods and apparatus described herein may also include: monitoring a tracking area list for entry by a device into a new tracking area represented on the tracking area list. The method includes: in response to the device entering the new tracking area, triggering reconfiguration of the device to operate within the new tracking area; and updating the tracking area list during one of a reselection or handover process.
[0107] Some implementations of the methods and apparatus described herein may further include: receiving, within a mobility management message, parameters of at least one additional tracking area outside of a registration area of a device associated with a network slice. The method includes: storing the parameters of the at least one additional tracking area. The method includes: selecting, during a subsequent cell selection outside of the registration area, the at least one additional tracking area to register the device to the associated network slice.
[0108] Fig.10 A flow chart of a method 1000 for an access controller of a support network to assign a RA with a partially denied or partially allowed network slice to a UE according to aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 1000 may be performed by a base station 102 and / or a mobile core network 106, as described in reference to Figures 1 to 6 Or network device 802. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the functions.
[0109] At 1005, the method may include: receiving a registration request message from a second device, the registration request message including: a core network capability indication that the second device supports partial registration to a network slice. The operations of 1005 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1005 may be described by reference to Figure 1 or the device described in 2.
[0110] At 1010, the method may include, in response to receiving a core network capability indication, identifying a registration area that includes more than one tracking area, and which network slices are not supported in all of the more than one tracking areas within the registration area. The operations of 1010 may be performed according to examples described herein. In some implementations, aspects of the operations of 1010 may be described with reference to Figure 1 or the device described in 2.
[0111] At 1015, the method may include sending a mobility management message to the second device, the mobility management message including parameters for the registration area, a partial network slice registration identifying at least one local network slice that is unavailable in all tracking areas within the registration area, and an associated list of tracking areas in which the local network slice is allowed or denied. The operations of 1015 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1015 may be described with reference to Figure 1 It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are also possible. In addition, aspects from two or more methods may be combined.
[0112] In one or more embodiments, method 1000 includes: receiving a core network capability indication as one of: (a) a parameter within a core network capability message, or (b) a new parameter. An access controller generates a mobility management message to include at least one allowed network slice, and includes a partial network slice registration in one of: (i) a single parameter with the at least one allowed network slice or (ii) a parameter separate from the at least one allowed network slice.
[0113] In one or more embodiments, method 1000 includes: generating a mobility management message by incorporating a partial network slice registration within the mobility management message, the partial network slice registration including: (i) at least one of a partially rejected network slice and a partially allowed network slice; (ii) a rejection reason for each partially rejected network slice; and (iii) a tracking area list of one or more tracking areas, wherein the identified network slice is partially rejected or partially allowed.
[0114] In one or more embodiments, method 1000 includes: generating a mobility management message by: (i) partially rejecting a specific network slice in a specific tracking area when the specific network slice is not supported in the specific tracking area; and (ii) merging identification details of the specific network slice and the specific tracking area within the mobility management message.
[0115] In one or more embodiments, method 1000 includes identifying at least one additional tracking area that supports the requested slice, the at least one additional tracking area being outside the registration area. Method 1000 includes sending parameters of the at least one additional tracking area using a mobility management message to enable a second device to register to the at least one additional tracking area during a subsequent search for selecting a cell having the requested slice outside the registration area.
[0116] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).
[0117] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.
[0118] Computer readable media include both non-transient computer storage media and communication media, including any medium that promotes the transfer of computer programs from one place to another. Non-transient storage media can be any available medium, which can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by general or special-purpose computers, general or special-purpose processors. Any other non-transient medium.
[0119] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are all included in the definition of computer-readable media. As used herein, disks and optical disks include CDs, laser discs, optical disks, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically copy data magnetically, while optical disks use lasers to copy data optically. The above combinations are also included within the scope of computer-readable media.
[0120] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items preceded by a phrase such as "at least one" or "one or more") represents an inclusive list, for example, a list of at least one of A, B, or C represents A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein, including in the claims, a "set" may include one or more elements.
[0121] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferably" or "better than other examples." The detailed description includes specific details for the purpose of providing an understanding of the technology. However, the technologies may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.
[0122] The description herein is provided to enable those of ordinary skill in the art to make or use the present disclosure. It will be apparent to those of ordinary skill in the art that various modifications to the present disclosure will be apparent, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A device for wireless communication, the device comprising: a transceiver, communicating with a mobile communication network, the mobile communication network managing network slices within more than one tracking area, each tracking area supporting one or more network slices; as well as a processor communicatively coupled to the transceiver, and the processor: sending a registration request message to the mobile communication network while the device is located in the first tracking area, wherein the registration request message includes: a core network capability indication that the device supports partial registration of at least one network slice that is unavailable in all tracking areas of the tracking area in the registration area; receiving a mobility management message from the mobile communication network, the mobility management message comprising parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) a partial network slice registration identifying at least one local network slice supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area; as well as When the device is located in the tracking area supporting the local network slice, Configure the device to use the local network slice registered with the partial network slice.
2. The apparatus according to claim 1, wherein: The received mobility management message is a registration acceptance message or a device configuration update command; The at least one local network slice is a partially allowed or partially denied network slice; as well as The partial network slice registration is provided within the mobility management message as one of: (i) a single parameter together with the at least one allowed slice; or (ii) a parameter separate from the at least one allowed slice.
3. The apparatus according to claim 1, wherein: The capability indication indicates that the device supports partial rejection of network slicing; The partial network slice registration includes: a partially rejected network slice that is unavailable in the first tracking area, and an associated list of tracking areas in which the partially rejected network slice is one of available or unavailable; and The processor: In response to one of the following: (i) detecting that a device moves to a tracking area in which the partially rejected network slice becomes available, and (ii) an application requesting connectivity to the partially rejected network slice, sending a registration request for the partially rejected network slice to the mobile communications network.
4. The apparatus according to claim 1, wherein: The capability indication indicates that the device supports a portion of the allowed network slices; The partial network slice registration comprises: the partially allowed network slices available in the first tracking area and an associated list of tracking areas in which the partially allowed network slices are available; as well as The processor is also responsive to determining to move to a second tracking area in which the partially allowed network slice is unavailable, to reconfigure the device to cease using the partially allowed network slice while in the second tracking area.
5. The device of claim 4, wherein to reconfigure the device in the second tracking area, the processor performs one of the following: initiating a process of suspending a data session associated with the partially allowed network slice, wherein the process of suspending the data session is a PDU session modification process including an indication for session suspension; and Release the data session associated with the partially allowed network slice.
6. The apparatus of claim 1, wherein the processor: Receiving the partial network slice registration within the mobility management message, the partial network slice registration comprising: At least one of partially denied network slices and partially allowed network slices; The rejection reason for each partially rejected network slice; as well as a tracking area list of one or more tracking areas in which the identified network slices are partially denied or partially allowed; as well as In response to receiving an update from the network, or the device entering a re-registration state, the received network configuration information is stored.
7. The apparatus of claim 6, wherein: In response to the partial network slice registration including a partially rejected slice, the processor stores the partially rejected slice with the rejection reason together with the tracking area list of one of supported or unsupported tracking areas for the partially rejected slice; as well as In response to the partial network slice registration including a partially allowed slice, the processor stores the partially allowed slice together with the tracking area list of one of the supported or unsupported tracking areas for the partially allowed slice.
8. The apparatus of claim 6, wherein the processor: monitoring the tracking area list for entry by the device into a new tracking area represented on the tracking area list; and In response to the device entering the new tracking area: triggering reconfiguration of the device to operate within the new tracking area; and During one of the reselection, or handover procedures, the tracking area list is updated.
9. The apparatus of claim 1, wherein the processor: receiving, within the mobility management message, parameters of at least one additional tracking area outside of the registration area of the device associated with a network slice; storing said parameters of said at least one additional tracking area; as well as During a subsequent cell selection outside of the registration area, the at least one additional tracking area is selected to register the device to the associated network slice.
10. A network device for wireless communication, the network device comprising: a transceiver communicatively connected to a second device, the second device registering with the network device for connectivity to a network, the transceiver receiving a registration request message from the second device, the registration request message comprising: a core network capability indication that the second device supports partial registration with a network slice; and an access controller communicatively connected to the transceiver and, in response to receipt of the core network capability indication, the access controller configures the network device to: identifying a registration area comprising more than one tracking areas, and in the registration area, network slicing is not supported in all tracking areas of the more than one tracking areas within the registration area; and A mobility management message is sent to the second device, the mobility management message including: parameters for the registration area, a partial network slice registration identifying at least one local network slice that is unavailable in all tracking areas within the registration area, and an associated list of tracking areas in which the local network slice is one of allowed or denied.
11. The network device according to claim 10, wherein: The core network capabilities indication is received as one of: (a) a parameter within a core network capabilities message, or (b) a new parameter; and The access controller generates the mobility management message to include at least one allowed network slice, and includes the partial network slice registration in one of the following items: (i) a single parameter together with the at least one allowed network slice, or (ii) a parameter separate from the at least one allowed network slice.
12. The network device according to claim 10, wherein: The capability indication comprises: a parameter indicating that the second device supports partial rejection of network slicing; and The partial network slice registration includes: a partially rejected network slice that is not available in the first tracking area but is available in the second tracking area, and an associated list of tracking areas in which the partially rejected network slice is either rejected or allowed.
13. The network device according to claim 10, wherein: The capability indication includes: parameters indicating that the device supports partially allowed network slices; and The partial network slice registration includes: a partially allowed network slice that is available in a first tracking area but not available in other tracking areas, and an associated list of tracking areas in which the partially allowed network slice is either allowed or denied.
14. The network device of claim 10, wherein to generate the mobility management message, the access controller incorporates information within the mobility management message, the information comprising: At least one of partially denied network slices and partially allowed network slices; The rejection reason for each partially rejected network slice; as well as A list of tracking areas for one or more tracking areas in which the identified network slice is partially denied or partially allowed.
15. The network device of claim 10, wherein to generate the mobility management message, the access controller: When the specific slice is not supported in a specific tracking area, partially rejecting the specific slice in the specific tracking area; and The identification details of the specific slice and the specific tracking area are merged within the mobility management message.
16. The network device according to claim 10, wherein the access controller: identifying at least one additional tracking area supporting the associated network slice, the at least one additional tracking area being located outside the registration area; and The parameters of the at least one additional tracking area are sent using the mobility management message to enable the second device to register the associated network slice within the at least one additional tracking area during subsequent cell selection outside the registration area.
17. A network device according to claim 10, wherein the access controller includes one or two of the following items: an access and mobility management function (AMF), and a network slice selection function (NSSF), wherein the AMF stores the capability in a device context and forwards the core network capability indication to the NSSF to trigger the NSSF to generate the registration area and partial network slice registration.
18. A method for wireless communication, the method comprising: sending a registration request message to a mobile communications network while the device is in the first tracking area, wherein the registration request message includes: an indication of a core network capability of the device to support partial registration of at least one network slice that is unavailable in all tracking areas of the tracking area in the registration area; receiving a mobility management message from the mobile communication network, the mobility management message comprising parameters for: (i) one or more allowed network slices supported by each tracking area of the registration area, and (ii) a partial network slice registration identifying at least one local network slice supported in at least one tracking area but not supported in all tracking areas of the tracking areas in the registration area; as well as When the device is located in the tracking area that supports the local network slice, the device is configured to use the local network slice registered with the partial network slice.
19. The method of claim 18, wherein: The capability indication indicates that the device supports partial rejection of network slicing; The partial network slice registration includes: a partially rejected network slice that is unavailable in the first tracking area, and an associated list of tracking areas in which the partially rejected network slice is one of available or unavailable; and The method comprises sending a registration request for the partially rejected network slice to the mobile communications network in response to one of: (i) detecting movement of a device to a tracking area in which the partially rejected network slice becomes available, and (ii) an application requesting connectivity to the partially rejected network slice.
20. The method of claim 18, further comprising: Receiving the partial network slice registration within the mobility management message, the partial network slice registration comprising: At least one of partially denied network slices and partially allowed network slices; The rejection reason for each partially rejected network slice; and A tracking area list of one or more tracking areas in which the identified network slices are partially denied or partially allowed; In response to receiving an update from the network, or the device entering a re-registration state, storing the received network configuration information; monitoring the tracking area list for entry by the device into a new tracking area represented on the tracking area list; and In response to the device entering the new tracking area: triggering reconfiguration of the device to operate within the new tracking area; and During one of the reselection, or handover procedures, the tracking area list is updated.
