Techniques for evaluating and / or providing QoS parameters for user equipment with mobile radio capability

The QoS parameters of network slices are dynamically adjusted through the QoS allocation device, which solves the problem that the QoS requirements of mobile radio capability user equipment cannot be met in the prior art, and realizes stable communication and data transmission of drones and other equipment.

CN120419240APending Publication Date: 2025-08-01DEUTSCHE TELEKOM AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480006182.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-01-05
Filing Date
2024-01-04
Publication Date
2025-08-01

AI Technical Summary

Technical Problem

In the prior art, the ability to dynamically modify slice resources is not sufficient to meet the QoS requirements of all mobile radio capability user equipment, especially in scenarios with fixed routes, predefined QoS values, such as the continuity of drone flight control and data transmission cannot be guaranteed.

Method used

Through the QoS allocation device, the QoS parameters of network slices are dynamically adjusted according to the QoS requirements of the radio-supported routes and path points of the user equipment, including retaining and increasing slice resources, ensuring that the QoS along the route meets the needs.

Benefits of technology

It realizes flexible QoS management of mobile radio-capable user equipment on fixed routes, ensures the continuity of communication and the reliability of data transmission, and is suitable for autonomous travel and remote operation of user equipment such as drones.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120419240A_ABST
    Figure CN120419240A_ABST
Patent Text Reader

Abstract

A method and system for evaluating and / or providing QoS parameters for a mobile radio-enabled user equipment, in particular a UAV, exchanging data with a radio communication network, comprising the steps of: requesting a radio network for a radio-supported route for the mobile radio-enabled user equipment, wherein the route request comprises geographic information, in particular waypoints of the route and corresponding QoS requirements for each of the waypoints; providing the QoS capacity of the radio network for the mobile radio-enabled user equipment according to the QoS requirements of the route by means of a QoS allocation device, in particular the QoS allocation device can be implemented as an OAM function that changes the QoS parameters of the corresponding network slice.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to a method, a radio communication system, a QoS allocation device, a verification device, and a computer program for evaluating and / or providing QoS parameters for a user equipment capable of mobile radio and exchanging data with a radio communication network. The radio communication network may be a 3GPP system.

[0002] 3GPP SA6 has completed TR 23.700-99, which is a technical report covering the research on the application architecture aspects solutions and enhancements for SEAL to enable network slice capability exposure.

[0003] This research has identified the architectural requirements and application architecture for supporting network slice capability exposure. The topics covered include: enhancements to network slice capability management, application layer exposure of network slice lifecycle management, discovery and registration aspects of management service exposure, network slice fault management capabilities, communication service management exposure, enabling application layer QoS verification capabilities, network slice related performance and analytics exposure, support for requirement transformation, support for trust enabling, support for managing (each) application owned by a trusted third party, dynamic slice SLA alignment, network slice capability exposure in edge data networks. Further technical background information of the present invention can be found in TS23.435 V0.4.0 (2022-11), which is hereby fully incorporated herein by reference.

[0004] There already exist technical means on how an Application Function (AF) can provide policies towards an NSCE server - for example, when the maximum number of PDU sessions / UEs is reached - to modify slice parameters through predefined steps. If a specific time period (summer) is reached - then slice resources can be reduced or increased.

[0005] There are use cases where a user equipment with mobile radio capabilities has to travel on a fixed route and where it is necessary to guarantee a predefined QoS value to this user equipment with mobile radio capabilities in order to enable C2 (command and control) communication. For example, if a UAV (Unmanned Aerial Vehicle) such as a drone flies through a certain area, it is important that flight control (e.g., remote flight control) is not interrupted. There are certain applications that have to transmit a certain amount of data along a specific route - for example, a UAV has a route of dozens of kilometers for visual inspection along an oil pipeline. Such UAVs need to have a certain guaranteed QoS along this route in order to be able to transmit data from the camera and for C2 communication (command and control).

[0006] However, the ability to dynamically modify slice resources is not sufficient for all use cases.

[0007] Therefore, the task is to provide a technology for implementing a more flexible solution to modify slice resources.

[0008] This object is solved by the features of the independent claims.

[0009] The features of the various aspects of the invention described below or the various embodiments can be combined with each other, unless this is explicitly excluded or technically impossible.

[0010] The invention discloses a method for evaluating and / or providing QoS parameters for a user equipment or user device (in particular a UAV) with mobile radio capabilities for exchanging data with a radio communication network. In particular, a user equipment with mobile radio capabilities receives control signals by means of a radio communication network. The method comprises the following steps:

[0011] · Requesting from the radio communication network a radio-supported route for a user equipment or user device with mobile radio capabilities, wherein the route request includes geographical information, in particular the path points of the route and the corresponding QoS requirements for each of these path points;

[0012] o The route can be requested as a policy for a user equipment or user device with mobile radio capabilities, which policy contains geographical information and corresponding QoS requirements; in principle, such policies already exist, but currently they lack geographical information;

[0013] o A user equipment with mobile radio capabilities and a UE can be technically the same;

[0014] o The route is a radio-supported route because a user equipment with mobile radio capabilities receives radio signals from the radio communication network along this route. By exchanging radio signals with the radio communication network, a user equipment with mobile radio capabilities can be remotely operated and / or the autonomous travel functionality of the user equipment with mobile radio capabilities can be realized. For this purpose, a user equipment with mobile radio capabilities is equipped with a transceiver for communicating with the radio network;

[0015] o The concept of path points has already been defined in ORAN TR36.777. A path point is a point that a user equipment with mobile radio capabilities can reach at a specific time, and a series of path points (preferably together with time) define a route. In one embodiment, the path points of the route are fixed; fixed path points mean that the user equipment with mobile radio capabilities must travel along these path points without deviation or switching to other path points.

[0016] o A user equipment with mobile radio capabilities, which can also be referred to as a user device (UE), can be a UAV (such as a drone), or a V2X (vehicle-to-everything) user equipment (such as a car, etc.).

[0017] o A user equipment with mobile radio capabilities, which can also be referred to as a user device (UE), can be a UAV (such as a drone), or a V2X (vehicle-to-everything) user equipment (such as a car, etc.).

[0018] Vehicle-to-Everything (V2X) is the communication between a vehicle and any entity that may affect the vehicle or any entity that may be affected by the vehicle. It is a vehicle communication system that combines other more specific communication types, such as V2I (Vehicle-to-Infrastructure), V2N (Vehicle-to-Network), V2V (Vehicle-to-Vehicle), V2P (Vehicle-to-Pedestrian), V2D (Vehicle-to-Device). The main motivations for V2X are road safety, traffic efficiency, energy conservation, and large-scale monitoring. There are two types of V2X communication technologies, and these two types of V2X communication technologies depend on the underlying

[0019] technology: based on WLAN and / or based on cellular (such as 5G);

[0020] · Provide and / or reserve the QoS capacity of the radio network for user equipment with mobile radio capabilities according to the QoS requirements of the route (especially for each waypoint) by a QoS allocation device. In particular, such a QoS allocation device can be implemented as an OAM (e.g., MnS) function that changes the QoS parameters of the corresponding network slice.

[0021] o The QoS allocation device can be implemented as a network function within a wireless communication network (especially a 5G network)

[0022] for changing the QoS parameters of the corresponding network slice.

[0023] o A 5G network includes several network slices, and each network slice can be configured, in particular, by using appropriate network functions to provide communication services with specific QoS capacities for user equipment or user equipment with mobile radio capabilities and the core network. If the QoS capacity changes, then the parameters of the network slice that provides the QoS capacity also change accordingly. For communication with the radio network, user equipment with mobile radio capabilities can generally select between the existing multiple subscribed slices and / or slices configured according to the QoS requirements of the radio-capable user equipment; in a 5G environment, along with the route, the radio-capable user equipment is attached to the subscribed network slice to pro

