Network slicing method and apparatus

Abstract

The present disclosure particularly relates to a user equipment for slice management comprising at least one processor, the at least one processor being configured to: obtain a slice group mapping (SGM) configuration, the SGM configuration indicating a mapping between slice groups and tracking areas (TAs); and perform cell reselection and / or random access operations based at least in part on the obtained SGM configuration:

Description

Technical Field

[0001] Various exemplary embodiments according to the present disclosure relate to network slicing in communication networks. Specifically, various exemplary embodiments according to the present disclosure relate to slice group mapping configuration.

Background Art

[0002] Network slicing is a key 5G function for supporting various services using the same mobile network infrastructure. For example, a network slice may be interpreted as a logical network that provides specific network functions and network characteristics to meet business objectives defined by customers. To benefit from such slice-specific network services, user equipment may require information in the form of slice groups for performing slice-specific network cell selection and / or random access to a specific network cell, etc.

[0003] However, support for slice groups in a radio access network (RAN) has recently been initiated by 3GPP (registered trademark) (3rd Generation Partnership Project). Many problems and issues need to be solved to support slice groups in 5G systems.

Summary of Invention

[0004] Certain embodiments may enable determining slice group mapping (SGM) configuration and providing the SGM configuration to user equipment for performing cell reselection and / or random access operations.

[0005] According to a first exemplary aspect, a user equipment comprising at least one processor is disclosed, the at least one processor is configured to: The user device obtains the slice group mapping (SGM) setting, which indicates the mapping between slice groups and tracking areas (TA). Based at least partially on the acquired slice group mapping settings, perform cell reselection and / or random access operations. It is configured in this way.

[0006] Furthermore, according to one exemplary embodiment of the first, the system comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are used by the at least one processor to provide at least one user device. The slice group mapping (SGM) settings are retrieved, and the SGM settings indicate the mapping between slice groups and tracking areas (TA). Based at least partially on the acquired SGM settings, perform cell reselection and / or random access operations. User equipment configured to perform the following is disclosed.

[0007] According to a second exemplary embodiment, the system comprises at least one processor, the at least one processor is The first network node obtains the Slice Group Mapping (SGM) settings, which indicate the mapping between slice groups and tracking areas (TAs). Provide SGM settings to user devices. A first network node configured in this manner is disclosed.

[0008] Furthermore, according to a second exemplary embodiment, the system comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are transmitted to at least one network node by the at least one processor. The SGM settings are retrieved, and the SGM settings show the mapping between slice groups and tracking areas. Provide SGM settings to user devices. A first network node is disclosed, configured to perform the following action.

[0009] According to a first exemplary embodiment, a method is disclosed, and the method is The user device obtains the SGM settings, which indicate the mapping between slice groups and tracking areas. The user device performs cell reselection and / or random access operations based at least partially on the acquired SGM settings. This includes the following.

[0010] According to a second exemplary embodiment, a method is disclosed, which is The first network node obtains the SGM configuration, which shows the mapping between slice groups and tracking areas. The first network node provides SGM settings to the user equipment. This includes the following.

[0011] In some examples, methods and / or apparatus according to the first and / or second exemplary embodiments (e.g., user equipment and a first network node) may be interpreted as methods and apparatus for slice management. Accordingly, according to the first exemplary embodiment, user equipment for slice management (e.g., for obtaining and / or providing slice group mappings) and methods for slice management (e.g., for obtaining and / or providing slice group mappings) are disclosed, and according to the second exemplary embodiment, a first network node for slice management (e.g., for obtaining and / or providing slice group mappings) and methods for slice management (e.g., for obtaining and / or providing slice group mappings) are disclosed.

[0012] In some embodiments, the method according to the first exemplary embodiment and / or the method according to the second exemplary embodiment may be interpreted as a method for providing slice group mapping (e.g., slice group mapping information in a first registration area that can be assigned to user equipment for which SGM settings are provided by a first network node).

[0013] According to a third exemplary embodiment, a system is disclosed which comprises at least user equipment according to the first exemplary embodiment and a first network node according to the second exemplary embodiment.

[0014] The disclosed user equipment may be interpreted as user equipment (UE). User equipment may be stationary equipment or mobile equipment. User equipment may be mobile equipment such as smartphones, tablets, wearables, smartwatches, low-power devices, IoT (Internet of Things) devices, and IIoT (Industrial IoT) devices. User equipment may be capable of acquiring sensor data (e.g., from external equipment) and transmitting the received sensor data to network nodes of the communication network. In general, user equipment may be other equipment capable of communicating with the respective communication network, such as vehicles such as automobiles and trucks. User equipment or mobile station may be interpreted as any equipment used to communicate with the respective network. User equipment in the first exemplary embodiment may be capable of communicating directly or indirectly with network nodes of the communication network, as will be described in more detail below.

[0015] The first network node may be interpreted as either a network node of the Radio Access Network (RAN) or a network node of the Core Network (CN).

[0016] Each network node in a core network (also referred to as a core network node) may be interpreted as an entity or function of any generation of communication network. Generally, a core network node may be or include hardware or software components that implement a particular function. Thus, a core network node may be implemented in a single device or module, or may be interpreted as a single device or module, or may be implemented across multiple devices or modules, or may include multiple devices or modules. In particular, a core network node may be interpreted as a network function and / or network entity as defined in the 3GPP® 5G or NR (New Radio) standard (see, for example, 3GPP® TS 23.501 version 16.10.0, sections 3 and 4). Thus, a 5G system architecture may include access and mobility management functions (AMF), session management functions (SMF), and further functions or entities. In particular, core network nodes may be implemented in the AMF, for example, to handle control signaling between the core network and user devices, security of user data, idle mobility, and authentication. The functions operating between the core network, more specifically between the AMF and user devices, are sometimes called the non-access layer (NAS) to separate them from the access layer (AS), which handles functions operating between user devices and the wireless access network.

[0017] Each network node in a RAN (also referred to as a radio access network node) is interpreted as a radio communication station installed in a fixed or mobile location, and can be, for example, any generation of a 3GPP® standard communication network (e.g., gNB, eNodeB, NodeB, BTS, etc.). Generally, a radio access network node is or may include hardware or software components that implement a specific function. In one example, a radio access network node may be a base station (also referred to as a gNB) as defined in a 3GPP® 5G or NR standard. Therefore, a radio access network node may be implemented in a single device or module, or be interpreted as a single device or module, or may be implemented across multiple devices or modules, or may include multiple devices or modules. Thus, a radio access network node may be implemented in or be a stationary device, in particular. Multiple radio access network nodes can establish a communication system or radio access network that is, in particular, a new radio (NR) or 5G system (5GS), or other mobile communication systems defined by past or future standards, in particular successor standards to current 3GPP® standards. A radio access network node may communicate directly and / or indirectly with one or more user devices, or with one or more further radio access network nodes, for example, as disclosed according to the first exemplary embodiment, as will be described in more detail below.

[0018] Referring to one or more radio access network nodes and one or more core network nodes, these nodes can communicate with each other directly and / or indirectly. According to the 5G architecture, gNBs are connected to the 5G core network by NG interfaces, and Xn interfaces can connect several gNBs to each other.

[0019] In general, any means of the apparatus disclosed in the first and / or second exemplary embodiments (i.e., user equipment and a first network node) can be implemented in hardware and / or software. They may include one or more modules or units that provide their respective functions. They may include, for example, at least one processor (e.g., for executing computer program code to perform the required functions), at least one memory for storing the program code, or both. There, it is considered disclosed that each apparatus (i.e., user equipment and / or a first network node) may include only at least one processor (e.g., without further memory or program code stored therein) configured to perform method steps as disclosed according to various embodiments. Alternatively, they may include circuitry designed to implement the required functions, implemented on a chipset or chip, such as an integrated circuit. In general, the means may include, for example, one or more processing means or processors.

[0020] Accordingly, according to the first and / or second exemplary embodiments of the present disclosure, each device (i.e., user equipment and network node) is disclosed, comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code are configured by at least one processor to cause at least the device to perform the method according to each embodiment of the present disclosure. Similarly, according to each exemplary embodiment of the present disclosure, each device (i.e., user equipment and network node) is disclosed, in each case, comprising means for performing the method according to the first and / or second exemplary embodiment.

[0021] However, the exemplary aspect disclosed above may generally be executed by an apparatus, which may for example be a module or a component for an apparatus such as a chip. The disclosed apparatus may comprise the disclosed components, e.g., means, processors, memories, or may further comprise one or more additional components.

[0022] According to the first and / or second exemplary aspects, a computer program is also disclosed, which, when executed by a processor of an apparatus (e.g., user equipment and a network node), causes the apparatus to perform the method according to the first and / or second exemplary aspects.

[0023] In each case, the computer program may be stored in a computer-readable storage medium, in particular a tangible medium and / or a non-transitory medium. The computer-readable storage medium may for example be a disk, a memory, or the like. The computer program may be stored in the computer-readable storage medium in the form of instructions encoding the computer program on the computer-readable storage medium. The computer-readable storage medium may be intended to be involved in the operation of the apparatus, such as an internal or external memory like a computer read-only memory (ROM) or a hard disk, or may be intended for distribution of the program, such as an optical disk.

[0024] Acquisition of an SGM configuration by user equipment may be interpreted to mean, for example, that the SGM configuration may be received by the user equipment from a network (e.g., a radio access network or a core network in the second exemplary embodiment), and more specifically, may be received by the user equipment from another entity such as a network node, which may for example be the network node of the aforementioned radio access network (i.e., a radio access network node) or the network node of the aforementioned core network (i.e., a core network node). For example, the SGM configuration may be received by the user equipment via a broadcast signal, or may be received via a dedicated signal as described below.

[0025] An SGM configuration (e.g., configured by a network) indicates at least one mapping between a slice group and a tracking area, which may be interpreted to mean, for example, that the SGM configuration includes information related to at least one mapping between a slice group and a tracking area (e.g., by referencing at least one mapping, or by indicating at least one mapping). The SGM configuration does not need to explicitly include at least one mapping. In other examples, indicating at least a mapping between a slice group and a tracking area may be interpreted to mean that the SGM configuration includes at least one mapping. For example, an SGM configuration that indicates or includes at least one mapping between each slice group and a tracking area means that the SGM configuration indicates or includes information related to at least one slice group, further information related to a corresponding tracking area, and / or further indication or information related to, for example, that the slice group and the tracking area are mapped to each other.

[0026] For example, an SGM setting that indicates (or, for example, includes) at least one mapping between a slice group and a tracking area may be interpreted as an SGM setting that indicates (or, for example, includes) one or more mappings between each slice group and each tracking area. In other words, referring to, for example, each slice group and the tracking area to which that slice group is mapped, an SGM setting can indicate (or, for example, include) at least one such pair of slice groups and tracking areas, or one or more such pairs. A slice group may be interpreted as information necessary for a user device to perform slice-specific cell reselection and / or slice-specific random access operations with respect to, or to, a network cell to which the user device intends to connect. In other words, slice-specific cell reselection or slice-specific random access channel information may be provided to the user device in the form of a slice group. According to some examples, each slice group may include at least one slice-to-slice group mapping, as further described below.

[0027] For example, in order for a user device to use slice-specific cell reselection for each network cell (and / or slice-specific random access channel operation for the radio access network node providing each network cell), each slice group must be specific to its respective network cell (which may be provided by its respective radio access network node). This means that each slice group is valid for a particular network cell.

[0028] Additionally or alternatively, each slice group must be specific to the tracking area containing the respective network cell. Therefore, slice groups are specific to each network cell and may, additionally or alternatively, be specific to the tracking area containing the respective network cell.

[0029] It should be understood that a tracking area refers to a group of network cells provided, for example, by a specific radio access network node. In other cases, a group of network cells may be grouped into a specific radio access network area identified by a radio access network area identifier (RAI), and multiple radio access network areas may be grouped into a tracking area. Such a tracking area, containing multiple network cells (e.g., each grouped into a radio access network area), may typically be identified by a tracking area identifier (TAI). A tracking area may be interpreted as a basis for tracking user equipment. To this end, user equipment may consist of a list of tracking area identifiers, or be assigned (e.g., by the core network) to each registration area containing them. For example, if user equipment enters a network cell belonging to a tracking area that is not included in the registration area to which the user equipment is assigned, the user equipment can access the core network and perform an update to its Non-Access Layer (NAS) registration. Thus, the core network can register the location of the user equipment and update the equipment registration area by, for example, providing the user equipment with a new list of tracking area identifiers containing the new tracking identifier.

[0030] For example, in this embodiment, a network slice may be interpreted as a logical network that provides specific network functions and characteristics to address customer-defined business objectives. For instance, a network slice allows for the creation of multiple virtual networks on a common shared physical infrastructure. A network slice may consist of, or include, various subnets, such as a wireless access network subnet, a core network subnet, and / or a transport network subnet. Typically, a telecommunications service provider can be the owner or tenant of the network infrastructure on which the network slice is created.

[0031] For example, as further described in the 3GPP® technical specifications, network slices are uniquely identified via S-NSSAI (Single Network Slice Selection Support Information). User equipment can connect to and receive services from up to eight network slices simultaneously, associated with eight S-NSSAIs. On the other hand, each network cell may support tens or hundreds of S-NSSAIs. For example, when user equipment registers with the network, it may indicate one or more slices that it may need access to (e.g., via the requested S-NSSAI). Furthermore, in this embodiment, the core network can analyze the user equipment's profile and subscription data to verify a list of slices that the user equipment may be allowed to access. As a result, the core network can send the user equipment a list of allowed slices (e.g., allowed NSSAIs). The list of allowed slices may differ from, or be only a subset of, the slices requested by the user equipment during the registration process. This is because the user equipment may not have access to a particular slice, or that slice is not supported at the current location where the registration request was initiated.

[0032] For a given tracking area, one or more identical network slices may be supported within that tracking area, which may be referred to as homogeneous or uniform slice support. For example, whenever user equipment moves and is to perform a slice-specific cell reselection or slice-specific random access channel (e.g., to a new network cell or a new radio access network node providing the new network cell), the user equipment may need corresponding information about such slice groups specific to the new network cell. For example, assuming the new network cell belongs to the same tracking area as the network cell to which the user equipment previously connected, and assuming the tracking area to which the new network cell and the previously connected network cell belong provides homogeneous slice support, the user equipment can use slice groups already available to the user equipment to connect to the reselected new network cell.

[0033] Performing cell reselection and / or random access operations on network cells (e.g., slice-specific cell reselection and / or slice-specific random access operations) based at least partially on the acquired SGM configuration may be interpreted as meaning that performing cell reselection and / or random access operations may be based on at least one mapping between slice groups and tracking areas indicated by the SGM configuration (e.g., by being included in the SGM configuration). For example, performing cell reselection and / or random access operations may be based at least partially on the respective mapping of each slice group to each tracking area containing each network cell. In particular, such mappings allow user equipment to use specific slice groups that are specific to each tracking area containing each network cell on which the cell reselection and / or random access operation is performed. For example, performing reselection and / or random access operations may include steps such as selecting specific random access channel resources and / or correctly prioritizing frequencies.

[0034] Preferably, user equipment can perform slice-specific cell reselection and / or random access operations on network cells, for example, based on the corresponding information contained in or comprising a slice group specific to each network cell. User equipment can benefit from network slice-based services when connecting to network cells, for example, by at least one mapping between the required slice groups and the tracking area containing each network cell.

[0035] In other examples, as further described below, it may be intended that a user device performs cell reselection and / or random access operations on network cells that fall within tracking areas where, for example, the acquired SGM configuration does not indicate (e.g., does not include) a corresponding slice group mapping. For example, after determining (e.g., by the user device) that such a case exists based on the acquired SGM configuration, the user device may proceed with fallback options, as further described below.

[0036] Referring to the first network node, the SGM setting is acquired by the network node before providing the user equipment with an SGM setting that shows at least one mapping between slice groups and tracking areas. In some embodiments, acquiring the SGM setting may be interpreted as the network node acquiring the SGM setting by determining the SGM setting, but in further embodiments, the network node may acquire the SGM setting by acquiring the SGM setting from the network node's memory. In other examples, the acquisition step may be interpreted as receiving the SGM setting from another network node (e.g., a wireless access network node or a core network node), as further described below.

[0037] In some embodiments, determining the SGM configuration may involve selecting one or more mappings between each slice group and each tracking area from a plurality of such mappings, where the selected one or more mappings may be mappings between each slice group and each tracking area, where each tracking area is adjacent to a tracking area belonging to at least one of a registration area assigned to the user device (e.g., the user device to which the SGM configuration is provided) and a wireless access network notification area assigned to the user device (e.g., the user device to which the SGM configuration is provided).

