WO2023284551A1 - 通信方法、装置和系统 - Google Patents

通信方法、装置和系统 Download PDF

Info

Publication number
WO2023284551A1
WO2023284551A1 PCT/CN2022/102224 CN2022102224W WO2023284551A1 WO 2023284551 A1 WO2023284551 A1 WO 2023284551A1 CN 2022102224 W CN2022102224 W CN 2022102224W WO 2023284551 A1 WO2023284551 A1 WO 2023284551A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
application
data packet
tunnel
user plane
Prior art date
Application number
PCT/CN2022/102224
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 华为技术有限公司
Priority to EP22841189.8A priority Critical patent/EP4354948A1/en
Publication of WO2023284551A1 publication Critical patent/WO2023284551A1/zh

Links

Images

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
    • 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/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present application relates to the communication field, and more specifically, to a communication method, device and system.
  • burst data may appear during the data transmission process, and the burst data may cause the queue to rise instantaneously. It will have a relatively large impact on the network.
  • the base station may not be able to process all the data packets at that moment, resulting in degradation of user experience.
  • the present application provides a communication method, device and system, in order to improve user experience by distinguishing and processing different types of data packets.
  • a communication method includes: a session management network element acquires a first rule, the first rule includes a quality of service (quality of service, QoS) parameter corresponding to an applied frame type; the session management The network element sends first indication information to the user plane network element according to the first rule, and the first indication information is used to instruct the user plane network element to determine the identifier of the QoS flow (QoS flow) corresponding to the data packet of the application according to the frame type ID, QFI), the data packet of the application is encapsulated in the first data packet, and the first data packet includes the frame type.
  • QoS quality of service
  • the first indication information here may correspond to indication information #1 in the specific implementation manner.
  • the first indication information includes the frame type and the QFI corresponding to the frame type.
  • the first indication information may be the correspondence between the frame type and the QFI.
  • the first indication information may be included in a packet detection rule (packet detection rule, PDR), and correspondingly, the QFI and the frame type are included in the PDR.
  • PDR packet detection rule
  • the user plane network element after receiving the first indication information, the user plane network element locally saves the corresponding relationship between the frame type and the QFI, so that after the user plane network element obtains the frame type corresponding to the application from the first data packet, it can according to The correspondence determines the QFI corresponding to the frame type.
  • the data packet can be differentiated according to the frame type of the data packet (or different types of frames can be Different QoS processing) to meet the different transmission requirements of different frame types, thereby improving user experience and preventing the network from being unable to distinguish between different types of data packets, resulting in inability to guarantee smoothness in some cases, such as network congestion user experience.
  • the session management network element receives the first rule from the policy control network element.
  • the policy control network element receives the application information of the application from the application function network element or the multi-access mobile computing platform, and the application information includes the frame type and QoS requirements corresponding to the application. It should be understood that the application information may include multiple different frame types of the application and different QoS requirements corresponding to different frame types.
  • the policy control network element generates a first rule according to the application information of the application, and sends the first rule to the session management network element, where the first rule includes a QoS parameter corresponding to the frame type, wherein the QoS parameter is based on the QoS requirement Sure.
  • the application information of the application may include QoS requirements corresponding to different service flows of the application, and different service flows correspond to different frame types.
  • the policy control network element can determine QoS parameters corresponding to different service flows according to the QoS requirements corresponding to different service flows.
  • the session management network element determines the first rule according to local configuration. That is to say, the QoS parameter corresponding to the frame type of the application can be configured for the session management network element in a pre-configuration manner.
  • the first rule here may be, for example, a policy and charging control (PCC) rule.
  • PCC policy and charging control
  • the first data packet includes the frame type, or it can be said that the first data packet carries the frame type, for example, the frame type is carried in a tunnel header or an extension header in the first data packet.
  • the data packet of the application is transmitted through a first tunnel, the first data packet includes a tunnel header of the first tunnel, and the tunnel header of the first tunnel includes the Frame type; the first indication information is used to indicate that the user plane network element determines the identifier QFI of the quality of service QoS flow corresponding to the application data packet according to the frame type, including: the first indication information is used to indicate that the user plane network The element determines the QFI according to the frame type in the tunnel header of the first tunnel.
  • the data packet of the application here may refer to a data packet of a certain service flow of the application.
  • the user plane network element receives the data packet of the application through the first tunnel, or will pass through the first tunnel.
  • the first tunnel here is, for example, the tunnel between the application server and the user plane network element, or the tunnel between the multi-access edge computing platform and the user plane network element, and the tunnel here may be called an N6 tunnel in some scenarios.
  • This solution carries the frame type corresponding to the data packet through the tunnel header of the N6 tunnel, which can allow the core network equipment to distinguish the QoS flow corresponding to the data packet according to the frame type without modifying the application layer protocol.
  • the first indication information is used to instruct the user plane network element to determine the identifier QFI of the QoS flow corresponding to the data packet of the application according to the frame type, including: the The first indication information is used to indicate that the user plane network element determines the QFI according to the Internet protocol (internet protocol, IP) header and the frame type of the application data packet; or, the first indication information is used to indicate the user plane network The element determines the QFI according to the identifier of the first tunnel and the frame type, and the identifier of the first tunnel is included in the tunnel header of the first tunnel.
  • IP Internet protocol
  • the first tunnel when the first tunnel is a device-level tunnel, that is, the first tunnel is a device-specific tunnel, the first tunnel may correspond to multiple different service flows, and at this time, the IP address of the data packet of the application
  • the identification information of the application is carried in the header, so as to determine the application corresponding to the data packet. Therefore, the first indication information indicates that the user plane network element determines the QFI corresponding to the application data packet according to the IP header and frame type of the application data packet.
  • the first indication information indicates that the user plane network element determines the QFI corresponding to the application data packet
  • the application identification information carried in the IP header of the packet determines the application corresponding to the data packet, and then further determines the QFI corresponding to the application through the frame type; when the first tunnel is an application-level tunnel, that is, the first tunnel is application-specific
  • the identification information of the application does not need to be carried in the IP header.
  • the service flow corresponding to the data packet can be determined through the identification of the first tunnel, and the identification of the first tunnel can be included in the tunnel header of the tunnel. Therefore, the first indication information instructs the user plane network element to determine the QFI according to the identifier of the first tunnel and the frame type.
  • the user plane network element can also determine and apply the corresponding QFI according to the frame type for different types of tunnels, so that different QoS processes can be performed on different types of frames.
  • the method further includes: the session management network element determines that the data packet of the application is sent to the user plane network element through the first tunnel.
  • the session management network element can instruct the user plane network element in advance to determine the QoS flow corresponding to the data packet of the application according to the frame type in the tunnel header , so that when the user plane network element receives the data of the application through the tunnel, it knows how to process it, which can improve the processing efficiency.
  • the session management network element determines that the data packet of the application is sent to the user plane network element through the first tunnel, including: the session management network element receives the The second indication information of the network element; the session management network element determines according to the second indication information that the data packet of the application is sent to the user plane network element through the first tunnel; or, the session management network element determines the The application data packet will be sent to the user plane network element through the first tunnel.
  • the session management network element before the session management network element sends the first indication information, it determines that the data packet of the application will be sent to the user plane network element through the tunnel, or the session management network element determines that the data packet of the application will be transmitted through the tunnel, Further, the session management network element instructs the user plane network element to determine the QFI corresponding to the data packet of the application according to the frame type in the tunnel header of the first tunnel. Moreover, the session management network element can determine that the data packets of the application will be transmitted through the tunnel according to the configuration information, or determine that the data packets of the application will be transmitted through the tunnel according to the instruction information from the policy control network element.
  • the policy control network element may carry the indication information in the first rule and send it to the session management network element.
  • the first data packet includes an extension header, and the extension header includes the frame type; the first indication information is used to indicate that the user plane network element Determining the identifier QFI of the quality of service QoS flow corresponding to the data packet of the application includes: the first indication information is used to instruct the user plane network element to determine the QFI according to the frame type in the extension header.
  • the data packets of the application are not transmitted through a tunnel, but based on a user plane protocol.
  • the first data packet is an IP packet
  • the first data packet includes an extension header
  • the extension header includes a frame type corresponding to the service flow.
  • the extension header here is, for example, an SRV6 extension header, or an IPv6 extension header.
  • the user plane network element can obtain the frame type corresponding to the application in the extension header, so that different QoS processes can be performed on different types of frames.
  • the method further includes: the session management network element determining the QFI corresponding to the frame type according to the QoS parameter corresponding to the frame type.
  • the session management network element can send the frame type and the QFI corresponding to the frame type to the user plane network element, so that the user plane network element can determine the frame type after obtaining the application frame type in the first data packet.
  • the QoS flow corresponding to the frame type so that different QoS processing can be performed on different types of frames.
  • the method further includes: the session management network element sending third indication information to the user plane network element, where the third indication information is used to indicate that the user plane network element The element sends the data packet of the application through the second tunnel, and the tunnel header of the second tunnel includes the QFI.
  • the third indication information is used to instruct the user plane network element to send the data packet of the application to a downlink node (for example, a radio access network device) through the QoS flow identified by the QFI.
  • the third indication information may be included in the PDR.
  • the third indication information may correspond to indication information #2 in the specific implementation manner.
  • first indication information and the third indication information may be carried in the same message, or may be carried in different messages.
  • the second tunnel is a tunnel for sending the data of the application to the downlink node, for example, the second tunnel is a GTP-U tunnel.
  • the application data packet can be sent to the access network device through the second tunnel so that the access network device can schedule the data according to the frame type of the data packet.
  • the first data packet further includes frame information of a frame corresponding to the application data packet, where the frame information includes the frame type, fourth indication information, One or more of the size information of the frame, the QoS requirement information of the frame, the fourth indication information is used to indicate the frame to which the data packet of the application belongs; the method also includes: the session management network element sends the user The network element on the plane sends fifth indication information, where the fifth indication information is used to instruct the network element on the user plane to carry the frame information in the tunnel header of the second tunnel.
  • the fourth indication information may be a frame number, and the frame number may identify the frame to which the data packet of the application belongs, or may identify the sequence number of the frame and the sequence number of the data packet of the application in the frame; or, the fourth indication information It is the frame header identifier and the frame tail identifier, and the data packets between the frame header and the frame tail are data packets of the same frame.
  • the fourth indication information is used to indicate whether the data packet of the application belongs to the same frame as a certain known data packet.
  • the network side can conveniently identify the frame to which the data packet belongs, so as to perform frame granularity scheduling.
  • the method further includes: the session management network element sending sixth indication information to the user plane network element, where the sixth indication information is used to indicate that the user plane network element The first tunnel is established; the session management network element receives information of the first tunnel from the user plane network element.
  • the session management network element before the session management network element sends the sixth indication information to the user plane network element, the session management network element receives eleventh indication information from the policy control network element, where the eleventh indication information is used to indicate the establishment The first tunnel.
  • a communication method includes: a user plane network element receives a first data packet, the first data packet includes an application data packet of an application and a frame type corresponding to the application data packet; the user The plane network element determines the identifier QFI of the QoS flow corresponding to the data packet of the application according to the frame type.
  • the user plane network element may determine the QFI corresponding to the data packet of the application according to the indication information received from the session management network element, where the indication information may specifically be the association relationship between the frame type of the data packet of the application and the QFI.
  • the user plane network element can save the association relationship, and after receiving the first data packet, obtain the frame type of the service flow from the first data packet, and determine the data packet of the application according to the locally saved association relationship and the frame type Corresponding QFI. It should be understood that the user plane network element may be the first data packet received from the application function network element or the multi-access edge computing platform or the application server.
  • the user plane network element can determine the QoS flow corresponding to the applied data packet according to the frame type in the first data packet, so that different QoS processing can be performed on different types of frames to meet different transmission requirements of different frame types.
  • the receiving the first data packet by the user plane network element includes: receiving the first data packet by the user plane network element through a tunnel, and the first data packet includes the The tunnel header of the first tunnel, the tunnel header of the first tunnel includes the frame type; the user plane network element determines the identifier QFI of the QoS flow corresponding to the data packet of the application according to the frame type, including: the user plane network element according to the frame type The frame type in the tunnel header of the first tunnel determines the QFI corresponding to the data packet of the application.
  • the frame type of the data packet is carried by the tunnel header, so that the user plane network element can determine the QFI corresponding to the applied data packet according to the frame type, so that different types of frames can be distinguished and processed.
  • the user plane network element determines the identifier QFI of the QoS flow corresponding to the data packet of the service flow according to the frame type, including: the user plane network element according to the application The Internet Protocol IP header of the data packet and the frame type determine the QFI corresponding to the data packet; or, the user plane network element determines the QFI corresponding to the application data packet according to the identifier of the first tunnel and the frame type, the second A tunnel identifier is included in the tunnel header of the first tunnel.
  • the first tunnel When the first tunnel is a device-level tunnel, that is, the first tunnel is a device-specific tunnel, the first tunnel may correspond to multiple different applications, and at this time, the IP header of the data packet of the application carries the identification of the application Information for determining the application corresponding to the data packet. Therefore, the user plane network element determines the QFI corresponding to the application according to the IP header and frame type of the application data packet. It can be understood that the user plane network element determines the data packet according to the application identification information carried in the IP header of the application data packet.
  • the corresponding application and then further determine the QFI corresponding to the application through the frame type corresponding to the application; when the first tunnel is an application-level tunnel, that is, the first tunnel is an application-specific tunnel, at this time, it is not necessary to use the IP
  • the identification information of the application is carried in the header, and the application corresponding to the data packet can be determined through the identification of the first tunnel, and the identification of the first tunnel can be included in the tunnel header of the tunnel. Therefore, the user plane network element determines the QFI according to the identifier of the first tunnel and the frame type.
  • the user plane network element can also determine and apply the corresponding QFI according to the frame type for different types of tunnels, so that different QoS processes can be performed on different types of frames.
  • the frame type is included in the extension header of the first data packet
  • the user plane network element determines the QoS flow corresponding to the application data packet according to the frame type
  • the identification QFI includes: the user plane network element determines the QFI corresponding to the data packet of the application according to the frame type in the extension header.
  • the user plane network element can obtain the frame type corresponding to the application in the extension header, so that different QoS processes can be performed on different types of frames.
  • the method further includes: sending, by the user plane network element, the data packet of the application through a second tunnel, where a tunnel header of the second tunnel includes the QFI.
  • the application data packet can be sent to the access network device through the second tunnel so that the access network device can schedule the data according to the frame type of the data packet.
  • the first data packet further includes frame information of a frame corresponding to the application data packet, where the frame information includes the frame type, fourth indication information, the One or more of the size information of the frame and the QoS requirement information of the frame, the fourth indication information is used to indicate the frame to which the data packet of the application belongs, and the tunnel header of the second tunnel includes the frame information.
  • the network side can conveniently identify the frame to which the data packet belongs, so as to perform frame granularity scheduling.
  • the method further includes: the user plane network element receiving first indication information, where the first indication information is used to instruct the user plane network element to The QFI is determined according to the frame type in the tunnel header or according to the frame type in the extension header.
  • the method further includes: the user plane network element receiving third indication information, where the third indication information is used to instruct the user plane network element to pass through the second tunnel
  • the data packet of the application is sent, and the tunnel header of the second tunnel includes the QFI.
  • the method further includes: the user plane network element receiving fifth indication information, where the fifth indication information is used to indicate that the user plane network element is in the second tunnel
  • the frame information is carried in the tunnel header.
  • the method further includes: the user plane network element receiving sixth indication information from the session management network element; the user plane network element establishing an The first tunnel.
  • a communication method includes: a policy control network element receives application information, and the application information includes a frame type corresponding to a data packet of the application; the policy control network element sends a session management network element QoS parameters corresponding to the frame type.
  • the information of the first application indicates to create a first tunnel, and the first tunnel is used to send the data packet of the application to the user plane network element; the method also includes : the policy control network element sends eleventh indication information to the session management network element, where the eleventh indication information is used to instruct the session management network element to establish the first tunnel.
  • the method further includes: the policy control network element receives the information of the first tunnel from the session management network element; the policy control network element sends the first tunnel information to the first tunnel The application function network element corresponding to the application sends the information of the first tunnel.
  • the first tunnel is a tunnel corresponding to the first application or the first service flow.
  • the information of the first application is also used to indicate that the first service flow or the data packet of the first application is sent to the user plane network element through the first tunnel
  • the policy control network element sends fifth indication information to the session management network element, where the fifth indication information is used to instruct that the data packet of the application is sent to the user plane network element through the first tunnel.
  • the information of the first application is also used to instruct to send the frame information of the frame corresponding to the data packet of the first application to the access network device, and the frame
  • the information includes one or more of the frame type, third indication information, size information of the frame, and QoS requirement information of the frame, and the third indication information is used to indicate the frame to which the data packet of the application belongs;
  • the policy The control network element sends seventh indication information to the session management network element, where the seventh indication information is used to instruct to send the frame information to the access network device.
  • the policy control network element sends the QoS parameter corresponding to the frame type to the session management network element, including: the policy control network element determines according to the information of the first application A first rule, where the first rule includes QoS parameters corresponding to the frame type; the policy control network element sends the first rule to the session management network element.
  • a communication method includes: the session management network element receives application feature information from the application function network element; the session management network element sends the application feature information and the seventh indication information to the user plane network element, The seventh indication information is used to instruct the user plane network element to determine the frame type corresponding to the data packet of the application according to the feature information.
  • the characteristic information is used to determine the frame type corresponding to the data packet, therefore, the characteristic information here is related to the frame.
  • the characteristic information of the application and the seventh indication information may be carried in the same message, or may be carried in different messages. That is to say, the session management network element can send the characteristic information of the application and the seventh indication information to the network element of the user plane at the same time, or can send the characteristic information of the application and the seventh indication information to the network element of the user plane in two consecutive messages Or, after sending the characteristic information of the application to the user plane network element, the seventh indication information can be sent after a period of time, for example, after the session management network element determines the QoS flow according to the QoS parameters of different frame types, and then sends the user plane The network element sends seventh indication information.
  • the above technical method can distinguish the frame types corresponding to different data packets by instructing the user plane network element to determine the frame type corresponding to the data packet according to the feature information, so that different types of frames can be differentiated and processed.
  • the characteristic information includes the sending rule of the application frame, the burst size of the application frame, the interval between the application frames, and the application IP At least one of header information, the application's identifier, and the application's type.
  • the method further includes: the session management network element receiving the QoS parameter corresponding to the frame type; the session management network element determining the QoS parameter corresponding to the frame type A QoS flow corresponding to the frame type; the session management network element sends eighth indication information to the user plane network element, where the eighth indication information is used to instruct the user plane network element to send the data packet corresponding to the frame type through the QoS flow.
  • the application data packet can be sent to the access network device through the second tunnel so that the access network device can schedule the data according to the frame type of the data packet.
  • the eighth indication information is used to instruct the user plane network element to send the data packet corresponding to the frame type through the QoS flow, including: the eighth indication information uses Instructing the user plane network element to send the data packet corresponding to the frame type through the second tunnel, the data packet is encapsulated in the second data packet, the second data packet also includes the tunnel header of the second tunnel, and the second tunnel
  • the tunnel header includes the frame information corresponding to the data packet and the identifier QFI of the QoS flow
  • the frame information includes one or more of the frame type
  • the ninth indication information, the size information of the frame, and the QoS requirement information of the frame item the ninth indication information is used to indicate the frame to which the data packet of the application belongs.
  • the method further includes: the session management network element sending tenth indication information to the user plane network element, where the tenth indication information is used to indicate that the user plane network element
  • the element detects the frame to which the data packet of the application belongs according to the feature information.
  • the tenth indication information can also be used to instruct the user plane network element to detect other frame information of the frame to which the data packet of the application belongs according to the feature information, such as the size information of the frame, the relative position of the data packet in the frame Positional information (e.g. relative to the frame header), which other packets this packet belongs to in the same frame, etc.
  • the method further includes: the session management network element receiving the feature information of the application from the application function network element.
  • a communication method includes: a user plane network element receives application characteristic information and seventh indication information from a session management network element; the user plane network element determines the application according to the seventh indication information The frame type corresponding to the data packet, the frame type is determined according to the characteristic information of the application.
  • the characteristic information includes the sending rule of the frame of the application, the burst size of the application, the interval between the frames of the application, and the IP header information of the application , at least one of the application identifier and the application type.
  • the method further includes: the user plane network element determines the QoS flow corresponding to the frame type according to the frame type of the application; the user plane network element passes the QoS flow Send the data packet corresponding to the frame type.
  • the user plane network element sending the data packet corresponding to the frame type through the QoS flow includes: the user plane network element sending the data packet corresponding to the frame type through the second tunnel A data packet, the data packet is encapsulated in a second data packet, the second data packet also includes a tunnel header of the second tunnel, and the second tunnel header includes the frame information corresponding to the data packet and the QFI of the QoS flow,
  • the frame information includes one or more of the frame type, ninth indication information, size information of the frame, and QoS requirement information of the frame, and the ninth indication information is used to indicate the frame to which the data packet of the application belongs.
  • the method further includes: the user plane network element detects the frame to which the data packet of the application belongs according to the feature information; the user plane network element uses the information of the frame Included in the tunnel header of this second tunnel.
  • the method further includes: the user plane network element receives seventh indication information from the session management network element, where the seventh indication information is used to indicate that the user plane The network element determines the frame type corresponding to the data packet of the application according to the feature information of the application.
  • a communication method includes: a first function receives an application data packet sent by an application server; the first function obtains frame information corresponding to the data packet, and the frame information includes the frame type, One or more of the ninth indication information, the size of the frame, and the QoS requirement information of the frame, the ninth indication information is used to indicate the frame to which the data packet of the application belongs; the first function reports to the user plane network element Send the application data packet and the frame information.
  • the first function may be, for example, an application function or a multi-access edge computing platform.
  • the method further includes: the first function receives a first message from the application server, and the first message includes the application data packet and frame information corresponding to the application data packet .
  • the method further includes: the first function sends the application data packet and the frame information to the user plane network element through a tunnel, where the frame information is included in the tunnel head.
  • the method further includes: the first function determines the tunnel identifier according to the frame type of the frame corresponding to the application data packet or the QoS requirement information of the frame, and the tunnel header includes the First tunnel ID.
  • the first function sends a third data packet to the user plane network element, where the third data packet includes the application data packet and an extension header, where the extension header includes frame information .
  • the method further includes: the first function provides a first API, and the first API is used for the application server to request the first function to prepare wireless resources for sending data of the application , the parameters of the first API include the frame type of the application and the QoS requirement information corresponding to the frame type.
  • the method further includes: the first function sends the frame type of the application and the QoS requirement information corresponding to the frame type to the network element of the core network, so as to provide the application Prepare wireless resources.
  • the method further includes that the first function sends the uplink tunnel identifier corresponding to the first tunnel to a network element of the core network, and receives a message from the network element of the user plane Downlink tunnel information.
  • the first network element determines the tunnel identifier corresponding to the frame type according to the frame type or the QoS requirement information.
  • the method further includes: the first function provides a second API, the second API is used for the application server to request the first function to send the application data packet, and the application server uses the The API sends the application data packet and the frame information corresponding to the application data packet.
  • the foregoing first message is a request message corresponding to the second API.
  • a communication method comprising: the application server calls the first API of the first function to send the frame type of the application and the QoS requirement information corresponding to the frame type to the first function for requesting the first function Prepare wireless resources for sending the data of the application; the application server calls the second API of the first function to send the application data packet, and is used for the first function to send the application data packet according to the frame type of the frame corresponding to the data packet;
  • the second API further includes frame information, and the frame information includes one or more of frame type, ninth indication information, and frame size,
  • the ninth indication information is used to indicate the frame to which the data packet of the application belongs.
  • a communication device is provided, and the device is configured to execute the methods provided in the first aspect to the eighth aspect above.
  • the apparatus may include a unit and/or module for executing the methods provided in the first aspect to the eighth aspect, such as a processing unit and/or a communication unit.
  • the apparatus is a network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the apparatus is a chip, a chip system or a circuit used in a network device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit etc.
  • the processing unit may be a processor, a processing circuit or a logic circuit and the like.
  • the device is a session management network element or a chip, a chip system or a circuit in the session management network element.
  • the device may include units and/or modules for executing the methods provided in the first aspect and the fourth aspect, such as a processing unit and/or a communication unit.
  • the device is a user plane network element or a chip, a chip system or a circuit in the user plane network element.
  • the device may include units and/or modules for executing the methods provided in the second aspect and the fifth aspect, such as a processing unit and/or a communication unit.
  • the device is a policy control network element or a chip, a chip system or a circuit in a policy control network element.
  • the apparatus may include units and/or modules for executing the method provided by the third aspect, such as a processing unit and/or a communication unit.
  • the above-mentioned transceiver may be a transceiver circuit.
  • the above input/output interface may be an input/output circuit.
  • a communication device which includes: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processor is used for executing the above-mentioned first to The method provided in the eighth aspect.
  • the apparatus is a network device (such as each network element mentioned above).
  • the apparatus is a chip, a chip system or a circuit used in network equipment (such as the above-mentioned network elements).
  • the present application provides a processor configured to execute the methods provided in the foregoing aspects.
  • the process of sending the above information and obtaining/receiving the above information in the above method can be understood as the process of outputting the above information by the processor and the process of receiving the input of the above information by the processor.
  • the processor When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver acquires/receives the above-mentioned information and inputs it to the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed before being input to the processor.
  • the receiving request message mentioned in the foregoing method may be understood as the processor receiving input information.
  • processor For the operations of transmitting, sending, and acquiring/receiving involved in the processor, if there is no special description, or if it does not conflict with its actual function or internal logic in the relevant description, it can be understood more generally as the processor Output and receive, input and other operations, rather than the transmission, transmission and reception operations performed directly by radio frequency circuits and antennas.
  • the above-mentioned processor may be a processor dedicated to performing these methods, or may be a processor that executes computer instructions in a memory to perform these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged on different chips.
  • ROM read-only memory
  • a computer-readable storage medium stores program code for execution by a device, and the program code includes a method for executing the methods provided in the first aspect to the fifth aspect.
  • a computer program product containing instructions is provided, and when the computer program product is run on a computer, it causes the computer to execute the methods provided in the first aspect to the fifth aspect.
  • a thirteenth aspect provides a chip, the chip includes a processor and a communication interface, the processor reads instructions stored in the memory through the communication interface, and executes the methods provided in the first aspect to the fifth aspect above.
  • the chip may further include a memory, the memory stores instructions, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the The processor is configured to execute the methods provided in the first aspect to the fifth aspect above.
  • a communication system including a session management network element and a user plane network element.
  • the session management network element is configured to acquire a first rule, where the first rule includes a quality of service QoS parameter corresponding to an applied frame type; and sends first indication information to a user plane network element according to the first rule, and the The first indication information is used to instruct the user plane network element to determine the identifier QFI of the QoS flow corresponding to the application data packet according to the frame type, the application data packet is encapsulated in the first data packet, the The first data packet includes the frame type; and the user plane network element is configured to receive the first indication information.
  • a communication system including a session management network element and a user plane network element.
  • the session management network element is configured to send application feature information to the user plane network element; send seventh indication information to the user plane network element, where the seventh indication information is used to instruct the user plane network element to
  • the characteristic information determines the frame type corresponding to the data packet of the application; the user plane network element is configured to determine the frame type corresponding to the data packet of the application according to the characteristic information of the application.
  • Fig. 1 shows a schematic diagram of a network architecture applicable to the embodiment of the present application.
  • FIG. 2 is a schematic diagram of a communication method 200 provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a communication method 300 provided by another embodiment of the present application.
  • Fig. 4 is a schematic diagram of a communication method 400 provided according to an embodiment of the present application.
  • FIG. 5 is a data structure diagram during data transmission through the N6 tunnel.
  • Fig. 6 is another schematic flowchart of a communication method applicable to an embodiment of the present application.
  • Fig. 7 is another schematic flowchart of a communication method applicable to an embodiment of the present application.
  • Fig. 8 is another schematic flowchart of a communication method applicable to an embodiment of the present application.
  • Fig. 9 is another schematic flowchart of a communication method applicable to an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Fig. 11 is another schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Fig. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the present application provides a communication system, which includes a session management network element and a user plane network element.
  • the session management network element is configured to obtain a first rule, where the first rule includes a quality of service (QoS) parameter corresponding to an applied frame type; send first indication information to a user plane network element according to the first rule, and the first indication
  • QoS quality of service
  • the information is used to instruct the user plane network element to determine the identifier QFI of the QoS flow corresponding to the application data packet according to the frame type, the application data packet is encapsulated in a first data packet, and the first data packet includes the frame type;
  • the user plane network element is configured to receive the first indication information.
  • the system also includes a policy control network element.
  • the policy control network element is used to receive the application information, and the application information includes the frame type corresponding to the application; and send the QoS parameter corresponding to the frame type to the session management network element.
  • the present application provides another communication system, which includes a session management network element and a user plane network element.
  • the session management network element is configured to send characteristic information of the application to the user plane network element; send seventh indication information to the user plane network element, where the seventh indication information is used to instruct the user plane network element to determine the application according to the characteristic information
  • the frame type corresponding to the data packet of the application the user plane network element is configured to determine the frame type corresponding to the data packet of the application according to the characteristic information of the application.
  • the system also includes application function network elements.
  • the application function network element is configured to send the feature information of the application to the session management network element.
  • the technical solution provided by this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division Duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type Communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • M2M machine type Communication
  • MTC machine type communication
  • IoT Internet of things
  • FIG. 1 it is a schematic diagram of a fifth generation (5th generation, 5G) network architecture based on a service architecture.
  • the session management network element in Figure 1(a) and Figure 1(b) may be the SMF in Figure 1(c), and the user plane network element in Figure 1(a) and Figure 1(b) It can be the UPF in (c) of Figure 1, the policy control network element in (a) of Figure 1 can be the PCF in (c) of Figure 1, and the application function network element in (b) of Figure 1 can be AF in (c) of Fig. 1 .
  • the 5G network architecture shown in (c) of FIG. 1 may include three parts, namely a terminal device part, a data network (data network, DN) and an operator network part.
  • a terminal device part namely a terminal device part, a data network (data network, DN) and an operator network part.
  • DN data network
  • operator network part namely a data network (data network, DN) and a operator network part.
  • the operator network may include one or more of the following network elements: authentication server function (authentication server function, AUSF) network element, network exposure function (network exposure function, NEF) network element, policy control function (policy control function, PCF) network element, unified data management (unified data management, UDM) network element, unified database (unified data repository, UDR), network storage function (network repository function, NRF) network element, application function (application function, AF) ) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, radio access network (radioaccess network, RAN) and user plane functions (user plane function, UPF) network element, etc.
  • authentication server function authentication server function, AUSF
  • NEF network exposure function
  • policy control function policy control function
  • PCF policy control function
  • unified data management unified data management
  • UDM unified database
  • NRF network repository function
  • application function application function, AF
  • AMF access and mobility management function
  • Terminal device it can also be called user equipment (UE), which is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed in On the water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, an industrial control (industrial control ), wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety , wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal device here refers to a 3rd generation partnership project (3rd generation partnership project, 3GPP) terminal.
  • 3rd generation partnership project 3rd generation partnership project
  • the above-mentioned terminal device can establish a connection with the operator network through an interface provided by the operator network (such as N1, etc.), and use services such as data and/or voice provided by the operator network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN, and/or the service provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and the terminal device, and may provide other services such as data and/or voice for the terminal device.
  • the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.
  • Wireless access network radio access network, RAN
  • RAN radio access network
  • the RAN is a sub-network of the operator's network and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal equipment To access the operator's network, the terminal equipment first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • the RAN device in this application is a device that provides a wireless communication function for a terminal device, and the RAN device is also called an access network device.
  • the RAN equipment in this application includes but is not limited to: next-generation base station (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base station g nodeB, gNB
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • baseband unit baseBand
  • the user plane network element may be a user plane function (user plane function, UPF) network element.
  • UPF user plane function
  • the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
  • Multicast/broadcast-user plane function (MB-UPF)
  • MB-UPF is mainly responsible for sending multicast broadcast streams to RAN (or UPF), which can perform packet filtering and distribution of multicast broadcast streams, and realize QoS enhancement and counting/reporting of multicast broadcast services.
  • RAN or UPF
  • MB-UPF and UPF are not strictly distinguished, and (MB-)UPF is used to represent MB-UPF or UPF.
  • Data network used to provide a network for transmitting data.
  • the data network element may be a data network element.
  • the data network element may still be a DN network element, or may have other names, which are not limited in this application.
  • Access and mobility management network elements are mainly used for mobility management and access management, etc., and can be used to implement other functions in MME functions except session management, such as lawful interception and access authorization/authentication.
  • the access and mobility management network element may be an access and mobility management function (access and mobility management function, AMF).
  • AMF access and mobility management function
  • the access and mobility management device may still be an AMF, or may have other names, which are not limited in this application.
  • Session management function (session management function, SMF): mainly used for session management, user equipment network interconnection protocol (internet protocol, IP) address allocation and management, selection of manageable user plane functions, policy control and charging function interface endpoints and downlink data notifications, etc.
  • SMF session management function
  • the session management network element may be a session management function network element.
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • Multicast/broadcast-session management function (MB-SMF)
  • MB-SMF is mainly responsible for multicast broadcast session management and control of multicast broadcast transmission. According to the policy rules of multicast broadcast services provided by PCF or locally configured, MB-UPF and RAN are configured accordingly to complete the transmission of multicast broadcast streams. . In this application, MB-SMF and SMF are not strictly distinguished, and (MB-)SMF is used to represent MB-SMF or SMF.
  • PCF Policy control function
  • the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
  • policy control network element may be a policy control function PCF network element.
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • Application function (Application function, AF): It is used for data routing influenced by applications, wireless access network open function network elements, and interaction with policy frameworks for policy control, etc.
  • the application network element may be an application function network element.
  • the application network element may still be an AF network element, or may have other names, which are not limited in this application.
  • Unified data management used to process UE identification, access authentication, registration and mobility management.
  • the data management network element may be a unified data management network element; in a 4G communication system, the data management network element may be a home subscriber server (HSS) network element.
  • HSS home subscriber server
  • the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
  • Unified data repository It mainly includes the following functions: the access function of contract data, policy data, application data and other types of data.
  • AUSF Authentication server function
  • the authentication server may be an authentication server functional network element.
  • the authentication server functional network element may still be an AUSF network element, or may have other names, which are not limited in this application.
  • Data network is a network located outside the operator's network.
  • the operator's network can access multiple DNs, and multiple services can be deployed on the DN, which can provide data and/or voice for terminal equipment. and other services.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is a company's internal office network.
  • the mobile phone or computer of the company's employees can be a terminal device, and the employee's mobile phone or computer can access information and data resources on the company's internal office network.
  • Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers refer to the meanings defined in the 3GPP standard protocol, and there is no limitation here.
  • FIG. 1 it is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • the introduction of the functions of the network elements can refer to the introduction of the functions of the corresponding network elements in (c) of FIG. 1, and will not be repeated.
  • the main difference between (d) in FIG. 1 and (c) in FIG. 1 is that the interface between network elements in (d) in FIG. 1 is a point-to-point interface rather than a service interface.
  • N7 The interface between PCF and SMF, which is used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.
  • protocol data unit protocol data unit
  • PDU protocol data unit
  • N15 an interface between the PCF and the AMF, used to issue UE policies and access control-related policies.
  • N5 the interface between the AF and the PCF, used for sending application service requests and reporting network events.
  • N4 The interface between SMF and UPF, which is used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules for the user plane, QoS control rules, traffic statistics rules, etc., and reporting of user plane information .
  • N11 The interface between SMF and AMF, used to transfer the PDU session tunnel information between RAN and UPF, the control message sent to UE, the radio resource control information sent to RAN, etc.
  • N2 the interface between the AMF and the RAN, used to transfer radio bearer control information from the core network side to the RAN, etc.
  • N1 The interface between the AMF and the UE, which is irrelevant to access and used to deliver QoS control rules to the UE.
  • N8 The interface between AMF and UDM, which is used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register UE current mobility management related information with UDM.
  • N10 the interface between SMF and UDM, used for SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.
  • N35 interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.
  • N36 interface between PCF and UDR, used for PCF to obtain policy related subscription data and application data related information from UDR.
  • N12 the interface between AMF and AUSF, used for AMF to initiate an authentication process to AUSF, which can carry SUCI as a subscription identifier;
  • N13 the interface between UDM and AUSF, used for AUSF to obtain user authentication vector from UDM to execute the authentication process.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the network device is the access and mobility management network element AMF
  • the base station is the radio access network RAN as an example for description.
  • the mobility management network element, session management network element, policy control network element, application function network element, access network device, and user plane network element in this application can be (c) or (b) of Figure 1, respectively.
  • the AMF, SMF, PCF, AF, RAN, and UPF in the network can also be network elements with the functions of the above-mentioned AMF, SMF, PCF, AF, RAN, and UPF in future communication such as the sixth generation (6G) network, This application is not limited to this.
  • network functional network element entities such as AMF, SMF network element, PCF network element, BSF network element, and UDM network element are all called network function (network function, NF) network elements; or, in another
  • network function network function, NF
  • a collection of network elements such as AMF, SMF, PCF, BSF, and UDM can be called control plane functional network elements.
  • Computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or tape, etc.), optical disks (e.g., compact disc (compact disc, CD), digital versatile disc (digital versatile disc, DVD) etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.).
  • magnetic storage devices e.g., hard disk, floppy disk, or tape, etc.
  • optical disks e.g., compact disc (compact disc, CD), digital versatile disc (digital versatile disc, DVD) etc.
  • smart cards and flash memory devices for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc.
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • FIG. 2 is an exemplary flowchart of a communication method 200 provided by an embodiment of the present application.
  • Method 200 includes:
  • the session management network element acquires the first rule.
  • the session management network element obtains the first rule, where the first rule includes the QoS parameter corresponding to the applied frame type.
  • the session management network element receives the first rule from the policy control network element.
  • the policy control network element receives the application information of the application from the application function network element or the multi-access edge computing platform, and the application information includes the frame type and QoS requirements corresponding to the application. It should be understood that the application information may include multiple different frame types of the application and different QoS requirements corresponding to different frame types.
  • the policy control network element generates a first rule according to the application information of the application, and sends the first rule to the session management network element, where the first rule includes a QoS parameter corresponding to the frame type, wherein the QoS parameter is based on the QoS requirement Sure.
  • the application information of the application may include QoS requirements corresponding to different service flows of the application, and different service flows correspond to different frame types.
  • the policy control network element can determine QoS parameters corresponding to different service flows according to the QoS requirements corresponding to different service flows. That is to say, the first rule may include different QoS parameters corresponding to different frame types of the application, such as 5G QoS indicator (5G QoS identifier, 5QI) and packet delay budget (packet delay budget) corresponding to different frame types. PDB) and other information.
  • 5G QoS indicator 5G QoS identifier, 5QI
  • PDB packet delay budget
  • the session management network element determines the first rule according to local configuration. That is to say, the QoS parameter corresponding to the frame type of the application can be configured for the session management network element in a pre-configuration manner.
  • the first rule here may be, for example, a PCC rule.
  • the session management network element determines the QoS flow identifier QFI corresponding to the frame type according to the QoS parameter.
  • the session management network element sends instruction information #1 to the user plane network element.
  • the user plane network element receives indication information #1 from the session management network element.
  • the session management network element sends indication information #1 to the user plane network element according to the first rule, and the indication information #1 is used to instruct the user plane network element to determine the QoS flow corresponding to the data packet of the application according to the frame type Identify the QFI.
  • the indication information #1 is used to instruct the user plane network element to determine the QFI corresponding to the data packet according to the frame type of the application when receiving the data packet of the application.
  • the application data packet here may refer to a data packet of a certain service flow of the application.
  • the indication information #1 includes the frame type and the QFI corresponding to the frame type.
  • the indication information #1 may be the correspondence between the frame type and the QFI.
  • the indication information #1 may be included in the PDR, and correspondingly, the QFI and the frame type (or the corresponding relationship between the QFI and the frame type) are included in the PDR.
  • the user plane network element after receiving the indication information #1, the user plane network element locally saves the correspondence between the frame type and the QFI.
  • the session management network element sends instruction information #2 to the user plane network element, where the instruction information #2 is used to instruct the user plane network element to send the data packet of the application through the second tunnel, and the tunnel header of the second tunnel includes The QFI; in other words, the indication information #2 instructs the user plane network element to encapsulate the data packet of the application in the second tunnel, and carry the QFI in the tunnel header of the second tunnel.
  • the second tunnel is a tunnel for sending data to the downlink node, for example, the second tunnel is a GTP-U tunnel.
  • the instruction information #2 instructs the user plane network element to send the data packet of the application to the downlink node, for example, to the radio access network device, through the QoS flow identified by the QFI.
  • the indication information #2 may be included in the PDR.
  • the user plane network element receives the first data packet.
  • the user plane network element receives a first data packet from an application function network element or a multi-access edge computing platform or an application server, and the first data packet includes a data packet of the application and a frame type corresponding to the data packet.
  • the data packet of the application is transmitted through the first tunnel, that is, the user plane network element receives the data packet of the application through the first tunnel.
  • the first tunnel here is, for example, the tunnel between the application server and the user plane network element, or the tunnel between the multi-access edge computing platform and the user plane network element, or the tunnel between the application function network element and the user plane network element. Tunnels, the first tunnel here may be called an N6 tunnel in some scenarios.
  • the first data packet includes a tunnel header of the first tunnel, and the tunnel header of the first tunnel includes a frame type corresponding to the service flow.
  • the indication information #1 can be specifically used to instruct the user plane network element to determine the QFI corresponding to the service flow according to the frame type in the tunnel header of the first tunnel, or in other words, the indication information #1 can be specifically used to indicate the user plane network element
  • the QFI corresponding to the service flow is determined according to the frame type carried in the tunnel header in the first data packet.
  • the first tunnel may be established in advance, or may be established only when the service is initiated.
  • the session management network element may instruct the user plane network element to establish the first tunnel, and the first tunnel is used to send the user plane network element Data packets for the application or applications of the application.
  • the session management network element sends instruction information #3 to the user plane network element, where the instruction information #3 is used to instruct the user plane network element to establish the first tunnel.
  • the user plane network element receives the indication information #3, and establishes the first tunnel according to the indication information #3, and then sends the information of the first tunnel to the session management network element, and the session management network element sends the tunnel information to the The policy controls network elements.
  • the information of the first tunnel may include the IP address of the first tunnel and/or the identifier of the first tunnel.
  • the indication information #3 may include the tunnel type, such as a GTP-U tunnel or a GRE tunnel. It should be understood that the session management network element determines that a tunnel needs to be established according to the instruction information #4 received from the PCF, and the session management network element sends the instruction information #3 to the user plane network element to establish the first tunnel. It should be understood that the indication information #4 may be carried in the first rule and sent to the session management network element.
  • the first tunnel may have different granularities.
  • the first tunnel is an application-level tunnel, that is, the first tunnel is not shared by service flows of other applications, or the first tunnel is a device-level tunnel
  • the first tunnel is shared by multiple applications on the multi-access edge computing platform, that is, multiple applications on the multi-access edge computing platform all send data to user plane network elements through the first tunnel.
  • the indication information #1 may also be used to indicate different content.
  • the indication information #1 may be used to instruct the user plane network element to determine the QFI corresponding to the service flow according to the IP header of the applied data packet and the frame type corresponding to the data packet;
  • indication information #1 may be used to instruct a user plane network element to determine the QFI corresponding to the service flow according to the identifier of the first tunnel and the frame type.
  • the device-level tunnel is a device-specific tunnel, and one device-level tunnel may correspond to multiple different applications.
  • the application identification information is carried in the IP header (or Ethernet header) of the data packet of the application, so as to determine the application corresponding to the data packet. It should be understood that in some scenarios, the identification information of the application can further determine the specific business flow in the application, that is, the identification information of the application can be the information identifying the application level or the information identifying the business level. Applications are not limited. Therefore, the indication information #1 indicates that the user plane network element determines the QFI corresponding to the application data packet according to the IP header (or Ethernet header) and the frame type of the application data packet.
  • the indication information #1 indicates that the user plane network element
  • the element determines the application corresponding to the data packet according to the application identification information carried in the IP header (or Ethernet header) of the application data packet, and then further determines the QFI corresponding to the data packet through the frame type corresponding to the data packet; the application level
  • the tunnel is an application-specific tunnel, that is, a different tunnel is created for each different application. Therefore, at this time, it is not necessary to determine the application according to the information carried in the IP header (or Ethernet header), and the identifier of the first tunnel can To determine the application corresponding to the data packet, the identifier of the first tunnel may be included in the tunnel header of the tunnel.
  • the application-level tunnel is used to send all data packets related to an application, different applications are distinguished through the tunnel identifier, and service flows with different QoS requirements in the application are determined through the frame type in the tunnel header.
  • the session management network element determines that the data packet of the application will be sent to the user plane network element through the first tunnel, or that the session management network element determines that the data packet of the application will be sent to the user plane network element through the tunnel. transmission.
  • the session management network element can determine that the data packets of the application will be sent to the user plane network element through the tunnel according to the configuration information; in another case, the session management network element can determine the data packets of the application according to the indication information The packet will be sent to the user plane network element through the first tunnel.
  • the session management network element receives indication information #5 from the policy control network element, where the indication information #5 is used to indicate that the data packet of the application will be sent to the user plane network element through the first tunnel.
  • the policy control network element may carry the instruction information #5 in the first rule and send it to the session management network element.
  • the session management network element may send instruction information #1 to the user plane network element after determining that the data packet of the application will be sent to the user plane network element through the first tunnel.
  • the data packets of the application are not transmitted through the first tunnel, but based on the user plane protocol.
  • the first data packet is an IP packet
  • the first data packet includes an extension header
  • the extension header includes a frame type corresponding to the service flow.
  • the indication information #1 can be specifically used to instruct the user plane network element to determine the QFI corresponding to the service flow according to the frame type in the extension header, or in other words, the indication information #1 can be specifically used to indicate the user plane network element to determine the QFI corresponding to the service flow after receiving The first data packet, and when the first data packet includes the application data packet, determine the QFI corresponding to the service flow according to the frame type carried in the extension header in the first data packet.
  • the extension header here is, for example, an SRV6 extension header, or an IPv6 extension header. It should be understood that in this implementation, the indication information #1 is also used to instruct the user plane network element to determine the QFI corresponding to the data packet of the application according to the IP header of the first data packet. At this time, the IP header of the first data packet uses to distinguish between different applications.
  • the first data packet further includes frame information of the frame corresponding to the data packet of the application, where the frame information may include frame type, indication information #6, frame size information, and QoS requirements of the frame one or more items.
  • Indication information #6 is used to indicate the frame to which the data packet of the application belongs. It should be noted that the indication information #6 may be a frame number, and the frame number may identify the frame to which the data packet of the application belongs, and may also identify the sequence number of the frame and the sequence number of the data packet of the application in the frame; or, The indication information #6 is a frame header identifier and/or a frame tail identifier, and the data packets between the frame header and the frame tail are data packets of the same frame.
  • the indication information #6 is used to indicate whether the data packet of the service flow belongs to the same frame as some other data packet. That is to say, the indication information #6 may explicitly indicate the frame to which the data packet of the application belongs, or implicitly indicate the frame to which the data packet of the application belongs. It should be understood that the above frame information may be included in the above tunnel header, or included in the above extension header.
  • the session management network element may send indication information #7 to the user plane network element, where the indication information #7 is used to instruct the user plane network element to carry the frame information in the tunnel header of the second tunnel, or in other words, The instruction information #7 is used to instruct the user plane network element to send the frame information to the downlink node.
  • the indication information #1, the indication information #2, the indication information #3, and the indication information #7 may be carried in the same message, or may be carried in different messages, that is to say, these indication information may be simultaneously may be sent at the same time or not at the same time, which is not limited in this application.
  • the user plane network element determines the QFI corresponding to the applied data packet according to the frame type.
  • the user plane network element determines the application data packet through the frame type in the tunnel header in the first data packet according to the indication information #1 Corresponding QFI.
  • the user plane network element may determine the QFI corresponding to the data packet according to the IP header of the application data packet and the frame type of the data packet of the service data flow; or, when When the first tunnel is an application-level tunnel, the user plane network element determines the QFI corresponding to the data packet according to the identifier of the first tunnel and the frame type of the data packet of the application.
  • the user plane network element when the user plane network element receives the first data packet, and the frame type corresponding to the service flow is included in the extension header in the first data packet, the user plane network element passes the extended The frame type in the header determines which QFI applies to the packet.
  • the user plane network element sends the data packet of the application through the second tunnel, and carries the QFI corresponding to the data packet of the application in the tunnel header of the second tunnel.
  • the session management network element instructs the user plane network element to determine the QoS flow corresponding to the data packet according to the frame type corresponding to the data packet, so that the data packet can be processed according to the frame type of the data packet. Differentiate processing to improve user experience.
  • FIG. 3 is an exemplary flowchart of a communication method 300 provided by an embodiment of the present application.
  • Method 300 includes:
  • the session management network element sends the characteristic information of the application to the user plane network element.
  • the user plane network element receives the feature information of the application from the session management network element.
  • the feature information of the application is used to determine the frame type corresponding to the data packet of the application, or in other words, the feature information of the application is feature information related to the frame type of the application.
  • the characteristic information of the application includes the frame type of the application, the sending rule of the frame of the application, the burst size of the frame, the interval between the frames of the application, the IP header information of the application, the application identification, the at least one.
  • the frame sending rule of the application may be the sending rule of different types of video frames.
  • the frame sending rule may indicate sending I frames and
  • the rule of the P frame for example, the sending rule may be IPPPIPPP, that is, sending one I frame and then sending three P frames is a cycle.
  • data packets of all applications may use the same IP header information, that is, use the same IP address, port number and protocol number; or, data packets of different frame types of different applications use different IP header information, at this time , the user plane network element can determine the frame type of the data packet according to the IP header information.
  • the session management network element sends instruction information #8 to the user plane network element.
  • the instruction information #8 is used to instruct the user plane network element to determine the frame type corresponding to the data packet of the application according to the characteristic information of the application.
  • the user plane network element receives indication information #8 from the session management network element.
  • the session management network element receives the QoS parameter corresponding to the frame type, and then determines the QoS flow identifier QFI corresponding to the frame type according to the QoS parameter corresponding to the frame type.
  • the session management network element sends indication information #9 to the user plane network element, and the indication information #9 is used to instruct the user plane network element to send the data packet corresponding to the frame type through the QoS flow, or in other words, the indication information #9 is used to instruct the user plane network element to send the data packet corresponding to the frame type through the second tunnel, and the tunnel header of the second tunnel includes the QFI.
  • the session management network element sends indication information #10 to the user plane network element, where the indication information #10 is used to instruct the user plane network element to detect the frame to which the data packet of the application belongs according to the feature information.
  • the indication information #10 can also be used to instruct the user plane network element to detect other frame information of the frame to which the data packet of the application belongs according to the characteristic information, such as the size information of the frame, and the relative position of the data packet in the frame information (e.g. position relative to the frame header), which other packets this packet belongs to in the same frame, etc.
  • indication information #8, indication information #9, and indication information #10 of the application may be carried in the same message or in different messages, which is not limited in this application.
  • the user plane network element determines the frame type corresponding to the data packet of the application according to the characteristic information of the application.
  • the user plane network element can determine according to the burst size of the frame The frame type corresponding to the data packet; or when the characteristic information includes the identification or type of the application, the user plane network element can obtain in advance that the application or the type of application includes I frames and P frames, and the I frame has a higher burst rate than the P frame. (The above information can also be sent to the user plane network element in the feature information), then the user plane network element can determine the frame type corresponding to the data packet according to the burst size of the frame.
  • the user plane network element determines the frame type of the first frame, it can determine the frame type of the next frame, thus, after receiving After subsequent data packets, the user plane network element can determine the frame type corresponding to the data packet only according to the frame interval and frame sending rule.
  • the user plane network element determines the QoS flow corresponding to the frame type according to the frame type.
  • the user plane network element sends the data packet corresponding to the frame type through the QoS flow.
  • the user plane network element sends the data packet corresponding to the frame type through the second tunnel, the data packet is encapsulated in the second data packet, the second data packet includes the tunnel header of the second tunnel, and the second tunnel header Include the frame information corresponding to the data packet and the identifier QFI of the QoS flow.
  • the frame information here may include one or more items of frame type, frame size information, frame QoS requirement, and indication information for indicating the frame to which the data packet of the application belongs.
  • the user plane network element detects the frame to which the data packet of the application belongs according to the characteristic information, and sends the information of the frame to the downlink node, for example, includes the information of the frame in the second tunnel in the tunnel head.
  • the user plane network element can also detect other frame information of the frame to which the data packet of the application belongs through the feature information according to the indication information #10, such as the size information of the frame, the relative position of the data packet in the frame (such as relative at the position of the frame header), the data packet and which other data packets belong to the same frame, etc., and send these information to the downstream node.
  • the data packet can be distinguished and processed according to the frame type of the data packet, and the user experience is improved.
  • FIG. 4 is an exemplary flow chart of a communication method 400 provided by an embodiment of the present application.
  • Method 400 includes:
  • the AS sends a connection establishment request message to the first function.
  • the AS when the AS needs to send application data, the AS sends a connection establishment request message to the first function.
  • the connection establishment request message is used to request the 5G system to allocate resources for the service flow of the application, so that the data of the application can get proper QoS guarantee when it is transmitted through the 5G network.
  • the first function here can be MEP or AF.
  • connection establishment request message may include QoS requirement information corresponding to different frame types of the application.
  • the connection establishment request is used to request the first function to prepare network resources for sending the application data.
  • the AS sends the connection establishment request message by calling a first application programming interface (application programming interface, API) provided by the first function.
  • the parameters of the first API include the frame type of the application and the corresponding QoS requirements.
  • the parameters of the first API may also include IP header information of the data packet of the application, such as IP address, port number, and protocol number.
  • the parameters of the first API may also include the type of application (for example, AR/VR service), whether AF/MEP is required to process the application, characteristics of the application, and the like.
  • the AS may also request the first function to process the service flow of the application.
  • the processing may be, for example, recoding the data of the application, or compressing the data of the application, or various processing
  • the combination of modes is not limited here.
  • the first function sends application information to the PCF/NEF.
  • the first function sends the application information of the application to the PCF, where the application information includes the frame type of the application and the corresponding QoS requirement.
  • the frame corresponding to the enhancement layer service and the frame corresponding to the base layer service have different frame types, or, the I frame and the P frame in the AR/VR service have different frame types.
  • the I frame and the P frame in the AR/VR service have different frame types.
  • the first function performs hierarchical encoding on the received VR video to obtain the base layer service data packet and the enhancement layer service data packet, and then the first function respectively determines the QoS requirements of the base layer frame and the enhancement layer frame, and passes The application information sends the QoS requirements of the base layer frame and the enhancement layer frame to the PCF/NEF.
  • the first function sends device-level tunnel establishment instruction information to the PCF/NEF, and the instruction information is used to establish a connection between the first function and the UPF.
  • the device-level tunnel may be called an N6 tunnel
  • the first function may send a data packet to the UPF through the N6 tunnel, and carry frame information of the data packet through the N6 tunnel.
  • the N6 tunnel header can be between the outer IP header and the inner IP packet, where the inner IP packet can also be called the inner data packet, the inner IP packet includes the inner IP header and the data packet, and the inner IP header is located in the inner layer
  • the initial part of the IP packet is connected with the N6 tunnel head.
  • the inner IP header of the tunnel includes application identification information, which is used to identify the application to which the data packet belongs, so UPF can identify the application according to the inner IP header.
  • the N6 tunnel header may include frame information of the data packet, such as the frame type and frame number of the frame to which the data packet belongs.
  • the N6 tunnel header may also include the tunnel identifier or other fields of the N6 tunnel, which is not limited in this application.
  • the first function may also indicate to the PCF/NEF the type of the device-level tunnel (for example, the GRE tunnel or the GTP-U tunnel), and the specific manner is not limited.
  • the first function may send indication information to the PCF/NEF to indicate that the data packet of the application is to be sent to the UPF through the N6 tunnel.
  • the first function also sends uplink tunnel identification information (such as the IP address of the N6 tunnel on the first function, an optional tunnel ID, etc.) to the PCF/NEF.
  • uplink tunnel identification information such as the IP address of the N6 tunnel on the first function, an optional tunnel ID, etc.
  • the PCF may pre-establish a device-level tunnel through configuration. If the device-level tunnel has been established, S403 may not be executed.
  • the first function sends the identification information of the application to the PCF/NEF.
  • the application identification information is used to identify the application to which the data packet belongs, and the application identification information may be, for example, an application identifier or a quintuple of the application. It should be understood that in some scenarios, the identification information of the application can further determine the specific business flow in the application, that is, the identification information of the application can be the information identifying the application level or the information identifying the business level. Applications are not limited.
  • a device-level tunnel is dedicated to a device, and one device-level tunnel may correspond to multiple different applications. Therefore, when the data packet is transmitted through the device-level tunnel, the first function needs to send the identification information of the application to the PCF/NEF, so as to indicate the application corresponding to the data packet.
  • each piece of information in S402-S404 may be carried in one message, or may be carried in different messages, which is not limited in this application.
  • the AS can also directly interface with the PCF/NEF.
  • the AS can directly send content such as application information to the PCF/NEF, that is, the solution can be executed directly from S402, and the first function needs to be replaced by the AS at this time.
  • the PCF/NEF generates a PCC rule according to the application information.
  • the PCF/NEF sends the PCC rule to the SMF.
  • the PCC rule includes identification information of the application and QoS parameters corresponding to the frame type of the application.
  • the QoS parameters of the application may include QoS parameters of different frame types of the application, for example, information such as 5QI and PDB of different frame types.
  • the PCF may determine the QoS parameter corresponding to the frame type of the application according to the application information (QoS requirement) of the application.
  • the PCC rule also includes instruction information for creating a device-level tunnel, and further, may also include the type of the device-level tunnel (such as a GRE tunnel or a GTP-U tunnel).
  • the PCC rule may also include identification information of the uplink tunnel and the like.
  • the PCC rule may also carry instruction information for sending the data packet of the first application through the N6 tunnel.
  • the SMF establishes a device-level tunnel between the AS and the UPF (or between the MEP and the UPF).
  • the SMF determines the QFI according to the QoS parameter.
  • the SMF acquires the QoS parameter corresponding to the frame type of the first application from the PCC rule, and determines the identifier QFI of the QoS flow corresponding to the frame type according to the QoS parameter.
  • the SMF creates different QoS flows according to QoS parameters corresponding to different frame types in the PCC rule, and determines the QFI corresponding to the frame type of the application.
  • the SMF configures the UPF.
  • the SMF can determine according to the configuration information that the data packet of the application is sent to the UPF through the N6 tunnel, or the SMF can determine the UPF according to the received indication information (for example, the PCC rule carries the indication information of sending the data packet of the application through the N6 tunnel).
  • Application data packets are sent to UPF through the N6 tunnel. It should be understood that in some scenarios, the data packet of the application may refer to a data packet of a service flow in the application.
  • the SMF instructs the UPF to match the identification information corresponding to the application according to the inner IP header of the N6 tunnel, so as to determine the QFI corresponding to the data packet.
  • the SMF sends indication information to the UPF, and the indication information is used to instruct the UPF to identify the application through the inner layer IP header of the N6 tunnel when receiving the data packet of the application through the N6 tunnel.
  • the SMF instructs the UPF to determine the identifier QFI of the QoS flow to which the data packet belongs according to the frame type in the frame information carried by the N6 tunnel header.
  • the SMF may send the corresponding relationship between the frame type of the application and the QFI to the UPF.
  • the UPF receives the correspondence between the frame type and the QFI, it saves the correspondence locally, so that when receiving the data packet of the application through the N6 tunnel, it can determine the frame according to the frame type carried in the tunnel header. Type corresponds to the QFI.
  • S408 and S409 there may be only one piece of indication information, which is used to instruct UPF to determine the application according to the inner layer IP header (or the IP header of the application data packet) and the frame type carried in the tunnel header.
  • the packets correspond to the QFI.
  • the SMF also instructs the UPF to encapsulate the inner layer IP packet into a downlink GTP-U tunnel and send it to the downstream node, and the GTP-U tunnel header includes the QFI corresponding to the QoS flow.
  • the SMF instructs the UPF to send the data packet of the application to the downlink node through the QoS flow identified by the QFI.
  • the SMF may also instruct the UPF to copy the frame information in the N6 tunnel header to the head of the downlink GTP-U, so as to send it to the downlink node (such as the base station), so that the downlink node performs the data packet according to the frame information scheduling.
  • the frame information may include one or more of frame type, frame size information, frame QoS requirement, and indication information for indicating the frame to which the data packet of the application belongs.
  • each piece of information in S409-S412 may be carried in the same message or in different messages, which is not limited in this application.
  • the SMF configures the RAN.
  • RAN exemplary:
  • the SMF sends a QoS flow modification request message to the RAN, where the QoS flow modification request message includes QoS configuration information of multiple QoS flows corresponding to the first application.
  • the SMF sends a response message to the first function.
  • the SMF sends a response message to the first function through the PCF/NEF.
  • the response message includes information about the N6 tunnel, such as the IP address and tunnel identifier of the N6 tunnel.
  • the first function sends a connection establishment response message to the AS.
  • the first function sends a connection establishment response message to the AS, where the connection establishment response message is used to respond to the connection establishment request message sent by the AS.
  • the AF/MEP sends the tunnel information (that is, the identifier of the N6 tunnel) to the AS.
  • the response message may be a response of the first API.
  • the AS sends the data packet of the application.
  • the AS sends the data packet of the application through the first function.
  • the AS sends the data packet of the application to the first function
  • the first function sends the data packet of the application to the UPF through the tunnel.
  • the AS sends the data packet of the application to the first function
  • it also sends the frame information corresponding to the data packet
  • the first function carries the frame information in the tunnel header and sends it to the UPF.
  • the AS may call the second API provided by the first function to send the data packet of the application.
  • the parameter of the second API may include a data packet of the application.
  • the parameters of the second API may also include frame information corresponding to the data packets of the application.
  • the first function processes, for example, re-encodes, the data packets of the application. At this time, the first function determines the frame information and carries it in the tunnel and sends it to the UPF.
  • the AS When the N6 tunnel is established between the AS and the UPF, the AS carries the frame information in the tunnel header and sends it to the UPF.
  • the AS may also directly request the first function to send the data packet without requesting in advance to establish a connection.
  • the QoS requirement of the frame type corresponding to the data packet is provided when requesting to send the data packet.
  • the parameters of the second API also include QoS requirements.
  • the first function may carry the QoS requirement as frame information in the tunnel header and send it to the UPF, and the UPF copies it into the second tunnel header and sends it to the base station.
  • the UPF when the UPF is to receive a data packet of an application through the N6 tunnel, the UPF is configured to determine the corresponding QoS flow, so that the data packets can be distinguished and processed according to the frame type of the data packet, which improves the user experience, and avoids the fact that the network cannot identify the frame type of the media data, and cannot distinguish between different types of data packets, resulting in some cases , For example, in the case of network congestion, a smooth user experience cannot be guaranteed.
  • AR/VR service scenarios such services will generate large bandwidth burst data, which will cause a relatively large impact on the network.
  • the base station may not be able to process all the data packets at that moment, resulting in a degradation of user experience. Therefore, video data of different frame types can be processed differently to ensure basic user experience.
  • AR/VR video is processed in a layered coding manner, that is, the video stream is layered into enhancement layer data packets and base layer data packets.
  • the terminal When the terminal only receives the base layer data packets and does not receive any enhancement layer data packets, the user can still watch the video, but the video definition decreases; when both the enhancement layer data packets and the base layer data packets arrive at the terminal device, Users can watch videos in higher definition.
  • the layered coded base layer packets and enhancement layer packets belong to different frame types, and their importance is different. In order to ensure a smooth user experience, in some cases, such as when the network is congested, the system should give priority to ensuring that the base layer data packets are sent to the terminal, and even if the enhancement layer data packets are properly lost, the user experience will not be affected too much.
  • the frame types of AR/VR video data packets include I frames and P frames, where I frames are reference frames, P frames are data frames, and P frames need to rely on I frames for decoding. Therefore, the loss of I frames It will cause subsequent P frames to be undecodeable, and discarding a P frame only affects the picture of one frame. Therefore, using the communication method provided by the embodiment of the present application, different processing priorities can be used for the data packets of the I frame and the P frame, so that the data packets of the I frame can be guaranteed first when the network is congested, thereby avoiding watching AR/VR video
  • the burst data of multiple users causes system congestion and affects user experience.
  • FIG. 6 is an exemplary flowchart of a communication method 600 provided by an embodiment of the present application.
  • Method 600 includes:
  • the AS sends a connection establishment request message to the first function.
  • the first function sends application information to the PCF.
  • S601-S602 are similar to S401-S402 in method 400, and will not be repeated in this application.
  • the first function sends application-level tunnel establishment indication information to the PCF/NEF, where the indication information is used to establish an application-level tunnel between the first function and the UPF.
  • the application-level tunnel can be called a kind of N6 tunnel, and the AS can send a data packet to the UPF through the N6 tunnel, and carry frame information of the data packet through the N6 tunnel.
  • the PCF/NEF generates a PCC rule according to the application information.
  • the PCF/NEF sends the PCC rule to the SMF.
  • the PCC rule includes instruction information for creating an application-level tunnel.
  • the type of the application-level tunnel eg, GRE tunnel or GTP-U tunnel
  • GRE tunnel e.g, GRE tunnel or GTP-U tunnel
  • the PCC rule may also include identification information of the uplink tunnel, etc.
  • the PCC rule may also carry indication information for sending application data packets through the N6 tunnel.
  • the application-level tunnel is application-specific, that is, the application-level tunnel corresponds to only one service, and different applications can be distinguished according to the tunnel. Therefore, when the first function indicates that the N6 tunnel established by the PCF/NEF is an application-level tunnel, the first function does not need to send application identification information to the PCF/NEF.
  • the SMF establishes an N6 tunnel.
  • the SMF establishes the application-level tunnel between the first function and the UPF according to the instruction information of creating the application-level tunnel in the PCC rule.
  • the SMF acquires N6 tunnel information (including IP address and logical tunnel identifier) for the application. For example, the SMF obtains the information of the N6 tunnel from the UPF.
  • N6 tunnel information including IP address and logical tunnel identifier
  • the application-level tunnel is application-specific, so the UPF can determine the application to which the data packet belongs according to the tunnel information of the N6 tunnel.
  • the SMF determines the QFI corresponding to the frame type according to the QoS parameter corresponding to the applied frame type.
  • S607 is similar to S408 in the method 400, for the sake of brevity, the description will not be repeated.
  • the UPF is configured.
  • the SMF can determine according to the configuration information that the data packet of the application is sent to the UPF through the N6 tunnel, or the SMF can determine the data packet of the application according to the received indication information (such as the indication information in the PCC rule that carries the data packet of the application through the N6 tunnel).
  • the packet is sent to UPF through the N6 tunnel.
  • the SMF instructs the UPF to determine the QoS flow corresponding to the data packet according to the tunnel information and the frame information (eg frame type) in the tunnel header.
  • the frame information eg frame type
  • the SMF sends indication information to the UPF, and the indication information is used to instruct the UPF to determine the application to which the data packet belongs according to the tunnel information of the N6 tunnel when receiving the data packet of the application through the N6 tunnel, and according to the information carried in the N6 tunnel header
  • the frame type determines the QoS flow to which the data packet belongs (that is, determines the QFI corresponding to the QoS flow).
  • the SMF may also instruct the UPF to copy the frame information of the N6 tunnel header to the header of the downlink GTP-U, so as to send it to the downlink node (such as the base station), so that the downlink node can compare the data packet according to the frame number to schedule.
  • the SMF can also instruct the UPF to copy other information in the frame information to the header of the GTP-U, which is not limited in this application.
  • the SMF also instructs the UPF to encapsulate the inner layer IP packet into a downlink GTP-U tunnel and send it to the downstream node, and the GTP-U tunnel header includes the QFI corresponding to the QoS flow.
  • S611-S613 are similar to S412-S415 in the method 400, and for the sake of brevity, the description will not be repeated.
  • the UPF when the UPF is to receive a data packet of an application through the N6 tunnel, the UPF is configured to determine the QoS flow corresponding to the data packet according to the tunnel information of the N6 tunnel and the frame type carried by the tunnel header, so that Differentiate processing of data packets of different frame types to improve user experience.
  • FIG. 7 is a schematic flowchart of a method 700 provided by an embodiment of the present application. It should be understood that the method 700 may be combined with the method 400 or the method 600, that is, the method 700 may be performed after the method 400 or the method 600, or may be performed separately. Method 700 includes:
  • the AS sends data packets through the N6 tunnel.
  • the AS encapsulates the original data packet in the N6 tunnel, and carries the frame information of the data packet at the head of the N6 tunnel, such as the frame type and frame number corresponding to the data packet.
  • the AS directly sends the data packet and the media information corresponding to the data packet to the UPF through the N6 tunnel.
  • the AS when the N6 tunnel is between the first function and the UPF (denoted as case 2), then at S702, the AS first sends the data packet and frame information to the first function, and the first function S703. Send the data packet to the UPF through the N6 tunnel.
  • the first function receives the data packet and the frame information corresponding to the data packet from the AS, encapsulates the data packet in the N6 tunnel, and carries the frame information corresponding to the data packet at the head of the N6 tunnel, for example, the frame information corresponding to the data packet Type, frame number and other information.
  • the AS sends the data packet and the frame information corresponding to the data packet to the UPF through the N6 tunnel.
  • the first function may also process the data packet sent by the AS at the application layer, for example, re-encode the data packet.
  • the first function encapsulates the processed data packet in the N6 tunnel, and carries the frame information corresponding to the processed data packet in the header of the N6 tunnel.
  • the UPF determines the QoS flow corresponding to the data packet.
  • the UPF determines the QFI according to the identification information of the application and the frame type.
  • the UPF receives the data packet sent by the first function/AS through the N6 tunnel, obtains application identification information through the inner IP header of the N6 tunnel, and determines the application corresponding to the data packet according to the application identification information.
  • the UPF obtains the frame type corresponding to the data packet at the header of the N6 tunnel, and determines the QoS flow identifier QFI corresponding to the data packet according to the frame type and application identification information.
  • the UPF determines the QFI according to the tunnel identifier and the frame type.
  • the UPF receives the data packet sent by the first function/AS through the N6 tunnel, and since the application-level tunnel is service-specific, the UPF can determine the application corresponding to the data packet according to the N6 tunnel information.
  • the UPF obtains the frame type corresponding to the data packet at the head of the N6 tunnel, and determines the QFI corresponding to the data packet according to the frame type and the N6 tunnel information.
  • the UPF sends the data packet of the application to the RAN.
  • the UPF encapsulates the inner layer IP packet in the GTP-U tunnel.
  • the UPF copies the frame information to the head of the GTP-U tunnel.
  • the N6 tunnel header also includes frame information of the frame corresponding to the data packet of the application.
  • UPF copies the frame information in the N6 tunnel header to the GTP-U tunnel header.
  • the UPF sends the data packet of the application to the RAN through the GTP-U tunnel, and the GTP-U tunnel carries the QFI corresponding to the data packet.
  • the RAN schedules the data packets.
  • the RAN receives the data packet from the UPF through the GTP-U tunnel, and determines the QoS parameter of the QoS flow corresponding to the data packet according to the QFI corresponding to the data packet, and then the RAN schedules the data packet according to the QoS parameter.
  • the RAN can perform frame granularity scheduling. For example, when the packet loss rate of a frame exceeds a certain threshold, the RAN may discard subsequent data packets in the frame.
  • the RAN can also perform scheduling according to the QoS parameters corresponding to the frame. For example, the RAN performs scheduling according to the PDB corresponding to the frame, and discards the data packets of the frame whose processing delay in the RAN exceeds the PDB.
  • the UPF when the UPF receives a data packet of an application through the N6 tunnel, the UPF determines the QoS flow corresponding to the data packet according to the tunnel information of the N6 tunnel and the frame type in the media information carried by the tunnel header , and send the data packet to the downstream node through the QoS flow, so that the network side can distinguish the data packet according to the frame type of the data packet, improve user experience, and avoid failure due to the inability of the network to recognize the frame type of the media data Different types of data are processed differently, so that in some cases, such as network congestion or insufficient resources, a smooth user experience cannot be guaranteed.
  • FIG. 8 is a schematic flowchart of a method 800 provided by an embodiment of the present application.
  • Method 800 includes:
  • the first function sends the application identifier and feature information to the SMF.
  • the AS when the AS needs to send application data, the AS sends the application identification and feature information of the application to the first function, and then the first function sends the application identification and frame feature information to the SMF through the PCF/NEF.
  • the frame feature information can include the sending rule of the frame.
  • the sending rule of the frame can be IPPP IPPP IPPP..., where I means an I frame, and P means a P frame, so the sending rule of the frame here is to send the data of an I frame , and then send the data of the P frame three times, and then repeat this sending method.
  • the feature information of the frame may also include the burst size of the frame, for example, the burst size of the I frame and the burst size of the P frame.
  • the feature information of frames may also include the interval between each frame.
  • the feature information of the frame may include the feature of the enhancement layer frame and the feature of the base layer frame, for example, the sending rule of the enhancement layer and the sending rule of the base layer, the frame of the enhancement layer Burst size, frame burst size of the base layer, frame interval of the enhancement layer, frame interval of the base layer, etc.
  • the AS can also directly interface with the PCF/NEF.
  • the AS may directly send the application identification and feature information of the application to the PCF/NEF.
  • the first function sends application information to the PCF/NEF.
  • the AS sends the application information of the application to the PCF/NEF through the first function, and the application information includes the application identifier of the application and the QoS requirement of the application.
  • the first function may indicate the QoS requirements of different frame types.
  • the data packets corresponding to the enhancement layer service and the data packets corresponding to the base layer service correspond to different frame types, or the data packets of the I frame and the P frame in the AR/VR service also correspond to different frame types. the frame type.
  • the frame type As a concrete example:
  • the first function performs hierarchical coding on the received VR video according to the request of the AS to obtain the base layer service data packet and the enhancement layer service data packet, and then the first function respectively determines the QoS of the base layer service data packet and the enhancement layer service data packet requirements, and send the QoS requirements of the base layer service data packets and enhancement layer service data packets to the PCF/NEF through the application information.
  • the PCF/NEF determines the QoS parameter corresponding to the application.
  • the PCF determines QoS parameters corresponding to the frame type of the application according to the application information of the application, and the QoS parameters of the application may include QoS parameters of different frame types of the application.
  • the application information of the application includes the QoS requirement corresponding to the enhancement layer frame and the QoS requirement corresponding to the base layer frame
  • the PCF determines the QoS parameter corresponding to the enhancement layer frame and the QoS parameter corresponding to the base layer frame according to the above information.
  • the PCF/NEF sends the QoS parameters of the first application to the SMF.
  • the AF may send the application identifier, feature information, and QoS requirements to the PCF/NEF together.
  • solution 2 the application identifier, feature information, and QoS requirements to the PCF/NEF together.
  • the first function sends the application identifier of the application, feature information of the application, and application information of the application to the PCF/NEF, where the application information of the application includes the QoS requirement of the application.
  • the PCF/NEF determines the QoS parameter corresponding to the frame type of the application.
  • the specific solution is similar to that of S803 and will not be described again.
  • the PCF/NEF sends the application identifier of the application, the feature information of the application, and the QoS parameters corresponding to the frame type of the application to the SMF.
  • the SMF configures the UPF so that the UPF can determine the frame type of the data packet when receiving the data packet.
  • the following uses S808-S811 to illustrate the SMF configuration UPF scheme:
  • the SMF sends feature information to the UPF. It should be understood that the feature information is used by the UPF to determine the frame type to which the data packet belongs.
  • the SMF instructs the UPF to determine the QFI according to the frame type, that is, to determine the QoS flow corresponding to the data packet.
  • the SMF instructs the UPF to send the data packet to the downstream node through the QoS flow. Specifically, the SMF may instruct the UPF to encapsulate the data packet into the downlink GTP-U after receiving the data packet of the first application.
  • the GTP-U The QFI corresponding to the data packet shall be included in the U packet header. Further, the UPF sends the encapsulated data packet to a downlink node, and the downlink node may be a RAN.
  • the SMF instructs the UPF to detect the frame number.
  • the SMF instructs the UPF to detect the frame number corresponding to the data packet according to the feature information.
  • the SMF establishes a QoS flow.
  • the SMF establishes the QoS flow according to the QoS parameters of the first application. It should be understood that when the QoS parameters received by the SMF are QoS parameters corresponding to different frame types of the application, the SMF creates different QoS flows according to the QoS parameters of each frame type.
  • the SMF configures the RAN.
  • RAN exemplary:
  • the SMF sends a QoS flow modification request message to the RAN.
  • the QoS flow modification request message includes QoS configuration information of multiple QoS flows corresponding to the application.
  • the UPF is configured to determine the frame type of the data packet according to the characteristic information of the application, and instructs the UPF to determine the QoS flow corresponding to the data packet according to the frame type, so that data packets of different frame types can be Perform differentiated processing to improve user experience.
  • Fig. 9 is an exemplary flowchart of a method 900 provided by an embodiment of the present application. It should be understood that the method 900 may be combined with the method 800, that is, the method 900 may be performed after the method 800, or may be performed separately. Method 900 includes:
  • the UPF receives a downlink data packet.
  • the UPF receives the data packet of the first application from the AF/MEP/AS.
  • the UPF determines the frame type corresponding to the data packet.
  • the UPF determines the frame type corresponding to the data packet according to the feature information.
  • the UPF can determine the corresponding data packet according to the burst size of the frame the frame type.
  • the feature information includes the frame interval and frame sending regularity, after the UPF determines the frame type of the first frame, the UPF can determine the frame type of the next frame, thus, after receiving the subsequent After the data packet, UPF can determine the frame type corresponding to the data packet only according to the frame interval and frame sending rule.
  • the UPF pre-saves feature information of the application, and the feature information is associated with the application identifier of the application.
  • the characteristic information of the application sent by the SMF to the UPF is the application identifier.
  • the UPF receives the data packet of the application, the UPF obtains the characteristic information of the application in the local storage according to the identifier of the application, and then according to the characteristic information to determine the frame type to which the packet corresponds.
  • the UPF determines the frame type through the information carried in the data packet.
  • the data packet sent by S901 carries the frame type information of the data packet in the application layer field, and the UPF can obtain the frame type corresponding to the data packet by parsing the data packet.
  • the data of the application is encapsulated in a data packet, which includes an extension header, which carries the frame type of the data packet, and UPF can obtain the frame type corresponding to the data packet from the extension header of the data packet .
  • the extension header here may be, for example, an SRV6 extension header, or an IPv6 extension header.
  • the UPF determines the frame number corresponding to the data packet.
  • the UPF determines the frame number corresponding to the data packet according to the feature information.
  • the UPF determines the first frame, it can determine the next frame according to the frame interval and frame sending rule, and mark all data packets of the next frame with the same frame number.
  • the UPF determines the frame number according to the information carried in the data packet.
  • the data packet sent by S901 carries the frame number information of the data packet, and the UPF can determine the position carried by the frame number according to the type of application, and obtain the corresponding frame number of the data packet by parsing the data packet. frame number.
  • the extension field of the data packet carries frame number information.
  • the UPF determines the QoS flow corresponding to the data packet.
  • the UPF determines the QoS flow corresponding to the data packet (that is, determines the QFI) according to the frame type corresponding to the data packet.
  • the UPF sends the data packet of the first application to the downstream node through the QoS flow.
  • the QoS flow Exemplarily:
  • the UPF encapsulates the data packet into the downlink GTP-U tunnel, and the GTP-U header includes the QFI determined in S904.
  • the UPF copies the frame number and other information to the header of the GTP-U tunnel.
  • the UPF sends the data packet to the RAN through the GTP-U.
  • the RAN schedules the data packets.
  • S908 is similar to S708 in method 700, and the present application will not repeat it here.
  • the UPF determines the frame type corresponding to the data packet according to the characteristic information of the application, or the UPF determines the frame type corresponding to the data packet according to the information carried in the data packet.
  • frame type and determine the QoS flow corresponding to the data packet according to the frame type, and send the data packet to the downstream node through the QoS flow, so that the network side can distinguish the data packet according to the frame type of the data packet, and improve User experience, avoiding that different types of data cannot be distinguished and processed because the network cannot recognize the frame type of media data, resulting in the failure to guarantee a smooth user experience in some cases, such as network congestion or insufficient resources.
  • method 400 and method 700 can be used in combination, or can be used independently.
  • method 800 can be used alone, or can be used in combination as a preparation for the method 900, and so on.
  • the methods and operations implemented by network equipment may also be implemented by components (such as chips or circuits) that can be used in network equipment.
  • Fig. 10 is a schematic block diagram of a communication device 10 provided by an embodiment of the present application.
  • the communication device 10 includes a transceiver unit 11 and a processing unit 12 .
  • the transceiver unit 11 can implement a corresponding communication function, and the processing unit 12 is used for data processing.
  • the transceiver unit 11 may also be called a communication interface or a communication unit.
  • the device 10 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 12 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 12 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .
  • the apparatus 10 can be used to execute actions performed by network devices (such as network elements, specifically, session management network elements, user plane network elements, etc.) in the above method embodiments. At this time, the apparatus 10 can It is a network device or a component that can be configured in the network device.
  • the transceiver unit 11 is used to perform operations related to sending and receiving on the network device side in the above method embodiments, and the processing unit 12 is used to perform processing on the network device side in the above method embodiments. related operations.
  • the apparatus 10 is used to execute the actions executed by the session management network element (or SMF) in the above embodiments.
  • the processing unit 12 is configured to obtain a first rule, the first rule includes a quality of service QoS parameter corresponding to an applied frame type; the transceiver unit 11 is configured to send the user The network element on the plane sends first indication information, and the first indication information is used to instruct the network element on the user plane to determine the identifier QFI of the QoS flow corresponding to the data packet of the application according to the frame type, and the service flow is the application The service flow of the application, the data packet of the application is encapsulated in the first data packet, and the first data packet includes the frame type.
  • the transceiver unit 11 is configured to send application feature information to the user plane network element; the transceiver unit 11 is also configured to send seventh indication information to the user plane network element, and the seventh indication The information is used to instruct the user plane network element to determine the frame type corresponding to the data packet of the application according to the feature information.
  • the feature information includes at least one of the sending regularity of the applied frames, the burst size of the applied frames, and the interval between the applied frames.
  • the device 10 can implement the steps or processes corresponding to the session management network element (or SMF) in the method embodiment according to the embodiment of the present application, and the device 10 can include a session management network element (or SMF) for executing the method embodiment in the method embodiment or SMF) to execute the unit of method. Moreover, each unit in the apparatus 10 and the above-mentioned other operations and/or functions are respectively for realizing the corresponding processes of the method embodiment in the session management network element (or SMF) in the method embodiment.
  • the transceiving unit 11 can be used to perform the transceiving steps in the method 200, such as step S220; the processing unit 12 can be used to perform the processing steps in the method 200, such as step S210 .
  • the transceiver unit 11 can be used to execute steps S310 and S320 in the method 300 .
  • the transceiver unit 11 can be used to execute steps S409-S414 in the method 400; the processing unit 12 can be used to execute the processing steps in the method 400, such as steps S407 and S408.
  • the transceiver unit 11 can be used to execute steps S608-S612 in the method 600; the processing unit 12 can be used to execute the processing steps in the method 600, such as steps S606 and S607.
  • the transceiver unit 11 can be used to execute steps S801, S804, S807-S811, and S813 in the method 800; the processing unit 12 can be used to execute the processing steps in the method 800, such as Step S812.
  • the apparatus 10 is configured to perform the actions performed by the user plane network element (or UPF) in the above method embodiments.
  • the transceiver unit 11 is configured to receive a first data packet, the first data packet includes an application data packet and a frame type corresponding to the application data packet; the processing unit 12 is configured to The frame type determines the identifier QFI of the QoS flow corresponding to the data packet of the application.
  • the transceiving unit 11 is configured to receive feature information of the application; the transceiving unit 11 is further configured to determine a frame type corresponding to a data packet of the application according to the feature information of the application.
  • the characteristic information includes at least one of the sending regularity of the applied frames, the applied burst size, and the interval between the applied frames.
  • the device 10 can implement steps or processes corresponding to the execution of the user plane network element (or UPF) in the method embodiment according to the embodiment of the present application, and the device 10 can include a user plane network element (or UPF) for executing the method embodiment in the method embodiment or a unit of a method performed by UPF). Moreover, each unit in the apparatus 10 and other operations and/or functions mentioned above are respectively for realizing the corresponding procedure of the method embodiment in the user plane network element (or UPF) in the method embodiment.
  • the transceiver unit 11 can be used to execute steps S220 and S230 in the method 200; the processing unit 12 can be used to execute the processing steps in the method 200, such as step S240.
  • the transceiver unit 11 can be used to execute steps S310 and S320 in the method 300; the processing unit 12 can be used to execute the processing steps in the method 300, such as step S330.
  • the transceiver unit 11 can be used to execute steps S409-S412 in the method 400.
  • the transceiver unit 11 can be used to execute steps S608-S610 in the method 600.
  • the transceiver unit 11 can be used to execute steps S701, S703, and S707 in the method 700; the processing unit 12 can be used to execute the processing steps in the method 700, such as steps S703-S706 .
  • the transceiver unit 11 can be used to execute steps S807-S811 in the method 800.
  • the transceiver unit 11 can be used to execute steps S901 and S907 in the method 900; the processing unit 12 can be used to execute the processing steps in the method 900, such as steps S902-S906.
  • the apparatus 10 is configured to execute the actions executed by the policy control network element (or PCF) in the above method embodiments.
  • the transceiver unit 11 is configured to receive application information, and the application information includes the frame type of the application; the transceiver unit 11 is also configured to send the frame type correspondence to the session management network element.
  • the quality of service QoS parameter is configured to send the frame type correspondence to the session management network element.
  • the device 10 can implement the steps or processes corresponding to the execution of the policy control network element (or PCF) in the method embodiment according to the embodiment of the present application, and the device 10 can include the policy control network element (or PCF) for executing the method embodiment in the method embodiment or the unit of the method performed by the PCF). Moreover, each unit in the apparatus 10 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the policy control network element (or PCF) in the method embodiment.
  • the transceiver unit 11 can be used to execute steps S402-S404, S406 in the method 400; the processing unit 12 can be used to execute the processing steps in the method 400, such as S405.
  • the transceiver unit 11 can be used to execute steps S602 and S603 in the method 600; the processing unit 12 can be used to execute the processing steps in the method 600, such as S604.
  • the transceiver unit 11 can be used to execute steps S801, S802, and S805 in the method 800; the processing unit 12 can be used to execute the processing steps in the method 800, such as S803 or S806.
  • the processing unit 12 in the above embodiments may be implemented by at least one processor or processor-related circuits.
  • the transceiver unit 11 may be implemented by a transceiver or a transceiver-related circuit.
  • the storage unit can be realized by at least one memory.
  • the embodiment of the present application also provides a device 20 .
  • the device 20 includes a processor 21, the processor 21 is coupled with a memory 22, the memory 22 is used to store computer programs or instructions and/or data, and the processor 21 is used to execute the computer programs or instructions and/or data stored in the memory 22, so that The methods in the above method embodiments are performed.
  • the device 20 includes one or more processors 21 .
  • the device 20 may further include a memory 22 .
  • the device 20 may include one or more memories 22 .
  • the memory 22 can be integrated with the processor 21, or set separately.
  • the device 20 may further include a transceiver 23 for receiving and/or sending signals.
  • the processor 21 is used to control the transceiver 23 to receive and/or send signals.
  • the apparatus 20 is used to implement the operations performed by the network equipment (such as the above-mentioned network elements) in the above method embodiments.
  • the embodiment of the present application also provides an apparatus 30, and the apparatus 30 may be a network device or a chip.
  • the apparatus 30 may be used to execute the operations performed by the network equipment (such as the above-mentioned network elements) in the foregoing method embodiments.
  • Fig. 12 shows a simplified structural schematic diagram.
  • the device 30 includes 31 parts and 32 parts.
  • Part 31 is mainly used for transmitting and receiving radio frequency signals and conversion between radio frequency signals and baseband signals;
  • part 32 is mainly used for baseband processing and controlling base stations.
  • Section 31 may generally be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver.
  • the part 32 is generally the control center of the base station, which can generally be referred to as a processing unit, and is used to control the base station to perform processing operations on the receiving end device side in the above method embodiments.
  • the transceiver unit in part 31 may also be referred to as a transceiver or a transceiver, etc., which includes an antenna and a radio frequency circuit, wherein the radio frequency circuit is mainly used for radio frequency processing.
  • the device used to realize the receiving function in part 31 can be regarded as a receiving unit
  • the device used to realize the sending function can be regarded as a sending unit, that is, part 31 includes a receiving unit and a sending unit.
  • the receiving unit may also be called a receiver, receiver, or receiving circuit, etc.
  • the sending unit may be called a transmitter, transmitter, or transmitting circuit, etc.
  • Section 32 may include one or more single boards, and each single board may include one or more processors and one or more memories.
  • the processor is used to read and execute programs in the memory to realize baseband processing functions and control the base station. If there are multiple single boards, each single board can be interconnected to enhance the processing capability. As an optional implementation, it is also possible that multiple single boards share one or more processors, or that multiple single boards share one or more memories, or that multiple single boards share one or more processors at the same time. device.
  • FIG. 12 is only an example rather than a limitation, and the foregoing network device including a transceiver unit and a processing unit may not depend on the structure shown in FIG. 12 .
  • the chip When the device 30 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the device 30 may also be a chip system or a processing system, so that the device installed with the device 30 can implement the methods and functions of the embodiments of the present application.
  • the processing unit 32 can be a processing circuit in a chip system or a processing system, which realizes the control of the device installed with the chip system or processing system, and can also be coupled to the link storage unit to call the instructions in the storage unit, so that the device can realize
  • the transceiver unit 31 can be an input and output circuit in a chip system or a processing system, outputting information processed by the chip system, or inputting data or signaling information to be processed into the chip system for processing .
  • the embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the network device (such as each network element) in the above method embodiment are stored.
  • the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product including instructions, and when the instructions are executed by a computer, the computer implements the method performed by the network device (such as each network element) in the above method embodiments.
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM random access memory
  • RAM can be used as an external cache.
  • RAM may include 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 connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • 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 devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) etc.
  • the aforementioned available medium may include But not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种通信方法、装置和系统。该方法可以包括：会话管理网元获取第一规则，该第一规则包括应用的帧类型所对应的服务质量QoS参数；该会话管理网元根据该第一规则向用户面网元发送第一指示信息，该第一指示信息用于指示该用户面网元根据该帧类型确定应用的数据包对应的QoS流的标识QFI，该业务流是该应用的业务流，该应用的数据包封装在第一数据包中，该第一数据包包括该帧类型。这样，可以使得用户面网元根据应用的帧类型确定该应用的数据包对应的QoS流，从而可以根据数据包的帧类型对数据包进行区分处理，以满足不同帧类型的数据包的传输需求。

