CN116017720A

CN116017720A - Wireless scheduling method, device and system

Info

Publication number: CN116017720A
Application number: CN202111213260.3A
Authority: CN
Inventors: 韩文勇; 丁辉; 周凯; 朱锦涛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-19
Filing date: 2021-10-19
Publication date: 2023-04-25
Also published as: WO2023065953A1

Abstract

The application provides a wireless scheduling method, a wireless scheduling device and a wireless scheduling system, wherein the wireless scheduling method comprises the following steps: the access network equipment receives a first quality of service (QoS) parameter and a second QoS parameter from a first network element; the access network device schedules a first data flow using the first QoS parameter; the access network equipment receives first indication information; the access network device schedules the first data flow using the second QoS parameter according to the first indication information. According to the method, the QoS parameters are replaced by configuration, when the network equipment needs to change the QoS parameters, a new configuration flow is not required to be repeated, the QoS parameters can be quickly switched, time delay is saved, the reliability of air interface transmission can be ensured, and the network efficiency is improved.

Description

Wireless scheduling method, device and system

Technical Field

The present disclosure relates to the field of communications, and in particular, to a wireless scheduling method, apparatus, and system.

Background

With the continuous development of the fifth generation mobile communication technology (5th generation mobile communication technology,5G) industrial internet technology, device communication in the industrial internet is currently being shifted from a wired-based communication to a wireless-based communication mode. The operation technology (operational technology, OT) is an important link of industrial automation as an important technology of industrial Internet. Networks using OT technology may be referred to as OT networks.

The wireless scheduling of the industrial internet is low in efficiency at present, taking the specific event of the OT network as an example, when data transmitted in the OT network is lost, the network should schedule the data by using a high-reliability quality of service (quality of service, qoS) policy. The control plane network element in the network modifies the corresponding QoS policy and resends it to the access network device. The wireless scheduling efficiency in the process is low, and the time delay requirement cannot be met. The equipment in the OT network continuously loses data in the time required for the control plane network element to reconfigure the QoS policy, which may cause equipment downtime, affecting production efficiency.

Therefore, how to improve the efficiency of the OT network in processing specific events and ensure the reliability of air interface transmission is a problem to be solved.

Disclosure of Invention

The application provides a wireless scheduling method, device and system. In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

in a first aspect, an embodiment of the present application provides a wireless scheduling method, where the method may include: the access network equipment receives a first quality of service (QoS) parameter and a second QoS parameter from a first network element; the access network device schedules a first data flow using the first QoS parameter; the access network equipment receives first indication information; the access network device schedules the first data flow using the second QoS parameter according to the first indication information. The method pre-configures the alternative QoS parameters, and when the QoS parameters need to be changed, the access network equipment does not need to re-initiate the flow of configuring the QoS parameters. The method improves the switching speed of QoS parameters, can rapidly meet the transmission requirement of data flow, ensures the reliability of air interface transmission, and improves the efficiency of wireless scheduling.

It will be appreciated that QoS parameters may also be referred to as QoS policies, qoS configurations, or QoS parameter information, and may also be referred to as names of other parameters for guaranteeing the quality of service of the network, as the present application is not limited. The above description may be applicable to descriptions of other aspects of the present application, and will not be repeated.

Furthermore, it is understood that the access network device may also receive at least one other QoS parameter from the first network element than the first QoS parameter and the second QoS parameter, which may each be an alternative QoS parameter to the first QoS parameter. The QoS parameters may correspond to different requirements of the same type, for example, a second QoS parameter corresponds to a requirement with a delay less than 2s, and a third QoS parameter corresponds to a requirement with a delay less than 1 s. The QoS parameters may also correspond to different types of requirements, for example, the fourth QoS parameter corresponds to a latency requirement of less than 2s, and the fifth QoS parameter corresponds to a requirement of less than 1% of packet loss rate. It should be understood that the QoS parameters may be sent by the first network element to the access network device, or may be preconfigured (also called preset) by the access network device, which is not limited in this application. The above description may be applied to descriptions of other aspects of the present application, and similar parts will not be repeated hereinafter.

It should be understood that, the access network device schedules the first data flow using the first QoS parameter, which may be that the access network device schedules one or more data packets in the first data flow using the first QoS parameter; the access network device uses the second QoS parameter to schedule the first data flow according to the first indication information, and may be the access network device uses the second QoS parameter to schedule data packets in the first data flow, except for the data packets scheduled by using the first QoS parameter, where the data packets may be one or multiple data packets. That is, packets scheduled by different QoS parameters may be different. The above description may be applied to descriptions of other aspects of the present application, and similar parts will not be repeated hereinafter.

In one possible implementation manner, the access network device receives the first data stream, where the first data stream includes a first data packet, and the first data packet includes the first indication information. That is, the indication information for indicating the handover QoS parameter may be carried in the data packet to be scheduled for transmission to the access network device. According to the implementation mode, the QoS parameters are adjusted for a specific one or more data packets, and the access network equipment receives the first indication information and the data packets to be scheduled at the same time, so that the time delay of signaling transmission can be saved, and the efficiency of wireless scheduling is further improved.

In one possible implementation manner, the access network device may schedule the first data packet using the second QoS parameter according to the first indication information; the implementation may further include: the access network device schedules other data packets in the first data stream than the first data packet using the first QoS parameter. That is, after the access network device schedules the current data packet using the second QoS parameter, the access network device may change the second QoS parameter to the first QoS parameter by itself, and schedule the subsequent data packet using the first QoS parameter. According to the implementation mode, after the access network equipment finishes scheduling of the data packet with higher transmission requirement, the QoS parameter is automatically recovered, and time-frequency resources can be effectively saved, so that the power consumption of the communication equipment is saved, and the efficiency of scheduling the data stream is improved.

A possible implementation manner, the access network device receives second indication information from the user plane function network element after the access network device schedules the first data flow according to the first indication information and using the second QoS parameter; the access network device schedules the first data flow using the first QoS parameter according to the second indication information.

In other words, the access network device may switch the QoS parameters after receiving the first indication information, or wait to receive the indication information from the user plane function network element, and switch the QoS parameters according to the indication information. The implementation mode provides a method for recovering the QoS parameters after the access network completes scheduling, and improves the flexibility of QoS parameter recovery.

It should be understood that the above access network device recovers the QoS parameters after completing the scheduling, and switches from the second QoS parameters to the first QoS parameters. When the access network device receives multiple QoS parameters from the first network element, the access network device may also switch from the second QoS parameter to a sixth QoS parameter, where the requirement corresponding to the sixth QoS parameter may be less stringent than the requirement corresponding to the second QoS parameter. Illustratively, the second QoS parameter corresponds to a requirement of latency less than 2 seconds and the sixth QoS parameter corresponds to a requirement of latency less than 4 seconds. It is to be understood that the above numbers are by way of example only and not by way of limitation. That is, the access network device may recover the QoS parameters before scheduling after completing scheduling, or may switch to a QoS parameter different from the first QoS parameter and the second QoS parameter.

It should also be understood that after the access network device completes scheduling and automatically switches the QoS parameters, the switched QoS parameters may also be reported to the user plane functional network element.

In addition, it may be appreciated that the data packet scheduled by the access network device after completing the scheduling using the QoS parameter switched again may be different from the data packet scheduled before the first QoS parameter and the second QoS parameter.

A possible implementation manner, the access network device receives the first indication information from a user plane function network element.

One possible implementation, the second indication information is general packet radio service user plane type information.

One possible implementation manner, the first indication information is general packet radio service user plane type information.

In a second aspect, an embodiment of the present application provides a wireless scheduling method, where the method may include: the access network equipment receives a first quality of service (QoS) parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter from a first network element; the access network device schedules a first data flow using the first QoS parameter; after the network state satisfies the handoff condition, the access network device schedules the first data flow using the second QoS parameter. In the method, the access network equipment receives the QoS parameters from the first network element and can also receive the switching conditions corresponding to the second QoS parameters, and the access network equipment can automatically detect according to the switching conditions and automatically switch the QoS parameters when the switching conditions are met. The access network equipment does not need to wait for receiving the switching instruction from other network elements, further shortens signaling delay, can rapidly switch QoS parameters, ensures the reliability of air interface transmission, and improves the efficiency of OT network processing specific events.

It should be understood that the handover condition corresponding to the second QoS parameter may be a condition for handover to the second QoS parameter, that is, the condition may be used to determine whether to handover to the second QoS parameter. The switching conditions may include a relationship between signal-to-noise ratio, channel utilization, channel quality of service or packet loss rate and an associated threshold. For example, the switching condition may be that the signal-to-noise ratio is smaller than a certain threshold, or that the channel usage is larger than a certain threshold, or that the channel service quality is smaller than a certain threshold, that the packet loss ratio is larger than a certain threshold, or the like. Wherein the channel usage rate may represent a degree of usage of the channel, in other words, the channel usage rate may represent a degree of congestion of the channel.

It should also be appreciated that when multiple QoS parameters are present, the multiple QoS parameters may correspond to different handoff conditions. Here, the corresponding relation between the plurality of QoS parameters and different handover conditions may refer to the description of the corresponding relation between the plurality of QoS parameters and different requirements in the first aspect, which is not repeated.

It should also be appreciated that the parameters included in the handover condition may be replaced by other similar parameters, and that the packet loss rate may be replaced by the number of packets lost, for example. The handover conditions may also include other parameters affecting the quality of service, such as bit error rate, etc. The present application is not limited in this regard. The above description about the handover condition is applicable to other aspects, and will not be repeated hereinafter.

In one possible implementation manner, the access network device sends third indication information to the first network element, where the third indication information includes a cause value, where the cause value is used to indicate a cause of the access network device scheduling the first data flow using the second QoS parameter.

It should be appreciated that the cause value may be a handover condition that is satisfied by the QoS parameter being handed over, for example, the cause value may include at least one of a signal-to-noise ratio being less than a certain threshold, a channel usage being greater than a certain threshold, a channel quality of service being less than a certain threshold, a packet loss being greater than a certain threshold, and so on. It will be appreciated that the cause value may also be used to indicate a specific value of a parameter affecting the occurrence of this handover. For example, the switching condition satisfied by the switching is that the packet loss rate is greater than 5%, and the specific value affecting the parameters of the switching, namely the packet loss rate, is 8%. The present application is not limited in this regard.

In addition, the access network device may also send the second QoS parameter to the first network element.

That is, the access network device may send the switched QoS parameter to the first network element, where the first network element learns the parameter to perform a subsequent charging procedure, and/or the first network element notifies the terminal device of the switched parameter. It may be appreciated that the first network element may store a correspondence between QoS parameters and handover conditions, and after the access network device sends the QoS parameters after handover to the first network element, the first network element may determine a condition satisfied by the handover. That is, the access network device may also implement the function of reporting the switching condition by reporting the QoS parameter after the switching.

A possible implementation manner, after the access network device meets the handover condition, the access network device may schedule the first data packet of the first data flow using the second QoS parameter; the implementation may further include: the access network device uses the first QoS parameter to schedule other data packets in the first data flow than the first data packet.

That is, the access network device automatically restores to schedule other data packets in the first data flow with the first QoS parameter after completing the scheduling of the first data packet. In the scheme, the access network equipment does not need to wait for the information indicating to restore the first QoS parameters under the condition that the second QoS parameters are used for completing the scheduling of the first data packet, so that the time delay is further shortened, and the efficiency of processing the data stream is improved.

It will be appreciated that the access network device may also switch to a seventh QoS parameter, which may refer to the description of the sixth QoS parameter in the first aspect, which is not described here again.

A possible implementation manner, after the access network device uses the second QoS parameter to schedule the first data flow after the network state meets the handover condition, the access network device receives fourth indication information from the user plane function network element; the access network device schedules the first data flow using the first QoS parameter according to the fourth indication information.

It will be appreciated that, as an alternative, the access network device may also wait for a handover indication sent by the user plane function network element, according to which the QoS parameters are handed over. The flexibility of switching QoS parameters of the access network equipment after the completion of the scheduling is improved.

A possible implementation manner, the switching condition includes at least one of the following: the signal-to-noise ratio is less than or equal to a first threshold, the channel usage is greater than or equal to a second threshold, the channel quality of service is less than or equal to a third threshold, and the packet loss rate is greater than or equal to a fourth threshold.

The above thresholds may be preset.

In a third aspect, an embodiment of the present application provides a wireless scheduling method, where the method may include: the first network element generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter; the first network element sends the first QoS parameter and the second QoS parameter to access network equipment and user plane function network elements; the first network element sends the switching condition to the access network equipment or the user plane function network element; or the first network element sends the first QoS parameter, the second QoS parameter and the handover condition to the access network device, and sends the first QoS parameter and the second QoS parameter to the user plane function network element. According to the scheme, the standby QoS parameters and the switching conditions corresponding to the standby QoS parameters are generated through the first network element, the first network element sends the parameters and the switching conditions to the access network equipment and the user plane function network element, and when the OT network encounters a specific event, the first network element does not need to reconfigure the QoS parameters for the data flow to be scheduled, so that the efficiency of switching the QoS parameters of the access network equipment can be improved, and the wireless scheduling efficiency is improved.

One possible implementation manner, the session management function network element receives fourth indication information from the user plane function network element; the session management function network element performs a first action according to the fourth indication information, the first action comprising at least one of charging or informing the terminal device of a handover of the QoS parameter.

In a fourth aspect, an embodiment of the present application provides a wireless scheduling method, where the method may include: the user plane functional network element receives a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter from a first network element, wherein the first QoS parameter or the second QoS parameter is used for scheduling a first data flow; after the network state meets the switching condition, the user plane function network element sends first indication information to the access network device, wherein the first indication information is used for indicating and scheduling the QoS parameters of the first data flow, and the first QoS parameters are switched to the second QoS parameters. According to the scheme, the standby QoS parameters and the corresponding switching conditions are sent to the user plane functional network element, the user plane functional network element can judge whether the conditions are met, and when the conditions are met, information indicating switching is sent to the access network equipment, so that the detection flexibility is improved.

It will be appreciated that the user plane function network element may also receive at least one other QoS parameter from the first network element than the first QoS parameter and the second QoS parameter, which may each be an alternative QoS parameter to the first QoS parameter. The explanation and supplementation of QoS parameters are similar to those of the first aspect, and will not be repeated here.

In one possible implementation manner, after the network state does not meet the handover condition, the user plane function network element sends second indication information to the access network device, where the second indication information is used to indicate, to schedule QoS parameters of the first data flow, and switch from the second QoS parameters to the first QoS parameters.

In one possible implementation manner, the user plane function network element sends the first data flow to the access network device, where the first data flow includes a first data packet, and the user plane function network element carries the first indication information through the first data packet.

In one possible implementation manner, the user plane function network element sends fourth indication information to the first network element, where the fourth indication information is used to indicate that the QoS parameter of the scheduled first data flow is switched from the second QoS parameter to the first QoS parameter.

In a fifth aspect, embodiments of the present application provide a communication device. The communication device may comprise a transceiver unit for receiving a first quality of service, qoS, parameter and a second QoS parameter from a first network element; a processing unit for scheduling a first data flow using the first QoS parameter; the receiving and transmitting unit is also used for receiving the first indication information; the processing unit is further configured to schedule the first data flow using the second QoS parameter according to the first indication information.

It should be understood that the fifth aspect is an apparatus embodiment corresponding to the method embodiment of the first aspect, and the explanation, supplement and beneficial effect of each possible implementation manner in the first aspect is applicable to the fifth aspect, which is not repeated herein.

In a sixth aspect, embodiments of the present application provide a communications device, where the communications device may include a transceiver unit configured to receive, from a first network element, a first quality of service QoS parameter, a second QoS parameter, and a handover condition corresponding to the second QoS parameter; a processing unit for scheduling a first data flow using the first QoS parameter; the processing unit is further configured to schedule the first data flow using the second QoS parameter after the network status satisfies the handoff condition.

It should be understood that the sixth aspect is an apparatus embodiment corresponding to the method embodiment of the second aspect, and the explanation, supplement and beneficial effect of each possible implementation manner in the second aspect is applicable to the sixth aspect, which is not repeated herein.

In a seventh aspect, embodiments of the present application provide a communication device, which may include a processing unit configured to generate a first quality of service QoS parameter, a second QoS parameter, and a handover condition corresponding to the second QoS parameter; a transceiver unit, configured to send the first QoS parameter and the second QoS parameter to an access network device and a user plane function network element; the transceiver unit is further configured to send the handover condition to the access network device or the user plane function network element.

It should be understood that the seventh aspect is an apparatus embodiment corresponding to the method embodiment of the third aspect, and that the explanation, supplementation and beneficial effect of each possible implementation manner in the third aspect is applicable to the seventh aspect, and is not repeated here.

In an eighth aspect, embodiments of the present application provide a communication device, which may include a transceiver unit configured to receive, from a first network element, a first quality of service QoS parameter, a second QoS parameter, and a handover condition corresponding to the second QoS parameter, where the first QoS parameter or the second QoS parameter is used to schedule a first data flow; a processing unit, configured to schedule a first data flow according to the first QoS parameter or the second QoS parameter after the network status satisfies the handover condition; the transceiver unit is further configured to send first indication information to the access network device, where the first indication information is used for indicating, and is used for scheduling QoS parameters of the first data flow, and switching from the first QoS parameters to the second QoS parameters.

