Sending and receiving a network slice service profile

Abstract

Methods and apparatus are provided. In an example, a method in a first network node of monitoring network slice usage is provided. The method comprises receiving a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions, and receiving usage information identifying usage of the network slice by a consumer of the network slice. The method also comprises determining whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

Description

[0001] SENDING AND RECEIVING A NETWORK SLICE SERVICE PROFILE

[0002] Technical Field

[0003] Example embodiments of this disclosure relate to sending and / or receiving a service profile, such as for example as part of monitoring network slice usage.

[0004] A network slice in a 5th generation (5G) wireless telecommunications network is an independent end-to-end logical network that runs on a shared physical infrastructure, capable of providing a negotiated service quality.

[0005] The network slicing management functions of 5G network, such as the Network Slice Management Function (NSMF), Network Slice Subnet Management Function (NSSMF) and Communication Service Management Function (CSMF), are responsible for the end-to-end creation, management, and orchestration of network slice instances and network slice subnet instances.

[0006] For provisioning of a network slice instance (NSI), the 3rd Generation Partnership Project (3GPP) have specified an allocateNsi operation. The allocateNsi operation is invoked by a service consumer in order to request the provider to allocate a network slice instance that fulfills its network slice related requirements.

[0007] When allocateNsi operation is invoked, the requirements specified in the allocateNsi operation are compared against the actual capabilities of all candidate NSIs by the provider. If an existing NSI can be found, for example with the right coverage and with good enough latency, it is eligible for allocation. In case there is no NSI matching the requirements, a new NSI is created with sufficient capabilities, if there is capacity for the required Network Slice Subnet Instances (NSSIs).

[0008] The input parameters of the allocateNsi request are detailed in table 1 below:

[0009] Table 1, Source TS 28.531 , Release 17, Section 6.5.1 .2

[0010] According to clause 6.3.3 of 3GPP TS 28.541 [2], “ServiceProfile” represents the properties of network slice related requirements that should be supported by the Networkslice instance in 5G network.

[0011] Attributes of “ServiceProfile” that represents network slice related requirements are listed in table below:

[0012]

[0013] Table2, TS 28.541 Release 17, Section 6.3.3, Attributes of “ServiceProfile”

[0014] According to 3GPP TS 28.202 [5], CEF (Charging Enablement Function) collects charging information per NSI Creation, Modification and Termination. This means that when a NSI is created, modified or terminated, then this information is conveyed to CEF. This is depicted in Figure 1 , from 3GPP TS 28.202, clause 4.2.2., which shows an example of a CEF collecting Network Slice Management Charging Information.

[0015] When an allocateNsi operation results in the creation of a NSI, then the provider, acting as an MnS producer (management service producer), informs CEF, as shown in Figure 1 . Based on the CEF configuration, NSI creation / modification / termination information is sent to a Charging Function (CHF) to take necessary action by CHF, such as for example discounted charging for users who are sharing their Network Slice.

[0016] According to 3GPP TS 28.202, clause 5.1.3, the following list of information elements of the “ServiceProfile” are identified to be used by CHF:

[0017] • ServiceProfile identifier.

[0018] • S-NSSAI(s).

[0019] • SST.

[0020] • Latency.

[0021] • Resource Sharing Level.

[0022] • Availability. • Jitter.

[0023] • Reliability.

[0024] • Maximum Number of UEs.

[0025] • Coverage Area.

[0026] • Max Number of PDU sessions,

[0027] • UE mobility Level.

[0028] • Delay Tolerance.

[0029] • UL / DL Throughput Per UE.

[0030] • UL / DL Throughput Per UE.

[0031] • UL / DL Throughput Per Slice.

[0032] • KPI Monitoring.

[0033] • Supported Access Technology.

[0034] • V2X Communication Mode

[0035] Examples of this disclosure may have certain advantages. For example, examples of this disclosure may allow consumers using a network slice to provide traffic profile conditions of their choice for conditional charging of network slices. A network operator or network slice provider may charge for this feature. Network slice consumers may be able to configure / modify / delete traffic profile conditions for network slice conditional charging.

[0036] One aspect of the present disclosure provides a method in a first network node of monitoring network slice usage. The method comprises receiving a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions, and receiving usage information identifying usage of the network slice by a consumer of the network slice. The method also comprises determining whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

[0037] Another aspect of the present disclosure provides a method of sending a service profile.

