WO2023185552A1 - 通信方法和装置 - Google Patents

通信方法和装置 Download PDF

Info

Publication number
WO2023185552A1
WO2023185552A1 PCT/CN2023/082830 CN2023082830W WO2023185552A1 WO 2023185552 A1 WO2023185552 A1 WO 2023185552A1 CN 2023082830 W CN2023082830 W CN 2023082830W WO 2023185552 A1 WO2023185552 A1 WO 2023185552A1
Authority
WO
WIPO (PCT)
Prior art keywords
congestion
data packet
access network
congestion information
network device
Prior art date
Application number
PCT/CN2023/082830
Other languages
English (en)
French (fr)
Inventor
高国娟
周汉
魏鑫鹏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023185552A1 publication Critical patent/WO2023185552A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and device.
  • Embodiments of the present application provide a communication method and device, which can provide congestion detection and control for implementing media streaming services, thereby ensuring the normal operation of network transmission.
  • a communication method includes: the access network device performs congestion detection on the first data flow; the access network device sends a first data packet to the user plane function according to the congestion detection result.
  • the first data packet The GTP-U header of the tunnel protocol user plane includes congestion information, or the access network device sends the first data packet to the user equipment UE according to the congestion detection result, and the service data adaptation protocol SDAP layer of the first data packet includes congestion information.
  • the information is used by the server to adjust the rate at which the first data stream is sent.
  • congestion information includes information on data transmission status determined by network equipment after congestion detection of data flows, such as queue delay value, packet loss number or packet loss rate, buffer size or buffer ratio information, reporting period nature, congestion level, speed reduction ratio, etc.
  • the congestion information may also refer to information indicating the data transmission status, or may refer to relevant information indicating whether there is congestion or congestion level, which is not limited in the embodiments of the present application.
  • the access network equipment performs congestion detection on data packets, so that it can sense the congestion situation on the network side, and avoids the problem of inaccurate algorithm caused by only detecting and judging network congestion on the terminal and server sides. ; Moreover, the access network device sends congestion information to the UPF through the GTP-U header of the data packet or to the UE through the SDAP layer according to the congestion detection result, so that the congestion information can be flexibly and quickly fed back to the server through the UPF or UE. This can provide congestion detection and control for media streaming services and ensure the normal operation of network transmission.
  • the user function may be a UPF network element.
  • the access network device receives the data flow identifier of the first data flow.
  • the access network device performs congestion detection on the first data flow according to the data flow identifier.
  • the access network device can also receive a congestion identifier.
  • the congestion identifier can be understood as being used by the access network device to extend congestion information in the detected data packets after performing congestion detection on the data flow, or it can also be understood as being used to indicate congestion detection.
  • the access network device performs congestion detection on the first data flow according to the data flow identifier and/or the congestion identifier.
  • the access network device can determine to perform congestion detection on the data flow based on the congestion identifier or the data flow identifier, and feed back the congestion detection results to the server.
  • the server can flexibly determine the data flows that require congestion detection, and ensure that congestion information is fed back to the server under the instruction of the congestion flag, ensuring that the server can provide congestion detection and control for media streaming services and ensure the normal operation of network transmission.
  • the congestion information includes first congestion information and second congestion information, where the first congestion information is congestion information between the access network device and the user plane function, and the second congestion information is the access Congestion information between network equipment and UE.
  • the congestion information sent by the access network device includes congestion information between the access network device and the user plane function and air interface congestion information, which helps the server to adjust the sending rate of data packets in a targeted manner.
  • the access network device determines that the congestion detection result satisfies the first condition; the access network device sends the second data packet to the user plane function or to the UE.
  • the first condition may include specific parameter information corresponding to the congestion detection result.
  • the access network device determines the congestion level based on the congestion detection result, and the feedback condition is congestion level #1, then the access network device can determine whether the congestion level in the detection result meets the congestion level #1, and if so, notify the UPF Or the UE sends a data packet. If it is not satisfied, it does not send the data packet or prohibits or stops sending the data packet.
  • the access network equipment only sends congestion information to the server when it determines that the detection results meet certain conditions, so that the server directly determines specific adjustment parameters based on the congestion information, improving adjustment efficiency.
  • the access network device receives the first data packet from the user plane function, and the first data packet includes the data flow identifier; or the access network device receives the congestion detection information from the SMF network element, and the congestion detection information is received by the access network device.
  • Detection information includes data flow identification.
  • the access network equipment can flexibly obtain the data flow identifier.
  • the first data flow is a quality of service QoS flow bound to the congestion detection policy control and charging PCC rule in the protocol data unit session.
  • the first data packet or the second data packet is a data packet for data flow transmission, or the first data packet or the second data packet is an access network device or a user plane functional network element. Generated monitoring data packets.
  • the congestion detection information includes at least one of queue delay, congestion reporting time, packet loss rate, buffer size, periodicity, congestion level, and speed reduction ratio.
  • the data packets used by the access network equipment for congestion detection may be downlink data packets used to transmit data flow data, or may be data packets used for congestion detection or virtual empty packets (the data packets or empty packets may does not carry data of the data stream), the embodiment of the present application does not limit this.
  • the access network equipment can perform congestion detection on any data packet. It does not have to wait for the data packet of the transmission service to perform congestion detection, so that the congestion status can be fed back to the server in a timely manner.
  • the congestion information includes at least one of the queue delay and threshold delay ratio, packet loss ratio, buffer size ratio, congestion level, and speed reduction ratio.
  • the first data packet and the second data packet are the same, or the first data packet and the second data packet are different.
  • a communication method which method includes: the user plane function can receive a first data packet from the access network device, and the tunnel protocol user plane GTP-U header of the first data packet includes first congestion information; The user plane function sends second congestion information to the server according to the first congestion information, and the second congestion information is used by the server to adjust the rate at which the first data stream is sent.
  • the first congestion information is congestion information of the first data flow.
  • the method may be executed by the user plane function, or by a component of the user plane function, such as a processor or a chip.
  • the user plane function sends congestion information to the server through uplink or downlink data packets.
  • the congestion information is used by the server to adjust the rate of sending data streams, so that the congestion information can be flexibly and quickly sent to the server through uplink or downlink data packets. It can provide congestion detection and control for the implementation of media streaming services, thereby ensuring the normal operation of network transmission.
  • the data packets received by the user plane function from the access network device include congestion information in the GTP-U header.
  • the protocol stack of the access network device and the user plane function itself has a GTP-U layer.
  • the access network device and the user plane The function can transmit data packets through this protocol stack, but there is no GTP-U layer in the upstream transmission protocol stack of the user plane function. Therefore, the user plane function receives the first data packet from the access network device and obtains the congestion information from the GTP-U header. Finally, the data packet can be marked and sent to the server.
  • the user plane function sends a second data packet to the server, and the second data packet includes second congestion information.
  • the user plane function sends the second congestion information to the server through the second data packet.
  • the user plane function sends the second congestion information to the server through the user equipment UE.
  • UPF can transmit congestion information through downlink data packets, and the implementation of the feedback mechanism is more flexible.
  • the user plane function sends a downlink data packet to the UE, and the downlink data packet includes the second congestion information.
  • the user plane function sends the second congestion information to the server through the session management function or the network opening function.
  • the user plane function determines that the congestion detection result satisfies the first condition; or determines that the first congestion information satisfies the first condition; and the user plane function sends the second congestion information to the server.
  • the user plane function determines that the detection result or the first congestion information meets certain conditions before sending congestion information to the server, so that the server directly determines specific adjustment parameters based on the second congestion information, improving adjustment efficiency.
  • the first data packet is a data packet of data stream transmission data or a monitoring data packet generated by the access network device or user plane function.
  • the access network equipment can perform congestion detection on any data packet. It does not have to wait for the data packet of the transmission service to perform congestion detection, so that the congestion status can be fed back to the server in a timely manner.
  • the congestion information includes at least one of the queue delay and threshold delay ratio, packet loss ratio, buffer size ratio, congestion level, and speed reduction ratio.
  • the first data packet and the second data packet are the same, or the first data packet and the second data packet are the same.
  • the packets are different.
  • a communication method includes: the terminal device UE receives a first data packet, the GTP-U header of the first data packet includes first congestion information, or the SDAP layer of the first data packet Including first congestion information, the first congestion information is used by the server to adjust the sending rate of the data stream; the UE sends second congestion information to the server according to the first congestion information.
  • the method may be executed by the terminal device, or by a component of the terminal device, such as a processor or a chip.
  • the terminal device includes congestion information in the GTP-U header or SDAP layer in the data packet received from the access network device, and further sends the congestion information to the server, thereby notifying the server of the access network device's awareness.
  • the congestion situation on the network side avoids the problem of inaccurate algorithm caused by only detecting and judging network congestion on the client and server side, and enables the server to adjust the data sending rate according to the congestion situation to ensure the normal operation of network transmission. .
  • the UE receives a first data packet from the user plane function, and the GTP-U header of the first data packet includes first congestion information.
  • the UE receives the data packet including the first congestion information in the GTP-U header from the user plane function, and further sends the congestion information to the server.
  • the UE receives a first data packet from the access network device, and the SDAP layer of the first data packet includes first congestion information.
  • the UE receives a data packet including first congestion information at the SDAP layer from the access network device, and further sends the congestion information to the server.
  • the UE sends the second congestion information to the server through the modem.
  • a communication device in a fourth aspect, includes: a processing unit for performing congestion detection on the first data stream; a transceiver unit for sending a first data packet to the user plane function according to the congestion detection result.
  • the tunnel protocol user plane GTP-U header of the data packet includes congestion information, or is also used to send the first data packet to the user equipment UE according to the congestion detection result, and the service data adaptation protocol SDAP layer of the first data packet includes congestion information,
  • the congestion information is used by the server to adjust the rate at which the first data stream is sent.
  • the processing unit performs congestion detection on data packets, so that it can sense the congestion situation on the network side, and avoids the problem of inaccurate algorithm caused by only detecting and judging network congestion on the client and server sides; and , the transceiver unit sends congestion information to the UPF through the GTP-U header of the data packet or to the UE through the SDAP layer according to the congestion detection result, which enables the congestion information to be flexibly and quickly fed back to the server through the user plane function or the UE, thereby It can provide congestion detection and control for the implementation of media streaming services, thereby ensuring the normal operation of network transmission.
  • the transceiver unit is also configured to receive a data flow identifier of the first data flow.
  • the access network device performs congestion detection on the first data flow according to the data flow identifier.
  • the access network device receives the congestion identifier.
  • the access network device performs congestion detection on the first data flow according to the data flow identifier and/or the congestion identifier.
  • the processing unit can determine to perform congestion detection on the data flow based on the congestion identification or the data flow identification, and feed back the congestion detection results to the server. This enables us to flexibly determine the data flows that require congestion detection. And under the instruction of the congestion flag, it can ensure that the congestion information is fed back to the server, ensuring that the server can provide congestion detection and control for the media streaming service and ensure the normal operation of the network transmission.
  • the congestion information includes first congestion information and second congestion information.
  • the first congestion information is congestion information between the access network device and the user plane function
  • the second congestion information is between the UE and the access network device. Congestion information between networked devices.
  • the congestion information sent by the transceiver unit includes congestion information between the access network equipment and the user plane function and air interface congestion information, which helps the server to adjust the sending rate of data packets in a targeted manner.
  • the processing unit is also configured to determine that the congestion detection result satisfies the first condition; the transceiver unit sends the first data packet to the user plane function or the UE.
  • the transceiver unit when the processing unit determines that the detection results meet certain conditions, the transceiver unit sends congestion information to the server, so that the server directly determines specific adjustment parameters based on the congestion information, improving adjustment efficiency.
  • the transceiver unit is specifically configured to receive a first data packet from the user plane function, where the first data packet includes a data flow identifier; or, the transceiver unit receives congestion detection information from the SMF network element, and the congestion detection The information includes data flow identification.
  • the transceiver unit can flexibly obtain the data flow identifier.
  • the first data packet is a data packet of data stream transmission data or a monitoring data packet generated by the access network device or user plane function.
  • the processing unit can perform congestion detection on any data packet, and does not have to wait for the data packet of the transmission service to perform congestion detection, so that the congestion status can be fed back to the server in a timely manner.
  • the congestion detection information includes at least one of queue delay, congestion reporting time, packet loss rate, buffer size, periodicity, congestion level, and speed reduction ratio.
  • the first data flow is a data flow bound to the quality of service QoS flow in the congestion detection policy control and charging PCC rule.
  • the congestion information includes at least one of the queue delay and threshold delay ratio, packet loss ratio, buffer size ratio, congestion level, and speed reduction ratio.
  • the first data packet and the second data packet are the same, or the first data packet and the second data packet are different.
  • a communication device configured to receive a first data packet from an access network device, where the tunnel protocol user plane GTP-U header of the first data packet includes first congestion information. ; The transceiver unit is also used to send second congestion information to the server based on the first congestion information, and the second congestion information is used by the server to adjust the rate at which the data stream is sent.
  • the transceiver unit sends congestion information to the server through uplink or downlink data packets.
  • the congestion information is used by the server to adjust the rate of sending data streams, and can provide congestion detection and control for the implementation of media streaming services, thereby ensuring network transmission time. of normal operation.
  • the device includes a processing unit configured to carry the second congestion information in the first data packet before the transceiver unit sends the second congestion information to the server.
  • the first data packet is an uplink data packet or Downstream data packets.
  • the transceiver unit is configured to send the second congestion information to the server through the user equipment UE. interest.
  • the transceiver unit can transmit congestion information through uplink data packets or downlink data packets, and the implementation of the feedback mechanism is more flexible.
  • the transceiver unit is specifically configured to send a downlink data packet to the UE, where the downlink data packet includes the second congestion information.
  • the transceiver unit is specifically configured to send the second congestion information to the server through the session management function or the network opening function.
  • the processing unit is also configured to determine that the congestion detection result or the first congestion information satisfies the first condition; the transceiver unit sends the congestion information to the server.
  • the processing unit only sends congestion information to the server when it determines that the detection results meet certain conditions, so that the server directly determines specific adjustment parameters based on the congestion information, improving adjustment efficiency.
  • the first data packet is a data packet of a data flow or a monitoring data packet generated by an access network device or a user plane function.
  • the processing unit can perform congestion detection on any data packet, and does not have to wait for the data packet of the transmission service to perform congestion detection, so that the congestion status can be fed back to the server in a timely manner.
  • the congestion information includes at least one of the queue delay and threshold delay ratio, packet loss ratio, buffer size ratio, congestion level, and speed reduction ratio.
  • a communication device in a sixth aspect, includes: a transceiver unit configured to receive a first data packet, the GTP-U header of the first data packet including first congestion information, or the SDAP of the first data packet.
  • the layer includes first congestion information, which is used by the server to adjust the sending rate of the first data flow; and the transceiver unit is also used to send second congestion information to the server according to the first congestion information.
  • the method may be executed by the terminal device, or by a component of the terminal device, such as a processor or a chip.
  • the data packet received by the transceiver unit includes congestion information in the GTP-U header or SDAP layer, and further sends the congestion information to the server, thereby notifying the server of the congestion situation on the network side perceived by the access network device.
  • the transceiver unit is specifically configured to receive a first data packet from the user plane function, and the GTP-U header of the first data packet includes first congestion information.
  • the transceiver unit specifically receives the data packet including the first congestion information in the GTP-U header from the user plane function, and further sends the congestion information to the server.
  • the transceiver unit is specifically configured to receive a first data packet from the access network device, where the SDAP layer of the first data packet includes first congestion information.
  • the transceiver unit is specifically configured to receive a data packet including first congestion information at the SDAP layer from the access network device, and further send the congestion information to the server.
  • the transceiver unit is also configured to send the second congestion information to the server through the modem.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method of the first aspect.
  • the device further includes a memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method of the second aspect.
  • the device further includes memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method of the third aspect.
  • the device further includes memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • a computer program product includes: a computer program (which may also be called a code, or an instruction).
  • a computer program which may also be called a code, or an instruction.
  • the computer program When the computer program is run, it causes the computer to execute the above first aspect, the second aspect or the third aspect. Any one of the three possible implementation methods.
  • a computer-readable storage medium stores a computer program (which can also be called a code, or an instruction). When run on a computer, it causes the computer to execute the above-mentioned first aspect, The method in any possible implementation manner of the second aspect or the third aspect.
  • a chip system including a processor for calling and running a computer program from a memory, so that a device installed with the chip system executes each implementation of the first aspect, the second aspect or the third aspect. method within the method.
  • a communication system in a thirteenth aspect, includes the device of the fourth aspect or the seventh aspect, and the device of the fifth aspect or the eighth aspect.
  • Figure 1 shows a schematic diagram of a communication system architecture 100 suitable for embodiments of the present application.
  • Figure 2 shows a schematic framework diagram suitable for the communication method provided by the embodiment of the present application.
  • Figure 3 shows a schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Figure 4 shows another schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Figure 5 shows another schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Figure 6 shows a schematic block diagram suitable for the communication device provided by the embodiment of the present application.
  • FIG. 7 shows a schematic architecture diagram suitable for a communication device provided by an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the terminal equipment in the embodiment of this application may refer to user equipment, access terminal, user unit, user station, mobile station, Mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communications equipment, user agent or user device.
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication device.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal device.
  • the network device may be a Global System of Mobile communication (GSM) system or a Code Division Multiple Access (CDMA) system. It can be a base station (Base Transceiver Station, BTS) in a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system (NodeB, NB), or an evolutionary base station (Evolutional) in an LTE system.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • WCDMA Wideband Code Division Multiple Access
  • NodeB NodeB
  • Evolutional evolutionary base station
  • NodeB, eNB or eNodeB or a wireless controller in a Cloud Radio Access Network (CRAN) scenario
  • the network device can be a relay station, access point, vehicle-mounted device, wearable device, and in the future
  • the embodiments of this application are not limited to network equipment in the network or network equipment in a future evolved PLMN network.
  • FIG. 1 a schematic structural diagram of a communication system 100 according to an embodiment of the present application is first briefly described with reference to FIG. 1 .
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but is not limited to: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), network exposure function (network exposure function) function, NEF), network storage function (NF repository function, NRF), policy control function (PCF), application function (AF), access and mobility management function (access and mobility management function, AMF), session management function (SMF), user equipment (UE), wireless access network equipment, user plane function (UPF), data network (DN).
  • NSF network slice selection function
  • AUSF authentication server function
  • UDM network exposure function
  • NEF network exposure function
  • NRF network storage function
  • PCF policy control function
  • AF application function
  • AF access and mobility management function
  • AMF session management function
  • SMS session management function
  • UE user equipment
  • UPF data network
  • DN data network
  • DN can be the Internet
  • NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, and UPF are network elements in the core network.
  • the core network can be called 5G core network (5G core network, 5GC or 5GCN).
  • UE It can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: mobile phones, tablet computers, notebook computers, PDAs, mobile internet devices (MID), wearable devices, virtual reality Virtual reality (VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, remote medical surgery wireless terminals, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones , cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistants, PDAs), handheld devices with wireless communication capabilities, computing devices Or other processing equipment connected to the wireless modem, wearable devices, terminal equipment in the 5G network or terminal equipment in the future evolved public land mobile communication network (public land mobile network, PLMN), etc., the embodiments of this application do not Not limited.
  • MID mobile internet
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine Interconnection, an intelligent network that interconnects things.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • (Radio) access network (R)AN) equipment It can provide authorized users in a specific area with the function of accessing the communication network. Specifically, it can include the 3rd generation partnership program (3rd generation partnership) Wireless network devices in project, 3GPP) networks may also include access points in non-3GPP (non-3GPP) networks. The following uses AN equipment representation for convenience of description.
  • AN equipment can adopt different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology.
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies may include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • AN equipment can be responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • QoS quality of service
  • AN equipment may include, for example, but is not limited to: macro base station, micro base station (also known as small station), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • AMF Mainly used for functions such as access control, mobility management, attachment and detachment.
  • SMF Mainly used for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation of terminal equipment, as well as session establishment, modification and release and QoS control.
  • IP Internet Protocol
  • UPF Mainly used for receiving and forwarding user plane data.
  • the UPF can receive user plane data from the DN and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN.
  • NEF Mainly used to safely open the services and capabilities provided by 3GPP network functions to the outside world.
  • PCF A unified policy framework mainly used to guide network behavior and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • AF Mainly used to provide services to the 3GPP network, such as interacting with PCF for policy control, etc.
  • NSF Network slice selection function
  • UDM Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.
  • DN Operator network mainly used to provide data services to UE.
  • the Internet For example, the Internet, third-party business networks, IP multimedia service (IMS) networks, etc.
  • IMS IP multimedia service
  • AUSF Mainly used for user authentication, etc.
  • NRF Mainly used to save network functional entities and description information of the services they provide.
  • each network element can communicate with each other through interfaces.
  • UE2 is connected to the AN device through a radio resource control (RRC) protocol, and the Uu interface is used to communicate between the UE and the AN device.
  • RRC radio resource control
  • the PC5 interface is used to communicate between UE1 and UE2.
  • the PC5 interface can be used for mutual discovery between UEs and the transmission of data and signaling between UEs.
  • N1 is the interface between UE2 and AMF
  • N2 is the interface between (R)AN and AMF, used for sending NAS messages, etc.
  • N3 is the interface between RAN and UPF, used for transmitting user Data on the interface, etc.
  • N4 is the interface between SMF and UPF, used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages
  • N6 interface is the interface between UPF and DN. Used to transmit user plane data, etc.
  • the N11 interface is the interface between AMF and SMF.
  • network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiments of the present application.
  • functions or network elements such as AMF, SMF, UPF, PCF, UDM, NSSF, and AUSF shown in Figure 1 can be understood as network elements used to implement different functions, and can, for example, be combined into network slices as needed.
  • These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • Figure 1 is only an application scenario of the embodiment of the present application, and the present application does not limit the application scenarios of this method.
  • the service-oriented architecture is taken as an example to describe the method provided by the embodiments of the present application in detail.
  • This application provides a communication method and device that can provide congestion detection and control for implementing media streaming services, thereby ensuring normal operation of network transmission and ensuring user experience.
  • Figure 2 is a schematic block diagram of a communication method provided by an embodiment of the present application.
  • the method 200 shown in Figure 2 can be used in the network architecture shown in Figure 1, and the method 200 can be executed by the access network device shown in Figure 1.
  • Method 200 includes the following steps:
  • S210 The access network device performs congestion detection on the first data flow.
  • the first data stream is the data stream to be detected.
  • the data packets used by the access network device for congestion detection may be downlink data packets used to transmit data flow data, or may be data packets used for congestion detection or virtual empty packets (the data packets or empty packets may not be The data carrying the data stream), the embodiment of the present application does not limit this.
  • the congestion detection results can be, for example, indicators such as downlink queue delay, packet loss, and buffer size.
  • the access network device calculates the congestion detection results of RAN-UE and UPF-RAN respectively based on the timestamp of GTP-U messages sent and received.
  • the access network equipment detects the congestion status between UPF and RAN by referring to the QoS monitoring related content in the 3GPP standard TS 23.501, which is not limited in the embodiments of this application.
  • the access network equipment may refer to the content in 3GPP standard TS 38.314 to detect the congestion status between RAN and UE, which is not limited in the embodiments of this application.
  • step S210 it may also include:
  • the access network device receives the first data flow identifier.
  • the access network device receives the data flow identifier of the data flow to be detected for congestion.
  • the access network device may perform congestion detection on the first data flow according to the data flow identifier.
  • the access network device is configured with one or more data flow identifiers related to congestion detection.
  • the access network device determines that the received data flow identifier The data flow corresponding to the received data flow ID needs to be checked for congestion.
  • the access network device receives a data flow identifier and a congestion identifier, and the congestion identifier is used to indicate that the data flow corresponding to the data flow identifier needs to undergo congestion detection, or the congestion identifier is used to indicate that feedback is required. Congestion information for this data flow. That is, the access network device can perform congestion detection on the data flow corresponding to the data flow ID based on the data flow ID and the congestion ID.
  • the access network device does not need to pre-configure certain data flows to be detected.
  • the congestion identifier may be a field that indicates whether congestion detection is required via true or false; or the congestion identifier may be a cell or message used to carry the data flow identifier, and the cell or message The type or name is related to congestion detection.
  • the field used to carry the congestion identifier can also be used to transmit congestion information after the access network device performs congestion detection. That is, the congestion flag is used by the access network equipment to feedback congestion information after detecting congestion on the data flow.
  • field #A is used as a congestion identifier. The access network device performs congestion detection on the data flow to obtain the congestion detection result, and determines the congestion information based on the detection result. This field #A is used to feed back the congestion level.
  • the above-mentioned access network equipment can receive the data flow identifier of the data flow to be checked for congestion from the core network equipment. Specifically, this can be achieved in the following ways:
  • the access network device receives a data packet from the UPF network element.
  • the data packet includes the above-mentioned data flow identifier and may also include a congestion identifier.
  • the data packet is a downlink data message
  • the GTP-U header of the downlink message includes a data flow identifier and a congestion identifier.
  • the access network device can perform congestion detection on the data packet based on the congestion identifier. That is, the access network device can perform congestion detection on the data flow (that is, the data packet carrying the congestion identifier) based on the congestion identifier.
  • the access network device may not consider the data flow identifier, but only determine whether the congestion result of the data packet needs to be calculated based on whether the data packet carries the congestion identifier.
  • the access network device receives congestion detection information from the SMF network element.
  • the congestion detection information includes the above-mentioned data flow identifier, and may also include a congestion identifier.
  • the congestion detection information may include at least one of queue delay, congestion reporting time, packet loss rate, buffer size, periodicity, congestion level, and speed reduction ratio. It may also include other parameters and data used to ensure congestion status and congestion information. The embodiments of the present application do not limit this.
  • the above data flow identifier may be the QFI of the QoS data flow.
  • the SMF binds the PCC rule to the QoS flow in the PDU session and defines the identifier of the data flow. It can be understood that the QoS flow is a QoS flow carrying a congestion identifier.
  • the QoS flow may be an existing QoS flow, or a newly established or modified QoS flow, which is not limited in the embodiments of the present application.
  • the access network device sends the first data packet to the user plane function UPF network element according to the congestion detection result.
  • the GTP-U header of the first data packet includes congestion information, or the access network device sends the user equipment UE according to the congestion detection result.
  • a second data packet is sent, and the SDAP layer of the second data packet includes congestion information.
  • GTP GPRS tunnel protocol
  • GTP-U GTP user plane part of GTP
  • T-PDU transport protocol data unit
  • GTP encapsulated user plane data unit GTP encapsulated user plane data unit
  • the service data adaptation protocol (SDAP) layer is a new protocol layer in NR (refer to 3GPP standard protocol 37.324).
  • the main functions of the SDAP layer include mapping between QoS flows and data radio bearers and marking QoS flow IDs (QFI) in downlink and uplink messages.
  • QFI QoS flow IDs
  • the first data packet and the second data packet may be the same or different, and are not limited in the embodiment of this application.
  • the above-mentioned first data packet or second data packet may be a data packet used to transmit data, or may be a data packet regularly established by the UPF and sent to the RAN, or a data packet regularly established by the RAN, for example, monitoring packets. ), or, dummy packet.
  • the access network device feeds back the congestion information to the server through the UPF or UE, so that the server can adjust the rate at which the data flow is sent based on the congestion information of the data flow.
  • the congestion information sent by the UPF or UE to the server and the congestion information received from the access network device can be the same or different (for example, changing the expression of the information when sending it to the server, or after secondary processing of the information) sent to the server).
  • the congestion information may include information on the data transmission status determined after the network device performs congestion detection on the data flow, for example, queue delay value, packet loss number or packet loss rate, buffer size or buffer ratio information, reporting periodicity , congestion level, speed reduction ratio, etc.
  • the congestion information may also refer to information indicating data transmission status.
  • the congestion information includes field #1, which is used to indicate that the queue delay is greater than a preset threshold, or the congestion information may also include field #2, This field #2 is used to indicate that the packet loss rate is greater than the preset threshold, etc. It may also refer to relevant information indicating whether there is congestion or congestion level.
  • the congestion information includes field #3, which is used to indicate the occurrence of congestion.
  • the congestion information may also include field #3, which is used to indicate the occurrence of congestion. Indicates higher congestion level, etc. The embodiments of the present application do not limit this.
  • the congestion information can reflect the congestion degree of the data flow, and can also be understood as the congestion information can reflect the transmission status of the data flow, which is conducive to the server side to obtain the transmission status of the data flow in real time and determine according to business level requirements. Whether the transmission rate needs to be adjusted.
  • the congestion information may include congestion information (hereinafter referred to as the first congestion information) between the UPF and the access network device (hereinafter referred to as the UPF-access network device), and may also include the congestion information between the UE and the access network device.
  • Air interface congestion information (hereinafter referred to as second congestion information) between access network devices (hereinafter referred to as UE-access network device).
  • the access network device determines the congestion information based on the congestion detection result.
  • the GTP-U header includes congestion information. It can be one or more bits in the GTP-U header used to carry congestion information, or it can be that the GTP-U header only extends one or more bits when it needs to carry congestion information. , the extended bits carry congestion information.
  • the SDAP layer includes congestion information, which can be one or more bits in the SDAP layer used to carry congestion information, or the SDAP layer can extend one or more bits only when it needs to carry congestion, and the extended bits are Carry congestion information.
  • congestion information can be one or more bits in the SDAP layer used to carry congestion information, or the SDAP layer can extend one or more bits only when it needs to carry congestion, and the extended bits are Carry congestion information.
  • the access network device may, before sending the first data packet to the UPF or to the UE, Determine whether the congestion detection results meet the corresponding feedback conditions.
  • the feedback condition can also be said to be a reporting condition.
  • the feedback condition can be preset by the AF/AS or by the access network device.
  • the feedback condition may include specific parameter information that the congestion detection result needs to satisfy.
  • the congestion information is sent.
  • the access network device obtains the congestion level based on the congestion detection result.
  • the feedback condition is congestion level #1
  • the access network device can determine whether the congestion level obtained based on the congestion detection result satisfies the congestion level #1. If so, then Send the first data packet to the UPF or UE. If the conditions are not met, the first data packet is not sent or the sending of the first data packet is prohibited or stopped.
  • the access network device obtains the speed reduction ratio based on the congestion detection result.
  • the feedback condition is the speed reduction ratio #1
  • the access network device can determine whether the speed reduction ratio obtained based on the congestion detection result satisfies the speed reduction ratio #1. , if satisfied, the first data packet is sent to the UPF or UE; if not satisfied, the first data packet is not sent.
  • AF/AS can further directly adjust the speed according to the speed reduction ratio to increase the adjustment speed of AF/AS.
  • the access network device can also directly determine whether the congestion detection result directly meets the specific parameter information to decide whether to send, not send, prohibit sending, or stop sending the first data packet, which will not be described in detail here.
  • the UPF network element receives the first data packet from the access network device.
  • the GTP-U header of the data packet includes congestion information.
  • the data packet may be an uplink data packet.
  • the UPF may Send the first data packet to the server.
  • the data packet can also be a downlink data packet, which is sent to the UE and sent to the server through the UE.
  • the UPF network element receives the first data packet from the access network device, the GTP-U header of the data packet includes congestion information, and the UPF sends the congestion information to the NEF (for example, through a capability opening notification ( Nupf_EventExposure_Notify) message), NEF then forwards the congestion information to AF/AS.
  • NEF for example, through a capability opening notification ( Nupf_EventExposure_Notify) message
  • NEF for example, through a capability opening notification ( Nupf_EventExposure_Notify) message
  • the congestion information sent by the UPF to the AF/AS and the congestion information received from the access network device can be the same or different (for example, changing the expression of the information when sending it to the server, or after secondary processing of the information) sent to AF/AS).
  • the UE receives the first data packet from the access network device, the SDAP layer of the data packet includes congestion information, and the terminal reports the congestion information to the AF/AS.
  • the terminal can forward the congestion information to the upper layer through the modem (MODEM) and send it to the AF/AS.
  • MODEM modem
  • the UPF may determine whether the congestion detection result meets the first condition before sending the congestion information to the AF/AS.
  • the access network device performs congestion detection on the data packet based on the congestion identifier and the data flow identifier, and sends congestion information to the UPF through the GTP-U header of the data packet according to the congestion detection result or to the UPF through the SDAP layer.
  • the UE sends congestion information, which is used by the server to adjust the rate of sending data streams, and can provide congestion detection and control for implementing media streaming services, thereby ensuring the normal operation of network transmission.
  • Figure 3 shows a schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Method 300 can be regarded as a specific implementation of method 200, and the method 300 can include the following steps.
  • message #1 includes a congestion information notification message, which is used to indicate a reporting method of congestion information to the AF/AS. It can be understood that the congestion information notification message can also be named with other message names, It can also be understood that the congestion information notification message is a logical summary of one or more pieces of information used to indicate a reporting manner of congestion information to the AF/AS.
  • the congestion information notification message may include notification cycle information (the period for reporting congestion information to AF/AS), notification time indication information (the time to report congestion information to AF/AS), and notification method information (reporting congestion information to AF/AS).
  • notification cycle information the period for reporting congestion information to AF/AS
  • notification time indication information the time to report congestion information to AF/AS
  • notification method information reporting congestion information to AF/AS.
  • the message #1 may include a flow description.
  • the flow description may include service flow quintuple, fully qualified domain name (FQDN), etc., which is not limited in the embodiment of this application.
  • the message #1 may be a subscription message.
  • PCF/NEF sends a subscription request message to AF/AS, and the subscription request message is used by AF/AS to send notification messages related to congestion information to PCF/NEF. Accordingly, the AS/AS receives the subscription request message.
  • PCF obtains the QoS parameters of the corresponding QoS flow based on the flow description included in message #1, and generates a PCC rule #A for congestion detection based on the QoS parameters.
  • SMF binds PCC rule #A to the QoS flow.
  • PCC rule #A may include information about data flow #A (or in other words, PCC rule #A defines data flow #A).
  • SMF can bind PCC rule #A to some or all existing QoS flows in the PDU session, thereby using the bound QoS flows as data flows to be detected for congestion.
  • the bound QoS flow can use the QFI before binding; when PCC rule #A includes QFI, the bound data flow can use the QFI in PCC rule #A.
  • SMF can also create a new QoS flow according to PCC rule #A.
  • This QoS flow can be used to transmit the data that needs to be detected for congestion for this PDU session.
  • the QoS flow can be identified using the QFI in PCC Rule #A.
  • message #2 includes congestion detection information, which may include QFI#A and congestion identification, and may also include one or more of flow description, or congestion information reporting time and other information.
  • congestion detection information may include QFI#A and congestion identification, and may also include one or more of flow description, or congestion information reporting time and other information.
  • the message #2 may be an N4 establishment request message or an N4 modification request message.
  • the SMF specifically extends the congestion detection related parameter information in the Context message through the N4 message.
  • UPF sends data packet #A to the access network device.
  • UPF carries congestion detection information through data packet #A.
  • the congestion detection information sent by the UPF to the access network device and the congestion detection information received from the SMF can be the same or different (for example, changing the expression of the information when sending it to the access network device, or performing a second step on the information). After processing, it is sent to the access network equipment).
  • UPF carries congestion detection information through user plane data packets.
  • UPF when UPF sends downlink data packets, it carries QFI#A and congestion identifier in the GTP-U packet header. It can also include information such as flow description, congestion information reporting time, packet sending or receiving timestamp, etc. one or more of.
  • steps S340(a1) and S340(a2) are one way for the SMF to send congestion detection information to the access network device (method one), and the following step S340(b) is another way (method two) , Method 1 or Method 2 can be executed by choosing one, and the embodiment of the present application does not limit this.
  • the SMF sends congestion detection information to the access network device.
  • the SMF sends the congestion detection information to the AMF, and the AMF sends the congestion detection information to the access network device.
  • the access network device receives the congestion detection information from the AMF.
  • the specific content of the congestion detection information please refer to step S340(a), which will not be described again here.
  • the SMF may send the congestion detection information to the AMF through an N11 message, and the N11 message may be an N1N2 message transfer (Namf_communication_N1N2MessageTransfer) message. Further, the AMF sends the congestion detection information to the access network device through the N2 message.
  • S350 The access network equipment performs congestion detection.
  • S350 The access network equipment performs congestion detection.
  • the access network device is pre-configured with the data flow identifier of the data flow that needs to be detected for congestion.
  • the access network device determines that it is necessary to perform congestion detection on data flow #A based on the fact that QFI#A in the congestion detection information belongs to the above-mentioned preconfigured data flow identifier, and detects data flow #A to obtain the congestion detection result.
  • the access network device determines that the QFI#A needs to perform congestion detection on the data flow #A based on the congestion identifier and the QFI#A, and detects the data flow #A to obtain the congestion detection result.
  • the congestion identifier is used to instruct congestion detection on the data stream corresponding to QFI#A and to feed back congestion information.
  • the way in which the access network device performs congestion detection may refer to step S210 in the method 200, which will not be described again here.
  • the access network device carries congestion information in the GTP-U header of the corresponding data packet for subsequent feedback of congestion information to AF/AS, so that AF/AS can respond based on the congestion information.
  • the data transfer rate is adjusted.
  • S360 The access network device sends congestion information to the UPF.
  • the access network device sends data packet #A to the UPF through the user, and the GTP-U header of the data packet #A includes congestion information.
  • the access network device may determine whether the congestion detection result satisfies the feedback condition (as an example of the first condition). This determination method is similar to the determination method in step S220 in method 200, and will not be described again.
  • the access network device determines the congestion information based on the congestion detection result.
  • the access network device carries congestion information in the GTP-U header of data packet #A, including but not limited to the following methods:
  • the GTP-U header of data packet #A includes congestion information.
  • the GTP-U header can specifically carry whether there is congestion, the number of congested data packets, the queue delay value, the number of lost packets, buffer size information, and periodicity. , congestion level, speed reduction ratio and other information;
  • GTP-U header of data packet #A needs to carry congestion information
  • the GTP-U extension header can specifically carry whether there is congestion or not, and data on congestion At least one of the number of packets, the ratio of queue delay to threshold delay, packet loss ratio, buffer ratio information, periodicity, congestion level, speed reduction ratio and other information.
  • UPF sends congestion information to AF/AS.
  • UPF sends congestion information to AF/AS through control.
  • the UPF reports the congestion information to the SMF through the N4 session message, and the SMF forwards the congestion information to the AF/AS, or the SMF forwards the congestion information to the AF/AS through the NEF.
  • the congestion information sent by SMF to AF/AS and the congestion information received from UPF can be the same or different (for example, changing the expression of the information when sending it to AF/AS, or performing secondary processing on the information before sending it to AF/AS).
  • the UPF sends the congestion information to the NEF through the capability exposure notification (Nupf_EventExposure_Notify) message, and the NEF forwards it to the AF/AS; or, the UPF may also directly send the congestion information to the NEF through the capability exposure notification (Nupf_EventExposure_Notify) message. AF/AS.
  • the UPF may determine whether the congestion detection result satisfies the feedback condition (as an example of the first condition). If the UPF determines that the congestion detection result meets the feedback conditions, the UPF will send the congestion information to the AF/AS. On the contrary, if the UPF determines that the congestion detection result does not meet the feedback conditions, it will not send the congestion information to the AF/AS or prohibit or stop sending it. the congestion information.
  • the feedback condition as an example of the first condition
  • step S220 The feedback conditions and specific judgment methods are similar to step S220, and will not be repeatedly described here.
  • AF/AS adjusts the sending rate based on congestion information.
  • AF/AS calculates and adjusts the rate of sending data packets based on congestion information.
  • the access network device performs congestion detection on the data packet based on the congestion identifier and the data flow identifier, and sends congestion information to the UPF through the GTP-U header of the data packet according to the detection result.
  • the congestion information is used for
  • the server adjusts the rate at which data streams are sent, which can provide congestion detection and control for implementing media streaming services, thereby ensuring the normal operation of network transmission.
  • Figure 4 shows another schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Figure 4 shows another schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Method 400 can be regarded as another specific implementation of method 200.
  • the UPF sends congestion information to the AF/AS through control.
  • the UPF may send congestion information to the AF/AS through data.
  • the specific steps of the method 400 are as follows.
  • Steps S410 to S460 are the same as steps S310 to S360, and will not be described again.
  • S470(a) and S480(a) are the specific steps for UPF to carry congestion information through uplink data packets (method 1);
  • S470(b), S480(b1) and S480(b2) are the steps for UPF to carry congestion information through downlink data packets.
  • Specific steps for data packets to carry congestion information step 2.
  • UPF carries congestion information in the uplink data packet.
  • UPF carries congestion information in uplink data packet #A.
  • UPF can carry congestion information in any layer of data packet #A, for example, it can be the GTP-U layer or the IP layer.
  • data packet #A may be an Ack data packet, or a data packet periodically established by UPF or RAN, such as monitoring packets or dummy packets.
  • the UPF can also determine whether the congestion detection result satisfies the feedback condition (as an example of the first condition). If UPF determines that the congestion detection result meets the feedback conditions, UPF will carry the congestion information in the upstream data packet #A. On the contrary, if UPF determines that the congestion detection result does not meet the feedback conditions, it will not carry the congestion detection information in the upstream data packet #A or It is prohibited or stopped for the upstream data packet #A to carry congestion detection information.
  • the feedback condition as an example of the first condition
  • the UPF can obtain the congestion detection result through the congestion information sent by the access network device, and the UPF can also receive the congestion detection result from the access network device. This is not limited in the embodiments of the present application.
  • the specific feedback condition that is, the judgment method is similar to that in step S370 in method 300. Please refer to the detailed description in step S370, which will not be described again here.
  • UPF sends congestion information to AF/AS.
  • UPF controls the sending of data packet #A to the AF/AS, carrying congestion information.
  • the specific sending method is the same as step S370 in method 300, and will not be described again.
  • UPF before sending data packet #A to AF/AS, UPF can also determine whether the feedback condition is met (as an example of the first condition). If UPF determines that the congestion detection result meets the feedback conditions, UPF sends data packet #A to AF/AS. On the contrary, if UPF determines that the congestion detection result does not meet the feedback conditions, it does not send data packet #A to AF/AS or prohibits, Stop sending packet #A to AF/AS.
  • the UPF can obtain the congestion detection result through the congestion information sent by the access network device, and the UPF can also receive the congestion detection result from the access network device. This is not limited in the embodiments of the present application.
  • the specific feedback condition that is, the judgment method is the same as that in step S370 in method 300. Please refer to the detailed description in step S370, which will not be described again here.
  • UPF carries congestion information in the downlink data packet.
  • UPF carries congestion information in the downlink data packet #A.
  • UPF can carry congestion information in any layer of data packet #A, for example, it can be the GTP-U layer or the IP layer.
  • UPF extends congestion information in the ECN identifier in the IP header of the downlink data packet.
  • UPF can also determine whether the feedback condition is met (as an example of the first condition) before the downlink data packet #A carries the congestion information. If UPF determines that the congestion detection result meets the feedback conditions, UPF will carry congestion information in the downstream data packet #A. On the contrary, if UPF determines that the congestion detection result does not meet the feedback conditions, it will not carry congestion information in the downstream data packet #A or prohibit it. , stop carrying congestion information in packet #A.
  • the UPF can obtain the congestion detection result through the congestion information sent by the access network device, and the UPF can also receive the congestion detection result from the access network device. This is not limited in the embodiments of the present application.
  • the specific feedback condition that is, the judgment method is the same as that in step S370 in method 300. Please refer to the detailed description in step S370, which will not be described again here.
  • UPF sends congestion information to the UE.
  • UPF sends data packet #A to the UE through the access network device, carrying congestion information.
  • the UPF may send data packet #A to the access network device through the N3 message, and further, the access network device sends data packet #A to the UE through the Uu interface.
  • the UPF may also determine whether the feedback condition is met (as an example of the first condition). If the UPF determines that the congestion detection result meets the feedback conditions, the UPF sends data packet #A to the UE. On the contrary, if the UPF determines that the congestion detection result does not meet the feedback conditions, it does not send data packet #A to the UE or prohibits or stops sending data packet #A to the AF/ AS sends packet #A.
  • the UPF can obtain the congestion detection result through the congestion information sent by the access network device, and the UPF can also receive the congestion detection result from the access network device. This is not limited in the embodiments of the present application.
  • step S370 the specific feedback condition, that is, the judgment method is the same as that in step S370 in method 300. Please refer to step S370. The detailed description in step S370 will not be repeated here.
  • the UE sends congestion information to the AF/AS.
  • the UE sends uplink data packet #A to the AF/AS, carrying congestion information.
  • AF/AS adjusts the sending rate based on congestion information.
  • AF/AS calculates and adjusts the rate of sending data packets based on congestion information.
  • the access network equipment performs congestion detection on the data packet based on the congestion identifier and the data flow identifier, and sends the congestion information to the UPF through the GTP-U header of the data packet according to the detection result.
  • the UPF passes the uplink and downlink data
  • the packet sends congestion information to the server.
  • the congestion information is used by the server to adjust the rate at which data streams are sent. It can provide congestion detection and control for implementing media streaming services, thereby ensuring the normal operation of network transmission.
  • Figure 5 shows another schematic interaction diagram suitable for the communication method provided by the embodiment of the present application.
  • Method 500 can be regarded as another specific implementation of method 200.
  • the GTP-U header of data packet #A includes congestion information, and in this embodiment, the SDAP layer of data packet #A may also include congestion information.
  • the specific steps of the method 500 are as follows.
  • Steps S510 to S540 are the same as steps S310 to S340, and will not be described again.
  • S550 The access network equipment performs congestion detection.
  • the access network device is pre-configured with the data flow identifier of the data flow that needs to be detected for congestion.
  • the access network device determines that it is necessary to perform congestion detection on data flow #A based on the fact that QFI#A in the congestion detection information belongs to the above-mentioned preconfigured data flow identifier, and detects data flow #A to obtain the congestion detection result.
  • the access network device determines that the QFI#A needs to perform congestion detection on the data flow #A based on the congestion identifier and the QFI#A, and detects the data flow #A to obtain the congestion detection result.
  • the congestion identifier is used to instruct congestion detection on the data stream corresponding to QFI#A and to feed back congestion information.
  • the way in which the access network device performs congestion detection may refer to step S210 in the method 200, which will not be described again here.
  • the access network device carries congestion information in the SDAP layer of the corresponding data packet for subsequent feedback of congestion information to AF/AS, so that AF/AS can process the data based on the congestion information.
  • the transmission rate is adjusted.
  • the access network device carries congestion information in the SDAP layer of data packet #A, including but not limited to the following methods:
  • the SDAP layer of data packet #A includes congestion information and can carry at least one of queue delay value, number of lost packets, buffer size information, periodicity, congestion level, speed reduction ratio and other information;
  • the SDAP layer of data packet #A includes whether it is congested, and carries at least one of the queue delay and threshold delay ratio, packet loss ratio, buffer ratio information, periodicity, congestion level, speed reduction ratio and other information.
  • the access network device sends congestion information to the UE.
  • the access network device sends congestion information to the UE through the SDAP layer.
  • the access network device sends data packet #A to the UE through the Uu interface, and the SDAP layer of the data packet #A includes congestion information.
  • the access network device may determine whether the feedback condition is met (as an example of the first condition). If the access network device determines that the congestion detection result meets the feedback conditions, the access network device sends the congestion information to the UE. On the contrary, if the access network device determines that the congestion detection result does not meet the feedback conditions, the access network device does not send the congestion information to the UE. Or prohibit or stop sending the congestion information.
  • the UPF can obtain the congestion detection result through the congestion information sent by the access network device, and the UPF can also receive the congestion detection result from the access network device. This is not limited in the embodiments of the present application.
  • the specific feedback condition that is, the judgment method is the same as that in step S370 in method 300. Please refer to the detailed description in step S370, which will not be described again here.
  • S570 The UE sends congestion information to the AF/AS.
  • the UE forwards the congestion information to the upper layer through the modem (MODEM).
  • MODEM modem
  • AF/AS adjusts the sending rate based on congestion information.
  • AF/AS calculates and adjusts the rate of sending data packets based on congestion information.
  • the access network device performs congestion detection on the data packet based on the congestion identifier and the data flow identifier, sends the congestion information to the UE through the SDAP layer of the data packet according to the detection result, and then forwards it to the upper layer server.
  • Congestion information is used by the server to adjust the rate at which data streams are sent, and can provide congestion detection and control for implementing media streaming services, thereby ensuring the normal operation of network transmission.
  • module may be a combination of software and/or hardware that implements a predetermined function.
  • apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
  • Figure 6 shows a schematic block diagram suitable for the communication device provided by the embodiment of the present application.
  • the device 600 includes a transceiver unit 610, which can be used to implement corresponding communication functions.
  • the transceiver unit 610 can also be called a communication interface or a communication unit.
  • the device 600 may also include a processing unit 620, which may be used for data processing.
  • the device 600 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 620 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of different devices in the network such as the actions of access network equipment and UPF network elements.
  • the device 600 is used to perform the actions performed by the access network equipment in each of the above method embodiments.
  • the processing unit 620 is configured to perform congestion detection on the first data flow; the transceiver unit 610 is configured to send the first data packet to the user plane function UPF network element according to the congestion detection result, and the tunnel protocol user plane of the first data packet is
  • the GTP-U header includes congestion information, or is also used to send the first data packet to the user equipment UE according to the congestion detection result.
  • the service data adaptation protocol SDAP layer of the first data packet includes congestion information. The congestion information is used by the server to adjust the sending. The rate of the first data stream.
  • the transceiver unit 610 is also configured to receive a data flow identifier of the first data flow.
  • the processing unit 620 is also configured to perform congestion detection on the first data flow according to the data flow identifier.
  • the transceiver unit 610 is also used to receive a congestion identifier.
  • the processing unit 620 is also configured to perform congestion detection on the first data flow according to the data flow identifier and/or the congestion identifier.
  • the congestion information includes first congestion information and second congestion information, where the first congestion information is congestion information between the access network device and the UPF network element, and the second congestion information is air interface congestion information.
  • the processing unit 620 is also configured to determine that the congestion detection result satisfies the first condition; the transceiver unit 610 sends the first data packet to the UPF network element, or sends the second data packet to the UE.
  • the transceiver unit 610 is specifically configured to receive the first data packet from the UPF network element, where the first data packet includes a data flow identifier; or, the transceiver unit 610 receives congestion detection information from the SMF network element, where the congestion detection information includes Data flow identifier.
  • the first data packet is a data packet of data stream transmission data or a monitoring data packet generated by the access network device or UPF network element.
  • the first data flow is a data flow bound to the quality of service QoS flow in the congestion detection policy control and charging PCC rule.
  • the congestion detection information includes at least one of queue delay, congestion reporting time, packet loss rate, buffer size, periodicity, congestion level, and speed reduction ratio.
  • the congestion information includes at least one of queue delay and threshold delay ratio, packet loss ratio, buffer size ratio, congestion level, and speed reduction ratio.
  • the first data packet and the second data packet are the same, or the first data packet and the second data packet are different.
  • the device 600 can implement the steps or processes performed by the access network equipment in the method embodiments according to the embodiments of the present application.
  • the device 600 can include steps for executing the steps in the embodiments shown in Figures 3, 4 and 5.
  • the device 600 is used to perform the actions performed by the UPF network element in each of the above method embodiments.
  • the transceiver unit 610 is configured to receive the first data packet from the access network device.
  • the tunnel protocol user plane GTP-U header of the first data packet includes the first congestion information; the transceiver unit 610 is also configured to receive the first data packet according to the first congestion information.
  • the information sends second congestion information to the server, and the second congestion information is used by the server to adjust the rate at which the data stream is sent.
  • the transceiver unit is specifically configured to send a second data packet to the server, where the second data packet includes the second congestion information.
  • the transceiving unit 610 is configured to send the second congestion information to the server through the user equipment UE.
  • the transceiver unit is specifically configured to send a downlink data packet to the UE, where the downlink data packet includes the second congestion information.
  • the transceiver unit is specifically configured to send the second congestion information to the server through the session management function or the network opening function.
  • the processing unit 620 is also configured to determine that the congestion detection result or the first congestion information satisfies the first condition; the transceiving unit 610 is configured to send the congestion information to the server.
  • the first data packet is a data packet of a data flow or a monitoring data packet generated by an access network device or a UPF network element.
  • the congestion information includes the ratio of queue delay to threshold delay, packet loss ratio, buffer size ratio, congestion At least one of level and deceleration ratio.
  • the device 600 can implement the steps or processes performed by the access network equipment in the method embodiments according to the embodiments of the present application.
  • the device 600 can include steps for executing the steps in the embodiments shown in Figures 3, 4 and 5.
  • the unit of the method executed by the UPF network element.
  • the device 600 is used to perform the actions performed by the terminal equipment UE in each of the above method embodiments.
  • the transceiver unit 610 is configured to receive a first data packet, the GTP-U header of the first data packet includes first congestion information, or the SDAP layer of the first data packet includes first congestion information, and the first congestion information The information is used by the server to adjust the sending rate of the data stream; the transceiver unit 610 is also used to send second congestion information to the server based on the first congestion information.
  • the transceiver unit 610 is specifically configured to receive the first data packet from the user plane function, and the GTP-U header of the first data packet includes the first congestion information.
  • the transceiver unit 610 is specifically configured to receive a first data packet from the access network device, where the SDAP layer of the first data packet includes first congestion information.
  • the transceiver unit 610 is also configured to send the second congestion information to the server through the modem.
  • the device 600 can implement the steps or processes performed by the access network equipment in the method embodiments according to the embodiments of the present application.
  • the device 600 can include steps for executing the steps in the embodiments shown in Figures 3, 4 and 5.
  • FIG. 7 shows a schematic architecture diagram suitable for a communication device provided by an embodiment of the present application.
  • the device 700 includes a processor 710 coupled to a memory 720 for storing computer programs or instructions and/or data.
  • the processor 710 is used for executing computer programs or instructions stored in the memory 720, or reading the memory 720.
  • the stored data is used to execute the methods in the above method embodiments.
  • the device 700 also includes a transceiver 730, which is used for receiving and/or transmitting signals.
  • the processor 710 is used to control the transceiver 730 to receive and/or transmit signals.
  • processors 710 there are one or more processors 710 .
  • the memory 720 is integrated with the processor 710, or is provided separately.
  • the device 700 is used to implement the operations performed by the access network equipment and the UPF network element in each of the above method embodiments.
  • the processor 710 is configured to execute computer programs or instructions stored in the memory 720 to implement related operations of the access network equipment in each of the above method embodiments. For example, the methods performed by the access network equipment in the embodiments shown in FIG. 3, FIG. 4, and FIG. 5.
  • the processor 710 is used to execute computer programs or instructions stored in the memory 720 to implement the above aspects.
  • Related operations of the terminal equipment in the method embodiment For example, the method performed by the UPF network element in the embodiment shown in FIG. 3, FIG. 4, and FIG. 5.
  • processors mentioned in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache.
  • RAM includes the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • This application also provides a computer-readable medium on which a computer program is stored.
  • the computer program is executed by a computer, the functions of any of the above method embodiments are implemented.
  • This application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • This application also provides a system, which includes the aforementioned first access network device, second access network device, access and mobility management function device, and first session management function device.
  • a computer program product includes one or more computer instructions.
  • Computer instructions When computer instructions are loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g.
  • Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless means to transmit to another website, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that contains one or more available media. Available media can be magnetic physical media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, high-density digital video disc (DVD)), or semiconductor media (eg, solid state disk (SSD)), etc.
  • an embodiment means that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments are not necessarily referred to the same embodiment throughout this specification. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the names of all nodes and messages in this application are only the names set by this application for the convenience of description.
  • the names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any names with and The names of nodes or messages with the same or similar functions used in this application are regarded as methods or equivalent replacements in this application, and are all within the protection scope of this application.
  • preset can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in the device (for example, terminal device).
  • this application does not limit its specific implementation, such as preset rules, preset constants, etc. in the embodiments of this application.
  • system and “network” are often used interchangeably herein.
  • network and/or in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations.
  • At least one of! or "at least one of" herein refers to all or any combination of the listed items, for example, "at least one of A, B and C", It can mean: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, and A, B and C exist simultaneously. "At least one” in this article means one or more. "Multiple" means two or more.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • the terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种通信方法，该方法包括：接入网设备对第一数据流进行拥塞检测；接入网设备根据拥塞检测结果向用户面功能UPF网元发送第一数据包，第一数据包的隧道协议用户面GTP-U头包括拥塞信息，或者，接入网设备根据拥塞检测结果向用户设备UE发送第二数据包，所述第二数据包的服务数据适配协议SDAP层包括所述拥塞信息，所述拥塞信息用于服务器调整发送所述第一数据流的速率。能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。

