Broadcast network slicing supported in overlapping adjacent tracking areas

Abstract

A method includes receiving, at a user equipment, network slice information from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information relates to network slices that are not supported in the one or more cells of the first tracking area but supported in the one or more cells of the second tracking area. The method comprises: when the user equipment is located in one or more cells of a first tracking area, triggering a process of accessing the network slice at the user equipment based on the network slice information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to UK patent application No. 2214078.4 filed on September 27, 2022, the entire contents of which are incorporated herein. Technical Field

[0003] The present disclosure relates to apparatus, methods and computer programs for communication systems and particularly to, but not limited to, apparatus, methods and computer programs related to network slicing. Background Art

[0004] A communication system can be considered as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network.

[0005] The communication system may be a wireless communication system. Examples of wireless communication systems include public land mobile networks (PLMNs) operating based on radio access technology standards, such as those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute), satellite communication systems, and different wireless local area networks (e.g., wireless local area networks (WLANs)). Wireless communication systems operating based on radio access technologies may generally be divided into cells, and are therefore generally referred to as cellular systems.

[0006] Communication systems and associated equipment typically operate according to one or more radio access technologies defined in a given specification of a standard (such as a standard provided by 3GPP or ETSI), which specifies what various entities associated with the communication system and communication equipment accessing or connected to the communication system are allowed to do and how it should be achieved. The communication protocols and / or parameters used by communication equipment to access or connect to the communication system are also typically defined in the standard. Examples of standards are the so-called LTE (Long Term Evolution) and 5G (Fifth Generation) standards provided by 3GPP. Summary of the invention

[0007] According to one aspect, a method is provided, the method comprising: receiving, at a user equipment, network slice information from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area; and triggering, at the user equipment, a process for accessing the network slice based on the network slice information when the user equipment is located in one or more cells of the first tracking area.

[0008] The method may include: using the network slice information to determine whether a process for accessing the network slice will be accepted, and if it will be accepted, triggering the process.

[0009] The process may include triggering cell reselection towards one of the one or more cells of the second tracking area.

[0010] The process may include: triggering a service request to activate a connection in the network slice.

[0011] The process may include: triggering a packet data unit session establishment request for a packet data unit session requesting the network slice.

[0012] The process may include: triggering a registration request to register with the network slice.

[0013] The network slice information may provide information for access to the network slice by a user device.

[0014] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0015] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0016] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0017] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0018] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0019] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0020] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0021] There may be multiple first tracking areas and / or second tracking areas.

[0022] The method may include: receiving partially allowed information for a network slice and an indication of where the network slice is supported, the partially allowed information indicating that the network slice is a partially allowed slice in a registration area of ​​a user equipment.

[0023] The method may include receiving partially allowed information in a registration accept message or a user equipment configuration update message.

[0024] The method may include: receiving information for partial rejection of a network slice and an indication of where the network slice is supported, the partial rejection information indicating that the network slice is a partially rejected slice in a registration area of ​​a user equipment.

[0025] The method may include: receiving partial rejection information in a registration acceptance message or a user equipment configuration update message.

[0026] Network slice information can be broadcast in the system information block.

[0027] The method is performed by a device. The device may be provided in a user equipment or be a user equipment.

[0028] According to another aspect, a device is provided, comprising: a component for receiving, at a user equipment, network slice information from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area; and a component for triggering, at the user equipment, a process for accessing the network slice based on the network slice information when the user equipment is located in the one or more cells of the first tracking area.

[0029] The apparatus may include: a component for determining, using the network slice information, whether a process for accessing the network slice will be accepted and triggering the process if it will be accepted.

[0030] The process may include triggering cell reselection towards one of the one or more cells of the second tracking area.

[0031] The process may include: triggering a service request to activate a connection in the network slice.

[0032] The process may include: triggering a packet data unit session establishment request for a packet data unit session requesting the network slice.

[0033] The process may include: triggering a registration request to register with the network slice.

[0034] The network slice information may provide information for access to the network slice by a user device.

[0035] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0036] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0037] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0038] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0039] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0040] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0041] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0042] There may be multiple first tracking areas and / or second tracking areas.

[0043] The receiving component can be used to receive partial allowed information for a network slice and an indication of where the network slice is supported, the partial allowed information indicating that the network slice is a partially allowed slice in a registration area of ​​a user equipment.

[0044] The receiving component may be configured to receive partially allowed information in a registration acceptance message or a user equipment configuration update message.

[0045] The receiving component can be used to receive information for partial rejection of a network slice and an indication of where the network slice is supported, the partial rejection information indicating that the network slice is a partially rejected slice in a registration area of ​​a user equipment.

[0046] The receiving component may be configured to receive partial rejection information in a registration acceptance message or a user equipment configuration update message.

[0047] Network slice information can be broadcast in the system information block.

[0048] The apparatus may be provided in or be a user equipment.

[0049] According to another aspect, a device is provided, comprising a circuit system configured to: receive, at a user equipment, network slice information from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area; and trigger a process of accessing the network slice at the user equipment based on the network slice information when the user equipment is located in one or more cells of the first tracking area.

[0050] The circuit system can be configured to use the network slice information to determine whether a process of accessing the network slice will be accepted, and if it will be accepted, trigger the process.

[0051] The process may include triggering cell reselection towards one of the one or more cells of the second tracking area.

[0052] The process may include: triggering a service request to activate a connection in the network slice.

[0053] The process may include: triggering a packet data unit session establishment request for a packet data unit session requesting the network slice.

[0054] The process may include: triggering a registration request to register with the network slice.

[0055] The network slice information may provide information for access to the network slice by a user device.

[0056] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0057] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0058] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0059] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0060] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0061] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0062] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0063] There may be multiple first tracking areas and / or second tracking areas.

[0064] The circuit system can be configured to: receive partial allowed information for a network slice and an indication of where the network slice is supported, the partial allowed information indicating that the network slice is a partially allowed slice in a registration area of ​​a user equipment.

[0065] The circuit system may be configured to receive the partially allowed information in a registration accept message or a user equipment configuration update message.

[0066] The circuit system can be configured to: receive information for partial rejection of a network slice and an indication of where the network slice is supported, the partial rejection information indicating that the network slice is a partially rejected slice in a registration area of ​​a user equipment.

[0067] The circuit system may be configured to receive the partial rejection information in a registration acceptance message or a user equipment configuration update message.

[0068] Network slice information can be broadcast in the system information block.

[0069] The apparatus may be provided in or be a user equipment.

[0070] According to another aspect, a device is provided, comprising: at least one processor and at least one memory storing instructions, which when executed by the at least one processor causes the device to at least: receive network slice information at a user equipment from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area; and trigger a process of accessing the network slice at the user equipment based on the network slice information when the user equipment is located in one or more cells of the first tracking area.

[0071] The device may be configured to: use the network slice information to determine whether a process for accessing the network slice will be accepted, and if so, trigger the process.

[0072] The process may include triggering cell reselection towards one of the one or more cells of the second tracking area.

[0073] The process may include: triggering a service request to activate a connection in the network slice.

[0074] The process may include: triggering a packet data unit session establishment request for a packet data unit session requesting the network slice.

[0075] The process may include: triggering a registration request to register with the network slice.

[0076] The network slice information may provide information for access to the network slice by a user device.

[0077] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0078] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0079] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0080] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0081] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0082] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0083] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0084] There may be multiple first tracking areas and / or second tracking areas.

[0085] The apparatus may be configured to receive partial allowed information for a network slice and an indication of where the network slice is supported, the partial allowed information indicating that the network slice is a partially allowed slice in a registration area of ​​a user equipment.

[0086] The apparatus may be configured to receive the partially allowed information in a registration accept message or a user equipment configuration update message.

[0087] The apparatus may be configured to receive information for partial rejection of a network slice and an indication of where the network slice is supported, the information for partial rejection indicating that the network slice is a partially rejected slice in a registration area of ​​a user equipment.

[0088] The apparatus may be configured to receive information of the partial rejection in a registration accept message or a user equipment configuration update message.

[0089] Network slice information can be broadcast in the system information block.

[0090] The apparatus may be provided in or be a user equipment.

[0091] According to another aspect, a method is provided, the method comprising: causing a radio access node to broadcast to a user equipment, the broadcast comprising a network slice information node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area.

[0092] The network slice information may provide information for access by a user device to the network slice.

[0093] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0094] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0095] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0096] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0097] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0098] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0099] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0100] There may be multiple first tracking areas and / or second tracking areas.

[0101] Network slice information can be broadcast in the system information block.

[0102] The method may be performed by an apparatus. The apparatus may be provided in a radio access node or be a radio access node. The radio access node may be a distributed unit of a gNB or a distributed gNB.

[0103] According to another aspect, a device is provided, comprising: a component for causing a radio access node to broadcast to a user equipment, wherein the broadcast includes a network slice information node associated with one or more cells of a first tracking area, and the network slice information is related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area.

[0104] The network slice information may provide information for access by a user device to the network slice.

[0105] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0106] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0107] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0108] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0109] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0110] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0111] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0112] There may be multiple first tracking areas and / or second tracking areas.

[0113] Network slice information can be broadcast in the system information block.

[0114] The apparatus may be provided in or be a radio access node. The radio access node may be a distributed unit of a gNB or a distributed gNB.

[0115] According to another aspect, a device is provided, which includes a circuit system configured to: cause a radio access node to broadcast to a user equipment, the broadcast including a network slice information node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area.

[0116] The network slice information may provide information for access by a user device to the network slice.

[0117] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0118] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0119] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0120] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0121] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0122] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0123] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0124] There may be multiple first tracking areas and / or second tracking areas.

[0125] Network slice information can be broadcast in the system information block.

[0126] The apparatus may be provided in or be a radio access node. The radio access node may be a distributed unit of a gNB or a distributed gNB.

[0127] According to another aspect, a device is provided, comprising: at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least: cause a radio access node to broadcast to a user equipment, the broadcast comprising a network slice information node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area.

[0128] The network slice information may provide information for access by a user device to the network slice.

[0129] The network slice information may indicate that one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

[0130] When the user equipment is located in one or more cells of the first tracking area, the network slice information may indicate indirect access to the network slice.

[0131] The indirect access may include at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

[0132] The network slice information may indicate indirect access to a network slice access group of a network slice.

[0133] One or more cells of the first tracking area and / or the second tracking area may be identified by corresponding cell identifiers.

[0134] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding tracking area identity.

[0135] One or more cells of the first tracking area and / or the second tracking area may be identified by an indication of a corresponding cell group identifier.

[0136] There may be multiple first tracking areas and / or second tracking areas.

[0137] Network slice information can be broadcast in the system information block.

[0138] The apparatus may be provided in or be a radio access node. The radio access node may be a distributed unit of a gNB or a distributed gNB.

[0139] According to a further aspect, there is provided a computer program comprising instructions which, when executed by the apparatus, cause the apparatus to perform any of the previously stated methods.

[0140] According to a further aspect, there is provided a computer program comprising instructions which, when executed, cause any of the previously stated methods to be performed.

[0141] According to one aspect, there is provided a computer program comprising computer executable code which is executed when causing any of the previously stated methods.

[0142] According to one aspect, a computer-readable medium is provided, on which program instructions are stored, the program instructions being used to execute at least one of the above methods.

[0143] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions which, when executed by the apparatus, cause the apparatus to perform any of the previously stated methods.

[0144] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions which, when executed, cause any of the previously stated methods.

[0145] According to one aspect, a non-volatile tangible storage medium is provided having stored thereon program instructions for executing at least one of the above methods.

[0146] In the above, many different aspects have been described. It should be understood that other aspects can be provided by combining any two or more of the above aspects.

[0147] Various other aspects are also described in the following detailed description and appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0148] Some example embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0149] Figure 1 A schematic diagram of a 5G system is shown;

[0150] Figure 2 A schematic diagram of the device is shown;

[0151] Figure 3 A schematic diagram of a user equipment is shown;

[0152] Figure 4 An example of a tracking area in a UE's registration area is shown:

[0153] Figure 5A first example of a signaling flow of some embodiments is shown;

[0154] Figure 6 A second example of a signaling flow of some embodiments is shown;

[0155] Figure 7 A third example of a signaling flow of some embodiments is shown;

[0156] Figure 8 A fourth example of a signaling flow of some embodiments is shown;

[0157] Fig. 9 Shows that it can be Figures 5 to 8 Examples of signalling flows used in combination with any signalling flow;

[0158] Fig.10 A first method of some embodiments is shown;

[0159] Fig.11 A second method of some embodiments is shown; and

[0160] Fig.12 A schematic diagram of a non-volatile storage medium storing instructions that, when executed by a processor, enable the processor to perform Figures 10 to 12 One or more of the steps of any method in a method. DETAILED DESCRIPTION

[0161] In the following, certain embodiments are explained with reference to a communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a communication device. Figure 1 , Figure 2 and Figure 3 Certain general principles of wireless communication systems, their access systems and communication devices are briefly explained to help understand the technology behind the described examples.

[0162] Figure 1 A schematic diagram of a communication system operating based on the fifth generation radio access technology, commonly referred to as a 5G system (5GS), is shown. The 5GS may be a (radio) access network ((R)AN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DNs). A user device may access or connect to one or more DNs via the 5GS.

[0163] The 5G(R)AN may include one or more base stations or radio access network (RAN) nodes, such as gNodeB (gNB). A base station or RAN node may include one or more distributed units connected to a central unit.

[0164] 5GC may include various network functions such as access and mobility management function (AMF), session management function (SMF), authentication server function (AUSF), user data management (UDM), user plane function (UPF), network data analysis function (NWDAF) and / or network open function (NEF). The operations performed by each of the various network functions of 5G are described in 3GPP TS23.501 and TS23.502 version 16.

[0165] Figure 2 An example of an apparatus 200 is illustrated. The apparatus 200 may be provided in a 5GS. The apparatus 200 may have at least one processor and at least one memory storing instructions for one or more network functions of a network function of the 5GS, which instructions, when executed by the at least one processor, cause one or more functions to be executed. In this example, the apparatus may include at least one random access memory (RAM) 211a, and / or at least one read-only memory (ROM) 211b, and / or at least one processor 212, 213, and / or an input / output interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be executed to perform one or more aspects of this aspect.

[0166] Figure 3 An example of a communication device 300 is shown. The communication device 300 may be any device capable of sending and receiving radio signals. Non-limiting examples of the communication device 300 include user equipment such as Figure 1 The user equipment shown is a mobile station (MS) or mobile device (such as a mobile phone or so-called "smartphone"), a computer equipped with a wireless interface card or other wireless interface facilities (such as a USB dongle), a personal data assistant (PDA) or tablet equipped with wireless communication capabilities, a machine type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination of these devices, etc. The communication device 300 can send or receive, for example, radio signals carrying communications. The communication can be one or more of voice, electronic mail (email), text message, multimedia, data, machine data, etc.

[0167] The communication device 300 may receive radio signals over the air or radio interface 307 via appropriate means for receiving, and may transmit radio signals via appropriate means for transmitting radio signals. Figure 33, the transceiver device is schematically represented by a block 306. The transceiver device 306 may be provided, for example, by components of a radio part and an associated antenna arrangement. The antenna arrangement may be arranged inside or outside the mobile device and may include a single antenna or multiple antennas. The antenna arrangement may be an antenna array including multiple antenna elements.

[0168] The communication device 300 may be equipped with at least one processor 301, and / or at least one ROM 302a, and / or at least one RAM 302b, and / or other possible components 303 for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access and communication to access systems (such as 5G RAN) and other communication devices. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute instructions of software code 308. Execution of the instructions of software code 308 may, for example, allow the communication device 300 to perform one or more operations. Software code 308 may be stored in ROM 302a. It should be understood that in other embodiments, any other suitable memory may be used alternatively or additionally to the above-mentioned ROM and / or RAM examples.

[0169] The at least one processor 301 , the at least one ROM 302a and / or the at least one RAM 302b may be provided on a suitable circuit board, in an integrated circuit and / or in a chipset. This feature is indicated by reference numeral 304 .

[0170] The communication device 300 may optionally have a user interface, such as a keyboard 305, a touch-sensitive screen or touchpad, a combination thereof, etc. Optionally, the communication device may have one or more of a display, a speaker, and a microphone.

[0171] In the following examples, the term UE or User Equipment is used. This term encompasses any of the previously discussed examples of the communication device 300 and / or any other communication device.

[0172] An example of a wireless communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). The radio access technology currently standardized by 3GPP is generally referred to as 5G or NR. Other radio access technologies standardized by 3GPP include the Long Term Evolution (LTE) or Advanced LTE Pro of the Universal Mobile Telecommunications System (UMTS). A wireless communication system typically includes an access network, such as a radio access network that operates based on a radio access technology including a base station or a radio access network node. The wireless communication system may also include other types of access networks, such as a wireless local area network (WLAN) and / or a WiMAX (Worldwide Interoperability for Microwave Access) network. It should be understood that the exemplary embodiments may also be used with standards for future radio access technologies such as 6G and beyond 6G.

[0173] A network slice is a logical entity that is divided at the resource level to provide end-to-end services. Resources can be computing resources, storage resources, bandwidth in the transport network, and radio resources. Resources can be allocated in a dedicated or shared manner. Each network slice is connected to a different network function optimization. Network slices can be set to serve different sets of use cases, or to serve the same service but for different sets of UEs. For example, 5GS may have a first network slice between a UE and a UPF that provides a first service, such as enhanced mobile broadband (eMBB), and a second network slice between a UE and a different UPF that provides a second service, such as ultra-reliable low-latency communication (URLLC).

[0174] 5GS enables user equipment to access one or more applications. When the user equipment requests a service, the network maps the service to a network slice that meets the SLA (Service Level Agreement). User services are mapped to corresponding slices, and the mapping is part of the URSP (UE Routing Policy) rules in the UE.

[0175] Network slicing allows 5GS to support different services using the same underlying network infrastructure. Network slices can differ in their service requirements or the tenants that provide these services, such as, for example, ultra-reliable low-latency communications (URLLC) and enhanced mobile broadband (eMBB).

[0176] A network slice is uniquely identified by S-NSSAI (Single Network Slice Selection Assistance Information). The 3GPP specification (e.g., 3GPP TS 23.501) allows a UE to be simultaneously connected to and served by up to eight network slices identified by S-NSSAI, and each cell of a TA can support dozens or even hundreds of network slices identified by S-NSSAI, so that, for example, a tracking area can support up to 65535 network slices. However, these numbers may vary depending on the standard, for example.