[0038] The method comprises receiving, at a second network node, a notification of allocation of a network slice and a service profile for the network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions, and sending, by the second network node, the service profile and usage information identifying usage of the network slice by a consumer of the network slice to a first network node. The method also comprises receiving, at the first network node, the service profile for the network slice and the usage information, and determining, by the first network node whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

[0039] An additional aspect of the present disclosure provides apparatus in a first network node for monitoring network slice usage. The apparatus comprises a processor and a memory. The memory contains instructions executable by the processor such that the apparatus is operable to receive a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions, receive usage information identifying usage of the network slice by a consumer of the network slice, and determine whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for a set of one or more conditions corresponding to the one or more conditions of the usage of the network slice.

[0040] A further aspect of the present disclosure provides a system comprising a first network node and a second network node. The system is configured to receive, at the second network node, a notification of allocation of a network slice and a service profile for the network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions; send, by the second network node, the service profile and usage information identifying usage of the network slice by a consumer of the network slice to a first network node; receive, at the first network node, the service profile for the network slice and the usage information; and determine, by the first network node whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

[0041] A still further aspect of the present disclosure provides apparatus in a first network node for monitoring network slice usage. The apparatus is configured to receive a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions, receive usage information identifying usage of the network slice by a consumer of the network slice, and determine whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for a set of one or more conditions corresponding to the one or more conditions of the usage of the network slice.

[0042] Brief Description of the Drawings

[0043] For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:

[0044] Figure 1 shows an example of a Charging Enablement Function (CEF) collecting Network Slice Management Charging Information;

[0045] Figure 2 shows an example of a variety of communication services provided by multiple network slices;

[0046] Figure 3 is a flow chart of an example of a method in a first network node of monitoring network slice usage;

[0047] Figure 4 is a flow chart of an example of a method of sending a service profile;

[0048] Figure 5 shows another example of a system in which examples of the method of Figure 4 may be implemented;

[0049] Figure 6 shows another example of a system in which examples of the method of Figure 4 may be implemented;

[0050] Figure 7 shows another example of a system in which examples of the method of Figure 4 may be implemented;

[0051] Figure 8 shows an example of a system for Network Slice Instance (NSI) allocation;

[0052] Figure 9 shows a schematic diagram of an apparatus for monitoring network slice usage. Detailed Description

[0053] The following sets forth specific details, such as particular embodiments or examples for purposes of explanation and not limitation. It will be appreciated by one skilled in the art that other examples may be employed apart from these specific details. In some instances, detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or more nodes using hardware circuitry (e.g. analog and / or discrete logic gates interconnected to perform a specialized function, Application Specific Integrated Circuits (ASICs), Programmable Logic Arrays (PLAs), etc.) and / or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

[0054] Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g. digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and / or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

[0055] Operators of wireless communication networks, such as for example 4G and / or 5G networks, can offer variety of services to its subscribers. For example, 5G systems are expected to be able to provide optimized support for a variety of different communication services, different traffic loads, and different types of end users. These communication services may be provided by multiple network slices as illustrated in Figure 2, from TS 28.530 section 4.1 .3, which shows an example of a variety of communication services provided by multiple network slices.

[0056] Operators would like to be able to charge for using the underlying network infrastructure (e.g. by network slices) based on conditions for offering different communication services, in order to maximize the monetization of these communication services. An operator can use various analytics to predict and understand subscribers’ traffic patterns and load on the network. However, these analytics do not take inputs directly from a Network Slice Management Services Consumer (NSMS_Consumer). The NSMS_Consumer may have knowledge of its own traffic pattern and usage. Inputs directly from NSMS_Consumer could assist in optimization and monetization of network slices, by encouraging conditional charging of these network slices.

[0057] At present there is no formal or established mechanism for a NSMS Consumer to give input or feedback regarding its traffic pattern to an operator, and accordingly share its preference for conditional charging of network slices. In particular, it is currently not possible for the following:

[0058] • A network slice provider receives input from the network slice consumer, for example during network slice allocation, on expected usage that can influence the rate and cost.

[0059] • Network slice consumers indicating the conditions for charging of network slices to the provider.

[0060] • The provider verifying that the actual usage of a network slice falls within the expected usage (e.g. as indicated by the consumer) and evaluate if these would impact the rate and cost.

[0061] In an example, consider a wireless communications network operator (a NSMS Provider) that offers a “Massive-loT (Internet of Things)” communication service in a given geographical area. A network slice may be used in this example to provide the service. Various users in this area (e.g. companies and / or businesses) may already be using a Massive-loT communication service to realize their business objectives, and may understand patterns of their traffic pattern and load.

[0062] An example NSMS_Consumer may use the Massive-loT service in one or more of the following example ways:

[0063] • NSMS_Consumer may have their business performed mostly in US time zone weekdays (Monday to Friday) from 9 am to 6 pm. This means that the NSMS_Consumer will have the most traffic and the strictest requirement on latency (e.g. lowest latency) during these business hours.

[0064] • NSMS_Consumer’s usage and requirements on latency may vary over the year, for example the requirements may be lower during summer, over holidays, etc.

[0065] • During a few weeks every year, the NSMS_Consumer consolidates and validates inputs from various loT devices as part of an auditing exercise, so during this period the NSMS_Consumer will require extra capacity. Considering the above scenarios, the NSMS_Consumer varying usage and requirements may allow the consumer to negotiate the cost with the provider, and the cost could vary. For example, sometimes it could be charged at a premium rate, whereas at other times it may be charged at discounted price based on conditions provided by the consumers of those network slices.

[0066] In some examples, if a consumer is provided discounted tariffs by a provider depending on conditions provided by them, then they could agree to pay premium price when their requirements are higher (higher capacity, lower latency, more connected devices, and / or higher bandwidth etc.).

[0067] Examples of this disclosure may provide a technical process for monitoring usage of a network slice by a network slice consumer under different conditions. For example, a service profile for a network slice may specify a different traffic usage profile for different conditions, and the network may monitor / determine whether the actual monitored traffic usage fits the profile for the current conditions. Thus, for example, the service profile may indicate one traffic profile (e.g. capacity, number of connected devices, bandwidth etc.) for one set of conditions (e.g. time, days, dates, geographical area etc.), and a different traffic profile for a different set of conditions. This way, for example, the provider may monitor and determine whether the actual usage during conditions that correspond to those of one of the traffic profiles (e.g. at the same time, in the same area etc) does not exceed the specified traffic profile for those conditions.

[0068] One example of how this could be used is that the consumer may be able to negotiate a lower cost tariff if, for example, the traffic profile has reduced usage at certain times, is area restricted, etc. This may also enable the network slice provider to charge the consumer if the actual usage exceeds the traffic profile for the conditions. For example, the consumer may have more connected devices and / or have a higher bandwidth usage than specified in the service profile, and / or the consumer may use devices and bandwidth outside of a specified area. In these cases, the operator may continue to allow the consumer to use the network slice (e.g. outside of the specified area) but may trigger a surcharge.

[0069] Below are provided some examples of one or more features that may be included in embodiments of this disclosure. According to 3GPP TS 28.541 , section 6.3.3.1 , a Service Profile (which represents the properties of network slice related requirement(s) that should be supported by a requested Network Slice instance in 5G network) has no existing parameter which can indicate that conditional charging is requested, and / or consumer provided traffic profile conditions, at the time of Network Slice Instance allocation. Therefore, example embodiments of this disclosure propose to introduce an indicator, referred to in some examples a “Network Slice Conditional Charging Indicator,” which will be provided by a network slice consumer requesting a NSI, and used by a network node (e.g. Network Slice Management Function, NSMF) during network slice allocation, usage monitoring and / or charging. Additionally or alternatively, for example, a set of traffic profiles and conditions, collectively referred to in some examples as “traffic profile condition,” which will indicate sets of conditions and associated traffic profiles (e.g. expected usage of the network slice). For example, which when satisfied, the traffic profiles and conditions may allow a network slice’ to be charged to the consumer differently based on the profiles and conditions provided, and / or may allow the consumer to be surcharged if the traffic profile is exceeded for the corresponding conditions.

[0070] A new network function (NF), named as NSCCMF (Network Slice Conditional Charging Management Function), is proposed in a 5G network in some examples. This newly proposed NF will store information relating to all network slices being conditionally charged (e.g. having the “networkSliceConditionalCharginglndicator” attribute value set, or “Network Slice Conditional Charging Indicator” referred to above), such as for example a service profile that includes traffic profiles and corresponding sets of condition(s).