[0024] vide communication;

[0025] o If the QoS capacity of each path point already matches the QoS requirements, it is sufficient to reserve the QoS capacity for user equipment with mobile radio capabilities in order to provide C2 communication and exchange data with the required QoS parameters; this reservation ensures that user equipment with mobile radio capabilities can access the required QoS parameters; in this sense, "reservation" means that appropriate slice resources can only be used by user equipment with mobile radio capabilities and are blocked for any other device for at least a specific period of time; the reservation can also be done as follows (usually currently done in this way): the reservation is done for the slice itself. The slice resources can be reserved for the corresponding UEs subscribing to the slice and are not available for other slices;

[0026] o If the QoS capacity of at least one path point does not yet match the QoS requirements, then at least for that path point, the QoS allocation device needs to take measures to increase the QoS capacity and provide the corresponding slice QoS capacity along the route – in those cases, the corresponding slice is being modified; in the case of a 5G radio network, there are existing routines that can be triggered to increase the capacity of a network slice that is responsible for the path point and to which user equipment with mobile radio capabilities is attached;

[0027] o In the case of a 5G radio network, the QoS allocation device can be an NSCE server, where the NSCE server is provided with an appropriate AF policy that specifies the QoS requirements for the path points of the route;

[0028] o There can be multiple slices available and their parallel coexistence may not be properly configured, or there are unused resources that are not allocated to any slice. Specifically, the NSCE server can take a specific request and modify the existing slice in order to serve the corresponding user equipment with radio capabilities so as to ensure that there are sufficient resources to serve the specific QoS requirements along the route through which the user equipment with radio capabilities is flying. Preferably, the unused resources of the radio network are used to increase the capacity of the network slice to which user equipment with mobile radio capabilities is attached.

[0029] Therefore, this enables the modification of slice parameters based on location information. This provides the advantage that the required QoS parameters can be provided to user equipment with mobile radio capabilities along the route. This is important if these required QoSs are necessary for the secure remote and / or autonomous travel of user equipment with radio capabilities, especially in cases where the road is fixed and it is not possible for the user equipment with radio capabilities to reach its destination point by using other path points. This is an important prerequisite for implementing autonomous driving and / or remote driving functionality in future communication networks.

[0030] In an embodiment, the route request includes time information about the route, in particular time points specifying when a user equipment with mobile radio capabilities reaches the respective path points.

[0031] This provides the advantage that the QoS capacity of the corresponding slices including the radio network and the core network can be adjusted more appropriately with respect to time. Additionally, if the required QoS values are provided to the individual path points along the route, these required QoS values can be checked at appropriate time points. The time information enables the radio network including the core network to provide QoS requirements only at specific time points (in particular for predefined time windows) that actually match the time points when the user equipment with mobile radio capabilities actually uses the QoS capacity.

[0032] In an embodiment, the route request includes priority information. If there are high-priority UEs, they can be handled in high-priority slices. The priority seems to be predefined via subscription information, since some UEs can subscribe to high-priority slices.

[0033] This provides the advantage that the QoS allocation device can decide based on the priority information whether the QoS capacity of the network slice should be increased, or whether there are other requests with higher priority from other use cases, even other requests from other user equipment with mobile radio capabilities. If two use cases compete for the same resources, the use case with the higher priority is preferred.

[0034] In an embodiment, the route request includes different QoS requirements for at least two path points. This can be expressed as different QoS requirements can be requested for different regions. There can be path points along the route of the user equipment with mobile radio capabilities that require lower QoS requirements than other path points. For example, if a drone should inspect the infrastructure by providing video recordings of the infrastructure, there may be areas where such video recordings are not necessarily required, or areas where it is possible to record the video with lower quality.

[0035] This provides the advantage that the radio communication network can be used more efficiently, because if the QoS capacity of the slice providing the QoS capacity is higher than the QoS requirements of a specific path point, those slices do not need to be modified, even if the QoS requirements of other path points are higher.

