Management of partial served network slices

Abstract

This invention relates to the management of network slices monitored by a communication device (ME) having a Security Element (USIM), the communication device at least conforming to a technique for implementing network slicing using routing strategies, the method comprising the following steps: for a communication device active in a registered area of ​​a network implementing the network slicing technique, the registered area including a tracking area: - requesting a given slice at the network; - receiving from the network slice status and slice information for the given slice, the slice information including a list of tracking areas supporting the given slice in the current registered area; - in response to a polling request from the security element or in an event-based notification, sending a portion of the served slice status and the list of tracking areas supporting the given slice to the security element.

Description

Technical Field

[0001] The present invention relates to a method for monitoring the management of network slices by a communication device having a security element, which may be partially supported in a subset of tracking regions TA in the same registration region RA.

[0002] The present invention also relates to a communication device and a security element for implementing this method. Background Technology

[0003] 5G network slicing is used in 5G to provide adapted QoS for specific applications. Currently, five Slice Service Types (SSTs) are defined, as disclosed in 3GPP TS 23.501 Clause 5.15.2.2, but it is foreseeable that this number will increase as 5G requirements evolve. Furthermore, within each of the five SSTs, the operator-specific distinguishers significantly increase the number of slice identifiers in the device environment.

[0004] With the introduction of 5G slicing, applications must ensure that the served slices are consistent with their data and / or power consumption, performance, and latency requirements when the slices are available. Therefore, slice management is an ever-growing challenge.

[0005] As defined in the standard, the communication equipment (hereinafter referred to as ME) selects network slices based on User Equipment Routing Policy (URSP) rules provided by the network or by the USIM. These URSP rules are generally under the control of the PLMN. It is advantageous to use a security element (hereinafter referred to as USIM), which is configured by the home PLMN with at least these URSP rules. This security element is installed in the ME.

[0006] The 3GPP TS 31.111 specification enables USIM to request slice-related status based on a polling mechanism. More specifically, this specification has been agreed upon regarding PROVIDE LOCAL INFORMATION, which is the method by which USIM applications retrieve information only when a slice is being serviced.

[0007] The current 3GPP TS 31.111 specification also enables USIM to receive slice-related status based on an event mechanism. Currently, the network notifies the ME of the following slice information: the allowed S-NSSAI value that the ME can use in the serving PLMN or SNPN in the current registered area; the served slice served by the network; and rejected slices, with the reasons for rejection listed below: S-NSSAI is not available in the current PLMN or SNPN, S-NSSAI is not available in the current registered area, S-NSSAI is not available due to failed or revoked network slice-specific authentication and authorization, and S-NSSAI is not available due to reaching the maximum number of UEs.

[0008] In the improvements of version 18, slicing is now partially supported on a subset of the tracking regions (TAs) of the RAs within the same registered region (RA). This is in Figure 1 As illustrated, three slices of MIoT, eMBB, and V2X, represented by three different lines, are supported on a subset of tracking regions of several registration regions distinguished by different patterns.

[0009] Partially supported slices are not part of the information provided to USIM for the current slices. Some USIM processes associated with a specific slice can take a considerable amount of time to complete, such as onboard key generation and SUCI calculation. Knowing as quickly as possible when a slice has been partially or not selected can be advantageous in hiding processing time. QoS can also be improved by USIM or a remote server when slices are only partially supported for a list of tracking areas.

[0010] Currently, the USIM cannot obtain status information related to the partially supported slice management performed by the ME. Therefore, with card power consumption minimized, the USIM cannot initiate slice-related processes when a slice request is accepted or rejected by the network in a partially tracked area.

[0011] Therefore, alternative and advantageous solutions will be needed in this field. Summary of the Invention

[0012] The present invention aims to reliably monitor slice management when slices are partially available on a subset of the tracking regions in a given registered region.

[0013] This invention is defined in its broadest sense as a method for monitoring the management of network slices by a communication device with a security element, the communication device at least conforming to a technology that implements network slicing using routing strategies, the method comprising the following steps: for a communication device active in a registration area of ​​a network implementing the network slicing technology, the registration area including a tracking area:

[0014] - Request a given slice at the network;

[0015] - Receive partial serviced slice status and slice information for a given slice from the network, including a list of tracking regions that support the given slice in the currently registered region;

[0016] - In response to a polling request from the security element or in an event-based notification, send the status of partially supported slices and a list of tracking regions that support a given slice to the security element.

[0017] This invention proposes, as a first original aspect, that the network provides a list of tracking regions registered by the communication device to the communication device. This aspect is unknown in the prior art. The invention further creates new slice states, which are "partially allowed" and "partially denied" states that can be sent to the security element. The tracking region list is forwarded to the security element along with the partially allowed / denied states. This invention is useful regardless of whether the network is currently effectively accepting or denying the slice. In effect, the partial state informs the security element that not the entire registered region provides full service for a given slice.

[0018] According to its advantageous features, the communication device also supports a USIM application toolkit framework for implementing event download packets. The method includes preparatory steps for a security element to register with a slice event defined in the USIM application toolkit framework supported by the communication device, and event download packets are used based on event notifications.

[0019] This feature corresponds to the definition of a specific event download packet suitable for carrying the slice information of the present invention into a secure element.

[0020] According to another advantageous feature, the method of the present invention further includes the following steps: for the security element, recording a list of tracking regions supporting a given slice in a registration area where the communication device is registered; the method further includes the following steps: for the communication device, providing the security element with information about the currently used tracking regions; and the following steps: for the security element, based on the list of tracking regions supporting a given slice and the information about the currently used tracking regions, executing at least one process associated with the given slice when the currently used tracking region is in the list.

[0021] This feature allows the secure element to execute processes in advance, or once a communication device is detected to be in a tracking area where the required slice is served. Typically, some processes can thus be completed in a hidden time before the results of processes required by the network or device. This is generally applicable to situations where time-consuming calculations are performed in advance. In effect, this invention enables the secure element to initiate slice-related processes without waiting for commands to do so. Associated processes include calculating new rules for routing policies, which includes updating stored rules (URSP rules) for routing policies in the secure element's memory. Such processes also include cryptographic calculations involving slice state, slice information, and at least one cryptographic configuration parameter of the secure element.

[0022] Generally speaking, this invention enables the initiation of time-consuming processes even before the results of cryptographic computations are requested. This allows such resource-intensive and time-consuming processes to be performed within a hidden timeframe. Therefore, this invention enables cryptographic computations, such as SUCI computations and onboard key generation, to be performed in advance on the first event confirming slice availability, before the actual use of the slice and associated cryptographic computations are applied.

[0023] According to another advantageous feature, the method includes the following steps: for a security element, constructing a tracking region map in which a given slice is supported or not supported.

[0024] This mapping is useful when communication equipment is in the field and moving, and when it may be necessary to perform calculations beforehand to enter a given slice. This mapping can include slice availability statistics.

[0025] Advantageously, the list of tracking regions supporting a given slice includes the tracking regions for which the communication device has registered.

[0026] This feature allows for better prediction of communication device movement not only in the current registration area but also in adjacent registration areas.

[0027] The present invention also relates to a communication device with a security element configured to monitor the management of network slicing, the communication device at least conforming to the technology of implementing network slicing using routing strategies, the communication device being active in a registration area of ​​a network implementing the network slicing technology, the registration area including a tracking area, the communication device being configured to:

[0028] - Request a given slice at the network to receive the slice status and slice information for the given slice from the network, which includes a list of tracking regions that support the given slice in the currently registered region;

[0029] - In response to a polling request from the security element or in an event-based notification, send the "partially allowed" or "partially denied" slice status and a list of tracking regions that support the given slice to the security element.

[0030] This communication device monitors slice management in situations where slices are geographically partially supported within the same registered area. Therefore, it improves the granularity of slice management.

[0031] The present invention also relates to a security element installed in a communication device configured to monitor the management of network slices using the security element. The communication device at least conforms to the technology of implementing network slicing using routing strategies. The security element is configured to receive partially allowed / rejected slice status and slice information when the communication device is active in a registered area of ​​a network implementing the network slicing technology. The registered area includes a tracking area, and the slice information includes a list of tracking areas that support a given slice in the current registered area.

[0032] Advantageously, the communication device also supports a USIM application toolkit framework for implementing event download packets, and the security element is also configured to register with slice events defined in the USIM application toolkit framework supported by the communication device, using event download packets for event-based notifications.

[0033] This registration enables the security element to automatically receive slice status and slice information (i.e., including a list of tracking areas) according to the present invention.

[0034] Preferably, the security element is further configured to record a list of tracking regions supporting a given slice in the registration area where the communication device is registered, and when the communication device provides the security element with information about the currently used tracking regions, based on the list of tracking regions supporting a given slice and the information about the currently used tracking regions, execute at least one process associated with the given slice when the currently used tracking region is in the list.

[0035] This security element has the potential to trigger a process immediately after communication has entered the tracking area that supports the slice.

[0036] Advantageously, the security element of the present invention is also configured to construct a tracking region map in which a given slice is supported and not supported.

[0037] This tracking region mapping enables the security element to quickly retrieve slice support information.

[0038] Based on specific characteristics, the list of tracking regions supporting a given slice includes the tracking regions for which the communication device has registered.

[0039] In order to achieve the foregoing and related objectives, one or more embodiments include the features fully described below and specifically pointed out in the claims. Attached Figure Description

[0040] The following description and accompanying drawings illustrate certain exemplary aspects of the invention. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings, and the disclosed embodiments are intended to include all such aspects and their equivalents.

[0041] • Figure 1 Examples of some supported slices in several registered regions are shown;

[0042] • Figure 2A and Figure 2B Timing diagrams of the slice management mechanism according to the first and second embodiments of the present invention are shown respectively. Detailed Implementation

[0043] To gain a more complete understanding of the invention, it will now be described in detail with reference to the accompanying drawings. The detailed description will illustrate and describe what is considered to be the preferred embodiments of the invention. Of course, it should be understood that various modifications and changes in form or detail can be readily made without departing from the scope of the invention. Therefore, the invention is not limited to the exact forms and details shown and described herein, nor is it limited to the entirety of the invention less than that disclosed herein and claimed below. In the different drawings, the same elements are denoted by the same reference numerals. For clarity, only those elements and steps useful for understanding the invention have been shown in the drawings and will be described therein.

[0044] Figure 1 The network environment is schematically illustrated, where slicing is partially supported in addition to the defined registration areas RA. Three registration areas, RA1, RA2, and RA3, are defined in this diagram. As defined in the standard, an RA consists of several tracking areas TA. Therefore, RA1 includes six TAs, namely TA1-1 to TA1-6, RA2 includes four TAs, namely TA2-1 to TA2-4, and RA3 includes six TAs, namely TA3-1 to TA3-6. Figure 1 Different patterns are used to distinguish the registration areas.

[0045] exist Figure 1The above represents three slices. These slices are supported by subsets of the tracking regions. Therefore, the first slice, MIoT, is supported in four tracking regions: TA1-2, TA1-3, TA2-3, and TA3-2. The second slice, V2X, is supported in five tracking regions: TA1-1, TA2-1, TA2-2, TA2-4, and TA3-3. The third slice, eMBB, is supported in four tracking regions: TA1-4, TA1-6, TA3-1, and TA3-6.

[0046] In this scenario, the invention applies to communication devices that, when registered in a tracking area within a registration region, have an application requesting network access and have selected slice X for that network access according to URSP rules. In practice, when receiving registration region information about supported slices as in the prior art, the communication device cannot currently detect whether the tracking region in which the communication device is located supports slices.