[0071] The newly proposed NF, NSCCMF, may in some examples provide one or more of the following services, which are illustrative examples:

[0072] • ConditionalChargingNsi (Get): To fetch information on all Network Slices from NSCCMF whose conditions are matched with a traffic profile condition ‘trafficProfileCondition’. NSMS_Provider Subscription may use ConditionalChargingNsi Get API during AllocateNsi operation.

[0073] • ConditionalChargingNsi Create (POST): To insert a new entry into NSCCMF for newly created Network Slices with ‘networkSliceConditionalCharginglndicator’ attribute value set and corresponding traffic profiles and sets of condition(s) stored in ‘trafficProfileCondition’. NSMS_Provider may use ConditionalSharingNsi Create (POST) API during AllocateNsi operation.

[0074] • ConditionalChargingNsi (Delete): To remove entry of Network Slices from NSCCMF with ‘networkSliceConditionalCharginglndicator’ attribute value set and corresponding traffic profiles and conditions stored in ‘trafficProfileCondition’.

[0075] NSMS Provider may use ConditionalChargingNsi Delete API during DeallocateNsi operation.

[0076] • ConditionalChargingNsi Update (Put): To modify existing conditions and / or traffic profiles stored in ‘trafficProfileCondition’ attribute. NSMS_Provider may use ConditionalChargingNsi Update (Put) API during AllocateNsi operation.

[0077] • ConditionalChargingNsi Subscription (Subscribe / Notify): NSMS_Provider would subscribe to events from NSCCMF using this interface.

[0078] A network exposure function (NEF) may expose these new REST based APIs so that consumers can add / modify / delete conditions stored in ‘trafficProfileCondition’ for the Network Slice with ‘networkSliceConditionalCharginglndicator’. This new REST interface can in some examples be hosted by NSCCMF, and NEF will act as Proxy. Any change in conditions and / or traffic profiles may in some examples need to pass feasibility check procedure in NSMS Provider.

[0079] In some examples, the parameters “NetworkSlice Conditional Charging Indicator” and “trafficProfileCondition” may be passed to the Charging function (CHF). The CHF may perform appropriate charging based on the conditions and traffic profiles provided, and may in some examples also perform surcharging based on whether the traffic profile is exceeded.

[0080] The above implementation is merely an example, and in other implementations different functions and processes may be used to achieve similar purposes for one or more of these functions. In addition, in some examples, instead of a new NF an existing NF may be used to implement one or more of these functions.

[0081] Figure 3 is a flow chart of an example of a method 300 in a first network node of monitoring network slice usage. The first network node may be any suitable node in a network (e.g. 4G and / or 5G network or core network), such as a Charging Function (CHF) in some examples. The method 300 comprises, in step 302, receiving a service profile for a network slice. The service profile identifies a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions. That is, for example, each set of condition(s) may indicate the traffic profile (e.g. expected usage of the network slice) that the consumer expects during usage of the network slice under certain condition(s), e.g. times, dates, days, areas and / or one or more other conditions. The expected usage may indicate for example the number of connected devices, data usage, bandwidth, and / or any other traffic or device related information. Step 304 of the method 300 comprises receiving usage information identifying usage of the network slice by a consumer of the network slice. In some examples, the service profile and / or usage information may be received from a second network node, such as for example a Charging Enablement Function (CEF). The usage information may be for example a charging data request from the CEF / second network node.

[0082] Step 306 of the method 300 comprises determining whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice. That is, for example, the first network node may, for the particular conditions of the usage, compare the usage with the traffic profile associated with corresponding conditions. For example, if the usage information corresponds to usage during certain times, then this usage is compared to the traffic information associated with a set of conditions that includes those times, to determine whether the usage satisfies the traffic profile (e.g. the usage indicates lower bandwidth than that specified in the traffic profile, etc.). Thus, in this way, for example, the usage of the network slice by a network slice consumer may be monitored according to different traffic profiles under different sets of one or more conditions.

[0083] In some examples, an action may be performed based on the determination in step 306. In one particular example, the method 300 may comprise performing a charging action based on the determination of whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for the set of one or more conditions corresponding to the one or more conditions of the usage of the network slice. Thus, for example, if the traffic profile is not satisfied but is instead exceeded, then the first network node may perform the charging action. Charging actions may include for example a surcharge action if the traffic profile is not satisfied but is instead exceeded, and / or a discount action for a consumer of the network slice if the usage is well below that indicated in the traffic profile, etc. In other examples, however, other actions other than charging actions may be taken following the determination in step 306. For example, other actions may include some restriction on the service provided to the consumer using the network slice.

