CN112425227B - Apparatus and method for managing network resources - Google Patents
Apparatus and method for managing network resources Download PDFInfo
- Publication number
- CN112425227B CN112425227B CN201880095567.8A CN201880095567A CN112425227B CN 112425227 B CN112425227 B CN 112425227B CN 201880095567 A CN201880095567 A CN 201880095567A CN 112425227 B CN112425227 B CN 112425227B
- Authority
- CN
- China
- Prior art keywords
- network
- user equipment
- network slice
- slice instance
- management entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 60
- 238000004891 communication Methods 0.000 claims abstract description 108
- 230000004044 response Effects 0.000 claims description 19
- 230000007704 transition Effects 0.000 claims description 18
- 238000007726 management method Methods 0.000 description 98
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 16
- 230000001960 triggered effect Effects 0.000 description 11
- 230000004048 modification Effects 0.000 description 10
- 238000012986 modification Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 6
- 230000003993 interaction Effects 0.000 description 6
- 230000008447 perception Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000003012 network analysis Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present application relates to a management entity for managing a plurality of network resources provided by a plurality of network slice instances in a communication network. The management entity comprises: a communication interface and a processor, the communication interface to receive an adjustment request from a user device, wherein the user device is attached to a first network slice instance, wherein the first network slice instance provides a first network resource to the user device, wherein the adjustment request defines an adjustment of the first network resource; the processor is configured to determine whether the first network slice instance is capable of providing the user equipment with the adjusted first network resource.
Description
Technical Field
The present application relates generally to communication networks. More particularly, the present application relates to an apparatus for managing network resources in a communication network, in particular a management entity for managing network resources in a communication network.
Background
According to industry consensus, standardization and deployment of fifth generation (5th Generation,5G) mobile technology will be achieved by 2020. Compared to 4G mobile telecommunication systems, 5G systems will support very diverse use cases of performance attributes, such as ultra-reliable communication for mission critical services, electronic health, public safety, real-time vehicle control, haptic internet, drone connectivity, etc. In order to support services with various requirements, according to the latest protocols of the standardized forum, the network slicing concept is expected to become one of the key components of 5G networks. The network slicing concept enables a service-customized network function provisioning scheme that is specifically directed to vertical industry integration. Network slicing is a collection of techniques for creating specialized, dedicated logical networks as services to support network service differentiation and meet the diverse requirements of the vertical industry. The network slice instance (network slice instance, NSI) is an implementation of the network slice concept. NSI is an end-to-end (E2E) logical network that includes a set of network functions, resources, and connectivity.
Among all 5G use cases, there are many use cases applied to the automotive industry. With the advent of autopilot functionality, vehicles would connect and communicate to exchange sensor data and plan paths. Autopilot places stringent performance requirements (latency, reliability, capacity) on 5G communication systems. For example, to support a wide range of vehicle-to-everything (V2X) use cases (e.g., cooperative collision avoidance, high density queuing driving, cooperative perception of autonomous vehicles), end-to-end latency is required to be less than 10ms and reliability is higher than 99.99%. Therefore, an understanding of how to design NSI to support V2X communications with specific performance requirements is crucial.
NSI may be designed and deployed based on a service-level-agreement (SLA) between the tenant and the operator. However, after NSI is deployed in the system, the exact system performance perceived by the terminals varies greatly due to reasons such as geographic location, environment, weather, etc. Thus, without 100% guaranteed service, mobile networks are difficult to accommodate, for example, diverse and stringent requirements from the vertical industry. Thus, how to ensure that a vehicle is working properly in this situation is a challenging problem, which can be considered to consist of two parts: first, how to guarantee performance-guaranteed end-to-end communication of V2X services (between two or more vehicles) in a highly dynamic environment; second, how to determine the required interactions between applications in V2X user equipment (V2X-UE) and the UE and/or communication parts in the cellular network to enable the terminal to modify the network requirements (especially the network slice adjustment on the V2X-UE side) to guarantee a guaranteed end-to-end communication.
Future vehicles will often have different modes of operation, as shown by the exemplary communication network 100 in fig. 1, which may be categorized, for example, by automation level: mode 1 is an automatic driving mode, mode 2 is an assisted driving mode, and mode 3 is a manual driving mode. Different modes of operation may invoke different in-vehicle applications, such as, for example, train travel, perspective, real-time traffic maps, etc. As shown in fig. 1, different modes of operation may be represented by state machines, the transition conditions of which depend on system performance. For example, if the system is in a high performance state where, for example, ultra low latency and high reliability can be guaranteed, the vehicle may transition from mode 3 to mode 2 or mode 1. When system performance is low (e.g., due to traffic congestion, geographic impact, etc.), the vehicle needs to transition from mode 1 to mode 3. Thus, to support V2X communications, the operation of V2X terminals is highly dependent on system performance, i.e., the performance of network 100.
Current 4G systems do not support such operational dependencies between the system and the terminal or user equipment. Furthermore, in current 4G systems, the interaction between the terminal and the application is semi-static and does not take into account the mode of operation.
In view of the foregoing, there is a need for improved apparatuses, systems, and methods that enable more efficient management of network resources in a communication network.
Disclosure of Invention
It is an object of the present application to provide a management entity, a user equipment, and a corresponding method, allowing for efficient management of network resources in a communication network.
The above object and other objects are achieved by the subject matter of the independent claims. Further embodiments are evident from the dependent claims, the description and the drawings.
In general, embodiments of the present application relate to a management entity, user Equipment (UE) or terminal, and corresponding method, for managing a plurality of network resources provided by a plurality of network slice instances in a communication network in an efficient manner. More specifically, embodiments of the present application may enable a tight collaboration between a user equipment and a communication network to facilitate services used at the user equipment, in particular services with critical performance requirements, such tight collaboration comprising two aspects: first, the user equipment can request information from the system (i.e., management entity) regarding current and/or recent performance metrics, and/or the communication system (i.e., management entity of the cellular network) periodically sends the message to the user equipment. This enables system performance awareness. Second, according to an embodiment, the user equipment is able to send a set of custom attributes of the Network Slice Instance (NSI) to the management entity, which are critical for a particular use case, the management entity can make adjustments to the system in terms of network service provisioning for a particular terminal, thus enabling terminal-triggered and network-controlled network slice instance adjustments. This may result in slice adjustment and/or slice reselection.
Embodiments of the present application provide, inter alia, the following advantages: causing a user device, such as a mobile terminal, to perceive real-time and/or estimated/predicted network conditions and performance, thereby enabling triggering of active network slice reselection and/or adjustment; and enabling the mobile network (i.e., management entity) to adjust and/or adapt NSI based on the user equipment actual/estimated performance requirements, taking network/slice conditions (e.g., congestion, availability, etc.) into account without affecting other user equipment performance.
More particularly, according to a first aspect, the present application relates to a management entity for managing a plurality of network resources provided by a plurality of network slice instances in a communication network. The management entity comprises a communication interface for receiving an adjustment request from a user equipment, wherein the user equipment is attached to a first network slice instance, wherein the first network slice instance provides a first network resource for the user equipment, wherein the adjustment request defines an adjustment of the first network resource. Further, the management entity comprises a processor for determining whether the first network slice instance is capable of providing the user equipment with the adjusted first network resource.
The user device may include an application that is at least partially operated by the user device, e.g., a side-by-side-queue travel application. An adjustment request may also be issued by the application.
The adjustment of the first network resources may include key performance indicators (key performance indicator, KPI) or quality of service (quality of service, qoS) parameters (e.g., delay, packet error rate, jitter, bit rate), and/or functional/protocol parameters, and/or resource parameters (e.g., spectrum/bandwidth, cloud resources).
Thus, an improved management entity is provided which allows for adjusting network resources for user equipment in an efficient manner. In an embodiment, the management entity may be implemented by a single physical server or a distributed physical server of an operator of the communication network. Alternatively, the management entity may be implemented by a physical cloud server. According to another alternative, the management entity may be implemented as a network function of the communication network, wherein the communication interface and the processor are implemented as virtual communication interfaces and virtual processors of the network function.
In another possible implementation of the first aspect, the processor is configured to select a second network slice instance capable of providing the user equipment with the adjusted first network resource, and attach the user equipment to the second network slice instance, in case the first network slice instance fails to provide the user equipment with the adjusted first network resource.
In a further possible implementation of the first aspect, the communication interface is configured to provide the user equipment with information related to the second network slice instance, in particular an identifier of the second network slice instance.
In another possible implementation manner of the first aspect, the communication interface is further configured to notify the user equipment that the adjustment request is denied in case the first network slice instance fails to provide the user equipment with the adjusted first network resource.
In another possible implementation of the first aspect, the communication interface is further configured to notify the user equipment that the adjustment request is approved if the first network slice instance is capable of providing the user equipment with the adjusted first network resource.
In a further possible implementation of the first aspect, the processor is configured to determine the predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance, and wherein the communication interface is further configured to provide the user equipment with information about the current performance metric and/or the predicted performance metric associated with the first network resource provided by the first network slice instance, in particular in response to an information request from the user equipment.
In another possible implementation of the first aspect, the processor is configured to determine a predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance, and the communication interface is further configured to provide the user equipment with information about the current performance metric and/or the predicted performance metric associated with the first network resource provided by the first network slice instance periodically and/or on an event (i.e. event trigger).
The event may be that the change in the current performance metric is greater than a threshold. Furthermore, the communication interface may be used to provide the user equipment with information about the current performance metric and/or the predicted performance metric periodically (i.e. at any predefined time interval, not limited to equidistant intervals).
In a further possible implementation of the first aspect, the communication interface is configured to provide the user equipment with information about a current performance metric and/or a predicted performance metric associated with the first network resource provided by the first network slice instance, periodically and/or on an event basis, in response to a subscription request of the user equipment.
In a further possible implementation of the first aspect, the current performance metric and/or the predicted performance metric is associated with at least one radio access network, at least one transport network, and/or at least one core network of the communication network.
In another possible implementation manner of the first aspect, the information related to the current performance metric and/or the predicted performance metric associated with the first network resource provided by the first network slice instance comprises: an identifier of the first network slice instance, in particular single network slice selection support information (singlenetwork slice selection assitance information, S-nsai) and/or network slice selection support information (network slice selection assitance information, nsai); information about current delay, current error rate, current jitter, current congestion level, current rate; information about predicted delay, predicted error rate, predicted jitter, predicted congestion level, predicted rate; and/or information related to a prediction reliability time window (i.e., a time window defining how long a prediction performance metric is reliable with a certain probability).
According to a second aspect, the present application relates to a corresponding method of managing a plurality of network resources provided by a plurality of network slice instances in a communication network, wherein the method comprises: receiving an adjustment request from a user device, wherein the user device is attached to a first network slice instance of a plurality of network slice instances of a communication network, wherein the first network slice instance provides the user device with a first network resource of a plurality of network resources, wherein the adjustment request defines an adjustment of the first network resource provided by the first network slice instance; and in response to receiving the adjustment request from the user device, determining whether the first network slice instance is capable of providing the adjusted first network resource for the user device.
Thus, an improved method is provided which allows for managing a plurality of network resources in an efficient manner.
According to a third aspect, the present application relates to a user equipment for using a first network resource provided by a first network slice instance in a communication network, wherein the user equipment comprises a communication interface for sending an adjustment request to a management entity, wherein the management entity is for managing a plurality of network resources provided by a plurality of network slice instances in the communication network, the plurality of network slice instances comprising the first network slice instance, the plurality of network resources comprising the first network resource, wherein the adjustment request defines an adjustment of the first network resource provided by the first network slice instance.
Thus, an improved user equipment is provided which allows triggering an adjustment of network resources in an efficient manner.
In another possible implementation of the third aspect, the user equipment further comprises a processor, wherein the processor is configured to implement a state machine for operating the user equipment in a plurality of states including a first state and a second state, wherein operating the user equipment in the first state requires a first network resource, and wherein operating the user equipment in the second state requires an adjusted first network resource.
In another possible implementation manner of the third aspect, the processor is configured to trigger sending the adjustment request to the management entity to transition from the first state to the second state.
According to a fourth aspect, the present application relates to a corresponding method of operating a user equipment for using a first network resource provided by a first network slice instance in a communication network, wherein the method comprises: sending an adjustment request to a management entity of the communication network, wherein the management entity is configured to manage a plurality of network resources provided by a plurality of network slice instances in the communication network, the plurality of network slice instances including a first network slice instance, the plurality of network resources including the first network resource, wherein the adjustment request defines an adjustment of the first network resource provided by the first network slice instance.
Thus, an improved method is provided which allows triggering the adjustment of network resources in an efficient manner.
According to a fifth aspect, the present application relates to a communication network comprising a plurality of network slice instances, a management entity according to the first aspect of the present application, and a user equipment according to the third aspect of the present application.
According to a sixth aspect, the present application relates to a computer program comprising a program code for performing the method of the second aspect and/or the method of the fourth aspect when executed on a computer.
The present application may be implemented in hardware and/or software.
Drawings
Other embodiments of the application will be described with reference to the following drawings, in which:
FIG. 1 shows a schematic diagram illustrating different modes of operation of a vehicle user equipment in a wireless communication network;
fig. 2 shows a schematic diagram of a wireless communication network comprising a management entity according to an embodiment and a user equipment according to an embodiment;
FIG. 3 shows a schematic diagram illustrating interactions between a management entity according to an embodiment and a user device according to an embodiment;
fig. 4 shows a schematic diagram illustrating different modes of operation of a user equipment according to an embodiment;
fig. 5 shows a flow chart illustrating state transitions of a user device according to an embodiment;
fig. 6 shows a diagram illustrating a signal flow between a management entity according to an embodiment and a user equipment according to an embodiment;
fig. 7 shows a diagram illustrating a signal flow between a management entity according to an embodiment and a user equipment according to an embodiment;
fig. 8A and 8B show diagrams illustrating respective signal flows between a management entity according to an embodiment and a user equipment according to an embodiment for two different network architectures;
fig. 9 shows a diagram illustrating a signal flow between a management entity according to an embodiment and a user equipment according to an embodiment;
Fig. 10 shows a diagram illustrating a signal flow between a management entity according to an embodiment and a user equipment according to an embodiment;
fig. 11 shows a schematic diagram of a wireless communication network comprising a management entity according to an embodiment and a user equipment according to an embodiment;
fig. 12 shows a schematic diagram of a wireless communication network comprising a management entity according to an embodiment and a user equipment according to an embodiment;
fig. 13 shows a schematic diagram of a wireless communication network comprising a management entity according to an embodiment and a user equipment according to an embodiment;
FIG. 14 shows a schematic diagram illustrating a method of managing a plurality of network resources in a communication network; and
fig. 15 shows a schematic diagram illustrating a method of operating a user equipment in a communication network.
In the drawings, like reference numerals are used for like or at least functionally equivalent features.
Detailed Description
In the following description, reference is made to the accompanying drawings, which form a part hereof, and in which are shown by way of illustration specific aspects of the application. It is to be understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present application. The following detailed description is, therefore, not to be taken in a limiting sense, since the scope of the present application is defined by the appended claims.
For example, it should be understood that the disclosure in connection with a described method also applies to a corresponding apparatus or system for performing the method, and vice versa. For example, if a specific method step is described, a corresponding device may comprise such a unit even if the unit for performing the described method step is not explicitly described or shown in the figures.
Furthermore, in the following detailed description and in the claims, examples are described having different functional blocks or processing units that are connected to or exchange signals with each other. It is to be understood that the present application also covers embodiments including additional functional blocks or processing units disposed between the functional blocks or processing units of the embodiments described below.
Finally, it should be understood that features of the various exemplary aspects described herein may be combined with one another, unless specifically indicated otherwise.
Fig. 2 schematically shows components of a wireless or cellular communication network 200, i.e. a management entity 201 according to an embodiment and a user equipment or mobile terminal 231 according to an embodiment.
The management entity 201 is for managing a plurality of network resources provided by a plurality of network slice instances of the communication network 200. To this end, as shown in fig. 2, the management entity 201 comprises a communication interface 203 and a processor 205.
The user equipment 231 is attached to a first NSI of the communication network 200 and is arranged to use a first network resource provided by the first NSI. To this end, the user device 231 comprises a communication interface 233 and a processor 235.
As will be described in further detail below, the communication interface 203 of the management entity 201 is configured to receive an adjustment request from the user equipment 231, wherein the adjustment request defines an adjustment of the first network resource provided by the first NSI, and the processor 205 of the management entity 201 is configured to determine whether the first NSI is capable of providing the adjusted first network resource to the user equipment 231.
In an embodiment, the wireless communication network 200 is a 5G network. In an embodiment, the management entity 201 may be implemented by a single physical server or a distributed physical server of a mobile network operator (mobile network operator, MNO) of the communication network 200. Alternatively, the management entity 201 may be implemented by a physical cloud server. According to another alternative, the management entity 201 may be implemented as a network function provided by the communication network 200, wherein the communication interface 203 and the processor 205 are implemented as virtual communication interfaces and virtual processors of the network function. In an embodiment, the user device 231 may be implemented as a mobile user device 231, in particular a vehicle user device 231. In an embodiment, the user device 231 may be implemented as a communication unit of a vehicle. In an embodiment, the V2X application 231a (as shown in fig. 3) may run on the communication unit or on a different control unit of the vehicle terminal with which it communicates.
Other embodiments of the management entity 201 and the user equipment 231 will be described below. As shown in fig. 3, an embodiment of the present application enables a tight interaction between the V2X application 231a in the mobile terminal 231 (or in communication with the mobile terminal 231) and the management entity 201 of the communication network 200, e.g. evolved packet system (evolved packet system, EPS), 5G system (5 gs), allowing for controlling the selection/adaptation of NSI to ensure that performance requirements are met. Thus, embodiments of the present application are based on two main aspects, namely, first, the perception of system performance by the V2X application 231a and/or the user equipment 231, and second, terminal-triggered and network-controlled NSI adjustment.
As shown in step 1 of the embodiment shown in fig. 3, for the perception of system performance by the user equipment 231 and/or the V2X application 231a, the user equipment 231 may request information from the management entity 201 (in fig. 3 referred to as communication system 201) regarding current and/or recent performance metrics associated with a plurality of NSIs provided by the communication network 200, in particular with a first NSI to which the user equipment 231 is attached for use of a first network resource provided by the first NSI. According to embodiments of the application, these performance metrics may include at least one of the following information elements and/or parameters: a slice identifier (particularly S-nsai/nsai) of one or more NSIs (particularly the first NSI) of the plurality of NSIs; information about the current NSI and/or network performance, such as information about latency, error rate, jitter, congestion level, rate; information about expected performance and/or performance fluctuations, e.g. latency, error rate, jitter, congestion level, rate; information about a time window of expected performance effectiveness (e.g., 1 minute, 1 hour, etc.); and/or network analysis and/or measurements performed by a radio access network (radio access network, RAN) and/or a Core Network (CN) of the communication network 200.
The terminal triggered and network controlled NSI adjustment provided by embodiments of the present application is illustrated by steps 2a to 2d of fig. 3. In step 2a, the user device 231 and/or the V2X application sends a set of custom attributes (i.e., adjustment requests) of NSI to the management entity 201, which are critical to a particular use case. In step 2b, the management entity 201 receives the adjustment request. In step 2c, the management entity 201 may adapt the system in terms of network service provisioning for a particular user device 231 or a set of user devices including the user device 231 affected by this change. In step 2d, the management entity 201 may send a notification with the necessary parameters back to the user equipment.
As described above, according to an embodiment of the present application, the user equipment 231 may be implemented as a vehicle user equipment or a vehicle type user equipment 231, which vehicle user equipment or vehicle type user equipment 231 includes an in-vehicle service and the capability to communicate with the mobile communication network 200. In an embodiment, the vehicle user equipment 231 may be in different operational states or modes, and the in-vehicle services may only be used when the user equipment 231 is in a particular state. The state may be defined by, for example, a slice type (e.g., enhanced movement bandwidth (enhanced mobile broadband, emmbb) state, ultra-reliable low-latency communication (URLLC) state, etc.), and/or by an application type (e.g., autonomous driving, assisted driving, manual driving). Fig. 4 shows a state machine of a user device 231 according to an embodiment, wherein the states 401, 402, and 403 may be, for example, an automatic driving state 401, an assisted driving state 402, and a manual driving state 403 (i.e., a non-assisted driving state).
Changing from one state to another is referred to as a state transition. According to an embodiment of the present application, the state transition of the user equipment 231 may be actively triggered or passively triggered. The active state transition may be triggered, for example, by the user device 231 deciding to use a service requiring a different state (e.g., a state transition from manual driving to assisted driving), or by the user device 231 deciding to simply terminate the service. The passive state transition may be triggered by a change in performance of the communication network 200, in particular the first NSI provided by the communication network 200. For example, a decrease in system performance greater than a predefined threshold may trigger the user device 231 to change from an automatic driving state to a manual driving state.
Fig. 5 shows a flow chart illustrating the steps involved in a state transition as implemented by an embodiment of the application. Before the service on the user equipment 231 is used, the user equipment 231 checks whether it is in the correct state to use the service. If not, a state change within the user equipment 231 is triggered (see step 501 of fig. 5) and the user equipment 231 requests assistance from the network 200 (more specifically, the management entity 201) by means of an adjustment request, as shown in step 503 of fig. 5. Based on the response of the management entity 201 to the adjustment request, the user device 231 will perform the required state transitions (step 507) or maintain its current state (step 509).
Thus, in an embodiment, the processor 235 of the user equipment is configured to implement a state machine for operating the user equipment 231 in a plurality of states including a first state and a second state, wherein operating the user equipment in the first state requires a first network resource, and wherein operating the user equipment in the second state requires an adjusted first network resource. In an embodiment, the processor 235 of the user equipment is configured to trigger sending an adjustment request to the management entity 201 to transition from the first state to the second state.
To facilitate state transitions of the user equipment 231, embodiments of the present application provide interactions between the user equipment 231 and the mobile communication network 200 (and in particular the management entity 201) to verify the transition conditions. The above-described interactions may be implemented in two different ways according to embodiments of the present application.
According to a first alternative request-response model as shown in fig. 6 may be implemented by an embodiment of the present application. When the terminal (i.e., the user equipment 231) is in state X and wants to transition to state y, information about the performance of the communication network 200 (in particular the first NSI provided by the communication network 200) needs to be obtained. To this end, in step 601 of fig. 6, the user equipment 231 sends a system metric request (system metric request, SMRq) message to the system (i.e., the management entity 201) to request information about the current performance or recent performance of the system. In step 603 of fig. 6, the system 300, upon receiving the SMRq message, sends back a system metric response (system metric response, SMRp) message containing information about the current or recent performance of the system.
According to a second alternative publish-subscribe model as shown in fig. 7 may be implemented by embodiments of the present application. When the terminal (i.e., user equipment 231) is in state X, the terminal sends a system metric subscription (system metric subscribe, SMSb) message to the management entity 201 in step 701 to subscribe to information about a specific system performance (e.g., SINR, latency, reliability, etc.). In response, the management entity 201 sends the subscribed information to the user equipment via a system metric publication (system metric publish, SMPb) message, as shown in steps 703, 705, and 707 of fig. 7. A timer or event (e.g., a metric change) may trigger this action.
Thus, in an embodiment, the processor 205 of the management entity 201 is configured to determine the predicted performance metric based on the current performance metric associated with the first network resource provided by the first network slice instance, wherein the communication interface 203 of the management entity 201 is further configured to provide the user device 231 with information related to the current performance metric and/or the predicted performance metric, in particular in response to an information request from the user device 231.
In an embodiment, the processor 205 of the management entity 201 is configured to determine a predicted performance metric based on a current performance metric associated with a first network resource provided by a first network slice instance, wherein the communication interface 203 of the management entity 201 is further configured to provide the user device 231 with information related to the current performance metric and/or the predicted performance metric periodically and/or on an event basis. In an embodiment, the communication interface 203 of the management entity 201 is configured to provide information about the current performance metric and/or the predicted performance metric to the user device 231 periodically and/or on the basis of events in response to a subscription request of the user device 231.
In an embodiment, the current performance metric and/or the predicted performance metric is associated with at least one radio access network, at least one transport network, and/or at least one core network of the communication network 200.
In an embodiment, the information about the current performance metric and/or the predicted performance metric comprises: an identifier of the first network slice instance, in particular S-nsai and/or nsai; information about current delay, current error rate, current jitter, current congestion level, current rate; information about predicted delay, predicted error rate, predicted jitter, predicted congestion level, predicted rate; and/or information related to a prediction reliability time window.
As shown in steps 811 and 813 of fig. 8A, where the information required by the user equipment 231 relates only to performance metrics associated with the RAN of the communication network 200, the RAN801 of the communication network 200 may handle the SMRq/SMRp/SMSb/SMPb described above in the context of fig. 5 and 6. In this case, these messages are Access Stratum (AS) messages and the management entity 201 may be at least partially implemented in the RAN801 of the communication network 200.
As shown in steps 831 and 833 of fig. 8B, in the event that the information required by the user equipment 231 relates to performance metrics associated with the RAN and/or CN of the communication network 200, the CN803 of the communication network 200 may process SMRq/SMRp/SMSb/SMPb messages. In an embodiment, a CN Network Function (NF) 803 may collect and data mine historical data, which may provide predictions with specific confidence intervals, providing the required metrics for the user equipment. In this case SMRq, SMRp, SMSb, as well as the SMPb message, are non-access stratum (NAS) messages and the management entity 201 may be at least partly implemented in the CN803 of the communication network 200, in particular as a network function of the CN 803.
As described above, embodiments of the present application enable terminal-triggered and network-controlled allocation and/or adjustment of system resources. For example, when the user device 231 is in a particular state (e.g., state X), it may be desirable to update the performance requirements (e.g., bandwidth). As described above, in this case, the user equipment 231 transmits an adjustment request, such as a system adjustment request (system adjustment request, SARq) message, containing information about the future performance requirements of the user equipment 231, to the management entity 201 (as shown in step 901 in fig. 9). Such requirements may include: slice-related information, such as slice type information; and/or performance related information such as latency, bandwidth, reliability, etc. Such information may be provided as exact values or as predefined indices.
According to an embodiment, the management entity 201, after receiving the message, will first verify the message based on e.g. subscription information and/or slice information of the user equipment. If the SARq message is valid, the management entity 201 will perform the corresponding adjustment (see step 903 of FIG. 9) and send a system adjustment response (system adjustment response, SARp) message back to the user device 231 (see step 905 of FIG. 9). In an embodiment, the SARp message may indicate one of the following adjustment results: (i) success: the resource allocation is adjusted according to the requirements of the user equipment 231; (ii) redirection: recommending that the user device 231 be associated with another system (in particular a network slice instance) that can meet the requirements of the user device 231; or (iii) failure: the management entity 201 rejects the SARq.
Thus, in an embodiment, the processor 205 of the management entity 201 is configured to select a second network slice instance capable of providing the user equipment 231 with the adjusted first network resource in case the first network slice instance fails to provide the user equipment 231 with the adjusted first network resource, and attach the user equipment 231 to the second network slice instance. In an embodiment, the communication interface 203 of the management entity 201 is arranged to provide the user equipment 231 with information related to the second network slice instance (in particular an identifier of the second network slice instance).
In an embodiment, the communication interface 203 of the management entity 201 is further configured to notify the user equipment 231 that the adjustment request is denied in case the first network slice instance cannot provide the user equipment 231 with the adjusted first network resource.
In an embodiment, the communication interface 203 of the management entity 201 is further configured to inform the user device 231 that the adjustment request is approved, in case the first network slice instance is capable of providing the user device 231 with the adjusted first network resource.
As described above, according to an embodiment of the present application, the SARq message and the SARp message are NAS messages, and may be handled by the management entity 201 implemented in the form of a network function of the CN803 (e.g., access and mobility management function (access and mobility management function, AMF) 1001 of the CN803 shown in fig. 10). If the adjustment request cannot be satisfied within the currently attached network slice (i.e., the first network slice), a handoff from one network slice to another may be triggered without changing the AMF 1001. The corresponding steps are shown in more detail in fig. 10. In step 1011 of fig. 10, the user equipment 231 triggers the procedure by sending an adjustment request in the form of a protocol data unit (protocol data unit, PDU) session modification request to the AMF 1001. In step 1012 of fig. 10, the AMF1001 triggers a PDU session modification procedure between the (R) AN801, the old session management function (session management function, SMF) 1002, the policy control function (policy control function, PCF) 1006, and the unified data management (unified data management, UDM) 1007. However, it will be appreciated that no modification can be made to the current PDU session. Thus, in step 1013 of fig. 10, AMF1001 performs an SMF reselection to select a new SMF1003. Thereafter, in step 1014 of fig. 10, the AMF1001 triggers a PDU session establishment procedure between the (R) AN801, the new SMF1003, the new UPF1005, the PCF1006, and the UDM 1007. At the same time, AMF1001 releases the PDU session on old SMF 1002 and old UPF 1004. Finally, in step 1015 of fig. 10, AN-specific resource modification (including PDU session modification command/ACK) is performed.
The above steps are slightly modified in case no adjustment can be made within the currently attached network slice instance (i.e. the first network instance). In this case, a handover from one network slice to another may be triggered without changing the current AMF 1001. More specifically, in a first step, the user equipment 231 triggers a procedure by sending a PDU session modification request to the AMF 1001. In a second step, the AMF triggers a PDU session modification procedure between (R) AN801, old SMF1002, PCF1006, and UDM 1007. However, it will be appreciated that no modification can be made to the current PDU session. Thus, in the third step, AMF1001 attempts to perform SMF reselection, but there are no SMFs that can be selected. In response thereto, in a fourth step, the AMF1001 suggests that the user equipment 231 performs a registration procedure, an AMF reselection, a separate re-registration/association procedure, or triggers an NS reselection by, for example, NSSF.
In the case where the adjustment can be made within the currently attached network slice, modifying the PDU session modification procedure may cover this case.
With further reference to fig. 11, a management entity 201 is provided as part of the network management plane of the communication network 200, according to an embodiment of the present application. In general, the network management plane provides the following services: instantiation, configuration, and activation of network slices. If the adjustment request from the user equipment 231 affects an adjustment that may not be of each terminal but of the overall network slice, it may be handled by the network management plane. In a corresponding embodiment, the user equipment sends an SARq message to the management entity 201, which is a NAS message. After receiving the request and verifying the credentials of the user device 231, a management entity, e.g. implemented in the form of an AMF1001, triggers the network service layer to communicate with the network management layer. The network management layer evaluates the adjustment request and can trigger corresponding adjustments in all relevant domains (as shown in fig. 11, i.e. AN801, CN 803) as well as in the transport network.
Fig. 12 shows another embodiment of a communication network 200 comprising a management entity 201 and a user equipment 231. In the embodiment shown in fig. 12, the management entity is an application entity, which may be an application belonging to a public land mobile network (public land mobile network, PLMN), and/or a third party application, and/or a vertical application. More specifically, the management entity 201 may be part of a V2X application server, and/or a V2X application enabling server (as defined in SA6, TR 23.795), and/or an Application Function (AF) (as defined in SA2, TS 23.501). In such an embodiment, the management entity 201 is configured to monitor and process system metrics of the V2X service (actual, and/or abstract, and/or predicted). As described above, when the V2X application 231a of the user device 231 determines the adaptability of the V2X status (also referred to as the automation level (level of automation, loA)), it sends a system adjustment request to the management entity 201. The management entity 201 responds to and triggers a system adjustment, in particular a slice instance resource adjustment or a slice instance reselection.
Fig. 13 shows another embodiment of a communication network 200 comprising a management entity 201 and a user equipment 231. In the embodiment shown in fig. 13, the management entity 201 is a network entity. More specifically, the management entity 201 may be part of a core network control plane (core network control plane, CN-CP), and/or RAN, and/or a slice management system of the communication network 200. As described above, the management entity 201 may be used to monitor and process system metrics of V2X services (actual, and/or abstract, and/or predicted). As described above, when the V2X application 231a of the user device 231 determines the adaptability (also referred to as LoA) of the V2X status, it sends a system adjustment request to the management entity 201. The management entity 201 responds to and triggers a system adjustment, in particular a slice instance resource adjustment or a slice instance reselection.
Fig. 14 shows a schematic diagram illustrating a method 1400 of managing a plurality of network resources provided by a plurality of network slice instances in a communication network 200. The method 1400 includes the steps of: step 1401, receiving an adjustment request from a user device 231, wherein the user device 231 is attached to a first network slice instance of a plurality of network slice instances, wherein the first network slice instance provides the user device 231 with a first network resource of a plurality of network resources, wherein the adjustment request defines an adjustment of the first network resource; and step 1403, in response to receiving the adjustment request, determining whether the first network slice instance is capable of providing the adjusted first network resource for the user equipment 231.
Fig. 15 shows a schematic diagram illustrating a method 1500 of operating a user equipment 231 for using a first network resource provided by a first network slice instance in a communication network 200.
The method 1500 includes the following step 1501: an adjustment request is sent to a management entity 201 of the communication network 200, wherein the management entity 201 is configured to manage a plurality of network resources provided by a plurality of network slice instances in the communication network 200, the plurality of network slice instances including a first network slice instance, the plurality of network resources including the first network resource, wherein the adjustment request defines an adjustment of the first network resource.
Although a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations or embodiments, such feature or aspect may be combined with one or more other features or aspects of the other implementations or embodiments, as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "includes," including, "" has, "" having, "or other variants are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term" comprising. Also, the terms "exemplary," e.g., and "such as" are merely representative of examples and are not intended to represent optimal or optimal. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms may have been used to indicate that two elements co-operate or interact with each other regardless of whether the elements are in direct physical or electrical contact or are not in direct contact with each other.
Although specific aspects have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific aspects shown and described without departing from the scope of the present disclosure. This disclosure is intended to cover any adaptations or variations of the specific aspects discussed herein.
Although elements in the claims are recited in a particular order with corresponding reference numerals, unless a claim recitation implies a particular order of implementing some or all of the elements, the elements are not limited to being implemented in that particular order.
Many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the above teaching. Of course, those skilled in the art will readily recognize that many applications of the present application are beyond the scope of the present application as described herein. While the application has been described with reference to one or more particular embodiments, those skilled in the art will recognize that many changes may be made thereto without departing from the scope of the present application. It is, therefore, to be understood that within the scope of the appended claims and equivalents thereof, the application may be practiced otherwise than as specifically described herein.
Claims (29)
1. A management entity (201) for managing a plurality of network resources provided by a plurality of network slice instances in a communication network (200), wherein the management entity (201) comprises:
-a communication interface (203) for receiving an adjustment request from a user equipment (231), wherein the user equipment (231) is attached to a first network slice instance, wherein the first network slice instance provides a first network resource for the user equipment (231), wherein the adjustment request defines an adjustment of the first network resource; and
A processor (205) for determining whether the first network slice instance is capable of providing the user equipment (231) with the adjusted first network resource, wherein the adjustment of the first network resource comprises one or more of a key performance indicator, a quality of service, qoS, parameters of functionality/protocols, resource parameters.
2. The management entity (201) of claim 1, wherein the processor (205) is configured to select a second network slice instance capable of providing the user equipment (231) with the adjusted first network resource if the first network slice instance fails to provide the user equipment (231) with the adjusted first network resource, and attach the user equipment (231) to the second network slice instance.
3. The management entity (201) of claim 2, wherein the communication interface (203) is configured to provide the user equipment (231) with information related to the second network slice instance.
4. A management entity (201) according to claim 3, wherein the information is an identifier of the second network slice instance.
5. The management entity (201) of claim 1, wherein the communication interface (203) is further configured to notify the user equipment (231) that the adjustment request is denied if the first network slice instance fails to provide the user equipment (231) with the adjusted first network resource.
6. The management entity (201) of claim 1, wherein the communication interface (203) is further configured to inform the user equipment (231) that the adjustment request is approved if the first network slice instance is capable of providing the user equipment (231) with the adjusted first network resource.
7. The management entity (201) according to any of claims 1-6, wherein the processor (205) is configured to determine a predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance, and wherein the communication interface (203) is further configured to provide the user equipment (231) with information related to the current performance metric and/or the predicted performance metric in response to an information request from the user equipment (231).
8. The management entity (201) according to any of claims 1-6, wherein the processor (205) is configured to determine a predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance, and wherein the communication interface (203) is further configured to provide the user equipment (231) with information related to the current performance metric and/or the predicted performance metric periodically and/or on an event basis.
9. The management entity (201) of claim 8, wherein the communication interface (203) is configured to provide information about the current performance metric and/or the predicted performance metric to the user equipment (231) periodically and/or on an event basis in response to a subscription request of the user equipment (231).
10. The management entity (201) of claim 7, wherein the current performance metric and/or the predicted performance metric is associated with at least one radio access network, at least one transport network, and/or at least one core network of the communication network (200).
11. The management entity (201) of claim 7, wherein the information about the current performance metric and/or the predicted performance metric comprises: an identifier of the first network slice instance comprising S-nsai and/or nsai; information about current delay, current error rate, current jitter, current congestion level, current rate; information about predicted delay, predicted error rate, predicted jitter, predicted congestion level, predicted rate; and/or information related to a prediction reliability time window.
12. A method (1400) of managing a plurality of network resources provided by a plurality of network slice instances in a communication network (200), wherein the method (1400) comprises:
-receiving (1401) an adjustment request from a user equipment (231), wherein the user equipment (231) is attached to a first network slice instance of the plurality of network slice instances, wherein the first network slice instance provides the user equipment (231) with a first network resource of the plurality of network resources, wherein the adjustment request defines an adjustment of the first network resource; and
in response to receiving the adjustment request, it is determined (1403) whether the first network slice instance is capable of providing the user equipment (231) with the adjusted first network resource, wherein the adjustment of the first network resource comprises one or more of a key performance indicator, a quality of service QoS parameter, a function parameter/protocol parameter, a resource parameter.
13. The method (1400) of claim 12, wherein the method (1400) includes:
in case the first network slice instance cannot provide the user equipment (231) with the adjusted first network resource, a second network slice instance capable of providing the user equipment (231) with the adjusted first network resource is selected and the user equipment (231) is attached to the second network slice instance.
14. The method (1400) of claim 13, wherein the method (1400) includes:
-providing information related to the second network slice instance to the user equipment (231).
15. The method (1400) of claim 14, wherein the information is an identifier of the second network slice instance.
16. The method (1400) of claim 12, wherein the method (1400) includes:
in case the first network slice instance cannot provide the user equipment (231) with the adjusted first network resource, informing the user equipment (231) that the adjustment request is denied.
17. The method (1400) of claim 12, wherein the method (1400) includes:
in case the first network slice instance is capable of providing the user equipment (231) with the adjusted first network resource, informing the user equipment (231) that the adjustment request is approved.
18. The method (1400) of any of claims 12-17, wherein the method (1400) includes:
determining a predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance;
-providing information about the current performance metric and/or the predicted performance metric to the user equipment (231) in response to an information request from the user equipment (231).
19. The method (1400) of any of claims 12-17, wherein the method (1400) includes:
determining a predicted performance metric based on a current performance metric associated with the first network resource provided by the first network slice instance;
-providing information about the current performance metric and/or the predicted performance metric to the user equipment (231) periodically and/or on the basis of events.
20. The method (1400) of claim 19, wherein the method (1400) includes:
-providing information about the current performance metric and/or the predicted performance metric to the user equipment (231) periodically and/or on an event basis in response to a subscription request of the user equipment (231).
21. The method (1400) of claim 18, wherein the current performance metric and/or the predicted performance metric is associated with at least one radio access network, at least one transport network, and/or at least one core network of the communication network (200).
22. The method (1400) of claim 18, wherein the information about the current performance metric and/or the predicted performance metric comprises: an identifier of the first network slice instance comprising S-nsai and/or nsai; information about current delay, current error rate, current jitter, current congestion level, current rate; information about predicted delay, predicted error rate, predicted jitter, predicted congestion level, predicted rate; and/or information related to a prediction reliability time window.
23. A user equipment (231) for using a first network resource provided by a first network slice instance in a communication network (200), wherein the user equipment (231) comprises:
-a communication interface (233) for sending an adjustment request to a management entity (201), wherein the management entity (201) is for managing a plurality of network resources provided by a plurality of network slice instances in the communication network (200), the plurality of network slice instances comprising the first network slice instance, the plurality of network resources comprising the first network resource, wherein the adjustment request defines an adjustment of the first network resource, the adjustment of the first network resource comprising one or more of a key performance indicator, a quality of service QoS parameter, a functional parameter/protocol parameter, a resource parameter.
24. The user equipment (231) of claim 23, wherein the user equipment (231) further comprises a processor (235), wherein the processor (235) is configured to implement a state machine configured to operate the user equipment (231) in a plurality of states including a first state and a second state, wherein operating the user equipment in the first state requires the first network resource, and wherein operating the user equipment in the second state requires the adjusted first network resource.
25. The user equipment (231) according to claim 24, wherein the processor (235) is configured to trigger sending the adjustment request to the management entity (201) to transition from the first state to the second state.
26. A method (1500) of operating a user equipment (231), the user equipment (231) being for using a first network resource provided by a first network slice instance in a communication network (200), wherein the method (1500) comprises:
-sending (1501) an adjustment request to a management entity (201) of the communication network (200), wherein the management entity (201) is configured to manage a plurality of network resources provided by a plurality of network slice instances in the communication network (200), the plurality of network slice instances comprising the first network slice instance, the plurality of network resources comprising the first network resource, wherein the adjustment request defines an adjustment of the first network resource, the adjustment of the first network resource comprising one or more of a key performance indicator, a quality of service QoS parameter, a function parameter/protocol parameter, a resource parameter.
27. The method (1500) of claim 26, wherein the method (1500) comprises:
operating the user equipment (231) in a plurality of states including a first state and a second state, wherein operating the user equipment in the first state requires the first network resource, and wherein operating the user equipment in the second state requires the adjusted first network resource.
28. The method (1500) of claim 27, wherein the method (1500) comprises:
triggering the sending of the adjustment request to the management entity (201) to transition from the first state to the second state.
29. A communication network (200) comprising a plurality of network slice instances, a management entity (201) according to any one of claims 1 to 10, and a user equipment (231) according to any one of claims 23 to 25.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2018/068817 WO2020011350A1 (en) | 2018-07-11 | 2018-07-11 | Devices and methods for managing network resources |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112425227A CN112425227A (en) | 2021-02-26 |
| CN112425227B true CN112425227B (en) | 2023-10-20 |
Family
ID=62948090
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201880095567.8A Active CN112425227B (en) | 2018-07-11 | 2018-07-11 | Apparatus and method for managing network resources |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112425227B (en) |
| WO (1) | WO2020011350A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4393157A1 (en) * | 2021-09-30 | 2024-07-03 | MediaTek Singapore Pte. Ltd. | Cross-layer optimization in xr-aware ran to limit temporal error propagation |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107708109A (en) * | 2016-08-08 | 2018-02-16 | 中兴通讯股份有限公司 | Method for processing business, device, system, base station, terminal and core network element |
| CN107710832A (en) * | 2015-06-01 | 2018-02-16 | 华为技术有限公司 | System and method for the virtualization in chain of command and data surface |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10142994B2 (en) * | 2016-04-18 | 2018-11-27 | Electronics And Telecommunications Research Institute | Communication method and apparatus using network slicing |
-
2018
- 2018-07-11 CN CN201880095567.8A patent/CN112425227B/en active Active
- 2018-07-11 WO PCT/EP2018/068817 patent/WO2020011350A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107710832A (en) * | 2015-06-01 | 2018-02-16 | 华为技术有限公司 | System and method for the virtualization in chain of command and data surface |
| CN107708109A (en) * | 2016-08-08 | 2018-02-16 | 中兴通讯股份有限公司 | Method for processing business, device, system, base station, terminal and core network element |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112425227A (en) | 2021-02-26 |
| WO2020011350A1 (en) | 2020-01-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7495069B2 (en) | DEVICE AND METHOD FOR PROVIDING QUALITY OF SERVICE FEATURES - Patent application | |
| US11722864B2 (en) | Entity, network, and user equipment for a V2X service as well as V2X application | |
| US11438807B2 (en) | Closed-loop control of a communication system for teleoperated driving | |
| CN111279743A (en) | Quality of service change notification techniques | |
| KR20200004397A (en) | FOSS control method and device | |
| CN109474450B (en) | Communication method, related equipment and system | |
| US20220369221A1 (en) | Entity and method for network slice enablement for a vertical application | |
| CA3187216A1 (en) | Managing the qos of an end-to-end application session | |
| CN113079541B (en) | Report information sending method, device and system | |
| US20220110024A1 (en) | Potential qos change notification methods and nodes for assisting application adjustment | |
| CN110326355A (en) | A kind of management method, administrative unit and system | |
| CN111246365B (en) | Mobile route management and control method, device and system | |
| CN116113919A (en) | Determining an expected QOS adaptation mode at a mobile edge computing entity | |
| WO2020052775A1 (en) | Device and method for providing a quality of service function | |
| WO2014071974A1 (en) | Mechanism for controlling a mobile communication with assured communication quality | |
| EP3198812B1 (en) | Congestion mitigation by offloading to non-3gpp networks | |
| CN112425227B (en) | Apparatus and method for managing network resources | |
| CN114651430B (en) | Network entity for managing distribution of slice service level agreement information in a communication network | |
| CN117204043A (en) | Apparatus and method for network slice admission control | |
| EP4164262A1 (en) | Network component, method for providing network connectivity, mobile terminal and method for performing radio communication | |
| CN115550965A (en) | Access network intelligent controller for multiple types of access networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |