Coding rate adjustment method and device

By detecting the network status through access network equipment and sending the recommended coding rate to the application server, the problem that the transmission status information cannot directly reflect the rate that the application should adjust is solved, adaptive adjustment is achieved, and the user experience and traffic control effect are improved.

WO2025213735A1PCT designated stage Publication Date: 2025-10-16HONOR DEVICE CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/123807
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-04-08
Filing Date
2024-10-10
Publication Date
2025-10-16

AI Technical Summary

Technical Problem

In existing communication systems, the transmission status information provided by the RAN or UPF cannot directly reflect the coding rate that the application should adjust, resulting in the server side having to speculate on the adjustment effect.

Method used

The access network device detects the network status and sends a recommended coding rate to the application server through the core network. The application server makes adaptive adjustments based on the recommended coding rate to avoid speculation.

Benefits of technology

It improves the effect of coding rate adjustment, ensures user experience, reduces the occupation of user plane resources, and achieves high availability and refined traffic control.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024123807_16102025_PF_FP_ABST
    Figure CN2024123807_16102025_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a coding rate adjustment method and a related device. The method comprises: an access network device detects a network state, the network state being used for representing a connection state of the access network device in uplink transmission or downlink transmission; and when the network state is a congested state, a near congestion state, a congestion ended state, or a near congestion-ended state, the access network device sends a recommended coding rate to an application server by means of a core network, so that, on the basis of the recommended coding rate, the application server adjusts the coding rate of resources transmitted between the application server and a terminal. Considering that general congestion occurs in uplink transmission or downlink transmission of an access network, in the method, the access network device can determine the recommended coding rate on the basis of the congestion condition, and directly sends the recommended coding rate to the application server by means of the core network, and the application server adaptively adjusts on the basis of the recommended coding rate instead of speculating the rate for adjustment, improving the adjustment effect and ensuring the user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for adjusting a coding rate

[0001] This application claims priority to the Chinese Patent Application No. 202410415582.3, filed on April 8, 2024, and entitled “Method and apparatus for adjusting a coding rate”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a method for adjusting a coding rate, an access network device, an application server, a communication system, and a computer readable storage medium. BACKGROUND

[0003] With the development of mobile communication technology, especially the continuous development of new generation mobile communication technology such as the fifth generation mobile communication technology (5G), the functions of communication systems are constantly being enhanced. Specifically, 5G communication systems can provide enhanced mobile broadband (eMBB) with faster connections, higher throughput and greater capacity, and provide ultra-reliable low-latency communications (uRLLC) to apply networks in critical task scenarios that require uninterrupted and stable data links, such as extended reality (XR) scenarios, to meet the requirements of ultra-reliability and low latency of wireless communication networks for scenarios.

[0004] However, the network state (or network condition) in the communication system is dynamically changing, for example, network congestion can occur during peak traffic periods. For this reason, a server (such as an XR application server) can adjust the coding rate of media (such as video or audio) according to the network state.

[0005] Currently, some transmission state information of a radio access network (RAN) or a user plane function (UPF) can be provided to the server, and the server adjusts the coding rate according to the transmission state information. However, the transmission state information does not directly reflect the rate that the application should adjust, and the server side needs to speculate the rate that the application should adjust and try to adjust according to the speculation result, which results in poor adjustment effect.

[0006] SUMMARY

[0007] The application provides a coding rate adjustment method and related devices, systems and media, aiming to solve the problem that the transmission state information provided by the RAN or the UPF cannot directly reflect the rate that should be adjusted by the application, the server side needs to adjust the rate according to the speculation result, resulting in poor adjustment effect, and to realize adaptive adjustment according to the recommended coding rate of the access network device and guarantee user experience.

[0008] To achieve the above object, the application provides the following technical solutions:

[0009] The first aspect of the application provides a coding rate adjustment method. The method can be executed by an access network device. The access network device can include but is not limited to a base station and a wireless relay node. Specifically, the access network device detects a network state, which is used to represent the connection state of the access network device in uplink transmission or downlink transmission. When the network state is congestion, about to be congested, end of congestion or about to end of congestion, the access network device sends a recommended coding rate to an application server through a core network, so that the application server adjusts the coding rate of the resource transmitted between the application server and a terminal according to the recommended coding rate. The recommended coding rate is determined by the access network device.

[0010] Considering that general congestion occurs in uplink (UL) transmission or downlink (DL) transmission of the access network, in the method, the access network device can determine the recommended coding rate according to the congestion condition, and directly send the recommended coding rate to the application server through the core network. The application server does not need to speculate the rate that should be adjusted, but performs adaptive adjustment according to the recommended coding rate, thereby improving the adjustment effect and guaranteeing user experience.

[0011] In some possible implementation manners, the access network device can send the recommended coding rate to the application server through a control plane network element of the core network. The control plane network element includes an access and mobility management function (AMF) network element, a session management function (SMF) network element, a policy control function (PCF) network element or a network exposure function (NEF) network element.

[0012] The method transmits the recommended coding rate to the application server through the control plane network element of the core network, which can realize adaptive adjustment of the application server according to the recommended coding rate, and can also reduce the occupation of the user plane resource, thereby guaranteeing the operation of the business.

[0013] In some possible implementation manners, when the access network device sends the recommended coding rate to the application server through the core network, the access network device can first send a protocol data unit (PDU) session resource notification to an AMF network element. The PDU session resource notification includes the recommended coding rate, and the AMF network element is used to transmit the recommended coding rate through a session update request.

[0014] In the method, the access network device can transmit the recommended encoding rate to the application server through the interfaces between the network elements of the core network in sequence, without developing a new interface to transmit the recommended encoding rate, and has high availability.

[0015] In some possible implementation manners, the access network device can send the recommended encoding rate to the application server through a user plane network element of the core network, and the user plane network element includes a user plane function (UPF) network element or a network exposure function (NEF) network element. The method supports transmitting the recommended encoding rate to the application server through different paths, and has high availability.

[0016] In some possible implementation manners, the access network device can send uplink data to the UPF network element, where the uplink data is encapsulated by a packet radio service tunneling protocol (GTP), and the recommended encoding rate is included in a header file of the uplink data, and the UPF network element is configured to transmit the recommended encoding rate to the application server.

[0017] In the method, the access network device encapsulates the recommended encoding rate in the GTP header of the uplink data, so that the recommended encoding rate is transmitted to the application server together when the uplink data is transmitted to the application server, network resources are multiplexed, and unnecessary communication overhead is reduced.

[0018] In some possible implementation manners, the UPF network element is configured to send the recommended encoding rate to the application server when the application server is in a trusted domain of the core network, and send the recommended encoding rate to the NEF network element when the application server is not in the trusted domain of the core network, and send the recommended encoding rate to the application server by the NEF network element.

[0019] In some possible implementation manners, the access network device can further send a transmission type to the application server. The transmission type includes uplink transmission or downlink transmission. When the transmission type is uplink transmission, the application server sends a temporary maximum media bit rate request (TMMBR) to the terminal according to the recommended encoding rate, and the TMMBR includes the recommended encoding rate. When the transmission type is downlink transmission, the application server sends a temporary maximum media bit rate notification (TMMBN) to the terminal according to the recommended encoding rate, and the TMMBN includes the recommended encoding rate.

[0020] The method provides a scheme for adaptively adjusting the encoding rate for uplink transmission or downlink transmission, and has high availability.

[0021] In some possible implementation manners, the access network device can send a flow identifier of a data flow and a recommended encoding rate corresponding to the flow identifier to the application server through the core network. In this way, resource encoding rate adaptive adjustment can be implemented at the granularity of the data flow, and the requirement of fine traffic control can be met.

[0022] The second aspect of the present application provides a coding rate adjustment method. The method can be performed by an application server. Specifically, the application server receives a recommended coding rate sent by an access network device when the access network device detects that a network state is congestion, about to be congestion, end of congestion, or about to end of congestion, the network state is used to represent a connection state of the access network device in uplink transmission or downlink transmission, and the recommended coding rate is determined by the access network device. Then the application server adjusts the coding rate of a resource transmitted between the application server and a terminal according to the recommended coding rate.

[0023] In the method, the application server can receive the recommended coding rate sent by the RAN side through the core network. The application server does not need to speculate the rate that should be adjusted, but performs adaptive adjustment according to the recommended coding rate, thereby improving the adjustment effect and ensuring user experience.

[0024] In some possible implementation manners, the application server can further receive a transmission type sent by the access network device, and the transmission type includes uplink transmission or downlink transmission. Accordingly, when the transmission type is uplink transmission, the application server sends a temporary maximum media bit rate request (TMMBR) to the terminal according to the recommended coding rate, and the TMMBR includes the recommended coding rate; and when the transmission type is downlink transmission, the application server sends a temporary maximum media bit rate notification (TMMBN) to the terminal according to the recommended coding rate, and the TMMBN includes the recommended coding rate.

[0025] The method supports adaptive adjustment of the coding rate of uplink transmission or downlink transmission, and has high availability.

[0026] The third aspect of the present application provides an electronic device, which can be an access network device. The access network device includes a memory and at least one processor. The memory is configured to store a program, and the at least one processor is configured to execute the program, so that the access network device implements the coding rate adjustment method provided by the first aspect of the present application.

[0027] The fourth aspect of the present application provides an electronic device, which can be an application server. The application server includes a memory and at least one processor. The memory is configured to store a program, and the at least one processor is configured to execute the program, so that the application server implements the coding rate adjustment method provided by the second aspect of the present application.

[0028] The fifth aspect of the present application provides a communication system, including a first device and a second device. The first device can be an access network device, and the second device can be an application server. The first device and the second device are configured to perform the coding rate adjustment method provided by the first aspect of the present application.

[0029] A sixth aspect of the present application is a computer storage medium, configured to store a computer program, wherein the computer program is executed to implement the coding rate adjustment method provided in the first aspect or the second aspect of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0030] FIG. 1 is an example diagram of a communication system architecture disclosed in an embodiment of the present application;

[0031] FIG. 2 is an application scenario diagram disclosed in an embodiment of the present application;

[0032] FIG. 3 is another application scenario diagram disclosed in an embodiment of the present application;

[0033] FIG. 4 is a flowchart of a coding rate adjustment method disclosed in an embodiment of the present application;

[0034] FIG. 5 is a flowchart of another coding rate adjustment method disclosed in an embodiment of the present application;

[0035] FIG. 6 is a signaling flowchart of a coding rate adjustment method disclosed in an embodiment of the present application;

[0036] FIG. 7 is a signaling flowchart of another coding rate adjustment method disclosed in an embodiment of the present application;

[0037] FIG. 8 is an example diagram of the structure of an electronic device disclosed in an embodiment of the present application;

[0038] FIG. 9 is an example diagram of the structure of another electronic device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing the specific embodiments and are not intended to be limiting to the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that “one or more” as used in the embodiments of the present application means one, two, or more than two; “and / or” describes the associated objects in the conjunctive relationship, which means that there can be three kinds of relationships; for example, A and / or B can mean that A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects.

[0040] Reference within this specification to "one embodiment" or "an embodiment" or "a specific embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" or "in some embodiments" within this specification do not necessarily refer to the same embodiment, although it can. The terms "including," "comprising," "having," and variations thereof, mean "including but not limited to," unless expressly specified otherwise.

[0041] The plurality of embodiments of the present application refers to greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the terms "first", "second", etc. are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can it be understood as indicating or implying order.

[0042] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as global system for mobile communications (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, 5th generation (5G) system or new radio (NR), and future communication systems.

[0043] In order to meet the challenge of wireless broadband technology, keep the leading advantage of 3GPP network, the 3GPP standard group formulates the next generation mobile communication network architecture (next generation system), called 5G network architecture. This architecture not only supports the wireless technologies defined by the 3GPP standard group, such as LTE and the like, to access the 5G core network (5G core network, 5GC), but also supports non-3GPP access technologies to access the 5GC through non-3GPP interworking function (non-3GPP interworking function, N3IWF), trusted non-3GPP gateway function (trusted non-3GPP gateway function, TNGF), trusted WLAN interworking function (trusted WLAN interworking function, TWIF) or next generation packet data gateway (next generation packet data gateway, NG-PDG). Among them, the core network function is divided into user plane function (user plane function, UPF) network element and control plane function (control plane function, CPF) network element. The UPF is mainly responsible for forwarding packet data, quality of service (quality of service, QoS) control, charging information statistics and the like. The CPF is mainly responsible for user registration authentication, mobility management and issuing data packet forwarding strategy and QoS control strategy to the UPF, which can be further divided into access and mobility management function (access and mobility management function, AMF) and session management function (session management function, SMF).

[0044] The core network device includes, for example, a mobility management entity (mobility management entity, MME), a broadcast multicast service center (broadcast multicast service center, BMSC) and the like, or can also include corresponding function entities in the 5G system, such as core network control plane (control plane, CP) or user plane (user plan, UP) network function and the like, for example: SMF, AMF and the like. Among them, the core network control plane can also be understood as a core network control plane function (control plane function, CPF) entity.

[0045] FIG. 1 is an example of a communication system architecture suitable for embodiments of the present application. Among them, the functions of the user equipment and each network entity are as follows.

[0046] Terminal: can be referred to as a terminal device, a terminal device unit, a terminal device station, a terminal device agent, a terminal device apparatus, an access terminal, a terminal in V2X communication, a subscriber unit, a user equipment (UE), a user station, a mobile station, a mobile station (MS), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user apparatus.

[0047] The user equipment in the embodiments of the present application can also be a mobile phone, a pad, a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an eXtended Reality (XR) terminal, a wireless terminal in industrial control, a haptic terminal device, a vehicle-mounted terminal device, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolution network, etc.

[0048] Among them, the wearable device can also be called a wearable smart device, which is a general term for devices that can be worn by applying wearable technology to the smart design and development of daily wear, such as headsets, XR glasses, gloves, watches, clothing, and shoes. Among them, the XR glasses can be AR glasses or VR glasses. The wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a powerful function realized through software support and data interaction, cloud interaction. The general wearable smart device includes functions, large size, and can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart bracelets and smart jewelry for monitoring vital signs. It should be noted that the wearable device, such as the XR device, can also integrate the functions of the smart phone, such as the XR device, which can also integrate the subscriber identity module (SIM) or embedded SIM (e SIM) for cellular communication.

[0049] Radio access network (RAN): a network composed of multiple 5G-RAN nodes, which implements wireless physical layer functions, resource scheduling and wireless resource management, wireless access control and mobility management functions. The 5G-RAN is connected to the UPF through the user plane interface N3 and is used to transmit data of the terminal device; the 5G-RAN establishes a control plane signaling connection through the control plane interface N2 and the AMF, which is used to realize the functions of wireless access bearer control. The RAN can be any device with wireless transceiver function, including but not limited to 5G node base (gNB), evolutional node base (eNB), wireless access point (WiFi AP), world interoperability for microwave access base station (WiMAX BS), transmission receiving point (TRP), wireless relay node, wireless backhaul node, etc.

[0050] The access network device in the embodiments of the present application, i.e., the network device of the access network, can also be a device for communicating with the terminal device. The access network device can be a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA) system, can be a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, can be an evolutional node base (eNB) in an LTE system, can be a wireless controller in a cloud radio access network (CRAN) scenario, or can be a relay station, an access point, a vehicle-mounted device, a wearable device, an access network device in a future 5G network, or an access network device in a future evolved PLMN network, etc. The embodiments of the present application are not limited.

[0051] In NR, the functions of a base station are divided into two parts, referred to as centralized unit (CU)-distributed unit (DU) separation. From the perspective of the protocol stack, the CU includes the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer of the LTE base station, and the DU includes the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer of the LTE base station. In a common 5G base station deployment, the CU and the DU can be connected by an optical fiber in a physical manner, and there is a specially defined F1 interface for communication between the CU and the DU in a logical manner. From the perspective of functions, the CU is mainly responsible for radio resource control and configuration, cross-cell mobility management, bearer management, etc. The DU is mainly responsible for scheduling, physical signal generation and transmission.

[0052] Some network elements involved in the communication system, such as SMF, UPF, PCF, AF or NEF, are described in detail below.

[0053] SMF: mainly responsible for the control plane function of terminal device session management, including the selection and control of user plane function (UPF), the allocation of internet protocol (IP) address, the QoS management of session, the acquisition of policy and charging control (PCC) policy from PCF, etc.

[0054] UPF: as the anchor point of protocol data unit (PDU) session connection, responsible for the data packet filtering, data transmission / forwarding, rate control, generation of charging information of terminal device, and provides connection with data network (DN).

[0055] PCF: provides configuration policy information for terminal device, and provides policy information for controlling terminal device for the control plane network element of network, such as SMF; generates terminal device access policy and QoS flow control policy.

[0056] AF: interacts with network elements of core network to provide some services, such as interacting with PCF to perform service policy control, interacting with network exposure function (NEF) network element to obtain some network capability information or providing some application information to network, and providing some data network access point information to PCF to generate corresponding data service routing information.

[0057] NEF: a network element connected to all network functions in a bus manner based on service-oriented architecture, exposes network capabilities to third-party applications, can realize friendly connection of network capabilities and service demand, improve service experience, and optimize network resource configuration.

[0058] The terminal device in the embodiment of the application is connected to the RAN device in a wireless manner, and the RAN network element is connected to the 5GC device in a wireless or wired manner. The 5GC device and the RAN network element can be independent and different physical devices, can be integrated with the functions of the 5GC device and the logical functions of the RAN network element on the same physical device, or can be a physical device integrated with part of the functions of the 5GC device and part of the functions of the RAN network element. The terminal device can be fixed or movable.

[0059] The 5GC device mainly includes the PCF network element, the SMF network element, and the UPF network element, etc.

[0060] It should be noted that the above "network element" can also be referred to as an entity, device, apparatus or module, etc., and the present application does not particularly limit it. In addition, in order to facilitate understanding and description, the description of "network element" is omitted in part of the description, for example, the NEF network element is referred to as NEF, in which case the "NEF" should be understood as the NEF network element or the NEF entity, and the following description of the same or similar cases is omitted.