[0084] The method 300 may in some examples comprise receiving, with the service profile, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile. For example, the indication may be the “networkSliceConditionalCharginglndicator” or “Network Slice Conditional Charging Indicator” referred to above.

[0085] Figure 4 is a flow chart of an example of a method 400 of sending a service profile. The method comprises, in step 402, receiving, at a second network node (e.g. a CEF), a notification of allocation of a network slice and a service profile for the network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions. For example, as indicated above, each set of condition(s) may indicate the traffic profile (e.g. expected usage of the network slice) that the consumer expects during usage of the network slice under certain condition(s), e.g. times, dates, days, areas and / or one or more other conditions. The expected usage may indicate for example the number of connected devices, data usage, bandwidth, and / or any other traffic or device related information.

[0086] Step 404 of the method 400 comprises sending, by the second network node, the service profile and usage information identifying usage of the network slice by a consumer of the network slice to a first network node. Step 406 of the method 400 comprises receiving, at a first network node (e.g. CHF), the service profile for the network slice and the usage information. Step 408 of the method 400 comprises determining, by the first network node whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice. In some examples, the first network node is the network node referred to above with respect to the method 300 shown in Figure 3, and thus in some examples the first network node may perform the method 300 of Figure 3.

[0087] Figure 5 shows an example of a system 500 in which examples of the method 400 of Figure 4 may be implemented. The system 500 includes a first network node 502, such as for example the first network node referred to above with respect to the method 400 of Figure 4, and may also in some examples be the first network node referred to above that performs the method 300 of Figure 3. The system 500 also includes a second network node 504, such as for example the second network node referred to above with respect to the method 400 of Figure 4.

[0088] In some examples, the method 400 includes sending, by the second network node (e.g. the second network node 504 shown in Figure 5), the service profile to the first network node (e.g. the first network node 502) in a charging data request. Additionally or alternatively, for example, the method 400 may comprise sending, by the second network node to the first network node, with the service profile, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile. The indication may be for example the “networkSliceConditionalCharging Indicator” or “Network Slice Conditional Charging Indicator” referred to above. The method 400 may in some examples comprise receiving, at the second network node, with the notification of allocation of a network slice, the indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.

[0089] The method 400 may in some examples sending, by the second network node to a network usage node (e.g. Management Data Analytics Service, MDAS), a subscription request to subscribe to usage information identifying usage of the network slice by a consumer of the network slice. The subscription request may be based on the service profile. The method 400 may also comprise receiving, from the network usage node, the usage information identifying usage of the network slice by a consumer of the network slice. In some examples, the information identifying the usage of the network slice by the consumer of the network slice is sent by the second network node to the first network node in a charging data request.

[0090] The method 400 may also in some examples comprises receiving, at a third network node (e.g. Network Slice Management Service, NSMS), a request for allocation of a network slice from a network slice consumer, the request identifying a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions. The third network node may determine a network slice instance, NSI, for the request and send a notification identifying the network slice instance to the second network node, the notification identifying the service profile. The notification identifying the network slice instance may in some examples comprise the notification of allocation of the network slice. In some examples, the request contains the service profile, and / or the notification contains the service profile.

[0091] Figure 6 shows another example of a system 600 in which examples of the method of Figure 4 may be implemented. The system 600 includes the first network node 502 and second network node 504 shown in Figure 5, and also includes a third network node 602, such as for example the third network node referred to above. Figure 7 shows another example of a system 700 in which examples of the method of Figure 4 may be implemented. The system 700 includes the first network node 502 and second network node 504 shown in Figure 5, and the third network node 602 shown in Figure 6. In addition, the system 700 includes a network slice consumer 702, such as for example the network slice consumer referred to above.

[0092] The method 400 may also in some examples comprise receiving, at the third network node (e.g. the third network node 602) from the second network node, a subscription request for notifications of allocations of network slice instances, the subscription request based on the service profile, wherein sending the notification to the second network node is performed in response to the subscription request. Additionally or alternatively, in some examples, the method 400 may comprise sending, by the third network node, an allocation response to the network slice consumer (e.g. the network slice consumer 702), the allocation response identifying the network slice instance.