[0038] The provision of SGM settings may be interpreted as meaning that the SGM settings are provided to the user equipment (e.g., the user equipment in the first exemplary embodiment) by, for example, a network node transmitting the settings to the user equipment. The SGM settings may then be available to the user equipment as a basis for performing cell reselection and / or random access operations, as described above. The first network node in the second exemplary embodiment may thus provide the respective SGM settings to the user equipment, for example, and thus enable the user equipment to perform slice-specific cell reselection and / or random access operations based on the corresponding information contained in the slice group specific to each network cell.

[0039] Further exemplary features and embodiments of various aspects of this disclosure will be described in more detail below.

[0040] According to an exemplary embodiment of the first exemplary embodiment, the SGM setting is obtained (by the user equipment according to the first exemplary embodiment) from at least one of the core network and the wireless access network (for example, according to the second exemplary embodiment).

[0041] According to another exemplary embodiment of the first exemplary aspect, obtaining SGM settings from the core network is: To obtain SGM settings in the non-access layer, Includes, Obtaining SGM settings from a wireless access network is possible. Obtaining SGM settings in downlink signaling and / or messages, Includes.

[0042] Furthermore, according to an exemplary embodiment of the first exemplary aspect, the user device acquires the SGM setting, Obtaining SGM settings from the core network, or Obtaining SGM settings from the wireless access network, Includes.

[0043] Furthermore, according to the exemplary embodiment of the first exemplary aspect, obtaining SGM settings from the core network is: Obtaining SGM settings in non-accessible layer (NAS) signaling and / or messages, Includes, Obtaining SGM settings from a wireless access network is possible. To obtain SGM settings in Radio Resource Control (RRC) signaling and / or messages, Includes.

[0044] In one embodiment, the SGM setting may be obtained from the network by the user equipment, and the network may be a core network or a radio access network. In particular, the network may be represented by network nodes in the second exemplary embodiment. With respect to the 5G architecture, further details regarding the overall structure and function of the core network and radio access network are described in the applicable technical specifications (see, for example, 3GPP® TS 23.003). When the SGM setting is obtained from the core network, the SGM setting can be obtained more specifically from core network nodes such as an AMF via the non-access layer. In other embodiments, when the SGM setting is obtained from the radio access network, the SGM setting can be obtained more specifically from radio access network nodes such as base stations (also referred to as gNBs) as defined by, for example, 3GPP® 5G or NR standards. In this embodiment, the SGM setting may be obtained by the user equipment in downlink signaling (e.g., RRCReconfiguration) and / or messages (e.g., handover messages).

[0045] According to an exemplary embodiment of the first exemplary aspect, at least one memory and computer program code are further transmitted to the user device by at least one processor. When user equipment moves from the first TA to the second TA, check whether the SGM settings are valid for the second TA, and / or When a user device moves from the first RA to the second RA, check whether the SGM setting is valid for the second registration area (RA). It was further configured to execute [the command].

[0046] Furthermore, according to an exemplary embodiment of the first exemplary aspect, at least one processor further, When a user device moves from the first TA to the second TA, check whether the SGM setting is valid for the second TA, or, When a user device moves from the first RA to the second RA, the system checks whether the SGM settings are valid for the second registration area (RA). It is configured in this way.

[0047] In one embodiment, a user device may move (e.g., into idle / inactive mode) within one specific tracking area, or from one tracking area (e.g., a first tracking area to which the user device was previously connected) to another tracking area (e.g., a second tracking area that the user device may have selected by cell reselection, e.g., by selecting a network cell belonging to the second tracking area). In such an example, the user device may be required to perform cell reselection and / or random access operations on network cells belonging to the second tracking area, for example, and for this purpose a corresponding slice group (e.g., a slice group unique to each network cell included in the second tracking area). In such an example, the user device may check whether the acquired SGM settings are valid for the second tracking area. In particular, this can be interpreted as meaning that the user device, or the user device, checks whether the second tracking area can correspond to a specific tracking area in which the acquired SGM settings indicate at least one mapping (e.g., a mapping between a slice group and a specific tracking area). Therefore, for example, if at least one mapping between a slice group and a tracking area indicated by the SGM setting is a mapping between a slice group and a second tracking area, then the acquired SGM setting is considered valid for the second tracking area. If the acquired SGM setting is valid for the second tracking area, the user equipment can, for example, perform cell reselection and / or random access operations for each network cell belonging to the second tracking area, at least in part, based on the acquired SGM setting (e.g., indicating or configuring a mapping between a slice group and a second tracking area).

[0048] In some of the exemplary embodiments, the first tracking area may be an adjacent tracking area of ​​the first tracking area, which can be interpreted, for example, as the coverage of network cells belonging to the first tracking area being adjacent to the coverage of network cells belonging to the second tracking area. In further examples of the exemplary embodiments, the first tracking area may be a non-adjacent tracking area of ​​the second tracking area.

[0049] In other examples of all exemplary embodiments, the first tracking area may belong to the same registration area as the second tracking area (e.g., the first registration area assigned to the user equipment). In this embodiment, the respective tracking area identifiers for the first and second tracking areas may both be listed in the same registration area. In such a case, for example, if the SGM settings are determined at least in part on the registration area to which the first and second tracking areas belong (e.g., by the network node from which the user equipment obtains the SGM settings), the obtained SGM settings may be valid in particular for the second tracking area.

[0050] In other examples of all exemplary embodiments, user equipment may be expected to move from a first registration area to a second registration area different from the first registration area, and, for example, perform cell reselection and / or random access operations on network cells belonging to tracking areas listed in the second registration area rather than the first registration area. Accordingly, user equipment may check whether the acquired SGM setting is valid for the second registration area. In particular, this may be interpreted as meaning that user equipment checks whether the tracking areas listed in the second registration area can correspond to a particular tracking area in which the acquired SGM setting indicates at least one mapping (e.g., a mapping between a slice group and a particular tracking area). Accordingly, for example, if the at least one mapping between a slice group and a tracking area indicated by the SGM setting is a mapping between a slice group and a tracking area belonging to the second registration area, then the acquired SGM setting is considered valid for the registered tracking area.

[0051] Considering all the exemplary embodiments described above, if the results of each check indicate that the SGM setting is valid for the second tracking area and / or second registration, the user device may, at least in part, proceed with performing cell reselection and / or random access operations to the corresponding network cell, for example, based on the acquired SGM setting.

[0052] According to an exemplary embodiment of the first exemplary aspect, at least one memory and computer program code are further transmitted to the user device by at least one processor. This involves falling back to legacy Random Access Channel (RACH), which includes using RACH resources without SGM support. It was further configured to execute [the command].

[0053] Furthermore, according to an exemplary embodiment of the first exemplary aspect, at least one processor further, Falling back to Legacy Random Access Channel (RACH), Legacy RACH includes using RACH resources without SGM support. It is configured in this way.

[0054] As disclosed above, in some examples, user equipment may be intended to perform cell reselection and / or random access operations on network cells that are included in or comprised of tracking areas where the corresponding slice group mapping is not indicated in the acquired SGM configuration. In such cases, user equipment may fall back to a legacy random access channel, which may be a random access channel without SGM support. In other embodiments, the legacy random access channel can use a random access channel resource that is not mapped to any slice group. This allows the user equipment to avoid potential flaws caused by slice-specific reselection or slice-specific random access operations when a valid SGM configuration is not available, by falling back to the legacy mechanism, respectively.

[0055] According to an exemplary embodiment of the first exemplary aspect, at least one memory and computer program code are further transmitted to the user device by at least one processor. In uplink signaling and / or messages, an invalid SGM configuration is indicated to the network, and the uplink signaling and / or messages include messages 3 (MSG3), 5 (MSG5), or 1 (MSG1) of the RACH procedure or Radio Resource Control (RRC) signaling. It was further configured to execute [the command].

[0056] Furthermore, according to an exemplary embodiment of the first exemplary aspect, at least one processor further, Uplink signaling and / or messages indicate an invalid SGM to the network, and the uplink signaling and / or messages include Random Access Channel (RACH) message 3 (MSG3), MSG5, or MSG1, or RRC signaling. It is configured in this way.