[0061] It should be noted that the naming of each network element included in Figure 1 is only a name, and the name does not constitute a limitation on the function of the network element itself. In 5G networks and future other networks, the above-mentioned various network elements can also be other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, part or all of the above-mentioned network elements can continue to use the terminology in 5G, or can be other names, etc., which are uniformly described here and will not be described again below.

[0062] It should be noted that the network elements in Figure 1 are not necessarily present at the same time, and it can be determined which network elements are needed according to the needs. The connection relationship between the network elements in Figure 1 is also not uniquely determined and can be adjusted according to the needs.

[0063] It can be understood that the above network element or function can be a network element in a hardware device, or a software function running on a dedicated hardware, or a platform, such as a virtualized function instantiated on a cloud platform.

[0064] Figure 2 is an application scenario provided by the present application, which is applicable to the present application. As shown in Figure 2, the embodiments of the present application can be applied to a multi-modal service scenario, for example, an XR scenario. The XR scenario includes an AF network element and a plurality of XR devices, for example, XR device 1 and XR device 2. The AF network element can be an XR server, and the XR device can be an XR head-mounted display (HMD), an XR glasses, and the XR device can also include a controller, such as a hand-held controller. In this example, the XR device 1 can be an XR glasses, and the XR device 2 can be a hand-held controller. The user can wear the XR glasses and hold the hand-held controller to play cloud games. The XR server can receive video frames, audio data, haptic data or pose & control data from the XR device side, for example, video frames, audio data collected by the XR glasses, and haptic data, pose & control data collected by the hand-held controller, and return processed video frames, audio data, haptic data or pose & control data to the XR device. The XR server and the XR device interact with various commands and data through a communication link in the network architecture to form a global control loop.

[0065] In a multi-modal service application scenario, multiple data flows, e.g., QoS flows, are needed to transmit different data types such as video, audio, haptics or pose and control. The data flows are correlated in space and time.

[0066] In the example of FIG. 2, the data collected by the XR devices, e.g., video frames, audio data, haptics data, pose and control data, can be transmitted to the access network, e.g., to the access network device, e.g., gNB, by the terminal. The access network device can transmit the data to the 5GC by QoS flows, and then the 5GC transmits the data to the XR server. It should be noted that the XR devices can also communicate directly with the access network device. For example, in the case that the XR devices integrate eSIM or the functions of the UE are integrated into the XR devices, the XR devices can directly connect to the access network device. Accordingly, the XR devices can transmit the collected data directly to the access network device, e.g., directly to the access network device by QoS flows, without going through the UE. Alternatively, the terminal can also be located inside the XR device, e.g., terminal 1 is located inside XR device 1 and terminal 2 is located inside XR device 2, and the XR devices 1 and 2 directly interact with the access network device.

[0067] Correspondingly, the XR server can return multi-modal data flows to the XR devices. Specifically, the XR server can first return multi-modal data flows to the 5GC, the 5GC transmits the multi-modal data flows to the access network device in the form of QoS flows, the access network device transmits the multi-modal data flows to the corresponding UE, and then the UE transmits the received data flows to the XR devices.

[0068] It should be noted that FIG. 2 is an example of a multi-modal scenario in which multiple XR devices connect to the network through different terminals, e.g., an inter-UE multi-modal scenario. In other possible implementations of the embodiments of the present application, the application scenarios of the present application can also include a multi-modal scenario in which multiple XR devices connect to the network through the same terminal, e.g., an intra-UE multi-modal scenario. As shown in FIG. 3, multiple XR devices can connect to the network through the same terminal, which can serve as a unified entry or exit for multiple XR devices to interact with the XR server. The multiple XR devices can include XR device 1 and XR device 2. In the example of FIG. 3, XR device 1 can be an XR glasses that can collect video data and audio data, and XR device 2 can be a handle that can collect haptics data, pose and control data. XR device 1 and XR device 2 are connected to the same terminal, and the data collected by XR device 1 and XR device 2 can be transmitted to the access network device through the terminal.

[0069] The above FIG. 2 and FIG. 3 are only used as an example of two XR devices, and the present application can be applied to multiple XR devices, not limited to two. Further, the above XR device can be replaced by other sensing devices, and the present application does not limit this.

[0070] However, the network state (or network condition) in the communication system is dynamically changing, for example, network congestion can occur during peak traffic period. Therefore, the server (such as XR application server) can adjust the encoding rate of media (such as video or audio) resources according to the network state to improve user experience.

[0071] Currently, related protocols or standards propose to disclose some transmission state information of RAN or UPF to the server, for example, to disclose the UE data rate, average bit rate, and round-trip delay of multiple QoS flows to the XR application server, and the server adjusts the encoding rate according to the transmission state information. However, the transmission state information cannot directly reflect the rate that the application should adjust, and the server side needs to speculate the rate that the application should adjust and try to adjust according to the speculation result, which leads to poor adjustment effect.

[0072] Therefore, the present application provides an encoding rate adjustment method. The method can be executed by an access network device. Specifically, the access network device can detect a network state, and the network state is used to represent the connection state of the access network device in uplink transmission or downlink transmission. When the network state is congestion, about to be congested, end of congestion, or about to end of congestion, the access network device sends a recommended encoding rate to an application server through a core network. The recommended encoding rate is determined by the access network device. In this way, the application server can adjust the encoding rate of the resources transmitted between the application server and the terminal according to the recommended encoding rate.

[0073] The method considers that general congestion occurs in uplink (UL) transmission or downlink (DL) transmission of RAN, and RAN can determine the recommended encoding rate according to the congestion condition and directly send the recommended encoding rate to the application server through the core network. The application server does not need to speculate the rate that should be adjusted, but performs adaptive adjustment according to the recommended encoding rate, which improves the adjustment effect and guarantees user experience.

[0074] In order to make the technical solutions of the present application clearer and easier to understand, the encoding rate adjustment method of the present application will be described in detail below with reference to the accompanying drawings.

[0075] Referring to a flowchart of an encoding rate adjustment method shown in FIG. 4, the method includes the following steps:

[0076] S402, the access network device detects the network state. When the network state is congestion, about to be congested, end of congestion, or about to end of congestion, S404 is performed.

[0077] The network state is used to represent the connection state of the access network device in uplink transmission or downlink transmission. The network state can include congestion, impending congestion, end of congestion, or impending end of congestion. Among them, congestion can be understood as congestion has occurred, and impending congestion means that congestion is perceived to be possible. Similarly, the end of congestion means that the congestion has ended, and the impending end of congestion means that the congestion is perceived to be possible to end.

[0078] Among them, congestion refers to a situation where the number of packets transmitted in a packet switching network is too large, and the network transmission performance is reduced due to the limited resources of the store-and-forward node (such as RAN). When the network is congested, data loss, increased latency, and decreased throughput will generally occur, and in severe cases, it can even lead to "congestion collapse". Generally, when the load in the network is excessively increased, causing the network performance to decrease, network congestion will occur.

[0079] Specifically, the access network device can monitor the resources allocated to the UE, and determine the network state according to the resource allocation, for example, when the resources allocated to the UE are difficult to meet the requirements of QoS, it means that the network is about to be congested, and the access network device can determine the network state as impending congestion. For another example, the resources allocated to the UE in the current period can meet the requirements of QoS, and the resources allocated to the UE in the previous n periods are difficult to meet the requirements of QoS, which means that the network is ending congestion.

[0080] S404, the access network device sends the recommended encoding rate to the application server through the core network, so that the application server adjusts the encoding rate of the resource transmitted between the application server and the terminal according to the recommended encoding rate.

[0081] Among them, the recommended encoding rate is determined by the access network device. The recommended encoding rate refers to the encoding rate recommended by the access network device according to the current network state. Among them, the access network device can measure the interference signal to noise ratio (Signal to Noise And Distortion Ratio, SINR) of the reference signal, wherein the SINR of the reference signal can be approximately regarded as the equivalent signal to noise ratio (Signal to Noise Ratio, SNR) under the condition of additive white Gaussian noise (Add white Gaussian noise, AWGN) channel. Based on this, the access network device can determine the encoding rate corresponding to the current network state according to the SINR of the reference signal by looking up the table.

[0082] The network status of uplink transmission and downlink transmission can be different, for example, the network status of uplink transmission can be about to be congested, and the network status of downlink transmission can be end of congestion. Based on this, the access network device can determine the respective recommended encoding rate for uplink transmission and downlink transmission, respectively.

[0083] In some possible implementation ways, the access network device can send the recommended encoding rate to the application server through a control plane network element of the core network. The control plane network element includes an access and mobility management function (AMF) network element, a session management function (SMF) network element, a policy control function (PCF) network element, or a network exposure function (NEF) network element.

[0084] Specifically, the access network device can send a PDU session resource notification to the AMF network element. The PDU session resource notification is denoted as PDU session resource notify. The PDU session resource notify includes the recommended encoding rate, which is also called access network bitrate recommendations (ANBR). The access network device such as gNodeB provides the recommended encoding rate to the UE according to the uplink air interface capability fed back by the MAC control element (CE), to cooperate with the UE to implement the rate adjustment function. The AMF network element is used to transmit the recommended encoding rate through a session update request.

[0085] In other possible implementation ways, the access network device can send the recommended encoding rate to the application server through a user plane network element of the core network. The user plane network element includes a user plane function (UPF) network element or a network exposure function (NEF) network element. Specifically, the access network device can send uplink data to the UPF network element, and the uplink data is encapsulated by a general packet radio service tunneling protocol (GTP). The header file of the uplink data includes the recommended encoding rate, such as ANBR. The UPF network element is used to transmit the recommended encoding rate to the application server.

[0086] When the recommended encoding rate is sent through a user plane network element, different paths can be selected to send the recommended encoding rate to the application server according to whether the application server is in a trust domain of the core network. The trust domain is also referred to as a trust boundary. In the core network, the AMF is a termination point of Non-Access Stratum (NAS) security. In the 3GPP 5G first stage specification, the AMF is collocated with a SEcurity Anchor Function (SEAF) that holds a root key (referred to as an anchor key) of the visited network.

[0087] For example, when the application server (such as an AF) is in the trust domain of the core network, the UPF network element is used to send the recommended encoding rate to the application server. For another example, when the application server is not in the trust domain of the core network, the UPF network element is used to send the recommended encoding rate to the NEF network element, and the NEF network element sends the recommended encoding rate to the application server.

[0088] It should be noted that the access network device can also send a transmission type to the application server, and the transmission type includes uplink transmission or downlink transmission. When the transmission type is uplink transmission, the application server can send a Temporal Max Media Bitrate Request (TMMBR) to the terminal according to the recommended encoding rate. The TMMBR includes the recommended encoding rate. The TMMBR is used to request that the encoding rate of the terminal be adjusted to the recommended encoding rate. When the transmission type is downlink transmission, the application server can send a Temporal Max Media Bitrate Request Notification (TMMBN) to the terminal according to the recommended encoding rate. The TMMBN can include the recommended encoding rate. The TMMBN is used to notify the terminal that the encoding rate on the server side is adjusted to the recommended encoding rate.

[0089] Further, a plurality of data flows, such as a plurality of QoS flows, can be included between the terminal and the application server. Accordingly, the access network device can send a flow identifier of a data flow and a recommended encoding rate corresponding to the flow identifier to the application server through the core network. The flow identifier of the data flow can uniquely identify the data flow. In some examples, when the data flow is a QoS flow, the flow identifier of the data flow can be a Quality of Service Flow Identifier (QFI).

[0090] Based on the above description, the application provides an encoding rate adjustment method. In the method, considering that general congestion occurs in uplink transmission or downlink transmission of the RAN, the RAN can determine a recommended encoding rate according to the congestion condition, and directly send the recommended encoding rate to the application server through the core network. The application server does not need to speculate the rate that should be adjusted, but performs adaptive adjustment according to the recommended encoding rate, thereby improving the adjustment effect and ensuring user experience.

[0091] FIG. 4 introduces the encoding rate adjustment method of the application from the perspective of the access network device. The following introduces the encoding rate adjustment method of the application from the perspective of the application server.

[0092] Referring to a flowchart of an encoding rate adjustment method shown in FIG. 5, the method includes the following steps.

[0093] S502. The application server receives a recommended encoding rate sent by the access network device when detecting that the network state is congestion, about to be congestion, end of congestion, or about to end of congestion.

[0094] The recommended encoding rate refers to an encoding rate recommended by the access network device according to the current network state, for example, ANBR. The recommended encoding rate can be determined by the access network device. For example, the access network device can determine the encoding rate corresponding to the current network state by looking up a table according to the SINR of the reference signal, and the encoding rate is the recommended encoding rate.

[0095] The application server can also receive the transmission type sent by the access network device, and the transmission type is used to identify uplink transmission or downlink transmission. Correspondingly, the recommended encoding rate received by the application server can be a recommended encoding rate for uplink transmission, or a recommended encoding rate for downlink transmission.

[0096] S504. The application server adjusts the encoding rate of the resource transmitted between the application server and the terminal according to the recommended encoding rate.

[0097] Specifically, the application server can adjust the encoding rate of the corresponding transmission type resource (such as uplink resource or downlink resource) transmitted between the application server and the terminal to the recommended encoding rate according to the transmission type. The adjustment process of uplink transmission and downlink transmission is described in detail below.

[0098] When the transmission type is uplink transmission, the application server can send TMMBR to the terminal according to the recommended encoding rate. The TMMBR includes the recommended encoding rate. The TMMBR is used to request to adjust the encoding rate of the terminal to the recommended encoding rate.

[0099] When the transmission type is downlink transmission, the application server can send a temporary maximum media bit rate notification (TMMBN) to the terminal according to the recommended encoding rate. The TMMBN can include the recommended encoding rate. The TMMBN is used to notify the terminal that the server-side encoding rate is adjusted to the recommended encoding rate.

[0100] Further, the application server can also receive the flow identifier of the data stream sent by the access network device, for example, QFI. Accordingly, the application server can adjust the encoding rate of the resource carried by the corresponding QoS flow according to the QFI, specifically to the recommended encoding rate.

[0101] Based on the above description, the application provides an encoding rate adjustment method. In this method, the application server can receive the recommended encoding rate sent by the RAN side through the core network. The application server does not need to speculate the rate that should be adjusted, but adjusts adaptively according to the recommended encoding rate, which improves the adjustment effect and guarantees the user experience.

[0102] Next, the encoding rate adjustment method of the application will be described in combination with specific application scenarios.

[0103] Referring to a signaling flowchart of an encoding rate adjustment method shown in FIG. 6, the method includes:

[0104] S602, the access network device detects the network state. When the network state is congestion, about to be congested, end of congestion, about to end of congestion, S604 is performed.

[0105] S604, the AMF sends a PDU session resource notification to the SMF.

[0106] The PDU session resource notification can be PDU session resource notify, and the PDU session resource notify can include the recommended encoding rate such as ANBR. Further, the PDU session resource notify can also include the transmission type, which can take the value of UL or DL, wherein UL represents uplink transmission and DL represents downlink transmission. In addition, the PDU session resource notify can also include the flow identifier of the data stream, for example, QFI. Based on this, the PDU session resource notify can be represented as PDU session resource notify (QFI, UL / DL, ANBR).

[0107] S606, the AMF sends an N4 session update request to the SMF.

[0108] In the process of establishing a PDU session, an N4 session (N4 session) is also established, also known as a Packet Forwarding Control Protocol (PFCP) session. The PFCP session is a communication session between the SMF and the UPF. The PFCP session defines a series of UPF actions on the PDU using PFCP, including but not limited to identification, forwarding, caching, marking, reporting, and multi-access.

[0109] The AMF can send an N4 session update request to the SMF, which can be denoted as N4 session update req. The N4 session update req can include the flow identity, the transmission type, and the recommended encoding rate of the data flow. The N4 session update req can be denoted as N4 session update req (QFI, UL / DL, ANBR).

[0110] In S608, the SMF sends a policy control update message to the PCF.

[0111] Specifically, the SMF can invoke the Npcf_SMPolicyControl_update service operation of the PCF to send the policy control update message to the PCF. The policy control update message can include the flow identity, the transmission type, and the recommended encoding rate of the data flow. For example, the policy control update message can be denoted as npcf_smpolicyControl_update (QFI, UL / DL, ANBR).

[0112] In S610, the PCF sends a policy authorization notification to the NEF.

[0113] The policy authorization notification can include the flow identity, the transmission type, and the recommended encoding rate of the data flow. Based on this, the policy authorization notification can be denoted as npfc_policy_authorization_notify (QFI, UL / DL, ANBR).

[0114] In S612, the NEF sends a session notification to the AF. When the transmission type in the session notification is uplink transmission, S614 is performed. When the transmission type in the session notification is downlink transmission, S616 is performed.

[0115] Specifically, the NEF can invoke the session interface with the AF to send the session notification. The session notification includes the flow identity, the transmission type, and the recommended encoding rate of the data flow. The session notification can be denoted as nnef_afsessionwithQos_Notfiy (QFI, UL / DL, ANBR).

[0116] S614, the AF sends the TMMBR to the UE.

[0117] The TMMBR can include a recommended coding rate, which can be a new coding rate for the uplink transmission process, denoted as UL new codec. The TMMBR is used to request the terminal to adjust the coding rate to the recommended coding rate.

[0118] S616, the AF sends the TMMBN to the UE.

[0119] The TMMBN can include a recommended coding rate, which can be a new coding rate for the downlink transmission process, denoted as DL new codec. The TMMBN is used to inform the terminal that the network side has adjusted the coding rate to the recommended coding rate.

[0120] FIG. 6 illustrates an example of adjusting the coding rate by the access network device transmitting the recommended coding rate through the control plane of the core network, and the following illustrates an example of adjusting the coding rate by the access network device transmitting the recommended coding rate through the user plane of the core network.

[0121] Referring to a signaling flowchart of a method for adjusting the coding rate shown in FIG. 7, the method includes:

[0122] S702, the access network device detects the network state. When the network state is congestion, about to be congested, end of congestion, about to end of congestion, S704 is performed.

[0123] S704, the access network device sends uplink data to the UPF.

[0124] The uplink data (UL data) can be encapsulated by the General Packet Radio Service Tunnelling Protocol (GTP). The GTP can be decomposed into multiple independent protocols, such as GTP-C and GTP-U. The GTP-U is used to transmit user data between the wireless access network and the core network within the GPRS core network.

[0125] The recommended coding rate, such as ANBR, can be included in the GTP-U header of the uplink data. Further, the transmission type can also be included in the GTP-U header of the uplink data. The transmission type can take the value of UL or DL, indicating that the recommended coding rate is the recommended coding rate for uplink transmission or the recommended coding rate for downlink transmission.

[0126] S706, when the AF is not in the trusted domain of the core network, the UPF sends an event exposure notification to the NEF.

[0127] The event exposure notification can include a recommended encoding rate, such as ANBR. Further, the event exposure notification can also include a transmission type. Based on this, the event exposure notification can be represented as Nupf_EventExposure_Notify (UL / DL, ANBR).

[0128] S708, the NEF sends an event exposure notification to the AF.

[0129] The NEF can invoke an interface with the AF to send an event exposure notification to the AF. The event exposure notification can include a recommended encoding rate, such as ANBR. Further, the event exposure notification can also include a transmission type. Based on this, the event exposure notification can be represented as Nnef_EventExposure_Notify (UL / DL, ANBR).

[0130] S710, when the AF is in the trust domain of the core network, the UPF sends an event exposure notification to the AF.

[0131] Wherein, the AF is in the trust domain of the core network, indicating that the AF is a trusted device. The UPF can directly send an event exposure notification including a recommended encoding rate to the AF. Further, the event exposure notification can also include a transmission type. Wherein, the event exposure notification sent by the UPF can be represented as Nupf_EventExposure_Notify (UL / DL, ANBR).

[0132] S712, when the transmission type is uplink, the AF sends a TMMBR to the UE.

[0133] The TMMBR can include a recommended encoding rate, which can be a new encoding rate for the uplink transmission process, denoted as UL new codec. The TMMBR is used to request the terminal to adjust the encoding rate to the recommended encoding rate.

[0134] S714, when the transmission type is downlink, the AF sends a TMMBN to the UE.

[0135] The TMMBN can include a recommended encoding rate, which can be a new encoding rate for the downlink transmission process, denoted as DL new codec. The TMMBN is used to notify the terminal that the network side has adjusted the encoding rate to the recommended encoding rate.

[0136] FIG. 8 is an example of a structure of an electronic device according to an embodiment of the present application. The electronic device can be a first device, including but not limited to an access network device such as a base station. FIG. 8 shows a simplified schematic diagram of a base station structure. The base station includes a 810 part, a 820 part, and a 830 part. The 810 part is mainly used for baseband processing, control of the base station, etc. The 810 part is usually the control center of the base station, which can be referred to as a processor, and is used to control the base station to perform the processing operations of the first device side in the above method embodiments. The 820 part is mainly used for storing computer program codes and data. The 830 part is mainly used for transceiving radio frequency signals and converting radio frequency signals and baseband signals. The 830 part can be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. The transceiver module of the 830 part, which can also be referred to as a transceiver or a transceiver, etc., includes an antenna 833 and a radio frequency circuit, which is not shown in FIG. 8, wherein the radio frequency circuit is mainly used for radio frequency processing. Optionally, the devices in the 830 part for implementing the receiving function can be regarded as a receiver, and the devices for implementing the sending function can be regarded as a transmitter, i.e., the 830 part includes a receiver 832 and a transmitter 831. The receiver can also be referred to as a receiving module, a receiver, or a receiving circuit, etc., and the transmitter can be referred to as a transmitting module, a transmitter, or a transmitting circuit, etc.

[0137] The 810 part and the 820 part can include one or more single boards, and each single board can include one or more processors and one or more memories. The processors are used to read and execute the programs in the memories to implement baseband processing functions and control of the base station. If there are multiple single boards, the single boards can be interconnected to enhance the processing capability. As an optional implementation, the multiple single boards can share one or more processors, or share one or more memories, or share one or more processors at the same time.

[0138] For example, in an implementation, the transceiver module of the 830 part is used to perform the transceiving-related processes performed by the base station, etc. network device in the above method embodiments. The processor of the 810 part is used to perform the processing-related processes performed by the base station in the above method embodiments.

[0139] It should be understood that FIG. 8 is only an example and not limiting, and the above network device including the processor, the memory, and the transceiver can not depend on the structure shown in FIG. 8.

[0140] FIG. 9 is another example of a structure of an electronic device according to an embodiment of the present application. The electronic device can be a second device, which can be an application server. The application server is a server that deploys or runs application services. As shown in FIG. 9, the server can include a processor 310, an external memory interface 320, an internal memory 321, and a wireless communication module 360, etc.

[0141] It can be understood that the structure illustrated in the embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device can include more or fewer components than those illustrated, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0142] The processor 310 can include one or more processing units, for example: the processor 310 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices, or can be integrated in one or more processors.

[0143] It can be understood that the interface connection relationship between the modules illustrated in the embodiment is only illustrative and does not constitute a structural limitation on the electronic device. In another embodiment of the present application, the electronic device can also use different interface connection modes in the above embodiments, or a combination of multiple interface connection modes.

[0144] The external memory interface 320 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external storage card communicates with the processor 310 through the external memory interface 320 to realize the data storage function. For example, save music, video and other files in the external storage card.

[0145] The internal memory 321 can be used to store computer executable program codes, the executable program codes including instructions. The processor 310 performs various function applications and data processing of the electronic device by running the instructions stored in the internal memory 321. The internal memory 321 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required for a function, such as an application program required for a sound play function, an image play function, etc. The data storage area can store data created during the use of the electronic device, such as audio data, a phone book, etc. In addition, the internal memory 321 can include a high-speed random access memory, and can further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 310 performs various function applications and data processing of the electronic device by running the instructions stored in the internal memory 321 and / or the instructions stored in the memory provided in the processor.

[0146] The wireless communication function of the electronic device can be implemented through the wireless communication module 360, etc.