[0093] In some examples, the method 400 comprises sending, by the third network node towards the second network node, usage information identifying usage of the network slice by a consumer of the network slice. This may in some examples comprise sending the usage information to an aggregation node (e.g. Management Data Analytics Service, MDAS) for aggregation of the usage information before the aggregation node sends the aggregated usage information to the second network node.

[0094] The method 400 may in some examples comprise receiving, at the third network node with the request, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile. Additionally or alternatively, in some examples, the method may comprise sending, by the third network node to the second network node, with the notification, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile. The indication may be the “networkSliceConditionalCharging Indicator” or “Network Slice Conditional Charging Indicator” referred to above for example.

[0095] In some examples, the network slice consumer may send to the third network node a request for a network slice instance, the request identifying a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions. The network slice consumer may in some examples also send with the request an indication that a charging action for the consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile. The network slice consumer may in some examples receive an allocation response from the third network node, the allocation response identifying the network slice instance.

[0096] Particular illustrative example embodiments will now be described.

[0097] Figure 8 shows an example of a system 800, such as for example a system for Network Slice Instance (NSI) allocation. The system includes NSMS consumer 802, NSMS provider 804, MDAS 806, CEF 808 and CHF 810. In some examples, the system 800 may be a particular example of the system 700 shown in Figure 7. Thus, for example, the NSMS consumer 802 may correspond to the network slice consumer 702, the NSMS provider 804 may correspond to the third network node 602, the CEF 808 may correspond to the second network node 504, and the CHF 810 may correspond to the first network node 502.

[0098] In this particular example, the system 800 exchanges messages and information as follows.

[0099] 1 . CEF 808 subscribes to NSI allocation events at the NSMS Provider (step 812)

[0100] 2. NSMS Provider 804 confirms the subscription (step 814)

[0101] 3. NSMS Consumer 802 request an allocation of an NSI including “traffic profile condition” and “Networkslice Conditional Charging Indicator” (step 816)

[0102] 4. NSMS Provider 804 checks if the NSI requires a new or if it may reuse an existing network slice (step 818)

[0103] 5. NSMS Provider 804 notifies the CEF 808 that a NSI has been allocated including “traffic profile condition”, “Networkslice Conditional Charging Indicator” and S-NSSAI (step 820)

[0104] 6. CEF 808 confirms the reception of the notification (step 822)

[0105] 7. NSMS Provider (804) confirms the allocation of the NSI including the S-NSSAI to be used for the DE to access the NSI (step 824)

[0106] 8. CEF (808) subscribes to performance measurements from the MDAS 806 based on the S-NSSAI and the “traffic profile condition” (step 826)

[0107] 9. MDAS (Management Data Analytics Service) 806 confirms the subscription of performance measurements (step 828)

[0108] 10. MDAS 806 subscribes to performance measurements from the NSMS Provider 804 or network functions (step 830)

[0109] 11 . MDAS 806 subscription is confirmed (step 832) 12. CEF 808 sends a charging data request to the CHF 810 including “traffic profile condition”, “NetworkSlice Conditional Charging Indicator” and S-NSSAI (step 834)

[0110] 13. CHF 810 stores the traffic profile condition” for the S-NSSAI, and generates a charging record of the event (step 836)

[0111] 14. CHF 810 confirms charging recording using a charging data response (step 838)

[0112] 15. Several performance reports are sent to MDAS 806, and aggregated at MDAS 806 (step 840)

[0113] 16. MDAS 806 notifies the CEF 808 of the NSI usage based on the subscription made by the CEF 808 (step 842)

[0114] 17. CEF 808 sends charging data request to the CHF 810 including the performance measurements for a S-NSSAI (step 844)

[0115] 18. CHF 810 compares the performance measurement with the “traffic profile condition” and decides if there should be a surcharge or discount, the CHF 810 creates a charging record of the event and decision (step 846)

[0116] 19. CHF 810 confirms charging recording using a charging data response (step 848)

[0117] Figure 9 is a schematic of an example of an apparatus 900 in a first network node for monitoring network slice usage. The apparatus 900 comprises processing circuitry 902 (e.g. one or more processors) and a memory 904 in communication with the processing circuitry 902. The memory 904 contains instructions, such as computer program code 910, executable by the processing circuitry 902. The apparatus 900 also comprises an interface 906 in communication with the processing circuitry 902. Although the interface 906, processing circuitry 902 and memory 904 are shown connected in series, these may alternatively be interconnected in any other way, for example via a bus.