It should be understood that the eighth aspect is an apparatus embodiment corresponding to the method embodiment of the fourth aspect, and that the explanation, supplement and beneficial effect of each possible implementation manner in the fourth aspect is applicable to the eighth aspect, and is not repeated herein.

A ninth aspect provides a communication system comprising an apparatus having means for implementing the above-mentioned first or second or third or fourth aspects, or any one of the possible implementations of the first or second or third or fourth aspects, or all of the possible implementations of the first or second or third or fourth aspects, and various possible designed functions.

A tenth aspect provides a processor, coupled to a memory, for performing the method of the first aspect or the second aspect or the third aspect or the fourth aspect described above, or any possible implementation of the first aspect or the second aspect or the third aspect or the fourth aspect, or all possible implementation of the first aspect or the second aspect or the third aspect or the fourth aspect.

An eleventh aspect provides a chip comprising a processor for communicating with an external device or an internal device, and a communication interface for implementing the above-described first or second or third or fourth aspects, or any of the possible implementations of the first or second or third or fourth aspects, or the method in all of the possible implementations of the first or second or third or fourth aspects.

Optionally, the chip may further include a memory having instructions stored therein, the processor being configured to execute the instructions stored in the memory or derived from other instructions. The processor is configured to implement the method of the first or second or third or fourth aspect described above or any possible implementation thereof when the instructions are executed.

Alternatively, the chip may be integrated on the terminal.

A twelfth aspect provides a computer readable medium storing program code for execution by a communication device, the program code comprising instructions for performing the first or second or third or fourth aspects, or any one of the possible implementations of the first or second or third or fourth aspects, or the communication method in the method of all of the possible implementations of the first or second or third or fourth aspects

A thirteenth aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the above-described first or second or third or fourth aspects, or any one of the possible implementations of the first or second or third or fourth aspects, or a method of all of the possible implementations of the first or second or third or fourth aspects.

Drawings

FIG. 1 illustrates a schematic diagram of an example communication architecture suitable for use in embodiments of the present application;

fig. 2 shows a flow chart of a wireless scheduling method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a wireless scheduling method according to an embodiment of the present application;

fig. 4 is a schematic flow chart of another wireless scheduling method according to an embodiment of the present application;

fig. 5 is a schematic flow chart of another wireless scheduling method according to an embodiment of the present application;

fig. 6 is a schematic flow chart of another wireless scheduling method according to an embodiment of the present application;

FIG. 7 shows a schematic block diagram of a communication device provided by an embodiment of the present application;

fig. 8 shows a schematic block diagram of another communication device provided in an embodiment of the present application.

Detailed Description

Fig. 1 is a schematic diagram of a 5GS architecture based on the form of a servitization interface. The network architecture comprises three parts, namely a terminal device, AN access network (R) AN and a core network.

The details of the parts involved in the network architecture are described below.

The terminal equipment is equipment with a wireless receiving and transmitting function. The terminal device is connected to the access network device by a wireless manner, so that the terminal device accessed to the communication system may also be called a terminal, a User Equipment (UE), a mobile station, a mobile terminal, etc. The terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiving function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned operation, a wireless terminal in teleoperation, a wireless terminal in smart grid, a wireless terminal in transportation security, a wireless terminal in smart city, a wireless terminal in smart home, or the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal equipment. By way of example and not limitation, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device or an intelligent wearable device, and is a generic name for intelligently designing daily wear and developing wearable devices, such as glasses, gloves, watches, clothes, shoes, and the like, by applying wearable technology. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring. The terminal device may also be an in-vehicle module, an in-vehicle component, an in-vehicle chip, or an in-vehicle unit built in the vehicle as one or more components or units, through which the vehicle may implement the method of the present application.

Illustratively, in an industrial field network, the terminal device may be a customer terminal device (customer premise equipment, CPE).

The (R) AN is used to implement wireless-related functions. The nodes in the (R) AN may also be referred to as access network devices or base stations for accessing the terminal devices to the wireless network. The access network device may be a base station (base station), an evolved NodeB (eNodeB) in an LTE system or an evolved LTE system (LTE-Advanced), a next generation NodeB (gNB) in a 5G communication system, a transmission reception point (transmission reception point, TRP), a baseband unit (BBU), a WiFi Access Point (AP), a base station in a future mobile communication system or an access node in a WiFi system, etc. The radio access network device may also be a module or unit that performs the functions of the base station part, for example, a Centralized Unit (CU), or a Distributed Unit (DU). The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the wireless access network equipment. For example, in one network architecture, the radio access network device may be a CU node, or a DU node, or an access network device comprising a CU node and a DU node. Specifically, the CU node is configured to support protocols such as radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP), etc.; the DU node is used to support radio link control (radio link control, RLC) layer protocols, medium access control (medium access control, MAC) layer protocols, and physical layer protocols.

The core network may include one or more of the following network elements: unified data management (unified data management, UDM) network elements, application function (application function, AF) network elements, policy control function (Policy Control Function, PCF) network elements, network opening function (Network Exposure Function, NEF) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, user plane function (user plane function, UPF) network elements, and the like. Each network element described above may also be referred to as an apparatus, device or entity, and the application is not limited herein, for example, a UDM network element may also be referred to as a UDM apparatus, UDM device or UDM entity. For convenience of description, hereinafter, the manner of short-term will be used, for example, "UDM network element" is abbreviated as "UDM" and "SMF network element" is abbreviated as "SMF".

The UDM is responsible for managing subscription data, notifying corresponding network elements when the subscription data is modified, managing group information, and the like. For example, in the user registration networking procedure, the UE sends a registration request to the AMF, and the AMF obtains subscription data from the UDM according to the user identifier of the user. The UE can implement data exchange between the UE and a Data Network (DN) by registering with the network and establishing a protocol data unit (protocol data unit, PDU) session procedure.

The AF is used for providing application layer services to the terminal device. The AF interacts with other controlling network elements on behalf of the application, including providing quality of service (quality of service, qoS) requirements, charging (Policy) requirements, routing Policy requirements, etc.

The PCF is used for the generation of terminal device access policies and QoS control policies, etc.

The AMF is used to take charge of mobility management of the user. Mobility management includes, for example, mobility state management, assigning a user temporary identity, authenticating and authorizing a user, and the like.

The SMF is used to take charge of the selection, reselection, network protocol (internet protocol, IP) address assignment, establishment, modification or release of PDU sessions, etc.

The UPF is interconnected with DN for detection, routing and forwarding of packet data packets. For example, the UPF may act as an upstream classifier (uplink classifier, ULCL) to support offloading traffic before forwarding to the data network, or the UPF may act as a offload point (BP) to support multi-homed PDU sessions.

The network elements described above may be implemented by specified hardware, or may be implemented by software instances on specified hardware, or may be implemented by virtual functions instantiated on a suitable platform, which is not limited in this regard.

The network elements may be existing names in future communication systems, or may have other names, which are not limited in this application.

The methods of the present application may be applicable to industrial networks or other networks, which are described herein by way of example, but are not emphasized that the methods are applicable only to industrial network scenarios.

The operation technology (operational technology, OT) is an important link of industrial automation as an important technology of industrial Internet. Networks using OT technology may be referred to as OT networks. The OT network may be implemented based on the network architecture shown in fig. 1. Among other things, in an OT network, for example, data is periodically and rapidly transferred between a programmable logic controller (programmable logic controller, PLC) and Input Output (IO) devices, the PLC may control specific behaviors of the IO devices in the network, for example, control states of input data of the IO devices. Specifically, the PLC may access the DN in fig. 1, and the IO device may be connected to the UE in fig. 1, so that the PLC may implement communication with the IO device through the network shown in fig. 1, thereby implementing control over the IO device. Therefore, the communication quality between the PLC and the IO device depends on the network state in the network shown in fig. 1.

At present, for different service flows or data packets, the QoS parameters corresponding to the service flows or data packets are generated by the control plane function network element. QoS parameters need to be replaced immediately when a specific event occurs in the OT network. For example, a particular event may be a loss of data, that is, the occurrence of the particular event results in the QoS parameters requiring immediate replacement. At this time, the OT network re-initiates a flow of configuring QoS parameters, and the access network device requests the control plane functional network element to reconfigure QoS parameters, and the control plane functional network element generates new QoS parameters and sends the new QoS parameters to the access network device. The access network device schedules subsequent data packets using the newly configured QoS parameters.