[0047] According to existing polling mechanisms for slice management, the 3GPP standard only specifies that for USIM applications implemented in polling mode, PROVIDE LOCAL INFORMATION related to slices should be sent periodically to obtain the current slice status. Therefore, the security element may have information about allowed or denied slices in response to polling. Only slices that are fully supported (i.e., supported in all tracking areas of the currently registered area) are sent in response to the current polling event. This severely limits the security element's ability to monitor connectivity behavior. Currently, there is no means to monitor a subset of allowed or denied slices in the currently registered area in polling mode, and therefore no means to build statistics or any artificial intelligence in the USIM, such as to adapt routing policies. Therefore, when a given slice is supported only in a subset of tracking areas defined for the currently registered area, the USIM has no way of knowing when the ME will update the slice status or information based on that information, regardless of what information is received from the network.

[0048] Using event-based notification-based slice management, communication devices may push slice status and slice information to the secure element. In addition to information related to the acceptance of a given slice, this slice information can also be rejection information with a rejection reason. Similar to polling mechanisms, slice information is sent to the secure element only if the slice is supported in all tracking areas of the currently registered region.

[0049] Figure 2A and Figure 2B This is a timing diagram illustrating the method of the present invention according to two embodiments.

[0050] The first embodiment is based on a polling mechanism, and the second embodiment is based on an event-based notification mechanism. All timing diagrams below illustrate the exchange between the network NW, the communication device ME, and the secure element USIM. The secure element USIM is typically a SIM card of any form factor, such as a removable SIM card, an embedded SIM card, or an integrated SIM card. The secure element USIM can also be a trusted execution environment (TEE) or any type of secure element configured to store sensitive data held by a user not equipped by the user's UE on behalf of a third party. Typically, the USIM belongs to the network NW operator, which is usually a PLMN. However, according to the invention, other types of networks can also be applied.

[0051] The device is typically a terminal or mobile equipment (ME) as defined in ETSI or 3GPP standard documents. It should be noted that the processing of the communication device routing policy (URSP) stored in the USIM is not disclosed in detail here, as this processing is known in the prior art. Generally, the routing policy URSP is managed by the operator associated with the device. Therefore, the home network operator and the visited network operator may influence the content of the URSP. On the other hand, the URSP rules in the USIM are currently controlled by the home network operator, but in certain situations, other configurations involving the visited network are conceivable in the future.

[0052] In step S1, the ME requests network access. In step S2, the ME evaluates the URSP rules and selects slice X. Subsequently, in step S3, the ME sends a slice request Req_SX to the network NW. In response, the network NW sends a rejection Rej_SX for the slice X request in step S4. Advantageously, this is associated with one of the previously proposed rejection reasons. According to the invention, the network NW includes a tracking area list L(TA). Even if the network provides slice information including a list of tracking areas supporting a given slice according to the main aspects of the invention, the currently defined polling mechanism will not forward the information to the security element because, according to the polling mode, only slice information supported on all tracking areas in the currently registered area is now provided to the security element.

[0053] It should be further noted here that, in the prior art, even in event-based mode, the communication device ME does not obtain any information related to the list of tracking areas where the requested slice is available, and the security element cannot respond.

[0054] Figure 2A This presents a scenario where the security element USIM uses a polling mechanism to obtain information related to the slice. In step S5, the security element therefore sends a polling Pol_SS regarding the slice status. According to the invention, in Figure 2A In the case illustrated, where the communication device has recently received a slice rejection Rej_SX and a list of tracking regions L(TA) supporting the requested slice, the ME responds to the polling by sending a partial rejection slice status Rej_SX and a list of tracking regions L(TA) supporting slice X in step S6.

[0055] When the USIM secure element receives additional information about the current service tracking area, it checks in step S7 whether the current service tracking area is in the list of tracking areas supporting a given slice, as received in list L(TA). According to the invention, in the event of movement of the communication device, the secure element advantageously receives real-time information about the service tracking area and / or the expected service tracking area. Based on this information about the current or expected service tracking area and the list of tracking areas supporting a given slice, the USIM secure element can therefore trigger a process associated with the given slice in step S8.

[0056] Since rejection may be due to congestion or temporary conditions, this allows the safety element to be calculated in advance, and more generally, to predict the process to be executed using a given slice.

[0057] Of course, these slices can be monitored in parallel based on the list of tracking regions that support the corresponding slices in each of the several slices.

[0058] If, in step S9, the ME subsequently evaluates another URSP rule to select slice Y, for example, a new request established by an application within the ME for a new PDU session using slice Y, this triggers step S10, where the ME executes the request for slice Y, Req_SY. Subsequently, the network NW accepts the request for slice Y, Acc_SY, in step S11. According to the invention, the network NW also appends the list of allowed tracking areas L(TA) to the acceptance.

[0059] exist Figure 2A In an exemplary example, in step S12, shortly after receiving acceptance of slice Y, the USIM sends a polling message Pol_SS for the slice status. The ME then responds to the USIM in step S13 by informing it of the availability of the served slice YAcc_SY. According to the invention, a list L(TA) of tracking areas supporting slice Y is appended to the response. In step S14, the security element initiates processes related to slice Y and can also anticipate the evolution of slice availability based on the movement of communication devices (if present).

[0060] It is important to note here that if slice Y is accepted, and no polling event occurs quickly after acceptance, USIM will only be notified during the next polling event, possibly outside the acceptance period. In this case, the opportunity to monitor the slice is lost.

[0061] Furthermore, the polling mode is known to have the following drawbacks: excessive battery consumption associated with regular commands to be sent from the USIM to the ME, and the potential for missing slice information if slice status is not requested at the correct timing. While polling provides information on a periodic basis, it does not provide immediate access to slice status and / or slice information as soon as they are updated.

[0062] like Figure 2B The event-based mechanism shown above is an improvement that can reduce power consumption. Figure 2B A timing diagram of the event-based notification method of the present invention is shown. In the preliminary step SO, the security element registers with the event-based slicing service. Subsequently, as... Figure 2B As disclosed above, in step S1, an application in the communication device ME requests network access for the ME. In step S2, the ME evaluates the URSP rules and selects slice X. Subsequently, in step S3, the ME sends a slice request Req_SX to the network NW. In response, the network NW sends a rejection Rej_SX for the slice X request in step S4. Advantageously, one of the previously proposed rejection reasons is associated. According to the invention, the network NW includes a tracking area list L (TA) in the rejection.

[0063] According to the method of the present invention, in event-based mode, after step S4, the communication device ME prepares an event download packet EE according to the content defined in the application toolkit. According to the present invention, the event download packet EE includes the slice status as partially rejected slices and a list of tracking regions supporting a given slice X as slice information.

[0064] Here, the slice status is therefore partially rejected, and the slice information is a list of tracking regions that support a given slice.

[0065] Therefore, the slice status pushed to the card as an event packet can be "partially rejected" and include a list of tracking areas. This information is undefined according to current standardized specifications and is therefore even less available between the device ME and the secure element USIM.

[0066] The device ME then sends an event download packet EE(Rej_SX, L(TA)) to the security element USIM in step S20.

[0067] In detail, the slice state for each slice can be:

[0068] - Allowed, advantageously associated with a single network slice selection auxiliary information (S-NSSAI) value that the ME can use in all tracking regions of the currently registered region's service PLMN or SNPN.

[0069] - Partially permitted, associated with slice information including a list of tracking regions where slices are permitted.

[0070] - Being rejected, but having favorable reasons for rejection.

[0071] - Partial rejection is associated with slice information, which includes a list of tracking regions where slices were rejected.

[0072] Slice information is a list of tracking regions that support slices.

[0073] According to TS 31.111, in addition to the set of events defined in Clause 4.7 of ETSI TS 102.223, events according to the present invention can also be reported to the USIM once the USIM is registered to the corresponding event, each event being associated with a category defined in the USIM Application Toolkit.