[0036] In an embodiment, the route request includes ID information of the user equipment with mobile radio capabilities (i.e., user equipment).

[0037] This provides the following advantage that it can be ensured that the QoS capacity is only reserved and / or provided for the user equipment / user equipment for which the request has been submitted. The request can be submitted by the entity controlling the flight / owning the drone.

[0038] In an embodiment, the request is submitted by a user equipment with mobile radio capabilities, in particular a V2X or UAV, UAE layer, and / or UTM.

[0039] This provides the advantage that the request can be submitted in a very flexible manner. In particular, the entity creating the route with fixed waypoints can submit the request in a very flexible way.

[0040] In an embodiment, the verification device of the radio network checks whether the QoS capacity of the waypoints meets the corresponding QoS requirements. Preferably, this step is performed before modifying the slice parameters by using the allocation device. However, the allocation device can provide the required QoS capacity without this additional checking step. In an embodiment, the verification device is an NSCE server with appropriate algorithms.

[0041] This provides the advantage that it can be more efficient in terms of network resources to first check whether the QoS requirements along the route match before modifying the specific part of the slice containing the waypoints in question.

[0042] In an embodiment, the signaling device of the radio network sends a route confirmation signal, in particular the route confirmation signal is received by a user equipment with mobile radio capabilities, UAE layer, and / or UTM.

[0043] This provides the advantage that it provides the knowledge that the QoS capacity along the route is being met, so that a user equipment with mobile radio capabilities can start its route.

[0044] In an embodiment, the route confirmation signal includes a start time and / or speed information.

[0045] This provides the advantage that the time point at which a user equipment with mobile radio capabilities actually uses the network resources corresponding to the waypoints can be changed. This provides a more efficient use of network resources. For example, it may be the case that during the day, at least one waypoint does not provide the required QoS value, while at night, all waypoints provide the required QoS value. For such a case, the confirmation signal can include a start time during the night.

[0046] In an embodiment, the QoS capacity of the user equipment with mobile radio capabilities is released by the QoS allocation device after the route is completed and / or after a predefined time period.

[0047] This provides the advantage that after the network resources are no longer needed to serve the user equipment with mobile radio capabilities, the network resources can be efficiently reused for other use cases.

[0048] According to a second aspect of the present invention, there is provided a QoS allocation device for a radio communication network configured to perform the steps of the above method.

[0049] In particular, the QoS allocation device is configured to:

[0050] · Receive a request for a radio-supported route of a user equipment with mobile radio capabilities in a radio network, wherein the route request includes the waypoints of the route and the corresponding QoS requirements for each of these waypoints

[0051] thereof;

[0052] · Provide and / or reserve the QoS capacity of the radio network for the user equipment with mobile radio capabilities according to the QoS requirements for each of the waypoints.

[0053] The QoS allocation device provides the above advantages in the context of the method of the present invention.

[0054] According to a third aspect of the present invention, there is provided a QoS verification device for a radio network, wherein the QoS verification device is configured to perform the steps of the above method.

[0055] The QoS verification device provides the above advantages in the context of the method of the present invention.

[0056] According to a fourth aspect of the present invention, a radio communication network is disclosed. The radio communication network is configured to perform the steps of the above method. For this purpose, the radio communication network may include appropriate communication links, communication interfaces, data networks, databases, servers, and / or radio access networks (RANs), wherein the RAN includes base stations providing radio access to various waypoints.

[0057] In an embodiment, the radio communication network is a 5G communication network, a network such as a subsequent communication standard like 6G. The 5G communication network is particularly suitable for the present invention because the resources of network slices can be modified. The 5G network is designed such that slices can be dynamically identified to match the QoS requirements of certain use cases, in this example of a device with mobile radio capabilities such as a UAV or any other type of radio-capable vehicle requiring certain QoS values.

[0058] The radio communication network provides the above advantages in the context of the method of the present invention.