The method cannot meet the time delay requirement of data transmission in the OT network. If the time delay of the flow of reconfiguring QoS parameters in the OT network after data loss occurs in a certain data transmission period is longer than the time interval between adjacent data transmission periods, the QoS policy in the OT network cannot be replaced before the next data transmission period, and the IO continuously loses a plurality of data packets. IO is down when a plurality of data packets are continuously lost (for example, 3 data packets can be used), and the production efficiency is seriously affected.

The schemes of the embodiments provided in the present application are set forth below taking the switching of QoS parameters in an OT network as an example. It should be understood that the schemes of the embodiments of the present application are not limited to OT networks, and are also applicable to other application scenarios including QoS parameter switching procedures.

In view of the above problems, the present application proposes a wireless scheduling method, which is shown in fig. 2:

step 201: the first network element generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second parameter.

The first network element may be an SMF.

Wherein the first QoS parameter may be used to schedule a data flow in a normal transmission state. The second QoS parameter may be a backup QoS parameter that may be used to schedule the data flow when a particular event occurs. For example, the specific event may be a degradation of the service quality of the OT network, or a data loss in the OT network.

The switching condition may be understood as the occurrence of a specific event. The handoff condition may correspond to a second QoS parameter. For example, the handover condition may be determined according to a parameter affecting the quality of service, e.g. the handover condition may be at least one of: the signal-to-noise ratio is smaller than the first threshold, the channel utilization is larger than the second threshold, the channel service quality is smaller than the third threshold, and the packet loss rate is larger than the fourth threshold. Wherein the channel usage rate may represent a degree of usage of the channel, in other words, the channel usage rate may represent a degree of congestion of the channel.

It should be understood that the parameters included in the handover condition may be replaced by other parameters, and for example, the packet loss rate may be replaced by the number of packet losses. The handover conditions may also include other parameters affecting the quality of service, such as bit error rate, etc. The present application is not limited in this regard.

It should be understood that, instead of generating the first QoS parameter, the first network element may also generate other QoS parameters, which include the second QoS parameter, and which may correspond to different handover conditions. For example, the plurality of QoS parameters may correspond to different requirements of the same type. For example, the second QoS parameter corresponds to a requirement of less than 2 seconds in time delay, and the third QoS parameter corresponds to a requirement of less than 1 second in time delay.

The QoS parameters may also correspond to different types of requirements, for example, the fourth QoS parameter corresponds to a requirement that the delay is less than 2 seconds, and the fifth QoS parameter corresponds to a requirement that the packet loss rate is less than 1%.

The present application is not limited in this regard. The above description may be applied to descriptions about QoS parameters in embodiments of the present application, and similar descriptions are omitted hereinafter.

Step 202: the first network element sends the first QoS parameter and the second QoS parameter to the access network device.

Accordingly, the access network device receives the first quality of service QoS parameter and the second QoS parameter from the first network element.

Step 203: the access network device schedules the first data flow using the first QoS parameter.

Step 204: the first network element sends the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second parameter to the user plane function network element.

Step 205: after the network state meets the switching condition, the user plane function network element sends first indication information to the access network equipment.

Whether the network state meets the switching condition or not can be judged by the user plane function network element.

For example, the user plane function network element may determine the handover condition by detecting a parameter for characterizing the quality of service by the user plane function network element, and determining a magnitude relation between the parameter and a threshold corresponding to the parameter. For example, the packet loss rate detected by the user plane functional network element is 5%, and the preset threshold value of the packet loss rate is 2%, and if the packet loss rate detected by the user plane functional network element is greater than the preset threshold value of the packet loss rate, the user plane functional network element determines that the switching condition is satisfied.

Optionally, the user plane function network element may send a first data stream, where the first data stream includes a first data packet, and the first data packet includes first indication information. The first indication information may be general packet radio service user plane type information.

The first indication information may indicate a QoS parameter for scheduling the first data flow to switch from the first QoS parameter to the second QoS parameter. The indication method can comprise the following two methods:

the first indication information may be a handover indication, for example, the content of the first indication information is a handover notification. That is, the user plane function network element informs the access network device to perform the handover action through the handover indication. It will be appreciated that the indication method may be applicable to scenarios where the access network device receives two QoS parameters, i.e. the access network device receives only a first QoS parameter and a second QoS parameter.

The first indication information may also indicate the second QoS parameter, that is, the first indication information indicates that the target QoS parameter to be switched is the second QoS parameter. It can be appreciated that the indication method may be applicable to a scenario in which the access network device receives two QoS parameters, or may be applicable to a scenario in which the access network device receives multiple QoS parameters.

It should be understood that the above indication method is only exemplary and not limiting, and other indication methods that can achieve the same effect are also within the scope of the present application.

Step 206: the access network device schedules the first data flow by using the second QoS parameter according to the first indication information.

The access network device scheduling the first data flow using the first QoS parameter may be that the access network device schedules one or more data packets in the first data flow using the first QoS parameter; the access network device uses the second QoS parameter to schedule the first data flow according to the first indication information, and may be the access network device uses the second QoS parameter to schedule data packets in the first data flow, except for the data packets scheduled by using the first QoS parameter, where the data packets may be one or multiple data packets. That is, packets scheduled by different QoS parameters may be different. The above description may be applied to other similar places in the present application, and will not be repeated.

In one possible implementation, the method may further include: the user plane function network element sends fourth indication information to the first network element.

The fourth indication information is used for notifying the first network element that the QoS switching event occurs. The first network element may perform subsequent actions according to the handover notification, e.g., the first network element performs a charging action, and/or the first network element notifies the UE that a QoS handover event has occurred.

In one possible implementation, the method may further include: the access network device schedules a current first data flow using the first QoS parameter. The implementation may be understood as the access network device switching from scheduling the current first data flow using the second QoS parameters to scheduling the current first data flow using the first QoS parameters. In particular, the implementation may include, but is not limited to, the following:

First alternative case: after the network state does not meet the switching condition, the user plane function network element sends second indication information to the access network equipment, and the access network equipment uses the first QoS parameter to schedule the current first data flow.

Whether the network state satisfies the handover condition may be determined by the user plane function network element.

For example, if the packet loss rate detected by the user plane functional network element is 1% and the preset threshold of the packet loss rate is 2%, the user plane device determines that the handover condition is not satisfied.

For example, in the case where the access network device completes scheduling the first data flow using the second QoS parameter, when the access network device receives the second indication information, the access network device schedules the current first data flow using the first QoS parameter. That is, after receiving the second indication information, the access network device switches the second QoS parameter currently used for scheduling the data flow to the first QoS parameter according to the second indication information.

The second indication information may be general packet radio service user plane type information, for example.

This optional scenario includes one possible implementation, where the user plane function network element also sends a handover notification to the first network element. The switch notification is used to notify the first network element that the access network device switches from scheduling the current first data flow using the second QoS parameter to scheduling the current first data flow using the first QoS parameter. That is, the first network element may learn the QoS parameters after the handover according to the handover notification. The first network element may perform subsequent actions according to the switched QoS parameters, for example, the first network element charges according to the QoS parameters used by the current access network device. For another example, the first network element may inform the terminal device that the access network device switches the second QoS parameters currently used for scheduling the data flow to the first QoS parameters.

Second alternative case: the access network device schedules a current first data flow using the first QoS parameter. This alternative scenario may be understood as that the access network device may switch to the first QoS parameter by itself after completing scheduling the first data packet using the second QoS parameter, and schedule other data packets using the first QoS parameter.

For example, the optional case may further include: the access network equipment reports the QoS parameters after switching to the user plane function network element.

In the method of this embodiment, the first network element generates two QoS parameters, that is, the first QoS parameter and the second QoS parameter, for example, it should be understood that, if the first network element generates, in addition to the first QoS parameter, another plurality of QoS parameters including the second QoS parameter, a plurality of QoS parameters including a sixth QoS parameter and a seventh QoS parameter are taken as an example. In the first case of step 206, when the access network device receives a plurality of QoS parameters from the first network element, the second indication information may also be used to instruct the access network device to switch the second QoS parameter currently used for scheduling the data flow to a sixth QoS parameter, where the requirement corresponding to the sixth QoS parameter may be less stringent than the requirement corresponding to the second QoS parameter. Illustratively, the second QoS parameter corresponds to a requirement of latency less than 2 seconds and the sixth QoS parameter corresponds to a requirement of latency less than 4 seconds. It is to be understood that the above numbers are by way of example only and not by way of limitation.

In the second case of step 206, when the access network device receives a plurality of QoS parameters from the first network element, the access network device may also switch from the second QoS parameter to a seventh QoS parameter, where the scheduling of the first data packet is completed using the second QoS parameter, where the requirement corresponding to the seventh QoS parameter may be less stringent than the requirement corresponding to the second QoS parameter. Illustratively, the second QoS parameter corresponds to a requirement that the delay be less than 2 seconds and the seventh QoS parameter corresponds to a requirement that the delay be less than 4 seconds.