[0057] As disclosed above, an invalid SGM setting may exist, for example, when a particular SGM setting does not indicate a mapping between slice groups and a specific tracking area that includes or constitutes network cells, for example, on which the user device intends to perform cell reselection and / or random access operations. In such a case, the user device can indicate to the network (e.g., a radio access network node or core network node in a second exemplary embodiment) that the acquired SGM setting is invalid. For such an indication, for example, the known message 3 from the four-step random access procedure between the user device and the network (including the preamble, response, message 3 and message 4) can be used to report an invalid SGM setting to the respective network. In further examples of all exemplary embodiments, any other arbitrary uplink message (e.g., for idle / inactive user devices) can be used to indicate an invalid SGM setting. In response to indicating an invalid SGM setting, the respective network may provide another (e.g., a valid) SGM setting (e.g., SGM reconfiguration) by, for example, using a downlink message (e.g., message 5) or an RRC reconfiguration message.

[0058] According to the first exemplary embodiment or the second exemplary embodiment, the SGM setting is: A set of slice groups to map to a set of TAs. One or more mappings between slice groups and TAs, One or more mappings between physical cell identifiers (PCIs) and slice groups, It comprises at least one of the following.

[0059] According to the first exemplary embodiment and / or other exemplary embodiments of the second exemplary embodiment, the slice group mapping further comprises at least one inter-slice group mapping.

[0060] As a non-limiting example, a particular SGM configuration could represent (e.g., by configuring) three mappings between each slice group (e.g., slice group 1, slice group 2, slice group 3) and each tracking area (tracking area 1, tracking area 2, tracking area 3), where slice group 1 is specific to tracking area 1, slice group 2 is specific to tracking area 2, and slice group 3 is specific to tracking area 3. In this case, the set of slice groups 1 to 3 can be interpreted as corresponding to (e.g., therefore mapped to) the set of tracking areas 1 to 3. Thus, an SGM configuration could include one or more mappings (three mappings in this embodiment) between each slice group and the corresponding tracking area (i.e., one mapping between slice group 1 and tracking area 1, one further mapping between slice group 2 and tracking area 2, and one further mapping between slice group 3 and tracking area 3). Considering that tracking areas 1, 2, and 3 contain or have different network cells, the three mappings shown in the SGM configuration could be, for example, one mapping between each network cell belonging to tracking area 1 and slice group 1, one mapping between the network cells belonging to tracking area 2 and slice group 2, and one mapping between the network cells belonging to tracking area 3 and slice group 3. Here, each network cell can be represented, for example, by its corresponding physical cell identifier.

[0061] According to further examples of all exemplary embodiments, each slice group mapping may include at least one inter-slice group mapping. For example, a slice group may represent a list of slices, and the representation of a list of slices by each slice group may be interpreted as a mapping from slice to slice group. For example, slice group 1 is mapped to slices 1 and 2, and slice group 2 is mapped to slices 3 and 5. Thus, if a particular slice group is, for example, unique and therefore mapped to its respective tracking area, then each inter-slice group mapping included in or composed of that slice group can be considered similarly unique and therefore mapped to its respective tracking area.

[0062] The SGM configuration, which provides at least one mapping between slice groups and tracking areas to the user equipment, may be acquired by the user equipment and used when performing cell reselection and / or random access operations on network cells. In some embodiments, further conditions regarding how the SGM configuration is provided to the user equipment may depend, for example, whether the SGM configuration is provided by a radio access network node or a core network node, as further disclosed below.

[0063] According to an exemplary embodiment of the second exemplary aspect, at least one memory and computer program code are further transmitted to the first network node by at least one processor. Determine the SGM settings. It is further configured to carry out the task.

[0064] Furthermore, according to an exemplary embodiment of the second exemplary aspect, at least one processor further, Determine the SGM settings. It is configured in this way.

[0065] According to another exemplary embodiment of the second exemplary aspect, at least one memory and computer program code are further transmitted to the first network node by at least one processor. Based on at least one mapping between slice groups and TAs, and in particular based on the registration area assigned to the user equipment, the SGM settings are determined. It is further configured to carry out the task.

[0066] According to yet another exemplary embodiment of the second exemplary aspect, at least one memory and computer program code are further transmitted to the first network node by at least one processor. The registration area (RA) settings of user devices are obtained from the core network node, and the SGM settings are determined. It is further configured to carry out the task.

[0067] Furthermore, according to an exemplary embodiment of the second exemplary aspect, at least one processor further, The registration area (RA) settings of user devices are obtained from the core network node, and the SGM settings are determined. It is configured in this way.

[0068] As described above regarding the acquisition of SGM settings, a network node can perform the step of determining the SGM settings. For example, determining the SGM settings may be based at least partially on at least one mapping (e.g., acquired by the network node) and on other information. According to the exemplary embodiment described above, determining the SGM settings may be based on at least one mapping between slice groups and tracking areas, and on registration areas assigned to user equipment. This can be interpreted as meaning that, for example, a network node acquires multiple mappings between each slice group and tracking areas, and can map one or more slice groups to one or more tracking areas that are included in or comprised of registration areas (e.g., registration areas assigned to user equipment for which SGM settings should be provided), and selects a particular mapping from these multiple mappings. In other words, at least one acquired mapping between slice groups and tracking areas can be matched with one or more tracking areas that are included in or comprised of registration areas.

[0069] For example, a network node can obtain one or more mappings between each slice group and a tracking area (e.g., slice group 1 is mapped to tracking area 1, slice group 2 is mapped to tracking area 2, and slice group 3 is mapped to tracking area 3). Furthermore, the network node can obtain a registration area listing tracking areas 1 and 2. Since these mappings relate to each tracking area contained in or composed of the registration area, the network node can then determine the SGM configuration by selecting the mappings between slice group 1 and tracking area 1, and between slice group 2 and tracking area 2.

[0070] By determining the SGM settings based at least partially on the registration area assigned to the user device (e.g., the user device for which the SGM settings are provided), it is possible to ensure that the SGM settings represent (e.g., configure) a mapping between slice groups and tracking areas for all tracking areas included in the registration area assigned to the user device (e.g., the user device for which the SGM settings are provided).

[0071] Furthermore, with respect to the exemplary embodiments described above, it should be noted that the use of registration areas when determining each SGM setting is independent of whether the network node where the SGM setting is determined is a radio access network node or a core network node. Considering an example where the network node in the second exemplary embodiment is a core network node, the registration areas (e.g., registration areas assigned to user equipment for which SGM settings are provided) may be available on the core network node. In other examples where the network node is a radio access network node in the second exemplary embodiment, the registration areas may not be available on the radio access network node initially (e.g., because radio access network nodes generally do not know about registration areas assigned to user equipment). In such examples, the radio access network node may obtain one or more registration areas (e.g., registration areas assigned to user equipment for which SGM settings are provided) and then use these one or more registration areas when determining the SGM setting. For example, the radio access network node may obtain one or more registration areas from the core network, particularly from core network nodes such as AMF (e.g., via an NG interface).

[0072] In some examples of the second exemplary embodiment, assuming that a network node is a radio access network node that acquires one or more registration areas from a core network, such acquisition may be performed and / or controlled in response to an initial message sent to the core network by the radio access network node. For example, this initial message may contain or consist of information specific to a user device (e.g., according to the first exemplary embodiment) for which the respective SGM settings should be provided, for example by establishing a connection between the radio access network node and the specific user device (e.g., by establishing an RRC connection) before sending the initial message to the core network. In such an example, the core network may respond to the initial message sent by the radio access network node by providing an initial context setting that includes registration areas assigned to the user device for which the initial message contains the specific information.

[0073] As described above, obtaining the registration area assigned to the user device can be interpreted as meaning that the registration area is available on the network node and therefore can be obtained, for example, from the network node's memory. In other embodiments, the registration area may be obtained (e.g., received) by the network node from one or more network nodes (e.g., core network nodes such as AMF).

[0074] According to another exemplary embodiment of the second exemplary aspect, at least one memory and computer program code are further transmitted to the first network node by at least one processor. Obtaining support information, which indicates that the user device has an invalid SGM setting, and / or Based on the invalid SGM settings shown, provide the user's device with valid SGM settings. It was further configured to execute [the command].

[0075] According to an exemplary embodiment of the second exemplary aspect, at least one processor further, Retrieve support information, which indicates that the user device has an invalid SGM setting, and / or Based on the invalid SGM settings shown, provide valid SGM settings to the user's device. It is configured in this way.

[0076] For example, support information can be obtained from user devices that have invalid SGM settings. In such cases, invalid SGM settings may exist on the user device after the SGM settings have been obtained (e.g., received) from the network node.

