Device and method for obtaining slice support information

Abstract

The present invention provides an access node device 100, which is used to: receive slice support information 101; and / or receive slice context information 102, and determine slice support information 101 based on the slice context information 102, wherein the slice support information 101 includes a mapping 103 of a slice 104 to an area 105, in particular a mapping to a tracking area (TA) or a slice support area; and process slice related information 106 based on the slice support information 101.

Description

Technical Field

[0001] The present invention relates to the field of wireless mobile communications, and in particular to network slicing. The present invention particularly relates to a device and method for obtaining slicing support information for an access node, and a corresponding device and method for an access and mobility management function (AMF) and / or an operations-and-management system (OMS), and a system thereof. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) introduced the concept of network slicing in 5G to meet the various needs of multiple industries using a shared network architecture. Through network slicing, network services can be customized according to the needs of different usage scenarios, thereby improving network operation efficiency.

[0003] Due to different deployments and dynamic situations in the 5G radio access network (RAN) (for example, load, resources and physical capabilities of the radio access nodes), some slices may be available only in part of the network. When a mobile user equipment (UE) moves, the UE may enter an area where sessions for slices associated with the area are not supported or available. This may result in the loss of active sessions of the UE and reduce the experience of the UE. Therefore, in order to ensure the service continuity of the UE, the slice availability information in the neighboring cells of the UE is particularly important.

[0004] 3GPP TS 38.423, "NR-RAN; Xn application protocol (XnAP) (Release 15)" defines that when an Xn interface is present, slice support information can be exchanged and / or updated through Xn setup and configuration messages.

[0005] 3GPP TS 38.413v0.2NG-RAN; NGAP June.2017 specifies that the network can obtain (updated) slice information from the RAN node via NG setup request or gNB configuration update, e.g. Fig.12 shown.

[0006] However, in the prior art, there is no solution on how to obtain slice support information of neighboring cells or areas without an Xn interface. Summary of the invention

[0007] In view of the above problems and disadvantages, the present invention aims to improve the traditional access node and core network (CN).

[0008] To this end, the present invention provides a device and method for a RAN node to directly or indirectly obtain slice support information of a neighboring cell or area through data processing, so as to achieve reliable and efficient UE mobility and service continuity. The present invention also provides corresponding devices and methods for AMF and / or OMS, and a system including these two devices.

[0009] The objects of the invention are achieved by what is presented in the attached independent claim. Advantageous implementations of the invention are further defined in the dependent claims.

[0010] A first aspect of the present invention provides a device for an access node, used to: receive slice support information; and / or receive slice context information, and determine slice support information based on the slice context information, wherein the slice support information includes a mapping of a slice to an area, in particular a mapping to a tracking area (TA) or a slice support area; and process slice related information based on the slice support information.

[0011] This ensures that enough information is available to determine which slice is available in which area.

[0012] Slice support information refers to the network slice of a certain area. It includes information that can directly identify the slice, such as the logo.

[0013] Slice context information includes information that can be used to infer the identity of at least one network slice.

[0014] Slice-related information may be any information related to a slice, and in particular any information related to received and interpreted slice support information and slice context information.

[0015] The mapping may be an explicit mapping, for example, an explicit relationship represented by a lookup table. Additionally or alternatively, the mapping may be an implicit mapping based on a priori rules, for example, such that only one of the slice or the region is explicitly mentioned in the slice support information, but where it is predefined and what the information is is known to the device, but not explicitly mentioned.

[0016] In a first implementation manner of the device according to the first aspect, the device can also be used to request the slice support information and / or the slice context information, especially to request the slice support information and / or the slice context information from a network entity and / or UE.

[0017] This ensures that when slice support information is needed, it can be obtained, for example, from a central node / function or from a UE acting as a relay to a target access node, such as a base station.

[0018] In a second implementation of the device according to the first aspect, the network entity (800) includes a CN entity, a network management entity and / or an access network entity, in particular an AMF, an OMS, operations-administration-maintenance (OAM) function and / or an access node.