[0059] According to a fifth aspect of the present invention, a computer program comprising instructions which, when executed by a computer, in particular by a QoS allocation device, cause the computer to perform the steps of the above method.

[0060] In the following, preferred embodiments of the present invention are explained with reference to the accompanying drawings:

[0061] Figure 1 : shows the AF policy provisioning;

[0062] Figure 2 : shows the network slice modification based on the AF policy;

[0063] Figure 3 : shows a first exemplary AF policy table;

[0064] Figure 4 : shows a second exemplary AF policy table;

[0065] Figure 5 : shows a third exemplary AF policy table;

[0066] Figure 6 : shows a radio communication system according to the present invention.

[0067] In the following, numerous features of the present invention are explained in detail by means of preferred embodiments. The present disclosure is not limited to the specifically named feature combinations. On the contrary, the features mentioned herein can be combined arbitrarily into the embodiments of the present invention, unless this is explicitly excluded below.

[0068] The part of the preferred embodiment should start with a definition:

[0069] Network Slice Capability Enablement (NSCE) is a service that enables network slice-related capabilities for third parties based on R17 SEAL. The NSCE service provides additional functionality and exposes slice capabilities based on SA5 MnS services and SA2 services (such as NEF API, NWDAF API, NSACF API). This technical specification provides procedures for enabling the NSCE service on 3GPP networks that define the architecture in TS23.434. NWDAF is a 5G 3GPP standard method for collecting data from user equipment, network functions, and operation, administration, and maintenance (OAM) systems, etc. This data comes from the 5G core network, cloud, and edge networks and can be used for analysis. NWDAF can be implemented on the server of the 5G radio network; the NWDAF can predict the QoS capacity of the corresponding requested radio cell in a time-resolved manner, especially based on historical data. OAM is the operation and maintenance function of the 5G system.

[0070] The network slice optimization based on the AF policy optimizes the network slice for vertical applications by triggering the network slice modification exposed by the EGMF defined in SA5. Article 9.5 of TS23.434 stipulates the network slice optimization based on the AF policy procedure.

[0071] UAV-C is an unmanned aerial vehicle controller. QoS is quality of service. UAS is an unmanned aviation system. UTM is UAS traffic management. USS is a UAS service provider. UAS is an unmanned aviation system. The UAS application enablement layer shall support one or more UAS applications. The UAS application-specific client provides client-side functionality corresponding to the UAS application (e.g., a client that interacts with the USS, UTM). The UAS application-specific client uses the UAE client for UAS application layer support functions. The UAS application-specific server provides server-side functionality corresponding to the UAS application (e.g., USS, UTM, route planning unit). The UAS application-specific server uses the UAE server for UAS application layer support functions. The UAE client supports interaction with the UAS application-specific client(s). AF is application function. UAE is the UAS application enablement. VAL is the vertical application layer.

[0072] The general idea of the embodiments of the present invention can be described as follows:

[0073] Within a 5G system that is a radio communication network, the UAE layer can check whether there are sufficient available resources in the area / route where a user equipment with mobile radio capabilities should execute a route, especially in the area / route where a UAV flight should be executed, by using the NSCE server as a QoS verification device.

[0074] The UAE layer can receive the corresponding flight route in the form of waypoints and optionally the estimated time to reach the corresponding waypoints from the UTM.

[0075] When the UAE layer issues a request to the NSCE server acting as a QoS allocation device, the specific resources that generate the requested QoS capacity can be created and / or reserved by the NSCE server in a specific geographical location / service area of the slice, especially for a specific time period. The specific resources correspond to the specific QoS value provided by the slice to which the UAV is attached.

[0076] This introduces additional flexibility and enables the provision and reservation of corresponding resources before the start of the UAV flight or before the UAV UE enters a specific slice service area. The same principle can be applied to V2X UE. Where the VAE layer (defined in SA6) can receive a specific route in the form of waypoints from the application function and can request the reservation of a specific slice capacity for the UE subscribing to the slice via the NSCE server.

[0077] Hereinafter, this general idea of the embodiments of the present invention will be disclosed in more detail.

[0078] Figure 1 The AF policy provisioning of the method according to the present invention is shown, andFigure 2 Shows the AF policy-based network slice modification according to the method of the present invention.

[0079] The prerequisites for the method of the present invention may include:

[0080] · The NSCE server 100 has information about the existing slices / slice profiles / slice services of the 5G network 105 being used by the VAL server 110;

[0081] · The NSCE server 100 is authorized to obtain network slice

[0082] management data notifications from the OAM 115 and / or NWDAF 115;

[0083] · The VAL server 110 is authorized to the NSCE server 105 for network slice modification;

[0084] · When the expected action is to expand the network slice, there is sufficient network capacity;

[0085] · The AF policy has been pre-configured on the VAL server 110;

[0086] · The AF policy has been provided to the NSCE server 100;

[0087] Regarding Figure 1 , the following steps can be performed:

[0088] In Figure 1 Step 1: The VAL server 110 sends an AF policy provisioning request to the NSCE server 100. The request may include the policy, the requester identifier (e.g., VAL server ID), security credentials, and / or network slice-related identifiers (e.g., S-NSSAI). Optionally, the request contains an indicator for policy coordination. The AF policy is in the form of a policy profile that includes a list of trigger events associated with parameters such as start time and / or end time and the expected action.

[0089] Figure 3 、 Figure 4 and Figure 5 Show a possible AF policy table according to the present invention.

[0090] All of these AF policies show rows with location information 125, where the rows of the expected action 130 can instruct to modify the capacity of the slices at these locations according to the QoS requirements of the user equipment 145 with mobile radio capabilities (e.g., UAV 145). If the slice does not meet the QoS requirements, the modification can be triggered.

[0091] The VAL server 110 that provides the policy table can be implemented by a user equipment 145 with mobile radio capabilities, UAE server 110, UTM 110, or USS110.

[0092] It can be modified here to cover the possibility that there are fixed routes (list of waypoints, list of geographical regions that can be called regions of interest, time such as date-configured time) where specific QoS (especially per UE) values are required. Accordingly, this is valid for different applications, not only in the case of UAVs, but also generally for V2X UEs. The AF policy can include location (list of waypoints, list of geographical regions, time when the UE will be at a specific point or geographical region) together with the required QoS value.

[0093] Figure 3 and Figure 4 is a modification to introduce this location information into the existing AF policy table. The location 125 can also be referred to as the "region of interest" 125.

[0094] Figure 3 and Figure 4 The difference between Figure 4 is that in

[0095] Figure 5 it is not only by adding a location that one of the policy profiles is modified, but there can be general modifications to the policy profiles. In the policy profiles, only locations can be added. All policies can take location as a mandatory element, or it can also be an optional element. Subsequently, the "time period policy" can be modified to add QoS.

[0096] The benefits of having the new policies are that the corresponding existing policies are requested independently because they are created without giving the location / smaller part (slice coverage area) of the slice. Without using the new policies, a specific QoS can be requested for the entire slice; with smaller granularity, it can help achieve more precise resource scheduling when needed.

[0097] In Figure 1In step 2: The NSCE server 100 checks whether the policy conflicts with the service profile and other pre-configured policies. One criterion is to transform the network slice parameters in the service profile to see if they conflict with the network slice parameters in the policy provided by the AF. The NSCE server also checks the validity of the policy (in terms of time or the number of times an event has occurred) to avoid the ping-pong effect of slice modification. If the policy is invalid, the request may be rejected. The NSCE server 100 can also act as a QoS verification device for the radio network (especially the radio core network) to check whether the QoS capacity of the path point meets the corresponding QoS requirements. If this is the case, the QoS capacity is reserved for the user equipment 145 with mobile radio capabilities. If not, slice modification according to Figure 2 can be started.

[0098] In Figure 1 step 3: If policy coordination is requested and was previously authorized, the NSCE server can determine the parameters of the coordinated policy.

[0099] In Figure 1 step 4: The NSCE server 100 sends an AF policy provisioning response to the VAL server 110 to indicate whether the request was successful. If successful, the policy ID is provided to the VAL server.

[0100] Regarding Figure 2 , the following steps can be performed:

[0101] In Figure 2 step 1: The VAL server 110 sends the network slice modification request as one of the AF policy tables of any of Figures 3 to 5 to the NSCE server 100. The request may include a policy ID indicating different policies.

[0102] In Figure 2 step 2: The NSCE server transforms the trigger event into a (the) service API with the necessary parameters and subscribes to relevant services if necessary. The NSCE server 100 can monitor the 5G network 105 and can subscribe to NWDAF analysis. In order to obtain the monitored performance metrics from the OAM, "notifyThresholdCrossing (threshold crossing notification)" is required. In order to monitor the network slice load prediction from the NWDAF, the NSCE server 100 subscribes to the NWDAF prediction by using "Nnwdaf_AnalyticsSubscription_Subscribe (Nnwdaf_analytics subscription_subscribe)" or "Nnwdaf_AnalyticsInfo_Request (Nnwdaf_analytics information_request)".

[0103] InFigure 2 In step 3: The NSCE server sends a network slice optimization subscription response to the VAL server to confirm the subscription of network slice optimization.

[0104] In Figure 2 step 4: The NSCE server 100 performs the expected action by triggering a slice modification as specified in the AF policy table. The network slice modification can be triggered by invoking the network slice provisioning service with the "modifyMOIAttributes (Modify MOI Attributes)" operation. The OAM can respond to the NSCE server 100 whether the requested slice modification is successful. The slice modification request includes the parameters to be updated. Since according to Figures 3 to 5 any one of the AF policy tables includes location information, the modified QoS capacity of the slice can enable the user equipment 145 with mobile radio capabilities to take into account the waypoints of the route.

[0105] In Figure 2 step 5: The NSCE server 100 provides a network slice modification notification to the VAL server 110 so that the user equipment 145 with mobile radio capabilities can start its route.

[0106] Figure 6 FIG. shows a wireless communication system 140 according to the present invention. Figure 6 FIG. shows a user equipment 145 with mobile radio capabilities in an exemplary embodiment of the UAV 145, where the UAV 145 exchanges data, especially video data and command and control data traffic, with the 5G radio network 105 when traveling along its route. At each waypoint along the route, the UAV 145 is connected to the 5G radio communication network 105 by means of a base station 150.

[0107] The UAV-C 145 and / or the VAL server 110 can provide the AF policy table 155 according to Figures 3 to 5 any one of to the 5G radio communication network 105 to ensure that the slice to which the UAV 145 is connected provides QoS capabilities according to the requirements of the UAV 145 along its route.

[0108] Figure 6 FIG. schematically shows a first slice configuration 165 including a first slice 166 with a first QoS capacity and a second slice 167 with a second QoS capacity.

[0109] Figure 6 FIG. schematically shows a second slice configuration 165b including a first slice 166b with a first QoS capacity and a second slice 167b with a second QoS capacity.

[0110] The AF policy table 155 can be provided to the QoS allocation device 160. The QoS allocation device 160 can be the NSCE server 100. The QoS allocation device 160 can create a first slice 166b according to the second slice configuration 165b, where the QoS value of the first slice 166b is created based on the AF policy table 155. Specifically, the QoS value can be generated correspondingly for different locations (especially path points) of the 5G communication network 105.

[0111] It is also possible that the first slice 166b is reserved for the UAV 145 so that the UAV 145 can start its route and can ensure that its QoS requirements are met along the route.

[0112] The AF policy table 155 can be provided to the QoS verification device 170. The QoS verification device 170 can be the NSCE server 100. The QoS verification device 170 of the 5G communication network 105 checks whether the QoS capacity of the path point meets the corresponding QoS requirements.

[0113] If the slice configuration has been configured to include the second slice configuration 165b of the first slice 166b that has already matched the QoS requirements of the UAV 145, then it is only necessary to parse the slice for the UAV as described above.

[0114] On the other hand, the slice configuration is configured as the first slice configuration 165. This can be a case where neither the first slice 166 nor the second slice 167 matches the QoS requirements of the UAV 145. In this case, the first slice 166 or the second slice 167 can be modified accordingly based on the AF policy table 155 as described above. In an embodiment, the first slice 166 of the first slice configuration is modified to the first slice 166b of the second slice configuration.

[0115] After this modification, the UAV 145 can start its route, where it is ensured that the QoS requirements of the UAV are met along the route.

Claims

1. A method for evaluating and / or providing QoS parameters for a user equipment (145), in particular a UAV (145), capable of mobile radio and exchanging data with a radio communication network (105), comprising the following steps: · Requesting from the radio communication network (105) a radio-supported route for the user equipment (145) capable of mobile radio, for example as a policy, where the route request includes geographical information (125), in particular waypoints (125) of the route and corresponding QoS requirements for each of the waypoints; · Providing, by a QoS allocation device (160), the QoS capacity of the radio communication network (105) for the user equipment capable of mobile radio according to the QoS requirements of the route, in particular the QoS allocation device is implemented as an OAM function for changing QoS parameters of corresponding network slices (166, 166b).

2. The method according to claim 1, characterized in that: The route request includes time information about the route, in particular time points specifying when the user equipment (145) capable of mobile radio arrives at the corresponding waypoints.

3. The method according to any one of the preceding claims, characterized in that: The route request includes priority information.

4. The method according to any one of the preceding claims, characterized in that: The route request includes different QoS requirements for at least two of the waypoints.

5. The method according to any one of the preceding claims, characterized in that: The route request includes ID information of the user equipment (145) capable of mobile radio.

6. The method according to any one of the preceding claims, characterized in that: The request is submitted by the user equipment (145) capable of mobile radio, the UAE layer, a server acting as a UAV-C, and / or the UTM.

7. The method according to any one of the preceding claims, characterized in that: Checking, by a QoS verification device of the radio network, in particular the radio core network, whether the QoS capacity of the waypoints meets the corresponding QoS requirements.

8. The method according to claim 7, characterized in that: The signaling device of the radio network sends a route confirmation signal, in particular the route confirmation signal is received by the user equipment (145) capable of mobile radio, the UAE layer, and / or the UTM.

9. The method according to claim 8, wherein: The route confirmation signal includes start time and / or speed information.

10. The method according to any one of the preceding claims, characterized in that: Releasing, by the QoS allocation device, the QoS capacity of the user equipment capable of mobile radio after completion of the route and / or after a predefined time period.

11. A QoS allocation device (160) of a radio communication network (105), the QoS allocation device (160) being configured to perform the steps of the method according to claim 1, in particular the QoS allocation device is configured to: · Receive a request for a radio-supported route for a user equipment capable of mobile radio of the radio network, where the route request includes waypoints of the route and corresponding QoS requirements for each of the waypoints; · Provide and / or reserve the QoS capacity of the radio network for the user equipment capable of mobile radio according to the QoS requirements for each of the waypoints.

12. A QoS verification device (170) of a radio network, the QoS verification device (170) being configured to perform the steps of the method according to claim 7.

13. A radio communication network configured to perform the steps of the method according to claim 1 and / or claim 7, wherein the communication network comprises a QoS allocation device according to claim 11 and / or a QoS verification device according to claim 12.

14. The radio communication network according to claim 13, wherein the radio communication network is a 5G radio communication network.

15. A computer program comprising instructions which, when the program is executed by a computer, in particular by a QoS allocation device according to claim 11, cause the computer to perform the steps of the method according to claim 1.