[0077] According to another exemplary embodiment of the second exemplary aspect, the first network node further comprises at least one transceiver, the at least one transceiver is Send a slice configuration update to the second network node, and the slice configuration update includes at least one SGM configuration, or The second network node receives a slice configuration update, and the slice configuration update includes at least one SGM configuration. It is configured in this way.

[0078] For example, the second network node may be a radio access network node or a core network node (e.g., AMF). For example, slice configuration updates may be sent to the second network node in radio access network configuration updates (RAN configuration updates), and the second network node may receive multiple radio access network configuration updates from multiple network nodes. In such an example, the second network node may be a core network node (e.g., AMF) that collects multiple SGM configurations from various radio access network nodes.

[0079] In another embodiment, the first network node can receive a slice configuration update from the second network node during a wireless access network configuration update (RAN configuration update). The first network node can then provide the SGM configuration included in the wireless access network configuration update to the user equipment.

[0080] According to an exemplary embodiment of the second exemplary aspect, the first network node includes a core network node or a wireless access network node.

[0081] For example, whether a network node is a core network node or a wireless access network node may affect how SGM settings are provided to user equipment and how at least one mapping between slice groups and tracking areas is obtained, as further disclosed below.

[0082] According to other exemplary embodiments of the second exemplary embodiment, the network node is a core network node and the SGM configuration is provided to the user equipment at the non-access layer, or the network node is a radio access network node and the SGM configuration is provided to the user equipment via downlink signaling and / or messages.

[0083] Considering one example, SGM settings may be provided to each user device by a core network node or a radio access network node. In the case of a 5G architecture as an example, if the SGM settings are provided by a core network node, the SGM settings may be provided more specifically by a core network node such as an AMF via the non-access layer. In other embodiments, if the SGM settings are provided by such a radio access network node, the SGM settings may be provided more specifically by a radio access network node such as a base station (also referred to as a gNB) as defined by the 3GPP® 5G or NR standard. In this example, the SGM settings may be obtained by the user device in downlink signaling (e.g., RRCreconfiguration) and / or messages (e.g., handover messages).

[0084] According to an exemplary embodiment of the second exemplary aspect, the network node is a core network node, and at least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, is obtained from one or more further radio access network nodes.

[0085] According to another exemplary embodiment of the second exemplary aspect, the network node is a core network node, and at least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, is obtained from one or more additional radio access network nodes in one or more radio access network configuration updates.

[0086] Consider an example where a network node is a core network node. The core network node may obtain at least one mapping between slice groups and tracking areas, and / or at least one SGM configuration from one or more radio access network nodes (e.g., in one or more radio access network configuration updates). For example, the core network node may obtain multiple mappings between each slice group and each tracking area from multiple radio access network nodes, and each of the multiple mappings may be obtained from each radio access network node (e.g., in each radio access network configuration update). In particular, each mapping between a slice group and a tracking area may be obtained from the radio access network node that provides each network cell contained in or composed of each tracking area.

[0087] According to an exemplary embodiment of the second exemplary aspect, the first network node is a wireless access network node, and At least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, is obtained from a core network node, or At least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, is obtained from one or more additional radio access network nodes.

[0088] In some embodiments, the network node may be a radio access network node, and at least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, is obtained from the core network node (which may be, for example, an AMF) in response to an initial message sent from the radio access network node to the core network node. In some embodiments, such an initial message may contain or consist of information specific to the user equipment for which the SGM configuration is provided. Thus, the core network node can select at least one mapping between slice groups and tracking areas, and / or at least one SGM configuration, according to the user equipment for which the SGM configuration is provided (for example, based on registration areas available in the core network and assigned to the user equipment identified by the information contained in the initial message). Further considering this embodiment, one or more selected mappings and / or SGM configurations are then provided by the core network node to the radio access network node providing the SGM configuration.

[0089] Consider an example where at least one mapping between each slice group and each tracking area, and / or at least one SGM configuration, is obtained from the core network node. This at least one mapping and / or at least one SGM configuration can be obtained at the core network node from, for example, further radio access network nodes (including, for example, radio access network nodes that provide SGM configurations). For example, this could initially make the mapping between slice groups and tracking, and / or SGM configuration, unavailable at the core network node until such mapping and / or configuration is obtained (e.g., collected) from further radio access network nodes.

[0090] In other examples of the second exemplary embodiment, the network node may be a radio access network node, and at least one mapping and / or at least one SGM setting between slice groups and tracking areas may be obtained, for example, from one or more further radio access network nodes. For example, a radio access network node may obtain multiple mappings and / or multiple SGM settings between each slice group and each tracking area from multiple further radio access network nodes, and each of the multiple mappings and / or each SGM setting is obtained from each radio access network node (for example, in each radio access network setting update). In particular, each mapping and / or each SGM setting between slice groups and tracking areas may be obtained from a radio access network node that provides network cells included in each tracking area. Thus, in some examples of the second exemplary embodiment, it may be initially (for example, initially only) available at the radio access network node providing the SGM setting that the mapping between slice groups and tracking areas includes or is configured with network cells provided by the radio access network node providing the SGM setting. By obtaining mappings and / or SGM settings between slice groups and tracking areas from further radio access network nodes, the radio access network node providing the SGM settings collects multiple mappings and / or SGM settings between each slice group and each tracking area, provides them to user equipment in the form of SGM settings, and the user equipment can then perform cell reselection and / or random access operations, for example, for various network cells, based on the obtained SGM settings.

[0091] According to an exemplary embodiment of the second exemplary aspect, the first network node is a radio access network node, and obtaining at least one mapping between slice groups and tracking areas, and / or SGM settings from the core network node, An Access and Mobility Management Function (AMF) configuration update includes obtaining at least one mapping and / or at least one SGM configuration. Obtaining at least one mapping and / or at least one SGM configuration between slice groups and tracking areas from one or more additional wireless access network nodes is possible. One or more RAN configuration updates include obtaining at least one mapping and / or at least one SGM configuration.

[0092] Considering an example where multiple mappings and / or SGM settings between each slice group and tracking area are obtained at a radio access network node as a network node from or by a core network node, these multiple mappings and / or SGM settings may be obtained together in one particular AMF configuration update. In other examples of all exemplary embodiments, multiple mappings and / or SGM settings between each slice group and tracking area may be obtained at a radio access network node as a network node from multiple further radio access network nodes, and each of these multiple mappings (and / or each of these multiple SGM settings) may be obtained from each further radio access network node in each radio access network configuration update.

[0093] According to an exemplary embodiment of the third exemplary aspect, the system may further include user equipment disclosed according to the first aspect and network nodes disclosed according to the second aspect, the network nodes may be wireless access network nodes or core network nodes. As described above with respect to various aspects of the disclosure, wireless access network nodes or core network nodes according to the second exemplary aspect may communicate with each other and / or with further wireless access network nodes. Thus, the system according to the third exemplary aspect may include further wireless access network nodes in addition to the wireless access network nodes or core network as network nodes and user equipment.

[0094] The embodiments disclosed herein are illustrative and not limiting.

[0095] Herein, the disclosure of method steps shall also be considered as the disclosure of means for carrying out each method step. Similarly, the disclosure of means for carrying out a method step shall also be considered as the disclosure of the method step itself.

[0096] Other features of this disclosure will become apparent from the following detailed description, which will be presented in conjunction with the accompanying drawings. However, it should be understood that the drawings are for illustrative purposes only and do not define the scope of this disclosure; for this, refer to the accompanying claims. Furthermore, it should be understood that the drawings are not drawn to scale and are merely for conceptual illustration of the structures and procedures described herein. [Brief explanation of the drawing]

[0097] In the following sections, various exemplary embodiments will be described in more detail with reference to the attached drawings. [Figure 1] Figure 1 is a block diagram of an exemplary embodiment of user equipment in various forms. [Figure 2] Figure 2 is a block diagram of exemplary embodiments of various network node configurations. [Figure 3] Figure 3 is a flowchart of an exemplary embodiment of the first exemplary aspect. [Figure 4] Figure 4 is a flowchart of an exemplary embodiment of the second exemplary aspect. [Figure 5] Figure 5 is an exemplary signaling chart showing various exemplary embodiments. [Figure 6] Figure 6 shows another exemplary signaling chart illustrating various exemplary embodiments. [Figure 7a] Figure 7a shows another exemplary signaling chart illustrating exemplary embodiments of various aspects. [Figure 7b] Figure 7b shows another exemplary signaling chart illustrating various exemplary embodiments. [Figure 8] Figure 8 is a schematic diagram showing examples of tangible and non-transient computer-readable storage media. [Modes for carrying out the invention]