[0177] The Registration Area (RA) in 5GS is a list of Tracking Areas (TA) configured by the core network to the UE. The UE receives the RA and TA information from the gNB.

[0178] The registration area is used to maintain the allowed network slices (identified by allowed NSSAI) for the UE. The allowed network slices (S-NSSAI) or allowed NSSAI can be configured to the UE by the network. The allowed S-NSSAI may refer to the S-NSSAI included in the allowed NSSAI. The UE may request registration to the network slice identified by the S-NSSAI by sending a registration request to register with the network slice, and the network will decide whether to add the S-NSSAI to the UE's allowed S-NSSAI list or the UE's allowed NSSAI list.

[0179] 3GPP TS23.501 Release 17 for 5G requires that all network slices identified by the S-NSSAI (Single Network Slice Selection Assistance Information) contained in the allowed NSSAI be supported in all TAs (Tracking Areas) of the RA (Registration Area) of the UE.

[0180] 3GPP TS 23.501 Release 18 for 5G introduces the possibility to indicate a "partially allowed NSSAI". The partially allowed NSSAI contains an S-NSSAI that identifies network slices that are only supported in one or more TAs of the UE's RA (which therefore constitute a subset of the RA). In other words, the partially allowed NSSAI identifies network slices that are not supported by all TAs of the UE's RA. Thus, a registration area may include tracking areas that support different network slices, such that a tracking area in a UE's registration area may support other network slices than all allowed network slices for the UE.

[0181] For partially allowed NSSAI, one option is that the UE is allowed to send a mobile originated (MO) request for partially allowed network slices (including partially supported network slices) when the UE resides in a cell that supports a subset of TAs for that network slice. The UE can send an MO request without first sending a registration request to the core network of the 5GS to register with the network slice. When the UE is in a cell that does not support network slicing, the UE can also be enabled to send a request (service request) for access to the service of the network slice by enabling the network to use a handover procedure to an overlapping cell, a redirection procedure to an overlapping cell, or a dual connection with an overlapping cell.

[0182] In practice, this may increase the signaling between the UE and the core network of the 5GS. This is because, when the UE moves in the RA, the UE has no information about which cells or TAs actually overlap with the TAs supporting the partially allowed network slices. Therefore, when the UE moves between cells, the UE will send a service request to access the services of the partially allowed network slices, and if the UE is not in a cell that overlaps with the cell of the tracking area supporting the partially allowed network slices, the service request may be rejected.

[0183] Figure 4 An example of the advantages of partially allowed NSSAI is shown in Figure 4 , a RA of a UE is shown. In this example, the RA of the UE has tracking areas denoted as TA11, TA12, TA13, TA14 and TA2. TA11, TA12, TA13 and TA14 serve frequency band a. TA2 serves frequency band b. The UE is moving in the RA of the UE. S-NSSAI 1 (identifying network slice 1) is supported in all TAs of the RA of the UE (i.e., all tracking areas TA11, TA12, TA13, TA14 and TA2). S-NSSAI 2 (identifying network slice 2) is supported only in TA2.

[0184] The UE receives the following information:

[0185] Information identifying the RA's TA, information indicating any network slices supported by all TAs of the RA, and information slices supported by one or more but not all tracking areas of the RA. For any network slices supported by one or more but not all tracking areas of the RA, information about the tracking areas in which these network slices are supported is also provided.

[0186] for Figure 4 In the example shown in , the following information can be provided to the UE.

[0187] RA=TA11, TA12, TA13, TA14, TA2

[0188] Allowed NSSAI = S-NSSAI 1

[0189] Partially allowed S-NSSAI = S-NSSAI 2, supported in TA2

[0190] With partially allowed NSSAI, if the UE reselects a cell of TA2, the UE can send a service request for access to network slice 2 of band b when moving within the RA without re-registering with the 5GS core network (5GC). As mentioned earlier, TA2 is part of the RA.

[0191] In some embodiments, the UE will receive a message including information about the partially allowed NSSAI. The message may be a registration accept message or a UE configuration update message. The message includes an indication that network slice 2 is not supported in the cell of TA1 but network slice 2 is supported in the cell of TA2.

[0192] In some embodiments, the UE will also receive network slice information for network slice 2. The network slice information for network slice 2 includes overlapping information (e.g., cells of TA1 overlap with cells of TA2) or indirect access information (e.g., cells in TA1 provide indirect access to cells of TA2). Therefore, the UE can receive network slice information for network slice 2, and the UE can use the network slice information to determine whether the UE can access the network slice and / or how the UE accesses the network slice.

[0193] Information about partially allowed NSSAI and network slice information may be provided together or separately.

[0194] The network slice information can be broadcast to the UE by a base station or RAN node, or can be included in a message by a network entity of 5GS (e.g., AMF) and sent to the UE, such as a registration acceptance message or a UE configuration update message.

[0195] Some signal flows will now be described, which illustrate different examples of providing network slice information to a UE. Figure 5 , which shows a first signal flow for providing network slice information to a UE in some embodiments.

[0196] As shown in reference numeral 1, a base station or a radio access node in a first cell ( Figure 5 The first cell is associated with TA13 and network slice 1. In this example, network slice 1 is allowed in all tracking areas of the RA of the UE.

[0197] The establishment request includes information that will allow the UE to determine how a network slice associated with one or more tracking areas (except TA13 in this example) is accessed via one or more different tracking areas. The network slice is not an allowed network slice in one or more tracking areas of the RA and is referred to as network slice 2 in this example. Network slice 2 is a partially allowed network slice. In this example, network slice 2 is a disallowed network slice in TA13.

[0198] Each tracking area may be associated with one or more cells.

[0199] The establishment request may include information indicating that gNB1 supports network slice 1 in TAI13. The establishment request may include information indicating that network slice 1 is supported by S-NSSAI identifying network slice 1.

[0200] The establishment request may include information indicating that TA13 and / or one or more cells of TA13 overlap with another tracking area. The other tracking area may be identified by an identifier of the other tracking area, which is usually called a tracking area identifier (tracking area ID) (TA2 in this example).

[0201] An identifier of a cell (typically referred to as a cell ID of one or more cells of TA13 that overlaps with TA2) may be provided.

[0202] Alternatively or additionally, the cell may be identified by a cell group identifier.The cell group identifier may be a closed access group identifier.

[0203] Alternatively or additionally, the cell may be identified by a network slice group identifier. In some embodiments, the UE resides on a cell selected in association with a particular NSAG (network slice access stratum group), the UE may then attempt to use partially allowed (or partially denied) network slices from that cell, even though these slices are not supported in these cells.

[0204] Alternatively, gNB1 may provide information identifying the TA or information identifying cells within a TA that do not overlap with any other TA.

[0205] As shown in reference numeral 2, a connection is established between the UE and the gNB1. The term connection established between the UE and the gNB1 may be an RRC (Radio Resource Control) connection.

[0206] As shown in reference numeral 3, the UE sends a registration request to the AMF to register with network slice 2. The UE can use the registration procedure to register with a PLMN (Public Land Mobile Network / SPNN (Standalone Non-Public Network)) or when it needs to provide updates to its capabilities or protocol parameters, such as those negotiated during a previous registration.

[0207] As shown in reference numeral 4, the AMF provides the UE with a response to the registration request sent by the UE. When the AMF of the PLMN or SNPN determines that the registration of the UE is accepted, the response provided to the UE may be a registration acceptance message sent by the AMF.

[0208] When a UE registers with a PLMN, the UE is assigned its Registration Area (RA), which includes all Tracking Areas - in this example TA11, TA12, TA13, TA14 and TA2. When a UE is registered, the UE may be provided with the identity of the TA.

[0209] The register acceptance response may include at least some of the information received by the AMF from gNB1, as shown in figure mark 1.

[0210] The register accept response may include information related to TA13 and / or a cell ID list of TA13 that overlaps with TA2 and / or a cell list of TA2.

[0211] The register accept response may include a list of cell IDs of TA2 that overlap with the cell IDs of TA13.

[0212] The response may indicate that network slice 2 is a partially allowed slice.

[0213] The response may indicate that network slice 2 is only allowed in TA2.

[0214] Alternatively, the response may include a list of TAs or a list of cells within a TA that do not overlap with any TA.

[0215] In the right Figure 5 The network slice information may be provided to the UE in a UE Configuration Update in the modification of the signal flow. The UE Configuration Update is a message triggered by the AMF to the UE which may update the Allowed NSSAI / Partially Allowed NSSAI. It may be triggered by the AMF after the Registration phase, i.e. the AMF first replies with a Registration Accept and then the AMF sends a UE Configuration Update which updates the Allowed NSSAI / Partially Allowed NSSAI.

[0216] refer to Figure 6 , which shows another embodiment. In this embodiment, as shown in the figure 1, gNB1 provides slice 1 information and slice 2 information in the RAN configuration update message sent to AMF. The information provided can be referred to Figure 5 Part 1 of the signal flow is discussed.

[0217] Figure 6 Steps 2 to 4 will be about Figure 5 Give a description.

[0218] In the right Figure 6In the modification of the signal flow, the network slice information may be provided to the UE in a UE Configuration Update message. The UE Configuration Update message is a message triggered by the AMF to the UE which may update the allowed NSSAI / partially allowed NSSAI. It may be triggered by the AMF after the registration phase, i.e. the AMF first responds with a Registration Accept and then the AMF sends a UE Configuration Update which updates the allowed NSSAI / partially allowed NSSAI. Figure 6 In the example shown, the UE sends a registration request to the AMF to register with the second network slice. Figure 6 In the modification of the signal flow, slice 2 will be provided in the UE configuration update message.

[0219] In About Figure 5 In a modification of the discussed example, the establishment request may indicate to the AMF that TA13 is able to provide indirect access to slice 2. (This is because one or more cells of TA13 overlap with one or more cells of TA2.) Indirect access refers to redirection, handover or dual connectivity.

[0220] Alternatively or additionally, the establishment request may provide information about the TA and / or cells that can indirectly support access to network slice 2.

[0221] Alternatively or additionally, the establishment request may provide information about a NSAG (network slice access layer group) containing network slice 2. A NSAG is a group (or list) of network slices identified by an S-NSSAI. The network slice group may include one or more network slices. For example, network slice 2 may be the only network slice.

[0222] Alternatively or additionally, the establishment request may provide information about the TA and / or cells within the TA that may not even provide indirect support for the network slice 2 identified by S-NSSAI 2.

[0223] In the right Figure 6 In a modification of the signal flow, the RAN configuration update message sent by the gNB to the AMF may indicate that TA13 is capable of providing indirect access to network slice 2.

[0224] Alternatively or additionally, the RAN configuration update message may include information about TAs and / or cells that can indirectly support access to network slice 2.

[0225] Alternatively or additionally, the RAN configuration update message may include information about the NSAG (Network Slice Access Stratum Group) that includes slice 2.

[0226] The configuration update message sent by gNB1 to AMF may be a RAN configuration update message. The message may be a NGAP (Next Generation Application Protocol) RAN configuration update message.

[0227] In some embodiments, information related to the partially allowed network slice (network slice 2) may be sent to the UE via a radio broadcast. The radio broadcast may be sent by a base station or a radio access node (such as a gNB of NG-RAN).

[0228] For any cell in the tracking area that does not support partially allowed network slicing but at least partially overlaps with tracking area 2 (or a cell of tracking area 2) that supports partially allowed network slicing, such as TA13, information that the cell overlaps with tracking area 2 (or at least one cell of tracking area 2) that supports partially allowed network slicing is broadcast.

[0229] exist Figure 4 In the example, any cell supporting TA13 of the network slice identified by S-NSSAI 2 that overlaps with TA2 broadcasts information that overlaps with TA2.

[0230] The UE receiving this information and using the partially allowed NSSAI and the information indicating that TA2 supports the network slice identified by S-NSSAI 2 can determine that the process of accessing the service provided by network slice 2 will be triggered only when the UE determines that the request will succeed. The process can be that the UE reselects to cell 2 of TA2 and sends a service request in TA2 cell 2, or the process can send a service request in the current cell and be redirected to TA2 cell 2, or the process can send a PDU session establishment request in the current cell and be redirected to TA2 cell 2. In some embodiments, after this process, it may be decided by the network to additionally or alternatively trigger dual connectivity between the serving gNB and one or more cells of TA2.

[0231] In another embodiment, or any cell of a tracking area that does not support partially allowed network slicing but at least partially overlaps with a tracking area that supports partially allowed network slicing, information that provides indirect access to the NSAG of network slice 2 is broadcast. Indirect access should be understood to be via redirection or handover or dual connectivity.

[0232] exist Figure 4 In the example of , any cell of TA13 overlapping with TA2 supports the network slice identified by S-NSSAI 2, and any cell broadcasts information that it provides indirect access to the NSAG of network slice 2. This information can be provided in the SIB (System Information Block).

[0233] A UE that receives this information and uses the partially allowed NSSAI as well as this information can, for example, reselect to a cell of TA2 to send a service request for a service provided by the network slice identified by S-NSSAI 2, indicating that TA2 supports the network slice identified by S-NSSAI2.

[0234] The UE that receives this information and uses the partially allowed NSSAI and this information can send a service request (expecting network redirection or switching) for the service provided by the network slice identified by S-NSSAI 2 in the current cell of TA13, indicating that TA 2 supports the network slice identified by S-NSSAI2.

[0235] The UE receiving this information and using the partially allowed NSSAI along with this information can connect to cell 1 and cell 1 initiates DC (dual connectivity) with cell 2 to provide support for network slice 2, indicating that TA 2 supports the network slice identified by S-NSSAI 2. The UE will remain anchored at cell 1 but will be able to offload some resources to another cell of another gNB (in this example, this would be cell 2 of gNB2).

[0236] refer to Figure 7 , which shows another signal flow of some embodiments. Again, this is described in the following scenario, where gNB1 serves cell 1 of TA13, which provides supported slice 1 (supported throughout the registration area), and slice 2 is a partially allowed slice provided in TA2.

[0237] As shown in the figure 1, gNB1 for cell 1 broadcasts information related to slice 2 in cell 1. The information may be that cell 1 overlaps with TA2 and / or at least one cell of TA2. In this example, one or more TA (tracking area) IDs may be broadcast.

[0238] As shown in reference numeral 2, the UE reselects cell 2 of TA2 based on the broadcast information. The UE uses the broadcast information and the partially allowed S-NSSAI (which indicates that TA2 supports the network slice identified by S-NSSAI 2) to determine the cell to reselect to TA2.

[0239] As shown in reference numeral 3, the UE sends a mobile originated request to the gNB of cell 2 (i.e., gNB2). The cell is associated with slice 2. This is a service request for the service provided by the network slice identified by S-NSSAI 2. The message is forwarded by gNB2 to the AMF.

[0240] The UE will then be provided with the service it requested. Figure 8, which shows another signal flow of some embodiments. Again, this is described in the following scenario, where gNB1 serves cell 1 of TA13, which provides supported slice 1 (supported in the entire registration area), and network slice 2 is a partially allowed network slice provided in TA2.

[0241] As shown in the figure 1, gNB1 for cell 1 broadcasts in cell 1 that it provides access to the NSAG of network slice 2. In this embodiment, the NSAG ID is broadcast. NSAG is a network slice group (or list). The NSAG ID is an 8-bit short identifier (ID), which can be easier to broadcast than the network slice ID (S-NSSAI). Therefore, in this example, information about the NSAG containing network slice 2 is broadcast. It should be understood that slice 2 can be the only slice contained in the NSAG.

[0242] As shown in reference numeral 2, the UE sends a mobile initiated request to the AMF via the gNB of cell 1. In some embodiments, the request may be a service request or a PDU session establishment request.

[0243] As shown in the figure mark 3, gNB1 switches to cell 2 of gNB2. This cell is associated with slice 2.

[0244] In some embodiments, the UE may determine whether to trigger a network slice request process for a partially allowed slice based on broadcast information it has received related to the partially allowed slice.

[0245] If the cell overlapping with the current cell does not support the requested partially allowed slices, the UE may suppress and / or postpone the request until the cell changes, or until the broadcast information is updated, or until a timer expires.

[0246] Otherwise, partially allowed slices may be requested.

[0247] Based on the above principles, the cell reselection process can take into account partial slice information as described above even within frequency band a. For example, if a UE in a cell of TA12 can choose between these two cells, it can preferably reselect a cell of TA13 rather than a cell of TA14, with the aim of enabling possible triggering of requesting S-NSSAI 2 once it will be in a cell of TA13.

[0248] In some embodiments, the UE will therefore use information related to the second network slice to determine whether a service request for the slice will succeed, and only if the UE determines that the request for the slice will succeed will the UE make a service request for the slice in the cell. This can be used in combination with any of the examples discussed previously.

[0249] When the UE determines from the received information that the UE will be able to access the services of the second network slice, the UE may send a registration request to the AMF to register with the second network slice. This may be used in combination with any of the examples discussed previously. When the UE determines from the received information that the UE will be able to access the services of the second network slice, cell reselection to one or more cells of the second TA may be performed. Cell reselection may be provided after the UE completes cell selection (reselection) (cell selection (reselection) to cell 1 in the example) and is in idle mode. The UE will perform the registration process in the reselected cell by sending a registration request to the AMF to register with the second network slice. This may be used in combination with any of the examples discussed previously.

[0250] When the UE determines from the received information that the UE will be able to access the services of the second network slice, the UE may send a PDU (packet data unit) session establishment request requesting a PDU session for the second network slice. This may be used in conjunction with any of the examples discussed previously. When the UE determines from the received information that the UE will be able to access the services of the second network slice, the UE may send a service request to activate a connection in the network slice.

[0251] refer to Fig. 9 , which shows a signal flow where a service request to access a network slice providing service is served by an overlapping cell and requested by a UE.

[0252] UE camps on cell 1

[0253] UE and gNB perform the RRC connection procedure.

[0254] The UE sends a mobile originated service request for the requested NSSAI slice 2 in cell 1. In some embodiments, this request is only sent if the UE has been provided with information about the second slice, such as discussed in the previously described embodiments, and this information indicates that the service will be accepted. In other words, the service request is unlikely to be rejected. This will be sent to the core network via gNB1. The service request is sent to the SMF via the AMF.

[0255] The AMF sends an Initial Context Setup Request message to gNB1 with the PDU session of slice 2 that is not supported in cell 1. The AMF may include a request for handover to a suitable target cell.

[0256] gNB1 triggers handover of the UE to overlapping cell 2 of gNB2 in TA2. gNB1 responds in the Initial Context Setup Response that the handover is in progress, which makes the AMF wait before contacting the SMF.

[0257] gNB1 switches the UE to gNB2.

[0258] gNB2 sends a path switch request to AMF.

[0259] After receiving the path switch request from gNB2, AMF contacts SMF to establish a tunnel between UPF and cell 2 of gNB2. AMF sends a tunnel modification request to SMF.

[0260] SMF and UPF perform tunnel establishment for the UE with respect to cell 2 of gNB2.

[0261] SMF will notify AMF when the tunnel is delivered.

[0262] UPF will deliver the data to gNB2, and gNB2 will deliver it through its cell 2. Therefore, the service request for the second slice succeeds.

[0263] It should be understood that this is an example of a signal flow that can be triggered when the UE wants to send a service request for a slice (slice 2), where the UE has used the received information to determine that the service request is most likely to be accepted. The received information can be any of the examples discussed above. The received information indicates to the UE in which cells of the current frequency band the UE can trigger the service request without failure. That is, the service request is less likely to be rejected.

[0264] In the previously described example, partially allowed network slicing is supported. Alternatively, in other embodiments, partially denied network slicing may be supported. Figure 4 In the context of the scenario, network slice 2 is partially rejected for RA of the UE because it is not supported in TA1, i.e. it is rejected.

[0265] For example, the AMF sends: allowed NSSAI (slice 1, slice 2), partially rejected NSSAI (slice 2), and an indication (TA2) about supporting slice 2 in case of partially rejected slice concept.

[0266] In contrast, for the concept of partial permission, for example, the AMF sends allowed NSSAI (slice 1, slice 2), partially allowed NSSAI (slice 2), and an indication of support for slice 2 (TA2).

[0267] It should be understood that any of the previously described embodiments may be modified to support the partially rejected slice concept.The partially allowed slice information may be replaced with partially rejected slice information.

[0268] Utilizing the partially allowed slicing concept, the UE may be able to directly trigger a service request or a PDU session establishment request.

[0269] Utilizing the partially rejected slice concept, the UE may need to first register with slice 2 by sending a registration request including slice 2, and then may send a service request or a PDU session establishment request.

[0270] Utilizing the concept of partially rejected slices, the UE may need to reselect to the TA2 cell and send a registration request to the TA2 cell, followed by a service request.

[0271] Utilizing the partially rejected slicing concept, the UE can send a registration request in the current cell and be redirected to the TA2 cell.

[0272] The partially rejected slice information may indicate that the network slice is not supported in one or more cells of the first TA, and / or indicate that the slice is supported in one or more cells of the second TA.

[0273] refer to Fig.10 , which illustrates a first method of some embodiments.

[0274] The method may be performed by a device. The device may be in a user device or in a user device

[0275] The apparatus may comprise suitable circuitry for providing the method.

[0276] Alternatively or additionally, the apparatus may include: at least one processor and at least one memory storing instructions, which when executed by the at least one processor cause the apparatus to at least provide the following method.

[0277] Alternatively or additionally, the device may be as described with respect to Figure 3 shown.

[0278] The method may be provided by computer program code or computer executable instructions.

[0279] The method may include: as shown in the figure mark A1, receiving network slice information at a user equipment from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information being related to network slices that are not supported in one or more cells of the first tracking area but are supported in one or more cells of a second tracking area.

[0280] The method may include: as shown in figure mark A2, when the user equipment is located in one or more cells of the first tracking area, triggering a process of accessing the network slice at the user equipment based on the network slice information.

[0281] It should be understood that Fig.10 The methods outlined in may be modified to include any of the previously described features.

[0282] refer to Fig.11 , which illustrates a second method of some embodiments.

[0283] The method may be performed by an apparatus. The apparatus may be in or be a radio access node. The radio access node may be a base station, such as a gNB.

[0284] The apparatus may comprise suitable circuitry for providing the method.

[0285] Alternatively or additionally, the apparatus may include: at least one processor and at least one memory storing instructions, which when executed by the at least one processor cause the apparatus to at least provide the following method.

[0286] Alternatively or additionally, the device may be as described with respect to Figure 2 shown.

[0287] The method may be provided by computer program code or computer executable instructions.

[0288] The method may include: as shown in the figure mark B1, causing the radio access node to broadcast to one or more user equipment, the broadcast including a network slice information node associated with one or more cells of the first tracking area, and the network slice information is related to a network slice that is not supported in one or more cells of the first tracking area but supported in one or more cells of the second tracking area.

[0289] It should be understood that Fig.11 The methods outlined in may be modified to include any of the previously described features.

[0290] Fig.12 A schematic diagram of a non-volatile storage medium 900a or 900b storing instructions and / or parameters is shown, which when executed by a processor allows the processor to perform one or more of the steps of the method of any embodiment. The non-volatile storage medium can be a computer disk (CD), a digital versatile disk (DVD) schematically marked as 900a, or a universal serial bus (USB) memory stick schematically marked as 900b. Computer instructions or codes can be downloaded and stored in one or more memories. The storage medium can store instructions and / or parameters 902, which when executed by a processor allows the processor to perform one or more of the steps of the method of the embodiment.

[0291] The computer program code may be downloaded and stored in one or more memories of the device.

[0292] It should be noted that while the above describes exemplifying embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0293] It should be noted that although some embodiments have been described for 5G networks, similar principles can also be applied to the standard.

