NETWORK FUNCTION NODE AND COMMUNICATION METHOD FOR NETWORK FUNCTION NODE - Patent application

Abstract

To provide a network function node for management and control of a network slice.SOLUTION: An application function / server (AF / AS13) owned by a service provider or 3GPP(R) can consent to a 3GPP mobile network for notification and retrieval of network slice allocation status and / or assign initial network slice allocation on the basis of service level agreement (SLA), replenishes or reduces allocated network slice allocations as needed, and redistributes allocated network slice allocations between network slices or mobile networks.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to communication systems. This disclosure has particular, but not exclusive, relevance to wireless communication systems and devices thereof operating in accordance with 3rd Generation Partnership Project (3GPP) standards or equivalents or derivatives thereof. This disclosure has particular, but not exclusive, relevance to network slice allocation management in so-called "5G" (or "next generation") systems.

[0002] <abbreviation> 3GPP:3rd Generation Partnership Project 5G: 5th Generation 5GC: 5G Core Network 5GS: 5G System 5G-AN: 5G Access Network AF: Application Function AMF:Access and Mobility Management Function AS: Application Server BSS: Business Support System DL:Downlink gNB: Next generation Node B GPSI:Generic Public Subscription Identifier GST: Generic Slice Template GUTI:Global Unique Temporary Identifier IMSI:International Mobile Subscriber Identifier LCM: Life Cycle Management MANO:Management and Orchestration MNO:Mobile Network Operator MSISDN:Mobile Station International Subscriber Directory Number NAS:Non-Access Stratum NEF:Network Expose Function NF:Network Function NG-RAN:Next Generation Radio Access Network NR:New Radio NSQ:Network Slice Quota function NSSF:Network Slice Selection Function NWDAF:Network Data Analytics Function OAM:Operations and Maintenance OSS:Operations Support System PCC:Policy and Charging Control PCF:Policy Control Function PDU:Protocol Data Unit PEI:Permanent Equipment Identifier PLMN:Public land mobile network RA:Registration Area (R)AN:(Radio) Access Network RRC:Radio Resource Control SLA:Service Level Agreement S-TMSI:Serving Temporary Mobile Subscriber Identity SUPI:Subscription Permanent Identifier TA:Tracking Area UDM: Unified Data Management UDR: Unified Data Repository UL:Uplink UE: User Equipment

[0003] <Definition> For the purposes of this document, the terms and definitions set forth in 3GPP Technical Report (TR) 21.905 (Non-Patent Document 1) and below apply. Terms defined in this document take precedence over the definition of the same term in 3GPP TR 21.905 (Non-Patent Document 1), if present. [Background technology]

[0004] Network slicing capabilities defined in 3GPP Release 15 and Release 16 enable a wide variety of communication services for both operators and verticals. To increase the commercial viability of network slicing, the GSMA 5GJA introduced in document NG.116 the concept of Generic Slice Templates (NPL 4) from which descriptions of several network slice types can be derived. Some parameters of GST explicitly indicate the definition of parameters and boundaries of the services offered to end customers. However, these boundaries and the application of some of these parameters are not yet supported in 5GS.

[0005] The SA2 study on enhancements to network slicing phase 2 (NPL 5) aims to identify gaps that need to be filled to support the implementation of GST parameters and appropriate solutions to address these gaps. The 3GPP SA2 working group agreed on a new "key issue" regarding support for network slice allocation event notifications in network slicing. See Key issue 4 in TR23.700-40ver0.3.0 (NPL 5). This key issue investigates whether and how to support event notifications for network slice related allocations. Since this key issue covers network slice related allocations as defined in all key issues described in this technical report, there is no independent solution to this key issue for each key issue addressed in this technical report.