[0147] In addition, an operating system, such as an iOS operating system, an Android operating system, a Windows operating system, etc., is run on the above-described components. An application program can be installed and run on the operating system. It can be clearly understood by those skilled in the art that, for the convenience and brevity of description, the explanation and beneficial effects of the related content in any one of the above-provided electronic devices can refer to the corresponding method embodiments provided above, and will not be described herein.

[0148] The present application also provides a communication system, which can include a first device, such as a network device, e.g., a base station, as shown in FIG. 8, and a second device, such as an application server, as shown in FIG. 9.

[0149] In the present application, the terminal or the application server can include 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 can include a central processing unit (CPU), a memory management unit (MMU), and a memory, etc. The memory is also referred to as the main memory. The operating system of the operating system layer can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system, etc. The application layer can include a browser, a phonebook, a word processing software, an instant messaging software, etc.

[0150] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and module can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0151] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are merely illustrative, for example, the division of the modules is only a logical function division, and actual implementation can have another division manner, for example, a plurality of modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the modules or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0152] The modules described as separate components can or can not be physically separated, and the components shown as modules can or can not be physical modules, i.e., can be located in one place or distributed to a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment.

[0153] In addition, the functional modules in each embodiment of the present application can be integrated into one processing module, or each module can exist physically, or two or more modules can be integrated into one module. The above integrated module can be realized in the form of hardware or in the form of a software functional module.

[0154] The integrated module, if realized in the form of a software functional module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially contribute to or the whole or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing a computer device, such as a personal computer, a server, or a network device, to execute all or part of the processes of the methods described in each embodiment of the present application. The foregoing storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

[0155] The above-described embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A coding rate adjustment method, characterized in that: The method comprises: The access network device detects a network status, where the network status is used to represent a connection status of the access network device in uplink transmission or downlink transmission; When the network state is congested, about to be congested, ended in congestion, or about to end in congestion, the access network device sends a recommended coding rate to the application server through the core network, so that the application server adjusts the coding rate of resources transmitted between the application server and the terminal according to the recommended coding rate; The recommended coding rate is determined by the access network device.

2. The method according to claim 1, characterized in that The access network device sends the recommended coding rate to the application server through the core network, including: The access network device sends the recommended coding rate to the application server through the control plane network element of the core network, and the control plane network element includes the access and mobility management function AMF network element, the session management function SMF network element, the policy control function PCF network element or the network open function NEF network element.

3. The method according to claim 2, characterized in that The access network device sends the recommended coding rate to the application server through the core network, including: The access network device sends a protocol data unit PDU session resource notification to the AMF network element, where the PDU session resource notification includes a recommended coding rate, and the AMF network element is used to transmit the recommended coding rate through a session update request.

4. The method according to claim 1, wherein The access network device sends the recommended coding rate to the application server through the core network, including: The access network device sends the recommended coding rate to the application server through the user plane network element of the core network, and the user plane network element includes a user plane function UPF network element or a network open function NEF network element.

5. The method according to claim 4, characterized in that The access network device sends the recommended coding rate to the application server through the user plane network element of the core network, including: The access network device sends uplink data to the UPF network element, the uplink data is encapsulated using the Packet Radio Tunneling Protocol GTP, the header file of the uplink data includes the recommended coding rate, and the UPF network element is used to transmit the recommended coding rate to the application server.

6. The method according to claim 5, characterized in that The UPF network element is used to send the recommended coding rate to the application server when the application server is within the trust domain of the core network, and to send the recommended coding rate to the NEF network element when the application server is not within the trust domain of the core network. The NEF network element sends the recommended coding rate to the application server.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The access network device sends a transmission type to the application server, where the transmission type includes uplink transmission or downlink transmission; When the transmission type is uplink transmission, the application server sends a temporary maximum media bit rate request TMMBR to the terminal according to the recommended coding rate, where the TMMBR includes the recommended coding rate; When the transmission type is downlink transmission, the application server sends a temporary maximum media bit rate notification TMMBN to the terminal according to the recommended coding rate, where the TMMBN includes the recommended coding rate.

8. The method according to any one of claims 1 to 7, characterized in that The access network device sends the recommended coding rate to the application server through the core network, including: The access network device sends a flow identifier of the data flow and a recommended coding rate corresponding to the flow identifier to the application server through the core network.

9. A coding rate adjustment method, characterized in that: The method comprises: receiving a recommended coding rate sent by an access network device when the access network device detects that the network state is congested, about to be congested, has ended congestion, or is about to end congestion, where the network state is used to represent a connection state of the access network device in uplink transmission or downlink transmission, and the recommended coding rate is determined by the access network device; According to the recommended coding rate, the coding rate of the resource transmitted between the application server and the terminal is adjusted.

10. The method according to claim 9, characterized in that The method further comprises: receiving a transmission type sent by the access network device, where the transmission type includes uplink transmission or downlink transmission; The adjusting, according to the recommended coding rate, the coding rate of resources transmitted between the application server and the terminal includes: When the transmission type is uplink transmission, sending a temporary maximum media bit rate request TMMBR to the terminal according to the recommended coding rate, where the TMMBR includes the recommended coding rate; When the transmission type is downlink transmission, a temporary maximum media bit rate notification TMMBN is sent to the terminal according to the recommended coding rate, where the TMMBN includes the recommended coding rate.

11. An access network device, characterized in that: The access network equipment includes: Memory for storing computer programs or computer instructions; A processor, configured to execute the computer program or computer instructions stored in the memory, so that the access network device performs the method according to any one of claims 1 to 8.

12. An application server, characterized in that: The application server includes: Memory for storing computer programs or computer instructions; A processor is configured to execute the computer program or computer instructions stored in the memory, so that the application server executes the method according to claim 9 or 10.

13. A communication system, characterized in that: The system includes an access network device and an application server, wherein the access network device is configured to execute the method according to any one of claims 1 to 8, so that the application server adjusts the coding rate.

14. A computer storage medium for storing a computer program, wherein when the computer program is executed, the computer program is used to implement the method according to any one of claims 1 to 10.

Citation Information

Patent Citations

  • Communication method and device

    CN115865811A

  • Communication method and device

    CN116866981A

  • Information transmission method, network system and storage medium

    CN117641439A

  • Coding rate adjusting method and equipment

    CN118101134A