Re-mapping a network profile
Apparatuses, methods, and systems are disclosed for network profile re-mapping for an application supporting one or more UEs. One apparatus includes a processor that configures a first mapping of a first application to a first network profile based on at least one application requirement of the first application. The processor receives a trigger event report from the first application for adapting the at least one application requirement for at least one UE of the first application. The processor determines, based on the trigger event report, a second mapping of the first application to a second network profile. The apparatus includes a transceiver that transmits the second mapping of the first application to the at least one UE of the first application.
1 . An apparatus providing an application function, the apparatus comprising:
a memory; and
a processor coupled to the memory, the processor configured to cause the application function to:
configure a first mapping of a first application to a first network slice, based on at least one application requirement, wherein the at least one application requirement comprises a requirement to re-locate to a new data network;
receive a request for network slice adaptation for at least one user equipment (“UE”) associated with the first application, wherein the request comprises an identifier for the first application and further comprises a set of UE identifiers (“IDs”) associated with the first application and a trigger event report;
determine, based on the trigger event report, a second mapping of the first application to a second network slice; and
transmit the second mapping of the first application to the at least one UE associated with the first application or to a network function, or both, wherein the second mapping of the first application indicates a target data network.
2 . The apparatus of claim 1 , wherein the first mapping further indicates a first Data Network Name (“DNN”) corresponding to the first application, and wherein the second mapping further indicates a second DNN corresponding to the first application.
3 . The apparatus of claim 1 , wherein the at least one application requirement comprises:
a Quality of Experience (“QoE”) requirement,
a Quality of Service (“QoS”) requirement,
a UE mobility requirement,
a service profile requirement,
a service operation requirement,
or a combination thereof.
4 . The apparatus of claim 1 , wherein the first mapping and the second mapping are based on at least one application requirement obtained from the first application.
5 . The apparatus of claim 4 , wherein the first application comprises an application server and one or more application clients at one or more UEs.
6 . The apparatus of claim 1 , wherein the processor is configured to cause the application function to receive an initial request for providing a network slice mapping function prior to configuring the first mapping, wherein the initial request comprises at least one of the following parameters:
an application ID,
a transaction ID,
a UE ID,
a service profile ID,
a service requirement,
a public land mobile network (“PLMN”) ID,
a non-public network (“NPN”) ID,
an application to Data Network Name (“DNN”) mapping,
an application registration parameter,
an application context parameter,
an enforcement flag,
an area of validity,
a time of validity,
or a combination thereof.
7 . The apparatus of claim 1 , wherein the processor is configured to cause the application function to receive network slice related parameters for one or more network slices supported by the at least one UE associated with the first application, wherein at least one of the first mapping or the second mapping is determined using the network slice related parameters, the network slice related parameters comprising at least one of:
a network slice subscription for the at least one UE associated with the first application,
a subscribed Single Network Slice Selection Assistance Information (“S-NSSAI”) for the at least one UE associated with the first application,
a network slice radio access technology (“RAT”) preference for the at least one UE associated with the first application,
a network slice frequency preference for the at least one UE associated with the first application,
a network slice priority for the network slice subscription,
a network slice performance parameters for a network slice,
a Generic Slice Template (“GST”) parameter for the network slice,
or a combination thereof.
8 . The apparatus of claim 7 , wherein the network slice related parameters are received from at least one of the network function or a slice management function.
9 . The apparatus of claim 8 , wherein the network slice related parameters received by the network function are received for each UE associated with the first application.
10 . The apparatus of claim 8 , wherein the network slice related parameters are received for each network slice supported by the first application.
11 . The apparatus of claim 1 , wherein the processor is configured to cause the application function to transmit a request to the network function for receiving network slice related parameters prior to the apparatus determining the first mapping of the first application.
12 . The apparatus of claim 1 , wherein the trigger event report comprises one or more of the following parameters:
a new service requirement,
a Quality of Experience (“QoE”) degradation notification,
a UE mobility change notification,
a degradation of Application Quality of Service (“QoS”) attributes,
a change of Application-to-Data Network Name (“DNN”) mapping,
a change of an automation level of the application,
a change of a communication model,
a change of a service profile mapped to the application,
a change of service requirements which are mapped to the application,
a change of a service area coverage for the application,
a change of QoE targets, a change of edge application server service area,
a change of Application-to-Edge Data Network (“EDN”) mapping,
at least one identifier selected from:
a UE ID,
an Application ID,
a Factory-of-the-Future Application Enabler Server (“FFAE-S”) ID,
a Vehicle-to-Everything Application Enabler Server (“VAE-S”) ID,
an Edge Enabler Server (“EES”) ID, or
a new service profile ID,
or a combination thereof.
13 . The apparatus of claim 1 , wherein the second mapping of the first application comprises one or more of the following parameters:
a first application ID,
an application client IDs,
one or more UE IDs,
an old slice ID,
a target slice ID,
an old Data Network Name (“DNN”),
a new DNN,
a configured Single Network Slice Selection Assistance Information (“S-NSSAI”) for a target slice,
a slice-related parameter update,
an Area of validity,
a Time of validity,
or a combination thereof.
14 . The apparatus of claim 1 , wherein the second mapping to the second network slice triggers a UE subscription update for a UE for which the second mapping to the second slice is not contained in a list of Single Network Slice Selection Assistance Information (“S-NSSAI”).
15 . A method performed by an application function, the method comprising:
configuring a first mapping of a first application to a first network slice based on at least one application requirement of the first application, wherein the at least one application requirement comprises a requirement to re-locate to a new data network;
receiving a request for network slice adaptation for at least one user equipment (“UE”) associated with the first application, wherein the request comprises an identifier for the first application and further comprises a set of UE identifiers (“IDs”) associated with the first application and a trigger event report; and
determining, based on the trigger event report, a second mapping of the first application to a second network slice; and
transmitting the second mapping of the first application to the at least one UE associated with the first application or to a network function, or both, wherein the second mapping of the first application indicates a target data network.
16 . The method of claim 15 , wherein the first mapping further indicates a first Data Network Name (“DNN”) corresponding to the first application, and wherein the second mapping further indicates a second DNN corresponding to the first application.
17 . The method of claim 15 , wherein the first mapping and the second mapping are based on at least one application requirement obtained from the first application, wherein the first application comprises an application server and one or more application clients at one or more UEs.
18 . The method of claim 15 , further comprising transmitting a request to the network function for receiving network slice related parameters prior determining the first mapping of the first application.
19 . The method of claim 15 , wherein the second mapping to the second network slice triggers a UE subscription update for a UE for which the second mapping to the second slice is not contained in a list of enclosed at the Single Network Slice Selection Assistance Information (“S-NSSAI”) list.
20 . The method of claim 15 , wherein the at least one application requirement comprises:
a Quality of Experience (“QoE”) requirement,
a Quality of Service (“QoS”) requirement,
a UE mobility requirement,
a service profile requirement,
a service operation requirement,
or a combination thereof.