[0006] In particular, this key issue addresses: Whether and how the AF can request event notifications from the 5GS and be notified by the 5GS about the allocation of network slice related attributes, e.g., to enable the AF to influence 5GS routing decisions by notifying the AF whether the allocation of a particular attribute has reached a specified threshold. NOTE: As part of the investigation of this important issue, interaction with OAM, if any, will be determined. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V15.0.0 (2018-03) [Non-Patent Document 2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". V16.1.0 (2019-06) - http: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.501 / 23501-g40.zip [Non-Patent Document 3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2" V16.140 (2019-06) -http: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.502 / 23502-g40.zip [Non-Patent Document 4] Generic Network Slice Template https: / / www.gsma.com / newsroom / wp-content / uploads / NG.116-v2.0.pdf [Non-Patent Document 5] SA2 SID on Enhancement of Network Slicing Phase 2. - http: / / www.3gpp.org / ftp / tsg_sa / WG2_Arch / Latest_SA2_Specs / Latest_draft_S2_Specs / 23700-40-030.zip [Non-Patent Document 6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)" V15.1.0 (2018-09) - https: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.032 / 23032-f10.zip [Non-Patent Document 7] IETF RFC 5580: "Carrying Location Objects in RADIUS and Diameter". Summary of the Invention [Problem to be solved by the invention]

[0008] The introduction of Life Cycle Management (LCM) in 3GPP mobile networks allows 3GPP operators to add / remove network resources per network slice. LCM allows network operators to allocate network resources to customers (e.g. third-party service providers) based on the service level agreements (SLAs) they have with those customers.

[0009] However, third-party service providers currently have no ability to monitor the usage of allocated network resources over network slices, e.g., the level of SLA-agreed allocation to deployed network resources (i.e., number of UEs per network slice, number of PDU sessions per network slice, and UL / DL data rates per network slice per UE).

[0010] If your network resources are significantly underutilized, the allocations agreed upon in the SLA may not be utilized, meaning your third-party service provider may be running their business inefficiently (i.e. wasting money).

[0011] Constantly high utilization of network resources may indicate insufficient allocations agreed in SLAs, which may indicate that third-party service operators are failing to deliver quality of service, i.e., poor user experience.

[0012] Clearly, third-party service providers need to be able to closely monitor the quality of service, utilization levels of allocated network resources, and allocations per network slice, so that the service provider can address any issues in time to maintain delivery of optimal levels of service quality and ensure that allocations comply with SLAs. [Means for solving the problem]

[0013] In a first aspect, there is provided a network function node for management and control of a network slice, comprising: A means for receiving a quota message on a network slice from another network function node or an application function node; means for transmitting information indicating a value of the allocation on the network slice to the other network function node or the application function node; Equipped with.

[0014] In a second aspect, there is provided a network function node for management and control of a network slice, means for receiving a request message for updating an allocation on the network slice from another network function node or an application function node; means for updating the allocation of the network slices based on the request message; means for transmitting a response message to the other network function node or the application function node to confirm the update of the allocation on the network slice; Equipped with.

[0015] In a third aspect, there is provided an application function node for management and control of a network slice, A means for transmitting a message for allocation on the network slice to a network function node for management and control of the network slice; means for receiving information from the network function node for management and control of the network slice, the information indicating the value of the allocation on the network slice; Equipped with.

[0016] In a fourth aspect, there is provided an application function node for management and control of a network slice, A means for transmitting a request message to a network function node for managing and controlling the network slice to update an allocation on the network slice; means for receiving, when updating the allocation on the network slice based on the request message, a response message for confirming the update of the allocation on the network slice from the network function node for management and control of the network slice; An application function node comprising:

[0017] In a fifth aspect, there is provided a network exposer function node, comprising: A means for receiving a message for subscribing to or updating an allocation on a network slice from a network function node or an application function node; means for authenticating whether the network function node or the application function node is authorized to subscribe to or update the allocation of the network slice; means for selecting a network function node for managing and controlling the network slice when the authenticating means determines that the authentication is successful; means for forwarding the messages for management and control of the network slice to the network function node; Equipped with.

[0018] In a sixth aspect, a method for management and control of a network slice is provided, comprising: receiving a message for allocation on the network slice from another network function node or an application function node; sending information to the other network function node or the application function node indicating a value of the allocation on the network slice; Equipped with.

[0019] In a seventh aspect, a method for management and control of a network slice is provided, comprising: receiving a request message from another network function node or an application function node to update an allocation on the network slice; updating the allocation of the network slices based on the request message; and sending a response message to the other network function node or the application function node to confirm the update of the allocation on the network slice; Equipped with.

[0020] In an eighth aspect, a method for management and control of a network slice is provided, comprising: Sending a message for allocation on the network slice to a network function node for management and control of the network slice; receiving information from the network function node for management and control of the network slice indicating a value of the allocation on the network slice; Equipped with.

[0021] In a ninth aspect, a method for management and control of a network slice is provided, comprising: Sending a request message to a network function node for management and control of the network slice to update an allocation on the network slice; receiving a response message from the network function node for management and control of network slices to confirm the update of the allocation on the network slice when updating the allocation on the network slice based on the request message; Equipped with.

[0022] In a tenth aspect, a method for a network exposer function is provided. Receiving a message from a network function node or an application function node to agree to or update an allocation on the network slice; Authenticating whether the network function node or the application function node is authorized to consent to or update the allocation of the network slice; selecting a network function node for managing and controlling the network slice if the authenticating means determines that the authentication is successful; forwarding the message for management and control of the network slice to the network function node; Equipped with. Effect of the Invention

[0023] According to the present disclosure, a method and apparatus for estimating the realization of a first objective can be provided. [Brief description of the drawings]

[0024] Embodiments of the present invention will be better understood and readily apparent to those skilled in the art from the following written description, by way of example only, and in conjunction with the drawings in which:

[0025] [Figure 1] FIG. 1 illustrates an example architecture for dynamic network slice allocation control.

[0026] [Diagram 2] Figure 2 provides a high-level overview of the notification and acquisition of network slice allocations (aspects 1 and 2) and updating of network slice allocations (aspect 3).

[0027] [Diagram 3] FIG. 3 illustrates an example procedure of AF / AS agreement for network slice allocation notification.

[0028] [Figure 4]Figure 4 shows an example of a network slice allocation notification procedure.

[0029] [Diagram 5] FIG. 5 shows that the AF / AS 13 can request the current allocation of a network slice from the NSQMC 11.

[0030] [Figure 6] FIG. 6 illustrates an exemplary procedure for provisioning or replenishing / reducing network slice allocation.

[0031] [Figure 7] FIG. 7 illustrates diagrammatically a mobile (cellular or wireless) communication system 1 to which the above aspects are applicable.

[0032] [Figure 8] FIG. 8 is a block diagram illustrating the main components of the UE (mobile device 3) shown in FIG.

[0033] [Figure 9] FIG. 9 is a block diagram illustrating the main components of an exemplary (R)AN node 5 (base station) shown in FIG.

[0034] [Figure 10] FIG. 10 is a block diagram illustrating the main components of the generic core network node (or functions) shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] <Common points> Dynamic Network Slice Allocation Control Architecture Using LCM (Life Cycle Management)

[0036] FIG. 1 illustrates an example architecture for dynamic network slice allocation control.

[0037] The architecture provides dynamic lifecycle management based on the utilization of network resources in each mobile network operator's network, based on Service Level Agreements (SLAs). Dynamic network slice control is based on the following architectural principles: -If services over network slicing are provided by the MNO, the AF / AS13 may reside in the 3GPP MNO domain. In this case, the NEF12 is not required and the NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF entities interface directly with the AF / AS13. -AF / AS13 may interface with multiple 3GPP MNOs if the services on the network slice span multiple 3GPP MNO domains. -When services on a network slice span multiple 3GPP MNO domains, the AF / AS13 provides coordinated allocation across multiple MNOs to ensure end-to-end services on the slice regardless of where the UE3 roams. -AF / AS13 allocates network slice allocations based on the SLAs managed by AF / AS13. -AF / AS13 allocates network slice allocations to the MNO network based on network resources reserved by the MNO domain. When a network slice needs to replenish its network slice allocation, the required network resources are guaranteed / provisioned in advance by the MNO domain's OSS / BSS, which may coordinate with the MANO system to trigger the materialization of additional network resources. If a network slice needs to reduce its network slice allocation, the OSS / BSS may obtain some network resources through the MANO system, and these network resources will be used by the MNO for other purposes.

[0038] Figure 2 provides a high-level overview of the notification and acquisition of network slice allocations (aspects 1 and 2) and updating of network slice allocations (aspect 3).

[0039] This exemplary procedure includes the following steps: 1) Network Slice Utilization Reporting Per Event - A network function or entity (NF) reports the utilization of its network slice allocation to the Network Slice Allocation Management and Control Node (referred to in this document as NSQMC11). The NSQMC11 can be an NSQ, AMF, NSSF, UDM, PCF, OAM, or NWDAF. The NSQMC11 may be co-located with the NSQ, AMF, NSSF, UDM, PCF, OAM, or NWDAF. The NF can be an AMF, an SMF, a PCF, a base station 5 or a UE 3. The network slice allocation is the number of UEs 3 per network slice allocation, or the number of PDU sessions per network slice allocation, or the UL / DL data rate per network slice allocation per UE 3. Per-event network slice usage reporting can be performed similarly to the case for AMF during registration and deregistration procedures and for interaction with SMF during PDU session establishment / release procedures. In this way, the NSQMC 11 keeps up-to-date information about available network slice allocations. The NSQMC 11 may exist as only one entity in the PLMN representing the PLMN, or as multiple entities in the PLMN. If there are multiple NSQMCs 11 in the PLMN, only one NSQMC 11 interacts with the NEF 12 and AF / AS 13 representing the PLMN. In this case, the NSQMC 11 representing the PLMN needs to interact with the other NSQMCs 11 to maintain the latest allocation information valid for the PLMN.