[0019] In a third implementation of the apparatus according to the first aspect, the slice support information and / or the slice context information may be received from a network entity, in particular via an N2 message.

[0020] In particular, this ensures that slice support information can be obtained from a new N2 aka NG2 message or signal, or through the fields of an existing N2 aka NG2 message or signal, or by adding a new information unit field to an existing N2 aka NG2 message or signal.

[0021] In a fourth implementation manner of the device according to the first aspect, the slice context information may include at least one of the following: a slice support area, in particular a slice support area identifier; a UE tracking area identity (TAI) list; an access node identifier; or a cell identifier.

[0022] This approach is beneficial because slice support information may be obtained from a correlation of several information, in particular information comprising one or more of the above-mentioned information.

[0023] In a fifth implementation manner of the device according to the first aspect, the device can also be used to: receive information about the TA; and request the slice support information based on the received information about the TA.

[0024] This scheme is beneficial because further information can be obtained when the measurement report received from the UE includes at least one TA for which slice support information is unknown.

[0025] In a sixth implementation manner of the apparatus according to the first aspect, the request for the slice support information and / or the slice context information may include an address and a TA identifier of an access node.

[0026] This scheme considers a "transparent mode", in which the request is sent directly to the target base station through the CN entity and / or UE relay without establishing an Xn interface. In this case, the response from the target access node can also be sent in the same way. An example process of this implementation method may be: for example, using a self-organizing network (SON) to configure a transmission information unit to obtain slice support information and / or slice context information in a configuration transmission process (3GPP TS38.413). In this example process, the address of the access node may include an identifier of the source access node and an identifier of the target access node.

[0027] In a seventh implementation of the device according to the first aspect, the device can also be used to store the slice context information in a database.

[0028] This ensures that slice support information can be determined when there is sufficient slice context information.

[0029] In an eighth implementation manner of the device according to the first aspect, the device can also be used to obtain and / or update the slice context information based on the slice support information directly received by the device.

[0030] This ensures that new slice context information can be derived based on the received slice support information, and the slice context information can be used to determine further or more accurate or more recent slice support information.

[0031] In a ninth implementation manner of the device according to the first aspect, the device can also be used to obtain and / or update the slice context information by requesting information about at least one of TAI, TAI list, access node identifier, S-NSSAI list or cell identifier from an external information source.

[0032] A second aspect of the present invention provides a method for obtaining slice support information, comprising the following steps: receiving slice support information; and / or receiving slice context information, and determining slice support information based on the slice context information, wherein the slice support information includes a mapping of a slice to a region, in particular a mapping to a TA or a slice support region; and processing slice related information based on the slice support information.

[0033] In a first implementation of the method according to the second aspect, the method may also include: requesting the slice support information and / or the slice context information, in particular requesting the slice support information and / or the slice context information from a network entity and / or UE.

[0034] In a second implementation of the method according to the second aspect, the network entity may be an AMF and / or an OMS.

[0035] In a third implementation of the method according to the second aspect, the slice support information and / or the slice context information may be received from a network entity, in particular, via an N2 message.

[0036] In a fourth implementation of the method according to the second aspect, the slice context information may include at least one of the following: a slice support area, in particular a slice support area identifier; a TAI list of the UE; an access node identifier; or a cell identifier.

[0037] In a fifth implementation of the method according to the second aspect, the method may further include: receiving information about the TA; and requesting the slice support information based on the received information about the TA.

[0038] In a sixth implementation of the method according to the second aspect, the request for the slice support information and / or the slice context information may include an address and a TA identifier of an access node.

[0039] In a seventh implementation of the method according to the second aspect, the method may further include: storing the slice context information in a database.

[0040] In an eighth implementation manner of the method according to the second aspect, the method may further include: obtaining and / or updating the slice context information based on the slice support information directly received by the device.

[0041] In a ninth implementation of the method according to the second aspect, the method may also include: obtaining and / or updating the slice context information by requesting information about at least one of TAI, TAI list, access node identifier, S-NSSAI list or cell identifier from an external information source.

[0042] The method in the second aspect and its implementation manner achieves the same advantages as the device in the first aspect and its corresponding implementation manner.

[0043] A third aspect of the present invention provides a device for AMF and / or OMS, used to: transmit slice support information; and / or transmit slice context information, wherein the slice support information includes a mapping of slices to regions, in particular, a mapping to a TA or a slice support area.

[0044] This ensures that enough information is provided to the access node to determine which slice is available in which area.

[0045] In a first implementation manner of the device according to the third aspect, the device may also be used to: receive a request for the slice support information, and transmit the slice support information according to the received request for the slice support information; and / or receive a request for the slice context information, and transmit the slice context information according to the received request for the slice context information.

[0046] This ensures that slice support information can be provided to the access node when required.

[0047] In a second implementation manner of the device according to the third aspect, the device may also be used to: transmit the slice support information via an N2 message; and / or transmit the slice context information via an N2 message.

[0048] In particular, this ensures that slice support information can be obtained from a new N2 aka NG2 message or signal, or through the fields of an existing N2 aka NG2 message or signal, or by adding a new information unit field to an existing N2 aka NG2 message or signal.

[0049] In a third implementation manner of the device according to the third aspect, the slice context information may include at least one of the following: a slice support area, in particular a slice support area identifier; a TAI list of the UE; an access node identifier; or a cell identifier.

[0050] This scheme is beneficial because in an access node receiving the above information, slice support information can be obtained from different types of information, especially from the correlation of one or more of the above information.

[0051] A fourth aspect of the present invention provides a method for operating an apparatus for AMF and / or OMS, the method comprising the following steps: transmitting slice support information; and / or transmitting slice context information, wherein the slice support information includes a mapping of slices to regions, in particular, a mapping to a TA or a slice support area.

[0052] In a first implementation manner of the method according to the fourth aspect, the method may further include: receiving a request for the slice support information, and transmitting the slice support information according to the received request for the slice support information; and / or, receiving a request for slice context information, and transmitting the slice context information according to the received request for the slice context information.

[0053] In a second implementation of the method according to the fourth aspect, the method may further include: transmitting the slice support information through an N2 message; and / or transmitting the slice context information through an N2 message.

[0054] In a third implementation of the method according to the fourth aspect, the slice context information may include at least one of the following: a slice support area, in particular a slice support area identifier; a TAI list of the UE; an access node identifier; or a cell identifier.

[0055] The method in the fourth aspect and its implementation manner achieves the same advantages as the device in the third aspect and its corresponding implementation manner.

[0056] A fifth aspect of the present invention provides a system for acquiring slice support information, comprising the apparatus as described in the first aspect and the apparatus as described in the third aspect.

[0057] The system of the fifth aspect achieves the same advantages as the apparatus in the first aspect and its corresponding implementation manner and the apparatus in the third aspect and its corresponding implementation manner.

[0058] It must be noted that all devices, elements, units and means described in this application can be implemented in software or hardware elements or any kind of combination thereof. All steps performed by various entities described in this application and functions performed by various entities are intended to represent that the various entities are suitable for or used to perform the various steps and functions. Even if, in the description of the following specific embodiments, the specific functions or steps to be performed by the external entity are not reflected in the description of the specific detailed elements of the specific entity performing the specific steps or functions, it should be clear to the technician that these methods and functions can be implemented in corresponding software or hardware elements or any kind of combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In conjunction with the accompanying drawings, the following description of specific embodiments will illustrate various aspects of the present invention and their implementation forms, wherein:

[0060] Figure 1 A device for accessing a node according to an embodiment of the present invention is shown;

[0061] Figure 2 An exemplary operation of the device is shown;

[0062] Figure 3 Another exemplary operation of the device is shown;

[0063] Figure 4 Another exemplary operation of the device is shown;

[0064] Figure 5 Another exemplary operation of the device is shown;

[0065] Figure 6 Another exemplary operation of the device is shown;

[0066] Figure 7 A schematic diagram showing a method according to an embodiment of the present invention is shown;

[0067] Figure 8 An apparatus for AMF and / or OMS according to an embodiment of the present invention is shown;

[0068] Fig. 9 A schematic diagram showing a method according to an embodiment of the present invention is shown;

[0069] Fig.10 shows a signaling diagram according to an embodiment of the present invention, in particular a signaling diagram for operation in transparent mode;

[0070] Fig.11 A system according to an embodiment of the present invention is shown;

[0071] Fig.12 The figure shows a method of processing slice information according to the prior art. DETAILED DESCRIPTION

[0072] Figure 1 An apparatus 100 for an access node (also referred to as a node) according to an embodiment of the present invention is shown. The access node may be, in particular, a RAN, a UE relay, or a gNB. According to the present invention, the apparatus 100 provides a method and a process for efficiently acquiring slice support information 101 of a neighboring cell with a tracking area (TA) as a granularity. The TA may be, in particular, regarded as a cell list.

[0073] Two different methods can be used to achieve this purpose. The first method, hereinafter referred to as method 1a, aims to directly obtain the slice support information 101 of the neighboring cells in each TA. To this end, the device 100 is used to: receive slice support information 101; and / or receive slice context information 102, and determine the slice support information 101 based on the slice context information 102. This can be regarded as a method for actively obtaining the slice support information 101, wherein the information source (e.g., AMF or OMS) distributes the slice support information 101 or the slice context information 102 to the access node implementing the device 100.

[0074] In other words, in method 1a, the network entity actively distributes the slice support information 101 and / or the slice context information 102 in the TA to the wireless node (e.g., the serving gNB of the UE) that needs the information. The network entity may be a CN control plane entity (e.g., AMF) or a network management entity (e.g., OMS).

[0075] In the case of AMF, slice support information 101 and / or slice context information 102 of other TAs or nodes may be carried in NG signaling (e.g., N2 also known as NG2 message) from the next generation core (NGC) to the NG RAN node. NG can generally be regarded as an interface between gNB and NGC.

[0076] NG signaling can be a response message of any request from RAN to NGC. The NG signaling can also be signaling from NGC to RAN, for example, a handover request from AMF to the target RAN node to indicate the slice support information 101 of the source RAN node in the case of NG-based handover. In another example, the NGC sends the slice support information 101 of the TA to the selected RAN node or all RAN nodes in the same TAI list. At this time, the TA is a TA that is not in the supported TA list of the current RAN node. The selected RAN node refers to a node different from the current RAN node.

[0077] More specifically, the slice support information 101 and / or the slice context information 102 may be received via an N2 message. The N2 message may be a dedicated N2 message, or utilize an N2 message for other purposes.

[0078] In particular, the slice support information 101 in the above example may include a list of S-NSSAIs specified by 3GPP. NSSAI is network slice selection auxiliary information, where S-NSSAI is a single NSSAI.

[0079] More specifically, the NG RAN node may include a gNB and / or an enhanced long term evolution (eLTE) access node, for example, an access node of 3GPP Release 15 and later. Throughout the document, examples using gNBs may also be implemented by NG RAN nodes instead.

[0080] Furthermore, the slice support information 101 received or obtained by the apparatus 100 comprises a mapping 103 of slices 104 to areas 105, in particular to TAs or slice support areas. A slice support area may in particular be a list of cells, in which the slice support is the same.

[0081] In order to take into account network slicing, the device 100 is also used to process slice related information 106 based on the slice support information 101. The slice related information can in particular be any information related to the slice. In other words, the device 100 is not only used to specifically receive the slice support information 101 and / or the slice context information 102, but also interpret the received information 101 and 102 and process the slice related information 106 accordingly. Processing the slice related information 106 based on the slice support information 101 may include any type of information processing.

[0082] Optionally, the device 100 may be used to request the slice support information 101 and / or the slice context information 102, in particular, to request the slice support information 101 and / or the slice context information 102 from a network entity (which may be an AMF or an OMS) and / or a UE. This manner of requesting the slice support information 101 and / or the slice context information 102 may also be regarded as method 1b. Method 1b may be regarded as a passive manner, in which a RAN node (e.g., a gNB) transmits a query to an information source to request the slice support information 101 and / or the slice context information 102. The query may trigger a number of reports by defining reporting conditions (e.g., timing, S-NSSAI of interest, TA, cell, etc.).

[0083] In other words, the RAN Node may request the UE to report the TA of the neighboring cell. If the slice support information 101 of the reported TA is unknown to the RAN node, the RAN node may also directly request the information from a network entity such as an AMF or an OMS (assuming that the information is known in the network entity). If there is no such information at the network entity, the network entity may indicate that the entity does not have such information, or redirect to other network entities (e.g., other AMFs or OMSs) that have such information. In addition, the request for a TA or some TAs may be, for example, in the form of a RAN configuration update message, such as in TS38.413, which may include a TA with known slice support information (e.g., a TA supported by the RAN node) and a TA with unknown slice support information (e.g., a newly discovered TA). Here, a format similar to the TA information element (IE) supported in TS 38.413 may be used.

[0084] The device 100 is used to receive slice context information 102. Optionally, the slice context information 102 may include at least one of the following: a slice support area, in particular a slice support area identifier; a TAI list of the UE; an access node identifier; or a cell identifier. For example, the slice support area may be a location area (related to GSM), a routing area (related to UMTS) or a tracking area (related to LTE). In order to consider further processing of the slice context information 102, the device 100 may also be used to store the slice context information 102 in a database.

[0085] Optionally, the device 100 can be used to obtain and / or update the slice context information 102 based on the slice support information 101 directly received by the device 100.

[0086] Optionally, the device 100 can be used to obtain and / or update the slice context information 102 by requesting information about at least one of TAI, TAI list, access node identifier, S-NSSAI list or cell identifier from an external information source (e.g., an application and a network data analysis module).

[0087] By processing the slice context information 102, for example, by utilizing at least one correlation between a TAI, a TAI list, a gNB identifier, or an S-NSSAI list, the device 100 may optionally derive slice support information 101, preferably deriving slice support information for each TA. This may be considered as method 2. Method 2 includes: a manner of establishing correlations between slice context information 102, and a process of deriving slice support information 101 based on existing slice context information 102. The slice context information 102 may be obtained in the manner described in methods 1a and 1b.

[0088] Further, based on the existing slice context information 102 (e.g., previously distributed / retrieved), the RAN node may first check whether the required slice support information 101 can already be derived from the existing slice context information 102 according to method 2. If not, the RAN node may send an explicit request for the missing information. The missing information may be the slice support information 101 (method 1a or 1b) itself or the slice context information 102, which helps to derive the slice support information 101.

[0089] Now combine Figure 2 As described above, the slice support information 101 of the predefined TA can be derived by processing the slice context information 102. That is, Figure 2 An exemplary operation of the apparatus 100 for accessing a node according to an embodiment of the present invention is shown.

[0090] Typically, a lot of information may be associated with each other in a wireless communication network, and in particular may be associated via the apparatus 100. For example:

[0091] -The RAN node knows the TAs it can support and the slice support information 101 of the TA.

[0092] -The CN node knows the RAN nodes to which it can connect, the TAs supported by each connected RAN node, and the slice support information 101 for each TA.

[0093] - The RAN node knows its own TA to RAN node mapping, and may also know the TA to RAN node mapping of neighboring cells (eg reported by UE).

[0094] - RAN node knows its own cell to TA mapping.

[0095] - Within the same registration area (TAI list) of a UE, the slice support of the TA (e.g., the NSSAI recognized by a UE) should be the same.

[0096] -In the same TA, the slice support of cells should be the same.

[0097] This data association (for example: Figure 2 As shown) can be used to convert between different slice support information 101 and / or slice context information 102 (for example, for each node, for each TA, for each cell), and derive slice support information 101 of a predefined TA through data processing.

[0098] The process of deriving the slice support information 101 of the predefined TA is given below:

[0099] System process (involving AMF, OMS and other network entities):

[0100] Step 1: Distribute slice related information (such as slice support information 101 and / or slice context information 102) to nodes that need the corresponding information and retrieve it by the nodes (for example, using method 1a or 1b).

[0101] Step 2: Each piece of information is updated individually through its own process. For example, when the UE crosses the boundary of the registration area, the TAI list is updated through the Non-Access Stratum (NAS) process. The slice support of the RAN node can be updated through the gNB configuration update process.

[0102] Node process (involving access nodes using the apparatus 100):

[0103] Step 1: Establish associations between the respective information. For example: Figure 2 An example is shown. For example: one TAI corresponds to x S-NSSAIs, for example, a fixed S-NSSAI list; or one RAN node corresponds to a fixed TA list; or TAs in the same TAI list guarantee support for the S-NSSAI accepted by the UE, etc. This step also includes a process for obtaining slice context information 102. For example, the serving gNB obtains the TAI list of the UE as part of the session establishment request from the NGC.

[0104] Step 2: Supplement the information base (e.g., database) using the correlation between the information. For example, the RAN node retains a list of neighboring RAN node identifiers, each neighboring RAN node identifier corresponds to a TAI list, and each TAI corresponds to a list of supported S-NSSAIs. When the S-NSSAI of a RAN node is completely or partially missing, the S-NSSAI of the RAN node identifier with the same TAI can be used to establish the S-NSSAI information or supplement the missing information.

[0105] Step 3: When the system process provides updated information, use data correlation to update the information base.

[0106] Figure 3 Another operation mode of the apparatus 100 for implementing the method 1a is shown. Figure 3 In particular, it shows how a RAN node (which uses the device 100) obtains slice support information 101 and / or slice context information 102 of a TA by distribution from a network entity 301, wherein the network entity may be an AMF or an OMS. Figure 3 An example of actively acquiring the slice support information 101 of the TA is specifically shown. Here, the slice support information 101 and / or slice context information 102 of the TA is sent to the serving RAN node of the UE (using the device 100) through NG signaling. In step 9 of the service request process triggered by the UE, the N2 request carries the slice support information 101 and / or slice context information 102 of all TAs related to the UE (for example, TAs in the UE TAI list, or TAs adjacent to the TAs in the UE TAI list). The current serving RAN node 100 of the UE 302 may not support certain TAs, so for the serving RAN node 100, the relevant slice support information 101 and / or slice context information 102 is unknown.

[0107] In the case where the network entity is an OMS, the slice support information 101 of the TA or node may be carried in a RAN configuration or configuration update message from the OMS.

[0108] Figure 4Another mode of operation of the device 100 is shown. Figure 4 In particular, it is shown in more detail Figure 3 The N2 request transmitted via NG2 signaling (or NG signaling) may include at least one of the following: a TAI list, or slice support information 101 of a TA in the TAI list and / or slice support information of a TA related to the UE and not in the TAI list.

[0109] Figure 5 Another operation mode of the apparatus 100 for implementing the method 1b is shown. Figure 5 In particular, a RAN node is shown that passively obtains slice support information 101 and / or slice context information 102 of the TA through an explicit request. Figure 5 An example is shown in which a RAN node (e.g., a serving gNB including the apparatus 100) requests slice support information 101 and / or slice context information 102 of a TA from a network entity 301 (e.g., an AMF or an OMS). In this example process, when a new possible target gNB 501 for HO is detected or a new neighboring TA is detected, in which the slice information is unknown, the requesting UE 302 also decodes TA-related information (e.g., mobile country code (MCC), mobile network code (MNC), and tracking area code (TAC)). The corresponding UE 302 reports the TA-related information to the serving gNB. In this case, the serving gNB explicitly sends a request for a certain TA or certain TAs to the AMF / OMS, and the AMF / OMS replies with the slice support information 101 and / or slice context information 102 of the requested TA.