[0118] In one embodiment, the memory 904 contains instructions executable by the processing circuitry 902 such that the apparatus 900 is operable / configured to receive a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions; receive usage information identifying usage of the network slice by a consumer of the network slice; and determine whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for a set of one or more conditions corresponding to the one or more conditions of the usage of the network slice. In some examples, the apparatus 900 is operable / configured to carry out the method 300 described above with reference to Figure 3. It should be noted that the above-mentioned examples illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative examples without departing from the scope of the appended statements. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the statements below. Where the terms, “first”, “second” etc. are used they are to be understood merely as labels for the convenient identification of a particular feature. In particular, they are not to be interpreted as describing the first or the second feature of a plurality of such features (i.e., the first or second of such features to occur in time or space) unless explicitly stated otherwise. Steps in the methods disclosed herein may be carried out in any order unless expressly otherwise stated. Any reference signs in the statements shall not be construed so as to limit their scope.

[0119] References

[0120] 1. GSM Association; Official Document NG.116 - Generic Network Slice Template; Version 7.0; 17 June 2022

[0121] 2. 3GPP TS 28.541 Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3; V17.4.0 (2021 -09)

[0122] 3. 3GPP TS 28.530 Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;Management and orchestration; Concepts, use cases and requirements; V17.1.0 (2021 -03)

[0123] 4. 3GPP TS 28.531 Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Provisioning; V17.1.0 (2021 -09)

[0124] 5. 3GPP TS 28.202 Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Charging management; Network slice management charging in the 5G System (5GS); Stage 2; V16.1.0 (2020-12)

[0125] 6. S5-211090; Rel-16 CR 28.531 Correction of NSI and NSSI Operations; 3GPP TSG- SA5 Meeting #135-e; Online, 25th Jan 2021 - 3rd Feb 2021

[0126] 7. 3GPP TSG-SA5 Meeting #134e; S5-206329d2; Revision of S5-206256rev3; Proposal on clarification of ServiceProfile representations; e-meeting

Claims

Claims1 . A method in a first network node of monitoring network slice usage, the method comprising: receiving a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions; receiving usage information identifying usage of the network slice by a consumer of the network slice; and determining whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

2. The method of claim 1 , wherein the service profile and / or the usage information is received from a second network node.

3. The method of claim 2, wherein he second network node is a Charging Enablement Function, CEF.

4. The method of any of claims 1 to 3, wherein the first network node is a Charging Function, CHF.

5. The method of any of claims 1 to 4, comprising performing a charging action based on the determination of whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for the set of one or more conditions corresponding to the one or more conditions of the usage of the network slice.

6. The method of claim 5, wherein the charging action comprises a surcharge action or a discount action for a consumer of the network slice.

7. The method of any of claims 1 to 6, comprising receiving, with the service profile, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.

8. The method of any of claims 1 to 7, wherein the usage information comprises a charging data request.

9. A method of sending a service profile, the method comprising: receiving, at a second network node, a notification of allocation of a network slice and a service profile for the network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions; sending, by the second network node, the service profile and usage information identifying usage of the network slice by a consumer of the network slice to a first network node; receiving, at the first network node, the service profile for the network slice and the usage information; and determining, by the first network node whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

10. The method of claim 9, comprising sending, by the second network node, the service profile to the first network node in a charging data request.11 . The method of claim 9 or 10, comprising sending, by the second network node to the first network node with the service profile, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.

12. The method of any of claims 9 to 1 1 , comprising receiving, at the second network node, with the notification of allocation of a network slice, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.

13. The method of any of claims 9 to 12, comprising sending, by the second network node to a network usage node, a subscription request to subscribe to usage information identifying usage of the network slice by a consumer of the network slice.

14. The method of claim 13, wherein the network usage node comprises a Management Data Analytics Service, MDAS.

15. The method of claim 13 or 14, wherein the subscription request is based on the service profile.

16. The method of any of claims 13 to 16, comprising: receiving, from the network usage node, the usage information identifying usage of the network slice by a consumer of the network slice.

17. The method of claim 16, wherein the information identifying the usage of the network slice by the consumer of the network slice is sent by the second network node to the first network node in a charging data request.