[0040] 2) Network slice utilization / allocation notification to AF / AS13 - AF / AS13 monitors the latest status of network slice allocation of the mobile network. See Aspect 1 and Aspect 2.

[0041] 3) Network slice allocation / resource reconfiguration (e.g. top-up / cut down / re-balancing) - Based on the network slice utilization / allocation notification to the AF / AS13, the AF / AS13 may determine if the network slice allocation is consistently under-utilized (i.e., the allocation is not optimally utilized and a reduction or redistribution / reallocation is required) or if the network slice allocation is over-utilized (i.e., under-allocation means poor quality of service and resource reconfiguration is required (e.g., top-up / cut down / re-balancing)), see aspect 3.

[0042] <Aspect 1 - Network slice allocation event notification> <Aspect 1, Example 1: AF / AS subscription for network slice allocation notification> A service provider (AF / AS 13) may be an application function or server external to 3GPP (i.e., not owned by a 3GPP network operator) or internal to 3GPP (i.e., owned by a 3GPP network operator) that needs to monitor the network slice quota status within a 3GPP mobile network. For this purpose, the AF / AS 13 agrees with the NSQMC 11. An example of the AF / AS agreement procedure for network slice quota notification is shown in Figure 3.

[0043] 1) Nnef_EventExposure_Subscribe_Request - The AF / AS 13 triggers subscription to the network slice allocation notification event by sending a Nnef_EventExposure_Subscribe_Request(network_slice_id, UE_ext_Id, location_id, quota_event_id, quota_notification_type, quota_notification_threshold, quota_notification_periodicity) message to the NEF 12. The AF / AS 13 includes the following parameters in the Nnef_EventExposure_Subscribe_Request message: - 'network_slice_id': One or more network slices (S-NSSAI) for which the AF / AS13 requires consent for network slice allocation notifications. - "UE_ext_id": One or more UE external IDs (GPSI, MSISDN, etc.) for which consent for network slice allocation status notifications is required. - "location": Geographical location for which network slice allocation notification is required. Location can form an ellipsoid point with uncertainty circle, an ellipsoid point with uncertainty ellipsoid, a high precision ellipsoid point with uncertainty ellipsoid, a Polygon, an ellipsoid point with altitude, a high precision ellipsoid point with altitude and uncertainty ellipsoid, a high precision ellipsoid point with altitude and uncertainty ellipsoid, an ellipsoid as defined in 3GPP TS 23.032. Location can be an operator name, a civic location, a geospatial location as defined in IETF RFC 5580. This information may not be required if the "location_id" information is set in this message. - 'location_id': geographic location (TA, RA, or cell) where network slice allocation notification is required (this information may not be required if 'location' information is set in this message). - "quota_event_id": One or a list of allocation event IDs to monitor, e.g. maximum number of UE3s per network slice allocation and / or maximum number of PDU sessions per network slice allocation and / or maximum UL or DL ​​data rate per network slice per UE allocation. - "quota_notification_type": Type of network slice quota notification, e.g. a one-time notice, or Threshold-based notifications, e.g., network slice quota notifications are triggered when a certain level (number or percentage) of quota is reached or remains. Or periodic notifications, e.g., network slice allocation notifications, are triggered upon expiry of a defined periodic timer. - "quota_notification_threshold": optional parameter. If "quota_notification_type" is threshold-based, AF / AS13 also includes "quota_notification_threshold" itself. "quota_notification_threshold" can be a value (e.g. quota is a numeric value, which when reached triggers a network slice quota notification) or the network slice quota is a percentage value of the remaining or already used network slice quota. - "quota_notification_periodicity": Optional parameter. If "quota_notification_type" is periodic, the AF / AS 13 also includes the "quota_notification_periodicity" parameter. The "quota_notification_periodicity" parameter can be a time value that defines the time between the resulting periodic network slice allocation notifications to the AF / AS 13.

[0044] If the AF / AS 13 has prior knowledge of the NSQMC node name or address, the AF / AS 13 includes the NSQMC node name or address in the Nnef_EventExposure_Subscribe_Request message.

[0045] 2) AF / AS Authorization - The NEF 12 checks if the AF / AS 13 is authorized for network slice allocation notification acceptance. If the AF / AS authorization is successful, proceed to step 4. The address of the NSQMC 11 may be resolved by the NEF 12 at this point.

[0046] 3) If AF / AS authorization fails, the NEF returns a Nnef_EventExpose_Subscribe_Reject(reject_cause = authentication_fail) message, in which the NEF includes the reject cause reject_cause = authentication_fail, and the procedure ends here.

[0047] 4) Nnsq_EventExposure_Subscribe_Request - The NEF 12 queries the UDM to convert the UE external ID "UE_ext_id" (GPSI, MSISDN, etc.) to a 3GPP internal "UE_Id" (SUPI, PEI, IMSI, S-TMSI, GUTI, etc.). The NEF 12 then forwards the request for subscription from the AF / AS 13 to the NSQMC 11 - Nnsq_EventExposure_Subscribe_Request(network_slice_id, UE_Id, location_id, quota_event_id, quota_notification_type, quota_notification_threshold, quota_notification periodicity). If the NEF 12 receives a location from the AF / AS 13 in the Nnsq_EventExposure_Subscribe_Request message, the NEF 12 converts the location to a location ID.

[0048] If multiple NSQMCs 11 exist in the PLMN, the NEF 12 selects one or more NSQMCs 11 and sends one or more Nnsq_EventExposure_Subscribe_Request messages to the NSQMCs 11. For example, if the Nnef_EventExposure_Subscribe_Request message contains a specific "location_id", the NEF 12 sends the Nnsq_EventExposure_Subscribe_Request message only to the NSQMCs 11 that are related to such location.

[0049] 5) QuotaEventExposure Subscription - The NSQMC 11 subscribes to the AF / AS 13 for network slice allocation status notification events according to the requested event notification parameters.

[0050] 6) Nnsq_EventExposure_Subscribe_Response - The NSQMC11 confirms the AF / AS consent to the network slice allocation notification to the NEF12.

[0051] 7) Nnef_EventExposure_Subscribe_Response - NEF 12 queries UDM to convert 3GPP internal "UE_Id" (SUPI, PEI, IMSI, S-TMSI, GUTI, etc.) to "UE_ext_id" (GPSI, MSISDN, etc.) and NEF 12 forwards the network slice allocation notification agreement confirmation to AF / AS 13. NEF 12 includes the name or address of the NSQMC in this message.

[0052] <Aspect 1, Example 2: Network slice allocation notification> When an allocation notification threshold is reached or an allocation notification periodicity timer expires, the NSQMC 11 triggers an allocation event notification, as shown diagrammatically in FIG.

[0053] 1) Allocation threshold is reached or allocation notification periodicity timer expires - When the network slice allocation notification threshold is reached or the network slice allocation notification periodicity timer expires, the NSQMC11 triggers a network slice allocation event notification procedure.

