WO2024000445A1

WO2024000445A1 - Qos flow control method and apparatus, and computer storage medium

Info

Publication number: WO2024000445A1
Application number: PCT/CN2022/102934
Authority: WO
Inventors: 吴锦花; 沈洋; 王德乾; 刘建宁; 毛玉欣
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-06-30
Filing date: 2022-06-30
Publication date: 2024-01-04
Also published as: CN117643100A

Abstract

Provided in the present disclosure are a QoS flow control method and apparatus, and a computer storage medium. The control method can be applied to a 5G system. The method may comprise: a first core network functional entity receiving terminal status information from an application function entity (S201), wherein the terminal status information is used for representing the power consumption status of a terminal; and the first core network functional entity executing one of the following: executing, according to the terminal status information, QoS updating on a QoS flow associated with the terminal (S202); and sending the terminal status information to a second core network functional entity, wherein the terminal status information is used for the second core network functional entity to execute QoS updating on a QoS flow (S203). In the present disclosure, an application function entity provides terminal status information of a terminal to a first core network functional entity, such that the first core network functional entity can control a QoS flow according to the power consumption status of the terminal, so as to guarantee a service requirement and the user experience.

Description

A QoS flow control method, device and computer storage medium

Technical field

The present disclosure relates to the field of wireless communication technology, and in particular, to a QoS flow control method, device and computer storage medium.

Background technique

In the fifth generation mobile networks (5G) technology, mobile media services, cloud extended reality (XR), cloud games, video-based machine or drone remote control, etc. are expected to provide 5G network Contribute more and more traffic.

Currently, because XR and media services have the characteristics of high throughput, low latency, and high reliability requirements, they require high power consumption on the terminal side, and the battery power of the terminal may affect the user experience.

Then, how to match business traffic characteristics and terminal energy consumption management is an urgent problem that needs to be solved.

Contents of the invention

The present disclosure provides a QoS flow control method, device and computer storage medium to match business traffic characteristics and terminal energy consumption management, thereby ensuring business requirements and user experience.

According to the first aspect of the present disclosure, a quality of service (QoS) flow control method is provided, which can be applied to the first core network functional entity in the communication system, such as policy control function (PCF) entity. The method may include: the first core network functional entity receives terminal status information (UE status information) from an application function (AF) entity, and the terminal status information is used to represent the power consumption status of the terminal; the first core network functional entity Perform one of the following: perform QoS update on the QoS flow associated with the terminal according to the terminal status information; send the terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.

In this disclosure, the first core network functional entity may be a PCF entity (can also be described as a first PCF entity), and the second core network functional entity may be other PCF entities (can also be described as a second PCF entity). The second PCF entity can be understood as one or more PCF entities.

In some possible implementations, the QoS flow includes at least one of the following: session QoS flow; service data flow QoS flow.

In some possible implementations, the terminal status information includes at least one of the following: battery power; battery life; power supply mode; CPU load; and terminal overheating status.

In some possible implementations, the QoS flow is a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow, and the QoS parameters of the QoS flow include: guaranteed flow bit rate (guaranteed flow bit rate, GFBR) and/or maximum flow bit rate (maximum flow bit rate, MFBR).

In some possible implementations, the first core network functional entity performs QoS updates on the QoS flow based on the terminal status information, including: the first core network functional entity lowers or increases the GFBR based on the terminal status information.

In some possible implementations, the above method also includes: the first core network functional entity sends MFBR to the third core network functional entity, and the MFBR is used by the third core network functional entity to perform QoS update on the downlink GBR QoS flow; and/or , the first core network functional entity sends the MFBR to the access network functional entity, and the MFBR is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.

In the present disclosure, the third core network function entity may be a user plan function (UPF) entity.

In some possible implementations, the QoS flow is a non-GBR QoS flow, and the QoS parameters of the QoS flow include: aggregate maximum bit rate (aggregate maximum bit rate, AMBR).

In some possible implementations, the first core network functional entity performs QoS updates on the QoS flow based on the terminal status information, including: the first core network functional entity reduces or increases AMBR based on the terminal status information.

In some possible implementations, AMBR includes at least one of the following: AMBR per terminal, AMBR per session.

In some possible implementations, in response to the AMBR including per-session AMBR, the above method further includes: the first core network functional entity sends the per-session AMBR to the third core network functional entity, and the per-session AMBR is used for the third core network functional entity. The core network functional entity performs QoS updates on the uplink and/or downlink session QoS flows; or, the first core network functional entity sends the AMBR of each session to the terminal, and the AMBR of each session is used by the terminal to perform protocol data based on the non-GBR QoS flow. Upstream rate limit for protocol data unit (PDU) sessions.

In some possible implementations, in response to the AMBR including the AMBR of each terminal, the above method further includes: the first core network functional entity sends the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used for the access network function. The entity performs QoS updates for each terminal's upstream and/or downstream non-GBR QoS flows.

In some possible implementations, the QoS flow is a GBR QoS flow or a non-GBR QoS flow, and the QoS parameters of the QoS flow include: maximum bit rate (maximum bit rate, MBR) per slice per terminal.

In some possible implementations, in response to the QoS parameter including the MBR of each terminal and each slice, the above method further includes: the first core network functional entity sends the MBR of each terminal and each slice to the access network functional entity, and the MBR of each terminal and each slice is sent to the access network functional entity. MBR is used by the access network functional entity to perform QoS updates on the PDU session QoS flow corresponding to the terminal's single network slice selection assistance information (single network slice selection assistance information, S-NSSAI).

In some possible implementations, the application function entity is a trusted application function entity; the first core network function entity receives terminal status information from the application function entity, including one of the following: the first core network function entity receives the terminal status information sent by the application function entity The terminal status information; the first core network functional entity receives the terminal status information sent by the time sensitive communication and time synchronization function (TSCTSF) entity, and the terminal status information is sent by the application function entity to the TSCTSF entity.

In some possible implementations, the application function entity is an untrusted application function entity; the first core network function entity receives terminal status information from the application function entity, including one of the following: the first core network function entity receives the network opening function The terminal status information sent by the (network exposure function, NEF) entity, the terminal status information is sent to the NEF entity by the application function entity; the first core network function entity receives the terminal status information sent by the TSCTSF entity, the terminal status information is sent by the application function entity Sent to the TSCTSF entity through the NEF entity.