[0098] The following description will be helpful in understanding this disclosure and will complement, and should be read together with, the description of exemplary embodiments in the above "Summary" section of this specification.

[0099] Note that in this disclosure, network slices are sometimes referred to simply as slices. A slice group includes a set of network slices. Slices included in a slice group may have common or similar network service characteristics.

[0100] Figure 1 is a block diagram of an exemplary embodiment of the user device 100 according to the present disclosure. For example, the user device 100 may be a smartphone, a tablet computer, a notebook computer, a smartwatch, a smart band, an IoT device, or a vehicle or a part thereof.

[0101] The user device 100 includes a processor 101. The processor 101 may refer to a single processor or two or more processors, at least partially connected, for example, via a bus. The processor 101 executes program code stored in program memory 102 (for example, program code that, when executed on the processor 101, causes the user device 100 connected to the network node 200 to execute one or more embodiments or parts thereof of embodiments of the method according to this disclosure) and communicates with main memory 103. The program memory 102 may include an operating system for the processor 101. Some or all of the memories 102 and 103 may also be included in the processor 101.

[0102] One or both of the processor's main memory and program memory (e.g., program memory 102 and main memory 103) may be fixedly connected to the processor (e.g., processor 101), or they may be at least partially detachable from the processor, for example, in the form of a memory card or memory stick.

[0103] The program memory (e.g., program memory 802) may be, for example, a non-volatile memory. It may be, for example, flash memory (or a part thereof), ROM, PROM, EPROM, MRAM, FeRAM (or a part thereof), or a hard disk (or a part thereof). For example, the program memory may comprise, for example, a first memory section that is fixedly installed and a second memory section that is removable, for example, in the form of a removable SD memory card.

[0104] The main memory (for example, main memory 103) may be, for example, volatile memory. It may be, for example, DRAM memory, to give an unspecified example. It can be used as working memory for the processor 101 when, for example, running the operating system, applications, programs, and / or the like.

[0105] Furthermore, processor 101 controls a communication interface 104 (e.g., a radio interface) configured to receive and / or transmit data and / or information. For example, communication interface 104 may be configured to transmit and / or receive radio signals from a network node such as a base station. Processing based on any computer program code necessary for receiving and / or evaluating radio signals may be stored in the communication interface 104's own memory and executed by the communication interface 104's own processor, and / or may be stored in memory 103, for example, and executed by processor 801, for example.

[0106] The communication interface 104 can be configured to communicate in accordance with a cellular communication system, such as 2G / 3G / 4G / 5G / NR or a next-generation cellular communication system. User equipment 100 can communicate with a network node using the wireless interface 104, as shown in Figure 2.

[0107] For example, the communication interface 104 may further comprise a BLE (Bluetooth® Low Energy) and / or Bluetooth® radio interface, including a BLE transmitter, receiver, or transceiver. For example, the radio interface 104 may additionally or alternatively comprise a WLAN (Wireless Local Area Network) radio interface, including at least a WLAN transmitter, receiver, or transceiver.

[0108] The components 102 to 104 of the mobile device 100 can be connected to the processor 801, for example, by one or more serial buses and / or parallel buses.

[0109] It should be understood that the user device 100 may include various other components. For example, the user device 100 may optionally include a user interface (e.g., a touch-sensitive display, keyboard, touchpad, display, etc.).

[0110] Figure 2 is a block diagram of an exemplary embodiment of a network node. For example, the network node 200 may be configured to schedule and / or transmit at least one of signals or messages to user equipment, as described above.

[0111] The network node 200 includes a processor 201. The processor 201 may refer to a single processor or two or more processors, which are at least partially connected, for example, via a bus. The processor 201 executes program code stored in program memory 202 (for example, program code that causes the device 200 to execute an embodiment of the user device 100 according to this disclosure or a part thereof, either alone or together with the device 200) and connects to main memory 203.

[0112] The program memory 202 may contain the operating system of the processor 201. Some or all of the memories 202 and 203 may be included in the processor 201.

[0113] Furthermore, the processor 201 controls a communication interface 204 configured to communicate according to a cellular communication system, such as a 2G / 3G / 4G / 5G / NR cellular communication system. The communication interface 204 of the network node 200 may be provided for communication between the network node and user equipment.

[0114] The components 202 to 204 of the network node 200 may be connected to the processor 201 by, for example, one or more serial buses and / or parallel buses.

[0115] The user device 100, along with the communication interface 104, can be configured to receive signals from and transmit signals to the network node 200 in this embodiment.

[0116] Please understand that devices 100 and 200 may have various other components.

[0117] Figure 3 is a flowchart 300 illustrating an exemplary embodiment of a method according to a first exemplary aspect of the present disclosure. Without limiting the scope of the present disclosure, it is assumed below that user equipment, such as that depicted in Figure 1, performs the operations / steps of flowchart 300.

[0118] In step 310, the user device obtains an SGM configuration, which indicates at least one mapping between slice groups and tracking areas.

[0119] For example, referring to the exemplary embodiment shown in Figure 5 (step 508 in the signaling chart 500), the user device 510 can obtain an SGM setting by downlink signaling (e.g., RRCRelease) from the gNB1 520 as a radio access network node, where the SGM setting indicates one or more mappings between the SGM and tracking areas (TAs). The SGM may further include mappings between slices (e.g., a first mapping of SGM1 to TA1 and a second mapping of SGM3 to TA5) and slice group mappings. Similar examples for obtaining an SGM setting are shown in the exemplary embodiments of Figure 6 (step 608 in the signaling chart 600), Figures 7a and 7b (step 710 in the signaling chart 700).

[0120] In step 320, the user equipment performs, for example, cell reselection and / or random access operations to a network cell or base station, based at least in part on the acquired SGM settings.

[0121] For example, referring to the exemplary embodiment shown in Figure 5 (step 509 in the signaling chart 500), the user device 510 can use the SGM settings obtained from the gNB1 510 as a radio access network node when performing slice-specific (e.g., slice-based) cell reselection. In particular, the obtained SGM settings indicate (e.g., configure) the mapping between slice groups (e.g., SGM1, SGM3) and tracking areas (TA1, TA5) for tracking areas included in the registration area (RA) assigned to the user device 510.

[0122] Figure 4 is a flowchart 400 illustrating an exemplary embodiment of a method according to a second exemplary aspect of the present disclosure. Without limiting the scope of the present disclosure, it is assumed below that a network node as depicted in Figure 2 performs the operation of flowchart 400.

[0123] In step 410, the network node obtains at least one mapping between slice groups and tracking areas.

[0124] For example, referring to the exemplary embodiment shown in Figure 5 (step 502 in the signaling chart 500), the radio access network node gNB1 520, acting as a network node, can obtain one mapping between a slice group (including an inter-slice mapping SGM3 for TA5) and a tracking area (TA5) from another radio access network node, gNB3 530. Furthermore, gNB1 520 can obtain another mapping between a slice group (including an inter-slice mapping SGM2 for TA2) and a tracking area (TA2) from another further radio access network node, gNB2 540.

[0125] In another example, referring to the exemplary embodiment shown in Figure 6 (step 605 of the signaling chart 600), the radio access network node gNB1 520 as a network node can obtain two mappings from the core network (e.g., the AMF as a core network node) between each slice group (including inter-slice mapping SGM1 for TA1 and inter-slice mapping SGM3 for TA5, respectively) and each tracking area (TA1 and TA5). A similar example of obtaining mappings from the core network is given in step 703 of the signaling chart 700.

[0126] In step 420, the network node provides an SGM configuration that shows at least one mapping between slice groups and tracking areas.

[0127] For example, referring to the exemplary embodiment shown in Figure 5 (step 508 in the signaling chart 500), the gNB1 520 as a radio access network node provides the SGM configuration to the user equipment 510 by downlink signaling (e.g., RRCRelease), and the SGM configuration shows two mappings between slice groups and tracking areas (e.g., a first mapping of SGM1 to TA1 and a second mapping of SGM3 to TA5), which configure the mapping to slice groups. Similar examples for providing the SGM configuration are shown in the exemplary embodiments of Figure 6 (step 608 in the signaling chart 600), Figures 7a and 7b (step 710 in the signaling chart 700).

[0128] The operations / steps shown in exemplary flowcharts 300 and 400 may generally provide a solution to the condition that the core network may also provide slices for slice group mapping. Furthermore, if the core network does not provide slice group mapping information / configurations to a particular wireless access network node, that particular wireless access network node may not be aware of the slice group mappings of other wireless access network nodes (e.g., including neighboring wireless access network nodes). In addition, wireless access network nodes may not be aware of the registration areas assigned to each user device.

[0129] For example, when a user device is idle / inactive, it may move from one tracking area to another, or within a single tracking area. If the slice group mappings of different tracking areas are different, the user device will need information about such differences when re-selecting the appropriate network cell. Another example considering movement within a single tracking area is that some wireless access network nodes (e.g., some gNBs) may lack slice group support, which can cause problems when the user device camps in the appropriate network cell.

[0130] For example, the solutions provided by all exemplary embodiments may enable a user device to obtain one or more mappings between slice groups and tracking areas, such one or more mappings may be valid within a registration area assigned to the user device. In this embodiment, the user device can configure one or more such mappings between slice groups and their respective tracking areas via the core network. This SGM configuration allows the user device to automatically perform cell reselection / random access resource selection based on the SGM configuration.

[0131] In other examples, one or more mappings are configured by a wireless access network node, and one or more mappings are active within a specific tracking area. For example, a gNB as a wireless access network node may provide a user device with an SGM setting that indicates slice group mappings for adjacent tracking areas. In this embodiment, when the user device moves to an adjacent tracking area, it can use this SGM setting to perform and / or control cell reselection / random access resource selection.

[0132] In yet another example, if the gNB cannot obtain the slice group mapping for adjacent tracking areas, the user device can perform a slice group mapping update when moving from tracking area TA1 to tracking area TA2, and TA1 and TA2 can belong to the same registered area configured on the user device. For example, when the user device moves from TA1 to TA2, an invalid mapping can be indicated using, for example, MSG3 or other uplink messages (for idle / inactive states). In this embodiment, the network can configure a valid mapping on the user device using downlink messages such as MSG5 or RRCreconfiguration.

[0133] Figure 5 shows an exemplary signaling chart 500 illustrating exemplary embodiments of various aspects of the present disclosure. According to the exemplary embodiment, the signaling chart 500 can be understood as a signaling chart for slice group mapping on a RAN.

[0134] For illustrative purposes and without limiting the scope of this disclosure, it is assumed that a user device 510 (e.g., user device 100 as depicted in Figure 1) communicates with a RAN node indicated as gNB1 520 (e.g., network node 200 as depicted in Figure 2). gNB1 controls network cell 1 (having PCI1) belonging to TA1. According to a further exemplary embodiment, gNB1 communicates with further RAN nodes gNB2 540 and gNB3 530, with gNB2 540 controlling network cell 2 (having PCI2) belonging to TA2, and gNB3 530 controlling network cell 3 (having PCI3) belonging to TA5. According to a further exemplary embodiment, all RAN nodes gNB1 520, gNB2 540, and gNB3 540 communicate with an AMF 550 as an exemplary core network node.

[0135] As shown in Figure 5, information on the mapping from slice to slice group (hereinafter referred to as SGM1, SGM2, and SGM3) may be included in the corresponding tracking area (hereinafter referred to as TA1, TA2, and TA5) and PCI for each slice group.

[0136] Option 1: [SGM1, SGM2, SGM3] are valid under the valid area [TA1, TA2, TA5]. Option 2: {TA1, SGM1}, {TA2, SGM2}, {TA5, SGM3}, or Option 3: {PCI1, SGM1}, {PCI2, SGM2}, {PCI3, SGM3}.

[0137] Option 3 may be used in TA border edge cases or in private networks where user equipment is not expected to move over a wide area. Similarly, dynamic slice deployment is a use case where cell-specific SGMs are needed instead of TA-specific SGMs.

[0138] Referring to the example of operation shown in Figure 5, operations / steps 501 to 510 can be understood as follows.

[0139] In step 501, Operation Management and Maintenance (OAM) sets up slice-to-slice group mappings to different network cells (cells 1, 2, and 3 controlled by the corresponding gNB1, 2, and 3 in a given example). In step 502, gNB1 obtains mappings between TAs and corresponding slice groups from neighboring RAN nodes gNB2 and gNB3, where each group may contain its own slice-to-slice mapping, and its network cell may have specific TAs according to the example above, which may be {cell 1, TA1, SGM1}, {cell 2, TA2, SGM2}, and {cell 3, TA5, SGM3}. In step 503, the UE can initiate an RRC connection with network cell 1 controlled by gNB1, and in response to the initiation of the RRC connection, gNB1 sends an initial UE message to the AMF to obtain the UE context (step 504). According to this embodiment, the registration area (RA) assigned to the UE may consist of TA1 and TA5, for example, RA=[TA1,TA5]. This information is provided from AMF to RAN node gNB1 in step 505 and may come from AMF as part of the initial context setup request. The transmission in step 505 may be acknowledged by the UE by the initial context setup response in step 506.

[0140] In step 507, the RAN node gNB1 currently connected to the UE can verify the received information and determine the SGM configuration. In particular, since the UE RA consists of TA1 and TA5, gNB1 needs the mapping to be used for these TAs, which are SGM1 and SGM3.

[0141] In step 508, RAN node gNB1 sends the determined SGM configuration to the UE, including SGM1 (indicating it is for TA1) and SGM3 (indicating it is for TA5). When the UE is moving in idle mode and re-selects a network cell in TA1 or TA5, the UE can recognize the requested SGM, select the correct RACH resource, and / or prioritize the correct frequencies (step 509).

[0142] Figure 6 shows another exemplary signaling chart 600 illustrating exemplary embodiments of various aspects of the present disclosure. According to the exemplary embodiment, the signaling chart 600 can be understood as a signaling chart for slice group mapping provided via RAN, while the mapping from TA to SGM is coordinated at the NG interface.

[0143] For illustrative purposes and without limiting the scope of this disclosure, we hereby assume that a user device 610 (e.g., user device 100 as depicted in Figure 1) communicates with a RAN node indicated as gNB1 620 (e.g., network node 200 as depicted in Figure 2). The gNB1 can then control a network cell 1 (having PCI1) belonging to TA1.

[0144] In a further exemplary embodiment, gNB1 may communicate with further RAN nodes gNB2 640 and gNB3 630, where gNB2 640 controls network cell 2 (having PCI2) belonging to TA2, and gNB3 630 controls network cell 3 (having PCI3) belonging to TA5. In a further exemplary embodiment, all RAN nodes gNB1 620, gNB2 640 and gNB3 640 can communicate with AMF650 as an exemplary core network node.

[0145] Referring to the example of operation shown in Figure 6, operations / steps 601 to 608 can be understood as follows.

[0146] In step 601, the OAM can configure slices to slice group mappings to different network cells (cells 1, 2, and 3 controlled by the corresponding gNBs 1, 2, and 3 in a given example).

[0147] In step 602, all RAN nodes can provide the AMF with the slice group mapping of the corresponding TA in either an NG setup message or a RAN configuration update. The AMF acknowledges these messages.

[0148] In step 603, the UE can initiate an RRC connection with network cell 1 controlled by gNB1, and in response to the initiation of this RRC connection, it sends an initial UE message to the AMF to obtain the UE context (step 604).

[0149] In steps 605 and 606, the AMF can respond with the requested UE context and send the slice group mapping associated with the UE's registration area to the gNB1. Alternatively, the AMF can include the UE's registration area, as well as the SGM associated with the TA, in the UE context message. In this case, the RAN node gNB1 can perform a matching of the TA with the associated SGM and send a list of the associated SGMs to the UE.

[0150] In step 607, RAN node gNB1 configures the UE with the determined list of SGMs included in the determined SGM configuration. The list of SGMs can be configured in the UE via RRCReconfiguration or a handover command message. Similarly, this message can also be broadcast in a way that is decipherable only by a subset of UEs.

[0151] In step 608, the UE uses the mapping provided by the RAN node to perform slice-based cell reselection and / or slice-specific RACH operations.

[0152] Figures 7a and 7b show other exemplary signaling charts 700 illustrating exemplary embodiments of various aspects. According to the exemplary embodiments, the signaling chart 700 can be understood as a signaling chart for slice group mapping provided via RAN, while the mapping from TA to SGM is coordinated at the NG interface.

[0153] For illustrative purposes and without limiting the scope of this disclosure, UE710 (e.g., user equipment 100 as depicted in Figure 1) can communicate with a RAN node indicated as gNB1 720 (e.g., network node 200 as depicted in Figure 2). The gNB1 can then control network cell 1 (having PCI1) belonging to TA1.