18. The method of any of claims 9 to 17, comprising: receiving, at a third network node, a request for allocation of a network slice from a network slice consumer, the request identifying a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions; determining, by the third network node, a network slice instance, NSI, for the request; and sending, by the third network node, a notification identifying the network slice instance to a second network node, the notification identifying the service profile.

19. The method of claim 18, wherein the notification identifying the network slice instance comprises the notification of allocation of the network slice.

20. The method of claim 18 or 19, comprising receiving, at the third network node from the second network node, a subscription request for notifications of allocations of network slice instances, the subscription request based on the service profile, wherein sending the notification to the second network node is performed in response to the subscription request.21 . The method of any of claims 18 to 20, comprising sending, by the third network node, an allocation response to the network slice consumer, the allocation response identifying the network slice instance.

22. The method of any of claims 18 to 21 , comprising sending, by the third network node towards the second network node, usage information identifying usage of the network slice by a consumer of the network slice.

23. The method of claim 22, wherein sending, by the third network node towards the second network node, the usage information comprises sending the usage information to an aggregation node for aggregation of the usage information before the aggregation node sends the aggregated usage information to the second network node.

24. The method of claim 23, wherein the aggregation node comprises a Management Data Analytics Service, MDAS.

25. The method of any of claims 18 to 24, comprising: receiving, at the third network node with the request, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile; and / or sending, by the third network node to the second network node, with the notification, an indication that a charging action for a consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.

26. The method of any of claims 18 to 25, wherein: the request contains the service profile; and / or the notification contains the service profile.

27. The method of any of claims 18 to 26, wherein the third network node comprises a Network Slice Management Service, NSMS, Provider.

28. The method of any of claims 9 to 27, wherein the second network node comprises a Charging Enablement Function, CEF.

29. The method of any of claims 18 to 28, comprising: sending, by the network slice consumer to the third network node, a request for a network slice instance, the request identifying a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and a plurality of traffic profiles, wherein individual traffic profiles are associated with a respective set of one or more conditions.

30. The method of claim 29, comprising sending, by the network slice consumer with the request, an indication that a charging action for the consumer of the network slice may be based on one or more of the sets of one or more conditions in the service profile.31 . The method of claim 29 or 30, comprising receiving, at the network slice consumer from the third network node, an allocation response, the allocation response identifying the network slice instance.

32. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 1 to 31.

33. A carrier containing a computer program according to claim 32, wherein the carrier comprises one of an electronic signal, optical signal, radio signal or computer readable storage medium.

34. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 32.

35. Apparatus in a first network node for monitoring network slice usage, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor such that the apparatus is operable to: receive a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions; receive usage information identifying usage of the network slice by a consumer of the network slice; and determine whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for a set of one or more conditions corresponding to the one or more conditions of the usage of the network slice.

36. The apparatus of claim 35, wherein the memory contains instructions executable by the processor such that the apparatus is operable to perform the method of any of claims 2 to 8.

37. A system comprising a first network node and a second network node, the system configured to: receive, at the second network node, a notification of allocation of a network slice and a service profile for the network slice, the service profile identifying a plurality of sets ofone or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions; send, by the second network node, the service profile and usage information identifying usage of the network slice by a consumer of the network slice to a first network node; receive, at the first network node, the service profile for the network slice and the usage information; and determine, by the first network node whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile associated with the set of one or more conditions that correspond to the one or more conditions of the usage of the network slice.

38. The apparatus of claim 37, wherein the system is configured to perform the method of any of claims 10 to 17.

39. The apparatus of claim 37 or 38, wherein the system comprises a third network node, and the system is configured to perform the method of any of claims 18 to 28.

40. The apparatus of claim 39, wherein the system comprises a network slice consumer, and the system is configured to perform the method of any of claims 29 to 31 .41 . Apparatus in a first network node for monitoring network slice usage, the apparatus configured to: receive a service profile for a network slice, the service profile identifying a plurality of sets of one or more conditions and, for individual sets of one or more conditions, a traffic profile for traffic in the network slice under the one or more conditions; receive usage information identifying usage of the network slice by a consumer of the network slice; and determine whether the usage of the network slice under one or more conditions of the usage of the network slice satisfies the traffic profile for a set of one or more conditions corresponding to the one or more conditions of the usage of the network slice.

42. The apparatus of claim 41 , wherein the apparatus is configured to perform the method of any of claims 2 to 8.

Images