Description

通信方法和装置
本申请要求于2022年3月28日提交中国专利局、申请号为202210311737.X、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法和装置。
背景技术
在通信系统中，例如第五代(5Generation；5G)移动通信系统中，实时媒体流业务对低时延高带宽有较高要求，但通过现有协议传输时无法提供有效的拥塞控制，媒体流传输消耗大量的网络资源时会影响网络的正常运行。
如何提供有效的拥塞检测与控制，保障网络传输时的正常运行，成为业界亟需解决的问题。
发明内容
本申请实施例提供一种通信方法和装置，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
第一方面，提供了一种通信方法，该方法包括：接入网设备对第一数据流进行拥塞检测；接入网设备根据拥塞检测结果向用户面功能发送第一数据包，第一数据包的隧道协议用户面GTP-U头包括拥塞信息，或者，接入网设备根据拥塞检测结果向用户设备UE发送第一数据包，第一数据包的服务数据适配协议SDAP层包括拥塞信息，拥塞信息用于服务器调整发送第一数据流的速率。
本申请中，该方法可以由接入网设备执行，或者由接入网设备的组件执行，例如，处理器或者芯片。本申请中，拥塞信息包括网络设备对数据流进行拥塞检测后确定的数据传输状况的信息，例如，队列时延值、丢包数量或者丢包率、缓冲区大小或者缓冲区比例信息、上报周期性、拥塞等级、降速比例等。该拥塞信息也可以是指代数据传输状况的信息，也可以是指代是否拥塞或者拥塞等级的相关信息，本申请实施例对此不作限定。
基于上述技术方案，本申请中，接入网设备对数据包进行拥塞检测，从而可以感知网络侧的拥塞情况，避免了仅在端和服务器侧对网络拥塞做检测判断，导致算法不准确的问题；并且，接入网设备根据拥塞检测结果通过数据包的GTP-U头向UPF发送拥塞信息或通过SDAP层向UE发送拥塞信息，使拥塞信息能够灵活快速的通过UPF或者UE反馈至服务器端，从而能够为媒体流业务提供拥塞检测与控制，保障网络传输时的正常运行。
本申请中，用户功能可以是UPF网元。
在一种可能的实现方式中，接入网设备接收第一数据流的数据流标识。
在一种可能的实现方式中，接入网设备根据数据流标识对第一数据流进行拥塞检测。
在一种可能的实现方式中，接入网设备还可以接收拥塞标识。
本申请中，拥塞标识可以理解为用于接入网设备对数据流进行拥塞检测后在检测的数据包中扩展拥塞信息，也可以理解为用于指示进行拥塞检测。
在一种可能的实现方式中，接入网设备根据数据流标识和/或拥塞标识对第一数据流进行拥塞检测。
基于上述技术方案，接入网设备可以根据拥塞标识或数据流标识确定对数据流进行拥塞检测，并向服务器反馈拥塞检测的结果。从而能够灵活判断需要进行拥塞检测的数据流，并在拥塞标识的指示下能够保证将拥塞信息反馈给服务器端，确保服务器能够为媒体流业务提供拥塞检测与控制，保障网络传输时的正常运行。
在一种可能的实现方式中，拥塞信息包括第一拥塞信息和第二拥塞信息，其中，第一拥塞信息为接入网设备和用户面功能之间的拥塞信息，第二拥塞信息为接入网设备和UE之间的拥塞信息。
基于上述技术方案，接入网设备发送的拥塞信息包括接入网设备和用户面功能之间的拥塞信息和空口拥塞信息，利于服务器针对性的调整数据包的发送速率。
在一种可能的实现方式中，接入网设备确定拥塞检测结果满足第一条件；接入网设备向用户面功能或向UE发送第二数据包。
本申请中，该第一条件可以包括对应于拥塞检测结果的具体参数信息。
例如，接入网设备根据拥塞检测结果确定拥塞等级，该反馈条件是拥塞等级#1，则接入网设备可以判断检测结果中的拥塞等级是否满足该拥塞等级#1，若满足，则向UPF或UE发送数据包，若不满足，则不发送该数据包或禁止、停止发送该数据包。
基于上述技术方案，接入网设备确定检测结果满足一定条件的时候才向服务器发送拥塞信息，从而服务器直接根据拥塞信息确定具体调整的参数，提高调整效率。
在一种可能的实现方式中，接入网设备接收来自用户面功能的第一数据包，第一数据包包括数据流标识；或者，接入网设备接收来自SMF网元的拥塞检测信息，拥塞检测信息包括数据流标识。
基于上述技术方案，接入网设备可以灵活的获取数据流标识。
在一种可能的实现方式中，第一数据流为协议数据单元会话中与拥塞检测策略控制与计费PCC规则绑定的服务质量QoS流。
在一种可能的实现方式中，第一数据包为或第二数据包为数据流传输数据的数据包，或者，第一数据包或第二数据包为接入网设备或用户面功能网元生成的监测数据包。
在一种可能的实现方式中，拥塞检测信息包括队列时延、拥塞上报时间，丢包率、缓存区大小、周期性、拥塞等级、降速比例中的至少一个。
本申请中，接入网设备进行拥塞检测的数据包可以是用于传输数据流数据的下行数据包，也可以是用于拥塞检测的数据包或虚拟的空包(该数据包或空包可以不携带数据流的数据)，本申请实施例对此不作限定。
基于上述技术方案，接入网设备可以对任意数据包进行拥塞检测，不必非要等到传输业务的数据包才做拥塞检测，从而可以及时的向服务器反馈拥塞状态。
在一种可能的实现方式中，拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
在一种可能的实现方式中，第一数据包和第二数据包相同，或者，第一数据包和第二数据包不同。
第二方面，提供了一种通信方法，该方法包括：用户面功能能接收来自接入网设备的第一数据包，第一数据包的隧道协议用户面GTP-U头包括第一拥塞信息；用户面功能根据第一拥塞信息向服务器发送第二拥塞信息，第二拥塞信息用于服务器调整发送第一数据流的速率。其中，该第一拥塞信息为第一数据流的拥塞信息。
本申请中，该方法可以由用户面功能执行，或者由用户面功能的组件执行，例如，处理器或者芯片。
基于上述技术方案，用户面功能通过上行或下行数据包向服务器发送拥塞信息，该拥塞信息用于服务器调整发送数据流的速率，使拥塞信息能够灵活快速的通过上行或下行数据包至服务器端，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
本申请中，用户面功能从接入网设备接收的数据包在GTP-U头包括拥塞信息，接入网设备和用户面功能本身的协议栈有GTP-U层，接入网设备和用户面功能可以通过该协议栈传输数据包，但用户面功能的上行传输协议栈时没有GTP-U层，因此用户面功能从接入网设备接收到第一数据包，从GTP-U头获取拥塞信息后，可以在数据包上进行标记，再发送给服务器。
在一种可能的实现方式中，用户面功能向服务器发送第二数据包，第二数据包包括第二拥塞信息。
根据该技术方案，用户面功能通过第二数据包向服务器发送第二拥塞信息。
在一种可能的实现方式中，用户面功能通过用户设备UE向服务器发送第二拥塞信息。
UPF可以通过下行数据包传输拥塞信息，反馈机制的实现更加灵活。
在一种可能的实现方式中，用户面功能向UE发送下行数据包，下行数据包包括第二拥塞信息。
该技术方案的有益效果可参考上述方案，在此不作赘述。
在一种可能的实现方式中，用户面功能通过会话管理功能或网络开放功能向服务器发送第二拥塞信息。
在一种可能的实现方式中，用户面功能确定拥塞检测结果满足第一条件；或者确定第一拥塞信息满足第一条件；用户面功能向服务器发送第二拥塞信息。
基于上述技术方案，用户面功能确定检测结果或第一拥塞信息满足一定条件的时候才向服务器发送拥塞信息，从而服务器直接根据第二拥塞信息确定具体调整的参数，提高调整效率。
在一种可能的实现方式中，第一数据包为数据流传输数据的数据包或接入网设备或用户面功能生成的监测数据包。
基于上述技术方案，接入网设备可以对任意数据包进行拥塞检测，不必非要等到传输业务的数据包才做拥塞检测，从而可以及时的向服务器反馈拥塞状态。
在一种可能的实现方式中，拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
在一种可能的实现方式中，第一数据包和第二数据包相同，或者，第一数据包和第二 数据包不同。
第三方面，提供了一种通信方法，该该方法包括：终端设备UE接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息，或者该第一数据包的SDAP层包括第一拥塞信息，该第一拥塞信息用于服务器调整数据流的发送速率；UE根据该第一拥塞信息，向服务器发送第二拥塞信息。
本申请中，该方法可以由终端设备执行，或者由终端设备的组件执行，例如，处理器或者芯片。
基于上述技术方案，本申请中，终端设备从从接入网设备接收的数据包在GTP-U头或SDAP层包括拥塞信息，进一步的向服务器发送拥塞信息，从而向服务器通知接入网设备感知的网络侧的拥塞情况，避免了仅在端和服务器侧对网络拥塞做检测判断，导致算法不准确的问题，并且能够使得服务器根据拥塞情况来调整数据发送的速率，保障网络传输时的正常运行。
在一种可能的实现方式中，UE从用户面功能接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息。
该方案中，UE从用户面功能接收在GTP-U头包括第一拥塞信息的数据包，进一步的向服务器发送拥塞信息。
在一种可能的实施方式中，UE从接入网设备接收第一数据包，该第一数据包的SDAP层包括第一拥塞信息。
该方案中，UE从接入网设备接收在SDAP层包括第一拥塞信息的数据包，进一步的向服务器发送拥塞信息。
在一种可能的实施方式中，UE通过modem向服务器发送第二拥塞信息。
第四方面，提供了一种通信装置，该装置包括：处理单元，用于对第一数据流进行拥塞检测；收发单元，用于根据拥塞检测结果向用户面功能发送第一数据包，第一数据包的隧道协议用户面GTP-U头包括拥塞信息，或者，还用于根据拥塞检测结果向用户设备UE发送第一数据包，第一数据包的服务数据适配协议SDAP层包括拥塞信息，拥塞信息用于服务器调整发送第一数据流的速率。
基于上述技术方案，本申请中，处理单元对数据包进行拥塞检测，从而可以感知网络侧的拥塞情况，避免了仅在端和服务器侧对网络拥塞做检测判断，导致算法不准确的问题；并且，收发单元根据拥塞检测结果通过数据包的GTP-U头向UPF发送拥塞信息或通过SDAP层向UE发送拥塞信息，该使拥塞信息能够灵活快速的通过用户面功能或者UE反馈至服务器端，从而能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
在一种可能的实现方式中，收发单元还用于接收第一数据流的数据流标识。
在一种可能的实现方式中，接入网设备根据数据流标识对第一数据流进行拥塞检测。
在一种可能的实现方式中，接入网设备接收拥塞标识。
在一种可能的实现方式中，接入网设备根据数据流标识和/或拥塞标识对第一数据流进行拥塞检测。
基于上述技术方案，处理单元可以根据拥塞标识或数据流标识确定对数据流进行拥塞检测，并向服务器反馈拥塞检测的结果。从而能够灵活判断需要进行拥塞检测的数据流， 并在拥塞标识的指示下能够保证将拥塞信息反馈给服务器端，确保服务器能够为媒体流业务提供拥塞检测与控制，保障网络传输时的正常运行。
在一种可能的实现方式中，拥塞信息包括第一拥塞信息和第二拥塞信息其中，第一拥塞信息为接入网设备和用户面功能之间的拥塞信息，第二拥塞信息为UE和接入网设备之间的拥塞信息。
基于上述技术方案，收发单元发送的拥塞信息包括接入网设备和用户面功能之间的拥塞信息和空口拥塞信息，利于服务器针对性的调整数据包的发送速率。
在一种可能的实现方式中，处理单元还用于确定拥塞检测结果满足第一条件；收发单元向用户面功能或UE发送第一数据包。
基于上述技术方案，处理单元确定检测结果满足一定条件的时候，收发单元才向服务器发送拥塞信息，从而服务器直接根据拥塞信息确定具体调整的参数，提高调整效率。
在一种可能的实现方式中，收发单元具体用于接收来自用户面功能的第一数据包，第一数据包包括数据流标识；或者，收发单元接收来自SMF网元的拥塞检测信息，拥塞检测信息包括数据流标识。
基于上述技术方案，收发单元可以灵活的获取数据流标识。
在一种可能的实现方式中，第一数据包为数据流传输数据的数据包或接入网设备或用户面功能生成的监测数据包。
基于上述技术方案，处理单元可以对任意数据包进行拥塞检测，不必非要等到传输业务的数据包才做拥塞检测，从而可以及时的向服务器反馈拥塞状态。
在一种可能的实现方式中，拥塞检测信息包括队列时延、拥塞上报时间，丢包率、缓存区大小、周期性、拥塞等级、降速比例中的至少一个。
在一种可能的实现方式中，第一数据流为拥塞检测策略控制与计费PCC规则中与服务质量QoS流绑定的数据流。
在一种可能的实现方式中，拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
在一种可能的实现方式中，第一数据包和第二数据包相同，或者，第一数据包和第二数据包不同。
第五方面，提供了一种通信装置，该方法包括：收发单元，用于接收来自接入网设备的第一数据包，第一数据包的隧道协议用户面GTP-U头包括第一拥塞信息；收发单元还用于根据第一拥塞信息向服务器发送第二拥塞信息，第二拥塞信息用于服务器调整发送数据流的速率。
基于上述技术方案，收发单元元通过上行或下行数据包向服务器发送拥塞信息，该拥塞信息用于服务器调整发送数据流的速率，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
在一种可能的实现方式中，装置包括处理单元，处理单元用于在收发单元向服务器发送第二拥塞信息之前，在第一数据包携带第二拥塞信息，第一数据包是上行数据包或下行数据包。
该方案的有益效果参考上述方案，在此不进行赘述。
在一种可能的实现方式中，收发单元用于通过用户设备UE向服务器发送第二拥塞信 息。
基于上述技术方案，收发单元可以通过上行数据包或者下行数据包传输拥塞信息，反馈机制的实现更加灵活。
在一种可能的实现方式中，收发单元具体用于向UE发送下行数据包，下行数据包包括第二拥塞信息。
在一种可能的实现方式中，收发单元具体用于通过会话管理功能或网络开放功能向服务器发送第二拥塞信息。
在一种可能的实现方式中，处理单元还用于确定拥塞检测结果或第一拥塞信息满足第一条件；收发单元向服务器发送拥塞信息。
基于上述技术方案，处理单元确定检测结果满足一定条件的时候才向服务器发送拥塞信息，从而服务器直接根据拥塞信息确定具体调整的参数，提高调整效率。
在一种可能的实现方式中，第一数据包为数据流的数据包或接入网设备或用户面功能生成的监测数据包。
基于上述技术方案，处理单元可以对任意数据包进行拥塞检测，不必非要等到传输业务的数据包才做拥塞检测，从而可以及时的向服务器反馈拥塞状态。
在一种可能的实现方式中，拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
第六方面，提供了一种通信装置，该装置包括：收发单元，用于接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息，或者该第一数据包的SDAP层包括第一拥塞信息，该第一拥塞信息用于服务器调整第一数据流的发送速率；收发单元，还用于根据该第一拥塞信息，向服务器发送第二拥塞信息。
本申请中，该方法可以由终端设备执行，或者由终端设备的组件执行，例如，处理器或者芯片。
基于上述技术方案，本申请中，收发单元接收的数据包在GTP-U头或SDAP层包括拥塞信息，进一步的向服务器发送拥塞信息，从而向服务器通知接入网设备感知的网络侧的拥塞情况，避免了仅在端和服务器侧对网络拥塞做检测判断，导致算法不准确的问题，并且能够使得服务器根据拥塞情况来调整数据发送的速率，保障网络传输时的正常运行。
在一种可能的实现方式中，收发单元具体用于从用户面功能接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息。
该方案中，收发单元具体从用户面功能接收在GTP-U头包括第一拥塞信息的数据包，进一步的向服务器发送拥塞信息。
在一种可能的实施方式中，收发单元具体用于从接入网设备接收第一数据包，该第一数据包的SDAP层包括第一拥塞信息。
该方案中，收发单元具体用于从接入网设备接收在SDAP层包括第一拥塞信息的数据包，进一步的向服务器发送拥塞信息。
在一种可能的实施方式中，收发单元还用于通过modem向服务器发送第二拥塞信息。
第七方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
第八方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第二方面的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
第九方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第三方面的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
第十方面，提供了一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
第十一方面，提供了一种计算机可读存储介质，计算机可读介质存储有计算机程序(也可以称为代码，或指令)，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
第十二方面，提供了一种芯片系统，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片系统的设备执行上述第一方面、第二方面或第三方面各实现方式中的方法。
第十三方面，提供了一种通信系统，通信系统包括如第四方面或第七方面的装置，和如第五方面或第八方面的装置。
附图说明
图1示出了适用于本申请实施例的通信系统架构100的示意图。
图2示出了适用于本申请实施例提供的通信方法的一种示意性框架图。
图3示出了适用于本申请实施例提供的通信方法的一种示意性交互图。
图4示出了适用于本申请实施例提供的通信方法的另一种示意性交互图。
图5示出了适用于本申请实施例提供的通信方法的另一种示意性交互图。
图6示出了适用于本申请实施例提供的通信装置的一种示意性框图。
图7示出了种适用于本申请实施例提供的通信装置的一种示意性架构图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、第五代(5th Generation，5G)系统或新无线(New Radio，NR)、或未来演进的系统等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、 移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为便于理解本申请实施例，首先结合图1简要说明本申请实施例的一种通信系统100的结构示意图。
如图1所示，该网络架构以5G系统(the 5th generation system，5GS)为例。该网络架构可以包括但不限于：网络切片选择功能(network slice selection function，NSSF)，认证服务器功能(authentication server function，AUSF)，统一数据管理(unified data management，UDM)，网络暴露功能(network exposure function，NEF)，网络存储功能(NF repository function，NRF)，策略控制功能(policy control function，PCF)，应用功能(application function，AF)，接入和移动性管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)，用户设备(user equipment，UE)，无线接入网设备，用户面功能(user plane function，UPF)，数据网络(data network，DN)。
其中，DN可以是互联网；NSSF、AUSF、UDM、NEF、NRF、PCF、AF、AMF、SMF、UPF属于核心网中的网元，由于图1以5G系统为例，那么该核心网可以称为5G核心网(5G core network，5GC或5GCN)。
下面对图1中示出的各网元做简单介绍。
1、UE：可以称终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现 实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网((radio)access network，(R)AN)设备：可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。下文为方便描述采用AN设备表示。
AN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
AN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
AN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对AN设备所采用的具体技术和具体设备形态不做限定。
3、AMF：主要用于接入控制、移动性管理、附着与去附着等功能。
4、SMF：主要用于用户面网元选择，用户面网元重定向，终端设备的因特网协议(internet protocol，IP)地址分配，以及会话的建立、修改和释放及QoS控制。
5、UPF：主要用于用户面数据的接收和转发。例如，UPF可以从DN接收用户面数据，并通过AN设备将用户面数据发送给终端设备。UPF还可以通过AN设备从终端设备接收用户面数据，并转发到DN。
6、NEF：主要用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
7、PCF：主要用于指导网络行为的统一策略框架，为控制面网元(例如AMF，SMF等)提供策略规则信息等。
8、AF：主要用于向3GPP网络提供业务，如与PCF之间交互以进行策略控制等。
9、网络切片选择功能(network slice selection function，NSSF)：主要用于网络切片选择。
10、UDM：主要用于UE的签约数据管理，包括UE标识的存储和管理，UE的接入授权等。
11、DN：主要用于为UE提供数据服务的运营商网络。例如，因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service，IMS)网络等。
12、AUSF：主要用于用户鉴权等。
13、NRF：主要用于保存网络功能实体以及其提供服务的描述信息等。
在图1所示的网络架构中，各网元之间可以接口通信。例如，UE2通过无线资源控制(radio resource control，RRC)协议与AN设备连接，UE和AN设备之间采用Uu接口进行通信。UE1和UE2之间采用PC5接口通信，PC5接口可以用于UE间互相发现、UE间进行数据和信令的传输。此外，在图1中，N1为UE2和AMF之间的接口，N2为(R)AN和AMF的接口，用于NAS消息的发送等；N3为RAN和UPF之间的接口，用于传输用户面的数据等；N4为SMF和UPF之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的接口，用于传输用户面的数据等，N11接口为AMF和SMF之间的接口。
应理解，上述所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、PCF、UDM、NSSF、AUSF等功能或者网元，可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
还应理解，图1仅为本申请实施例的一种应用场景，本申请对于该方法所应用的场景并不做限定。下文示出的实施例中，仅为便于理解和说明，以该服务化架构为例详细说明本申请实施例提供的方法。
在5GS通信系统中，通过现有协议传输时无法提供有效的拥塞控制，媒体流传输消耗大量的网络资源时会影响网络的正常运行。例如，基于RTP/RTCP协议的拥塞控制算法，在端和服务器侧对网络拥塞做检测判断，没有考虑网络本身因素可能导致算法不准确的问题，导致拥塞检测不准确或拥塞控制不及时，从而影响通信质量，直接影响用户体验。
本申请提供一种通信方法和装置，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行，保障用户体验。
下面以具体的实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
下面将结合附图详细说明本申请实施例提供的一种通信的方法和装置。
图2是本申请实施例提供的一种通信方法的示意性框图。图2所示的方法200可以用于图1所示的网络架构中，该方法200可以由图1所示的接入网设备执行。
方法200包括以下步骤：
S210，接入网设备对第一数据流进行拥塞检测。
第一数据流为待检测的数据流。
具体地，接入网设备进行拥塞检测的数据包可以是用于传输数据流数据的下行数据包，也可以是用于拥塞检测的数据包或虚拟的空包(该数据包或空包可以不携带数据流的数据)，本申请实施例对此不作限定。
接入网设备对数据流进行拥塞检测后，获得拥塞检测结果。拥塞检测结果例如可以是下行队列时延、丢包、缓存区大小等指标。
一种可能的实施方式中，接入网设备根据GTP-U收发报文时间戳，分别计算RAN-UE以及UPF-RAN的拥塞检测结果。其中，接入网设备检测UPF-RAN之间的拥塞状况可以参考3GPP标准TS 23.501中QoS监控相关内容，本申请实施例对此不作限定。接入网设备检测RAN-UE之间的拥塞状况可以参考3GPP标准TS 38.314中的内容，本申请实施例对此不作限定。
在步骤S210之前，还可以包括：
一种可能的实施方式中，接入网设备接收第一数据流标识。
其中，接入网设备接收待进行拥塞检测的数据流的数据流标识。接入网设备可以根据数据流标识对第一数据流进行拥塞检测。
示例性的，接入网设备配置有拥塞检测相关的一个或多个数据流标识，当接入网设备接收的数据流标识属于上述一个或多个数据流标识，则接入网设备确定该接收到的数据流标识所对应的数据流需要进行拥塞检测。
另一种可能的实现方式中，接入网设备接收数据流标识和拥塞标识，该拥塞标识用于指示该数据流标识所对应的数据流需要进行拥塞检测，或者该拥塞标识用于指示需要反馈该数据流的拥塞信息。即接入网设备可以根据数据流标识和拥塞标识对该数据流标识对应的数据流进行拥塞检测。
可以理解，在此情况下，接入网设备可以不预配置某些数据流需要进行检测。
作为示例而非限定，拥塞标识可以是一个字段，该字段通过true或者false来指示是否需要进行拥塞检测；或者，拥塞标识可以是用于携带数据流标识的信元或者消息，该信元或者消息的类型或者名称与拥塞检测相关。
可选的，用于携带拥塞标识的字段，也可在接入网设备进行拥塞检测后用于传输拥塞信息。即拥塞标识用于接入网设备对数据流进行拥塞检测后反馈拥塞信息。例如，字段#A作为拥塞标识，接入网设备对数据流进行拥塞检测后获得拥塞检测结果，根据检测结果确定拥塞信息，该字段#A用来反馈拥塞等级。
上述接入网设备可以从核心网设备接收待进行拥塞检测的数据流的数据流标识，具体可以通过以下方式实现：
一种可能的实施方式中，接入网设备接收来自UPF网元的数据包，该数据包包括上述数据流标识，还可以包括拥塞标识。作为一种示例，该数据包为下行数据报文，该下行报文的GTP-U头包括数据流标识和拥塞标识。可以理解的是，当接入网设备接收的下行数据包包括拥塞标识，接入网设备可以根据该拥塞标识对该数据包进行拥塞检测。即接入网设备可以根据拥塞标识对该数据流(即携带该拥塞标识的数据包)进行拥塞检测。基于这种实施方式，接入网设备可以不考虑数据流标识，而仅通过数据包是否携带拥塞标识来判断是否需要计算该数据包的拥塞结果。
又一种可能的实施方式中，接入网设备接收来自SMF网元的拥塞检测信息，该拥塞检测信息包括上述数据流标识，还可以包括拥塞标识。
本申请中，拥塞检测信息可以包括队列时延、拥塞上报时间，丢包率、缓存区大小、周期性、拥塞等级、降速比例中的至少一个。也可以包括其他用来保证拥塞状况和拥塞信息的参数及数据。本申请实施例对此不作限定。
作为示例而非限定，上述数据流标识可以是QoS数据流的QFI。一种可能的实施方式中，SMF将PCC规则与PDU会话中的QoS流进行绑定，并定义该数据流的标识。可以理解，该QoS流是携带拥塞标识的QoS流，该QoS流可以是现有的QoS流，也可以是新建立或者修改的QoS流，本申请实施例对此不作限定。
S220，接入网设备根据拥塞检测结果向用户面功能UPF网元发送第一数据包，第一数据包的GTP-U头包括拥塞信息，或者，接入网设备根据拥塞检测结果向用户设备UE发送第二数据包，第二数据包的SDAP层包括拥塞信息。
其中，GPRS隧道传输协议(GPRS tunnel protocol，GTP)是一组基于IP的高层协议 (可参考3GPP标准协议29.281)，位于TCP/IP，UDP/IP协议之上。GTP用户面部分(user plane part of GTP，GTP-U)是一个基于IP/UDP的隧道协议，它允许在各个GTP-U实体(协议实体)之间建立多个隧道，GTP-U将UE发出的原始业务数据称为传输协议数据单元(transport protocol data unit，T-PDU)，T-PDU在GTP-U实体中被封装上了GTP-U头之后就称为GTP封装的用户平面数据单元(GTP encapsulated user plane data unit，G-PDU)。
其中，服务数据适配协议(service data adaptation protocol，SDAP)层是NR中新增的协议层(可参考3GPP标准协议37.324)。SDAP层的主要功能包括QoS流和数据无线电承载之间的映射以及在下行和上行报文中标记QoS flow ID(QFI)。
本申请中，第一数据包和第二数据包可以相同，也可以不同，本申请实施例在此不作限定。
上述第一数据包或第二数据包可以是用于传输数据的数据包，也可以是UPF定期建立并发送给RAN的数据包，或RAN定期建立的数据包，例如，监测数据包(monitoring packets)，或者，虚拟数据包(dummy packet)。
接入网设备通过UPF或者UE将拥塞信息反馈至服务器，从而使服务器能够根据该数据流的拥塞信息调整发送该数据流的速率。可以理解的是，UPF或UE向服务器发送的拥塞信息与从接入网设备接收的拥塞信息可以相同，也可以不同(例如在发送给服务器时改变信息表达方式，或对信息进行二次处理后发送给服务器)。
其中，拥塞信息可以包括网络设备对数据流进行拥塞检测后确定的数据传输状况的信息，例如，队列时延值、丢包数量或者丢包率、缓冲区大小或者缓冲区比例信息、上报周期性、拥塞等级、降速比例等。该拥塞信息也可以是指代数据传输状况的信息，例如，该拥塞信息包括字段#1，该字段#1用于指示队列时延大于预设阈值，或者该拥塞信息还可以包括字段#2，该字段#2用于指示丢包率大于预设阈值，等。也可以是指代是否拥塞或者拥塞等级的相关信息，例如，该拥塞信息包括字段#3，该字段#3用于指示发生拥塞，该拥塞信息还可以包括字段#3，该字段#4用于指示拥塞等级较高，等。本申请实施例对此不作限定。
需要说明的是，该拥塞信息可以反映该数据流的拥塞程度，也可以理解为该拥塞信息可以反映该数据流的传输状态，利于服务器侧实时获取该数据流的传输状况并根据业务等级需求确定是否需要对传输速率进行调整。
还应理解，在本申请中，拥塞信息可以包括UPF与接入网设备之间(下文简称为UPF-接入网设备)的拥塞信息(下文简称为第一拥塞信息)，也可以包括UE与接入网设备之间(下文简称为UE-接入网设备)的空口拥塞信息(下文简称为第二拥塞信息)。
具体地，接入网设备根据拥塞检测结果确定拥塞信息。
其中，GTP-U头包括拥塞信息可以是GTP-U头中的一个或多个比特位用于携带拥塞信息，也可以是GTP-U头仅在需要携带拥塞信息时扩展一个或多个比特位，由该扩展的比特位携带拥塞信息。
类似的，SDAP层包括拥塞信息可以是SDAP层中的一个或多个比特位用于携带拥塞信息，也可以是SDAP层仅在需要携带拥塞时扩展一个或多个比特位，由扩展的比特位携带拥塞信息。
一种可能的实施方式中，接入网设备可以在向UPF或者向UE发送第一数据包之前， 确定拥塞检测结果是否满足相应的反馈条件。
其中，反馈条件也可以说是上报条件，该反馈条件可以由AF/AS预设，也可以由接入网设备预设。
其中，该反馈条件可以包括拥塞检测结果需要满足的具体参数信息。当接入网设备对该数据流的拥塞检测结果满足该反馈条件，则发送拥塞信息。
例如，接入网设备根据拥塞检测结果获得拥塞等级，当反馈条件是拥塞等级#1，则接入网设备可以判断根据拥塞检测结果获得的拥塞等级是否满足该拥塞等级#1，若满足，则向UPF或UE发送该第一数据包，若不满足，则不发送该第一数据包或禁止、停止发送该第一数据包。
再例如，接入网设备根据拥塞检测结果获得降速比例，当反馈条件是降速比例#1，则接入网设备可以判断根据拥塞检测结果获得的降速比例是否满足该降速比例#1，若满足，则向UPF或UE发送该第一数据包，若不满足，则不发送该第一数据包。在此情况下，AF/AS可以进一步直接根据该降速比例调整速率，提高AF/AS的调整速率。
可以理解的是，接入网设备还可以直接判断拥塞检测结果是否直接满足具体参数信息，以决策是否发送、不发送、禁止发送或停止发送第一数据包，此处不作赘述。
一种可能的实施方式中，UPF网元接收到来自接入网设备的第一数据包，该数据包的GTP-U头包括拥塞信息，该数据包可以是上行数据包，进一步的，UPF可以将该第一数据包发送给服务器。或者，该数据包也可以是下行数据包，则发送给UE，通过UE发送给服务器
一种可能的实施方式中，UPF网元接收到来自接入网设备的第一数据包，该数据包的GTP-U头包括拥塞信息，UPF将拥塞信息发送给NEF(例如通过能力开放通知(Nupf_EventExposure_Notify)消息)，NEF再将拥塞信息转发给AF/AS。可以理解的是，UPF向AF/AS发送的拥塞信息与从接入网设备接收的拥塞信息可以相同，也可以不同(例如在发送给服务器时改变信息表达方式，或对信息进行二次处理后发送给AF/AS)。
一种可能的实施方式中，UE接收到来自接入网设备的第一数据包，该数据包的SDAP层包括拥塞信息，终端将拥塞信息上报给AF/AS。示例性的，终端可以通过调制解调器(MODEM)将拥塞信息转发到上层并发送给AF/AS。
一种可能的实施方式中，UPF可以在向AF/AS发送拥塞信息之前，判断拥塞检测结果是否满足第一条件。
其中，第一条件参考上文中对反馈条件的描述，在此不进行赘述。
根据本申请实施例提供的技术方案，接入网设备基于拥塞标识和数据流标识对数据包进行拥塞检测，根据拥塞检测结果通过数据包的GTP-U头向UPF发送拥塞信息或通过SDAP层向UE发送拥塞信息，该拥塞信息用于服务器调整发送数据流的速率，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
图3示出了适用于本申请实施例提供的通信方法的一种示意性交互图。方法300可以视为方法200的一种具体实现方式，该方法300可以包括如下步骤。
S310，AF/AS向PCF/NEF发送消息#1。
具体地，消息#1包括拥塞信息通知消息，该拥塞信息通知消息用于指示向AF/AS上报拥塞信息的上报方式。可以理解的是，拥塞信息通知消息还可以命名为其他消息名称， 也可以理解为该拥塞信息通知消息是用于指示向AF/AS上报拥塞信息的上报方式的一种或多种信息的逻辑概括。
例如，该拥塞信息通知消息可以包括通知周期信息(向AF/AS上报拥塞信息的周期)，通知时间指示信息(向AF/AS上报拥塞信息的时间)，通知方式信息(向AF/AS上报拥塞信息的具体方式)，以上仅为示例性说明，本申请实施例在此不作限定。
该消息#1可以包括流描述(flow description)。流描述可以包括业务流五元组，全地址域名(fully qualified domain name，FQDN)等，本申请实施例对此不作限定。
示例性的，该消息#1可以是订阅消息。
一种可能的实施方式中，PCF/NEF向AF/AS发送订阅请求消息，该订阅请求消息用于AF/AS向PCF/NEF发送拥塞信息相关的通知消息。相应的，AS/AS接收订阅请求消息。
S320，PCF根据消息#1生成PCC规则#A。
具体地，PCF根据消息#1包括的流描述获取对应的QoS流的QoS参数，根据QoS参数生成一个用于拥塞检测的PCC规则#A。
S330，SMF将PCC规则#A与QoS流绑定。
其中，PCC规则#A中可以包括数据流#A的信息(或者说PCC规则#A定义了数据流#A)。
SMF可以将PCC规则#A，与PDU会话中已有的部分或全部QoS流进行绑定，从而将被绑定的QoS流作为待拥塞检测的数据流。被绑定的QoS流可以使用绑定前的QFI；当PCC规则#A包括QFI，被绑定的数据流可以使用PCC规则#A中的QFI。
SMF也可以根据PCC规则#A创建新的QoS流，该QoS流可以用于传输该PDU会话需要进行拥塞检测的数据。该QoS流的标识可以使用PCC规则#A中的QFI。
S340(a1)，SMF向UPF发送消息#2。
具体地，消息#2包括拥塞检测信息，该拥塞检测信息可以包括QFI#A和拥塞标识，还可以包括流描述，或拥塞信息的上报时间等信息中的一个或多个。示例性的，该消息#2可以是N4建立请求消息，也可以是N4修改请求消息。
一种可能的实施例中，SMF具体通过N4消息在Context消息中扩展拥塞检测相关参数信息。
S340(a2)，UPF向接入网设备发送数据包#A。
其中，UPF通过数据包#A携带拥塞检测信息。
可以理解的是，UPF向接入网设备发送的拥塞检测信息与从SMF接收的拥塞检测信息可以相同，也可以不同(例如在发送给接入网设备时改变信息表达方式，或对信息进行二次处理后发送给接入网设备)。
一种可能的实施方式中，UPF通过用户面数据包携带拥塞检测信息。
例如，UPF在发送的下行数据报文中，在GTP-U报文头携带QFI#A和拥塞标识，还可以包括流描述，拥塞信息的上报时间，报文的发送或接收时间戳等信息中的一个或多个。
应理解，上述步骤S340(a1)和S340(a2)为SMF向接入网设备发送拥塞检测信息的一种方式(方式一)，下述步骤S340(b)为另一种方式(方式二)，方式一和方式二择一执行即可，本申请实施例对此不作限定。
S340(b)，SMF向接入网设备发送拥塞检测信息。
具体地，SMF向AMF发送拥塞检测信息，AMF再向接入网设备发送该拥塞检测信息。相应的，接入网设备从AMF接收该拥塞检测信息，该拥塞检测信息具体内容可以参看步骤S340(a)，在此不进行赘述。
示例性的，SMF可以通过N11消息向AMF发送拥塞检测信息，该N11消息可以是N1N2消息传递(Namf_communication_N1N2MessageTransfer)消息。进一步的，AMF通过N2消息将该拥塞检测信息发送给接入网设备。S350，接入网设备进行拥塞检测。
S350，接入网设备进行拥塞检测。
该过程可参考S210的介绍。
一种实现方式中，接入网设备预配置需要进行拥塞检测的数据流的数据流标识。接入网设备根据拥塞检测信息中的QFI#A属于上述预配置的数据流标识，确定需要对数据流#A进行拥塞检测，并对该数据流#A进行检测获得拥塞检测结果。
另一种实现方式中，接入网设备根据拥塞标识和QFI#A确定该QFI#A判断需要对数据流#A进行拥塞检测，对该数据流#A进行检测获得拥塞检测结果。
可以理解，该拥塞标识用于指示对QFI#A对应的数据流进行拥塞检测并反馈拥塞信息。
接入网设备进行拥塞检测的方式可以参考方法200中的步骤S210，在此不进行赘述。
具体的，接入网设备在进行拥塞检测后，在相应的数据包的GTP-U头中携带拥塞信息，用于后续向AF/AS反馈拥塞信息，从而AF/AS可以根据该拥塞信息来对数据的传输速率进行调整。
S360，接入网设备向UPF发送拥塞信息。
该过程具体可参考S220的介绍。
可以理解，接入网设备通过用户面向UPF发送数据包#A，该数据包#A的GTP-U头包括拥塞信息。
可选的，接入网设备可以在向UPF发送拥塞信息之前，接入网设备可以判断拥塞检测结果是否满足反馈条件(作为第一条件的一例)。该判断方式与方法200中步骤S220中的判断方式相似，在此不进行赘述。
具体地，接入网设备根据拥塞检测结果确定拥塞信息。
作为一种示例，接入网设备在数据包#A的GTP-U头携带拥塞信息，包括但不仅限于以下几种方式：
a，数据包#A的GTP-U头包括拥塞信息，GTP-U头具体可以携带是否拥塞、拥塞的数据包个数、可携带队列时延值、丢包数量、缓冲区大小信息、周期性、拥塞等级、降速比例等信息中的至少一个；
b，数据包#A的GTP-U头在需要携带拥塞信息时，扩展GTP-U头，并在GTP-U扩展头中包括拥塞信息，GTP-U扩展头具体可携带是否拥塞、拥塞的数据包个数、携带队列时延与阈值时延比例、丢包比例、缓冲区比例信息、周期性、拥塞等级、降速比例等信息中的至少一个。
以上举例仅为示例性说明，对本申请实施例不构成任何限定。
S370，UPF向AF/AS发送拥塞信息。
具体地，UPF通过控制面向AF/AS发送拥塞信息。
一种可能的实施方式中，UPF通过N4会话消息将拥塞信息上报给SMF，SMF将拥塞信息转发AF/AS，或者SMF通过NEF将拥塞信息转发给AF/AS。可以理解的是，SMF向AF/AS发送的拥塞信息与从UPF接收的拥塞信息可以相同，也可以不同(例如在发送给AF/AS时改变信息表达方式，或对信息进行二次处理后发送给AF/AS)。
又一种可能的实施方式中，UPF通过能力开放通知(Nupf_EventExposure_Notify)消息发送拥塞信息给NEF，NEF再转发给AF/AS；或者，UPF也可能直接通过能力开放通知(Nupf_EventExposure_Notify)消息发送拥塞信息给AF/AS。
可选的，UPF可以在向AF/AS发送拥塞信息之前，UPF可以判断拥塞检测结果是否满足反馈条件(作为第一条件的一例)。若UPF判断拥塞检测结果满足反馈条件，则UPF向AF/AS发送该拥塞信息，相反的，若UPF判断拥塞检测结果不满足反馈条件，则不向AF/AS发送该拥塞信息或禁止、停止发送该拥塞信息。
反馈条件和具体判断方式与步骤S220类似，在此不进行重复性说明。
S380，AF/AS基于拥塞信息调整发送速率。
具体地，AF/AS基于拥塞信息计算并调整发送数据包的速率。
根据本申请实施例提供的技术方案，接入网设备基于拥塞标识和数据流标识对数据包进行拥塞检测，根据检测结果通过数据包的GTP-U头向UPF发送拥塞信息，该拥塞信息用于服务器调整发送数据流的速率，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
图4示出了适用于本申请实施例提供的通信方法的另一种示意性交互图。图4示出了适用于本申请实施例提供的通信方法的另一种示意性交互图。方法400可以视为方法200的另一种具体实现方式。
在方法300中，UPF通过控制面向AF/AS发送拥塞信息，而在本实施例中，UPF可以通过数据面向AF/AS发送拥塞信息。该方法400的具体步骤如下。
步骤S410-步骤S460与步骤S310-步骤S360相同，在此不进行赘述。
以下步骤中，S470(a)和S480(a)，是UPF通过上行数据包携带拥塞信息的具体步骤(方式一)；S470(b)、S480(b1)和S480(b2)，是UPF通过下行数据包携带拥塞信息的具体步骤(步骤二)。
S470(a)，UPF在上行数据包携带拥塞信息。
具体地，UPF在上行的数据包#A携带拥塞信息。
需要说明的是，UPF可以在数据包#A的任意层携带拥塞信息，例如，可以是GTP-U层，也可以是IP层。
示例性的，数据包#A可以是Ack数据包，也可以是UPF或RAN定期建立的数据包，例如，监测数据包(monitoring packets)，或者，虚拟数据包(dummy packet)。
可选的，UPF在对上行的数据包#A携带拥塞信息之前，还可以判断拥塞检测结果是否满足反馈条件(作为第一条件的一例)。若UPF判断拥塞检测结果满足反馈条件，则UPF在上行的数据包#A携带拥塞信息，相反的，若UPF判断拥塞检测结果不满足反馈条件，则不在上行的数据包#A携带拥塞检测信息或禁止、停止在上行的数据包#A携带拥塞检测信息。
可以理解，UPF可以通过接入网设备发送的拥塞信息获取拥塞检测结果，UPF也可以从接入网设备接收拥塞检测结果，本申请实施例对此不作限定。
本实施例中，具体的反馈条件即判断方式与方法300中步骤S370中相似，可参看步骤S370中的详细说明，在此不进行赘述。
S480(a)，UPF向AF/AS发送拥塞信息。
具体地，UPF通过控制面向AF/AS发送数据包#A，携带拥塞信息。
具体的发送方式和方法300中的步骤S370相同，在此不进行赘述。
可选的，UPF在向AF/AS发送数据包#A之前，还可以判断是否满足反馈条件(作为第一条件的一例)。若UPF判断拥塞检测结果满足反馈条件，则UPF向AF/AS发送数据包#A，相反的，若UPF判断拥塞检测结果不满足反馈条件，则不向AF/AS发送数据包#A或者禁止、停止向AF/AS发送数据包#A。
可以理解，UPF可以通过接入网设备发送的拥塞信息获取拥塞检测结果，UPF也可以从接入网设备接收拥塞检测结果，本申请实施例对此不作限定。
本实施例中，具体的反馈条件即判断方式与方法300中步骤S370中相同，可参看步骤S370中的详细说明，在此不进行赘述。
S470(b)，UPF在下行数据包携带拥塞信息。
具体地，UPF在下行的数据包#A携带拥塞信息。
需要说明的是，UPF可以在数据包#A的任意层携带拥塞信息，例如，可以是GTP-U层，也可以是IP层。
例如，UPF在下行数据包IP头中的ECN标识扩展拥塞信息。
可选的，UPF在下行的数据包#A携带拥塞信息之前，还可以判断是否满足反馈条件(作为第一条件的一例)。若UPF判断拥塞检测结果满足反馈条件，则UPF在下行的数据包#A携带拥塞信息，相反的，若UPF判断拥塞检测结果不满足反馈条件，则不在下行的数据包#A携带拥塞信息或者禁止、停止在数据包#A携带拥塞信息。
可以理解，UPF可以通过接入网设备发送的拥塞信息获取拥塞检测结果，UPF也可以从接入网设备接收拥塞检测结果，本申请实施例对此不作限定。
本实施例中，具体的反馈条件即判断方式与方法300中步骤S370中相同，可参看步骤S370中的详细说明，在此不进行赘述。
S480(b1)，UPF向UE发送拥塞信息。
具体地，UPF通过接入网设备向UE发送数据包#A，携带拥塞信息。
示例性的，UPF可以通过N3消息向接入网设备发送数据包#A，进一步的，接入网设备通过Uu接口向UE发送数据包#A。
可选的，UPF在向UE发送数据包#A之前，还可以判断是否满足反馈条件(作为第一条件的一例)。若UPF判断拥塞检测结果满足反馈条件，则UPF向UE发送数据包#A，相反的，若UPF判断拥塞检测结果不满足反馈条件，则不向UE发送数据包#A或者禁止、停止向AF/AS发送数据包#A。
可以理解，UPF可以通过接入网设备发送的拥塞信息获取拥塞检测结果，UPF也可以从接入网设备接收拥塞检测结果，本申请实施例对此不作限定。
本实施例中，具体的反馈条件即判断方式与方法300中步骤S370中相同，可参看步 骤S370中的详细说明，在此不进行赘述。
S480(b2)，UE向AF/AS发送拥塞信息。
具体地，UE向AF/AS发送上行的数据包#A，携带拥塞信息。
S490，AF/AS基于拥塞信息调整发送速率。
具体地，AF/AS基于拥塞信息计算并调整发送数据包的速率。
根据本申请实施例提供的技术方案，接入网设备基于拥塞标识和数据流标识对数据包进行拥塞检测，根据检测结果通过数据包的GTP-U头向UPF发送拥塞信息，UPF通过上下行数据包将拥塞信息发送给服务器，该拥塞信息用于服务器调整发送数据流的速率，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
图5示出了适用于本申请实施例提供的通信方法的另一种示意性交互图。方法500可以视为方法200的又一种具体实现方式。
在方法300中，数据包#A的GTP-U头包括拥塞信息，而在本实施例中，数据包#A的SDAP层也可以包括拥塞信息。该方法500的具体步骤如下。
步骤S510-步骤S540与步骤S310-步骤S340相同，在此不进行赘述。
S550，接入网设备进行拥塞检测。
该过程可参考S210的介绍。
一种实现方式中，接入网设备预配置需要进行拥塞检测的数据流的数据流标识。接入网设备根据拥塞检测信息中的QFI#A属于上述预配置的数据流标识，确定需要对数据流#A进行拥塞检测，并对该数据流#A进行检测获得拥塞检测结果。
另一种实现方式中，接入网设备根据拥塞标识和QFI#A确定该QFI#A判断需要对数据流#A进行拥塞检测，对该数据流#A进行检测获得拥塞检测结果。
可以理解，该拥塞标识用于指示对QFI#A对应的数据流进行拥塞检测并反馈拥塞信息。
接入网设备进行拥塞检测的方式可以参考方法200中的步骤S210，在此不进行赘述。
具体的，接入网设备在进行拥塞检测后，在相应的数据包的SDAP层中携带拥塞信息，用于后续向AF/AS反馈拥塞信息，从而AF/AS可以根据该拥塞信息来对数据的传输速率进行调整。
作为一种示例，接入网设备在数据包#A的SDAP层携带拥塞信息，包括但不仅限于以下几种方式：
a，数据包#A的SDAP层包括拥塞信息，可携带队列时延值、丢包数量、缓冲区大小信息、周期性、拥塞等级、降速比例等信息中的至少一个；
b，数据包#A的SDAP层包括是否拥塞，携带队列时延与阈值时延比例、丢包比例、缓冲区比例信息、周期性、拥塞等级、降速比例等信息中的至少一个。
以上举例仅为示例性说明，对本申请实施例不构成任何限定。
S560，接入网设备向UE发送拥塞信息。
具体地，接入网设备通过SDAP层向UE发送拥塞信息。
可以理解，接入网设备通过Uu接口向UE发送数据包#A，在该数据包#A的SDAP层包括拥塞信息。
可选的，接入网设备可以在向UE发送拥塞信息之前，接入网设备可以判断是否满足反馈条件(作为第一条件的一例)。若接入网设备判断拥塞检测结果满足反馈条件，则接入网设备向UE发送该拥塞信息，相反的，若接入网设备判断拥塞检测结果不满足反馈条件，则不向UE发送该拥塞信息或者禁止、停止发送该拥塞信息。
可以理解，UPF可以通过接入网设备发送的拥塞信息获取拥塞检测结果，UPF也可以从接入网设备接收拥塞检测结果，本申请实施例对此不作限定。
本实施例中，具体的反馈条件即判断方式与方法300中步骤S370中相同，可参看步骤S370中的详细说明，在此不进行赘述。
S570，UE向AF/AS发送拥塞信息。
具体地，UE通过调制解调器(MODEM)将拥塞信息转发到上层。
S580，AF/AS基于拥塞信息调整发送速率。
具体地，AF/AS基于拥塞信息计算并调整发送数据包的速率。
根据本申请实施例提供的技术方案，接入网设备基于拥塞标识和数据流标识对数据包进行拥塞检测，根据检测结果通过数据包的SDAP层向UE发送拥塞信息，进而转发给上层服务器，该拥塞信息用于服务器调整发送数据流的速率，能够为实施媒体流业务提供拥塞检测与控制，从而保障网络传输时的正常运行。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
以上，结合图2至图5详细说明了本申请实施例提供的方法。以下，结合图6至图7详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
该装置用于实现上述实施例及相关实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6示出了适用于本申请实施例提供的通信装置的一种示意性框图。
该装置600包括收发单元610，收发单元610可以用于实现相应的通信功能，收发单元610还可以称为通信接口或通信单元。
该装置600还可以包括处理单元620，处理单元620可以用于进行数据处理。
可选地，该装置600还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元620可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中不同设备的动作，例如，接入网设备、UPF网元的动作。
作为一种设计，该装置600用于执行上文各个方法实施例中接入网设备所执行的动作。
具体地，处理单元620，用于对第一数据流进行拥塞检测；收发单元610，用于根据拥塞检测结果向用户面功能UPF网元发送第一数据包，第一数据包的隧道协议用户面GTP-U头包括拥塞信息，或者，还用于根据拥塞检测结果向用户设备UE发送第一数据包，第一数据包的服务数据适配协议SDAP层包括拥塞信息，拥塞信息用于服务器调整发送第一数据流的速率。
可选地，该收发单元610还用于接收第一数据流的数据流标识。
可选地，该处理单元620还用于根据数据流标识对第一数据流进行拥塞检测。
可选地，该收发单元610还用于接收拥塞标识。
可选地，该处理单元620还用于根据数据流标识和/或拥塞标识对第一数据流进行拥塞检测。
可选地，该拥塞信息包括第一拥塞信息和第二拥塞信息，其中，第一拥塞信息为接入网设备和UPF网元之间的拥塞信息，第二拥塞信息为空口拥塞信息。
可选地，该处理单元620还用于确定拥塞检测结果满足第一条件；收发单元610向UPF网元发送第一数据包，或者，向UE发送第二数据包。
可选地，该收发单元610具体用于接收来自UPF网元的第一数据包，第一数据包包括数据流标识；或者，收发单元610接收来自SMF网元的拥塞检测信息，拥塞检测信息包括数据流标识。
可选地，该第一数据包为数据流传输数据的数据包或接入网设备或UPF网元生成的监测数据包。
可选地，该第一数据流为拥塞检测策略控制与计费PCC规则中与服务质量QoS流绑定的数据流。
可选地，该拥塞检测信息包括队列时延、拥塞上报时间，丢包率、缓存区大小、周期性、拥塞等级、降速比例中的至少一个。
可选地，该拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
可选地，第一数据包和第二数据包相同，或者，第一数据包和第二数据包不同。
该装置600可实现对应于根据本申请实施例的方法实施例中的接入网设备执行的步骤或者流程，该装置600可以包括用于执行图3、图4和图5所示实施例中的接入网设备执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为一种设计，该装置600用于执行上文各个方法实施例中UPF网元所执行的动作。
具体地，收发单元610，用于接收来自接入网设备的第一数据包，第一数据包的隧道协议用户面GTP-U头包括第一拥塞信息；收发单元610还用于根据第一拥塞信息向服务器发送第二拥塞信息，第二拥塞信息用于服务器调整发送数据流的速率。
可选地，收发单元具体用于向服务器发送第二数据包，第二数据包包括第二拥塞信息。
可选地，收发单元610用于通过用户设备UE向服务器发送第二拥塞信息。
可选地，收发单元具体用于向UE发送下行数据包，下行数据包包括第二拥塞信息。
可选地，收发单元具体用于通过会话管理功能或网络开放功能向服务器发送第二拥塞信息。
可选地，处理单元620还用于确定拥塞检测结果或第一拥塞信息满足第一条件；收发单元610用于向服务器发送拥塞信息。
可选地，第一数据包为数据流的数据包或接入网设备或UPF网元生成的监测数据包。
可选地，拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞 等级、降速比例中的至少一个。
该装置600可实现对应于根据本申请实施例的方法实施例中的接入网设备执行的步骤或者流程，该装置600可以包括用于执行图3、图4和图5所示实施例中的UPF网元执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为一种设计，该装置600用于执行上文各个方法实施例中终端设备UE所执行的动作。
具体地，收发单元610，用于接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息，或者该第一数据包的SDAP层包括第一拥塞信息，该第一拥塞信息用于服务器调整数据流的发送速率；收发单元610还用于根据该第一拥塞信息，向服务器发送第二拥塞信息。
可选地，收发单元610具体用于从用户面功能接收第一数据包，该第一数据包的GTP-U头包括第一拥塞信息。
可选地，收发单元610具体用于从接入网设备接收第一数据包，该第一数据包的SDAP层包括第一拥塞信息。
可选地，收发单元610还用于通过modem向服务器发送第二拥塞信息。
该装置600可实现对应于根据本申请实施例的方法实施例中的接入网设备执行的步骤或者流程，该装置600可以包括用于执行图3、图4和图5所示实施例中的UE执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
图7示出了种适用于本申请实施例提供的通信装置的一种示意性架构图。
该装置700包括处理器710，处理器710与存储器720耦合，存储器720用于存储计算机程序或指令和/或数据，处理器710用于执行存储器720存储的计算机程序或指令，或读取存储器720存储的数据，以执行上文各方法实施例中的方法。如图7所示，该装置700还包括收发器730，收发器730用于信号的接收和/或发送。例如，处理器710用于控制收发器730进行信号的接收和/或发送。
可选地，处理器710为一个或多个。
可选地，存储器720为一个或多个。
可选地，该存储器720与该处理器710集成在一起，或者分离设置。
作为一种方案，该装置700用于实现上文各个方法实施例中由接入网设备和UPF网元执行的操作。
例如，处理器710用于执行存储器720存储的计算机程序或指令，以实现上文各个方法实施例中接入网设备的相关操作。例如，图3、图4和图5所示实施例中的接入网设备执行的方法。
又如，处理器710用于执行存储器720存储的计算机程序或指令，以实现上文各个方 法实施例中终端设备的相关操作。例如，图3、图4和图5所示实施例中的UPF网元执行的方法。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例的功能。
本申请还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
本申请还提供一种系统，其包括前述的第一接入网设备、第二接入网设备、接入与移动性管理功能设备和第一会话管理功能设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁 性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
在本申请实施例中，“示例的”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。本申请中所有节点、消息的名称仅仅是本申请为描述方便而设定的名称，在实际网络中的名称可能不同，不应理解本申请限定各种节点、消息的名称，相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下UE或者基站会做出相应的处理，并非是限定时间，且也不要求UE或基站实现时一定要有判断的动作，也不意味着存在其它限定。
需要说明的是，本申请实施例中，“预先设定”、“预先配置”等可以通过在设备(例如，终端设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定，例如本申请实施例中预设的规则、预设的常数等。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本文中术语“……中的至少一个”或“……中的至少一种”，表示所列出的各项的全部或任意组合，例如，“A、B和C中的至少一种”，可以表示：单独存在A，单独存在B，单独存在C，同时存在A和B，同时存在B和C，同时存在A、B和C这六种情况。本文中的“至少一个”表示一个或者多个。“多个”表示两个或者两个以上。
应理解，在本申请各实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
应理解，在本申请的各种实施例中，第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的信息等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    接入网设备对第一数据流进行拥塞检测；
    所述接入网设备根据拥塞检测结果向用户面功能发送第一数据包，所述第一数据包的隧道协议用户面GTP-U头包括拥塞信息，或者，所述接入网设备根据所述拥塞检测结果向用户设备UE发送第二数据包，所述第二数据包的服务数据适配协议SDAP层包括所述拥塞信息，所述拥塞信息用于服务器调整发送所述第一数据流的速率。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收所述第一数据流的数据流标识。
  3. 根据权利要求2所述的方法，其特征在于，所述接入网设备对第一数据流进行拥塞检测，包括：
    所述接入网设备根据所述数据流标识对所述第一数据流进行拥塞检测。
  4. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收拥塞标识。
  5. 根据权利要求4所述的方法，其特征在于，所述接入网设备对第一数据流进行拥塞检测，包括：
    所述接入网设备根据所述数据流标识和/或所述拥塞标识对所述第一数据流进行拥塞检测。
  6. 根据权利要求1-5项中任一项所述的方法，其特征在于，所述拥塞信息包括第一拥塞信息和第二拥塞信息，其中，所述第一拥塞信息为所述接入网设备和所述用户面功能之间的拥塞信息，所述第二拥塞信息为所述接入网设备和所述UE之间的拥塞信息。
  7. 根据权利要求1-6项中任一项所述的方法，其特征在于，所述接入网设备根据拥塞检测结果向用户面功能发送第一数据包，或者，所述接入网设备根据所述拥塞检测结果向用户设备UE发送所述第二数据包，包括：
    所述接入网设备确定所述拥塞检测结果满足第一条件；
    所述接入网设备向所述用户面功能发送所述第一数据包，或者，所述接入网设备向所述UE发送所述第二数据包。
  8. 根据权利要求2所述的方法，其特征在于，所述接入网设备接收所述第一数据流的数据流标识，包括：
    所述接入网设备接收来自所述用户面功能的所述第一数据包，所述第一数据包包括所述数据流标识；
    或者，
    所述接入网设备接收来自SMF网元的拥塞检测信息，所述拥塞检测信息包括所述数据流标识。
  9. 根据权利要求8所述的方法，其特征在于，所述拥塞检测信息还包括队列时延、拥塞上报时间，丢包率、缓存区大小、周期性、拥塞等级、降速比例中的至少一个。
  10. 根据权利要求1-9项中任一项所述的方法，其特征在于，所述第一数据流为协议数据单元PDU会话中与拥塞检测策略控制与计费PCC规则绑定的服务质量QoS流。
  11. 根据权利要求1-10项中任一项所述的方法，其特征在于，所述第一数据包或所述第二数据包为用于传输所述数据流的数据的数据包，或者，所述第一数据包或所述第二数据包为所述接入网设备或所述用户面功能生成的监测数据包。
  12. 根据权利要求1-11项中任一项所述的方法，其特征在于，所述拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
  13. 根据权利要求1-11项中任一项所述的方法，其特征在于，所述第一数据包和所述第二数据包相同，或者，所述第一数据包和所述第二数据包不同。
  14. 一种通信方法，其特征在于，包括：
    用户面功能能接收来自接入网设备的第一数据包，所述第一数据包的隧道协议用户面GTP-U头包括第一拥塞信息；
    所述用户面功能根据所述第一拥塞信息向服务器发送第二拥塞信息，所述第二拥塞信息用于所述服务器调整发送第一数据流的速率。
  15. 根据权利要求14所述的方法，其特征在于，所述用户面功能向服务器发送所述第二拥塞信息，包括：
    所述用户面功能向所述服务器发送第二数据包，所述第二数据包包括所述第二拥塞信息。
  16. 根据权利要求14或15所述的方法，其特征在于，所述用户面功能向服务器发送所述第二拥塞信息，包括：
    所述用户面功能通过用户设备UE向服务器发送所述第二拥塞信息。
  17. 根据权利要求16所述的方法，其特征在于，所述用户面功能通过用户设备UE向服务器发送所述第二拥塞信息，包括：
    所述用户面功能向所述UE发送下行数据包，所述下行数据包包括所述第二拥塞信息。
  18. 根据权利要求14-17项中任一项所述的方法，其特征在于，所述用户面功能向服务器发送所述第二拥塞信息，包括：
    所述用户面功能通过会话管理功能或网络开放功能向服务器发送所述第二拥塞信息。
  19. 根据权利要求14-18项中任一项所述的方法，其特征在于，所述用户面功能向服务器发送所述第二拥塞信息，包括：
    所述用户面功能确定所述第一拥塞信息满足第一条件，或者所述用户面功能根据所述第一拥塞信息确定拥塞检测结果满足第一条件；
    所述用户面功能向所述服务器发送所述第二拥塞信息。
  20. 根据权利要求14-19项中任一项所述的方法，其特征在于，所述第一数据包为所述数据流传输数据的数据包或所述接入网设备或所述用户面功能生成的监测数据包。
  21. 根据权利要求14-19项中任一项所述的方法，其特征在于，所述拥塞信息包括队列时延与阈值时延比例、丢包比例、缓存区大小比例、拥塞等级、降速比例中的至少一个。
  22. 一种通信装置，其特征在于，包括：
    用于实现权利要求1至21项中任一项所述的方法的模块或单元。
  23. 一种通信系统，其特征在于，包括执行如权利要求1至21项中任一项所述的通信方法的模块或单元，或者包括实现如权利要求1至权利要求21项中任一项所述方法的通信装置。
  24. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述通信装置执行权利要求1至21项中任一项所述的通信方法。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至21项中任意一项所述的通信方法。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至21项中任一项所述的通信方法的指令。
PCT/CN2023/082830 2022-03-28 2023-03-21 通信方法和装置 WO2023185552A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210311737.XA CN116866981A (zh) 2022-03-28 2022-03-28 通信方法和装置
CN202210311737.X 2022-03-28

Publications (1)

Publication Number Publication Date
WO2023185552A1 true WO2023185552A1 (zh) 2023-10-05

Family

ID=88199259

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082830 WO2023185552A1 (zh) 2022-03-28 2023-03-21 通信方法和装置

Country Status (2)

Country Link
CN (1) CN116866981A (zh)
WO (1) WO2023185552A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118102382B (zh) * 2024-04-07 2024-09-06 荣耀终端有限公司 一种数据处理方法及相关设备
CN118101134B (zh) * 2024-04-08 2024-10-29 荣耀终端有限公司 编码速率调整方法及设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223663A (zh) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 一种获取网络负荷的方法及系统
US20200382992A1 (en) * 2019-08-16 2020-12-03 Intel Corporation V2x qos and congestion control for new radio (nr) systems
US20200404531A1 (en) * 2019-06-24 2020-12-24 Verizon Patent And Licensing Inc. Integration of radio and core layers
CN112423340A (zh) * 2019-08-21 2021-02-26 华为技术有限公司 一种用户面信息上报方法及装置
US20210235291A1 (en) * 2018-07-20 2021-07-29 Lg Electronics Inc. Method and apparatus for supporting link congestion detection in wireless communication system
US20220038946A1 (en) * 2019-02-08 2022-02-03 Lg Electronics Inc. Method by which nwdaf transmits and receives signal in wireless communication system, and device therefor

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223663A (zh) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 一种获取网络负荷的方法及系统
US20210235291A1 (en) * 2018-07-20 2021-07-29 Lg Electronics Inc. Method and apparatus for supporting link congestion detection in wireless communication system
US20220038946A1 (en) * 2019-02-08 2022-02-03 Lg Electronics Inc. Method by which nwdaf transmits and receives signal in wireless communication system, and device therefor
US20200404531A1 (en) * 2019-06-24 2020-12-24 Verizon Patent And Licensing Inc. Integration of radio and core layers
US20200382992A1 (en) * 2019-08-16 2020-12-03 Intel Corporation V2x qos and congestion control for new radio (nr) systems
CN112423340A (zh) * 2019-08-21 2021-02-26 华为技术有限公司 一种用户面信息上报方法及装置

Also Published As

Publication number Publication date
CN116866981A (zh) 2023-10-10

Similar Documents

Publication Publication Date Title
US11968565B2 (en) User plane information reporting method and apparatus
WO2023185552A1 (zh) 通信方法和装置
WO2020143061A1 (zh) 用于资源建立的方法及设备
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
WO2022012212A1 (zh) 一种资源调度方法、通信装置及系统
WO2021212341A1 (zh) 用户设备能力上报方法、设备及计算机可读存储介质
JP5767223B2 (ja) 遅延時間を規定する拒否応答
WO2020083263A1 (zh) WiFi网络中的数据传输方法、装置及设备
WO2022110214A1 (zh) 通信方法及装置
EP2560455B1 (en) Systems and methods for multiple radio access bearer traffic throttling
KR20210021059A (ko) 멀티-홉 데이터 전달에서의 서비스 품질 실현
WO2022016948A1 (zh) 一种通信方法及装置
WO2016015244A1 (zh) 多通信制式传输方法及装置
US12133096B2 (en) Data transmission method, apparatus, and device
WO2021023185A1 (zh) 一种接入限制检测方法和装置
WO2020051745A1 (zh) 一种数据传输方法及装置、通信设备
US11647419B2 (en) Adjusting window size based on quality of experience
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2022155977A1 (zh) 通信方法和装置
WO2022151206A1 (zh) 通信方法和网络设备
WO2023125310A1 (zh) 一种通信方法及通信装置
WO2023273880A1 (zh) 传输方式切换的方法和相关装置
WO2022063187A1 (zh) 一种通信方法和装置
WO2021142767A1 (zh) 通信方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23777925

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023777925

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023777925

Country of ref document: EP

Effective date: 20240924