[0110] Figure 6 Another mode of operation of the device 100 is shown. Figure 6 In particular, it is shown how to derive the slice support information 101 of the TA or new slice context information 102 from the slice context information 102 in the database of the device 100. Figure 6 A general method for deriving slice support information 101 is shown. The following specific use cases fall within the scope of the general method:

[0111] Use case 1: RAN node 1 knows the slice support information 101 of RAN node 2, and RAN node 3 has the same TAI as RAN node 2. RAN node 1 can derive the slice support information 101 of RAN node 3.

[0112] Use case 2: RAN node 1 knows that RAN node 2 is in the same TA. RAN node 1 can assume that RAN node 2 has the same slice support as RAN node 1 for this TA.

[0113] Use case three: RAN node 1 knows that RAN node 2 is in the same TA of the UE's registration area / TAI list. RAN node 1 can assume that RAN node 2 can also support the slices of this UE.

[0114] Figure 7 A schematic diagram of a method 700 for obtaining slice support information 101 according to an embodiment of the present invention is shown. The method 700 corresponds to Figure 1 The device 100, and correspondingly, is used to operate the device 100.

[0115] The method 700 comprises: step 701: receiving slice support information 101. Additionally or alternatively, the method 700 comprises step 702: receiving slice context information 102 and determining slice support information 101 based on the slice context information 102, wherein the slice support information 101 comprises a mapping 103 of a slice 104 to an area 105, in particular to a TA or slice support area. The method 700 comprises a final step 703: processing slice related information 106 based on the slice support information 101.

[0116] Figure 8 An apparatus 800 for AMF and / or OMS according to an embodiment of the present invention is shown. In order to provide the required information to the apparatus 100, the apparatus 800 is used to transmit slice support information 101 and / or transmit slice context information 102. The transmitted slice support information 101 includes a mapping 103 of a slice 104 to an area 105, in particular a mapping to a TA or a slice support area. The slice support information 101 and / or the slice context information 102 provided by the apparatus 800 in particular include all the features and functions of the slice support information 101 and the slice context information 102 as described above.

[0117] Fig. 9 A schematic diagram of a method 900 for operating an apparatus for AMF and / or OMS according to an embodiment of the present invention is shown. The method 900 corresponds to Figure 8 The device 800 is configured to operate the device 800 accordingly.

[0118] The method 900 comprises step 901 of transmitting slice support information 10. Additionally or alternatively, the method 900 comprises step 902 of transmitting slice context information 102, wherein the slice support information 101 comprises a mapping 103 of slices 104 to areas 105, in particular to TAs or slice support areas.

[0119] Fig.10 Another operation manner of the apparatus 100 for implementing the method 1b in the transparent mode is shown. Fig.10 In particular, a RAN node is shown that passively obtains slice support information 101 and / or slice context information 102 of the TA through an explicit request. Fig.10 An example is shown, in which the RAN node (e.g., a serving gNB including the apparatus 100) requests slice support information 101 and / or slice context information 102 of a TA from a new possible target gNB 501, wherein the request is transmitted via a network entity 301 (e.g., an AMF or an OMS). In this process, when a new neighboring TA is detected, for which the slice support information is unknown, the requesting UE 302 also decodes TA related information (e.g., MCC, MNC, and TAC). The corresponding UE 302 reports the TA related information to the serving gNB. In this case, the AMF / OMS transmits the request to the target gNB according to the target gNB identifier. The target gNB identifier replies with the requested slice support information 101 and / or slice context information 102 of the TA, and the reply is transmitted to the serving gNB via the AMF / OMS. An example process of this implementation method may be: for example, using the SON configuration transmission information unit to obtain slice support information and / or slice context information in the configuration transmission process (3GPP TS38.413).

[0120] Fig.11 A system 1000 according to an embodiment of the present invention is shown. In particular, the system 1000 is a wireless communication system for acquiring slice support information according to 3GPP, and includes the apparatus 100 and the apparatus 800.

[0121] According to the present invention, even without the Xn interface, the gNB can obtain the slice support information 101 of the neighboring cell at the TA granularity. This can help the serving gNB make the optimal HO decision, thereby reducing the HO failure rate and improving the UE experience. In addition, the present invention proposes a method for sensing the availability of neighboring cell slices by combining all available relevant slice context information 102 (for each TA or each node based on the slice support information 101). This ensures minimal signaling overhead and latency, thereby further improving user experience and network efficiency.

[0122] The invention has been described in conjunction with different embodiments and implementations as examples. However, other variants can be understood and obtained by a person skilled in the art by practicing the claimed invention, studying the drawings, the present disclosure and the independent claims. In the claims and the description, the term includes but does not exclude other elements or steps, and "one" does not exclude the possibility of a plurality. A single element or other unit may fulfil the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not mean that a combination of these measures cannot be used in an advantageous implementation.

Claims

1. A method for accessing a node, characterized in that: The method comprises: Receiving slice support information (101) from a network entity; and / or receiving slice context information (102) from the network entity, and determining slice support information (101) based on the slice context information (102), wherein The network entity (800) includes a core network CN entity access and mobility management function AMF and / or a network management entity operation management system OMS, and the slice support information (101) includes a mapping (103) of a slice (104) to an area (105); and Slice related information (106) is processed based on the slice support information (101), and the mapping (103) of the slice (104) to the area (105) includes mapping the slice to a tracking area TA or a slice support area.

2. The method according to claim 1, characterized in that Also includes: The slice support information (101) and / or the slice context information (102) is requested from at least one of the following entities: the network entity (301, 800), the user equipment UE (302), another access node connected through the network entity.

3. The method according to claim 1, characterized in that The slice support information (101) and / or the slice context information (102) are received from the network entity (800) via an N2 message (201).

4. The method according to claim 1, characterized in that: The slice context information (102) includes at least one of the following: Slices support region identification; UE's TA identity TAI list; access node identification; and Cell ID.

5. The method according to any one of claims 2 to 4, characterized in that Also used for: Receiving TA information about a slice support area; and The slice support information is requested based on the received information about the TA (101).

6. The method according to claim 1, characterized in that The request for the slice support information (101) and / or the slice context information (102) includes the address of the access node and the TA identifier.

7. The method according to claim 1, characterized in that It is also used to store the slice context information (102) in a database.

8. The method according to claim 1, characterized in that Also used for: The slice context information (102) is obtained and / or updated based on the slice support information (101) directly received by the network entity (800).

9. The method according to claim 1, characterized in that: Also used for: The slice context information (102) is obtained and / or updated by requesting information about at least one of TAI, TAI list, access node identifier, single network slice selection auxiliary information S-NSSAI list and cell identifier from an external information source.

10. A method for an access and mobility management function AMF and / or an operations management system OMS, characterized in that: Used for: Transmitting slice support information (101) to a device for accessing a node; and / or Transmitting slice context information (102) to a device for accessing a node, wherein The slice support information (101) comprises a mapping of slices (104) to tracking areas TA or slice support regions.

11. The method according to claim 10, characterized in that Also used for: receiving a request for the slice support information (101), and transmitting the slice support information (101) according to the received request for the slice support information (101); and / or A request for the slice context information (102) is received, and the slice context information (102) is transmitted according to the received request for the slice context information (102).

12. The method according to claim 10 or 11, characterized in that: Also used for: Transmitting the slice support information (101) via an N2 message; and / or The slice context information (102) is transmitted via an N2 message.

13. The method according to claim 10, characterized in that The slice context information (102) includes at least one of the following: Slices support region identification; UE's TA identity TAI list; access node identification; and Cell ID.

14. A device (100) arranged at an access node, characterized in that: The device comprises a processor configured to execute computer instructions so as to enable the device to perform the method according to any one of claims 1 to 9.

15. A device (800) arranged in an access and mobility management function AMF and / or an operations management system OMS, characterized in that: The device comprises a processor configured to execute computer instructions so as to cause the device to perform the method according to any one of claims 10 to 13.

16. A system (1000) for obtaining slice support information, characterized in that: include: The device (100) according to claim 14, and the device (800) according to claim 15.

Images