[0054] 2) Nnsq_QuotaEvent_Notification - The NSQMC 11 sends an Nnsq_QuotaEvent_Notification (network_slice_id; UE_Id, location_id, quota_event_id, quota_value) to the NEF 12 with the following parameters: - 'network_slice_id': One or more network slices (S-NSSAI) for which the network slice allocation notification is applicable. - "UE_id": One or more UE IDs (SUPI, PEI, IMSI, GUTI, S-TMSI, etc.) to which the network slice allocation notification relates. - 'location_id': The geographic location (TA, RA, or list of cells) to which the network slice allocation notification applies. - "quota_event_id": One or a list of allocation event IDs, e.g. maximum number of UE3s per network slice allocation and / or maximum number of PDU sessions per network slice allocation and / or maximum UL or DL ​​data rate per network slice per UE allocation. - "quota_value": "quota_value" represents the latest status of the network slice allocation. It may be a numeric value (e.g. current number of UE3s per network slice, current number of PDU sessions per network slice, current value of UL / DL data per network slice per UE3) or "quota_value" may represent the usage level of the network slice allocation in percentage or the remaining / available level of the network slice allocation per type of one or more "quota_event_id".

[0055] 3) NEF 12 queries UDM to map 3GPP internal "UE_Id" (SUPI, PEI, IMSI, S-TMSI, GUTI, etc.) to "UE_ext_Id" (GPSI, MSISDN, etc.). NEF 12 then forwards the received network slice allocation notification to AF / AS 13. If NEF 12 receives location information from AF / AS 13 in Nnef_EvanceExosure_Subbrice_Quest message, NEF 12 converts the location ID to a location and sends it to AF / AS 13.

[0056] <Aspect 2 - Reclaiming network slice allocation> A service provider or 3GPP owned application / server (AF / AS 13) may need to obtain a current network slice allocation from the 3GPP system. The AF / AS 13 may request the current allocation of a network slice from the NSQMC 11, as shown diagrammatically in FIG. 5.

[0057] 1) Nnef_NetworkSliceQuota_Status_Request(network_slice_id, UE_ext_id, location_id, quota_event_id) - The AF / AS 13 sends a request to the NEF 12 to obtain a network slice allocation and includes some or all of the following parameters: - 'network_slice_id': One or more network slices (S-NSSAI) for which the latest network slice allocation status is obtained. - "UE_ext_id": One or more UE external IDs (GPSI, MSISDN, etc.) for which to get the latest network slice allocation status. - "location": Geographical location where network slice allocation notification is required. Location can form an ellipsoid point with uncertainty circle, an ellipsoid point with uncertainty ellipsoid, a high precision ellipsoid point with uncertainty ellipsoid, a Polygon, an ellipsoid point with altitude, a high precision ellipsoid point with altitude and uncertainty ellipsoid, a high precision ellipsoid point with altitude and uncertainty ellipsoid, an ellipsoid as defined in 3GPP TS 23.032. Location can be an operator name, a civic location, a geospatial location as defined in IETF RFC 5580. This information may not be required if the "location_id" information is set in this message. - "location_id": The geographic location (TA, RA, or list of cells) for which to obtain the maximum data network slice allocation status. This information may not be required if the "location" information is set in this message. - "quota_event_id": One or a list of network slice allocation IDs for which to get the latest network slice allocation status (e.g. maximum number of UE3s per network slice allocation and / or maximum number of PDU sessions per network slice allocation and / or maximum UL or DL ​​data rate per network slice per UE allocation).

[0058] If the AF / AS 13 has prior knowledge of the NSQMC node name or address, the AF / AS 13 includes the NSQMC node name or address in the Nnef_EventExposure_Subscribe_Request message.

[0059] 2) AF / AS authorization - The NEF 12 checks if the AF / AS 13 is authorized to obtain the allocation status. The NEF 12 can also map the "UE_ext_id" (GPSI, MSISDN, etc.) to a 3GPP internal "UE_Id" (SUPI, PEI, IMSI, GUTI, S-TMSI, etc.) via a query with the UDM.

[0060] If AF / AS authorization is successful, proceed to step 4.

[0061] 3) If AF / AS authorization fails, the NEF 12 returns a Nnef_NetworkSliceQuota_Status_Reject(reject_cause=authentication_fail) message, which includes a reject cause reject_cause=authentication_fail to the NEF 12, and the procedure ends here.

[0062] 4) Nnsq_NetworkSliceQuota_Status_Request(network_slice_id, UE_id, location_id, quota_event_id) - NEF 12 forwards the request from AF / AS 13 for getting the network slice allocation status to NSQMC 11 or the entity that keeps the latest status of the network slice allocation (NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF etc.). If NEF 12 receives the location from AF / AS 13 in the Nnsq_NetworkSliceQuota_Status_Request message, NEF 12 translates the location to a location id.

[0063] 5) Allocation Status Generation - The NSQMC11 or any entity that holds the latest status of network slice allocation (NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF etc.) generates a "quota_value" (numerical or percentage value of available quota) for the requested "network_slice_id" and "quota_event_id" taking into account "UE_Id" and "location_id" if any. The network slice "quota_value" may be a numeric value (e.g. current number of UEs per network slice, current number of PDUs per network slice, current values ​​of UL / DL data per network slice per UE3) or the "quota_value" may represent the used level of network slice allocation or the remaining / available level of network slice allocation in percentage per one or more types of "quota_event_id".

[0064] 6) Nnsq_NetworkSliceQuota_Status_Response(network_slice_id, UE_id, location_id, quota_event_id, quota_value) - The NSQMC 11 sends network slice allocation status information to the NEF 12 and includes some or all of the following parameters: - 'network_slice_id': One or more network slices (S-NSSAI) for which the latest network slice allocation status is reported. - "UE_id": One or more UE IDs (SUPI, PEI, IMSI, GUTI, S-TMSI, etc.) for which the latest network slice allocation status is reported. -'location ID': The geographic location (TA, RA, or list of cells) for which the maximum data network slice allocation status is reported. - 'quota_event_id': One or a list of allocation event IDs for which the latest network slice allocations are reported (e.g. maximum number of UE3s per network slice allocation and / or maximum number of PDU sessions per network slice allocation and / or maximum UL or DL ​​data rate per network slice per UE allocation). - "quota_value": numeric or percentage value of the reported quota. "quota_value" represents the latest status of the network slice quota. It can be a numeric value (e.g., the current number of UE3s per network slice, the current number of PDUs per network slice, the current value of UL / DL data per network slice per UE3) or "quota_value" can represent the used level of network slice quota or the remaining / available level of network slice quota as a percentage for one or more types of "quota_event_id".