[0154] In a further exemplary embodiment, gNB1 can communicate with further RAN nodes gNB2 740 and gNB3 730, gNB2 740 controls network cell 2 (having PCI2) belonging to TA2, and gNB3 730 controls network cell 3 (having PCI3) belonging to TA5. In a further exemplary embodiment, all RAN nodes gNB1 720, gNB2 740 and gNB3 740 communicate with AMF750 as an exemplary core network node.

[0155] Steps 701 and 702 depicted in the signaling chart 700 in Figures 7a and 7b are identical to steps 601 and 602 depicted in the signaling chart 600 in Figure 6. Therefore, in step 701, the OAM sets up slices to slice group mappings to different network cells (cells 1, 2, and 3 controlled by the corresponding gNBs 1, 2, and 3 in this embodiment). Furthermore, in step 702, all RAN nodes provide the AMF with the slice group mappings of the corresponding TAs in either an NG setup message or a RAN configuration update. The AMF acknowledges these messages.

[0156] Steps 703-708 depicted in signaling chart 700 can be understood as alternative options to steps 603-606 depicted in signaling chart 600, and are explained as follows:

[0157] In steps 703 and 704, the AMF provides a list of SGMs mapped to the corresponding TAs through an AMF configuration update. In step 705, the UE initiates an RRC connection with network cell 1 controlled by gNB1. Subsequently, in steps 706 and 707, the RAN node gNB1 sends an initial UE message to the AMF, which responds in the UE context and sends the UE's registration area to the RAN node. In step 708, the RAN node determines which SGM to set for the UE in relation to the registration area assigned to the UE.

[0158] Steps 709 and 710, as depicted in the signaling chart 700 in Figures 7a and 7b, are identical to steps 607 and 608, as depicted in the signaling chart 600 in Figure 6. Therefore, in step 709, the RAN node gNB1 configures the UE with the determined list of SGMs included in the determined SGM configuration. The list of SGMs can be configured in each UE via RRCReconfiguration or handover command messages. Similarly, messages can be broadcast in a manner that can only be decoded by a subset of UEs. In step 710, the UEs use the mapping provided by the RAN node to perform slice-based cell reselection and / or slice-specific RACH operations.

[0159] As an additional note to the exemplary embodiments given by signaling charts 600 and 700, the list of SGMs corresponding to different TAs for each SGM may be separate for cell reselection and RACH. The list of SGMs may be further extended through other lists for other slice-specific functional behaviors. Furthermore, if RA is not available in RAN, the SGM may be determined simply based on information exchange on Xn. Thus, the effective area of ​​the provided SGM may be smaller than that of RA. Therefore, if a UE is located outside the list of TAs provided by RAN, the UE may revert to legacy cell reselection. In other examples, such as within a CU, SGM information may be exchanged via the F1AP procedure.

[0160] Figure 8 is a schematic diagram illustrating examples of tangible and non-transient computer-readable storage media according to the present disclosure that may be used to implement, for example, memory 102 in Figure 1 or memory 202 in Figure 2. For this purpose, Figure 8 shows, for example, flash® memory 800, a solid-state drive 801 including multiple memory chips (e.g., flash® memory chips), a magnetic hard drive 802, a Secure Digital (SD) card 803, a Universal Serial Bus (USB) Memory Stick 804, an optical storage medium 805 (e.g., a CD-ROM or DVD), and a magnetic storage medium 806, which may be soldered or bonded to a printed circuit board.

[0161] All connections presented in the described embodiments should be understood in the sense that the components involved are functionally coupled. Therefore, connections can be direct or indirect, regardless of the number or combination of intervening elements, and there may only be functional relationships between the components.

[0162] Furthermore, the term "circuit" as used in this text refers to one of the following: (a) Hardware-only circuit implementation (such as implementation of analog and / or digital circuits only) (b) combination of circuitry and software (and / or firmware), (i) combination of processor(s), or (ii) part of processor(s) / software (including digital signal processor(s)), software, and memory(s) that work together to enable a device such as a mobile phone to perform various functions), and (c) Microprocessors or parts of microprocessors, or any circuitry that requires software or firmware to operate (including cases where the software or firmware is not physically present).

[0163] This definition of “circuit” applies to all use of the term in this document, including in the claims. As a further example, the term “circuit” in this embodiment also includes not only a processor (or more processors) or a portion of a processor and the associated software and / or firmware implementation. The term “circuit” also includes, for example, a baseband integrated circuit or an application processor integrated circuit for a mobile phone.

[0164] Any processor mentioned in this text, not limited to processors 101 and 201 in Figures 1 and 2, could be any suitable type of processor. Any processor may consist of, but is not limited to, one or more microprocessors, one or more processors with accompanying digital signal processors, one or more processors without accompanying digital signal processors, one or more special-purpose computer chips, one or more field-programmable gate arrays (FPGAS), one or more controllers, one or more application-specific integrated circuits (ASICS), or one or more computers. The associated structures / hardware are programmed to perform the functions described.

[0165] Furthermore, any operation or step described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored in a computer-readable storage medium (e.g., disk, memory, etc.) to be executed by such a processor. The reference to "computer-readable storage medium" should be understood to include specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0166] Furthermore, any operation described or illustrated herein may be implemented using executable instructions in a general-purpose or special-purpose processor and stored in a computer-readable storage medium (e.g., disk, memory, etc.) to be executed by such a processor. The reference to "computer-readable storage medium" should be understood to include specialized circuits such as FPGAs, ASICs, signal processing devices, and other devices.

[0167] The expressions "A, or B, or C, or any combination thereof" or "at least one of A, B, and C" are not exhaustive and can be understood to include at least the following: (i) A, or (ii) B, or (iii) C, or (iv) A and B, or (v) A and C, or (vi) B and C, or (vii) A, B, and C, (i) A, (ii) B, or (iii) A and B. Furthermore, the expression "A and / or B" can be considered equivalent to the expression "at least one of A and B."

[0168] The embodiments disclosed herein are illustrative only, and it will be understood that any feature presented in a particular exemplary embodiment may be used in any aspect of this disclosure, either by itself or in combination with any feature presented in the same or other particular exemplary embodiment, and / or in combination with any other feature not mentioned. It will also be understood that any feature presented in an exemplary embodiment in a particular category may be used in a corresponding aspect of an exemplary embodiment in another category.

Claims

1. A user device, A means for obtaining a slice group mapping (SGM) setting, wherein the SGM setting indicates a plurality of mappings, each mapping including a mapping between a slice group and a tracking area (TA), Means for performing at least one of cell reselection or random access operation based at least in part on the acquired slice group mapping settings, Equipped with, The aforementioned user equipment further includes: A means for checking whether the SGM setting is valid for the second TA when the user device moves from the first TA to the second TA, or Means for checking whether the SGM setting is valid for the second RA when the user device moves from the first registration area (RA) to the second RA, Equipped with, User equipment.

2. The user device acquires the SGM settings. Obtaining the SGM settings from the core network, or Obtaining the SGM settings from the wireless access network, The user device according to claim 1, comprising at least one of the following.

3. Obtaining the SGM settings from the core network includes obtaining the SGM settings in non-access layer (NAS) signaling and / or messages. Obtaining the SGM setting from the wireless access network includes obtaining the SGM setting in radio resource control (RRC) signaling and / or messages. The user device according to claim 2.

4. The aforementioned user equipment further includes: Means for indicating an invalid SGM to the network in uplink signaling and / or messages, wherein the uplink signaling and / or messages include messages 3, MSG3, MSG5, or MSG1 of a random access channel, RACH, or RRC signaling. A user device according to any one of claims 1 to 3, comprising:

5. The slice group mapping settings described above are: A set of slice groups to map to a set of TAs. One or more mappings between slice groups and TA, One or more mappings between physical cell identifiers (PCIs) and slice groups, A user device according to any one of claims 1 to 4, comprising at least one of the following.

6. The user device according to any one of claims 1 to 5, wherein the slice group mapping further comprises at least one inter-slice mapping.

7. The user device acquires a slice group mapping (SGM) setting, wherein the SGM setting indicates multiple mappings, and each mapping includes a mapping between a slice group and a tracking area (TA). Based at least partially on the acquired slice group mapping settings, perform at least one of cell reselection or random access operations. Includes, When the user device moves from the first TA to the second TA, check whether the SGM setting is valid for the second TA, or When the user device moves from the first registration area (RA) to the second RA, check whether the SGM setting is valid for the second RA. Further including, method.

Images