In some possible implementations, the first core network functional entity sends the terminal status information to the second core network functional entity, including: the first core network functional entity queries the subscription event and determines the first event associated with the terminal status information; When an event satisfies event reporting conditions, the first core network functional entity sends terminal status information to the second core network functional entity.

According to a second aspect of the present disclosure, a QoS flow control method is provided, which method can be applied to an application function entity in a communication system. The method includes: an application function entity receives terminal status information sent by a terminal, and the terminal status information is used to represent the power consumption status of the terminal; the application function entity sends terminal status information to a first core network functional entity, and the terminal status information is also used for the first The core network functional entity performs QoS updates on the QoS flows associated with the terminal.

In some possible implementations, the QoS flow includes at least one of the following: QoS flow of the session; QoS flow of the service data flow.

In some possible implementations, the application function entity is a trusted application function entity; the application function entity sends terminal status information to the first core network function entity, including one of the following: the application function entity sends terminal status information to the first core network function entity Status information: the application function entity sends terminal status information to the TSCTSF entity, and the terminal status information is also used by the TSCTSF entity to send to the first core network function entity.

In some possible implementations, the application function entity is an untrusted application function entity; the application function entity sends terminal status information to the first core network function entity, including: terminal status information sent by the application function entity to the NEF entity, terminal status The information is also used by the NEF entity to send to the first core network functional entity, or the terminal status information is also used by the NEF entity to send to the first core network functional entity through the TSCTSF entity.

According to a third aspect of the present disclosure, a QoS flow control device is provided. The control device may be the first core network functional entity in the communication system or the chip or system-on-chip of the first core network functional entity. It may also be the first core network functional entity. The functional modules in the network functional entity are used to implement the methods described in the above embodiments. The control device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module configured to receive terminal status information (UE status information) from the application function entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to, based on the terminal status information, The QoS flow associated with the terminal performs QoS update; the sending module is configured to send terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.

In this disclosure, the first core network functional entity may be a PCF entity, and the second core network functional entity may be other PCF entities.

In some possible implementations, the QoS flow is a GBR QoS flow, and the QoS parameters of the QoS flow include: GFBR and/or MFBR.

In some possible implementations, the processing module is configured to reduce or increase the GFBR according to the terminal status information.

In some possible implementations, the sending module is configured to send the MFBR to the third core network functional entity. The MFBR is used by the third core network functional entity to perform QoS updates on the downlink GBR QoS flow; and/or to the access network function. The entity sends MFBR, which is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.

In the present disclosure, the third core network functional entity may be a UPF entity.

In some possible implementations, the QoS flow is a non-GBR QoS flow, and the QoS parameters of the QoS flow include: AMBR.

In some possible implementations, the processing module is configured to reduce or increase the AMBR according to the terminal status information.

In some possible implementations, in response to the AMBR including a per-session AMBR, the sending module is configured to send the per-session AMBR to the third core network functional entity, and the per-session AMBR is used for the third core network functional entity pair Perform QoS updates for upstream and/or downlink session QoS flows; or, send per-session AMBR to the terminal, and the per-session AMBR is used by the terminal to perform PDU session-based upstream rate limiting on non-GBR QoS flows.

In some possible implementations, in response to the AMBR including the AMBR of each terminal, the sending module is configured to send the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used by the access network functional entity for each terminal. Perform QoS updates for upstream and/or downstream non-GBR QoS flows.

In some possible implementations, the QoS flow is a GBR QoS flow or a non-GBR QoS flow, and the QoS parameters of the QoS flow include: MBR per terminal per slice.

In some possible implementations, in response to the QoS parameter including the MBR per terminal per slice, the sending module is configured to send the MBR per terminal per slice to the access network functional entity, and the MBR per terminal per slice is used for access. The network function entity performs QoS updates on the PDU session QoS flow corresponding to the terminal's single network slice selection auxiliary information S-NSSAI.

In some possible implementations, the application function entity is a trusted application function entity; the receiving module is configured to perform one of the following: receiving terminal status information sent by the application function entity; receiving terminal status information sent by the TSCTSF entity, terminal status The information is sent by the application function entity to the TSCTSF entity.

In some possible implementations, the application function entity is an untrusted application function entity; the receiving module is configured to perform one of the following: receiving terminal status information sent by the NEF entity, and the terminal status information is sent by the application function entity to the NEF entity Receive the terminal status information sent by the TSCTSF entity. The terminal status information is sent by the application function entity to the TSCTSF entity through the NEF entity.

In some possible implementations, the processing module is configured to query the subscription event and determine the first event associated with the terminal status information; the sending module is configured to send the message to the second core when the first event satisfies the event reporting condition. The network function entity sends terminal status information.

According to the fourth aspect of the present disclosure, a QoS flow control device is provided. The control device can be an application function entity in a communication system or a chip or system-on-chip of an application function entity. It can also be an application function entity used to implement each of the above. Functional module of the method described in the embodiment. The control device can realize the functions performed by the application function entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The control device may include: a receiving module configured to receive terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal; a sending module configured to send the terminal status information to the first core network functional entity, The terminal status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.

In some possible implementations, the application function entity is a trusted application function entity; the sending module is configured to perform one of the following: sending terminal status information to the first core network functional entity; sending terminal status information to the TSCTSF entity. The status information is also used by the TSCTSF entity to send to the first core network functional entity.

In some possible implementations, the application function entity is an untrusted application function entity; the sending module is configured to send terminal status information to the NEF entity, and the terminal status information is also used by the NEF entity to send to the first core network function entity , or, the terminal status information is also used by the NEF entity to send to the first core network function entity through the TSCTSF entity.

According to a fifth aspect of the present disclosure, a communication device, such as a first core network functional entity, is provided. The communication device may include: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored on the memory to implement the above-mentioned first aspect and any possible implementation manner thereof. QoS flow control method.

According to a sixth aspect of the present disclosure, a communication device, such as a second core network functional entity, is provided. The communication device may include: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored on the memory to implement the above second aspect and any possible implementation manner thereof. QoS flow control method.

According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided. Instructions are stored in the computer-readable storage medium; when the instructions are run on a computer, they are used to perform the above-mentioned first to second aspects and any possible method thereof. The QoS flow control method described in the embodiment.

According to an eighth aspect of the present disclosure, a computer program or computer program product is provided. When the computer program product is executed on a computer, the computer implements QoS as described in the above first to second aspects and any possible implementation manner thereof. Flow control methods.

In the present disclosure, the terminal status information of the terminal is provided to the first core network functional entity (such as PCF) through the application function entity (ie, AF entity), so that the first core network functional entity can match the service traffic characteristics and terminal according to the terminal status information. Energy consumption management is to control QoS flow according to the power consumption status of the terminal to ensure business needs and user experience. Furthermore, the terminal status information provided by the application function entity is used as additional information for policy determination, which can reduce the use of wireless interface network resources, especially when resources are limited. Further, by providing the terminal status information of the terminal to the first core network functional entity through the application function entity, the use of network resources according to the capabilities of the UE can be supported. Further, the terminal status information of the terminal is provided to the first core network functional entity through the application function entity, so that the user's key applications are allowed to run in the power saving mode, thereby improving the user experience and extending the battery life. Completely closed.

It should be understood that the third to eighth aspects of the present disclosure are consistent with the technical solutions of the first to second aspects of the present disclosure, and the beneficial effects achieved by each aspect and corresponding feasible implementations are similar, and will not be described again.

Description of drawings

Figure 1 is an architectural schematic diagram of a 5G communication system in an embodiment of the present disclosure;

Figure 2 is a schematic flowchart of the implementation of the first QoS flow control method in an embodiment of the present disclosure;

Figure 3 is a schematic flowchart of an implementation process for performing QoS updates on GBR QoS flows in an embodiment of the present disclosure;

Figure 4 is a schematic flowchart of an implementation process for performing QoS updates on non-GBR QoS flows in an embodiment of the present disclosure;

Figure 5 is a schematic flowchart of the implementation of the second QoS flow control method in an embodiment of the present disclosure;

Figure 6 is a schematic structural diagram of a QoS flow control device in an embodiment of the present disclosure;

Figure 7 is a schematic structural diagram of a communication device in an embodiment of the present disclosure;

Figure 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with aspects of embodiments of the present disclosure as detailed in the appended claims.

The terminology used in the embodiments of the present disclosure is for the purpose of describing specific embodiments only and is not intended to limit the embodiments of the present disclosure. As used in the embodiments of the present disclosure and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms “first”, “second”, “third”, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, "first information" may also be called "second information", and similarly, "second information" may also be called "first information". Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining."

Further, in the description of the embodiments of the present disclosure, "and/or" is only an association relationship describing associated objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present disclosure, "plurality" may refer to two or more than two.

The technical solution of the embodiment of the present disclosure relates to the architecture of a communication system. The communication system may be a 5G communication system or a future evolution communication system. In the architecture of the communication system, there are terminals, access network functional entities (which can also be described as access network functional entities, access network elements, access network functional components, access network functional modules, etc.) and at least one core Network function (NF) entity (can also be described as core network equipment, core network element, core network functional component, core network functional module, etc.). At least one core network functional entity is located in the core network (ie 5GC). The terminal is used to report terminal status information (UE status information) used to indicate its own power consumption status to the first core network side; at least one core network functional entity has at least the following functions: according to the received terminal status information, the terminal associated The QoS flow performs QoS update; and, the terminal status information is sent to the next-level core network functional entity for the second core network functional entity to perform QoS update on the QoS flow. In practical applications, the above QoS flow is the QoS flow of the first service of the terminal. The first service may include XR service, mobile media service, etc., wherein XR service and mobile media service may also be called XRM service, or may be described as XR\M service.

In the following, the embodiments of the present disclosure will be explained and described, taking a 5G communication system as an example. It should be noted that the embodiments of the present disclosure are also applicable to any future evolution communication system after the 5G communication system, and the embodiments of the present disclosure do not specifically limit this.

Figure 1 is an architectural schematic diagram of a 5G communication system in an embodiment of the present disclosure. Referring to Figure 1, the above-mentioned 5G communication system 100 may include a 5G Radio Access Network (RAN) and a 5G Core Network (5GC). The 5G wireless access network may include next generation radio access network (NG RAN). NG RAN 101 communicates with the terminal (or terminal device) 102 through the Uu interface. The 5G core network may include: at least one core network functional entity mentioned above, such as access and mobility management function (AMF) entity 1031, SMF entity 1032, PCF entity 1033, UPF entity 1034, AF entity 1035, NEF entity 1036, TSCTSF entity 1037, etc. In the embodiment of the present disclosure, the above communication system may also include other network functional entities (which may also be called network elements, network devices, etc.), which are not specifically limited in the embodiment of the present disclosure.

It should be noted that in Figure 1, both the third-party (3rd) AF entity and the operator (operator) AF entity belong to AF entities. The difference is that third-party AF entities (such as instant messaging service servers, electronic payment service servers, etc.) are not controlled by the operator, while operator AF entities (such as the agent-call session control function in the IP multimedia system) proxy-call session control function, P-CSCF) entity) is controlled by the operator. Third-party AF entities need to pass NEF entities when interacting with PCF entities. The above operator AF entity can also be described as a trusted or trusted AF entity, and the above third party AF can also be described as an untrusted or untrusted AF entity.

In addition, in order to make the description more concise, in the subsequent description, the "entity" in each functional entity will be removed. For example, the PCF entity is abbreviated as PCF, and the SMF entity is abbreviated as SMF. Other entities are similar and will not be listed one by one.

In the embodiment of the present disclosure, in the above-mentioned 5G communication system 100, the following interfaces may be provided between each core network functional entity:

N3: Communication interface between UPF 1034 and NG RAN 101.

N4: The interface between SMF 1032 and UPF 1034, used to transfer information between the control plane and the user plane (user plan, UP), including controlling the delivery of UP-oriented forwarding rules, QoS control rules, traffic statistics rules, etc. Report UP information.

N2: The interface between AMF 1031 and NG RAN 101, used to transmit wireless bearer control information from the core network side to NG RAN 101, etc.

N1: The interface between AMF 1031 and terminal 102, has nothing to do with access, and is used to transmit QoS control rules to terminal 102, etc.

In Figure 1, between NEF, PCF, TSCTSF, AMF and SMF, the communication between any two entities can use service-oriented communication. For example, the interfaces Nnef and Npcf used for communication between NEF and PCF are both service-oriented interfaces. , similarly, the interfaces Naf, Ntsctsf, Namf and Nsmf are all service-oriented interfaces.

The above-mentioned terminal may be a terminal device with a wireless communication function and a wireless sensing function, and may also be called user equipment (UE). Terminals can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as aircraft, balloons, satellites, etc.). The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, or an industrial control (industrial control) ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. The terminal may also be a handheld device, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem with wireless communication functions and wireless sensing functions. Optionally, the terminal device can also be called by different names in different networks, for example: terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G communication system or terminals in future evolution communication systems, etc.

The above-mentioned access network functional entity may be a functional entity used by the access network side to support communication terminals to access the wireless communication system. For example, it can be the next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP), etc. in the 5G communication system.

It should be noted that in the communication system shown in FIG. 1 , each functional entity and interface are only exemplary, and not all functions of each functional entity are necessary when applied in the embodiments of the present disclosure. The functional entities of the access network and the core network may be physical physical devices or virtualized devices, which are not limited here. Of course, the communication system in the embodiment of the present disclosure may also include other devices not shown in Figure 1, which are not limited here.

In 5G networks, mobile media services, XR, cloud games, video-based machine or drone remote control, etc. are expected to contribute more and more traffic to 5G networks. Especially XR and media (extend reality and media, XRM) business. XRM business has the characteristics of high throughput, low latency, and high reliability requirements, and requires high power consumption on the terminal side. The battery power of the terminal may affect the user experience.

Currently, based on existing terminal implementations and considering service traffic characteristics, a terminal power saving enhancement solution has been defined in 3GPP. For example, the power saving mode of the terminal in different connection states (connection management, CM), such as the power saving mode of CM-IDLE (idle state) and the power saving mode of CM-CONNECTED (connected) in the RRC inactive state. Defines mobile initiated connection only (MICO) mode, extended discontinuous reception (extended DRX, eDRX) mode, etc. However, the above solutions are specially designed for IoT terminals with ultra-low power consumption. If these solutions are used on smartphones, the user experience will be greatly affected.

Therefore, how to match business traffic characteristics and terminal energy consumption management is an urgent problem that needs to be solved.

In the embodiments of the present disclosure, in the following embodiments, the terminal device in the communication system may be a UE as an example, the access network functional entity may be a base station as an example, the first core network functional entity may be a PCF as an example, and the second core network functional entity may be a PCF as an example. The network function entity may be other PCF as an example, the third core network function entity may be UPF as an example, and the application function entity may be AF as an example to describe the QoS flow control method proposed in the embodiment of the present disclosure. In the 5G communication system and its evolved versions, the terminal, access network functional entity, first core network functional entity, second core network functional entity, third core network functional entity and application functional entity may also have the same or similar functions. and other functional entities with connection relationships, which are not limited in the embodiments of the present disclosure.

In order to solve the above problem, in combination with the above communication system, embodiments of the present disclosure provide a QoS flow control method.

Figure 2 is a schematic flowchart of the implementation of the first QoS flow control method in an embodiment of the present disclosure. As shown in Figure 2, in this embodiment, the QoS flow control method is applied to the first core network functional entity (such as PCF ) side, the QoS flow control method may include S201 to S204.

S201, PCF receives terminal status information (UE status information) sent from the application function entity (such as AF).

The terminal status information is used to indicate the power consumption status of the UE. Exemplarily, the terminal status information includes one or more parameters related to the UE performance. For example, the UE status information may include at least one of the following: UE battery level, UE battery life, UE's power supply mode (powered mode), UE's CPU load, UE overheating status (UE overheating status). Of course, in this embodiment of the present disclosure, parameters related to UE power consumption may include other parameters. Here, the power supply mode of the UE may include: battery-powered mode (battery-powered) and power supply mode (mains/wall-powered). Here, the battery power supply mode refers to using the built-in battery of the UE to provide power, and the power supply mode refers to using a power adapter to connect to a power source such as a wall socket, a mobile socket, etc., to power the UE.

It should be understood that the registered UE can report its own terminal status information to the AF through the application layer, and then the AF reports it to the PCF.

In some possible implementations, the AF may, but is not limited to, send terminal status information to the PCF through the following paths.

In the first path, AF directly sends terminal status information to PCF. It can be understood that AF sends terminal status information to PCF through Naf and Npcf. At this time, AF is trusted AF.

In the second path, AF sends terminal status information to PCF through NEF. It can be understood that AF sends terminal status information to NEF through Naf and Nnef, and NEF sends terminal status information to PCF through Nnef and Npcf. At this time, AF is an untrusted AF.

In the third path, AF sends terminal status information to PCF through TSCTSF. It is understandable that AF sends terminal status information to TSCTSF through Naf and Ntsctsf, and TSCTSF sends terminal status information to PCF through Ntsctsf and Npcf. At this time, AF is a trusted AF, and the first service is a time-sensitive service.

In the fourth path, AF sends terminal status information to PCF through NEF and TSCTSF. It can be understood that AF sends the terminal status information to NEF through Naf and Nnef, and NEF sends the terminal status information to TSCTSF through Nnef and Ntsctsf. TSCTSF then sends the terminal status information to PCF through Ntsctsf and Npcf. At this time, AF is not Trusted AF, the first service is time-sensitive service.

It can be seen from the above first to fourth methods that for different AF types and/or first service types, one or more NFs can be set between the AF and the PCF, such as the above-mentioned NEF, TSCTSF, etc. Correspondingly, different transmission paths may exist for terminal status information. It should be noted that the above is only an example of the transmission path of the terminal status information, and does not limit the transmission method and transmission path of the terminal status information. The terminal status information can also be transmitted from the AF to the PCF using other paths.

Of course, with the evolution of communication systems, the above NF may be deployed in other situations, and the embodiments of the present disclosure do not specifically limit this.

In some possible implementations, when the AF is an untrusted AF, the AF can provide terminal status information to the NEF, and the terminal status information is carried in the AF request message. For example, the AF request message may include: NEF parameter creation request message (such as Nnef_ParameterProvision_Create Request), NEF parameter update request message (such as Nnef_ParameterProvision_Update Request), AF session resource request message (such as Nnef_AFsessionWithQoS_Create request), etc. NEF authorizes AF's request and performs related mapping. NEF then provides terminal status information to PCF. In an embodiment, in a multi-UE scenario, NEF can also provide terminal status information to one or more PCFs corresponding to the multi-UEs.

In an embodiment, NEF may send terminal status information to the corresponding PCF according to the UE's identity or group identity.

In another embodiment, PCF may subscribe to NEF for events associated with terminal status information. When the event meets the reporting conditions, PCF receives the terminal status information reported by NEF. Optionally, NEF can also report service QoS update information (Service QoS update) to PCF.

In some possible implementations, after receiving the terminal status information sent by the AF, NEF can also send the terminal status information to the user data register (user data repository, UDR) functional entity or unified data management (unified data management, UDM) ) functional entity, used as AMF associated parameter storage, SMF associated parameter storage or business characteristic parameter storage of application data.

After S201, the PCF may perform at least one of S202 to S203.

S202: The PCF performs QoS update on the QoS flow associated with the UE according to the terminal status information.

It can be understood that after receiving the terminal status information of the UE, the PCF can update the QoS flow associated with the UE according to the power consumption status of the UE.

Here, the QoS flow associated with the UE may be related to the first service. In this embodiment of the present disclosure, the first service may be an XRM service or an XRM service group.

In some possible implementations, the above-mentioned QoS flows may be of different granularities, for example, they may be session-specific (ie, session QoS flow) or service-oriented (eg, business data flow QoS flow). This is not the case in the embodiments of the present disclosure. Specific limitations.

It can be understood that the PCF can determine corresponding QoS parameters for one or more sessions of a service (ie, the first service) of the UE according to the terminal status information. Alternatively, the PCF may determine corresponding QoS parameters for a service of the UE (ie, the first service) based on the terminal status information. Here, "OK" can be described as "setting", "generating", "updating", etc.

S203: The PCF sends terminal status information to other PCFs, and the terminal status information is used by other PCFs to perform QoS updates on the QoS flow.

It should be understood that in a multi-UE scenario, different UEs may correspond to different PCFs. Then, when a PCF (can be recorded as PCF0) receives the terminal status information from the AF, it can provide the terminal status information to other PCFs (PCF 1, PCF 2, PCF 3,...) for other PCFs to execute such as The QoS update process described in S202 above.

In one embodiment, after receiving the terminal status information, PCF 0 can directly send it to other PCFs such as PCF 1, PCF 2, PCF 3, etc. Alternatively, other PCFs such as PCF 1, PCF 2, PCF 3, etc. can also subscribe to PCF 0 for events associated with the terminal status information (i.e., the first event). When the first event meets the reporting conditions, PCF 0 sends terminal status information to other PCFs such as PCF 1, PCF 2, PCF 3, etc. Furthermore, all PCFs subscribe to NEF for events related to terminal status information. When the event meets the reporting conditions, NEF sends terminal status information to all PCFs. Of course, multiple PCFs can also obtain terminal status information through other methods, which are not specifically limited in the embodiments of the present disclosure.

In some possible implementations, the above-mentioned QoS flows may be GBR QoS flows and non-GBR QoS flows. For different types of QoS flows, the corresponding QoS parameters are also different. For example, if the QoS flow is a GBR QoS flow, the QoS parameters of the QoS flow may include: GFBR and/or MFBR. For QoS flows that are non-GBR QoS flows, the QoS parameters of the QoS flow can include: AMBR. Among them, AMBR can be divided into: AMBR per terminal (UE-AMBR) and AMBR per session (session-AMBR) according to different granularities.

In one embodiment, if the QoS flow is a GBR QoS flow or a non-GBR QoS flow, the QoS parameters of the QoS flow may also include: MBR (UE-session-MBR) per terminal per slice.

In some possible implementations, when the QoS flow associated with the UE is a GBR QoS flow, S202 may include: the PCF decreases or increases one or more of the GFBR and MFBR according to the terminal status information, so as to GBR QoS flow performs QoS updates.

In some possible implementations, Figure 3 is a schematic flowchart of an implementation of performing QoS updates on GBR QoS flows in an embodiment of the present disclosure. Referring to Figure 3, after the PCF performs S202 to perform QoS updates, the PCF can also perform at least the following: One: S301 and S302.

S301, PCF sends QoS parameters (such as GFBR and/or MFBR) to the UPF entity. The QoS parameters are used by UPF to perform QoS updates on the downlink GBR QoS flow.

It is understandable that PCF can send QoS parameters to SMF through Npcf and Nsmf, and then SMF sends it to UPF. After UPF receives the QoS parameters, it uses the QoS parameters to perform QoS updates on the downstream GBR QoS flow.

S302. The PCF sends QoS parameters to the base station. The QoS parameters are used by the base station to perform QoS updates on the uplink and/or downlink GBR QoS flows.

It can be understood that the PCF can send the QoS parameters to the AMF through Npcf and Namf, and then the AMF sends it to the base station. After receiving the QoS parameters, the base station uses the QoS parameters to perform QoS updates on the uplink and/or downlink GBR QoS flows.

In the above S301 and S302, AMF and SMF can also obtain the QoS parameters sent by PCF by subscribing to events. For example, AMF can subscribe to PCF for events related to QoS parameters. After the QoS parameters, PCF queries the subscription events and confirms the events associated with the QoS parameters. When the event meets the reporting conditions, PCF sends QoS parameters to AMF. Similarly, SMF can also subscribe to PCF for events related to QoS parameters. After the QoS parameters, PCF queries the subscription events and confirms the events associated with the QoS parameters. When the event meets the reporting conditions, PCF sends QoS parameters to SMF. Of course, AMF and SMF can also use other methods to obtain QoS parameters from PCF, and this is not specifically limited in the embodiments of the present disclosure.

In some possible implementations, when the QoS flow is a non-GBR QoS flow, S202 may also include: PCF lowers or increases AMBR based on the terminal status information to perform QoS updates for the non-GBR QoS flow. For example, if the terminal status information indicates that the temperature of the UE is too high and cannot meet the current bandwidth demand, the PCF reduces the Session-AMBR of the first service of the UE.

In some possible implementations, Figure 4 is a schematic flowchart of an implementation of QoS update for non-GBR QoS flows in an embodiment of the present disclosure. Refer to Figure 4. For different QoS parameters, after S202, the PCF can also Perform at least one of the following: S401 to S403.

S401, PCF sends session-AMBR to UPF, so that UPF uses session-AMBR to perform QoS updates on the uplink and/or downlink session QoS flows. Here, PCF first sends session-AMBR to SMF, and then SMF sends it to UPF.

S402. The PCF sends session-AMBR to the UE, causing the UE to perform PDU session-based uplink rate limitation on non-GBR QoS flows.

S403. The PCF sends the UE-AMBR to the base station, so that the base station performs QoS updates on the uplink and/or downlink non-GBR QoS flows of each UE.

Of course, PCF can also perform other QoS updates for the GBR QoS flow, which is not specifically limited in this embodiment of the disclosure.

In some possible implementations, the QoS flow is a GBR QoS flow or a non-GBR QoS flow, and the QoS parameters of the QoS flow include: MBR per terminal per slice (UE-slice-MBR).

In some possible implementations, after the above S202, the above method includes: the PCF sends the UE-slice-MBR to the base station, so that the base station performs QoS update on the PDU session QoS flow corresponding to the S-NSSAI of the UE. S-NSSAI is used to represent a network slice (slice)

It should be understood that the UE can correspond to one or more PDU sessions on one slice, and the one or more PDU sessions are sessions of the first service. Then, after receiving the UE-slice-MBR, the base station uses the UE-slice-MBR to perform QoS updates for the QoS flows of all sessions of the first service on the slice corresponding to the S-NSSAI.

It should be noted that whenever a request to establish or modify a GBR QoS flow is received, the base station admission control should ensure that the sum of the GFBR values of the admitted GBR QoS flow does not exceed the UE-Slice-MBR. If the QoS flow cannot be Accepted, the base station shall reject the establishment or modification of the QoS flow. And, the base station should ensure that the aggregate bit rate of all GBR and non-GBR QoS flows belonging to the PDU sessions corresponding to the UE's S-NSSAI does not exceed the UE-Slice-MBR, while always ensuring the GFBR of each GBR QoS flow of these PDU sessions.

In the above S202, PCF performs QoS update, and the QoS parameters sent by PCF are updated QoS parameters.

Through the above process, PCF completes the process of performing QoS update based on terminal status information.

At this point, the QoS control process for the QoS flow has been implemented.

It should be noted that the above QoS control process can be reused with the service specific information provisioning procedure (Service specific information provisioning procedure), AF session establishment procedure (Setting up an AF session with required QoS procedure), etc. Of course, it can also be reused in other processes, which is not specifically limited in the embodiments of the present disclosure.

In the embodiment of the present disclosure, the AF provides the terminal status information of the UE to the PCF, so that the PCF can match the service traffic characteristics and terminal energy consumption management according to the terminal status information, that is, control the QoS flow according to the power consumption status of the UE to ensure Business needs and user experience. Furthermore, the terminal status information provided by the AF is used as additional information for policy determination, which can reduce the use of wireless interface network resources, especially when resources are limited. Furthermore, the AF provides the PCF with the terminal status information of the UE, which can support the use of network resources according to the UE's capabilities. Furthermore, U's terminal status information is provided to the PCF through AF, allowing the user's critical applications to be run in the power saving mode, thereby improving the user experience and extending battery life, rather than shutting down completely.

In some possible implementations, embodiments of the present disclosure also provide a QoS flow control method. Figure 5 is a schematic flowchart of the implementation of the second QoS flow control method in the embodiment of the present disclosure. Referring to Figure 5, the QoS flow control method can be applied to the application function entity (such as AF) side. The QoS flow control method can Including S501 to S502.

S501. The AF receives the terminal status information sent by the UE. The terminal status information is used to indicate the power consumption status of the UE.

It should be understood that after the UE registers with the network, it selects PCF to complete AM session association. The UE sends terminal status information to the AF.

S502: The AF sends terminal status information to the PCF. The terminal status information is also used by the PCF to perform QoS updates on the QoS flow associated with the UE.

In the implementation of the present disclosure, the execution process of AF can be referred to the description of the AF execution process in the above-mentioned embodiments of FIGS. 2 to 4. For the sake of simplicity of the description, no further description is given here.

Based on the same inventive concept, the embodiment of the present disclosure provides a QoS flow control device. Figure 6 is a schematic structural diagram of a QoS flow control device in the embodiment of the present disclosure. Referring to Figure 6, the control device 600 can It includes: processing module 601, receiving module 602 and sending module 603.

In some possible implementations, the control device may be the first core network functional entity in the communication system or a chip or system-on-chip of the first core network functional entity. It may also be the first core network functional entity used to implement the above. Functional modules of the methods described in various embodiments. The control device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module 602, configured to receive terminal status information from the application function entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module 601, configured to, based on the terminal status information, perform a The QoS flow performs QoS update; the sending module 603 is configured to send terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.

In the present disclosure, the first core network functional entity may be a PCF entity, and the second core network functional entity may be other PCF entities.

In some possible implementations, the processing module 601 is configured to reduce or increase the GFBR according to the terminal status information.

In some possible implementations, the sending module 603 is configured to send the MFBR to the third core network functional entity. The MFBR is used by the third core network functional entity to perform QoS updates on the downlink GBR QoS flow; and/or to the access network. The functional entity sends MFBR, which is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.

In some possible implementations, the processing module 601 is configured to reduce or increase the AMBR according to the terminal status information.

In some possible implementations, in response to the AMBR including the AMBR per session, the sending module 603 is configured to send the AMBR per session to the third core network functional entity, and the AMBR per session is used for the third core network functional entity. Perform QoS updates on upstream and/or downstream session QoS flows; or, send per-session AMBR to the terminal, and the per-session AMBR is used by the terminal to perform PDU session-based upstream rate limiting on non-GBR QoS flows.

In some possible implementations, in response to the AMBR including the AMBR of each terminal, the sending module 603 is configured to send the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used by the access network functional entity for each QoS updates are performed on the terminal's upstream and/or downstream non-GBR QoS flows.

In some possible implementations, in response to the QoS parameters including the MBR per terminal per slice, the sending module 603 is configured to send the MBR per terminal per slice to the access network functional entity, and the MBR per terminal per slice is used for access. The network access functional entity performs QoS updates on the PDU session QoS flow corresponding to the terminal's S-NSSAI.

In some possible implementations, the application function entity is a trusted application function entity; the receiving module 602 is configured to perform one of the following: receiving terminal status information sent by the application function entity; receiving terminal status information sent by the TSCTSF entity. Status information is sent by the application function entity to the TSCTSF entity.

In some possible implementations, the application function entity is an untrusted application function entity; the receiving module 602 is configured to perform one of the following: receiving terminal status information sent by the NEF entity, and the terminal status information is sent to the NEF by the application function entity Entity; receives the terminal status information sent by the TSCTSF entity. The terminal status information is sent by the application function entity to the TSCTSF entity through the NEF entity.

In some possible implementations, the processing module 601 is configured to query subscription events and determine the first event associated with the terminal status information; the sending module 603 is configured to send the first event to the third event if the first event satisfies the event reporting condition. The second core network functional entity sends terminal status information.

In some possible implementations, the above-mentioned control device may also be an application function entity in the communication system or a chip or system-on-chip of the application function entity, or may be an application function entity used to implement the methods described in the above embodiments. functional module. The control device can realize the functions performed by the application function entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.

Correspondingly, the receiving module 602 is configured to receive terminal status information sent by the terminal, and the terminal status information is used to represent the power consumption status of the terminal; the sending module 603 is configured to send the terminal status information to the first core network functional entity, and the terminal The status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.

In some possible implementations, the application function entity is a trusted application function entity; the sending module 603 is configured to perform one of the following: sending terminal status information to the first core network functional entity; sending terminal status information to the TSCTSF entity, The terminal status information is also used by the TSCTSF entity to send to the first core network functional entity.

In some possible implementations, the application function entity is an untrusted application function entity; the sending module 603 is configured to send terminal status information to the NEF entity. The terminal status information is also used by the NEF entity to send the first core network function entity to the NEF entity. Send, or the terminal status information is also used by the NEF entity to send to the first core network function entity through the TSCTSF entity.

It should be noted that for the specific implementation process of the processing module 601, the receiving module 602 and the sending module 603, reference can be made to the detailed description of the embodiments in Figures 2 to 5. For the sake of simplicity of the description, they will not be described again here.

The receiving module 602 mentioned in the embodiment of the present disclosure may be a receiving interface, a receiving circuit or a receiver, etc.; the sending module 603 may be a sending interface, a sending circuit or a transmitter, etc.; and the processing module 601 may be one or more processors.

Based on the same inventive concept, embodiments of the present disclosure provide a communication device, which may be the first core network functional entity or the application functional entity described in one or more of the above embodiments. Figure 7 is a schematic structural diagram of a communication device in an embodiment of the present disclosure. As shown in Figure 7, the communication device 700 uses general computer hardware, including a processor 701, a memory 702, a bus 703, an input device 704 and an output device. Device 705.

In some possible implementations, memory 702 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory. Memory 702 may store an operating system, application programs, other program modules, executable code, program data, user data, and the like.

Input device 704 may be used to enter commands and information to a communication device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television dish, scanner, or similar device. These input devices may be connected to processor 701 via bus 703 .

The output device 705 can be used for communication devices to output information. In addition to the monitor, the output device 705 can also be other peripheral output devices, such as speakers and/or printing devices. These output devices can also be connected to the processor 701 through the bus 703. .

The communication device may be connected to a network through the antenna 706, such as a local area network (LAN). In a networked environment, the computer execution instructions stored in the control device can be stored in a remote storage device and are not limited to local storage.

When the processor 701 in the communication device executes the executable code or application program stored in the memory 702, the communication device executes the relay communication method on the UE side or the network device side in the above embodiments. For the specific execution process, refer to the above embodiments. , which will not be described in detail here.

In addition, the above-mentioned memory 702 stores computer execution instructions for realizing the functions of the processing module 601, the receiving module 602 and the sending module 603 in FIG. 6 . The functions/implementation processes of the processing module 601, the receiving module 602 and the sending module 603 in Figure 6 can all be implemented by the processor 701 in Figure 7 calling the computer execution instructions stored in the memory 702. For specific implementation processes and functions, please refer to the above-mentioned relevant Example.

Based on the same inventive concept, embodiments of the present disclosure provide a network functional entity, such as a first core network functional entity or an application functional entity.

Figure 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure. Referring to Figure 8, the network functional entity 800 may include a processing component 801, which further includes one or more processors, and is represented by a memory 802 A memory resource used to store instructions, such as application programs, that can be executed by processing component 801. The application program stored in memory 802 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 801 is configured to execute instructions to perform any of the foregoing methods applied to the network device.

The network function entity 800 may also include a power supply component 803 configured to perform power management of the network function entity 800, a wired or wireless network interface 804 configured to connect the network function entity 800 to the network, and an input/output (I/O ) interface 805. The network function entity 800 may operate based on an operating system stored in the memory 802, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as an access network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory. , to implement the information reporting method on the access network function entity side as described in one or more of the above embodiments.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as a first core network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer executable data stored on the memory. Instructions are provided to implement the QoS flow control method on the first core network functional entity side as described in one or more of the above embodiments.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as an application function entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored on the memory. Implement the QoS flow control method on the application function entity side as described in one or more of the above embodiments.

Based on the same inventive concept, embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the network in one or more of the above embodiments. QoS flow control method on the functional entity side. Here, the network functional entity may include: a first core network functional entity or an application functional entity.

Based on the same inventive concept, embodiments of the present disclosure also provide a computer program or computer program product. When the computer program product is executed on a computer, it causes the computer to implement QoS on the entity side of the network function in one or more of the above embodiments. Flow control method Here, the network functional entity may include: a first core network functional entity or an application functional entity.

Other embodiments of the invention will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common common sense or customary technical means in the technical field that are not disclosed in the present disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It is to be understood that the present invention is not limited to the precise construction described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

A quality of service QoS flow control method, including:

The first core network functional entity receives terminal status information from the application functional entity, where the terminal status information is used to represent the power consumption status of the terminal;

The first core network functional entity performs one of the following:

According to the terminal status information, perform QoS update on the QoS flow associated with the terminal;

The terminal status information is sent to the second core network functional entity, where the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
The method according to claim 1, wherein the first core network functional entity is a first policy and control function (PCF) entity, and the second core network functional entity is a second PCF entity.
The method of claim 1, wherein the QoS flow includes at least one of the following:

Session QoS flow;

Business data flow QoS flow.
The method according to claim 1, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

CPU load;

Terminal overheating status.
The method according to claim 1, wherein the QoS flow is a guaranteed bit rate GBR QoS flow, and the QoS parameters of the QoS flow include: guaranteed flow bit rate GFBR and/or maximum flow bit rate MFBR.
The method according to claim 5, wherein the first core network functional entity performs QoS update on the QoS flow according to the terminal status information, including:

The first core network functional entity lowers or raises the GFBR according to the terminal status information.
The method of claim 5, further comprising:

The first core network functional entity sends an MFBR to the third core network functional entity, and the MFBR is used by the third core network functional entity to perform QoS update on the downlink GBR QoS flow; and/or,

The first core network functional entity sends an MFBR to the access network functional entity, and the MFBR is used by the access network functional entity to perform QoS updates on uplink and/or downlink GBR QoS flows.
The method according to claim 1, wherein the QoS flow is a non-GBR QoS flow, and the QoS parameters of the QoS flow include: aggregate maximum bit rate AMBR.
The method according to claim 8, wherein the first core network functional entity performs QoS update on the QoS flow according to the terminal status information, including:

The first core network functional entity lowers or raises the AMBR according to the terminal status information.
The method according to claim 8, wherein the AMBR includes at least one of the following: AMBR per terminal, AMBR per session.
The method of claim 10, wherein in response to the AMBR comprising a per-session AMBR, the method further includes:

The first core network functional entity sends the per-session AMBR to the third core network functional entity, and the per-session AMBR is used by the third core network functional entity to perform QoS updates on the uplink and/or downlink session QoS flows. ;or,

The first core network functional entity sends the per-session AMBR to the terminal, and the per-session AMBR is used by the terminal to perform uplink rate limiting based on the protocol data unit PDU session on the non-GBR QoS flow. .
The method of claim 10, wherein in response to the AMBR comprising a per-terminal AMBR, the method further includes:

The first core network functional entity sends the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used by the access network functional entity for the uplink and/or downlink non-GBR QoS of each terminal. Flow performs QoS updates.
The method according to claim 1, wherein the QoS flow is a GBR QoS flow or a non-GBR QoS flow, and the QoS parameters of the QoS flow include: the maximum bit rate MBR per slice per terminal.
The method of claim 13, wherein in response to the QoS parameters including MBR per terminal per slice, the method further includes:

The first core network functional entity sends the MBR of each slice of each terminal to the access network functional entity. The MBR of each slice of each terminal is used by the access network functional entity to select a single network slice for the terminal. The PDU session QoS flow corresponding to S-NSSAI performs QoS update.
The method according to claim 1, wherein the application function entity is a trusted application function entity;

The first core network functional entity receives terminal status information from the application functional entity, including one of the following:

The first core network functional entity receives the terminal status information sent by the application functional entity;

The first core network function entity receives the terminal status information sent by a time-sensitive communication time synchronization function TSCTSF entity, and the terminal status information is sent by the application function entity to the TSCTSF entity.
The method according to claim 1, wherein the application function entity is an untrusted application function entity;

The first core network functional entity receives terminal status information from the application functional entity, including one of the following:

The first core network function entity receives the terminal status information sent by the network opening function NEF entity, and the terminal status information is sent by the application function entity to the NEF entity;

The first core network function entity receives the terminal status information sent by the time-sensitive communication time synchronization function TSCTSF entity, and the terminal status information is sent by the application function entity to the TSCTSF entity through the NEF entity.
The method according to claim 1, wherein the first core network functional entity sends the terminal status information to the second core network functional entity, including:

The first core network functional entity queries the subscription event and determines the first event associated with the terminal status information;

When the first event satisfies event reporting conditions, the first core network functional entity sends the terminal status information to the second core network functional entity.
A quality of service QoS flow control method, including:

The application function entity receives terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal;

The application function entity sends the terminal status information to the first core network functional entity, and the terminal status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.
The method of claim 18, wherein the QoS flow includes at least one of the following:

Session QoS flow;

QoS flow of business data flow.
The method according to claim 18, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

CPU load;

Terminal overheating status.
The method according to claim 18, wherein the application function entity is a trusted application function entity;

The application function entity sends the terminal status information to the first core network function entity, including one of the following:

The application function entity sends the terminal status information to the first core network function entity;

The application function entity sends the terminal status information to the time-sensitive communication time synchronization function TSCTSF entity, and the terminal status information is also used by the TSCTSF entity to send to the first core network function entity.
The method according to claim 18, wherein the application function entity is an untrusted application function entity;

The application function entity sends the terminal status information to the first core network function entity, including:

The terminal status information sent by the application function entity to the network opening function NEF entity, the terminal status information is also used by the NEF entity to send to the first core network function entity, or the terminal status information is also The NEF entity sends the time-sensitive communication time synchronization function TSCTSF entity to the first core network function entity through the time-sensitive communication time synchronization function TSCTSF entity.
A quality of service QoS flow control device, including:

A receiving module configured to receive terminal status information from the application function entity, where the terminal status information is used to represent the power consumption status of the terminal;

A processing module configured to perform QoS update on the QoS flow associated with the terminal according to the terminal status information;

The sending module is configured to send the terminal status information to the second core network functional entity, where the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
A quality of service QoS flow control device, including:

A receiving module configured to receive terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal;

The sending module is configured to send the terminal status information to the first core network functional entity, where the terminal status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.
A communication device, characterized in that it includes: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored on the memory to implement claims 1 to 1 The quality of service QoS flow control method described in any one of 22.
A computer storage medium that stores computer-executable instructions, characterized in that, after being executed by a processor, the computer-executable instructions can implement the quality of service QoS flow control method as described in any one of claims 1 to 22.