[0065] 7) Nnef_NetworkSliceQuota_Status_Response(network_slice_id, UE_ext_id, location_id, quota_event_id, quota_value) - NEF 12 can map the UE internal 3GPP ID "UE_id" (e.g. SUPI, PEI, IMSI, GUTI or S-TMSI) to the UE external ID "UE_ext_Id" (e.g. GSPI, MSISDN) via a query with UDM. NEF 12 then forwards the network slice allocation response to AF / AS 13. If NEF 12 receives location information from AF / AS 13 in the Nnef_SlectyQota_Vasiod_Quest message, NEF 12 converts the location ID to a position and sends it to AF / AS 13.

[0066] <Aspect 3 - Provision and replenishment / reduction of network slice allocation> A service provider or 3GPP owned application function / server (AF / AS 13) may need to provision, replenish, reduce or replace a network slice allocation in a mobile operator's network. The AF / AS 13 can request an update of the network slice allocation from the NSQMC 11 or an entity that holds the network slice allocation (e.g., NSQ / AMF / NSSF / UDM / PCS / OAM / NWDAF) via the NEF 12 (see Figure 6).

[0067] This procedure may be performed after the appropriate LCM procedures have been completed with the PLMN's OSS / BSS and MANO.

[0068] The procedure illustrated in FIG. 6 can be used by a service operator to:

[0069] 1) The initial provision in the mobile operator network will be the network slice allocation agreed in the SLA, e.g. maximum number of UE3s per network slice allocation, maximum number of PDU sessions per network slice allocation, maximum UL / DL data rates per network slice per UE allocation.

[0070] 2) Replenish or reduce network slice allocations in the mobile operator's network based on renegotiated SLA agreements with the mobile operator in order to optimize resource utilization and / or balance traffic loads, ensure that service quality is maintained and resources are utilized in an optimal manner.

[0071] 3) A service operator may also redistribute network slice allocations between multiple network slices (if a service is offered over multiple network slices) or between multiple mobile networks (if a service spans multiple mobile networks).

[0072] FIG. 6 illustrates an exemplary procedure for provisioning or replenishing / reducing network slice allocation.

[0073] 1) Nnef_NetworkSliceQuota_Update_Request(network_slice_id, UE_ext_id, location_id, quota_event_id, quota_value, add / cut_flag) - The AF / AS 13 sends a request for network slice allocation update to the NEF 12 and includes some or all of the following parameters: - 'network_slice_id': One or more network slices (S-NSSAI) for which the network slice allocation is updated. - "UE_ext_id": One or more UE external IDs (GPSI, MSISDN, etc.) for which the network slice allocation is updated. - "location": Geographical location where network slice allocation notification is required. Location can form an ellipsoid point with uncertainty circle, an ellipsoid point with uncertainty ellipsoid, a high precision ellipsoid point with uncertainty ellipsoid, a Polygon, an ellipsoid point with altitude, a high precision ellipsoid point with altitude and uncertainty ellipsoid, a high precision ellipsoid point with altitude and uncertainty ellipsoid, an ellipsoid as defined in 3GPP TS 23.032. Location can be an operator name, a civic location, a geospatial location as defined in IETF RFC 5580. This information may not be required if the "location_id" information is set in this message. - "location ID": The geographic location (TA, RA, or list of cells) where the network slice allocation is updated. This information may not be required if the "location" information is set in this message. - 'quota_event_id': one or a list of network slice allocation event IDs (e.g., maximum number of UE3s per network slice allocation and / or maximum number of PDU sessions per network slice allocation and / or maximum UL or DL ​​data rate per network slice per network slice allocation). - "quota_value": Numeric or percentage value of the network slice allocation update. "quota_value" represents the network slice allocation to be added, reduced or replaced. It can be a numeric value (e.g., number of UE3s per network slice, number of PDU sessions per network slice, UL / DL data rate values ​​per network slice per UE3). - 'add / cut_flag': This parameter MAY contain multiple values ​​to define whether an update to the network slice quota in the 'quota_value' parameter should: It will be added to (supplement) the network slice allocation already allocated in the 3GPP system. · It will be removed (reduced) from the network slice allocation already allocated in the 3GPP system. Completely replacing network slice allocations already assigned in the 3GPP system (e.g. after renegotiating SLA agreements with mobile network operators).

[0074] If the AF / AS 13 knows the NSQMC node name or address in advance, the AF / AS 13 includes the NSQMC node name or address in the Nnef_NetworkSliceQuota_Update_Req message.

[0075] 2) AF / AS Authorization - The NEF 12 checks if the AF / AS 13 is authorized to update the allocation.

[0076] If AF / AS authorization is successful, proceed to step 4.

[0077] 3) If AF / AS authorization fails, the NEF 12 returns a Nnef_NetworkSliceQuota_Update_Reject(reject_cause=authentication_fail) message, which includes a reject cause reject_cause=authentication_fail to the NEF 12, and the procedure ends here.

[0078] 4) Nnsq_NetworkSliceQuota_Update_Request(network_slice_id, UE_id, location_id, quota_event_id, quota_value, add / cut_flag) - NEF 12 can map the UE external ID "UE_ext_id" (e.g. GSPI, MSISDN) to the 3GPP UE ID "UE_id" (e.g. SUPI, PEI, IMSI, GUTI or S-TMSI) via a query with UDM. NEF 12 then forwards the request for network slice allocation update from AF / AS 13 to the network entity responsible for network slice allocation management or the entity holding the network slice allocation (NSQ / AMF / NSSF / UDM / PCF / OAM, etc.). If NEF 12 receives a location from AF / AS 13 in the Nnsq_NetworkSliceQuota_Update_Request message, NEF 12 translates the location to a location ID.

[0079] 5) Quota Update - NSQMC11 updates the "quota_value" for the requested "network_slice_id" and "quota_event_id" per UE3 and / or location.

[0080] 6) Nnsq_NeworkSliceQuota_Update_Confirm - NSQMC11 confirms the update of the network slice allocation to NEF12.

[0081] 7) Nnef_NetworkSliceQuota_Update_Confirm - NEF 12 can map the UE internal 3GPP ID "UE_id" (SUPI, PEI, IMSI, GUTI, S-TMSI, etc.) to the UE external ID "UE_ext_Id" (GPSI, MSISDN, etc.) via a query with the UDM. The NEF 12 then forwards the confirmation of the network slice allocation update to the AF / AS 13.

[0082] <Summary> Beneficially, the above aspects include one or more of the following features, but are not limited to these. - AF / AS (Application Function / Server) consent with network slice quota holding or management entity (NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF etc.) for slice quota related notifications - New subscription procedure (i.e. service) and parameters like network_slice_id, quota_event_id, quota_notification_type, quota_notification_threshold, quota_notification_periodicity etc. - Network slice allocation notification by the quota holding or management entity (NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF etc.) - New consent procedure (e.g. service) and parameters like network_slice_id, quota_event_id, quota_value etc. - Network slice allocation acquisition by AF / AS13 from an allocation holding or management entity (NSQ / AMF / NSSF / UDM / PCF / OAM / NWDAF etc.) - New allocation acquisition procedure (e.g. service) and parameters like network_slice_id, quota_event_id, quota_value, UE_ext_id, location_id etc. - Network slice quota provision or replenishment by AF / AS13 - new quota update procedure with parameters like 'network_slice_id', 'quota_event_id', 'quota_value', 'UE_ext_id'.