[0074] This invention can use a previously unused category. This provides the USIM security element with the opportunity to register with such slice events. Figure 2B Step S0 illustrates this pre-registration of the safety element at the device ME, which supports the application toolkit.

[0075] The event list data object contains information about the associated events that are triggered, i.e., the slice status. Advantageously, the device ME uses the following additional data objects to set events: device identity, access technology, slice status, slice information (with or without mapping information), and rejected slice information (with or without mapping information), depending on the execution context.

[0076] The device identity data object is set to source = network NW and destination = secure element USIM. The access technology data object contains the access technology of the current serving cell.

[0077] In step S21, the security element checks whether the current service tracking region exists in the received list L(TA), and may trigger a process associated with the given slice in step S22 to pre-connect the given slice.

[0078] If the device is not camped on any cell, the access technology data object should not exist. In this case, the tracking area list L(TA) is used to predict the next service tracking area and the process to be triggered, thereby simplifying the slice entry requirements.

[0079] like Figure 2B As presented above, after rejecting slice X, in step S9, the ME can then further evaluate another URSP rule to select slice Y, for example, for a new request from an application within the ME to establish a new PDU session using slice Y. The ME then typically makes a request for another slice Y in step S10 and receives acceptance for slice Y in step S11. Similarly, the device ME prepares the event download packet according to what is defined in the application toolkit. The device ME then sends the event packet EE(Acc_SY, L(TA)) to the USIM in step S23. This event packet EE contains the slice status and slice information, i.e., the response received from the network NW related to the network slice request sent from the device ME to the network NW. This time, the status is allowed, and the information is the tracking area list L(TA).

[0080] The USIM then uses the slice status and slice information to enable processes linked to slice events, thereby influencing slice management at the ME. Based on the slice events received from the device ME and the configuration information in the USIM, the USIM can begin executing slice-related processing in step S24.

[0081] exist Figure 2A and Figure 2B In the example, the Security Element (USIM) adapts URSP rules to slice status and slice information, and advantageously adapts them to historical slice status and slice information. These rules are provided to the Device ME for updating the Routing Policy (URSP) to be used for network slice management. This updating of URSP is beneficial for the Device ME to always have the ability to adapt to slices in real time. Based on the recorded status, the USIM typically calculates a new priority order for the URSP rules stored locally and provides the priority-ordered URSP rules to the Device ME.

[0082] As a general result, the USIM process benefits from this invention. Specifically, the invention is advantageously combined with processes associated with specific slices, which take a considerable amount of time to implement.

[0083] Such processes are particularly important for onboard key generation, Subscription Hidden Identifier (SUCI) computation, and any other processes involving cryptographic computation. It is crucial to know as quickly as possible when a slice has been selected to advantageously utilize the hidden processing time.

[0084] If the current service tracking area is in the list, or if the communication device is expected to soon enter one of the listed tracking areas, the receipt of the event packet of the present invention advantageously triggers the USIM to initiate an onboard key generation process. In this case, using the present invention, the secure element can begin generating a key using key generation parameters (e.g., key / algorithm type, key length, desired key quality). Such a key can be used in end-to-end encryption processes, device authentication, such as in IoT security features.

[0085] The packet command contains information related to the accepted slice, at least the slice identifier. For example, the remaining information required for key generation has been configured in the USIM by the key owner, who is either the HPLMN or a third party different from the HPLMN.

[0086] By receiving the slice status and current service tracking area of ​​the present invention in near real-time at the Secure Element USIM, the Secure Element USIM can initiate SUCI calculations for slices that require network-specific slice authentication and authorization, such as in the case of slice SIM use cases.

[0087] Using this invention, USIM can also calculate the mapping of tracking areas in near real-time. Therefore, USIM can improve QoS by predicting entry into the next tracking area. Based on the recorded slice status, USIM advantageously calculates the availability score for each slice in each tracking area.

[0088] Using this invention, USIM can generally perform slice availability statistics and perform corresponding adjustments typically found in URSP rules to improve fast connectivity to an appropriate QoS via a specific slice.

[0089] By leveraging improved geographic granularity of slice availability, this invention enables the behavior of the Security Element USIM to be altered without any delay regarding slice availability. This result will become increasingly useful as the number of devices benefiting from network slicing increases.

[0090] In the detailed description above, reference has been made to the accompanying drawings, which illustrate by way of example specific embodiments in which the invention may be practiced. These embodiments have been described in sufficient detail to enable those skilled in the art to practice the invention. Therefore, the detailed description above should not be construed as limiting, and the scope of the invention is to be properly interpreted only by the appended claims.

Claims

1. A method for monitoring the management of network slices by a communication device (ME) having a Security Element (USIM), said communication device at least conforming to the technology of implementing network slicing using routing strategies, the method comprising the following steps: For the communication device active in the registration area of ​​a network implementing the network slicing technology, the registration area includes a tracking area: - Request a given slice at the network; - Receive from the network the slice status and slice information for the given slice, the slice information including a list of tracking regions that support the given slice in the current registered region; - In response to a polling request from the security element or in an event-based notification, send to the security element the partially supported slice status and the list of tracking regions supporting the given slice.

2. The method according to claim 1, wherein, The communication device also supports a USIM application toolkit framework for implementing event download packets. The method includes a preparatory step for the security element to register with slice events defined in the USIM application toolkit framework, and the event-based notification uses event download packets.

3. The method according to any one of the preceding claims, further comprising the step of: For the security element, a list of tracking regions supporting the given slice is recorded in the registration area where the communication device is registered. The method further includes the following steps: for the communication device, providing the security element with information about currently used tracking regions; and for the security element, based on the list of tracking regions supporting the given slice and the information about currently used tracking regions, when the currently used tracking region is in the list, executing at least one process associated with the given slice.

4. The method according to any one of the preceding claims, the method comprising the following steps: For the security element, a tracking region map is constructed, in which the given slice is either supported or not supported.

5. The method according to any one of the preceding claims, wherein the list of tracking regions supporting the given slice includes tracking regions of the registered regions registered by the communication device.

6. A communication device (ME) having a secure element (USIM) and configured to monitor the management of network slicing, the communication device (ME) at least conforming to a technique for implementing network slicing using routing strategies, the communication device (ME) being active in a registration area of ​​a network implementing the network slicing technique, the registration area including a tracking area, the communication device (ME) being configured to: - Request a given slice at the network to receive slice status and slice information for the given slice from the network, the slice information including a list of tracking regions that support the given slice in the currently registered region; - In response to a polling request from the security element or in an event-based notification, send the security element a "partially allowed" or "partially denied" slice status and a list of tracking regions supporting the given slice.

7. A Secure Element (USIM) installed in a communication device (ME), the communication device (ME) being configured to monitor the management of network slices using the Secure Element (USIM), the communication device at least conforming to a technology for implementing network slicing using routing policies, the Secure Element being configured to receive partially allowed / rejected slice status and slice information when the communication device is active in a registered area of ​​a network implementing the technology for network slicing, the registered area including a tracking area, the slice information including a list of tracking areas supporting the given slice in the currently registered area.

8. The safety element according to claim 7, wherein, The communication device also supports a USIM application toolkit framework for implementing event download packets, and the security element is further configured to register with slice events defined in the USIM application toolkit framework supported by the communication device, wherein the event-based notification uses event download packets.

9. The security element according to any one of claims 7 or 8, further configured to record a list of tracking regions supporting the given slice in the registration area where the communication device is registered, and when the communication device provides the security element with information about currently used tracking regions, based on the list of tracking regions supporting the given slice and the information about currently used tracking regions, execute at least one process associated with the given slice when the currently used tracking region is in the list.

10. The security element according to any one of claims 7 to 9, wherein the security element is further configured to construct a tracking region map in which the given slice is supported and not supported.

Images