It is to be understood that the above numbers are by way of example only and not by way of limitation.

That is, the access network device may recover the QoS parameters before scheduling after completing scheduling, or may switch to a QoS parameter different from the first QoS parameter and the second QoS parameter.

According to the scheme, the first network element generates a plurality of QoS parameters and sends the QoS parameters to the access network equipment, the user plane functional network element informs the access network equipment to switch the QoS parameters, the OT network does not need to be initiated to reconfigure the QoS parameters, the switching efficiency of the QoS parameters is improved, and the reliable transmission of an air interface is further ensured.

The above explanation and supplement of QoS parameters, first indication information, second indication information, and fourth indication information are applicable to the embodiments of the present application, and similar parts will not be repeated hereinafter.

In connection with the method shown in fig. 2, the present application provides a method for wireless scheduling, as shown in fig. 3, where the method shown in the figure is described by taking an OT network scenario as an example. In this scenario, the CPE may be a UE in the system architecture shown in fig. 1, and the CPE may be connected to a plurality of devices (e.g., IO devices) that may transmit data with the PLC through the CPE. The data flow in the method shown in the figure may be the first data flow in fig. 2, the SMF may be the first network element in the method shown in fig. 2, the RAN may be the access network device in the method shown in fig. 2, and the UPF may be the user plane function network element in the method shown in fig. 2. The method may comprise the steps of:

step 301: the CPE sends a session establishment request to the SMF.

For example, the session may be an ethernet PDU session.

It should be understood that the CPE may also send a session modification request to the SMF, as this application is not limited in this regard.

One possible way is that the ethernet PDU session corresponds to a default QoS flow identity (QoS flow identifier, QFI) and a service QFI. Wherein the default QFI corresponds to a QoS parameter, and the service QFI corresponds to a first QoS parameter and a second QoS parameter. The following steps take the first QoS parameter and the second QoS parameter corresponding to the service QFI as an example to make scheme statements.

Step 302: the SMF generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter.

It should be understood that step 302 may refer to the description in step 201 in fig. 2, and will not be described herein.

Step 303: the SMF sends the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second QoS parameter to the UPF.

This step may be described with reference to step 204 shown in fig. 2.

Step 304: the SMF sends the first QoS parameter and the second QoS parameter to the RAN.

The SMF may send the first QoS parameter, the second QoS parameter, and a handover condition corresponding to the second QoS parameter to the RAN based on a policy and charging control Rule (policy and charging control Rule, PCC Rule) issued by the PCF.

This step may be described with reference to step 202 shown in fig. 2.

Step 303 and step 304 may be performed simultaneously or separately, and this is not a limitation of the present application.

Step 305: the RAN sends the first QoS parameters to the CPE.

Accordingly, the CPE receives the first QoS parameter. After the CPE receives the first QoS parameter, the CPE may schedule the data flow received by the CPE using the first QoS parameter.

Step 306: the session establishment is completed.

The session is the session requested to be established in step 301. Also, the session may be a PDU session.

It should be appreciated that when the CPE sends a session modification request to the SMF in step 301, step 306 may be that the session modification is complete.

Step 307: the RAN schedules the data flow using the first QoS parameters.

It is understood that the RAN schedules the data flow as indicated by the first QoS parameter such that the QoS of the data flow may meet the indication of the QoS parameter.

Step 308: the device and the PLC transmit the data packets.

It should be appreciated that in an OT network, data packets are periodically transmitted between a device and a PLC, for example, the device transmits data packets between the device and the PLC through a CPE.

When the device receives a data packet from the PLC, the device performs an action corresponding to the information indicated by the data packet. For example, the device may be a robotic arm, the data packet including information indicating "left", the robotic arm performing a movement to the left upon receiving the data packet. The CPE has a function of forwarding the data packet, that is, forwarding the data packet between the device and the PLC can be implemented by the CPE.

Step 309: the UPF detects a specific event.

The UPF can determine whether the network state satisfies the handover condition by detecting a specific event. For example, if the device or PLC fails to receive data within a certain period, it may indicate that the transmission is abnormal and that a specific event has occurred in the OT network. The UPF may determine that a specific event occurs according to the first condition. For example, when the UPF detects that the signal-to-noise ratio is smaller than a certain threshold, or the channel usage rate is larger than a certain threshold, or the channel service quality is smaller than a certain threshold, or the packet loss rate is larger than a certain threshold, the UPF may determine that the data transmission state in the OT network meets the first condition. That is, a specific event occurs in the OT network.

The first condition may refer to the description of the switching condition in step 205 in fig. 2, and the step may refer to the description in step 205 in fig. 2, which is not repeated herein.

Step 310: the UPF sends handover indication information to the RAN.

The handover indication information may refer to the description of the first indication information in step 205 in fig. 2.

It should be appreciated that the UPF may generate a handover indication message upon determining that a specific event has occurred in the OT network. The UPF may send the handover indication information to the RAN via a general packet radio service tunneling protocol (general packet radio service tunneling protocol for the user plane, GTP-U) at the user plane, in other words, the handover indication information may be GTP-U type information. For example, the handover indication information may be carried by a field of the next extended message header type (next extension header type) in the GTP-U. For example, the field of the next extension message header type of the GTP-U may be a PDU session extension (PDU session container) field, which may carry the second QoS parameter. For example, this field may contain a second QoS parameter and traffic QFI. The handover indication information is used to instruct the RAN to handover the first QoS parameter to the second QoS parameter.

Step 311: the RAN switches the first QoS parameter to a second QoS parameter.

For example, the RAN switches the first QoS parameter to the second QoS parameter according to the switching instruction information.

Step 312: the RAN schedules the data flow using the second QoS parameters.

Step 311 and step 312 may be described with reference to step 206 shown in fig. 2.

Step 313: the UPF sends a handover notification to the SMF.

The handover notification may refer to the description of the fourth indication information in the method of fig. 2.

The handoff notification may be used to notify the SMF that the first QoS parameter has been handed off to the second QoS parameter.

It should be understood that the numbering of the steps in this application is not limiting as to the timing of the execution of the steps. For example, step 313 may be performed after step 310, after step 312, or simultaneously with steps 311-312. The present application is not limited in this regard.

Referring to the description of the first alternative scenario in step 206 shown in FIG. 2, the method may further comprise the steps of:

step 314: the UPF detects a specific event.

It should be appreciated that the detection of a particular event by the UPF herein may be the detection of whether the particular event is resumed. For example, when the UPF detects that the signal-to-noise ratio is greater than a certain threshold, or the channel usage rate is less than a certain threshold, or the channel service quality is greater than a certain threshold, or the packet loss rate is less than a certain threshold, it may be determined that the data transmission state in the OT network has been restored to a normal state, that is, that a specific event in the OT network has been restored.

Step 315: the UPF sends handover indication information to the RAN.

The handover indication information may refer to the description of the second indication information in the method of fig. 2.

It should be appreciated that the handover indication information may be used to instruct the RAN to handover the second QoS parameter to the first QoS parameter.

The handover indication information may be GTP-U type information.

Step 316: the UPF sends a handover notification to the SMF.

The handover notification may refer to the description of the handover notification in the method of fig. 2. The handoff notification may be used to notify the SMF that a QoS handoff event has occurred, i.e., that the second QoS parameter has been switched to the first QoS parameter.

Step 317: the RAN schedules the data flow using the first QoS parameters.

In connection with the method shown in fig. 2, the present application provides a method of a wireless scheduling method, as shown in fig. 4, where the method shown in the figure is described by taking an OT network scenario as an example. Wherein, the data flow in the method shown in the figure may be the first data flow in fig. 2, the SMF may be the first network element in the method shown in fig. 2, the RAN may be the access network device in the method shown in fig. 2, the UPF may be the user plane function network element in the method shown in fig. 2, and the method may include the following steps:

Step 401: the CPE sends a session establishment request to the SMF.

Step 402: the SMF generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter.

Step 403: the SMF sends the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second QoS parameter to the UPF.

Step 404: the SMF sends the first QoS parameter, the second QoS parameter to the RAN.

Step 405: the RAN sends the first QoS parameters to the CPE.

Step 406: the session establishment is completed.

Step 407: the RAN schedules the data flow using the first QoS parameters.

Step 408: data packets are transmitted between the device and the PLC.

Step 409: the UPF detects a specific event.

The UPF can determine whether the network state satisfies the handover condition by detecting a specific event.