[0083] -New network slice allocation notifications and allocation status updates are now available to AF, allowing AF to: -Re-balance the load of network slices by operating some UE3s across network slices. -Rebalancing (i.e., redistributing) local allocations among roaming partners while roaming. -Replenish or reduce allocations per network slice to optimize load and maintain quality of service (e.g., good user experience). -Add / remove network resources to maintain the expected network slice load and quality of service within the SLA allocation agreement. - Optimize traffic load on network slices by scheduling traffic by time and location. -Re-negotiate new SLA allocations with network operators.

[0084] <Advantages> The above aspects allow service providers to subscribe to notification and acquisition of network slice allocations, so that the service provider can monitor the latest status of network slice allocations in the mobile operator's network. These aspects also provide tools for providing network slice allocations to 3GPP mobile networks, updating network slice allocations, and redistributing network slice allocations between network slices and between mobile networks.

[0085] <System Overview> FIG. 7 illustrates diagrammatically a mobile (cellular or wireless) communication system 1 to which the above aspects are applicable.

[0086] In this network, users of mobile devices 3 (UE) can communicate with each other and other users via respective base stations 5 and core networks 7 using an appropriate 3GPP radio access technology (RAT), e.g., E-UTRA and / or 5G RAT. It will be understood that several base stations 5 form a (radio) access network or (R)AN. As one skilled in the art will appreciate, although one mobile device 3 and one base station 5 (an (R)AN node) are shown in FIG. 7 for illustrative purposes, when implemented the system will typically include other base stations and mobile devices 3 (UE).

[0087] Each base station 5 controls one or more associated cells (directly or via other nodes such as home base stations, relays, remote radio heads, distributed units, etc.). Base stations 5 supporting E-UTRA / 4G protocols may be referred to as "eNBs" and base stations 5 supporting next generation / 5G protocols may be referred to as "gNBs". It will be appreciated that some base stations 5 may be configured to support both 4G and 5G, and / or any other 3GPP or non-3GPP communication protocols.

[0088] The mobile device 3 and its serving base station 5 are connected via an appropriate air interface (such as the so-called "Uu" interface). Neighboring base stations 5 are connected to each other via appropriate base station-to-base station interfaces (such as the so-called "X2" interface, "Xn" interface, etc.). The base stations 5 are also connected to core network nodes via appropriate interfaces (such as the so-called "S1", "N2", "N3" interfaces, etc.).

[0089] The core network 7 typically includes logical nodes (or "functions") for supporting communications in the communication system 1. Typically, for example, the core network 7 of a "next generation" / 5G system includes, among other functions, a control plane function (CPF) and a user plane function (UPF). It will be appreciated that the core network 7 also includes, among other functions, a network slice allocation management and control node (NSQMC) 11 and a network exposer function (NEF) 12. It will be appreciated that the functionality of the NSQMC 11 is provided by one or more of the NSQ, AMF, NSSF, UDM, PCF, OAM, and NWDAF. The core network 7 is also coupled to at least one application function (AF) / application server (AS) 13. Connectivity is also provided from the core network 7 to external IP networks / data networks 20 (such as the Internet).

[0090] The components of this system 1 are configured to carry out one or more of the aspects described above.

[0091] <User Equipment (UE)> FIG. 8 is a block diagram illustrating the main components of the UE (mobile device 3) shown in FIG. 7. As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to and receive signals from connected nodes via one or more antennas 33. Although not necessarily shown in FIG. 8, the UE 3 of course has all the usual functions of a conventional mobile device (such as a user interface 35), which may be provided by any one or any combination of hardware, software, and firmware. A controller 37 controls the operation of the UE 3 according to software stored in a memory 39. The software may be pre-installed in the memory 39 and / or may be downloaded, for example, via the telecommunications network 1 or from a removable data storage device (RMD). The software includes, among other things, an operating system 41 and a communication control module 43. The communication control module 43 is responsible for processing (generating / sending / receiving) signaling messages and uplink / downlink data packets between the UE 3 and other nodes, including the (R)AN node 5, application functions, and core network nodes. Such signaling includes properly formatted requests and responses related to network slice allocation management.

[0092] <(R)AN node> FIG. 9 is a block diagram illustrating the main components of an exemplary (R)AN node 5 (base station) shown in FIG. 7. As shown, the (R)AN node 5 includes a transceiver circuit 51 operable to transmit signals to and receive signals from connected UEs 3 via one or more antennas 53, transmit signals to other antennas 53, and receive signals from other network nodes (either directly or indirectly) via a network interface 55. The network interface 55 typically includes an appropriate base station-base station interface (such as X2 / Xn) and an appropriate base station-core network interface (such as S1 / N2 / N3). The controller 57 controls the operation of the (R)AN node 5 according to software stored in memory 59. The software may be pre-installed in the memory 59 and / or may be downloaded, for example, via the telecommunications network 1 or from a removable data storage device (RMD). The software includes, among other things, an operating system 61 and a communication control module 63. The communications control module 63 is responsible for handling (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, the AF / AS 13, and core network nodes. Such signaling includes properly formatted requests and responses related to network slice allocation management.

[0093] <Core network node> FIG. 10 is a block diagram illustrating the main components of the generic core network node (or functions) shown in FIG. 7, e.g., NSQMC 11 (NSQ, AMF, NSSF, UDM, PCF, OAM, NWDAF, etc.). It will be understood that the same block diagram may be applicable to AF / AS 13. As shown, the core network node includes a transceiver circuit 71 operable to transmit and receive signals to and from other nodes (including UE 3 and (R)AN node 5) via a network interface 75. A controller 77 controls the operation of the core network node according to software stored in memory 79. The software may be pre-installed in memory 79 and / or may be downloaded, for example, via the telecommunications network 1 or from a removable data storage device (RMD). The software includes, among other things, an operating system 81 and at least a communication control module 83. The communication control module 83 is responsible for handling (generating / sending / receiving) signaling between the core network node and other nodes, such as UE 3, (R)AN node 5, and other core network nodes. Such signaling includes properly formatted requests and responses related to network slice allocation management.

[0094] <Modifications and Substitutions> Detailed aspects have been described above. As those skilled in the art will appreciate, many modifications and alternatives can be made to the above embodiments while still benefiting from the invention embodied therein. By way of illustration, only some of these alternatives and modifications are described herein.

[0095] In the above description, for ease of understanding, the UE3, (R)AN5 node, and core network node are described as having several separate modules (such as a communications control module). These modules may be provided in this way for a particular application, e.g., an existing system being modified to implement the above aspects, and for other applications, e.g., a system designed from the beginning with the inventive features in mind, but because these modules are embedded in the overall operating system or code, these modules may not be recognizable as separate entities. These modules may also be implemented in software, hardware, firmware, or a combination of these.

[0096] Each controller may include any suitable form of processing circuitry, including, but not limited to, one or more hardware implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses and / or address buses), direct memory access (DMA) facilities, hardware or software implemented counters, pointers and / or timers, and / or the like.