[0294] Thus, although certain embodiments are described above by way of example with reference to certain example architectures of wireless networks, technologies and standards, the embodiments may be applied to any other suitable form of communication system than shown and described herein.

[0295] It is also noted herein that while the above describes example embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0296] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions (wherein a list of two or more elements is connected by “and” or “or”) refer to at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0297] In general, various embodiments may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the disclosure is not limited thereto. Although various aspects of the disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representation, it is well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0298] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0299] (a) hardware circuit implementations only (such as implementations using only analog and / or digital circuitry) and

[0300] (b) a combination of hardware circuitry and software such as (where applicable):

[0301] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0302] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions), and

[0303] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) for operation, but in which the software may not be present when not required for operation.”

[0304] This definition of circuitry applies to all uses of the term "component" in this application, including in any claims. As another example, as used in this application, the term circuitry also includes an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0305] The embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device (such as in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets and / or macros) may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is running. One or more computer executable components may be at least one software code or a portion thereof.

[0306] Furthermore, in this regard, it should be noted that any block of the logic flow shown in the figure can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software can be stored on physical media, such as memory chips or memory blocks implemented in a processor, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and their data variants CDs. Physical media are non-transient media.

[0307] The term "non-transitory" as used herein is a restriction on the medium itself (ie, tangible, not a signal), not on the persistence of data storage (eg, RAM vs. ROM).

[0308] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0309] Embodiments of the present disclosure may be implemented in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert logic level designs into semiconductor circuit designs for etching and formation on semiconductor substrates.

[0310] The claims define the scope of protection sought by various embodiments of the present disclosure. Embodiments and features described in this specification that do not belong to the scope of the claims (if any) are to be construed as examples that help understand the various embodiments of the present disclosure.

[0311] It should be noted that different claims with different claim scopes may be pursued in related applications such as divisional applications or continuation applications.

[0312] The above description provides a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, when read in conjunction with the accompanying drawings and the appended claims, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the above description. However, all of these and similar modifications of the teachings of the present disclosure will still fall within the scope of the present invention as defined in the appended claims. In fact, there are also other embodiments that include a combination of one or more embodiments with any other embodiments previously discussed.

Claims

1. A method comprising: receiving, at a user equipment, network slice information from a broadcast from a radio access node associated with one or more cells of a first tracking area, the network slice information relating to network slices that are not supported in the one or more cells of the first tracking area but are supported in one or more cells of a second tracking area; as well as When the user equipment is located in one or more cells of the first tracking area, the process of accessing the network slice is triggered at the user equipment based on the network slice information.

2. The method according to claim 1, comprising: The network slice information is used to determine whether the process of accessing the network slice will be accepted, and if it will be accepted, the process is triggered.