Steps 401 to 409 may refer to the descriptions of steps 301 to 309 shown in fig. 3, and are not repeated here.

Step 410: the UPF sends handover indication information to the RAN.

Accordingly, the RAN receives the handover indication information from the UPF.

It should be appreciated that the handover indication information may be used to instruct the RAN to handover the first QoS parameter to the second QoS parameter.

It should be noted that, the handover indication information is carried in a data packet to be scheduled, that is, the data packet includes the handover indication information, and the UPF sending the data packet to the RAN means that the UPF sends the handover indication information to the RAN.

Step 411: the RAN switches the first QoS parameter to a second QoS parameter.

Since the RAN receives the handover indication information in step 410, the RAN switches the first QoS parameter to the second QoS parameter.

Step 412: the RAN schedules the data packet using the second QoS parameter.

Step 411 and step 412 may be described with reference to step 206 shown in fig. 2.

Step 413: the UPF sends a handover notification to the SMF.

The handover notification may be described with reference to step 313 shown in fig. 3.

Also, this step may be performed after step 412, may be performed simultaneously with step 411, may be performed simultaneously with step 410, and is not limited in this application.

Referring to the second alternative scenario in step 206 shown in fig. 2, the method may further comprise the steps of:

step 414: the RAN schedules the data flow using the first QoS parameters.

For example, after completing scheduling of the current data packet, the RAN switches the second QoS parameter to the first QoS parameter, and schedules the data flow using the first QoS parameter.

That is, after completion of the execution of step 412, the RAN may autonomously switch QoS parameters for scheduling the data flow. For example, after the RAN switches the QoS parameters for the scheduled data flow to the second QoS parameters, the RAN automatically switches the QoS parameters to the first QoS parameters.

Step 415: the UPF sends a handover notification to the SMF.

The handover notification may refer to the description of the handover notification in the method of fig. 2. The handoff notification may be used to notify the SMF that a QoS handoff event has occurred and that the second QoS parameter has been switched to the first QoS parameter.

It will be appreciated that the UPF sending a handoff notification to the SMF is convenient to tell the SMF which QoS parameter is currently being used, in particular which QoS parameter. This step may facilitate the SMF to implement other functions, such as charging functions, etc., according to the QoS parameters currently in use.

The scheme realizes the scheduling of the service quality strategy aiming at the data packet. After the RAN finishes the scheduling of the data packets, the RAN can automatically resume the scheduling of other data packets in the data stream by using the first QoS parameters before switching to the second QoS parameters, does not need to wait for receiving the indication information and then resume the QoS parameters, and can further reduce the time delay.

The application also proposes a wireless scheduling method, as shown in fig. 5, which may include the following steps:

step 501: the first network element generates a first QoS parameter, a second QoS parameter, and a handoff condition corresponding to the second QoS parameter.

The first QoS parameter, the second QoS parameter, and the handover condition may be described with reference to step 201 in fig. 2, and will not be described herein.

Step 502: the access network device receives the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second QoS parameter from the first network element.

Step 503: the access network device schedules the first data flow using the first QoS parameter.

Step 504: and after the network state meets the switching condition, the access network equipment uses the second QoS parameter to schedule the first data flow.

Whether the network state meets the switching condition or not can be judged by the access network equipment. Illustratively, the access network device determines whether the network state satisfies the handover condition by detecting a specific event. It should be understood that the access network device detecting a specific event may be understood as the access network device determining whether the first condition is fulfilled. The access network device determining that the first condition is satisfied may be understood as that the access network device detects that a specific event occurs in the OT network. This step may refer to the description of the actions of the user plane function network element in step 205.

Optionally, the method may further include:

the access network device sends third indication information to the first network element.

Wherein the third indication information may comprise a cause value, which may be used to indicate a cause of the access network device scheduling the first data flow using the second QoS parameter, i.e. a cause of the access network device switching QoS parameters. For example, the reason value included in the third indication information may indicate that the reason why the access network device switches the QoS parameter is that the signal-to-noise ratio is greater than a preset threshold. Or, the reason why the access network device switches the QoS parameters is that the channel quality of service is less than a preset threshold. Or, the reason why the access network device switches the QoS parameter is that the packet loss rate is greater than a preset threshold. The present application is not limited in this regard. That is, the cause value may be a handover condition satisfied by the QoS parameter to be handed over.

It will be appreciated that the cause value may also be used to indicate a specific value of a parameter affecting the occurrence of this handover. For example, the switching condition satisfied by the switching is that the packet loss rate is greater than 5%, and the specific value affecting the parameters of the switching, namely the packet loss rate, is 8%. The present application is not limited in this regard.

In addition, the third indication information may also include a second QoS parameter.

One possible implementation, the method may further include, but is not limited to, the following:

first alternative case: in case the scheduling of the first data packet is completed using the second QoS parameter, the access network device schedules other data packets than the first data packet in the first data flow using the first QoS parameter.

That is, the access network device proactively switches the second QoS parameters for scheduling data packets in the data flow to the first QoS parameters and schedules the data flow using the first QoS parameters.

Second alternative case: the access network device may receive fourth indication information from the user plane function network element, and schedule the first data flow using the first QoS parameter according to the fourth indication information.

In other words, the access network device may wait to receive indication information for switching QoS parameters to switch QoS parameters.

In this method, it may be understood that the access network device may also switch the first QoS parameter to another QoS parameter, where the other QoS parameter may refer to the description of the sixth QoS parameter and the seventh QoS parameter in step 206 shown in fig. 2.

In the scheme, the first network element generates and sends the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second QoS parameter to the access network equipment, and the access network equipment can autonomously detect the specific event. When a specific event occurs, the access network device can autonomously detect the occurrence of the specific event and switch the QoS parameters, so that the quick switching of the QoS parameters is realized. The method of the embodiment can further improve the switching efficiency of QoS parameters, thereby further ensuring the reliable transmission of the air interface.

In connection with the method shown in fig. 5, the present application provides a method of a wireless scheduling method, as shown in fig. 6, where the method shown in the figure is described by taking an OT network scenario as an example. Wherein, the data flow in the method shown in the figure may be the first data flow in fig. 5, the SMF may be the first network element in the method shown in fig. 5, the RAN may be the access network device in the method shown in fig. 5, the UPF may be the user plane function network element in the method shown in fig. 5, and the method may include the following steps:

step 601: the CPE sends a session establishment request to the SMF.

Step 602: the SMF generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter.

It should be understood that steps 601 and 602 may refer to the descriptions of steps 301 and 302 shown in fig. 3.

Step 603: the SMF sends the first QoS parameter, the second QoS parameter and the switching condition corresponding to the second QoS parameter to the RAN.

This step may be described with reference to step 303 shown in fig. 3.

Step 604: the session establishment is completed.

Specifically, the session is the session that the CPE requests to establish in step 601.

Wherein the CPE is connected to at least one device (e.g., an IO device), and the at least one device can transmit data with the PLC after the session establishment is completed.

Step 605: the RAN schedules the data flow using the first QoS parameters.

It should be understood that steps 604-605 may be described with reference to steps 306-307 shown in fig. 3.

Step 606: the RAN detects a specific event.

It should be understood that step 606 may refer to the actions of the UPF in step 309 shown in fig. 3, and that the difference between step 309 and step 606 is only that the subject of the detection is performed, i.e. the UPF detects a specific event in step 309, whereas the RAN detects a specific event in step 606, and the logic of detecting a specific event is consistent.

Step 607: the RAN switches the first QoS parameter to a second QoS parameter.

Step 608: the RAN schedules the data flow using the second QoS parameters.

It should be understood that steps 607 and 608 may refer to the description of steps 311 and 312 shown in fig. 3.

Step 609: the RAN sends a handover notification to the SMF.

The handover notification may refer to the description of the third indication information in the method of fig. 5.

For example, the handoff notification may contain an identification of the second QoS parameter. For example, the identification of the second QoS parameter may be an index (reference) of the second QoS parameter.

Optionally, the handover notification may further include a cause value that triggers the handover. The cause value may refer to the description of the cause value in fig. 5.

Step 610: the RAN schedules the first data flow using the first QoS parameter.

In a possible implementation, referring to the first alternative case in step 504 shown in fig. 5, this step includes: after scheduling the data flow using the second QoS parameters, the RAN autonomously alters the QoS parameters in step 608. I.e. the RAN schedules the data flow using the first QoS parameters.

In a possible implementation, referring to the second alternative case in step 504 shown in fig. 5, the step includes: the RAN receives fourth indication information from the user plane function network element, and the access network equipment uses the first QoS parameter to schedule the first data flow according to the fourth indication information. That is, the RAN switches the QoS parameters currently used according to the indication information.

In the above several possible implementations, the RAN may switch the second QoS parameter to another QoS parameter different from the first QoS parameter, and the other QoS parameters herein may refer to the description of the sixth QoS parameter and the seventh QoS parameter in step 206 shown in fig. 2, which is not repeated.

Step 611: the RAN sends a handover notification to the SMF.

The handover notification is used to inform the SMF that a handover event has occurred. It should be appreciated that step 611 may refer to the description of step 316 shown in fig. 3.

According to the scheme, the RAN autonomously detects a specific event and rapidly switches the QoS parameters, so that the time delay generated by multi-instruction interaction when the RAN switches the QoS parameters according to the indication information can be further shortened. The scheme further improves the efficiency of switching QoS parameters and can ensure the reliable transmission of the air interface.

In the above solution, only one CPE is included in the OT network as an example, and it should be understood that the number of CPEs in the OT network is not limited to this. Illustratively, a plurality of CPEs may be included in the OT network, and an emergency Stop event (E-Stop) button may also be included. The above method is equally applicable, and the present application is not limited thereto.

The various embodiments described herein may be separate solutions or may be combined according to inherent logic, which fall within the scope of the present application.

In the embodiments provided in the present application, the methods provided in the embodiments of the present application are described from the perspective of interaction between the respective devices. In order to implement the functions in the methods provided in the embodiments of the present application, the network device or the terminal device may include a hardware structure and/or a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

The division of the modules in the embodiment of the present application is schematic, which is merely a logic function division, and other division manners may be implemented in practice. In addition, each functional module in the embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules.

Fig. 7 is a schematic diagram of a communication device according to an embodiment of the present application, which is the same as the above concept.

The communication device comprises a processing module 701, a receiving module 702 and a transmitting module 703. The processing module 701 is configured to implement processing of data by the communication device. The receiving module 702 is configured to receive contents of a communication device and other units or network elements, and the sending module 703 is configured to receive contents of a communication device and other units or network elements. It should be appreciated that the processing module 701 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component (alternatively referred to as a processing circuit), and the receiving module 702 may be implemented by a receiver or a receiver-related circuit component. The transmit module 703 may be implemented by a transmitter or transmitter related circuit components.

The communication device may be a communication device apparatus, a chip applied in the communication device apparatus, or other combination devices, components, etc. having the functions of the communication device apparatus.

The communication device may be an SMF or a session management function device of any of fig. 3 to 6, a UPF or a user plane function device of any of fig. 3 to 6, or a RAN or an access network device of any of fig. 3 to 6, for example.

When the communication device is a UPF or a user plane function device, the receiving module 702 is configured to receive QoS parameters and handover conditions from the session management function device (e.g. step 204 in fig. 2, step 303 in fig. 3, step 403 in fig. 4); the sending module 703 is configured to send a data packet to the PLC (e.g. step 308 in fig. 3, step 408 in fig. 4); the processing module 701 is configured to detect a specific event (e.g., step 309 in fig. 3, step 409 in fig. 4); the sending module 703 is configured to send handover indication information (e.g. step 205 in fig. 2, step 310 in fig. 3, step 410 in fig. 4) to the RAN according to the result of the specific event (or whether the network status satisfies the handover condition); the sending module 703 is configured to send a handover notification to the SMF (e.g. step 316 in fig. 3, step 413 in fig. 4).

Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

When the communication device is an SMF or session management function device, the processing module 701 is configured to generate QoS parameters and handover conditions (e.g. step 201 in fig. 2, step 302 in fig. 3, step 402 in fig. 4, step 501 in fig. 5, step 602 in fig. 6); the sending module 703 is configured to send QoS parameters and handover conditions (e.g. step 202 and step 204 in fig. 2, step 303 and step 304 in fig. 3, step 403 and step 404 in fig. 4, step 502 in fig. 5, step 603 in fig. 6) to the RAN and the UPF; the receiving module 702 is configured to receive a handover notification (e.g. step 313 in fig. 3, step 413 in fig. 4, step 609 in fig. 6).

When the communication device is a RAN, the receiving module 702 is configured to receive QoS parameters (e.g., step 202 in fig. 2, step 304 in fig. 3, step 404 in fig. 4, step 502 in fig. 5, step 603 in fig. 6); the sending module 703 is configured to send a handover notification to the SMF (e.g. step 609 in fig. 6).

Fig. 8 is a schematic diagram of another communication device according to an embodiment of the present application, where the communication device includes: a processor 801, a communication interface 802, and a memory 803. Wherein the processor 801, the communication interface 802, and the memory 803 may be interconnected by a bus 804; bus 804 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus 804 may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one line is shown in fig. 8, but not only one bus or one type of bus. The processor 801 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP. The processor may further comprise a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (Generic Array Logic, GAL), or any combination thereof. The memory 803 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache.

The communication device may be an SMF or a session management function device of any of fig. 3 to 6, a UPF or a user plane function device of any of fig. 3 to 6, a terminal device (a device or CPE of fig. 3 to 6) of any of fig. 3 to 6, or a RAN or access network device of any of fig. 3 to 6, for example. The processor 801 is configured to implement a data processing operation of the communication apparatus, and the communication interface 802 is configured to implement a receiving operation and a transmitting operation of the communication apparatus.

When the communication device is a UPF or a user plane function device, the communication interface 802 is configured to receive QoS parameters and handover conditions from the session management function device (e.g., step 204 in fig. 2, step 303 in fig. 3, step 403 in fig. 4); the communication interface 802 is used to send data packets to the PLC (e.g., step 308 in fig. 3, step 408 in fig. 4); the processor 801 is configured to detect a specific event (e.g., step 309 of fig. 3, step 409 of fig. 4); the communication interface 802 is configured to send handover indication information (step 205 in fig. 2, for example, step 310 in fig. 3, step 410 in fig. 4) to the RAN according to the result of the specific event (or whether the network status satisfies the handover condition); the communication interface 802 is configured to send a handover notification to the SMF (e.g., step 316 in fig. 3, step 413 in fig. 4).

When the communication device is an SMF or session management function device, the processor 801 is configured to generate QoS parameters and handover conditions (e.g., step 201 in fig. 2, step 302 in fig. 3, step 402 in fig. 4, step 501 in fig. 5, step 602 in fig. 6); the communication interface 802 is configured to send QoS parameters and handover conditions (e.g., step 202 and step 204 in fig. 2, step 303 and step 304 in fig. 3, step 403 and step 404 in fig. 4, step 502 in fig. 5, step 603 in fig. 6) to the RAN and the UPF; the communication interface 802 is configured to receive a handover notification (e.g., step 313 in fig. 3, step 413 in fig. 4, step 609 in fig. 6).

When the communication device is a RAN, the communication interface 802 is configured to receive QoS parameters (e.g., step 202 in fig. 2, step 304 in fig. 3, step 404 in fig. 4, step 502 in fig. 5, step 603 in fig. 6); the communication interface 802 is used to send a handoff notification to the SMF (e.g., step 609 in fig. 6).

The embodiment of the application provides a communication system, which comprises the foregoing user plane function device (or UPF) and session management function device (or SMF) and access network equipment (or RAN), where the user plane function device (or UPF) performs a method performed by the UPF or the user plane function device in any of the embodiments shown in fig. 3 to 6, the session management function device (or SMF) performs a method performed by the SMF in the embodiment shown in fig. 3 to 6, and the access network equipment (or RAN) performs a method performed by the RAN or the access network equipment in any of the embodiments shown in fig. 3 to 6.

The present application further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, where the computer may implement a procedure related to SMF in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment, or implement a procedure related to UPF in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment, or implement a procedure related to RAN in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment.

The present application further provides a computer program product, where the computer program product is configured to store a computer program, where the computer may implement a procedure related to SMF in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment, or the computer may implement a procedure related to UPF in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment, or the computer may implement a procedure related to RAN in any one of the embodiments shown in fig. 3 to 6 provided by the foregoing method embodiment.

The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory to perform the corresponding operations and/or flows provided by UDM, AF, UPF, SMF or the terminal device in the method for registering with multiple networks provided herein. Optionally, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further comprises a communication interface, and the processor is connected to the communication interface. The communication interface is used for receiving the processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, interface circuitry, output circuitry, input circuitry, pins, or related circuitry, etc. on the chip. The processor may also be embodied as processing circuitry or logic circuitry.

The chip may be replaced by a chip system, and will not be described herein.

The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. The object of the present embodiment can be achieved by actually selecting some or all of the units therein.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In the embodiment of the application, the user equipment or the access network equipment comprises a hardware layer, an operating system layer running on the hardware layer and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like. The embodiment of the present application is not particularly limited to a specific structure of the execution body of the method provided in the embodiment of the present application, as long as the execution body of the method provided in the embodiment of the present application can communicate with the method provided in the embodiment of the present application by executing a program recorded with a code of the method provided in the embodiment of the present application, and for example, the execution body of the method provided in the embodiment of the present application may be a user equipment or an access network device, or a functional module in the user equipment or the access network device that can call the program and execute the program.

Furthermore, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape, etc.), optical disks (e.g., compact Disk (CD), digital versatile disk (digital versatile disc, DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable storage medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

The embodiments shown above are not particularly limited to the specific structure of the execution body of the method provided in the embodiments of the present application, as long as the communication can be performed by the method provided in the embodiments of the present application by running the program recorded with the code of the method provided in the embodiments of the present application, and for example, the execution body of the method provided in the embodiments of the present application may be a terminal device or a core network device, or a functional module in the terminal device or the core network device that can call the program and execute the program.

In order to facilitate understanding of the embodiments of the present application, the following description is made.

First, the first, second, and various numerical numbers shown in the present application are for convenience of description only, and are not intended to limit the scope of the embodiments of the present application for distinguishing objects. For example, distinguishing between different messages, etc. Rather than to describe a particular order or sequence. It is to be understood that the objects so described may be interchanged under appropriate circumstances so as to be able to describe aspects other than the embodiments of the application.

Second, in this application, "preset" may include a predefined, e.g., protocol definition. The "pre-defining" may be implemented by pre-storing a corresponding code, table, or other manner that may be used to indicate the relevant information in a device (including, for example, a terminal device or a core network device), which is not limited to a specific implementation manner.

Third, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the field of communications, and may include, for example, a 5G protocol, a New Radio (NR) protocol, and related protocols applied in future communication systems, which are not limited in this application.

Furthermore, the term "include" and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

Although the present application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the present application. It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A wireless scheduling method, comprising:

The access network equipment receives a first quality of service (QoS) parameter and a second QoS parameter from a first network element;

the access network device schedules a first data flow using the first QoS parameter;

the access network equipment receives first indication information;

and the access network equipment uses the second QoS parameters to schedule the first data flow according to the first indication information.

2. The method of claim 1, wherein the access network device receives the first indication information, comprising:

the access network equipment receives the first data stream, wherein the first data stream comprises a first data packet, and the first data packet comprises the first indication information.

3. The method of claim 2, wherein the step of determining the position of the substrate comprises,

the access network device uses the second QoS parameter to schedule the first data flow according to the first indication information, including: the access network equipment uses the second QoS parameter to schedule the first data packet according to the first indication information;

the method further comprises the steps of:

the access network device uses the first QoS parameter to schedule other data packets in the first data flow than the first data packet.

4. The method of claim 1, wherein the access network device receives the first indication information, comprising:

the access network device receives the first indication information from a user plane function network element.

5. The method of claim 4, wherein after the access network device schedules the first data flow using the second QoS parameter according to the first indication information, the method further comprises:

the access network equipment receives second indication information from the user plane function network element;

and the access network equipment uses the first QoS parameter to schedule the first data flow according to the second indication information.

6. The method of claim 5, wherein the second indication information is general packet radio service user plane type information.

7. The method according to any one of claims 1 to 6, wherein the first indication information is general packet radio service user plane type information.

8. A wireless scheduling method, comprising:

the access network equipment receives a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter from a first network element;

and after the network state meets the switching condition, the access network equipment uses the second QoS parameter to schedule the first data flow.

9. The method of claim 8, wherein the method further comprises:

the access network device sends third indication information to the first network element, wherein the third indication information comprises a cause value, and the cause value is used for indicating a cause of the access network device for scheduling the first data flow by using the second QoS parameter.

10. The method according to claim 8 or 9, wherein said access network device scheduling said first data flow using said second QoS parameter after said network state satisfies said handover condition, comprising: after the access network device meets the switching condition, scheduling a first data packet of the first data flow by using the second QoS parameter;

the method further comprises the steps of:

11. The method according to claim 8 or 9, wherein after the access network device schedules the first data flow using the second QoS parameter, the method further comprises:

The access network equipment receives fourth indication information from the user plane function network element;

and the access network equipment uses the first QoS parameter to schedule the first data flow according to the fourth indication information.

12. The method according to any one of claims 8 to 11, wherein the handover condition comprises at least one of: the signal-to-noise ratio is less than or equal to a first threshold, the channel usage is greater than or equal to a second threshold, the channel quality of service is less than or equal to a third threshold, and the packet loss rate is greater than or equal to a fourth threshold.

13. A wireless scheduling method, comprising:

the first network element generates a first QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter;

the first network element sends the first QoS parameter and the second QoS parameter to access network equipment, and sends the first QoS parameter, the second QoS parameter and the switching condition to the user plane function network element;

or alternatively, the process may be performed,

the first network element sends the first QoS parameter, the second QoS parameter and the handover condition to an access network device, and sends the first QoS parameter and the second QoS parameter to the user plane functional network element.

14. The method of claim 13, wherein the first network element comprises a session management function network element, the method further comprising:

the session management function network element receives fourth indication information from the user plane function network element;

the session management function network element performs a first action according to the fourth indication information, wherein the first action comprises at least one of charging or notifying the terminal equipment of switching of QoS parameters.

15. The method according to claim 13 or 14, wherein the handover condition comprises at least one of: the signal-to-noise ratio is less than or equal to a first threshold, the channel usage is greater than or equal to a second threshold, the channel quality of service is less than or equal to a third threshold, and the packet loss rate is greater than or equal to a fourth threshold.

16. A wireless scheduling method, comprising:

the user plane function network element receives a first quality of service QoS parameter, a second QoS parameter and a switching condition corresponding to the second QoS parameter from a first network element, wherein the first QoS parameter and the second QoS parameter are used for scheduling a first data flow; after the network state meets the switching condition, the user plane function network element sends first indication information to the access network device, wherein the first indication information is used for indicating and scheduling the QoS parameters of the first data flow, and the first QoS parameters are switched to the second QoS parameters.

17. The method of claim 16, wherein the user plane function network element sends the first indication information to the access network device, comprising:

the user plane function network element sends the first data stream to access network equipment, wherein the first data stream comprises a first data packet, and the user plane function network element carries the first indication information through the first data packet.

18. The method according to claim 16 or 17, characterized in that the method further comprises:

and after the network state does not meet the switching condition, the user plane function network element sends second indication information to the access network equipment, wherein the second indication information is used for indicating and scheduling the QoS parameters of the first data flow, and the second QoS parameters are switched to the first QoS parameters.

19. The method of claim 18, wherein the second indication information is general packet radio service user plane type information.

20. The method according to any of claims 16 to 19, wherein the first indication information is general packet radio service user plane type information.

21. The method according to any one of claims 16 to 20, further comprising:

And the user plane function network element sends fourth indication information, wherein the fourth indication information is used for indicating that the QoS parameters of the first data flow are scheduled to be switched from the second QoS parameters to the first QoS parameters.

22. The method according to any one of claims 16 to 21, wherein the handover condition comprises at least one of: the signal-to-noise ratio is less than or equal to a first threshold, the channel usage is greater than or equal to a second threshold, the channel quality of service is less than or equal to a third threshold, and the packet loss rate is greater than or equal to a fourth threshold.

23. A communication device comprising a transceiver unit and a processing unit, the communication device being adapted to perform the method of any of claims 1 to 7 or to perform the method of any of claims 8 to 12.

24. A communication device comprising a transceiver unit and a processing unit, the communication device being adapted to perform the method of any of claims 13 to 15.

25. A communication device comprising a transceiver unit and a processing unit, the communication device being adapted to perform the method of any of claims 16 to 22.

26. A communication system comprising an access network device performing the method of any one of claims 1 to 7 and a user plane functional network element performing the method of any one of claims 16 to 22.

27. A communication system according to claim 26, characterized in that the communication system comprises a first network element, which performs the method according to any of claims 13 to 15.

28. A computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 7, or causes the computer to perform the method of any one of claims 8 to 12, or causes the computer to perform the method of any one of claims 13 to 15, or any one of claims 16 to 22.

29. A computer program product which, when executed on a computer, causes the computer to perform the method of any one of claims 1 to 7, or causes the computer to perform the method of any one of claims 8 to 12, or causes the computer to perform the method of any one of claims 13 to 15, or the method of any one of claims 16 to 22.

30. A chip comprising a processor and a communication interface, the processor being configured to read instructions to perform the method of any one of claims 1 to 7, or to cause the computer to perform the method of any one of claims 8 to 12, or to cause the computer to perform the method of any one of claims 13 to 15, or to perform the method of any one of claims 16 to 22.