[0097] In the above embodiment, several software modules have been described. As those skilled in the art will appreciate, the software modules may be provided in compiled or uncompiled form and may be provided to the UE 3, the (R)AN node 5, and the core network node as a signal via a computer network or on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it facilitates the updating of the UE 3, the (R)AN node 5, and the core network node to update their functions.

[0098] The above aspects are also applicable to "non-mobile" or generally fixed user equipment.

[0099] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0100] It will be understood by those skilled in the art that numerous variations and / or modifications may be made to the invention as illustrated in the specific embodiments without departing from the spirit or scope of the invention as broadly described. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive.

[0101] Although the present invention has been described with reference to exemplary embodiments, the present invention is not limited to the above. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0102] For example, all or part of the exemplary embodiments disclosed above can be described as, but are not limited to, the following supplementary notes. (Appendix 1) A network function node for management and control of a network slice, comprising: means for receiving a message for allocation on a network slice from another network function node or an application function node; means for transmitting information indicating a value of the allocation on the network slice to the other network function node or the application function node; A network function node comprising: (Appendix 2) The message may include: A network slice identifier (ID) for the network slice; A User Equipment (UE) ID for the allocation on the network slice; A location ID indicating a geographic location, an assigned event ID indicating an event to be monitored on the network slice; A type indicating at least one condition for notification regarding the allocation on the network slice; a threshold indicating a trigger for said notification; and a periodicity indicating a time value of the time between the resulting periodic notifications regarding the allocation on the network slice; At least one of 2. A network function node as claimed in claim 1. (Appendix 3) The transmitting means is configured to transmit the information indicating the value of the allocation on the network slice, the network slice corresponding to at least one of the network slice iD, the UE ID, the location ID, the allocation event ID, the type of the notification, the threshold, and the periodicity. 3. A network function node as described in Supplementary Note 2. (Appendix 4) The assigned event ID is The maximum number of UEs per network slice to be monitored, The maximum number of Protocol Data Unit (PDU) sessions per monitored network slice, and The maximum uplink (UL) or downlink (DL) data rate per network slice per UE to be monitored; Indicate at least one of 4. A network node according to claim 2 or 3. (Appendix 5) the message includes the type, the means for transmitting is configured to transmit the information if the at least one condition indicated by the type is satisfied. 5. A network function node according to any one of Supplementary Notes 2 to 4. (Appendix 6) the message includes the threshold value; the type indicates that the notification is triggered if the allocation reaches the threshold; the means for transmitting is configured to transmit the information when the allocation reaches the threshold. 6. A network function node as claimed in claim 5. (Appendix 7) the message includes the periodicity; the type indicates that the notification is triggered upon expiration of the periodicity; the means for transmitting is configured to transmit the information upon expiration of the periodicity. 6. A network function node as claimed in claim 5. (Appendix 8) the means for transmitting is configured to transmit the information in response to the message. 8. A network function node according to any one of Supplementary Notes 1 to 7. (Appendix 9) A network function node for management and control of a network slice, comprising: means for receiving a request message for updating an allocation on the network slice from another network function node or an application function node; means for updating the allocation of the network slices based on the request message; means for transmitting a response message to the other network function node or the application function node to confirm the update of the allocation on the network slice; A network function node comprising: (Appendix 10) The request message: A network slice identifier (ID) for the network slice; A User Equipment (UE) ID for the allocation on the network slice; A location ID indicating a geographic location, an assigned event ID indicating an event to be updated on the network slice; A value for updating the allocation on the network slice; and A flag indicating an operation to update the allocation on the network slice; At least one of 10. The network function node according to claim 9. (Appendix 11) The assigned event ID is The maximum number of UEs per network slice to update, The maximum number of Protocol Data Unit (PDU) sessions per network slice to be updated, and The maximum uplink (UL) or downlink (DL) data rate per network slice per UE to be updated; Indicate at least one of 11. The network function node of claim 10. (Appendix 12) the receiving means is configured to receive the message or the request message from the application function node via a network exposer function node; 12. A network function node according to any one of Supplementary Notes 1 to 11. (Appendix 13) The receiving means is configured to receive the message or the request message if a check by the network exposer function node regarding authorization of the application function node to access the network function node to inquire about the allocation on the network slice is successful. 13. The network function node of claim 12. (Appendix 14) The message or the request message includes a node name or address of a specific network function node for management and control of the network slice; the receiving means is configured to receive the message or the request message if the node name or the address of the particular network function node corresponds to the particular network function node; 14. A network function node as claimed in claim 12 or 13. (Appendix 15) the message or the request message includes a location ID; the receiving means is configured to receive the message or the request message if the location ID corresponds to the network function node; 15. A network function node according to any one of Supplementary Notes 1 to 14. (Appendix 16) The allocation on the network slice comprises: a number of UEs per network slice; the number of PDU sessions per network slice; and UL or DL ​​data rate per network slice per UE, At least one of 16. A network function node according to any one of Supplementary Notes 1 to 15. (Appendix 17) An application function node for management and control of a network slice, comprising: A means for transmitting a message for allocation on the network slice to a network function node for management and control of the network slice; means for receiving information from the network function node for management and control of the network slice, the information indicating the value of the allocation on the network slice; An application function node comprising: (Appendix 18) The message may include: A network slice identifier (ID) for the network slice; A User Equipment (UE) ID for the allocation on the network slice; A location ID indicating a geographic location, an assigned event ID indicating an event to be monitored on the network slice; A type indicating at least one condition for notification regarding the allocation on the network slice; a threshold indicating a trigger for said notification; and a periodicity indicating a time value of the time between the resulting periodic notifications regarding the allocation on the network slice; At least one of 18. An application function node as described in Appendix 17. (Appendix 19) The receiving means is configured to receive the information indicating the value of the allocation on the network slice, the network slice corresponding to at least one of the network slice iD, the UE ID, the location ID, the allocation event ID, the type of the notification, the threshold, and the periodicity. 19. An application function node as described in Appendix 18. (Appendix 20) The assigned event ID is The maximum number of UEs per network slice to be monitored, The maximum number of Protocol Data Unit (PDU) sessions per monitored network slice, and The maximum uplink (UL) or downlink (DL) data rate per network slice per UE to be monitored; Indicate at least one of 20. An application function node as described in Appendix 18 or 19. (Appendix 21) the message includes the type, the receiving means is configured to receive the information if the at least one condition indicated by the type is satisfied. 21. An application function node according to any one of Supplementary Notes 18 to 20. (Appendix 22) the message includes the threshold value; the type indicates that the notification is triggered if the allocation reaches the threshold; the means for receiving is configured to receive the information when the allocation reaches the threshold. 22. An application function node as described in Appendix 21. (Appendix 23) the message includes the periodicity; the type indicates that the notification is triggered upon expiration of the periodicity; the means for receiving is configured to receive the information upon expiration of the periodicity. 22. An application function node as described in Appendix 21. (Appendix 24) the means for receiving is configured to receive the information in response to the message. 24. An application function node according to any one of Supplementary Notes 17 to 23. (Appendix 25) An application function node for management and control of a network slice, comprising: A means for transmitting a request message to a network function node for managing and controlling the network slice to update an allocation on the network slice; means for receiving, when updating the allocation on the network slice based on the request message, a response message for confirming the update of the allocation on the network slice from the network function node for management and control of the network slice; An application function node comprising: (Appendix 26) The request message: A network slice identifier (ID) for the network slice; A User Equipment (UE) ID for the allocation on the network slice; A location ID indicating a geographic location, an assigned event ID indicating an event to be updated on the network slice; A value for updating the allocation on the network slice; and A flag indicating an operation to update the allocation on the network slice; At least one of 26. An application function node as described in Appendix 25. (Appendix 27) The assigned event ID is The maximum number of UEs per network slice to update, The maximum number of Protocol Data Unit (PDU) sessions per network slice to be updated, and The maximum uplink (UL) or downlink (DL) data rate per network slice per UE to be updated; Indicate at least one of 27. An application function node as described in Appendix 26. (Appendix 28) The sending means is configured to send the message or the request message to the network function node for management and control of the network slice via a network exposer function node. 28. An application function node according to any one of Supplementary Notes 17 to 27. (Appendix 29) the sending means is configured to send the message or the request message if a check by the network exposer function node regarding authorization of the application function node to access the network function node to inquire about the allocation on the network slice is successful. 29. An application function node as described in Appendix 28. (Appendix 30) The message or the request message includes a node name or address of a specific network function node for management and control of the network slice; the sending means is configured to send the message or the request message if the node name or the address of the particular network function node corresponds to the particular network function node; 30. An application function node as described in Appendix 28 or 29. (Appendix 31) the message or the request message includes a location ID; the means for sending is configured to send the message or the request message if the location ID corresponds to the network function node; 31. An application function node according to any one of Supplementary Notes 17 to 30. (Appendix 32) The allocation on the network slice comprises: a number of UEs per network slice; the number of PDU sessions per network slice; and UL or DL ​​data rate per network slice per UE, At least one of 32. An application function node according to any one of Supplementary Notes 17 to 31. (Appendix 33) A network exposer function node, A means for receiving a message from a network function node or an application function node for agreeing to or updating an allocation on a network slice; means for authenticating whether the network function node or the application function node is authorized to consent to or update the allocation of the network slice; means for selecting a network function node for managing and controlling the network slice when the authenticating means determines that the authentication is successful; means for forwarding the messages for management and control of the network slice to the network function node; A network exposer function node comprising: (Appendix 34) The message includes a node name or address of a specific network function node for management and control of the network slice; The selecting means is configured to select the network function node for management and control of the network slice based on the node name or the address of the particular network function node for management and control of the network slice. 34. A network exposer function node as described in Appendix 33. (Appendix 35) The message includes a location identifier (ID), The selecting means is configured to select the network function node for management and control of the network slice corresponding to the location ID. 35. A network exposer function node as described in Appendix 32 or 34. (Appendix 36) The message may include: A user equipment (UE) ID for the allocation on the network slice; The network exposer function node further comprises: means for mapping the UE ID to an internal UE ID of a network including the network function node for management and control of network slices; The forwarding means is configured to forward the message including the internal UE ID to the network function node for management and control of a network slice. 36. A network exposer function node according to any one of appendix 33 to 35. (Appendix 37) A method for management and control of a network slice, comprising: receiving a message for allocation on the network slice from another network function node or an application function node; sending information to the other network function node or the application function node indicating a value of the allocation on the network slice; A method for providing the above. (Appendix 38) A method for management and control of a network slice, comprising: receiving a request message from another network function node or an application function node to update an allocation on the network slice; updating the allocation of the network slices based on the request message; and sending a response message to the other network function node or the application function node to confirm the update of the allocation on the network slice; A method for providing the above. (Appendix 39) A method for management and control of a network slice, comprising: Sending a message for allocation on the network slice to a network function node for management and control of the network slice; receiving information from the network function node for management and control of the network slice indicating a value of the allocation on the network slice; A method for providing the above. (Appendix 40) A method for management and control of a network slice, comprising: Sending a request message to a network function node for management and control of the network slice to update an allocation on the network slice; receiving a response message from the network function node for management and control of network slices to confirm the update of the allocation on the network slice when updating the allocation on the network slice based on the request message; A method for providing the above. (Appendix 41) A method for a network exposer function node, comprising: Receiving a message from a network function node or an application function node to agree to or update an allocation on the network slice; Authenticating whether the network function node or the application function node is authorized to consent to or update the allocation of the network slice; selecting a network function node for managing and controlling the network slice if the authenticating means determines that the authentication is successful; forwarding the message for management and control of the network slice to the network function node; A method for providing the above.