Description

通信方法、装置和系统
本申请要求于2021年07月13日提交中国专利局、申请号为202110790888.3、申请名称为“通信方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更加具体地，涉及一种通信方法、装置和系统。
背景技术
随着数据网络的快速发展，网络中的流量呈现爆发式增长，网络带宽和数据的传输速度也越来越高，因此数据传输过程可能会出现突发数据，突发数据导致队列瞬时冲高，会对网络造成比较大的冲击。当多个用户的突发数据包同时到达基站时，可能会导致基站在该瞬间无法处理所有数据包，导致用户体验下降。
发明内容
本申请提供了一种通信方法、装置和系统，以期通过对不同类型的数据包进行区分处理，提高用户体验。
第一方面，提供了一种通信方法，该方法包括：会话管理网元获取第一规则，该第一规则包括应用的帧类型所对应的服务质量(quality of service，QoS)参数；该会话管理网元根据该第一规则向用户面网元发送第一指示信息，该第一指示信息用于指示该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识(QoS flow ID，QFI)，该应用的数据包封装在第一数据包中，该第一数据包包括该帧类型。
应理解，这里的第一指示信息例如可以对应于具体实施方式中的指示信息#1。
作为一种具体的实现方式，该第一指示信息包括该帧类型和该帧类型对应的QFI。或者说，该第一指示信息可以是帧类型和该QFI的对应关系。进一步地，该第一指示信息可以包括在包检测规则(packet detection rule，PDR)中，相应地，该QFI和该帧类型包括在PDR中。对应地，用户面网元接收该第一指示信息之后，在本地保存该帧类型和该QFI的对应关系，以便用户面网元从第一数据包获取到该应用对应的帧类型后，可以根据该对应关系确定该帧类型对应的QFI。
基于上述技术方案，通过指示用户面网元根据应用的帧类型确定该应用的数据包对应的QoS流，从而可以根据数据包的帧类型对数据包进行区分处理(或者说可以针对不同类型的帧进行不同的QoS处理)以满足不同帧类型的不同传输需求，进而提升用户体验，避免网络无法对不同类型是数据包进行区分处理，导致在一些情况下，例如网络拥塞的情况下，无法保障流畅的用户体验。
作为一种可能的实现方式，会话管理网元从策略控制网元接收该第一规则。例如，策 略控制网元从应用功能网元或者多接入移动计算平台接收该应用的应用信息，该应用信息包括该应用对应的帧类型以及QoS需求。应理解，该应用信息中包括的可以是该应用的多种不同帧类型以及不同帧类型对应的不同的QoS需求。策略控制网元根据该应用的应用信息生成第一规则，并将该第一规则发送给会话管理网元，该第一规则中包括帧类型对应的QoS参数，其中，该QoS参数根据该QoS需求确定。需要说明的是，该应用的应用信息中可以包括该应用的不同业务流对应的QoS需求，不同的业务流与不同的帧类型对应。策略控制网元可以根据不同业务流对应的QoS需求确定不同业务流对应的QoS参数。
作为另一种可能的实现方式，会话管理网元根据本地配置确定第一规则。也就是说，可以通过预配置的方式为会话管理网元配置该应用的帧类型所对应的QoS参数。
这里的第一规则例如可以是策略和计费控制(policy and charging control，PCC)规则。这里的第一数据包包括该帧类型，也可以说是第一数据包携带了该帧类型，例如，该帧类型携带在第一数据包中的隧道头或者扩展头中。
结合第一方面，在第一方面的某些实现方式中，该应用的数据包通过第一隧道传输，该第一数据包包括该第一隧道的隧道头，该第一隧道的隧道头包括该帧类型；该第一指示信息用于指示该用户面网元根据该帧类型确定该应用的数据包对应的服务质量QoS流的标识QFI，包括：该第一指示信息用于指示该用户面网元根据该第一隧道的隧道头中的帧类型确定该QFI。应理解，这里的应用的数据包可以指的是该应用的某一业务流的数据包。
或者说，用户面网元通过第一隧道，或将通过第一隧道，接收该应用的数据包。这里的第一隧道例如是应用服务器和用户面网元之间的隧道，或者是多接入边缘计算平台和用户面网元之间的隧道，这里的隧道在一些场景中可以称为N6隧道。
该方案通过N6隧道的隧道头携带数据包对应的帧类型，可以在不修改应用层协议的基础上，也能让核心网设备根据帧类型区分数据包所对应的QoS流。
结合第一方面，在第一方面的某些实现方式中，该第一指示信息用于指示该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI，包括：该第一指示信息用于指示该用户面网元根据该应用的数据包的互联网协议(internet protocol，IP)头和该帧类型确定该QFI；或者，该第一指示信息用于指示该用户面网元根据该第一隧道的标识和该帧类型确定该QFI，该第一隧道的标识包括在该第一隧道的隧道头中。
需要说明的是，当该第一隧道为设备级隧道时，即该第一隧道是设备专用的隧道，该第一隧道可能与多个不同的业务流对应，此时该应用的数据包的IP头中携带应用的识别信息，以用于确定数据包所对应的应用。因此，第一指示信息指示用户面网元根据应用的数据包的IP头和帧类型确定该应用的数据包对应的QFI，可以理解为，第一指示信息指示用户面网元根据应用的数据包的IP头中携带的应用的识别信息确定数据包所对应的应用，然后进一步通过该帧类型确定该应用对应的QFI；当该第一隧道为应用级隧道时，即该第一隧道是应用专用的隧道，此时可以不需要在IP头中携带应用的识别信息，通过该第一隧道的标识可以确定数据包所对应的业务流，该第一隧道的标识可以包括在隧道的隧道头中。因此，第一指示信息指示该用户面网元根据该第一隧道的标识和该帧类型确定该QFI。
基于上述方案，可以使得用户面网元对于不同类型的隧道，也能根据帧类型确定应用对应的QFI，从而可以对不同类型的帧进行不同的QoS处理。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该会话管理网元确定 该应用的数据包通过该第一隧道发送给该用户面网元。
通过该方案，在用户面网元将通过隧道接收该应用的数据包的情况下，会话管理网元可以提前指示用户面网元根据隧道头中的帧类型确定该应用的数据包对应的QoS流，因此使得用户面网元通过隧道接收到该应用的数据时便知道该如何处理，能够提升处理的效率。
结合第一方面，在第一方面的某些实现方式中，会话管理网元确定该应用的数据包通过该第一隧道发送给该用户面网元，包括：该会话管理网元接收来自策略控制网元的第二指示信息；该会话管理网元根据该第二指示信息确定该应用的数据包通过该第一隧道发送给该用户面网元；或者，该会话管理网元根据配置信息确定该应用的数据包将通过该第一隧道发送给该用户面网元。
也就是说，会话管理网元在发送第一指示信息之前，确定该应用的数据包将通过隧道发送给用户面网元，或者说会话管理网元确定该应用的数据包将通过隧道进行传输，则进一步地，会话管理网元指示用户面网元根据该第一隧道的隧道头中的帧类型确定该应用的数据包对应的QFI。并且，会话管理网元既可以根据配置信息确定该应用的数据包将通过隧道进行传输，也可以根据来自策略控制网元的指示信息确定该应用的数据包将通过隧道进行传输。策略控制网元可以将该指示信息携带在第一规则中发送给会话管理网元。
结合第一方面，在第一方面的某些实现方式中，该第一数据包包括扩展头，该扩展头包括该帧类型；该第一指示信息用于指示该用户面网元根据该帧类型确定该应用的数据包对应的服务质量QoS流的标识QFI，包括：该第一指示信息用于指示该用户面网元根据该扩展头中的帧类型确定该QFI。
即在另一种可能的实现方式中，该应用的数据包不是通过隧道进行传输的，而是基于用户面协议。此时，第一数据包为IP包，第一数据包包括扩展头，该扩展头包括该业务流对应的帧类型。这里的扩展头例如是SRV6扩展头，或者IPv6扩展头。
基于上述方案，可以使得用户面网元在扩展头中获取应用对应的帧类型，从而可以对不同类型的帧进行不同的QoS处理。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该会话管理网元根据该帧类型对应的QoS参数确定该帧类型对应的该QFI。
通过该方案，会话管理网元可以将该帧类型和该帧类型对应的QFI发送给用户面网元，从而使得用户面网元在第一数据包中获取到应用的帧类型后，可以确定该帧类型对应的QoS流，从而可以对不同类型的帧进行不同的QoS处理。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该会话管理网元向该用户面网元发送第三指示信息，该第三指示信息用于指示该用户面网元通过第二隧道发送该应用的数据包，该第二隧道的隧道头包括该QFI。或者说，该第三指示信息用于指示用户面网元通过该QFI标识的QoS流将该应用的数据包发送给下行节点(例如是无线接入网设备)。该第三指示信息可以包括在PDR中。
该第三指示信息例如可以对应与具体实施方式中的指示信息#2。
应理解，第一指示信息和第三指示信息可以承载于同一消息中，也可以承载于不同消息中。
应理解，该第二隧道是用于将该应用的数据发送给下行节点的隧道，例如，该第二隧道为GTP-U隧道。
通过上述方案，可以通过第二隧道将应用的数据包发送给接入网设备以便接入网设备可以根据数据包的帧类型对数据进行调度。
结合第一方面，在第一方面的某些实现方式中，该第一数据包中还包括该应用的数据包所对应的帧的帧信息，该帧信息包括该帧类型、第四指示信息、该帧的大小信息、该帧的QoS需求信息中的一项或多项，该第四指示信息用于指示该应用的数据包所属的帧；该方法还包括：该会话管理网元向该用户面网元发送第五指示信息，该第五指示信息用于指示该用户面网元在该第二隧道的隧道头中携带该帧信息。
该第四指示信息可以是帧号，该帧号可以标识该应用的数据包所属的帧，也可以标识帧的序号以及该应用的数据包在该帧中的序号；或者，该第四指示信息是帧头标识和帧尾标识，介于帧头和帧尾间的数据包是同一个帧的数据包。或者，该第四指示信息用于指示该应用的数据包是否与某个已知数据包属于同一个帧。
通过上述方案，可以使得网络侧方便地识别数据包所属的帧，以便进行帧粒度的调度。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该会话管理网元向用户面网元发送第六指示信息，该第六指示信息用于指示该用户面网元建立该第一隧道；该会话管理网元从该用户面网元接收该第一隧道的信息。
可选地，在该会话管理网元向用户面网元发送第六指示信息之前，该会话管理网元接收来自策略控制网元的第十一指示信息，该第十一指示信息用于指示建立该第一隧道。
第二方面，提供了一种通信方法，该方法包括：用户面网元接收第一数据包，该第一数据包包括应用的应用的数据包和该应用的数据包对应的帧类型；该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI。
用户面网元可以根据从会话管理网元接收到的指示信息，确定该应用的数据包对应的QFI，这里的指示信息具体可以是该应用的数据包的帧类型和QFI的关联关系。用户面网元可以实现保存该关联关系，在接收到第一数据包之后，从第一数据包获取该业务流的帧类型，并根据本地保存的关联关系和该帧类型确定该应用的数据包对应的QFI。应理解，用户面网元可以是从应用功能网元或者多接入边缘计算平台或者应用服务器接收的第一数据包。
通过上述方案，用户面网元可以根据第一数据包中的帧类型确定应用的数据包对应的QoS流，从而可以对不同类型帧进行不同的QoS处理，以满足不同帧类型的不同传输需求。
结合第二方面，在第二方面的某些实现方式中，该用户面网元接收第一数据包，包括：该用户面网元通过隧道接收该第一数据包，该第一数据包包括该第一隧道的隧道头，该第一隧道的隧道头包括该帧类型；该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI，包括：该用户面网元根据该第一隧道的隧道头中的帧类型确定该应用的数据包对应的该QFI。
在该方案中，通过隧道头携带数据包的帧类型，以便用户面网元可以根据该帧类型确定应用的数据包对应的QFI，从而可以对不同类型的帧进行区分处理。
结合第二方面，在第二方面的某些实现方式中，该用户面网元根据该帧类型确定该业务流的数据包对应的QoS流的标识QFI，包括：该用户面网元根据该应用的数据包的互联网协议IP头和该帧类型确定该数据包对应的QFI；或者，该用户面网元根据该第一隧道的标识和该帧类型确定该应用的数据包对应的QFI，该第一隧道的标识包括在该第一隧道 的隧道头中。
当该第一隧道为设备级隧道时，即该第一隧道是设备专用的隧道，该第一隧道可能与多个不同的应用对应，此时该应用的数据包的IP头中携带应用的识别信息，以用于确定数据包所对应的应用。因此，用户面网元根据应用的数据包的IP头和帧类型确定该应用对应的QFI，可以理解为，用户面网元根据应用的数据包的IP头中携带的应用的识别信息确定数据包所对应的应用，然后进一步通过该应用对应的帧类型确定该应用对应的QFI；当该第一隧道为应用级隧道时，即该第一隧道是应用专用的隧道，此时可以不需要在IP头中携带应用的识别信息，通过该第一隧道的标识可以确定数据包所对应的应用，该第一隧道的标识可以包括在隧道的隧道头中。因此，该用户面网元根据该第一隧道的标识和该帧类型确定该QFI。
基于上述方案，可以使得用户面网元对于不同类型的隧道，也能根据帧类型确定应用对应的QFI，从而可以对不同类型的帧进行不同的QoS处理。
结合第二方面，在第二方面的某些实现方式中，该帧类型包括在该第一数据包的扩展头中，该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI，包括：该用户面网元根据该扩展头中的帧类型确定该应用的数据包对应的QFI。
基于上述方案，用户面网元可以在扩展头中获取应用对应的帧类型，从而可以对不同类型的帧进行不同的QoS处理。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元通过第二隧道发送该应用的数据包，该第二隧道的隧道头包括该QFI。
通过上述方案，可以通过第二隧道将应用的数据包发送给接入网设备以便接入网设备可以根据数据包的帧类型对数据进行调度。
结合第二方面，在第二方面的某些实现方式中，该第一数据包还包括该应用的数据包所对应的帧的帧信息，该帧信息包括该帧类型、第四指示信息、该帧的大小信息、该帧的QoS需求信息中的一项或多项，该第四指示信息用于指示该应用的数据包所属的帧，该第二隧道的隧道头中包括该帧信息。
通过上述方案，可以使得网络侧方便地识别数据包所属的帧，以便进行帧粒度的调度。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元接收第一指示信息，该第一指示信息用于指示该用户面网元根据该第一隧道的隧道头中的帧类型或根据该扩展头中的帧类型确定该QFI。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元接收第三指示信息，该第三指示信息用于指示该用户面网元通过该第二隧道发送该应用的数据包，该第二隧道的隧道头包括该QFI。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元接收第五指示信息，该第五指示信息用于指示该用户面网元在该第二隧道的隧道头中携带该帧信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该用户面网元接收来自会话管理网元的第六指示信息；该用户面网元根据该第六指示信息建立该第一隧道。
第三方面，提供了一种通信方法，该方法包括：策略控制网元接收应用的信息，该应用的信息包括该应用的数据包对应的帧类型；该策略控制网元向会话管理网元发送该帧类型对应的服务质量QoS参数。
结合第三方面，在第三方面的某些实现方式中，该第一应用的信息指示创建第一隧道，该第一隧道用于向用户面网元发送该应用的数据包；该方法还包括：该策略控制网元向会话管理网元发送第十一指示信息，该第十一指示信息用于指示该会话管理网元建立该第一隧道。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该策略控制网元接收来自该会话管理网元的该第一隧道的信息；该策略控制网元向该第一应用对应的应用功能网元发送该第一隧道的信息。
结合第三方面，在第三方面的某些实现方式中，该第一隧道为该第一应用或该第一业务流对应的隧道。
结合第三方面，在第三方面的某些实现方式中，该第一应用的信息还用于指示该第一业务流或该第一应用的数据包通过该第一隧道发送给用户面网元；该策略控制网元向该会话管理网元发送第五指示信息，该第五指示信息用于指示该应用的数据包通过该第一隧道发送给该用户面网元。
结合第三方面，在第三方面的某些实现方式中，该第一应用的信息还用于指示将该第一应用的数据包所对应的帧的帧信息发送给接入网设备，该帧信息包括该帧类型、第三指示信息、该帧的大小信息、该帧的QoS需求信息中的一项或多项，该第三指示信息用于指示该应用的数据包所属的帧；该策略控制网元向该会话管理网元发送第七指示信息，该第七指示信息用于指示将该帧信息发送给该接入网设备。
结合第三方面，在第三方面的某些实现方式中，该策略控制网元向会话管理网元发送该帧类型对应的QoS参数，包括：该策略控制网元根据该第一应用的信息确定第一规则，该第一规则包括该帧类型对应的QoS参数；该策略控制网元向该会话管理网元发送该第一规则。
第四方面，提供了一种通信方法，该方法包括：会话管理网元从应用功能网元接收应用的特征信息；会话管理网元向用户面网元发送应用的特征信息和第七指示信息，该第七指示信息用于指示该用户面网元根据该特征信息确定该应用的数据包对应的帧类型。
该特征信息用于确定数据包对应的帧类型，因此，这里的特征信息与帧相关。
应理解，该应用的特征信息和该第七指示信息可以承载于相同的消息中，也可以承载于不同的消息中。也就是说，会话管理网元可以同时向用户面网元发送应用的特征信息和第七指示信息，也可以在两条连续的消息中向用户面网元发送应用的特征信息和第七指示信息，或者，还可以在向用户面网元发送应用的特征信息之后，经过一段时间再发送第七指示信息，例如，会话管理网元根据不同帧类型的QoS参数确定QoS流之后，再向用户面网元发送第七指示信息。
上述技术方法，通过指示用户面网元根据特征信息确定数据包对应的帧类型，可以区分不同数据包对应的帧类型，从而可以对不同类型的帧进行区分处理。
结合第四方面，在第四方面的某些实现方式中，该特征信息包括该应用的帧的发送规律、该应用的帧的突发大小、该应用的帧之间的间隔、该应用的IP头信息、该应用的标识、该应用的类型中的至少一项。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该会话管理网元接收该帧类型对应的QoS参数；该会话管理网元根据该帧类型对应的QoS参数确定该帧类型对应的QoS流；该会话管理网元向该用户面网元发送第八指示信息，该第八指示信息用 于指示该用户面网元通过该QoS流发送该帧类型对应的数据包。
通过上述方案，可以通过第二隧道将应用的数据包发送给接入网设备以便接入网设备可以根据数据包的帧类型对数据进行调度。
结合第四方面，在第四方面的某些实现方式中，该第八指示信息用于指示该用户面网元通过该QoS流发送该帧类型对应的数据包，包括：该第八指示信息用于指示该用户面网元通过第二隧道发送该帧类型对应的数据包，该数据包封装在第二数据包中，该第二数据包还包括该第二隧道的隧道头，该第二隧道的隧道头包括该数据包对应的帧信息和该QoS流的标识QFI，该帧信息包括该帧类型、第九指示信息、该帧的大小信息、该帧的QoS需求信息中的一项或多项，该第九指示信息用于指示该应用的数据包所属的帧。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该会话管理网元向该用户面网元发送第十指示信息，该第十指示信息用于指示该用户面网元根据该特征信息检测该应用的数据包所属的帧。可选的，该第十指示信息还可用于指示用户面网元根据该特征信息检测该应用的数据包所属的帧的其他帧信息，如帧的大小信息、该数据包在该帧中的相对位置信息(例如，相对于帧头的位置)、该数据包与哪些其他数据包属于同一帧等。
结合第四方面，在第四方面的某些实现方式中，其特征在于，该方法还包括：该会话管理网元从应用功能网元接收该应用的特征信息。
第五方面，提供了一种通信方法，该方法包括：用户面网元接收来自会话管理网元的应用的特征信息和第七指示信息；该用户面网元根据该第七指示信息确定该应用的数据包对应的帧类型，该帧类型是根据该应用的特征信息确定的。
结合第五方面，在第五方面的某些实现方式中，该特征信息包括该应用的帧的发送规律、该应用的突发大小、该应用的帧之间的间隔、该应用的IP头信息、该应用的标识、该应用的类型中的至少一项。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：该用户面网元根据该应用的帧类型确定该帧类型对应的QoS流；该用户面网元通过该QoS流发送该帧类型对应的数据包。
结合第五方面，在第五方面的某些实现方式中，该用户面网元通过该QoS流发送该帧类型对应的数据包，包括：该用户面网元通过第二隧道发送该帧类型对应的数据包，该数据包封装在第二数据包中，该第二数据包还包括第二隧道的隧道头，该第二隧道头包括该数据包对应的帧信息和该QoS流的标识QFI，该帧信息包括该帧类型、第九指示信息、该帧的大小信息、该帧的QoS需求信息中的一项或多项，该第九指示信息用于指示该应用的数据包所属的帧。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：该用户面网元根据该特征信息检测该应用的数据包所属的帧；该用户面网元将该帧的信息包括在该第二隧道的隧道头中。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：该用户面网元接收来自该会话管理网元的第七指示信息，该第七指示信息用于指示该用户面网元根据该应用的特征信息确定该应用的数据包对应的帧类型。
第六方面，提供一种通信方法，该方法包括：第一功能接收应用服务器发送的应用数据包；该第一功能获取该数据包对应的帧的信息，该帧的信息包括该帧的类型、第九指示信息、该帧的大小、该帧的QoS需求信息中的一项或多项，该第九指示信息用于指示该 应用的数据包所属的帧；该第一功能向用户面网元发送该应用数据包和该帧信息。
该第一功能例如可以是应用功能或者是多接入边缘计算平台。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第一功能从应用服务器接收第一消息，该第一消息包括该应用数据包和该应用数据包对应的帧信息。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：该第一功能通过隧道向用户面网元发送该应用数据包和该帧信息，其中，该帧信息包括在隧道头部。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第一功能根据应用数据包对应的帧的帧类型或帧的QoS需求信息确定隧道标识，上述隧道头部包括该第一隧道标识。
结合第六方面，在第六方面的某些实现方式中，第一功能向用户面网元发送第三数据包，第三数据包包括该应用数据包和扩展头，其中，扩展头包括帧信息。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第一功能提供第一API，该第一API用于应用服务器请求第一功能为发送该应用的数据准备无线资源，该第一API的参数包括该应用的帧类型及该帧类型对应的QoS需求信息。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第一功能将该应用的帧类型及该帧类型对应的QoS需求信息发送给核心网网元，以便为该应用准备无线资源。
结合第六方面，在第六方面的某些实现方式中，该方法还包括，第一功能将所述第一隧道对应的上行隧道标识发送给核心网网元，并接收来自用户面网元的下行隧道信息。
第一网元根据在接收到应用服务器通过第一API发送的帧类型和QoS需求信息，第一网元根据帧类型或QoS需求信息确定该帧类型所对应的隧道标识。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第一功能提供第二API，该第二API用于应用服务器请求第一功能发送应用数据包，应用服务器通过该API发送应用数据包和该应用数据包对应的帧的信息。
结合第六方面，在第六方面的某些实现方式中，上述第一消息是该第二API对应的请求消息。
第七方面，提供一种通信方法，该方法包括：应用服务器调用第一功能的第一API将应用的帧类型及该帧类型对应的QoS需求信息发送给第一功能，用于请求第一功能为发送该应用的数据准备无线资源；应用服务器调用第一功能的第二API发送应用数据包，用于第一功能根据该数据包对应的帧的帧类型发送该应用数据包；
结合第七方面，，在第七方面的某些实现方式中，该第二API还包括帧信息，帧的信息包括帧类型、第九指示信息、该帧的大小中的一项或多项，该第九指示信息用于指示该应用的数据包所属的帧。
第八方面，提供一种通信装置，该装置用于执行上述第一方面至第八方面提供的方法。具体地，该装置可以包括用于执行第一方面至第八方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为网络设备。当该装置为网络设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是处理器。
在另一种实现方式中，该装置为用于网络设备中的芯片、芯片系统或电路。当该装置为用于通信设备中的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可 以是处理器、处理电路或逻辑电路等。
一种可能情况，该装置为会话管理网元或会话管理网元中的芯片、芯片系统或电路。在该情况下，该装置可以包括用于执行第一方面、第四方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一种可能情况，该装置为用户面网元或用户面网元中的芯片、芯片系统或电路。在该情况下，该装置可以包括用于执行第二方面、第五方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一种可能情况，该装置为策略控制网元网元或策略控制网元中的芯片、芯片系统或电路。在该情况下，该装置可以包括用于执行第三方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
可选地，上述收发器可以为收发电路。可选地，上述输入/输出接口可以为输入/输出电路。
第九方面，提供一种通信装置，该装置包括：存储器，用于存储程序；处理器，用于执行存储器存储的程序，当存储器存储的程序被执行时，处理器用于执行上述第一方面至第八方面提供的方法。
在一种实现方式中，该装置为网络设备(如上述各个网元)。
在另一种实现方式中，该装置为用于网络设备(如上述各个网元)中的芯片、芯片系统或电路。
第十方面，本申请提供一种处理器，用于执行上述各方面提供的方法。在执行这些方法的过程中，上述方法中有关发送上述信息和获取/接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器获取/接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的接收请求消息可以理解为处理器接收输入的信息。
对于处理器所涉及的发射、发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第十一方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第五方面提供的方法。
第十二方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第五方面提供的方法。
第十三方面，提供一种芯片，所述芯片包括处理器与通信接口，所述处理器通过所述通信接口读取存储器上存储的指令，执行上述第一方面至第五方面提供的方法。
可选地，作为一种实现方式，所述芯片还可以包括存储器，所述存储器中存储有指令，所述处理器用于执行所述存储器上存储的指令，当所述指令被执行时，所述处理器用于执行上述第一方面至第五方面提供的方法。
第十四方面，提供一种通信系统，包括会话管理网元和用户面网元。所述会话管理网元，用于获取第一规则，所述第一规则包括应用的帧类型所对应的服务质量QoS参数；根据所述第一规则向用户面网元发送第一指示信息，所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，所述应用的数据包封装在第一数据包中，所述第一数据包包括所述帧类型；所述用户面网元，用于接收所述第一指示信息。
第十五方面，提供一种通信系统，包括会话管理网元和用户面网元。所述会话管理网元，用于向所述用户面网元发送应用的特征信息；向用户面网元发送第七指示信息，所述第七指示信息用于指示所述用户面网元根据所述特征信息确定所述应用的数据包对应的帧类型；所述用户面网元，用于根据所述应用的特征信息确定所述应用的的数据包对应的帧类型。
附图说明
图1示出了适用于本申请实施例的网络架构的一示意图。
图2是本申请一实施例提供的一种通信方法200的示意图。
图3是本申请另一实施例提供的一种通信方法300的示意图。
图4是根据本申请一实施例提供的一种通信方法400的示意图。
图5是通过N6隧道进行数据传输时的一种数据结构图。
图6是适用于本申请一实施例的通信方法的又一示意性流程图。
图7是适用于本申请一实施例的通信方法的又一示意性流程图。
图8是适用于本申请一实施例的通信方法的又一示意性流程图。
图9是适用于本申请一实施例的通信方法的又一示意性流程图。
图10是根据本申请实施例提供的通信装置的示意性框图。
图11是根据本申请实施例提供的通信装置的另一示意性框图。
图12是本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图，对本申请中的技术方案进行描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
为了解决背景技术提到的问题，如图1的(a)所示，本申请提供一种通信系统，该系统包括会话管理网元和用户面网元。该会话管理网元，用于获取第一规则，该第一规则包括应用的帧类型所对应的服务质量QoS参数；根据该第一规则向用户面网元发送第一指示信息，该第一指示信息用于指示该用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI，该应用的数据包封装在第一数据包中，该第一数据包包括该帧类型； 该用户面网元，用于接收该第一指示信息。
可选地，该系统中还包括策略控制网元。该策略控制网元，用于接收该应用的信息，该应用的信息包括该应用对应的帧类型；向该会话管理网元发送该帧类型对应的该QoS参数。
图1的(a)中各网元之间的具体交互可以参照图2中的方法流程，具体方案可见方法200中的说明。
如图1的(b)所示，本申请提供另一种通信系统，该系统包括会话管理网元和用户面网元。该会话管理网元，用于向该用户面网元发送应用的特征信息；向用户面网元发送第七指示信息，该第七指示信息用于指示该用户面网元根据该特征信息确定该应用的数据包对应的帧类型；该用户面网元，用于根据该应用的特征信息确定该应用的的数据包对应的帧类型。
可选地，该系统中还包括应用功能网元。该应用功能网元，用于向该会话管理网元发送该应用的特征信息。
图1的(b)中各网元之间的具体交互可以参照图3中的方法流程，具体方案可见方法300中的说明。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
如图1的(c)所示，为基于服务化架构的第五代(5th generation，5G)网络架构示意图。图1的(a)和图1的(b)中的会话管理网元可以是图1的(c)中的SMF，图1的(a)和图1的(b)中的用户面网元可以是图1的(c)中的UPF，图1的(a)中的策略控制网元可以是图1的(c)中的PCF，图1的(b)中的应用功能网元可以是图1的(c)中的AF。
图1的(c)所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括以下网元中的一个或多个：鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR)、网络存储功能(network repository function，NRF)网元、应用功能(application function，AF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、无线接入网(radioaccess network，RAN)以及用户面功能(user plane function，UPF)网元等。上述运营商网络中，除无线接入网部分之外的部分可以称为核心网络部分。
1、终端设备(terminal device)：也可以成为用户设备(user equipment，UE)，是一种 具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。这里的终端设备，指的是第三代合作伙伴计划(3rd generation partnership project，3GPP)终端。为便于说明，本申请后续以UE代指终端设备为例进行说明。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
2、无线接入网络(radio access network，RAN)网元：在下文中简称为RAN，对应接入网设备。
RAN是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过RAN，进而可通过RAN与运营商网络的业务节点连接。本申请中的RAN设备，是一种为终端设备提供无线通信功能的设备，RAN设备也称为接入网设备。本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(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)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。3、用户面功能(user plane function，UPF)：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、多播/广播用户面功能(multicast/broadcast-user plane function，MB-UPF)
MB-UPF主要负责将多播广播流传送到RAN(或者UPF)，可以进行多播广播流的包过滤、分发，实现多播广播服务的QoS增强以及计数/上报等。本申请中的MB-UPF和UPF不做严格区分，使用(MB-)UPF表示MB-UPF或者UPF。
5、数据网络(data network，DN)：用于提供传输数据的网络。
在5G通信系统中，该数据网络网元可以是数据网络网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
6、接入和移动管理网元
接入和移动管理网元主要用于移动性管理和接入管理等，可以用于实现MME功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信系统中，该接入和移动管理网元可以是接入和移动管理功能(access and mobility management function，AMF)。在未来通信系统中，接入和移动管理设备仍可以是AMF，或者，还可以有其它的名称，本申请不做限定。
7、会话管理功能(session management function，SMF)：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
8、多播/广播会话管理功能(multicast/broadcast-session management function，MB-SMF)
MB-SMF主要负责多播广播会话管理，控制多播广播传输，根据PCF提供或本地配置的多播广播服务是策略规则对MB-UPF和RAN进行相应的配置，以完成多播广播流的传输。本申请中的MB-SMF和SMF不做严格区分，使用(MB-)SMF表示MB-SMF或者SMF。
9、策略控制功能(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF等)提供策略规则信息等。
在4G通信系统中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信系统中，该策略控制网元可以是策略控制功能PCF网元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
10、应用功能(application function，AF)：用于进行应用影响的数据路由，无线接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信系统中，该应用网元可以是应用功能网元。在未来通信系统中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
11、统一数据管理(unified data management，UDM)：用于处理UE标识，接入鉴权，注册以及移动性管理等。
在5G通信系统中，该数据管理网元可以是统一数据管理网元；在4G通信系统中，该数据管理网元可以是归属用户服务器(home subscriber server，HSS)网元在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
12、统一数据存储(unified data repository，UDR)：主要包括以下功能：签约数据、策略数据、应用数据等类型数据的存取功能。
13、认证服务器(authentication server function，AUSF)：用于鉴权服务、产生密钥实现对用户设备的双向鉴权，支持统一的鉴权框架。
在5G通信系统中，该认证服务器可以是认证服务器功能网元。在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
14、数据网络(data network，DN)：DN是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手 机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1的(c)中Nausf、Nnef、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义，在此不做限制。
如图1的(d)所示，为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图1的(c)中对应的网元的功能的介绍，不再赘述。图1的(d)与图1的(c)的主要区别在于：图1的(d)中的各个网元之间的接口是点对点的接口，而不是服务化的接口。
在图1的(d)所示的架构中，各个网元之间的接口名称及功能如下：
1)N7：PCF与SMF之间的接口，用于下发协议数据单元(protocol data unit，PDU)会话粒度以及业务数据流粒度控制策略。
2)N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
3)N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
4)N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5)N11：SMF与AMF之间的接口，用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。
6)N2：AMF与RAN之间的接口，用于传递核心网侧至RAN的无线承载控制信息等。
7)N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
8)N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
9)N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
10)N35：UDM与UDR间的接口，用于UDM从UDR中获取用户签约数据信息。
11)N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
12)N12：AMF和AUSF间的接口，用于AMF向AUSF发起鉴权流程，其中可携带SUCI作为签约标识；
13)N13：UDM与AUSF间的接口，用于AUSF向UDM获取用户鉴权向量，以执行鉴权流程。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。为方便说明，本申请后续，以网络设备为接入和移动管理网元AMF，基站为无线接入网络RAN为例进行说明。
本申请中的移动性管理网元、会话管理网元、策略控制网元、应用功能网元、接入网设备、用户面网元分别可以是图1的(c)或图1的(b)中的AMF、SMF、PCF、AF、RAN、UPF，也可以是未来通信如第六代(6th generation，6G)网络中具有上述AMF、SMF、PCF、AF、RAN、UPF的功能的网元，本申请对此不限定。
应理解，上述应用于本申请实施例的网络架构仅是一种举例说明，适用本申请实施例 的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF、SMF网元、PCF网元、BSF网元以及UDM网元等网络功能网元实体都称为网络功能(network function，NF)网元；或者，在另一些网络架构中，AMF，SMF网元，PCF网元，BSF网元，UDM网元等网元的集合都可以称为控制面功能网元。
本申请实施例的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
图2是本申请实施例提供的通信方法200的示例性流程图。方法200包括：
S210，会话管理网元获取第一规则。
示例性地，会话管理网元获取第一规则，该第一规则中包括应用的帧类型所对应的QoS参数。
作为一种可能的实现方式，会话管理网元从策略控制网元接收该第一规则。例如，策略控制网元从应用功能网元或者多接入边缘计算平台接收该应用的应用信息，该应用信息包括该应用对应的帧类型以及QoS需求。应理解，该应用信息中包括的可以是该应用的多种不同帧类型以及不同帧类型所对应的不同QoS需求。策略控制网元根据该应用的应用信息生成第一规则，并将该第一规则发送给会话管理网元，该第一规则中包括帧类型对应的QoS参数，其中，该QoS参数根据该QoS需求确定。需要说明的是，该应用的应用信息中可以包括该应用的不同业务流对应的QoS需求，不同的业务流与不同的帧类型对应。策略控制网元可以根据不同业务流对应的QoS需求确定不同业务流对应的QoS参数。也就是说，第一规则中可以包括该应用不同帧类型对应的不同的QoS参数，例如不同帧类型对应的5G QoS指示符(5G QoS identifier，5QI)、数据包时延预算(packet delay budget，PDB)等信息。
作为另一种可能的实现方式，会话管理网元根据本地配置确定第一规则。也就是说，可以通过预配置的方式为会话管理网元配置该应用的帧类型所对应的QoS参数。
这里的第一规则例如可以是PCC规则。
可选地，会话管理网元从第一规则中获取到该应用的帧类型所对应的QoS参数之后，根据该QoS参数确定该帧类型所对应的QoS流的标识QFI。
S220，会话管理网元向用户面网元发送指示信息#1。
对应的，用户面网元从会话管理网元接收指示信信息#1。
示例性地，会话管理网元根据第一规则向用户面网元发送指示信息#1，该指示信息#1用于指示用户面网元根据该帧类型确定该应用的数据包对应的QoS流的标识QFI。或者说，该指示信息#1用于指示用户面网元在接收到该应用的数据包时，根据该应用的帧类型确定该数据包对应的QFI。应理解，这里的应用的数据包可以指的是该应用的某一业务流的 数据包。
作为一种具体的实现方式，该指示信息#1包括该帧类型和该帧类型对应的QFI。或者说，该指示信息#1可以是帧类型和该QFI的对应关系。进一步地，该指示信息#1可以包括在PDR中，相应地，该QFI和该帧类型(或者说该QFI和该帧类型的对应关系)包括在PDR中。对应地，用户面网元接收该指示信息#1之后，在本地保存该帧类型和该QFI的对应关系。
可选地，会话管理网元向用户面网元发送指示信息#2，该指示信息#2用于指示用户面网元通过第二隧道发送该应用的数据包，该第二隧道的隧道头包括该QFI；或者说，该指示信息#2指示用户面网元将该应用的数据包封装在第二隧道中，并在第二隧道的隧道头中携带该QFI。该第二隧道是用于将数据发送给下行节点的隧道，例如，该第二隧道为GTP-U隧道。或者说，该指示信息#2指示用户面网元通过该QFI标识的QoS流将该应用的数据包发送给下行节点，例如发送给无线接入网设备。进一步地，该指示信息#2可以包括在PDR中。
S230，用户面网元接收第一数据包。
示例性地，用户面网元从应用功能网元或多接入边缘计算平台或应用服务器接收第一数据包，该第一数据包包括该应用的数据包以及该数据包对应的帧类型。
作为一种可能的实现方式，该应用的数据包通过第一隧道进行传输，即用户面网元通过第一隧道接收该应用的数据包。这里的第一隧道例如是应用服务器和用户面网元之间的隧道，或者是多接入边缘计算平台和用户面网元之间的隧道，或者是应用功能网元和用户面网元间的隧道，这里的第一隧道在一些场景中可以称为N6隧道。此时，第一数据包包括该第一隧道的隧道头，该第一隧道的隧道头中包括该业务流对应的帧类型。此时指示信息#1具体可以用来指示用户面网元根据第一隧道的隧道头中的帧类型确定该业务流对应的QFI，或者说，指示信息#1具体可以用来指示用户面网元在通过第一数据包接收到该应用的数据包时，根据该第一数据包中的隧道头携带的帧类型确定该业务流对应的QFI。
应理解，该第一隧道可以是预先建好的，也可以在业务发起时才建立。可选地，如果该第一隧道没有预先建立(即在业务发起时才建立)，会话管理网元可以指示用户面网元建立该第一隧道，该第一隧道用于向用户面网元发送该应用或该应用的应用的数据包。例如，会话管理网元向用户面网元发送指示信息#3，该指示信息#3用于指示用户面网元建立该第一隧道。对应地，用户面网元接收指示信息#3，并根据指示信息#3建立第一隧道，然后将该第一隧道的信息发送给会话管理网元，由会话管理网元将隧道的信息发生给该策略控制网元。该第一隧道的信息可以包括该第一隧道的IP地址和/或该第一隧道的标识。该指示信息#3可以包括隧道的类型，例如GTP-U隧道或者GRE隧道。应理解，会话管理网元根据从PCF接收的指示信息#4确定需要建立隧道，会话管理网元向用户面网元发送指示信息#3，以便建立第一隧道。应理解，该指示信息#4可以携带在第一规则中发送给会话管理网元。
可选地，该第一隧道可以有不同的粒度，例如，该第一隧道是应用粒度的隧道，即，该第一隧道不被其他应用的业务流共享，或者该第一隧道为设备级隧道，例如，该第一隧道由多接入边缘计算平台上的多个应用共享，即该多接入边缘计算平台上的多个应用均通过该第一隧道将数据发送给用户面网元。
进一步地，对于不同的粒度的隧道，指示信息#1还可以用来指示不同的内容。例如， 当该第一隧道为设备级隧道时，指示信息#1可以用来指示用户面网元根据应用的数据包的IP头和该数据包对应的帧类型确定该业务流对应的QFI；又例如，当该第一隧道为应用级隧道时，指示信息#1可以用来指示用户面网元根据该第一隧道的标识和该帧类型确定该业务流对应的QFI。
还需要说明的是，设备级隧道是设备专用的隧道，一个设备级隧道可以与多个不同的应用对应。该应用的数据包的IP头(或以太网头)中携带应用的识别信息，以用于确定数据包所对应的应用。应理解，在一些场景中，该应用的识别信息还可以进一步确定该应用中的具体业务流，即应用的识别信息既可以是识别到应用层面的信息，也可以识别到业务层面的信息，本申请不作限定。因此，指示信息#1指示用户面网元根据应用的数据包的IP头(或以太网头)和帧类型确定该应用的数据包对应的QFI，可以理解为，指示信息#1指示用户面网元根据应用的数据包的IP头(或以太网头)中携带的应用的识别信息确定数据包所对应的应用，然后进一步通过该数据包对应的帧类型确定该数据包对应的QFI；应用级隧道是应用专用的隧道，即为每个不同的应用创建不同的隧道，因此，此时可以不需要根据IP头(或以太网头)中携带的信息确定应用，通过该第一隧道的标识可以确定数据包所对应的应用，该第一隧道的标识可以包括在隧道的隧道头中。应用级的隧道用于发送一个应用相关的所有数据包，通过隧道标识区分不同的应用，并通过隧道头中的帧类型确定该应用中具有不同QoS需求的业务流。
可选地，在发送指示信息#1之前，会话管理网元确定该应用的数据包将通过第一隧道发送给用户面网元，或者说会话管理网元确定该应用的数据包将通过隧道进行传输。在一种情况下，会话管理网元可以根据配置信息确定该应用的数据包将通过隧道发送给用户面网元；在另一种情况下，会话管理网元可以根据指示信息确定该应用的数据包将通过第一隧道发送给用户面网元。例如，会话管理网元从策略控制网元接收指示信息#5，该指示信息#5用于指示该应用的数据包将通过第一隧道发送给用户面网元。策略控制网元可以将该指示信息#5携带在第一规则中发送给会话管理网元。
应理解，会话管理网元可以是在确定该应用的数据包将通过第一隧道发送给用户面网元之后，向用户面网元发送指示信息#1。
作为另一种可能的实现方式，该应用的数据包不是通过第一隧道进行传输，而是基于用户面协议。此时，第一数据包为IP包，第一数据包包括扩展头，该扩展头中包括该业务流对应的帧类型。此时，指示信息#1具体可以用来指示用户面网元根据扩展头中的帧类型确定该业务流对应的QFI，或者说，指示信息#1具体可以用来指示用户面网元在接收到第一数据包，且该第一数据包包括该应用的数据包时，根据该第一数据包中扩展头携带的帧类型确定该业务流对应的QFI。这里的扩展头例如是SRV6扩展头，或者IPv6扩展头。应理解，在该实现方式中，指示信息#1还用来指示用户面网元根据第一数据包的IP头确定该应用的数据包对应的QFI，此时，第一数据包的IP头用来区分不同的应用。
可选地，该第一数据包中还包括该应用的数据包所对应的帧的帧信息，这里的帧信息可以包括帧类型、指示信息#6、帧的大小信息、帧的QoS需求中的一项或者多项。指示信息#6用于指示应用的数据包所属的帧。需要说明的是，该指示信息#6可以是帧号，该帧号可以标识该应用的数据包所属的帧，也可以标识帧的序号以及该应用的数据包在该帧中的序号；或者，该指示信息#6是帧头标识和/或帧尾标识，介于帧头和帧尾间的数据包是同一个帧的数据包。或者，该指示信息#6用于指示该业务流的数据包是否与某个其他 数据包属于同一个帧。也就是说，指示信息#6可以显性地指示该应用的数据包所属的帧，也可以隐性地指示该应用的数据包所属的帧。应理解，上述帧信息可以包括在上述隧道头中，或者包括在上述扩展头中。
在这种情况下，会话管理网元可以向用户面网元发送指示信息#7，该指示信息#7用于指示用户面网元在第二隧道的隧道头中携带该帧信息，或者说，该指示信息#7用于指示用户面网元将该帧信息发送给下行节点。
应理解，指示信息#1、指示信息#2、指示信息#3、指示信息#7可以承载于同一个消息中，也可以承载于不同的消息中，也就是说，这几个指示信息可以同时发送，也可以不同时发送，本申请不作限定。
S240，用户面网元根据帧类型确定应用的数据包对应的QFI。
作为一个示例，当用户面网元通过第一隧道接收第一数据包时，则用户面网元根据指示信息#1，通过该第一数据包中的隧道头中的帧类型确定应用的数据包对应的QFI。
可选地，当该第一隧道为设备级隧道时，用户面网元可以根据该应用的数据包的IP头和该业务数据流的数据包的帧类型确定数据包对应的QFI；或者，当该第一隧道为应用级隧道时，用户面网元根据第一隧道的标识和该应用的数据包的帧类型确定数据包对应的QFI。
作为又一个示例，用户面网元接收到第一数据包，该业务流对应的帧类型包括在该第一数据包中的扩展头中，则用户面网元根据指示信息#1，通过该扩展头中的帧类型确定应用的数据包对应的QFI。
进一步地，用户面网元通过第二隧道发送该应用的数据包，并且在该第二隧道的隧道头中携带该应用的数据包对应的QFI。
因此，本申请实施例提供的通信方法，会话管理网元指示用户面网元根据应用的数据包对应的帧类型确定该数据包对应的QoS流，从而可以根据数据包的帧类型对数据包进行区分处理，提升用户体验。
图3是本申请实施例提供的通信方法300的示例性流程图。方法300包括：
S310，会话管理网元向用户面网元发送应用的特征信息。
对应的，用户面网元从该会话管理网元接收该应用的特征信息。
示例性地，该应用的特征信息用于确定该应用的数据包对应的帧类型，或者说，该应用的特征信息是与该应用的帧类型相关的特征信息。
例如，该应用的特征信息包括该应用的帧类型、应用的帧的发送规律、帧的突发大小、该应用的帧之间的间隔、该应用的IP头信息、应用标识、应用类型中的至少一项。示例性的，当应用是视频类应用时，应用的帧的发送规律可以是不同类型的视频帧的发送规律，例如，视频包括I帧和P帧，则帧的发送规律可以指示发送I帧和P帧的规律，例如，发送规律可以是IPPPIPPP，即发送一个I帧后发送3个P帧为一个周期循环。示例性的，所有应用的数据包可以使用相同的IP头信息，即使用相同的IP地址、端口号和协议号；或者，不同应用的不同帧类型的数据包使用不同的IP头信息，此时，用户面网元可根据IP头信息确定数据包的帧类型。
S320，会话管理网元向用户面网元发送指示信息#8。该指示信息#8用于指示用户面网元根据该应用的特征信息确定应用的数据包对应的帧类型。
对应的，用户面网元从该会话管理网元接收指示信息#8。
可选地，在S310之前，会话管理网元接收该帧类型对应的QoS参数，然后根据该帧类型对应的QoS参数确定该帧类型对应的QoS流的标识QFI。
可选地，会话管理网元向用户面网元发送指示信息#9，该指示信息#9用于指示用户面网元通过该QoS流发送该帧类型对应的数据包，或者说，该指示信息#9用于指示用户面网元通过第二隧道发送该帧类型对应的数据包，该第二隧道的隧道头包括该QFI。
可选地，会话管理网元向用户面网元发送指示信息#10，该指示信息#10用于指示用户面网元根据该特征信息检测该应用的数据包所属的帧。可选的，指示信息#10还可用于指示用户面网元根据该特征信息检测该应用的数据包所属的帧的其他帧信息，如帧的大小信息、该数据包在该帧中的相对位置信息(例如，相对于帧头的位置)、该数据包与哪些其他数据包属于同一帧等。
应理解，该应用的特征信息、指示信息#8、指示信息#9、指示信息#10可以承载于同一个消息中，也可以承载于不同的消息中，本申请对此不做限定。
S330，用户面网元根据应用的特征信息确定该应用的数据包对应的帧类型。
示例性地，若特征信息中包括帧的突发大小，由于不同帧类型对应的突发大小不同，例如I帧和P帧的突发大小不同，用户面网元可以根据帧的突发大小确定数据包对应的帧类型；或者特征信息包括应用的标识或类型时，用户面网元可预先获得该应用或该类型的应用包括I帧和P帧、且I帧比P帧具有更高的突发(也可以在特征信息中将上述信息发送给用户面网元)，则用户面网元可根据帧的突发大小确定数据包对应的帧类型。进一步地，如果特征信息中包括帧的间隔以及帧的发送规律，则用户面网元在确定了第一个帧的帧类型之后，便可以确定下一帧的帧类型，由此，在接收到后续的数据包之后，只要根据帧的间隔和帧的发送规律，用户面网元即可确定该数据包所对应的帧类型。
进一步地，用户面网元根据该帧类型确定该帧类型对应的QoS流。
可选地，根据指示信息#9，用户面网元通过该QoS流发送该帧类型对应的数据包。示例性地，用户面网元通过第二隧道发送该帧类型对应的数据包，该数据包封装在第二数据包中，该第二数据包包括第二隧道的隧道头，该第二隧道头中包括该数据包对应的帧信息和该QoS流的标识QFI。这里的帧信息可以包括帧类型、帧的大小信息、帧的QoS需求、用于指示该应用的应用的数据包所属帧的指示信息中的一项或者多项。
可选地，根据指示信息#10，用户面网元根据特征信息检测该应用的数据包所属的帧，并将该帧的信息发送给下行节点，例如，将该帧的信息包括在第二隧道的隧道头中。可选地，用户面网元还可以根据指示信息#10通过特征信息检测该应用的数据包所属的帧的其他帧信息，如帧的大小信息、该数据包在帧中的相对位置(如相对于帧头的位置)、该数据包与哪些其他数据包属于同一帧等，并将这些信息发送给下行节点。
因此，本申请实施例的通信方法，通过指示用户面网元根据应用的特征信息确定应用的数据包对应的QoS流，从而可以根据数据包的帧类型对数据包进行区分处理，提升用户体验。
图4是本申请实施例提供的通信方法400的示例性流程图。方法400包括：
S401，AS向第一功能发送建立连接请求消息。
示例性地，当AS需要发送应用的数据时，AS向第一功能发送建立连接请求消息。该建立连接请求消息用于请求5G系统为该应用的业务流分配资源，以便该应用的数据在经过5G网络传输时能得到恰当的QoS保证。这里的第一功能可以是MEP或者AF。
可选的，该建立连接请求消息可包括该应用的不同帧类型所对应的QoS需求信息。该建立连接请求用于请求第一功能为发送该应用的数据准备网络资源。
可选的，AS通过调用第一功能提供的第一应用程序接口(application programming interface，API)发送上述建立连接请求消息。第一API的参数包括应用的帧类型和对应的QoS需求。第一API的参数还可以包括该应用的数据包的IP头信息，如IP地址、端口号、协议号。
可选地，第一API的参数还可以包括应用的类型(例如AR/VR业务)、是否需要AF/MEP对应用进行处理、应用的特性等。
可选地，AS还可以请求第一功能对该应用的业务流进行处理，这里的处理例如可以是对应用的数据进行重新编码，或者是对应用的数据进行压缩，或者也可以是多种处理方式的组合，这里不作限定。
S402，第一功能向PCF/NEF发送应用信息。
示例性地，第一功能向PCF发送该应用的应用信息，该应用信息包括该应用的帧类型和对应QoS需求。
例如，AR/VR业务中增强层业务对应的帧和基础层业务对应的帧具有不同的帧类型，或者，AR/VR业务中的I帧和P帧具有不同的帧类型。作为一个具体示例：
第一功能根据AS的请求，将接收到的VR视频进行分层编码得到基础层业务数据包和增强层业务数据包，然后第一功能分别确定基础层帧和增强层帧的QoS需求，并通过应用信息将基础层帧和增强层帧的QoS需求发送给PCF/NEF。
可选地，在S403，若还未建立第一功能到UPF间的设备级隧道，则第一功能向PCF/NEF发送设备级隧道建立指示信息，该指示信息用于建立第一功能和UPF之间的设备级隧道。
应理解，该设备级隧道可以称为是一种N6隧道，第一功能可以通过N6隧道向UPF发送数据包，并通过N6隧道携带数据包的帧信息。
下面结合图5对一种N6隧道的结构作简单介绍：
N6隧道头可以在外层IP头和内层IP包之间，其中内层IP包也可以称作内层数据包，内层IP包包括内层IP头和数据包，内层IP头位于内层IP包的起始部分并与N6隧道头相连。当N6隧道为设备级隧道时，隧道的内层IP头包括应用的识别信息，该应用的识别信息用于识别数据包所属的应用，因此UPF可以根据内层IP头识别应用。N6隧道头中可以包括数据包的帧信息，例如数据包所属帧的帧类型、帧号等。N6隧道头中还可以包括该N6隧道的隧道标识或者其他字段，本申请不作限定。
可选地，第一功能还可以向PCF/NEF指示设备级隧道的类型(例如GRE隧道或GTP-U隧道)，具体方式不作限定。
可选地，第一功能可以向PCF/NEF发送用于指示该应用的数据包通过N6隧道发送给UPF的指示信息。
可选地，若该N6隧道还用于发送上行数据，第一功能还向PCF/NEF发送上行隧道标识信息(例如该N6隧道在第一功能上的IP地址、可选的隧道标识等)。
应理解，PCF可能通过配置的方式预先建立了设备级隧道。如果设备级隧道已经建立完成，则可以不执行S403。
S404，第一功能向PCF/NEF发送应用的识别信息。
应理解，该应用的识别信息用于识别数据包所属的应用，该应用的识别信息例如可以是该应用的应用标识或者五元组。应理解，在一些场景中，该应用的识别信息还可以进一步确定该应用中的具体业务流，即应用的识别信息既可以是识别到应用层面的信息，也可以识别到业务层面的信息，本申请不作限定。
应理解，设备级隧道是设备专用的，一个设备级隧道可能与多个不同的应用对应。因此，当通过设备级隧道传输数据包时，第一功能需要向PCF/NEF发送该应用的识别信息，以指示该数据包所对应的应用。
应理解，S402-S404的各条信息可以承载于一条消息中，也可以承载于不同的消息中，本申请不做限定。
应理解，上述方案是以AS与第一功能接口为例进行说明的。但是AS也可以直接与PCF/NEF接口。当AS直接与PCF/NEF接口时，可以直接由AS向PCF/NEF发送应用信息等内容，即该方案可以直接从S402开始执行，此时需要将第一功能替换成AS。
S405，PCF/NEF根据应用信息生成PCC规则。
S406，PCF/NEF向SMF发送PCC规则。
示例性地，该PCC规则中包括应用的识别信息，以及该应用的帧类型所对应的QoS参数。应理解，该应用的QoS参数可以包括该应用的不同帧类型的QoS参数，例如是不同帧类型的5QI、PDB等信息。PCF可以根据该应用的应用信息(QoS需求)确定该应用的帧类型对应的QoS参数。
可选地，如果N6隧道还没有建立，则PCC规则中还包括创建设备级隧道的指示信息，进一步地，还可以包括该设备级隧道的类型(例如GRE隧道或GTP-U隧道)。
可选地，若该第一隧道还用于发送上行数据，则该PCC规则中还可以包括上行隧道的标识信息等。
可选地，该PCC规则还可以携带通过N6隧道发送第一应用的数据包的指示信息。
如果PCC规则中包含建立设备级隧道指示信息，则可选地，在S407，SMF在AS和UPF之间(或者是MEP和UPF之间)建立设备级隧道。
S408，SMF根据QoS参数确定QFI。
示例性地，SMF从PCC规则中获取第一应用的帧类型所对应的QoS参数，并根据该QoS参数确定该帧类型所对应的QoS流的标识QFI。
具体地，SMF根据PCC规则中的不同帧类型对应的的QoS参数创建不同的QoS流，确定该应用的帧类型所对应的QFI。
进一步地，当SMF确定该应用的数据包通过N6隧道发送给UPF(或者说该应用的数据包将通过N6隧道进行传输)之后，SMF对UPF进行配置。其中，SMF可以根据配置信息确定该应用的数据包通过N6隧道发送给UPF，或者，SMF根据接收到的指示信息(例如PCC规则中携带通过N6隧道发送该应用的数据包的指示信息)确定该应用的数据包通过N6隧道发送给UPF。应理解，在一些场景中，该应用的数据包可以指的是该应用中的一个业务流的数据包。
下面通过S409-S412对SMF配置UPF的方案作示例性说明：
S409，SMF指示UPF根据N6隧道的内层IP头匹配应用对应的识别信息，以便确定数据包对应的QFI。例如，SMF向UPF发送指示信息，该指示信息用于指示UPF在通过N6隧道接收到应用的数据包时，通过N6隧道的内层IP头识别应用。
S410，SMF指示UPF根据N6隧道头的携带的帧信息中的帧类型，确定数据包所属的QoS流的标识QFI。具体地，SMF可以向UPF发送该应用的帧类型和QFI的对应关系。对应地，UPF接收到该帧类型和该QFI的对应关系之后，在本地保存该对应关系，以便后续在通过N6隧道接收到该应用的数据包时，根据隧道头中携带的帧类型确定该帧类型对应的QFI。
应理解，对于S408和S409，可以仅是一条指示信息，该指示信息用于指示UPF根据内层IP头(或者说该应用的数据包的IP头)和隧道头中携带的帧类型确定该应用的数据包对应的QFI。
可选地，S411，SMF还指示UPF将内层IP包封装到下行GTP-U隧道中发送给下游节点，GTP-U隧道头部包括该QoS流对应的QFI。或者说，SMF指示UPF通过该QFI标识的QoS流将该应用的数据包发送给下行节点。
进一步可选地，S412，SMF还可以指示UPF将N6隧道头中的帧信息拷贝到下行GTP-U的头部，以便发送给下行节点(如基站)，以便下行节点根据帧信息对数据包进行调度。该帧信息可以包括帧类型、帧的大小信息、帧的QoS需求、用于指示该应用的数据包所属帧的指示信息中的一项或多项。
应理解，S409-S412的各条信息可以承载于同一个消息中，也可以承载于不同的消息中，本申请对此不做限定。
进一步地，SMF对RAN进行配置。示例性地：
S413，SMF向RAN发送QoS流修改请求消息，该QoS流修改请求消息中包括第一应用对应的多个QoS流的QoS配置信息。
S414，SMF向第一功能发送响应消息。
示例性地，SMF通过PCF/NEF向第一功能发送响应消息。该响应消息中包括N6隧道的信息，例如N6隧道的IP地址和隧道标识。
S415，第一功能向AS发送建立连接响应消息。
示例性地，第一功能向AS发送建立连接响应消息，该建立连接响应消息用于响应AS发送的建立连接请求消息。当N6隧道建立在AS和UPF之间，则AF/MEP将隧道信息(即N6隧道的标识)发送给AS。
示例性的，若AS调用第一功能的第一API发送建立连接请求，则该响应消息可以是该第一API的响应。
进一步地，AS发送该应用的数据包。
当N6隧道建立在第一功能与UPF间时，AS通过第一功能发送该应用的数据包。相应的，AS将该应用的数据包发送给第一功能，由第一功能将该应用的数据包通过隧道发送给UPF。可选的，AS在向第一功能发送该应用的数据包时还发送该数据包对应的帧信息，第一功能在收到帧信息后将帧信息携带在隧道头部发送给UPF。在该方式下，可选的，AS可调用第一功能提供的第二API发送该应用的数据包。第二API的参数可以包括应用的数据包。可选的，第二API的参数还可以包括该应用的数据包对应的帧信息。
在一种实现方式中，第一功能对应用的数据包进行处理，例如，重新编码。此时，由第一功能确定帧信息并携带在隧道中发送给UPF。
当N6隧道建立在AS与UPF间时，AS将帧信息携带在隧道头部发送给UPF。
需要说明的是，AS也可以不预先请求建立连接，而直接请求第一功能发送数据包。 此时，在请求发送数据包时提供该数据包对应的帧类型的QoS需求。相应的，第二API的参数还包括QoS需求。可选的，在该方式下，第一功能可将QoS需求作为帧信息携带在隧道头部发送给UPF，并由UPF拷贝到第二隧道头中发送给基站。
因此，本申请实施例提供的通信方法，当UPF将通过N6隧道接收某应用的数据包时，配置UPF根据N6隧道的内层IP头和隧道头携带的帧信息中的帧类型确定数据包对应的QoS流，从而可以根据数据包的帧类型对数据包进行区分处理，提升用户体验，避免因网络无法识别媒体数据的帧类型，无法对不同类型是数据包进行区分处理，导致在一些情况下，例如网络拥塞的情况下，无法保障流畅的用户体验。
例如，在AR/VR业务场景中，由于此类业务会产生较大带宽的突发数据，因此会对网络造成比较大的冲击。当多个用户的突发数据包同时基站时，可能会导致基站在该瞬时无法处理所有的数据包，导致用户体验下降。因此，可以对不同帧类型的视频数据进行区分处理以保证基本的用户体验。比如，采用分层编码的方式处理AR/VR视频，即将视频流分层为增强层数据包和基础层数据包。当终端只接收到基础层数据包，未接收到任何增强层数据包时，用户仍可以观看该视频，但视频的清晰度下降；当增强层数据包接基础层数据包都到达终端设备时，用户可以观看更高清晰度的视频。分层编码后的基础层数据包和增强层属于不同帧类型的数据包，它们的重要性不同。为了保障流畅的用户体验，在一些情况下，例如网络拥塞时，系统应当优先保障将基础层数据包发送给终端，而增强层数据包即使适当丢包也不会过多得影响用户体验。因此，采用本申请实施例提供的通信方法，可以对分层编码的增强层数据包和基础层数据包采用不同的处理优先级，以便在网络拥塞时可以优先保障基础层数据包，从而避免观看AR/VR视频的多个用户的突发数据导致系统拥塞而影响用户体验。
又例如，AR/VR视频的数据包的帧类型包括I帧和P帧，其中，I帧为参考帧，P帧是数据帧，P帧需要依靠I帧才能进行解码，因此，I帧的丢失会导致后续几个P帧无法解码，而丢弃一个P帧仅仅影响一帧的画面。因此，采用本申请实施例提供的通信方法，可以对I帧和P帧的数据包采用不同的处理优先级，以便在网络拥塞时可以优先保障I帧的数据包，从而避免观看AR/VR视频的多个用户的突发数据导致系统拥塞而影响用户体验。
图6是本申请实施例提供的通信方法600的示例性流程图。方法600包括：
S601，AS向第一功能发送建立连接请求消息。
S602，第一功能向PCF发送应用信息。
应理解，S601-S602与方法400中的S401-S402类似，本申请不再赘述。
S603，第一功能向PCF/NEF发送应用级隧道建立指示信息，该指示信息用于建立第一功能和UPF之间的应用级隧道。
应理解，该应用级隧道可以称为是一种N6隧道，AS可以通过N6隧道向UPF发送数据包，并通过N6隧道携带数据包的帧信息。
S604，PCF/NEF根据应用信息生成PCC规则。
S605，PCF/NEF向SMF发送PCC规则。
示例性地，该PCC规则中包括创建应用级隧道的指示信息。进一步地，还可以包括该应用级隧道的类型(例如GRE隧道或GTP-U隧道)。
可选地，若该N6隧道还用于发送上行数据，则该PCC规则中还可以包括上行隧道的 标识信息等。
可选地，该PCC规则还可以携带通过N6隧道发送应用的数据包的指示信息。
应理解，应用级隧道是应用专用的，即应用级隧道只对应于一个业务，根据隧道即可区分不同应用。因此，当第一功能指示PCF/NEF建立的N6隧道为应用级隧道时，第一功能不需要向PCF/NEF发送应用的识别信息。
S606，SMF建立N6隧道。
示例性地，根据PCC规则中的创建应用级隧道的指示信息，SMF在第一功能和UPF之间建立应用级隧道。
进一步地，SMF为应用获取N6隧道信息(包括IP地址和逻辑隧道标识)。例如，SMF从UPF获取N6隧道的信息。
应理解，应用级隧道是应用专用的，因此UPF可以根据N6隧道的隧道信息确定数据包所属的应用。
S607，SMF根据应用的帧类型对应的QoS参数确定该帧类型对应的QFI。
S607与方法400中的S408类似，为了简洁，不再重复说明。
进一步地，当SMF确定应用的数据包通过N6隧道发送给UPF(或者说应用的数据包将通过N6隧道进行传输)之后，对UPF进行配置。其中，SMF可以根据配置信息确定应用的数据包通过N6隧道发送给UPF，或者，SMF根据接收到的指示信息(例如PCC规则中携带通过N6隧道发送应用的数据包的指示信息)确定应用的数据包通过N6隧道发送给UPF。
下面通过S608-S610对SMF配置UPF的方案作示例性说明：
S607，SMF指示UPF根据隧道信息和隧道头中的帧信息(例如帧类型)确定数据包对应的QoS流。
示例性地，SMF向UPF发送指示信息，该指示信息用于指示UPF在通过N6隧道接收到应用的数据包时，根据N6隧道的隧道信息确定数据包所属的应用，并根据N6隧道头中携带的帧类型确定数据包所属的QoS流(即确定该QoS流对应的QFI)。
进一步，可选地，S609，SMF还可以指示UPF将N6隧道头部的帧信息拷贝到下行GTP-U的头部，以便发送给下行节点(如基站)，以便下行节点根据帧号对数据包进行调度。SMF还可以指示UPF将帧信息中的其他信息拷贝到GTP-U的头部，本申请不作限定。
可选地，S610，SMF还指示UPF将内层IP包封装到下行GTP-U隧道中发送给下游节点，GTP-U隧道头部包括该QoS流对应的QFI。
应理解，S611-S613与方法400中的S412-S415类似，为了简洁，不再重复说明。
因此，本申请实施例提供的通信方法，当UPF将通过N6隧道接收某应用的数据包时，配置UPF根据N6隧道的隧道信息以及隧道头携带的帧类型确定数据包对应的QoS流，从而可以对不同帧类型的数据包进行区分处理，提升用户体验。
图7是本申请实施例提供的方法700的示意性流程图。应理解，方法700可以与方法400或方法600结合，即方法700可以在方法400或方法600之后执行，也可以单独执行。方法700包括：
首先，AS通过N6隧道发送数据包。
在一种可能的情况中，当N6隧道在AS和UPF之间(记为情况1)，则在S701，AS通过N6隧道将数据包发送给UPF。
示例性地，AS将原始数据包封装在N6隧道中，并在N6隧道的头部携带数据包的帧信息，例如数据包对应的帧类型、帧号等信息。AS通过N6隧道直接将数据包和数据包对应的媒体信息发送给UPF。
在另一种可能的情况中，当N6隧道在第一功能和UPF之间(记为情况2)，则在S702，AS先将数据包和帧信息发送给第一功能，由第一功能在S703，通过N6隧道将数据包发送给UPF。
示例性地，第一功能从AS接收数据包和数据包对应的帧信息，将数据包封装在N6隧道中，并在N6隧道的头部携带数据包对应的帧信息，例如数据包对应的帧类型、帧号等信息。AS通过N6隧道将数据包和数据包对应的帧信息发送给UPF。
可选地，在情况2中，第一功能还可以将AS发送的数据包进行应用层的处理，例如对数据包进行重新编码。在这种情况下，第一功能将处理后的数据包封装在N6隧道中，并在N6隧道的头部携带处理后的数据包对应的帧信息。
进一步地，UPF确定数据包对应的QoS流。
在一种可能的情况中，当N6隧道为设备级隧道时(记为情况a)，则：
S703，UPF根据应用的识别信息和帧类型确定QFI。
示例性地，UPF通过N6隧道接收第一功能/AS发送的数据包，并通过N6隧道的内部IP头获取应用的识别信息，根据该应用的识别信息确定数据包对应的应用。UPF在N6隧道的头部获取数据包对应的帧类型，并根据该帧类型和应用识别信息确定数据包对应的QoS流的标识QFI。
在另一种可能的情况中，当N6隧道为应用隧道时(记为情况b)，则：
S704，UPF根据隧道标识和帧类型确定QFI。
示例性地，UPF通过N6隧道接收第一功能/AS发送的数据包，并且由于应用级隧道是业务专用的，因此UPF可以根据N6的隧道信息确定数据包对应的应用。UPF在N6隧道的头部获取数据包对应的帧类型，并根据该帧类型和N6隧道信息确定数据包对应的QFI。
进一步地，UPF将该应用的数据包发送给RAN。
可选地，S705，UPF将内层IP包封装在GTP-U隧道中。
可选地，S706，UPF将帧信息拷贝到GTP-U隧道头部。
示例性地，N6隧道头中还包括该应用的数据包所对应的帧的帧信息。UPF将N6隧道头中的帧信息拷贝到GTP-U隧道头部。
然后在S707，UPF通过GTP-U隧道将该应用的数据包发送给RAN，该GTP-U隧道中携带该数据包对应的QFI。
S708，RAN对数据包进行调度。
示例性地，RAN通过GTP-U隧道从UPF接收数据包，并根据数据包对应的QFI确定数据包对应的QoS流的QoS参数，然后RAN按照该QoS参数对数据包进行调度。
如果GTP-U隧道中携带了数据包对应的帧号等信息，例如GTP-U隧道头部携带了帧标识，则RAN可以进行帧粒度的调度。例如，当一个帧的丢包率超过一定阈值时，RAN可丢弃该帧中后续的数据包。RAN还可根据帧所对应的QoS参数进行调度，例如，RAN根据帧所对应的PDB进行调度，丢弃该帧的在RAN的处理时延超过PDB的数据包。
因此，本申请实施例提供的通信方法，当UPF通过N6隧道接收某应用的数据包时，UPF根据N6隧道的隧道信息，以及隧道头携带的媒体信息中的帧类型确定数据包对应的 QoS流，并将该数据包通过该QoS流发送给下游节点，从而可以使得网络侧能够根据数据包的帧类型对数据包进行区分处理，提升用户体验，避免因网络无法识别媒体数据的帧类型而无法不同类型的数据进行区分处理，导致在一些情况下，例如网络拥塞或资源不够的情况下，无法保障流畅的用户体验。
图8是本申请实施例提供的方法800的示意性流程图。方法800包括：
S801，第一功能向SMF发送应用标识和特征信息。
示例性地，当AS需要发送应用的数据时，AS向第一功能发送该应用的应用标识和特征信息，然后第一功能通过PCF/NEF将应用标识和帧特征信息发送给SMF。
帧特征信息可以包括帧的发送规律，例如，帧的发送规律可以是IPPP IPPP IPPP……，这里的I表示I帧，P表示P帧，因此这里的帧的发送规律是发送一次I帧的数据，然后发送三次P帧的数据，然后重复这样的发送方式。帧的特征信息还可以包括帧的突发大小，例如I帧的突发大小、P帧的突发大小。帧的特征信息还可以包括每个帧之间的间隔。当媒体帧分为增强层帧和基础层帧时，帧的特征信息可以包括增强层帧的特征和基础层帧的特征，例如，增强层的发送规律和基础层的发送规律，增强层的帧突发大小、基础层的帧突发大小，增强层的帧间隔、基础层的帧间隔等。
应理解，上述方案是以AS与第一功能接口为例进行说明的。但是AS也可以直接与PCF/NEF接口。当AS直接与PCF/NEF接口时，可以直接由AS向PCF/NEF发送应用的应用标识和特征信息。
S802，第一功能向PCF/NEF发送应用信息。
示例性地，当应用启动后，AS再通过第一功能向PCF/NEF发送该应用的应用信息，该应用信息包括该应用的应用标识和该应用的QoS需求。
在该应用的QoS需求中，第一功能可以指示不同帧类型的QoS需求。例如，AR/VR业务中增强层业务对应的数据包和基础层业务对应的数据包对应不同的帧类型，或者，AR/VR业务中的I帧的数据包和P帧的数据包也对应不同的帧类型。作为一个具体示例：
第一功能根据AS的请求，将接收到的VR视频进行分层编码得到基础层业务数据包和增强层业务数据包，然后第一功能分别确定基础层业务数据包和增强层业务数据包的QoS需求，并通过应用信息将基础层业务数据包和增强层业务数据包的QoS需求发送给PCF/NEF。
S803，PCF/NEF确定应用对应的QoS参数。
示例性地，PCF根据该应用的应用信息，确定该应用的帧类型所对应的QoS参数，该应用的QoS参数可以包括该应用的不同帧类型的QoS参数。例如，该应用的应用信息中包括增强层帧对应的QoS需求和基础层帧对应的QoS需求，则PCF根据以上信息确定增强层帧对应的QoS参数和基础层帧对应的QoS参数。进一步地，
在S804，PCF/NEF将第一应用的QoS参数发送给SMF。
在另一种可能的方案(记为方案2)中，AF可以将应用标识、特征信息、QoS需求一起发送给PCF/NEF。示例性地：
S805，第一功能向PCF/NEF发送该应用的应用标识、该应用的特征信息、该应用的应用信息，其中，该应用的应用信息包括该应用的QoS需求。
S806，PCF/NEF确定该应用的帧类型对应的QoS参数。具体方案与S803类似，不再重复说明。
S807，PCF/NEF向SMF发送该应用的应用标识、该应用的特征信息和该应用的帧类型对应的QoS参数。
进一步地，SMF对UPF进行配置，以便UPF在接收到数据包时可以确定数据包的帧类型。下面通过S808-S811对SMF配置UPF的方案作示例性说明：
S808，SMF向UPF发送特征信息。应理解，该特征信息用于UPF确定数据包所属的帧类型。
S809，SMF指示UPF根据帧类型确定QFI，即确定数据包对应的QoS流。
S810，SMF指示UPF通过该QoS流将数据包发送给下游节点，具体地，SMF可以指示UPF在接收到第一应用的数据包之后，将该数据包封装到下行GTP-U中，该GTP-U包头中应包括数据包对应的QFI。进一步地，UPF将封装后的数据包发送给下行节点，该下游节点可以是RAN。
S811，SMF指示UPF检测帧号。示例性地，SMF指示UPF根据特征信息检测数据包对应的帧号。
S812，SMF建立QoS流。
示例性地，SMF根据第一应用的QoS参数建立QoS流。应理解，当SMF接收到的QoS参数是应用的不同帧类型对应的QoS参数时，SMF根据各帧类型的QoS参数创建不同的QoS流。
进一步地，SMF对RAN进行配置。示例性地：
S813，SMF向RAN发送QoS流修改请求消息。可选地，该QoS流修改请求消息中包括应用对应的多个QoS流的QoS配置信息。
因此，本申请实施例提供的通信方法，配置UPF根据该应用的特征信息确定数据包的帧类型，并指示UPF根据该帧类型确定数据包对应的QoS流，从而可以对不同帧类型的数据包进行区分处理，提升用户体验。
图9是本申请实施例提供的方法900的示例性流程图。应理解，方法900可以与方法800结合，即方法900可以在方法800之后执行，也可以单独执行。方法900包括：
S901，UPF接收下行数据包。
示例性地，UPF从AF/MEP/AS接收第一应用的数据包。
S902，UPF确定数据包对应的帧类型。
作为一种可能的实现方式，UPF根据特征信息确定数据包对应的帧类型。
示例性地，若特征信息中包括帧的突发大小，由于不同帧类型对应的突发大小不同，例如I帧和P帧的突发大小不同，UPF可以根据帧的突发大小确定数据包对应的帧类型。进一步地，如果特征信息中包括帧的间隔以及帧的发送规律，则UPF在确定了第一个帧的帧类型之后，UPF便可以确定下一帧的帧类型，由此，在接收到后续的数据包之后，只要根据帧的间隔和帧的发送规律，UPF即可确定该数据包所对应的帧类型。
应理解，在这种实现方式中，UPF预先保存了该应用的特征信息，该特征信息与应用的应用标识相关联。例如，方法800中，SMF给UPF发送的应用的特征信息为应用的标识，当UPF接收到应用的数据包后，UPF根据应用的标识在本地存储中获取该应用的特征信息，然后根据该特征信息确定数据包对应的帧类型。
作为另一种可能的实现方式，UPF通过数据包携带的信息确定帧类型。
应理解，在这种实现方式中，S901发送的数据包在应用层字段中携带了数据包的帧 类型的信息，UPF通过解析数据包可以获取数据包对应的帧类型。或者说，该应用的数据封装在一个数据包中，该数据包包括扩展头，该扩展头中携带该数据包的帧类型，UPF可以从数据包的扩展头中获取该数据包对应的帧类型。这里的扩展头例如可以是SRV6扩展头，或者IPv6扩展头。
可选地，在S903，UPF确定数据包对应的帧号。
作为一种可能的实现方式，UPF根据特征信息确定数据包对应的帧号。示例性地，UPF确定了第一个帧之后，可以根据帧的间隔和帧的发送规律确定下一帧，并为下一帧的所有数据包打上相同的帧号。
作为另一种可能的实现方式，UPF根据数据包携带的信息确定帧号。应理解，在这种实现方式中，S901发送的数据包中携带了数据包的帧号的信息，UPF可以根据应用的类型确定帧号携带的位置，并通过解析数据包可以获取数据包对应的帧号。示例的，数据包的扩展字段中携带帧号信息。
S904，UPF确定数据包对应的QoS流。
示例性地，UPF根据数据包对应的帧类型确定数据包对应的QoS流(即确定QFI)。
进一步地，UPF通过该QoS流将第一应用的数据包发送给下游节点。示例性地：
S905，UPF将数据包封装到下行GTP-U隧道中，GTP-U头部包括S904中确定的QFI。
可选地，如果UPF还确定了帧号等信息，则在S906，UPF将帧号等信息拷贝到GTP-U隧道的头部。
S907，UPF通过GTP-U将数据包发送给RAN。
S908，RAN对数据包进行调度。
S908与方法700中的S708类似，本申请在此不再赘述。
因此，本申请实施例提供的通信方法，当UPF接收到第一应用的数据包之后，UPF根据应用的特征信息确定数据包对应的帧类型，或者UPF根据数据包携带的信息确定数据包对应的帧类型，并根据该帧类型确定数据包对应的QoS流，并将该数据包通过该QoS流发送给下游节点，从而可以使得网络侧能够根据数据包的帧类型对数据包进行区分处理，提升用户体验，避免因网络无法识别媒体数据的帧类型而无法不同类型的数据进行区分处理，导致在一些情况下，例如网络拥塞或资源不够的情况下，无法保障流畅的用户体验。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。例如，方法400和方法700可以结合使用，也可以独立使用。又如，方法800可以单独使用，也可以作为方法900的准备工作结合使用，等等。
可以理解的是，上述各个方法实施例中，由网络设备(如各个网元)实现的方法和操作，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
以上，结合图2至图9详细说明了本申请实施例提供的方法。以下，结合图10至图11详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图10是本申请实施例提供的通信装置10的示意性框图。该通信装置10包括收发单元11和处理单元12。收发单元11可以实现相应的通信功能，处理单元12用于进行数据处理。收发单元11还可以称为通信接口或通信单元。
可选地，该装置10还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元12可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该装置10可以用于执行上文方法实施例中网络设备(如各个网元，具体地，可以是会话管理网元，或者用户面网元等)所执行的动作，这时，该装置10可以为网络设备或者可配置于网络设备的部件，收发单元11用于执行上文方法实施例中网络设备侧的收发相关的操作，处理单元12用于执行上文方法实施例中网络设备侧的处理相关的操作。
作为一种设计，该装置10用于执行上文实施例中会话管理网元(或者SMF)所执行的动作。
一种可能的实现方式，处理单元12，用于获取第一规则，所述第一规则包括应用的帧类型所对应的服务质量QoS参数；收发单元11，用于根据所述第一规则向用户面网元发送第一指示信息，所述第一指示信息用于指示所述用户面网元根据所述帧类型确定应用的数据包对应的QoS流的标识QFI，所述业务流是所述应用的业务流，所述应用的数据包封装在第一数据包中，所述第一数据包包括所述帧类型。
另一种可能的实现方式，收发单元11，用于向用户面网元发送应用的特征信息；所述收发单元11，还用于向用户面网元发送第七指示信息，所述第七指示信息用于指示所述用户面网元根据所述特征信息确定所述应用的数据包对应的帧类型。其中，所述特征信息包括所述应用的帧的发送规律、所述应用的帧的突发大小、所述应用的帧之间的间隔中的至少一项。
该装置10可实现对应于根据本申请实施例的方法实施例中的会话管理网元(或者SMF)执行的步骤或者流程，该装置10可以包括用于执行方法实施例中的会话管理网元(或者SMF)执行的方法的单元。并且，该装置10中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的会话管理网元(或者SMF)中的方法实施例的相应流程。
其中，当该装置10用于执行图2中的方法200时，收发单元11可用于执行方法200中的收发步骤，如步骤S220；处理单元12可用于执行方法200中的处理步骤，如步骤S210。
其中，当该装置10用于执行图3中的方法300时，收发单元11可用于执行方法300中的步骤S310、S320。
当该装置10用于执行图4中的方法400时，收发单元11可用于执行方法400中的步骤S409-S414；处理单元12可用于执行方法400中的处理步骤，如步骤S407、S408。
当该装置10用于执行图6中的方法600时，收发单元11可用于执行方法600中的步骤S608-S612；处理单元12可用于执行方法600中的处理步骤，如步骤S606、S607。
当该装置10用于执行图8中的方法800时，收发单元11可用于执行方法800中的步骤S801、S804、S807-S811、S813；处理单元12可用于执行方法800中的处理步骤，如步骤S812。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置10用于执行上文方法实施例中用户面网元(或者UPF)所执行的动作。
一种可能的实现方式，收发单元11，用于接收第一数据包，所述第一数据包包括应用的数据包和所述应用的数据包对应的帧类型；处理单元12，用于根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI。
另一种可能的实现方式，收发单元11，用于接收应用的特征信息；所述收发单元11，还用于根据所述应用的特征信息确定所述应用的数据包对应的帧类型。其中，所述特征信 息包括所述应用的帧的发送规律、所述应用的突发大小、所述应用的帧之间的间隔中的至少一项。
该装置10可实现对应于根据本申请实施例的方法实施例中的用户面网元(或者UPF)执行的步骤或者流程，该装置10可以包括用于执行方法实施例中的用户面网元(或者UPF)执行的方法的单元。并且，该装置10中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的用户面网元(或者UPF)中的方法实施例的相应流程。
其中，当该装置10用于执行图2中的方法200时，收发单元11可用于执行方法200中的步骤S220、S230；处理单元12可用于执行方法200中的处理步骤，如步骤S240。
当该装置10用于执行图3中的方法300时，收发单元11可用于执行方法300中的步骤S310、S320；处理单元12可用于执行方法300中的处理步骤，如步骤S330。
当该装置10用于执行图4中的方法400时，收发单元11可用于执行方法400中的步骤S409-S412。
当该装置10用于执行图6中的方法600时，收发单元11可用于执行方法600中的步骤S608-S610。
当该装置10用于执行图7中的方法700时，收发单元11可用于执行方法700中的步骤S701、S703、S707；处理单元12可用于执行方法700中的处理步骤，如步骤S703-S706。
当该装置10用于执行图8中的方法800时，收发单元11可用于执行方法800中的步骤S807-S811。
当该装置10用于执行图9中的方法900时，收发单元11可用于执行方法900中的步骤S901、S907；处理单元12可用于执行方法900中的处理步骤，如步骤S902-S906。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置10用于执行上文方法实施例中策略控制网元(或者PCF)所执行的动作。
一种可能的实现方式，收发单元11，用于接收应用的信息，所述应用的信息包括所述应用的的帧类型；收发单元11，还用于向会话管理网元发送所述帧类型对应的服务质量QoS参数。
该装置10可实现对应于根据本申请实施例的方法实施例中的策略控制网元(或者PCF)执行的步骤或者流程，该装置10可以包括用于执行方法实施例中的策略控制网元(或者PCF)执行的方法的单元。并且，该装置10中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的策略控制网元(或者PCF)中的方法实施例的相应流程。
其中，当该装置10用于执行图4中的方法400时，收发单元11可用于执行方法400中的步骤S402-S404、S406；处理单元12可用于执行方法400中的处理步骤，如S405。
当该装置10用于执行图6中的方法600时，收发单元11可用于执行方法600中的步骤S602、S603；处理单元12可用于执行方法600中的处理步骤，如S604。
当该装置10用于执行图8中的方法800时，收发单元11可用于执行方法800中的步骤S801、S802、S805；处理单元12可用于执行方法800中的处理步骤，如S803或S806。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理单元12可以由至少一个处理器或处理器相关电路实现。收发单 元11可以由收发器或收发器相关电路实现。存储单元可以通过至少一个存储器实现。
如图11所示，本申请实施例还提供一种装置20。该装置20包括处理器21，处理器21与存储器22耦合，存储器22用于存储计算机程序或指令和/或数据，处理器21用于执行存储器22存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。
可选地，该装置20包括的处理器21为一个或多个。
可选地，如图11所示，该装置20还可以包括存储器22。
可选地，该装置20包括的存储器22可以为一个或多个。
可选地，该存储器22可以与该处理器21集成在一起，或者分离设置。
可选地，如图11所示，该装置20还可以包括收发器23，收发器23用于信号的接收和/或发送。例如，处理器21用于控制收发器23进行信号的接收和/或发送。
作为一种方案，该装置20用于实现上文方法实施例中由网络设备(如上述各个网元)执行的操作。
本申请实施例还提供一种装置30，该装置30可以是网络设备也可以是芯片。该装置30可以用于执行上述方法实施例中由网络设备(如上述各个网元)所执行的操作。
图12示出了一种简化的结构示意图。装置30包括31部分以及32部分。31部分主要用于射频信号的收发以及射频信号与基带信号的转换；32部分主要用于基带处理，对基站进行控制等。31部分通常可以称为收发单元、收发机、收发电路、或者收发器等。32部分通常是基站的控制中心，通常可以称为处理单元，用于控制基站执行上述方法实施例中接收端设备侧的处理操作。
31部分的收发单元，也可以称为收发机或收发器等，其包括天线和射频电路，其中射频电路主要用于进行射频处理。可选地，可以将31部分中用于实现接收功能的器件视为接收单元，将用于实现发送功能的器件视为发送单元，即31部分包括接收单元和发送单元。接收单元也可以称为接收机、接收器、或接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
32部分可以包括一个或多个单板，每个单板可以包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对基站的控制。若存在多个单板，各个单板之间可以互联以增强处理能力。作为一种可选的实施方式，也可以是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
应理解，图12仅为示例而非限定，上述包括收发单元和处理单元的网络设备可以不依赖于图12所示的结构。
当该装置30为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。当然装置30还可以为一个芯片系统或处理系统，使得安装该装置30的设备可以实现本申请实施例的方法和功能。例如，处理单元32可以为芯片系统或处理系统中的处理电路，实现对安装了该芯片系统或处理系统的设备的控制，还可以耦合链接存储单元，调用存储单元中的指令，使得设备可以实现本申请实施例的方法和功能，收发单元31，可以为芯片系统或处理系统中的输入输出电路，将芯片系统处理好的信息输出，或将待处理的数据或信令信息输入芯片系统进行处理。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例 中由网络设备(如各个网元)执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由网络设备(如各个网元)执行的方法。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(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或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的保护范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的 部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质可以包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种通信方法，其特征在于，包括：
    会话管理网元获取第一规则，所述第一规则包括应用的帧类型所对应的服务质量QoS参数；
    所述会话管理网元根据所述第一规则向用户面网元发送第一指示信息，所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，所述应用的数据包封装在第一数据包中，所述第一数据包包括所述帧类型。
  2. 根据权利要求1所述的方法，其特征在于，所述应用的数据包通过第一隧道传输，所述第一数据包包括所述第一隧道的隧道头，所述第一隧道的隧道头包括所述帧类型；
    所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的服务质量QoS流的标识QFI，包括：
    所述第一指示信息用于指示所述用户面网元根据所述第一隧道的隧道头中的帧类型确定所述QFI。
  3. 根据权利要求2所述的方法，其特征在于，所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，包括：
    所述第一指示信息用于指示所述用户面网元根据所述应用的数据包的互联网协议IP头和所述帧类型确定所述QFI；
    或者，所述第一指示信息用于指示所述用户面网元根据所述第一隧道的标识和所述帧类型确定所述QFI，所述第一隧道的标识包括在所述第一隧道的隧道头中。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元确定所述应用的数据包通过所述第一隧道发送给所述用户面网元。
  5. 根据权利要求4所述的方法，其特征在于，会话管理网元确定所述应用的数据包通过所述第一隧道发送给所述用户面网元，包括：
    所述会话管理网元接收来自策略控制网元的第二指示信息；
    所述会话管理网元根据所述第二指示信息确定所述应用的数据包通过所述第一隧道发送给所述用户面网元；或者，
    所述会话管理网元根据配置信息确定所述应用的数据包将通过所述第一隧道发送给所述用户面网元。
  6. 根据权利要求1所述的方法，其特征在于，所述第一数据包包括扩展头，所述扩展头包括所述帧类型；
    所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的服务质量QoS流的标识QFI，包括：
    所述第一指示信息用于指示所述用户面网元根据所述扩展头中的帧类型确定所述QFI。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元根据所述帧类型对应的QoS参数确定所述帧类型对应的所述QFI。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述用户面网元发送第三指示信息，所述第三指示信息用于指示所述用户面网元通过第二隧道发送所述应用的数据包，所述第二隧道的隧道头包括所述 QFI。
  9. 根据权利要求8所述的方法，其特征在于，所述第一数据包中还包括所述应用的数据包所对应的帧的帧信息，所述帧信息包括所述帧类型、第四指示信息、所述帧的大小信息、所述帧的QoS需求信息中的一项或多项，所述第四指示信息用于指示所述应用的数据包所属的帧；
    所述方法还包括：
    所述会话管理网元向所述用户面网元发送第五指示信息，所述第五指示信息用于指示所述用户面网元在所述第二隧道的隧道头中携带所述帧信息。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述用户面网元发送第六指示信息，所述第六指示信息用于指示所述用户面网元建立所述第一隧道；
    所述会话管理网元从所述用户面网元接收所述第一隧道的信息。
  11. 一种通信方法，其特征在于，包括：
    用户面网元接收第一数据包，所述第一数据包包括应用的数据包和所述应用的数据包对应的帧类型；
    所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI。
  12. 根据权利要求11所述的方法，其特征在于，所述用户面网元接收第一数据包，包括：
    所述用户面网元通过第一隧道接收所述第一数据包，所述第一数据包包括所述第一隧道的隧道头，所述第一隧道的隧道头包括所述帧类型；
    所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，包括：
    所述用户面网元根据所述第一隧道的隧道头中的帧类型确定所述应用的数据包对应的所述QFI。
  13. 根据权利要求12所述的方法，其特征在于，所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，包括：
    所述用户面网元根据所述应用的数据包的互联网协议IP头和所述帧类型确定所述数据包对应的QFI；或者
    所述用户面网元根据所述第一隧道的标识和所述帧类型确定所述应用的数据包对应的QFI，所述第一隧道的标识包括在所述第一隧道的隧道头中。
  14. 根据权利要求11所述的方法，其特征在于，所述帧类型包括在所述第一数据包的扩展头中，所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，包括：
    所述用户面网元根据所述扩展头中的帧类型确定所述应用的数据包对应的QFI。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元通过第二隧道发送所述应用的数据包，所述第二隧道的隧道头包括所述QFI。
  16. 根据权利要求5所述的方法，其特征在于，所述第一数据包还包括所述应用的数据包所对应的帧的帧信息，所述帧信息包括所述帧类型、第四指示信息、所述帧的大小信息、所述帧的QoS需求信息中的一项或多项，所述第四指示信息用于指示所述应用的数 据包所属的帧，所述第二隧道的隧道头中包括所述帧信息。
  17. 根据权利要求11至16中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收第一指示信息，所述第一指示信息用于指示所述用户面网元根据所述第一隧道的隧道头中的帧类型或根据所述扩展头中的帧类型确定所述QFI。
  18. 根据权利要求15或16所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收第三指示信息，所述第三指示信息用于指示所述用户面网元通过所述第二隧道发送所述应用的数据包，所述第二隧道的隧道头包括所述QFI。
  19. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述用户面网元接收第五指示信息，所述第五指示信息用于指示所述用户面网元在所述第二隧道的隧道头中携带所述帧信息。
  20. 一种通信方法，其特征在于，包括：
    所述会话管理网元从应用功能网元接收应用的特征信息；
    会话管理网元向用户面网元发送所述应用的特征信息和第七指示信息，所述第七指示信息用于指示所述用户面网元根据所述特征信息确定所述应用的数据包对应的帧类型。
  21. 根据权利要求20所述的方法，其特征在于，所述特征信息包括所述应用的帧的发送规律、所述应用的帧的突发大小、所述应用的帧之间的间隔、所述应用的IP头信息、所述应用的标识、所述应用的类型中的至少一项。
  22. 根据权利要求20或21所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元接收所述帧类型对应的QoS参数；
    所述会话管理网元根据所述帧类型对应的QoS参数确定所述帧类型对应的QoS流；
    所述会话管理网元向所述用户面网元发送第八指示信息，所述第八指示信息用于指示所述用户面网元通过所述QoS流发送所述帧类型对应的数据包。
  23. 根据权利要求22所述的方法，其特征在于，所述第八指示信息用于指示所述用户面网元通过所述QoS流发送所述帧类型对应的数据包，包括：
    所述第八指示信息用于指示所述用户面网元通过第二隧道发送所述帧类型对应的数据包，所述数据包封装在第二数据包中，所述第二数据包还包括所述第二隧道的隧道头，所述第二隧道的隧道头包括所述数据包对应的帧信息和所述QoS流的标识QFI，所述帧信息包括所述帧类型、第九指示信息、所述帧的大小信息、所述帧的QoS需求信息中的一项或多项，所述第九指示信息用于指示所述应用的数据包所属的帧。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述用户面网元发送第十指示信息，所述第十指示信息用于指示所述用户面网元根据所述特征信息检测所述应用的数据包所属的帧。
  25. 一种通信方法，其特征在于，包括：
    用户面网元接收来自会话管理网元的应用的特征信息和第七指示信息；
    所述用户面网元根据所述第七指示信息来确定所述应用的数据包对应的帧类型，所述帧类型是根据所述应用的特征信息确定的。
  26. 根据权利要求25所述的方法，其特征在于，所述特征信息包括所述应用的帧的发送规律、所述应用的突发大小、所述应用的帧之间的间隔、所述应用的IP头信息、所述应用的标识、所述应用的类型中的至少一项。
  27. 根据权利要求25或26所述的方法，其特征在于，所述方法还包括：
    所述用户面网元根据所述应用的帧类型确定所述帧类型对应的QoS流；
    所述用户面网元通过所述QoS流发送所述帧类型对应的数据包。
  28. 根据权利要求27所述的方法，其特征在于，所述用户面网元通过所述QoS流发送所述帧类型对应的数据包，包括：
    所述用户面网元通过第二隧道发送所述帧类型对应的数据包，所述数据包封装在第二数据包中，所述第二数据包还包括第二隧道的隧道头，所述第二隧道头包括所述数据包对应的帧信息和所述QoS流的标识QFI，所述帧信息包括所述帧类型、第九指示信息、所述帧的大小信息、所述帧的QoS需求信息中的一项或多项，所述第九指示信息用于指示所述应用的数据包所属的帧。
  29. 根据权利要求25至28中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面网元根据所述特征信息检测所述应用的数据包所属的帧；
    所述用户面网元将所述帧的信息包括在所述第二隧道的隧道头中。
  30. 一种通信系统，其特征在于，所述系统包括会话管理网元和用户面网元；
    所述会话管理网元，用于获取第一规则，所述第一规则包括应用的帧类型所对应的服务质量QoS参数；根据所述第一规则向用户面网元发送第一指示信息，所述第一指示信息用于指示所述用户面网元根据所述帧类型确定所述应用的数据包对应的QoS流的标识QFI，所述应用的数据包封装在第一数据包中，所述第一数据包包括所述帧类型；
    所述用户面网元，用于接收所述第一指示信息。
  31. 根据权利要求30所述的系统，其特征在于，所述系统还包括策略控制网元，所述策略控制网元用于：接收所述应用的信息，所述应用的信息包括所述应用对应的帧类型；向所述会话管理网元发送所述帧类型对应的所述QoS参数。
  32. 根据权利要求31所述的系统，其特征在于，所述应用的信息指示创建所述第一隧道，所述第一隧道用于向用户面网元发送所述应用的数据包；
    所述策略控制网元还用于：向会话管理网元发送第十一指示信息，所述第十一指示信息用于指示所述会话管理网元建立所述第一隧道。
  33. 一种通信系统，其特征在于，包括会话管理网元和用户面网元；
    所述会话管理网元，用于向所述用户面网元发送应用的特征信息；向用户面网元发送第七指示信息，所述第七指示信息用于指示所述用户面网元根据所述特征信息确定所述应用的数据包对应的帧类型；
    所述用户面网元，用于根据所述应用的特征信息确定所述应用的的数据包对应的帧类型。
  34. 根据权利要求33所述的系统，其特征在于，所述系统还包括应用功能网元，所述应用功能网元用于向所述会话管理网元发送所述应用的特征信息。
  35. 一种通信装置，其特征在于，包括用于执行如权利要求1至10中任一项或权利要求11至19中任一项或权利要求20至24中任一项或权利要求25至29中任一项所述方法的各个步骤的模块。
PCT/CN2022/102224 2021-07-13 2022-06-29 通信方法、装置和系统 WO2023284551A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22841189.8A EP4354948A1 (en) 2021-07-13 2022-06-29 Communication method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110790888.3 2021-07-13
CN202110790888.3A CN115623542A (zh) 2021-07-13 2021-07-13 通信方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2023284551A1 true WO2023284551A1 (zh) 2023-01-19

Family

ID=84854525

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/102224 WO2023284551A1 (zh) 2021-07-13 2022-06-29 通信方法、装置和系统

Country Status (3)

Country Link
EP (1) EP4354948A1 (zh)
CN (1) CN115623542A (zh)
WO (1) WO2023284551A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116709212B (zh) * 2023-08-09 2023-11-14 腾讯科技（深圳）有限公司 数据传输方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188747A (zh) * 2007-12-10 2008-05-28 上海华为技术有限公司 在无线通信系统中实现视频业务的方法及网元设备
WO2017190329A1 (zh) * 2016-05-05 2017-11-09 华为技术有限公司 视频业务的传输方法和装置
US20170332282A1 (en) * 2016-05-13 2017-11-16 Huawei Technologies Co., Ltd. Method and system for providing guaranteed quality of service and quality of experience channel
CN113079541A (zh) * 2020-01-06 2021-07-06 华为技术有限公司 一种报告信息的发送方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188747A (zh) * 2007-12-10 2008-05-28 上海华为技术有限公司 在无线通信系统中实现视频业务的方法及网元设备
WO2017190329A1 (zh) * 2016-05-05 2017-11-09 华为技术有限公司 视频业务的传输方法和装置
US20170332282A1 (en) * 2016-05-13 2017-11-16 Huawei Technologies Co., Ltd. Method and system for providing guaranteed quality of service and quality of experience channel
CN113079541A (zh) * 2020-01-06 2021-07-06 华为技术有限公司 一种报告信息的发送方法、装置及系统

Also Published As

Publication number Publication date
EP4354948A1 (en) 2024-04-17
CN115623542A (zh) 2023-01-17

Similar Documents

Publication Publication Date Title
US10973000B2 (en) Message sending method and apparatus
AU2019249989B2 (en) Message transmission method, apparatus and system
US20220256393A1 (en) TSN AND 5GS QoS MAPPING - A USER PLANE BASED METHOD
US11968565B2 (en) User plane information reporting method and apparatus
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
EP4221005A1 (en) Multipath transmission method and communication apparatus
WO2021135650A1 (zh) 通信方法及装置
CN113746585A (zh) 授时方法和通信装置
US20220408317A1 (en) Handover method and communication apparatus
CN113973322A (zh) 一种通信方法及装置
WO2023284551A1 (zh) 通信方法、装置和系统
WO2023088009A1 (zh) 一种数据传输的方法及通信装置
US20230050923A1 (en) Media packet transmission method, apparatus, and system
WO2020125237A1 (zh) 一种通信方法及通信装置
WO2023029894A1 (zh) 测量网络状态的方法和装置
WO2022267652A1 (zh) 一种通信方法、通信装置及通信系统
CN114424498B (zh) 数据传输方法、装置、系统和存储介质
CN116723582A (zh) 通信方法和装置
WO2024067194A1 (zh) 通信方法、通信装置、以及通信系统
EP4325929A1 (en) Wireless communication method, communication apparatus and communication system
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2023016298A1 (zh) 一种业务感知方法、通信装置及通信系统
CN112135329B (zh) 参数传输方法、装置及系统
WO2024055692A1 (zh) 通信方法、通信装置和通信系统
WO2023050828A1 (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: 22841189

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022841189

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022841189

Country of ref document: EP

Effective date: 20240110

NENP Non-entry into the national phase

Ref country code: DE