3. The method according to claim 1 or 2, wherein the process comprises: Cell reselection towards one of the one or more cells of the second tracking area is triggered.

4. The method according to any one of the preceding claims, wherein the process comprises: Triggering a service request to activate a connection in the network slice.

5. The method according to any one of the preceding claims, wherein the process comprises: Triggering a packet data unit session establishment request for a packet data unit session of the network slice.

6. A method according to any one of the preceding claims, wherein the process comprises: Trigger a registration request to register with the network slice.

7. A method according to any of the preceding claims, wherein the network slice information provides information for the access of the network slice by the user equipment.

8. A method according to any of the preceding claims, wherein the network slice information indicates that the one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

9. A method according to any of the preceding claims, wherein when the user equipment is located in the one or more cells of the first tracking area, the network slice information indicates indirect access to the network slice.

10. The method of claim 9, wherein the indirect access comprises at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

11. A method according to claim 9 or 10, wherein the network slice information indicates indirect access to a network slice access group of the network slice.

12. The method according to any of the preceding claims, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by respective cell identifiers.

13. The method according to any of the preceding claims, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by an indication of the respective tracking area identity.

14. A method according to any preceding claim, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by an indication of a respective cell group identifier.

15. A method according to any preceding claim, wherein there are a plurality of first tracking areas and / or second tracking areas.

16. A method according to any one of the preceding claims, comprising: Receive partially allowed information for the network slice and an indication of where the network slice is supported, the partially allowed information indicating that the network slice is a partially allowed slice in a registration area of ​​the user equipment.

17. The method according to claim 16, comprising: The partially allowed information is received in a registration acceptance message or a user equipment configuration update message.

18. The method according to any one of claims 1 to 15, comprising: Receive information for partial rejection of the network slice and an indication of where the network slice is supported, the information for partial rejection indicating that the network slice is a partially rejected slice in a registration area of ​​the user equipment.

19. The method according to claim 18, comprising: The partial rejection information is received in a registration acceptance message or a user equipment configuration update message.

20. A method according to any of the preceding claims, wherein the network slice information is broadcast in a system information block.

21. A method according to any preceding claim, wherein the method is performed by an apparatus, the apparatus being provided in or being a user equipment.

22. An apparatus comprising: Components for performing a method according to any one of the preceding claims.

23. An apparatus comprising: at least one processor; as well as At least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to perform a method according to any one of the preceding claims.

24. A computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to any one of the preceding claims.

25. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to any preceding claim.

26. A method comprising: Causes the radio access node to broadcast to the user equipment, the broadcast including a network slice information node associated with one or more cells of a first tracking area, the network slice information being related to a network slice that is not supported in one or more cells of the first tracking area but is supported in one or more cells of a second tracking area.

27. A method according to claim 26, wherein the network slice information is capable of providing information for the access of the user equipment to the network slice.

28. The method of claim 26 or 27, wherein the network slice information indicates that the one or more cells in the first tracking area overlap with at least one of the one or more cells in the second tracking area.

29. A method according to claim 26 or 27, wherein when the user equipment is located in the one or more cells of the first tracking area, the network slice information indicates indirect access to the network slice.

30. The method of claim 29, wherein the indirect access comprises at least one of: redirection to one or more cells of the second tracking area; handover to one or more cells of the second tracking area; and / or dual connectivity with one or more cells of the second tracking area.

31. A method according to any one of claims 26 to 30, wherein the network slice information indicates indirect access to a network slice access group of the network slice.

32. The method according to any one of claims 26 to 31, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by respective cell identifiers.

33. The method according to any one of claims 26 to 31, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by an indication of the corresponding tracking area identity.

34. The method according to any one of claims 26 to 31, wherein the one or more cells of the first tracking area and / or the second tracking area are identified by an indication of a corresponding cell group identifier.

35. The method of any one of claims 26 to 34, wherein there are a plurality of first tracking areas and / or second tracking areas.

36. A method according to any one of claims 26 to 36, wherein the network slice information is broadcast in a system information block.

37. The method according to any one of claims 26 to 37, wherein the method is performed by an apparatus, and wherein the apparatus is provided in or is a radio access node.

38. The method of claim 38, wherein the radio access node comprises a gNB or a distributed unit of a distributed gNB.

39. An apparatus comprising: Means for carrying out the method according to any one of claims 26 to 39.

40. An apparatus comprising: at least one processor; as well as At least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to perform a method according to any one of claims 26 to 39.

41. A computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to claims 26 to 39.

42. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to claims 26 to 39.

Images