[0103] This application is based on and claims the benefit of priority to European Provisional Patent Application No. EP20173721.0, filed May 8, 2020, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0104] 1 System 3 Mobile Device (UE) 5 (R)AN Node Base Station 7 Core Network 11. NSQMC 12 NEF 13 AF / AS 20 External IP Networks 31 Transceiver Circuit 33 Antenna 35 User Interface 37 Controller 39 Memory 41 Operating Systems 43 Communication Control Module 51 Transceiver Circuit 53 Antenna 55 Network Interface 57 Controller 59 Memory 61 Operating Systems 63 Communication Control Module 71 Transceiver Circuit 75 Network Interface 77 Controller 79 Memory 81 Operating Systems 83 Communication Control Module

Claims

1. A network slice allocation control function node that controls and manages network slice allocation, A receiving means for receiving a request message from an application function (AF) node via a network exposure function (NEF) node, the request message including a network slice ID and an EVENT ID indicating the number of protocol data unit (PDU) sessions; A sending means for sending a message to the AF node, via the NEF node, the message including information regarding a number of User Equipment (UE) for the allocation of the network slice; Equipped with The network slice allocation control function node is not a Network Data Analytics Function (NWDAF) node. Network slice allocation control function node.

2. A communication method for a network slice allocation control function node that controls and manages network slice allocation, comprising: Receive a request message from an Application Function (AF) node via a Network Exposure Function (NEF) node, the request message including a network slice ID and an EVENT ID indicating the number of Protocol Data Unit (PDU) sessions; Sending a message to the AF node via the NEF node, the message including information regarding a number of User Equipment (UE) for allocation of the network slice; The network slice allocation control function node is not a Network Data Analytics Function (NWDAF) node. A communication method for a network slice allocation control function node.

Images