WO2022147727A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022147727A1
WO2022147727A1 PCT/CN2021/070710 CN2021070710W WO2022147727A1 WO 2022147727 A1 WO2022147727 A1 WO 2022147727A1 CN 2021070710 W CN2021070710 W CN 2021070710W WO 2022147727 A1 WO2022147727 A1 WO 2022147727A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
type
qos
qos flow
indication information
Prior art date
Application number
PCT/CN2021/070710
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 PCT/CN2021/070710 priority Critical patent/WO2022147727A1/zh
Priority to EP21916785.5A priority patent/EP4262314A4/en
Priority to CN202180089087.2A priority patent/CN116746264A/zh
Publication of WO2022147727A1 publication Critical patent/WO2022147727A1/zh
Priority to US18/347,950 priority patent/US20230354334A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a communication method and device.
  • encoding modes for video such as hierarchical encoding mode and non-hierarchical encoding mode.
  • this method combines a basic layer (basic layer, BL) and several enhancement layers (extend layer, EL) into a multi-layer video system, the basic layer provides the code stream of basic image quality, and the enhancement layer provides A codestream with higher image quality can be constructed on the basis of the basic image quality.
  • the present application provides a communication method and apparatus for performing differential scheduling on different types of data packets.
  • an embodiment of the present application provides a communication method, which is used to implement a function on a network device side.
  • the method may be applied to an access network device or a chip in an access network device, and the embodiment of the present application is not limited to The specific execution body of this method.
  • the access network device receives configuration information of a first QoS flow from a first core network device, and the configuration information of the first QoS flow includes the first QoS flow.
  • the QoS parameters of a QoS flow wherein, the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types respectively; the first data packet of the first QoS flow of the device; and performing downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the access network device can use the corresponding QoS parameters according to the type of the data packets.
  • the QoS parameters are used to perform downlink scheduling on the data packets, so as to realize differentiated scheduling of different types of data packets in the same QoS flow, and improve the service experience of users.
  • the method further includes: receiving first indication information from the second core network device, where the first indication information indicates a type to which the first data packet belongs.
  • the first data packet and the first indication information are carried in a second data packet from the second core network device, and the first indication information is carried in the second data packet in the header of the package.
  • the method further includes: mapping the first data packet to the type corresponding to the type of the first data packet according to the correspondence between the type to which the first data packet belongs and the logical channel logical channel.
  • the access network device can map different types of data packets to corresponding logical channels for transmission, thereby effectively meeting the transmission requirements of different types of data packets.
  • the QoS parameters corresponding to the first type indicate that the transmission reliability requirements of the first type of data packets are higher
  • the QoS parameters corresponding to the second type indicate that the transmission reliability requirements of the second type of data packets are lower
  • the first type Types can be duplicated/retransmitted on multiple logical channels, and the second type can be transmitted on a single logical channel.
  • the number of logical channels corresponding to the first type can be greater than the number of logical channels corresponding to the second type .
  • the multiple types include a first type
  • the QoS parameter corresponding to the first type includes at least one of the following: first information, where the first information is used to indicate the first type Whether the data packets of the first type are allowed to be discarded; second information, the second information is used to indicate the number of data packets of the first type that are allowed to be discarded within a set time.
  • the embodiments of the present application provide a communication method, which is used to implement functions on the network device side.
  • the method may be applied to a CU or a chip in the CU, and the embodiments of the present application do not limit the specific execution of the method. main body.
  • the CU receives the configuration information of the first QoS flow from the first core network device, and the configuration information of the first QoS flow includes the QoS parameters of the first QoS flow.
  • the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types respectively; and, sending the first QoS flow corresponding to the DU
  • the configuration information of the DRB includes the QoS parameters corresponding to the multiple types respectively.
  • the CU can send QoS parameters corresponding to multiple types to the DU, so that after receiving the data packet, the DU can use the corresponding QoS parameters to perform downlink scheduling on the data packet according to the type of the data packet, so as to achieve Differentiated scheduling of different types of packets in the same QoS flow.
  • the method further includes: receiving a first data packet of the first QoS flow from a second core network device; sending the first data packet and second indication information to the DU , and the second indication information indicates the type to which the first data packet belongs.
  • sending the first data packet and the second indication information to the DU includes: sending a third data packet to the DU, where the third data packet includes the first data packet The data packet and the second indication information, where the second indication information is carried in the header of the third data packet.
  • the method further includes: sending third indication information to the DU, where the third indication information indicates the number of downlink tunnel addresses corresponding to the multiple types respectively; The first message of the DU, where the first message includes downlink tunnel addresses corresponding to the multiple types respectively.
  • the third indication information indicates the number of downlink tunnel addresses corresponding to the multiple types, which may also be replaced by the third indication information indicating the number of logical channels corresponding to the multiple types.
  • the CU can configure the number of logical channels corresponding to different types of data packets, so that the transmission requirements of different types of data packets can be effectively met.
  • the QoS parameters corresponding to the first type indicate that the transmission reliability requirements of the first type of data packets are higher
  • the QoS parameters corresponding to the second type indicate that the transmission reliability requirements of the second type of data packets are lower
  • the first type Types can be duplicated/retransmitted on multiple logical channels, and the second type can be transmitted on a single logical channel.
  • the number of logical channels corresponding to the first type can be greater than the number of logical channels corresponding to the second type .
  • the downlink tunnel address is the downlink tunnel address corresponding to the type to which the first data packet belongs.
  • the embodiments of the present application provide a communication method, which is used to implement functions on the network device side.
  • the method can be applied to a DU or a chip in a DU, and the embodiments of the present application are not limited to the specific execution of the method. main body.
  • the DU receives the configuration information of the DRB from the CU, the DRB corresponds to the first QoS flow, the first QoS flow supports multiple types of data packets, the DRB
  • the configuration information includes the QoS parameters corresponding to the various types; receiving the first data packet from the CU; according to the QoS parameters corresponding to the type to which the first data packet belongs, downlink the first data packet schedule.
  • the method further includes: receiving second indication information from the CU, where the second indication information indicates a type to which the first data packet belongs.
  • the first data packet and the second indication information are carried in a third data packet from the CU, and the second indication information is carried in a header of the third data packet .
  • the method further includes: receiving third indication information from the CU, where the third indication information indicates the number of downlink tunnel addresses corresponding to the multiple types respectively;
  • the CU sends a first message, where the first message includes downlink tunnel addresses corresponding to the multiple types respectively.
  • receiving the first data packet from the CU includes: receiving the first data packet from the CU through a first tunnel, where the downlink tunnel address of the first tunnel is the first data packet The downlink tunnel address corresponding to the type it belongs to.
  • an embodiment of the present application provides a communication method, and the method is used to implement a function on a network device side.
  • the method can be applied to a first core network device or a chip in the first core network device.
  • the embodiment of the present application The specific execution body of the method is not limited.
  • the first core network device determines the configuration information of the first QoS flow, and sends the configuration information of the first QoS flow to the access network device or the CU , the configuration information of the first QoS flow includes QoS parameters of the first QoS flow; wherein, the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include the multiple types of data packets. QoS parameters corresponding to each type.
  • an embodiment of the present application provides a communication method, and the method is used to implement a function on a network device side.
  • the method can be applied to a second core network device or a chip in a second core network device.
  • the embodiment of the present application The specific execution body of the method is not limited. Taking the method applied to the second core network device as an example, in this method, the second core network device receives the first data packet from the application server; sends the first data packet and the indication information to the access network device or the CU , and the indication information indicates the type to which the first data packet belongs.
  • sending the first data packet and the first indication information to the access network device or CU includes: sending a second data packet to the access network device or CU, where the second data packet includes The first data packet and the first indication information, where the first indication information is carried in the header of the second data packet.
  • an embodiment of the present application provides a communication device, where the communication device may be an access network device or a chip that can be provided inside the access network device.
  • the communication device has the function of implementing the first aspect.
  • the communication device includes modules or units or means (means) corresponding to the steps involved in executing the first aspect, and the functions, units or means may be implemented by software. , or implemented by hardware, or by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit may include a receiving unit and/or a sending unit, and the communication unit may be used to send and receive signals, so as to realize the communication between the communication device and other devices.
  • the processing unit may be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the first aspect above.
  • the communication apparatus includes a processor, and may also include a transceiver, where the transceiver is used for transmitting and receiving signals, and the processor utilizes the transceiver to complete any possible implementation of the first aspect above.
  • the communication apparatus may further include one or more memories, where the memories are configured to be coupled with the processor, and the memories may store computer programs or instructions for implementing the functions involved in the first aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation of the first aspect.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store computer programs or instructions that implement the functions involved in the first aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the first aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the first aspect above .
  • an embodiment of the present application provides a communication device, where the communication device may be a CU or a chip that can be provided inside the CU.
  • the communication device has the function of implementing the second aspect.
  • the communication device includes modules or units or means corresponding to the operations involved in the second aspect.
  • the modules, units, or means may be implemented by software, or by It can be realized by hardware, and can also be realized by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit can be used to send and receive signals to implement communication between the communication device and other devices, for example, the communication unit is used to receive data from Uplink information of the terminal equipment; the processing unit can be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the second aspect above.
  • the communication apparatus includes a processor, and may further include a transceiver, where the transceiver is used for transmitting and receiving signals, and the processor utilizes the transceiver to accomplish any possible implementation of the second aspect above.
  • the communication apparatus may further include one or more memories, where the memories are configured to be coupled with the processor, and the memories may store computer programs or instructions for implementing the functions involved in the second aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the second aspect.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store computer programs or instructions for implementing the functions involved in the second aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the second aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the second aspect above .
  • an embodiment of the present application provides a communication device, where the communication device may be a DU or a chip that can be provided inside the DU.
  • the communication device has the function of implementing the third aspect.
  • the communication device includes modules or units or means (means) corresponding to the steps involved in the execution of the third aspect, and the functions or units or means may be implemented by software. , or implemented by hardware, or by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit includes a receiving unit and/or a sending unit, and the communication unit can be used to send and receive signals to realize communication between the communication device and other devices communication; the processing unit may be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the third aspect.
  • the communication apparatus includes a processor, and may also include a transceiver, where the transceiver is used for transmitting and receiving signals, and the processor utilizes the transceiver to complete any possible implementation of the third aspect above.
  • the communication apparatus may further include one or more memories, where the memories are configured to be coupled with the processor, and the memories may store computer programs or instructions for implementing the functions involved in the third aspect above.
  • the processor can execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the third aspect.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store computer programs or instructions that implement the functions involved in the third aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the third aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the third aspect above .
  • an embodiment of the present application provides a communication device, where the communication device may be a first core network device or a chip that can be disposed inside the first core network device.
  • the communication device has the function of implementing the fourth aspect.
  • the communication device includes modules or units or means corresponding to the operations involved in the fourth aspect.
  • the modules, units, or means can be implemented by software, or by It can be realized by hardware, and can also be realized by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit may include a receiving unit and/or a sending unit, and the communication unit may be used to send and receive signals, so as to realize the communication between the communication device and other devices.
  • the processing unit may be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the fourth aspect above.
  • the communication device includes a processor, and may also include a transceiver, where the transceiver is used for transmitting and receiving signals, and the processor utilizes the transceiver to complete any possible implementation of the fourth aspect above.
  • the communication apparatus may further include one or more memories, where the memories are used for coupling with the processor, and the memories may store computer programs or instructions for implementing the functions involved in the fourth aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the fourth aspect.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store computer programs or instructions for implementing the functions involved in the fourth aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the fourth aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the fourth aspect above .
  • an embodiment of the present application provides a communication device, where the communication device may be a second core network device or a chip that can be disposed inside the second core network device.
  • the communication device has the function of implementing the fifth aspect.
  • the communication device includes modules or units or means corresponding to the steps involved in the fifth aspect, and the functions, units or means can be implemented by software. , or implemented by hardware, or by executing corresponding software by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit may include a receiving unit and/or a sending unit, and the communication unit may be used to send and receive signals, so as to realize the communication between the communication device and other devices.
  • the processing unit may be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit may correspond to the operations involved in the fifth aspect.
  • the communication apparatus includes a processor, and may further include a transceiver, where the transceiver is used for transmitting and receiving signals, and the processor utilizes the transceiver to perform any possible implementation of the fifth aspect above.
  • the communication device may further include one or more memories, where the memories are used for coupling with the processor, and the memories may store computer programs or instructions for implementing the functions involved in the fifth aspect.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the fifth aspect.
  • the communication device includes a processor, which may be operative to couple with the memory.
  • the memory may store computer programs or instructions that implement the functions involved in the fifth aspect above.
  • the processor may execute computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the fifth aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices through the interface circuit, and execute the method in any possible design or implementation of the fifth aspect above .
  • the processor may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a logic circuit or an integrated circuit.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory.
  • the above processors may be one or more, and the memory may be one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor. In a specific implementation process, the memory and the processor may be integrated on the same chip, or may be separately provided on different chips.
  • the embodiment of the present application does not limit the type of the memory and the manner of setting the memory and the processor.
  • an embodiment of the present application provides a communication system, where the communication system includes the communication device according to the sixth aspect, the communication device according to the ninth aspect, and the communication device according to the tenth aspect.
  • an embodiment of the present application provides a communication system, where the communication system includes the communication device according to the seventh aspect and the communication device according to the eighth aspect.
  • the communication device according to the ninth aspect and the communication device according to the tenth aspect may also be included.
  • an embodiment of the present application provides a computer-readable storage medium, where computer-readable instructions are stored in the computer storage medium, and when a computer reads and executes the computer-readable instructions, the computer is made to execute the above-mentioned first The method in any one possible design of the one aspect to the fifth aspect.
  • an embodiment of the present application provides a computer program product, which, when a computer reads and executes the computer program product, causes the computer to execute the method in any possible design of the first aspect to the fifth aspect. .
  • an embodiment of the present application provides a chip, where the chip includes a processor, and the processor is coupled to a memory and configured to read and execute a software program stored in the memory, so as to implement the above-mentioned first aspect
  • the method in any possible design to the fifth aspect.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applicable;
  • FIG. 2a is a schematic diagram of a protocol layer structure between a terminal device and an access network device provided by an embodiment of the present application;
  • FIG. 2b is a schematic diagram of a CU-DU separation architecture provided by an embodiment of the present application.
  • FIG. 2c is a schematic diagram of another CU-DU separation architecture provided by an embodiment of the present application.
  • FIG. 2d is a schematic diagram of the distribution of an air interface protocol stack provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of a QoS model in a 5G communication system
  • FIG. 5 is a schematic flowchart corresponding to the communication method provided in Embodiment 1 of the present application.
  • FIG. 6 is a schematic flowchart corresponding to the communication method provided in Embodiment 2 of the present application.
  • FIG. 7 is a schematic flowchart corresponding to the communication method provided in Embodiment 3 of the present application.
  • FIG. 8 is a possible exemplary block diagram of the apparatus involved in the embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an access network device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied.
  • a terminal device can access a wireless network to obtain services from an external network (such as a data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as with other terminals device communication.
  • the wireless network includes a (radio) access network ((R)AN) and a core network (CN), wherein the (R)AN (hereinafter referred to as RAN) is used to connect terminal devices to Access to the wireless network, the CN is used to manage the terminal equipment and provide a gateway for communication with the DN.
  • R radio access network
  • CN core network
  • the terminal equipment, RAN, CN, and DN involved in FIG. 1 are respectively described in detail below.
  • Terminal devices include devices that provide voice and/or data connectivity to users, and may include, for example, handheld devices with wireless connectivity, or processing devices connected to a wireless modem.
  • the terminal equipment may communicate with the core network via the radio access network, and the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, and device-to-device (D2D) communication.
  • Terminal equipment vehicle to everything (V2X) terminal equipment, machine-to-machine/machine-type communications (M2M/MTC) terminal equipment, internet of things (IoT) ) terminal equipment, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user equipment, etc.
  • V2X vehicle to everything
  • M2M/MTC machine-to-machine/machine-type communications
  • IoT internet of things
  • these may include mobile telephones (or "cellular" telephones), computers with mobile terminal equipment, portable, pocket-sized, hand-held, computer-embedded mobile devices, and the like.
  • mobile telephones or "cellular” telephones
  • PCS personal communication service
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistants
  • devices such as devices with lower power consumption, or devices with limited storage capabilities, or devices with limited computing capabilities, etc.
  • the RAN may include one or more RAN devices (or access network devices), and the interface between the access network device and the terminal device may be a Uu interface (or called an air interface).
  • RAN devices or access network devices
  • Uu interface or called an air interface
  • An access network device is a node or device that accesses a terminal device to a wireless network.
  • An access network device includes, but is not limited to, a new generation base station (gNB), an evolved node B ( evolved node B (eNB), next generation eNB (ng-eNB), wireless backhaul equipment, 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 ((home evolved nodeB, HeNB) or (home node B, HNB)), baseband unit (baseBand unit, BBU), Transmission and receiving point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
  • gNB new generation base station
  • eNB evolved node B
  • ng-eNB next generation eNB
  • RNC radio network controller
  • node B node B
  • base station Controller base station controller
  • BTS
  • the control plane protocol layer structure may include a radio resource control (radio resource control, RRC) layer, a packet data convergence layer protocol (packet data convergence protocol, PDCP) ) layer, radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical layer;
  • the user plane protocol layer structure may include PDCP layer, RLC layer, MAC layer and physical layer , in a possible implementation, a service data adaptation (service data adaptation protocol, SDAP) layer may also be included above the PDCP layer.
  • the data transmission needs to go through the user plane protocol layer, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer, among which SDAP layer, PDCP layer,
  • the RLC layer, the MAC layer, and the physical layer may also be collectively referred to as the access layer.
  • data is transmitted between the access network device and the terminal device by establishing at least one data radio bearer (DRB), and each DRB may correspond to a set of functional entities, such as including a PDCP layer entity, the At least one RLC layer entity corresponding to the PDCP layer entity, at least one MAC layer entity corresponding to the at least one RLC layer entity, and at least one physical layer entity corresponding to the at least one MAC layer entity.
  • DRB and SRB can be collectively referred to as radio bearer (RB) .
  • FIG. 2a is a schematic diagram of downlink data transmission between layers.
  • the downward arrow in FIG. 2a indicates data transmission, and the upward arrow indicates data reception.
  • the SDAP layer entity obtains the data from the upper layer, it can map the data to the PDCP layer entity of the corresponding DRB according to the QoS flow indicator (QFI) of the data, and the PDCP layer entity can transmit the data to at least one corresponding to the PDCP layer entity.
  • QFI QoS flow indicator
  • One RLC layer entity is further transmitted by at least one RLC layer entity to the corresponding MAC layer entity, and then the MAC layer entity generates a transport block, and then performs wireless transmission through the corresponding physical layer entity.
  • the data is encapsulated correspondingly in each layer.
  • the data received by a certain layer from the upper layer of the layer is regarded as the service data unit (SDU) of the layer, and becomes the protocol data unit (protocol data unit) after layer encapsulation. unit, PDU), and then passed to the next layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data received by the PDCP layer entity from the upper layer is called PDCP SDU
  • the data sent by the PDCP layer entity to the lower layer is called PDCP PDU
  • the data received by the RLC layer entity from the upper layer is called RLC SDU
  • the data sent by the RLC layer entity to the lower layer Called RLC PDU can be transmitted between different layers through corresponding channels.
  • data can be transmitted between the RLC layer entity and the MAC layer entity through a logical channel (LCH), and the MAC layer entity and the physical layer entity can be transmitted through the A transport channel to transmit data.
  • LCH logical channel
  • the terminal device also has an application layer and a non-access layer; wherein, the application layer can be used to provide services to applications installed in the terminal device, for example, the terminal device receives Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided by the application layer to the application program; for another example, the application layer can obtain the data generated by the application program, transmit the data to the physical layer in turn, and send it to other communication devices.
  • the non-access layer can be used for forwarding user data, for example, forwarding the uplink data received from the application layer to the SDAP layer or forwarding the downlink data received from the SDAP layer to the application layer.
  • the access network device may include one or more centralized units (centralized units, CUs) and one or more distributed units (distributed units, DUs), and multiple DUs may be centrally controlled by one CU.
  • the interface between the CU and the DU may be referred to as an F1 interface, wherein the control panel (CP) interface may be F1-C, and the user panel (UP) interface may be F1-U.
  • CP control panel
  • UP user panel
  • the CU and DU can be divided according to the protocol layer of the wireless network: for example, as shown in Figure 2b, the functions of the PDCP layer and the above protocol layers are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and the MAC layer, etc.) are set in the DU.
  • the above division of the processing functions of CU and DU according to the protocol layer is only an example, and can also be divided in other ways, for example, the functions of the protocol layer above the RLC layer are set in the CU, and the RLC layer and the following protocol layers.
  • the function of the CU is set in the DU.
  • the CU or DU can be divided into functions with more protocol layers.
  • the CU or DU can also be divided into partial processing functions with protocol layers. In one design, some functions of the RLC layer and functions of the protocol layers above the RLC layer are placed in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are placed in the DU.
  • the functions of the CU or DU can also be divided according to the service type or other system requirements, for example, by the delay, the functions whose processing time needs to meet the delay requirements are set in the DU, and do not need to meet the delay.
  • the required functionality is set in the CU.
  • the CU may also have one or more functions of the core network.
  • the CU can be set on the network side to facilitate centralized management; the DU can have multiple radio functions, or the radio functions can be set remotely. This embodiment of the present application does not limit this.
  • the functions of the CU may be implemented by one entity, or may also be implemented by different entities.
  • the functions of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (ie the CU-CP entity) and the user plane CU entity. (ie the CU-UP entity), the CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN device.
  • the interface between the CU-CP entity and the CU-UP entity may be the E1 interface
  • the interface between the CU-CP entity and the DU may be the F1-C interface
  • the interface between the CU-UP entity and the DU may be the F1-U interface interface.
  • one DU and one CU-UP can be connected to one CU-CP.
  • one DU can be connected to multiple CU-UPs
  • one CU-UP can be connected to multiple DUs.
  • FIG. 2d is a schematic diagram of the distribution of an air interface protocol stack.
  • the air interface protocol stack may be RLC, MAC, and PHY in the DU, and PDCP and above protocol layers in the CU.
  • the signaling generated by the CU may be sent to the terminal device through the DU, or the signaling generated by the terminal device may be sent to the CU through the DU.
  • the DU may not parse the signaling, but directly encapsulate it through the protocol layer and transparently transmit it to the terminal device or CU.
  • the sending or receiving of the signaling by the DU includes this scenario.
  • the signaling of the RRC or PDCP layer will eventually be processed as the data of the physical layer and sent to the terminal device, or converted from the received data of the physical layer.
  • the signaling of the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the radio frequency device.
  • CN may include one or more CN devices. Taking 5G communication system as an example, CN may include access and mobility management function (AMF) network elements, session management function (SMF) ) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management (unified data management, UDM) network element, application function (application function, AF) ) network element, etc.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM unified data management
  • UDM application function
  • AF application function
  • the AMF network element is the control plane network element provided by the operator's network. It is responsible for the access control and mobility management of the terminal equipment accessing the operator's network, such as the management of mobility status, the allocation of user temporary identities, and the authentication and authorization of users. .
  • the SMF network element is the control plane network element provided by the operator's network and is responsible for managing the PDU sessions of the terminal equipment.
  • a PDU session is a channel for transmitting PDUs. Terminal devices need to communicate PDUs with the DN through the PDU session.
  • the PDU session is established, maintained and deleted by the SMF network element.
  • SMF network elements include session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), selection and control of UPF network elements, service and session continuity (SSC) mode selection, Session related functions such as roaming.
  • the UPF network element is the gateway provided by the operator, and is the gateway for the communication between the operator's network and the DN.
  • UPF network elements include user plane-related functions such as packet routing and transmission, packet detection, quality of service (QoS) processing, legal interception, upstream packet detection, and downstream packet storage.
  • QoS quality of service
  • the PCF network element is a control plane function provided by the operator, and is used to provide the policy of the PDU session to the SMF network element.
  • the policies may include charging-related policies, QoS-related policies, authorization-related policies, and the like.
  • the AF network element is a functional network element that provides various business services, can interact with the core network through other network elements, and can interact with the policy management framework for policy management.
  • network exposure function NEF
  • UDR network element unified data repository
  • the access network device and the core network device may be collectively referred to as network devices.
  • a DN can also be called a packet data network (PDN), which is a network outside the operator's network.
  • PDN packet data network
  • the operator's network can access multiple DNs.
  • Application servers corresponding to various services can be deployed in the DN.
  • the terminal equipment offers a variety of possible services.
  • Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers please refer to the meanings defined in the relevant standard protocols, which are not limited here.
  • a 5G communication system is used as an example for illustration in FIG. 1
  • the solutions in the embodiments of the present application may also be applied to other possible communication systems, such as an LTE communication system or a future sixth generation (the 6th generation) generation, 6G) communication system.
  • the above network elements or functions may be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the foregoing network element or function may be implemented by one device, or may be implemented jointly by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • data can be transmitted between the terminal device and the UPF network element through PDU sessions, and each PDU session can transmit multiple data streams with different QoS requirements, which are called QoS streams.
  • FIG. 3 is a schematic diagram of a QoS model in a 5G communication system.
  • the UPF network element filters the downlink data according to the packet filter sets (packet filter sets) in the packet detection rule (PDR) configured by the SMF network element.
  • the packets are distinguished into different QoS flows, and the data packets in the QoS flow are marked with the QoS flow indicator (QoS flow indicator, QFI).
  • QoS flow indicator QoS flow indicator
  • the access network device After receiving the data packet, the access network device determines the QoS flow to which the data belongs according to the QFI corresponding to the data packet, and then according to the QoS parameters of the QoS flow, Downlink data packets are transmitted on the air interface.
  • the access network device After the application layer of the terminal device obtains the data packets, it can distinguish the upstream data packets into different QoS flows according to the packet filtering set in the QoS rules configured by the SMF network element, and then transmit the upstream data packets on the air interface. . It should be noted that, in this embodiment of the present application, research is mainly conducted on related implementations in the downlink direction.
  • FIG. 4 is a schematic diagram of part of the process involved in the PDU session establishment process. Referring to FIG. 4, the process may include:
  • Step 401 the AF network element sends the QoS requirement information of the service (for example, service 1) to the PCF network element.
  • the service for example, service 1
  • the service 1 may be a VR service, an AR service, a high-definition video service, or a tactile Internet service, etc., which is not specifically limited.
  • Service 1 may include multiple data streams, such as video data streams, audio data streams, etc., and different data streams may have different QoS requirement information.
  • Step 402 the PCF network element receives the QoS requirement information of the service 1, and determines the QoS parameters corresponding to different data flows in the service 1 according to the QoS requirement information of the service 1.
  • Step 403 the PCF network element sends the QoS parameters corresponding to different data flows in the service 1 to the SMF network element.
  • the terminal device when the terminal device has the need to receive service 1, the terminal device can initiate a PDU session establishment process, and after receiving the PDU session establishment request from the terminal device, the SMF network element can send a request message to the PCF network element to request The message is used to obtain QoS parameters corresponding to different data flows in service 1, and then the PCF network element can send the QoS parameters corresponding to different data flows in service 1 to the SMF network element.
  • Step 404 the SMF network element determines the configuration information of each QoS flow in the one or more QoS flows included in the to-be-established PDU session and the packet filtering set corresponding to each QoS.
  • the configuration information of each QoS flow may include QoS parameters of each QoS flow. For example, if one or more QoS flows include a first QoS flow, and the first QoS flow is used to carry the video data flow in service 1, the QoS parameters of the first QoS flow are the QoS parameters corresponding to the video data flow.
  • Step 405 the SMF network element sends the packet filtering set corresponding to each QoS flow in the one or more QoS flows to be established in the PDU session to the UPF network element.
  • the UPF network element can distinguish the data packets into different QoS flows according to the packet filtering set corresponding to each QoS flow.
  • Step 406 the SMF network element sends a PDU session resource establishment request message to the access network device through the AMF network element, and the PDU session resource establishment request message includes the configuration of each QoS flow in the one or more QoS flows that need to be established in the PDU session. information.
  • the access network device can transmit downlink data packets on the air interface according to the QoS parameters of each QoS flow included in the configuration information of each QoS flow.
  • QoS flows may include guaranteed bit rate (guaranteed bit rate, GBR) QoS flows and non-guaranteed bit rate (non-guaranteed bit rate, Non-GBR) QoS flows.
  • GBR guaranteed bit rate
  • Non-GBR non-guaranteed bit rate
  • the services carried by the GBR QoS flow have strict requirements on delay or rate, and the transmission rate of the flow needs to be guaranteed, such as services such as session video; the services carried by the Non-GBR QoS flow have no rate requirements. High, no real-time rate guarantee is required, such as web browsing, file download and other services.
  • each GBR QoS flow can correspond to a set of QoS parameters, which can include 5G QoS identifier (5G QoS identifier, 5QI), guaranteed flow bit rate (guaranteed flow bit rate, GFBR), Maximum flow bit rate (MFBR).
  • 5G QoS identifier 5G QoS identifier, 5QI
  • guaranteed flow bit rate guaranteed flow bit rate
  • GFBR Guarantee flow bit rate
  • MFBR Maximum flow bit rate
  • GFBR represents the bit rate guaranteed by the network to the QoS flow over the average window
  • MFBR is used to limit the bit rate to the highest bit rate expected by the QoS flow (e.g. packets may be blocked by UE/RAN/UPF when MFBR is exceeded throw away).
  • the value of GFBR may be the same in uplink (UL) and downlink (downlink, DL), and the value of MFBR may also be the same in UL and DL.
  • 5QI is a scalar used to index to the corresponding 5G QoS feature.
  • 5QI is divided into standardized 5QI, pre-configured 5QI and dynamically allocated 5QI.
  • the standardized 5QI corresponds to a set of standardized 5G QoS features one-to-one; the 5G QoS feature values corresponding to the pre-configured 5QI can be pre-configured on the access network equipment; the 5G QoS features corresponding to the dynamically allocated 5QI are determined by the core network equipment Sent to the access network device.
  • Non-GBR QoS flow can use Non-GBR resource type.
  • GBR QoS flows can use either the GBR resource type or the latency-sensitive GBR resource type.
  • Priority level which indicates the resource scheduling priority between 5G QoS flows. This parameter is used to distinguish each QoS flow of a terminal device, and can also be used to distinguish the QoS flow of different terminal devices. The smaller the parameter value, the higher the priority.
  • PDB Packet delay budget
  • Packet error rate which defines an upper limit, that is, the data packet has been processed by the link layer (such as the RLC layer) of the sender, but has not been submitted to the upper layer by the corresponding receiver (such as PDCP layer) ratio upper limit.
  • the packet error rate can also be called the packet error rate, and the two are interchangeable. It should be noted that, for a GBR QoS flow using the delay-sensitive GBR resource type, if the data burst sent within the PDB period is less than the default maximum data burst and the QoS flow does not exceed the guaranteed flow bit rate, the delay is greater than the PDB. of packets are counted as lost.
  • the average window is defined for the GBR QoS flow, and is used for related network elements to count GFBR and MFBR.
  • MDBV Maximum data burst volume
  • the corresponding resource type is the delay-sensitive GBR
  • the priority level is 19
  • the PDB is 10ms
  • the PER is 10-4
  • the MDBV is 255 bytes.
  • the average window is 2000ms.
  • a video can be composed of consecutive images (or pictures, photos, etc.) that are played continuously. When 24 images are played rapidly in one second, the human eye will think that this is a continuous picture (ie, video).
  • Frame rate refers to the number of images played per second. For example, 24 frames means playing 24 images per second, 60 frames means playing 60 images per second, and so on.
  • a video frame can be understood as an image (that is, a video frame can include multiple data packets corresponding to an image). When the frame rate is 60 frames, the duration of a video frame is 1000ms/60Hz, which is approximately equal to 16ms.
  • Video encoding is to convert video files from one format to another, so as to compress video files for storage and transmission of video files.
  • video coding There are many ways of video coding, such as hierarchical coding and non-hierarchical coding.
  • the hierarchical coding mode may be based on time domain for hierarchical coding, or based on space for hierarchical coding, or based on quality for hierarchical coding, or based on any combination of time domain, space, and quality for hierarchical coding,
  • the video stream encoded in the hierarchical coding manner may include a base layer code stream and an enhancement layer code stream, and the base layer code stream and the enhancement layer code stream are separately decodable sub-code streams, and the enhancement layer code stream may Include one or more layers.
  • the base layer code stream can include the base layer data packet, which is a necessary condition for video playback.
  • the video quality is poor; while the enhancement layer code stream can include the enhancement layer data packet, the enhancement layer Data packets are supplementary conditions for video playback; for example, if the video quality corresponding to the base layer code stream is smooth, then the first enhancement layer code stream is superimposed on the base layer code stream to achieve SD image quality.
  • Superimposing the second enhancement layer code stream on the basis of high-definition image quality can achieve high-definition image quality, and superimposing the third enhancement layer code stream on the basis of high-definition image quality can achieve Blu-ray image quality. That is to say, the more code streams of the enhancement layer are superimposed on the base layer code stream, the better the video quality will be obtained after decoding.
  • two layers of the base layer and the enhancement layer are used as examples for description, that is, the enhancement layer involved in the embodiments of the present application may include one layer or may include multiple layers.
  • the video stream encoded in the non-hierarchical encoding manner may include I frames, P frames and B frames.
  • I frame also known as an intra-frame coded frame
  • P frame also known as inter-frame predictive coding frame
  • P frame needs to refer to the previous I frame for coding, which indicates the difference between the current frame and the previous frame (the previous frame may be an I frame or a P frame), which needs to be decoded.
  • B frame is also known as bidirectional predictive coding frame, that is, B frame records the difference between the current frame and the previous frame; that is to say, to decode B frame, not only the previous cached picture, but also the decoded picture must be obtained. The superposition of the picture and the data of this frame obtains the final picture.
  • each QoS flow corresponds to a set of QoS parameters, and for all data packets in the QoS flow, the access network equipment is based on the QoS parameters of the QoS flow.
  • the video data packets mapped to the same QoS stream may include different types of data packets (such as the base layer data packets and enhancement layer data packets, and the data packets corresponding to I frames, P frames, etc.) Corresponding data packets and data packets corresponding to B frames); since the QoS requirements of different types of data packets are different, if the access network equipment performs unified scheduling according to the QoS parameters of the QoS flow, it will cause the access network equipment It is impossible to accurately schedule each data packet, and cannot meet the QoS requirements of different types of data packets, which affects the user's service experience.
  • the embodiments of the present application provide a communication method for implementing differentiated scheduling of different types of data packets, so as to meet the QoS requirements of different types of data packets, thereby improving user service experience.
  • FIG. 5 is a schematic flowchart corresponding to the communication method provided in Embodiment 1 of the present application. As shown in FIG. 5 , the method includes the following steps:
  • the first core network device sends configuration information of the first QoS flow to the access network device, and correspondingly, the access network device may receive the configuration information of the first QoS flow.
  • the configuration information of the first QoS flow includes QoS parameters of the first QoS flow, the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types.
  • the first core network device may be an SMF network element and/or an AMF network element, and in this embodiment of the present application, the first core network device is an AMF network element as an example.
  • the AMF network element may send the configuration information of the first QoS flow to the access network device.
  • the AMF network element may send the first QoS to the access network device through a PDU session resource setup request (PDU session resource setup request) message or a PDU session resource modification request (PDU session resource modification request) message. Configuration information for the stream.
  • PDU session resource setup request PDU session resource setup request
  • PDU session resource modification request PDU session resource modification request
  • the terminal device when the terminal device has a demand for receiving downlink services, the terminal device can initiate a PDU session establishment process, and then trigger the AMF network element to send a PDU session resource establishment request message to the access network device.
  • the PDU session resource establishment request message may include the message to be established
  • the identifier of the PDU session and the configuration information of multiple QoS flows in the PDU session, wherein the multiple QoS flows may include the first QoS flow.
  • the terminal device needs to modify the first QoS flow in the established PDU session.
  • the terminal device can initiate a PDU session resource modification process, and then trigger the AMF network element to send a PDU session resource modification request to the access network device.
  • the PDU session resource modification request message may include configuration information of the first QoS flow.
  • the AMF network element may also send the configuration information of the first QoS flow to the access network device through other possible messages, which is not specifically limited.
  • the first QoS flow supports multiple types of data packets, that is, during data transmission, the first QoS flow transmitted by the UPF network element to the access network device may include at least one type of data among multiple types Bag.
  • multiple types of data packets may be divided based on multiple possible criteria.
  • multiple types of data packets may include base layer data packets and enhancement layer data packets (that is, two types of data packets); for another example, multiple types of data packets may include data packets corresponding to I frames, and data packets corresponding to P frames.
  • the basis for dividing and obtaining various types of data packets may not be limited, that is, as long as there are different types of data packets and the QoS parameters of the different types of data packets are different, the application of the present application may be adopted.
  • the configuration information of the first QoS flow may include QoS parameters of the first QoS flow, and optionally, may also include an identifier of the first QoS flow, and identifiers of multiple types of data packets supported by the first QoS flow.
  • the QoS parameters of the first QoS flow may include QoS parameters corresponding to multiple types respectively.
  • the multiple types of data packets supported by the first QoS flow include the first type, the second type and the third type
  • the QoS parameters of the first QoS flow may include a set of QoS parameters corresponding to the first type (called is the first QoS parameter), a group of QoS parameters corresponding to the second type (referred to as the second QoS parameter), and a group of QoS parameters corresponding to the third type (referred to as the third QoS parameter).
  • the configuration information of the first QoS flow may include an identifier of the first QoS flow, and as shown in Table 1, the correspondence between the identifiers of various types to which the data packets supported by the first QoS flow belong and the QoS parameters .
  • Table 1 Example of correspondence between type identifiers and QoS parameters
  • the first type of data packet may be a data packet corresponding to an I frame
  • the second type of data packet may be a data packet corresponding to a P frame
  • the third type of data packet may be a data packet corresponding to a B frame.
  • the identifier of the I frame may be information used to identify the I frame, which is not specifically limited.
  • the first QoS parameter may include at least one of the following: first information, where the first information is used to indicate whether the data packets of the first type are allowed to be discarded; the second information, and the second information is used to indicate the number of data packets of the first type that are allowed to be discarded within a set time.
  • first information where the first information is used to indicate whether the data packets of the first type are allowed to be discarded
  • second information and the second information is used to indicate the number of data packets of the first type that are allowed to be discarded within a set time.
  • the first QoS parameter may no longer include the second information, or the second information included in the first QoS parameter is used to indicate the first type
  • the number of data packets allowed to be dropped within the set time is 0.
  • the second information can be used to indicate that the number of data packets of the first type that are allowed to be discarded within the set time is n (n is greater than or equal to n). an integer of 0).
  • the set time may be a period of time pre-agreed in the agreement, or may also be a period of time indicated by the second information, which is not specifically limited.
  • the first QoS parameter may also include other possible information, such as 5QI, GFBR, MFBR, and the like.
  • the first QoS parameter and the second QoS parameter may be completely different, such as the first QoS parameter and the second QoS parameter.
  • the first information, second information, 5QI, GFBR, and MFBR included in a QoS parameter are completely different from the first information, second information, 5QI, GFBR, and MFBR included in the second QoS parameter.
  • the first QoS parameter may be partially different from the second QoS parameter, for example, the 5QI, GFBR, and MFBR included in the first QoS parameter are the same as the 5QI, GFBR, and MFBR included in the second QoS parameter, but the first QoS parameter includes the same 5QI, GFBR, and MFBR.
  • the included first information and second information are different from the first information and second information included in the second QoS parameter.
  • the AMF network element obtains the configuration information of the first QoS flow is described.
  • the AMF network element needs to obtain the configuration information of the first QoS flow first.
  • the AMF network element may obtain the configuration information of the first QoS flow from the SMF network element.
  • the SMF network element can obtain the QoS parameters corresponding to different data flows in the service 1 from the PCF network element.
  • the service 1 includes a video data flow
  • the video data flow includes various types of data packets
  • the QoS parameters corresponding to the video data flow It includes QoS parameters corresponding to various types.
  • the QoS parameters of the first QoS flow are the QoS parameters corresponding to the video data flow;
  • the AMF network element sends the configuration information of the first QoS flow. It should be noted that, in this embodiment of the present application, the specific implementation of the QoS parameters corresponding to different data flows in the PCF network element generation service 1 may not be limited.
  • the access network device may process the first QoS flow according to the configuration information of the first QoS flow.
  • the access network device processing the first QoS flow according to the configuration information of the first QoS flow may include: configuring the corresponding air interface resources for the first QoS flow by the access network device according to the configuration information of the first QoS flow. , for example, configure the DRB corresponding to the first QoS flow.
  • the access network device may configure the first QoS flow to correspond to the first DRB according to the configuration information of the first QoS flow, and the first DRB may be associated with multiple logical channels. Further, the access network device may also configure the correspondence between multiple types supported by the first QoS flow and multiple logical channels, where one type may correspond to one or more logical channels, or one logical channel may also correspond to Two or more types. For example, the multiple types supported by the first QoS flow include the first type, the second type, and the third type, and the multiple logical channels associated with the first DRB include the first logical channel, the second logical channel, and the third logical channel.
  • the access network device may configure the first type corresponding to the first logical channel and the second logical channel, the second type corresponding to the third logical channel, and the third type corresponding to the fourth logical channel.
  • the multiple logical channels may be used to transmit duplicate data packets.
  • the access network device may configure the correspondence between multiple types and multiple logical channels according to QoS parameters corresponding to multiple types.
  • the QoS parameters corresponding to the first type indicate that the transmission reliability requirements of the first type of data packets are higher
  • the QoS parameters corresponding to the second type indicate that the transmission reliability requirements of the second type of data packets are lower
  • the first type Types can be duplicated/retransmitted on multiple logical channels, and the second type can be transmitted on a single logical channel.
  • the number of logical channels corresponding to the first type can be greater than the number of logical channels corresponding to the second type .
  • the access network device can also map multiple types of data packets to the same logical channel for transmission. Subsequently, the access network device can perform downlink scheduling on different types of data packets at the MAC layer according to their corresponding QoS parameters.
  • the QoS parameters corresponding to the first type indicate that the first type has higher requirements for transmission reliability, and the MAC layer may
  • the data packets corresponding to the first type are transmitted using a lower-level modulation and coding scheme, or more resources are allocated for transmitting the data packets corresponding to the first type.
  • the second core network device sends the first data packet in the first QoS flow to the access network device, and accordingly, the access network device may receive the first data packet in the first QoS flow from the second core network device .
  • the second core network device may be a UPF network element, and after receiving the first data packet from the application server, the UPF network element may map the first data packet to the first QoS flow according to the packet filtering set (the first The data packet may be marked with an identifier of the first QoS flow), and then sent to the access network device.
  • the UPF network element may map the first data packet to the first QoS flow according to the packet filtering set (the first The data packet may be marked with an identifier of the first QoS flow), and then sent to the access network device.
  • the UPF network element may also send indication information 1 to the access network device, where the indication information 1 is used to indicate the type to which the first data packet belongs.
  • the indication information 1 may include an identifier of the type to which the first data packet belongs.
  • the UPF network element sends the second data packet to the access network device, and the second data packet includes the first data packet and the indication information.
  • Information 1, indicating that information 1 can be carried in the packet header of the second data packet.
  • the GTP-U protocol is a general packet radio service (GPRS) tunnel transmission.
  • GPRS general packet radio service
  • One of the protocols of the GPRS tunnel protocol (GTP) therefore, after the UPF network element receives the first data packet from the application server, it can encapsulate the first data packet according to the GTP-U protocol (for example, adding a GTP-U header ) to obtain a second data packet, the second data packet may be called a GTP-U data packet, and the indication information 1 may be carried in the GTP-U packet header.
  • the type to which the first data packet belongs may be determined first.
  • the UPF network element may determine the type of the first data packet.
  • the application server may indicate the type of the first data packet.
  • the UPF network element may The type to which the first data packet belongs is determined according to a preset rule, which is not specifically limited.
  • the access network device performs downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the access network device if the access network device is configured with the correspondence between multiple types supported by the first QoS flow and multiple logical channels, the access network device, according to the QoS parameter corresponding to the type to which the first data packet belongs, will Before the data packet is scheduled for downlink, the first data packet may be mapped to the first DRB corresponding to the first QoS flow according to the identifier of the first QoS flow marked by the first data packet, and then according to the type to which the first data packet belongs, The first data packet is mapped to the logical channel corresponding to the first type.
  • the access network device performs downlink scheduling on the first data packet according to QoS parameters corresponding to the type to which the first data packet belongs, which may include: the access network device according to the type corresponding to the first data packet. QoS parameters, send the first data packet to the terminal device; or, the access network device discards the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the type to which the first data packet belongs is the first type
  • the first type corresponds to the first QoS parameter
  • the first information in the first QoS parameter indicates that the data packet of the first type is allowed to be discarded. If the access network device determines that it meets at least one of the following situations 1 and 2, it can discard the first data packet; if it determines that it does not meet the situations 1 and 2, it can send the first data packet to the terminal device.
  • Scenario 1 is: the access network equipment is heavily loaded, for example, the number of terminal equipment served by the access network equipment is greater than or equal to the number threshold, and for example, the resource utilization rate of the access network equipment is greater than or equal to the resource utilization rate threshold ;
  • the quantity threshold and resource usage threshold can be set according to the actual situation, which is not specifically limited.
  • Scenario 2 The access network device determines, according to the PDB of the first data packet, that the first data packet exceeds the transmission delay requirement.
  • the access network device needs to satisfy this requirement when determining whether to discard the first data packet. Restriction, that is, if the number of discarded data packets within the set time is greater than or equal to the allowed discarded number, the first data packet may not be discarded, and the first data packet may be sent to the terminal device.
  • the access network device can use the corresponding QoS parameters according to the type of the data packets.
  • the QoS parameters are used to perform downlink scheduling on the data packets, so as to implement differentiated scheduling of different types of data packets in the same QoS flow.
  • the access network device is described as a whole device. In some possible situations, the access network device may also include separate nodes, such as CU and DU, as shown in FIG. 2b.
  • FIG. 6 is a schematic flowchart corresponding to the communication method provided in Embodiment 2 of the present application. As shown in FIG. 6 , the method includes the following steps:
  • the first core network device sends configuration information of the first QoS flow to the CU, and accordingly, the CU may receive the configuration information of the first QoS flow.
  • the configuration information of the first QoS flow includes QoS parameters of the first QoS flow
  • the first QoS flow supports multiple types of data packets
  • the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types.
  • the CU may process the first QoS flow according to the configuration information of the first QoS flow.
  • the CU processing the first QoS flow according to the configuration information of the first QoS flow may include, the CU configures corresponding air interface resources for the first QoS flow according to the configuration information of the first QoS flow, such as configuring the first QoS flow.
  • the CU sends the configuration information of the DRB corresponding to the first QoS flow to the DU, and accordingly, the DU may receive the configuration information of the DRB corresponding to the first QoS flow.
  • the configuration information of the DRB includes QoS parameters corresponding to various types respectively.
  • the configuration information of the DRB may include the correspondence between various types of identifiers and QoS parameters, as shown in Table 1, for example.
  • the second core network device sends the first data packet in the first QoS flow to the CU, and accordingly, the CU may receive the first data packet in the first QoS flow from the second core network device.
  • the CU sends the first data packet and the indication information 2 to the DU, and accordingly, the DU may receive the first data packet and the indication information 2.
  • the CU may send the first data packet and the indication information 2 to the DU.
  • the CU sends a third data packet to the DU, where the third data packet may include the first data packet and indication information 2, and the indication information 2 may be carried in a header of the third data packet.
  • the third data packet may be a GTP-U data packet, and the indication information 2 may be carried in a GTP-U header of the third data packet.
  • the DU performs downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the DU performs downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs, for the implementation of the downlink scheduling of the first data packet, please refer to the corresponding implementation of the access network device according to the type of the first data packet in the above-mentioned first embodiment.
  • the QoS parameter is a description of the downlink scheduling for the first data packet, which is not repeated here.
  • the CU can send QoS parameters corresponding to multiple types to the DU, so that after receiving the data packet, the DU can use the corresponding QoS parameters to perform downlink scheduling on the data packet according to the type of the data packet, so as to achieve Differentiated scheduling of different types of data packets in the same QoS flow.
  • FIG. 7 is a schematic flowchart corresponding to the communication method provided in Embodiment 3 of the present application. As shown in FIG. 7 , the method includes the following steps:
  • the first core network device sends configuration information of the first QoS flow to the CU, and accordingly, the CU receives the configuration information of the first QoS flow.
  • the configuration information of the first QoS flow includes QoS parameters of the first QoS flow
  • the first QoS flow supports multiple types of data packets
  • the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types.
  • the CU may process the first QoS flow according to the configuration information of the first QoS flow.
  • the CU processing the first QoS flow according to the configuration information of the first QoS flow may include, the CU configures corresponding air interface resources for the first QoS flow according to the configuration information of the first QoS flow, such as configuring the first QoS flow.
  • the CU sends the configuration information of the DRB corresponding to the first QoS flow to the DU, and accordingly, the DU receives the configuration information of the DRB corresponding to the first QoS flow.
  • the configuration information of the DRB includes QoS parameters corresponding to the various types, and optionally, indication information 3, which indicates the number of downlink tunnel addresses corresponding to the various types.
  • the DU sends a first message to the CU, where the first message includes downlink tunnel addresses corresponding to multiple types respectively.
  • one or more tunnels may be established between the CU and the DU, and the tunnel is used to transmit the data packets of the PDCP layer of the CU to the RLC entity of the DU (which can be understood as downlink transmission), and or, transmit the data packet received by the RLC entity of the DU to the PDCP entity of the CU (which can be understood as uplink transmission).
  • Each tunnel may include an uplink tunnel address and a downlink tunnel address, the uplink tunnel address refers to the address of the tunnel on the CU side, and the downlink tunnel address refers to the address of the tunnel on the DU side.
  • the indication information 3 indicates the number of downlink tunnel addresses corresponding to the various types, and can also be replaced with other possible descriptions. For example, the indication information 3 indicates the number of downlink tunnel addresses corresponding to multiple types, which may be replaced by the indication information 3 to indicate whether multiple types of data packets need to be repeatedly transmitted. In addition, when the indication information 3 indicates that a certain type of data packet needs to be repeatedly transmitted, the number of times of repeated transmission may be further indicated.
  • the indication information 3 indicates that the data packets of the first type do not need to be repeatedly transmitted, it means that the number of downlink tunnel addresses corresponding to the first type is 1; if the indication information 3 indicates that the data packets of the first type are 1 If the packet needs to be repeatedly transmitted, and the number of times of repeated transmission is k, it means that the number of downlink tunnel addresses corresponding to the first type is k.
  • the indication information 3 indicates the number of downlink tunnel addresses corresponding to the various types, which may be replaced by the indication information 3 indicating the number of logical channels corresponding to the various types.
  • each downlink tunnel address may correspond to a logical channel, wherein the corresponding relationship between the downlink tunnel address and the logical channel may be determined by the DU.
  • the DU may send the correspondence between the downlink tunnel address and the logical channel to the CU; or, the DU may also separately send the identifier of the logical channel corresponding to the first type and/or the configuration information of the logical channel to the CU; and Alternatively, the DU may also only send the identifier of the primary logical channel and/or the configuration information of the primary logical channel in the logical channel corresponding to the first type to the CU, so that the CU can use the relevant information to generate an RRC message and send it to the terminal device , so that the terminal device can obtain relevant information to receive the first type of data packets.
  • the above-mentioned repeated transmission may refer to the repeated transmission of the PDCP layer.
  • the data packets are copied into multiple identical data packets (that is, repeated packets) at the PDCP layer, and then the multiple data packets are respectively submitted to the Multiple different RLC layer entities perform transmission, and then transmit to MAC layer entities through different logical channels.
  • the commonly referred to retransmission refers to retransmission (retransmission)
  • the duplication transmission (duplication transmission) in this embodiment of the present application does not mean retransmission.
  • Retransmission refers to the retransmission of the same data packet after the failure to send it, or the continuous multiple transmission of the same data packet, and the repeated transmission is to copy a data packet to multiple data packets and put them on multiple logical channels for transmission.
  • the "repetition” here can also be understood as "copying”.
  • the indication information 3 may indicate the number of downlink tunnel addresses corresponding to various types in various ways. Several possible ways are described below with reference to Examples 1 to 4.
  • the indication information 3 may include uplink tunnel addresses corresponding to multiple types, wherein each type of the multiple types may correspond to one or more uplink tunnel addresses. That is to say, the indication information 3 implicitly indicates the number of downlink tunnel addresses corresponding to the various types by indicating the number of uplink tunnel addresses corresponding to the various types.
  • the indication information 3 indicates an implicit way.
  • the data packets of the first type are not repeatedly transmitted; when the first type corresponds to two uplink tunnel addresses, it indicates that the number of downlink tunnel addresses corresponding to the first type is 2. In this case, it can be understood that the indication information 3 passes through.
  • the implicit method indicates that the first type of data packet needs to be repeatedly transmitted, and the number of repeated transmissions is 2.
  • the number of uplink tunnel addresses corresponding to the first type included in the indication information 3 is the number of downlink tunnel addresses corresponding to the first type or the number of logical channels corresponding to the first type.
  • the uplink tunnel address corresponding to the first type may refer to the address on the CU side of the tunnel that carries the first type of data packet when the DU sends the first type of data packet to the CU;
  • the downlink tunnel address may refer to the address on the DU side of the tunnel carrying the first type of data packet when the CU sends the first type of data packet to the DU.
  • the multiple types include a first type, a second type and a third type; wherein the first type corresponds to the first QoS parameter, the second type corresponds to the second QoS parameter, and the third type corresponds to the third QoS parameter
  • the corresponding upstream tunnel address of the first type includes upstream tunnel address 1
  • the corresponding upstream tunnel address of the second type includes upstream tunnel address 2 and upstream tunnel address 3
  • the corresponding upstream tunnel address of the third type includes upstream tunnel address 4
  • DRB The configuration information of can include the content as shown in Table 2.
  • Table 2 Examples of contents included in DRB configuration information
  • the DU can assign a downlink tunnel address to each uplink tunnel address, for example, assign downlink tunnel address 1 to uplink tunnel address 1, assign downlink tunnel address 2 to uplink tunnel address 2, and assign downlink tunnel address 2 to uplink tunnel address 2.
  • Downlink tunnel address 3 is allocated to address 3
  • downlink tunnel address 4 is allocated to uplink tunnel address 4.
  • the DU sends a first message to the CU, where the first message may include downlink tunnel addresses corresponding to multiple types, and optionally, the first message may further include a correspondence between downlink tunnel addresses and uplink tunnel addresses. See Table 3, which is an example of the content included in the first message.
  • the indication information 3 may include the number of downlink tunnel addresses (or uplink tunnel addresses) corresponding to various types respectively. Wherein, each of the multiple types may correspond to one or more downlink tunnel addresses. Taking the first type as an example, if the number of downlink tunnel addresses corresponding to the first type included in the indication information 3 is 1, it can be understood that the indication information 3 implicitly indicates that the data packets of the first type are not repeated.
  • the indication information 3 implicitly indicates that the number of logical channels corresponding to the first type is 1; if the number of downlink tunnel addresses corresponding to the first type included in the indication information 3 is k (k is greater than 1 Integer), it can be understood that the indication information 3 implicitly indicates that the first type of data packets need to be repeatedly transmitted, or the indication information 3 implicitly indicates that the number of logical channels corresponding to the first type is k.
  • the multiple types include a first type, a second type and a third type; wherein the first type corresponds to the first QoS parameter, the second type corresponds to the second QoS parameter, and the third type corresponds to the third QoS parameter
  • the number of downlink tunnel addresses corresponding to the first type is 1, the number of downlink tunnel addresses corresponding to the second type is 2, and the number of downlink tunnel addresses corresponding to the third type is 4; then the configuration information of the DRB may include as shown in Table 4.
  • Table 4 Example of content included in DRB configuration information
  • the DU after the DU receives the configuration information of the DRB, it can allocate downlink tunnel addresses according to the number of downlink tunnel addresses corresponding to various types, for example, downlink tunnel address 1 is allocated for the first type, and downlink tunnel addresses are allocated for the second type. Address 2, Downlink Tunnel Address 3, Downlink Tunnel Address 4 is allocated for the third type. Further, a first message is sent to the CU, where the first message may include downlink tunnel addresses corresponding to multiple types respectively. See Table 5, which is an example of the content included in the first message.
  • the indication information 3 may include the number of logical channels corresponding to multiple types respectively. Wherein, each of the multiple types may correspond to one or more logical channels. Taking the first type as an example, if the number of logical channels corresponding to the first type included in the indication information 3 is 1, it can be understood that the indication information 3 implicitly indicates the number of downlink tunnel addresses corresponding to the first type. The number is 1, or the indication information 3 indicates in an implicit manner that the data packet of the first type is not to be repeatedly transmitted.
  • the indication information 3 implicitly indicates that the number of downlink tunnel addresses corresponding to the first type is k, or the indication information 3 Indicates that the first type of data packet needs to be repeatedly transmitted by an implicit way.
  • the indication information 3 may include indication information corresponding to multiple types, for example, the multiple types include the first type, the second type and the third type, the indication information 3 may include the indication information 31 corresponding to the first type, and the indication information 31 corresponding to the second type.
  • the indication information 31 corresponding to the first type is used to indicate whether the data packets of the first type need to be repeatedly transmitted. In this case, it can be understood that the indication information 3 explicitly indicates whether multiple types of data packets need to be repeatedly transmitted.
  • the second core network device sends the first data packet in the first QoS flow to the CU, and accordingly, the CU may receive the first data packet.
  • the CU sends the first data packet to the DU through the first tunnel, and correspondingly, the DU may receive the first data packet through the first tunnel.
  • the downlink tunnel address of the first tunnel is a downlink tunnel address corresponding to the type to which the first data packet belongs.
  • the CU can learn the type to which the first data packet belongs.
  • the type to which the first data packet belongs is the first type.
  • the CU can pass the tunnel whose downlink tunnel address is the downlink tunnel address 1 (for example, Tunnel 1) sends the first data packet to the DU.
  • the type to which the first data packet belongs is the second type.
  • the CU can copy the first data packet as Two first data packets, and respectively send the first data packets to the DU through the tunnel whose downlink tunnel address is downlink tunnel address 2 (eg, tunnel 2 ) and the tunnel whose downlink tunnel address is downlink tunnel address 3 (eg, tunnel 3 ).
  • the DU performs downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the DU after receiving the first data packet through the first tunnel, the DU can convert the first data packet into the first data packet according to the correspondence between the downlink tunnel address of the first tunnel and the logical channel. Packets are mapped to corresponding logical channels. Further, since the downlink tunnel address of the first tunnel is the downlink tunnel address corresponding to the first type, the DU can further perform downlink scheduling on the first data packet according to the QoS parameter corresponding to the first type.
  • the CU can send the configuration information of the DRB to the DU.
  • the configuration information of the DRB includes the QoS parameters corresponding to the various types and the indication information 3 respectively.
  • the indication information 3 is used to indicate the downlink tunnel address corresponding to the various types.
  • the DU can allocate downlink tunnel addresses for multiple types respectively according to the configuration information of the DRB, and feed it back to the CU.
  • the CU can send the first data packet to the DU through the corresponding tunnel (such as the first tunnel) according to the type of the first data packet, and the DU can use the corresponding QoS parameters after receiving the first data packet through the first tunnel.
  • Downlink scheduling is performed on the first data packet, thereby implementing differentiated scheduling on different types of data packets in the same QoS flow.
  • step numbers of the flowcharts described in Embodiments 1 to 3 are only an example of the execution process, and do not constitute a restriction on the sequence of execution of the steps, and there is no timing dependency between the embodiments of this application. There is no strict order of execution between the steps of a relationship.
  • steps shown in each flowchart are steps that must be executed, and some steps may be added or deleted on the basis of each flowchart according to actual needs.
  • the access network device, core network device or terminal device may include corresponding hardware structures and/or software modules for performing each function.
  • the embodiments of the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the access network device, the core network device, or the terminal device may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated. in one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of software functional units.
  • FIG. 8 shows a possible exemplary block diagram of the apparatus involved in the embodiment of the present application.
  • the apparatus 800 may include: a processing unit 802 and a communication unit 803 .
  • the processing unit 802 is used to control and manage the actions of the device 800 .
  • the communication unit 803 is used to support the communication between the apparatus 800 and other devices.
  • the communication unit 803 is also referred to as a transceiving unit, and may include a receiving unit and/or a sending unit, which are respectively configured to perform receiving and sending operations.
  • the apparatus 800 may further include a storage unit 801 for storing program codes and/or data of the apparatus 800 .
  • the apparatus 800 may be the access network device in the foregoing embodiment, or may also be a chip set in the access network device.
  • the processing unit 802 may support the apparatus 800 to perform the actions of the access network device in each method example above.
  • the processing unit 802 mainly performs the internal actions of the access network device in the method example, and the communication unit 803 (including the receiving unit and the sending unit) can support the communication between the apparatus 800 and other devices.
  • the receiving unit is configured to: receive configuration information of a first QoS flow from a first core network device, where the configuration information of the first QoS flow includes QoS parameters of the first QoS flow;
  • the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types respectively;
  • the processing unit is configured to: perform downlink scheduling on the first data packet according to the QoS parameter corresponding to the type to which the first data packet belongs.
  • the receiving unit is further configured to: receive first indication information from the second core network device, where the first indication information indicates a type to which the first data packet belongs.
  • the first data packet and the first indication information are carried in a second data packet from the second core network device, and the first indication information is carried in the second data packet in the header of the package.
  • the processing unit is further configured to: map the first data packet to the type of the first data packet to which the first data packet belongs according to the corresponding relationship between the type to which the first data packet belongs and the logical channel.
  • the logical channel corresponding to the type.
  • the multiple types include a first type
  • the QoS parameter corresponding to the first type includes at least one of the following: first information, where the first information is used to indicate the first type Whether the data packets of the first type are allowed to be discarded; second information, the second information is used to indicate the number of data packets of the first type that are allowed to be discarded within a set time.
  • the apparatus 800 may be the CU in the foregoing embodiment or a chip provided in the CU.
  • the processing unit 802 may support the apparatus 800 to perform the actions of the CU in each method example above.
  • the processing unit 802 mainly performs the internal actions of the CU in the method example, and the communication unit 803 (including the receiving unit and the sending unit) can support the communication between the apparatus 800 and other devices.
  • the receiving unit is configured to: receive configuration information of a first QoS flow from a first core network device, where the configuration information of the first QoS flow includes QoS parameters of the first QoS flow;
  • the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include QoS parameters corresponding to the multiple types respectively;
  • the sending unit is configured to: send the configuration of the DRB to the DU information, the configuration information of the DRB includes the QoS parameters corresponding to the multiple types respectively.
  • the receiving unit is further configured to: receive the first data packet of the first QoS flow from the second core network device; the sending unit is further configured to: send the data packet to the DU the first data packet and second indication information, where the second indication information indicates the type to which the first data packet belongs.
  • the sending unit is specifically configured to: send a third data packet to the DU, where the third data packet includes the first data packet and the second indication information, and the third data packet includes the first data packet and the second indication information.
  • the second indication information is carried in the header of the third data packet.
  • the sending unit is further configured to: send third indication information to the DU, where the third indication information indicates the number of downlink tunnel addresses corresponding to the multiple types; the The receiving unit is further configured to: receive a first message from the DU, where the first message includes downlink tunnel addresses corresponding to the multiple types respectively.
  • the receiving unit is further configured to: receive the first data packet of the first QoS flow from the second core network device; the sending unit is further configured to: send the data packet to the second core network device through the first tunnel.
  • the DU sends the first data packet, and the downlink tunnel address of the first tunnel is the downlink tunnel address corresponding to the type to which the first data packet belongs.
  • the apparatus 800 may be the DU in the foregoing embodiment or a chip provided in the DU.
  • the processing unit 802 can support the apparatus 800 to perform the actions of the DU in each method example above.
  • the processing unit 802 mainly performs the internal actions of the DU in the method example, and the communication unit 803 (including the receiving unit and the sending unit) can support the communication between the apparatus 800 and other devices.
  • the receiving unit is configured to: receive configuration information of a DRB from the CU, where the DRB corresponds to a first QoS flow, the first QoS flow supports multiple types of data packets, and the DRB's
  • the configuration information includes QoS parameters corresponding to the multiple types respectively; and, receiving a first data packet from the CU; the processing unit is configured to: according to the QoS parameters corresponding to the type to which the first data packet belongs, The first data packet performs downlink scheduling.
  • the receiving unit is further configured to: receive second indication information from the CU, where the second indication information indicates a type to which the first data packet belongs.
  • the first data packet and the second indication information are carried in a third data packet from the CU, and the second indication information is carried in a header of the third data packet .
  • the receiving unit is further configured to: receive third indication information from the CU, where the third indication information indicates the number of downlink tunnel addresses corresponding to the multiple types respectively;
  • the sending unit is configured to send a first message to the CU, where the first message includes downlink tunnel addresses corresponding to the multiple types respectively.
  • the receiving unit is further configured to: receive a first data packet from the CU through a first tunnel, where the downlink tunnel address of the first tunnel is corresponding to the type to which the first data packet belongs Downlink tunnel address.
  • the apparatus 800 may be the first core network device in the foregoing embodiment, or may also be a chip provided in the first core network device.
  • the processing unit 802 may support the apparatus 800 to perform the actions of the first core network device in each method example above.
  • the processing unit 802 mainly performs the internal actions of the first core network device in the method example, and the communication unit 803 may support the communication between the apparatus 800 and other devices.
  • the processing unit 802 is configured to: determine the configuration information of the first QoS flow; the communication unit 803 is configured to: send the configuration information of the first QoS flow to the access network device or the CU, the The configuration information of the first QoS flow includes QoS parameters of the first QoS flow; wherein, the first QoS flow supports multiple types of data packets, and the QoS parameters of the first QoS flow include the multiple types of packets, respectively. Corresponding QoS parameters.
  • the apparatus 800 may be the second core network device in the foregoing embodiment, or may also be a chip provided in the second core network device.
  • the processing unit 802 may support the apparatus 800 to perform the actions of the second core network device in each method example above.
  • the processing unit 802 mainly performs the internal actions of the second core network device in the method example, and the communication unit 803 may support the communication between the apparatus 800 and other devices.
  • the communication unit 803 is configured to: receive the first data packet from the application server; and send the first data packet and indication information to the access network device or the CU, where the indication information indicates The type to which the first data packet belongs.
  • each unit in the device can all be implemented in the form of software calling through the processing element; also can all be implemented in the form of hardware; some units can also be implemented in the form of software calling through the processing element, and some units can be implemented in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called and executed by a certain processing element of the device. Function.
  • all or part of these units can be integrated together, and can also be implemented independently.
  • the processing element described here can also become a processor, which can be an integrated circuit with signal processing capability.
  • each operation of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, eg, one or more application specific integrated circuits (ASICs), or, one or more Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs field programmable gate arrays
  • a unit in the apparatus can be implemented in the form of a processing element scheduler
  • the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processors that can invoke programs.
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above unit for receiving is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • Access network equipment 90 may include one or more DUs 901 and one or more CUs 902.
  • the DU 901 may include at least one antenna 9011, at least one radio frequency unit 9012, at least one processor 9013 and at least one memory 9014.
  • the DU 901 part is mainly used for the transceiver of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing.
  • the CU 902 may include at least one processor 9022 and at least one memory 9021 .
  • the CU 902 part is mainly used to perform baseband processing, control access network equipment, and the like.
  • the DU 901 and the CU 902 may be physically set together, or may be physically set apart, that is, a distributed base station.
  • the CU 902 is the control center of the access network equipment, which can also be called a processing unit, and is mainly used to complete the baseband processing function.
  • the CU 902 may be used to control the access network device to perform the operation process of the access network device in the foregoing method embodiments.
  • the access network device 90 may include one or more radio frequency units, one or more DUs, and one or more CUs.
  • the DU may include at least one processor 9013 and at least one memory 9014
  • the radio unit may include at least one antenna 9011 and at least one radio unit 9012
  • the CU may include at least one processor 9022 and at least one memory 9021 .
  • the CU902 may be composed of one or more single boards, and multiple single boards may jointly support a wireless access network (such as a 5G network) with a single access indication, or may respectively support wireless access systems of different access standards.
  • Access network such as LTE network, 5G network or other network.
  • the memory 9021 and the processor 9022 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the DU901 can be composed of one or more single boards, and multiple single boards can jointly support a wireless access network (such as a 5G network) with a single access indication, or can support a wireless access network with different access standards (such as a 5G network). LTE network, 5G network or other network).
  • the memory 9014 and processor 9013 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the access network device shown in FIG. 9 can implement each process involving the access network device in the foregoing method embodiments, the CU shown in FIG. 9 can implement various processes involving the CU in the foregoing method embodiments, and the DU shown in FIG. 9 Various processes involving DUs in the foregoing method embodiments can be implemented.
  • the operations and/or functions of each module in the access network device or the CU or DU shown in FIG. 9 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • FIG. 10 it is a schematic structural diagram of a core network device according to an embodiment of the present application. It may be the first core network device or the second core network device in the above embodiment, and is used to implement the operation of the first core network device or the second core network device in the above embodiment.
  • the core network device 1000 may include a processor 1001 , a memory 1002 and an interface circuit 1003 .
  • the processor 1001 can be used to process the communication protocol and communication data, and to control the communication device.
  • the memory 1002 may be used to store programs and data, and the processor 1001 may execute the method performed by the AMF network element or the SMF network element in the embodiment of the present application based on the program.
  • the interface circuit 1003 can be used for the core network device 1000 to communicate with other devices, and the communication can be wired communication or wireless communication, and the interface circuit can be, for example, a service-oriented communication interface.
  • the above memory 1002 may also be externally connected to the core network device 1000 .
  • the core network device 1000 may include an interface circuit 1003 and a processor 1001 .
  • the above interface circuit 1003 may also be externally connected to the core network device 1000 .
  • the core network device 1000 may include a memory 1002 and a processor 1001 .
  • the communication apparatus 1000 may include a processor 1001 .
  • the core network device shown in FIG. 10 can implement each process involving the first core network device or the second core network device in the foregoing method embodiments.
  • the operations and/or functions of each module in the core network device shown in FIG. 10 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • system and “network” in the embodiments of the present application may be used interchangeably.
  • At least one means one or more, and “plurality” means two or more.
  • And/or which describes the association relationship of the associated objects, means that there can be three kinds of relationships, for example, A and/or B, which can mean: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one of A, B and C includes A, B, C, AB, AC, BC or ABC.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority or importance of multiple objects degree.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Abstract

本申请涉及通信技术领域，公开了一种通信方法及装置。其中方法包括：接入网设备接收第一QoS流的配置信息，第一QoS流支持多种类型的数据包，该配置信息包括多种类型分别对应的QoS参数；以及，在接收到第一QoS流的第一数据包后，根据第一数据包所属的类型对应的QoS参数对第一数据包进行下行调度。采用上述方法，由于第一QoS流的配置信息可以包括多种类型分别对应的QoS参数，使得接入网设备接收到第一QoS流中的数据包后，可以根据数据包所属的类型，采用相应的QoS参数来对该数据包进行下行调度，从而实现对同一QoS流中不同类型的数据包进行差异化调度，提升用户的业务体验。

Description

一种通信方法及装置 技术领域
本申请涉及无线通信技术领域，特别涉及一种通信方法及装置。
背景技术
移动通信网络中，运营商能够为用户提供多种丰富多彩的业务，比如虚拟现实(virtual reality，VR)业务、增强现实(augmented reality，AR)业务、高清视频业务、触觉互联网业务等。以这些业务中涉及的视频传输为例，视频通常有多种编码方式，比如分级编码方式和非分级编码方式。以分级编码方式为例，该方式将一个基本层(basic layer，BL)和若干个增强层(extend layer，EL)成一个多层视频系统，基本层提供基本图像质量的码流，增强层提供可在基本图像质量的基础上构建出更高图像质量的码流。
然而，针对编码后得到的不同类型的数据包，如何进行差异化调度，仍需进一步的研究。
发明内容
本申请提供了一种通信方法及装置，用于对不同类型的数据包进行差异化调度。
第一方面，本申请实施例提供一种通信方法，该方法用于实现网络设备侧的功能，例如该方法可以应用于接入网设备或者接入网设备中的芯片，本申请实施例不限该方法的具体的执行主体。以该方法应用于接入网设备为例，在该方法中，接入网设备接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；接收来自第二核心网设备的所述第一QoS流的第一数据包；以及，根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
采用上述方法，由于第一QoS流的QoS参数可以包括多种类型分别对应的QoS参数，使得接入网设备接收到第一QoS流中的数据包后，可以根据数据包所属的类型，采用相应的QoS参数来对该数据包进行下行调度，从而实现对同一QoS流中不同类型的数据包进行差异化调度，提升用户的业务体验。
在一种可能的设计中，所述方法还包括：接收来自所述第二核心网设备的第一指示信息，所述第一指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，所述第一数据包和所述第一指示信息承载于来自所述第二核心网设备的第二数据包，所述第一指示信息承载于所述第二数据包的包头中。
在一种可能的设计中，所述方法还包括：根据所述第一数据包所属的类型和逻辑信道的对应关系，将所述第一数据包映射至所述第一数据包所属的类型对应的逻辑信道。
采用上述方法，接入网设备可以将不同类型的数据包映射到相应的逻辑信道进行传输，从而能够有效满足不同类型的数据包的传输需求。比如，第一类型对应的QoS参数表明第一类型的数据包的传输可靠性要求较高，而第二类型对应的QoS参数表明第二类型的数据包的传输可靠性要求较低，则第一类型可以在多个逻辑信道上复制/重复传输，第二类型可 以在单个逻辑信道上传输，换句话说，第一类型对应的逻辑信道的个数可以大于第二类型对应的逻辑信道的个数。
在一种可能的设计中，所述多种类型包括第一类型，所述第一类型对应的QoS参数包括以下至少一项：第一信息，所述第一信息用于指示所述第一类型的数据包是否允许丢弃；第二信息，所述第二信息用于指示所述第一类型的数据包在设定时间内允许丢弃的个数。
第二方面，本申请实施例提供一种通信方法，该方法用于实现网络设备侧的功能，例如该方法可以应用于CU或者CU中的芯片，本申请实施例不限该方法的具体的执行主体。以该方法应用于CU为例，在该方法中，CU接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；以及，向DU发送所述第一QoS流对应的DRB的配置信息，所述DRB的配置信息包括所述多种类型分别对应的QoS参数。
采用上述方法，CU可以向DU发送多种类型分别对应的QoS参数，使得DU接收到数据包后，可以根据数据包所属的类型，采用相应的QoS参数来对该数据包进行下行调度，从而实现对同一QoS流中不同类型的数据包进行差异化调度。
在一种可能的设计中，所述方法还包括：接收来自第二核心网设备的所述第一QoS流的第一数据包；向所述DU发送所述第一数据包和第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，向所述DU发送所述第一数据包和所述第二指示信息，包括：向所述DU发送第三数据包，所述第三数据包包括所述第一数据包和所述第二指示信息，所述第二指示信息承载于所述第三数据包的包头中。
在一种可能的设计中，所述方法还包括：向所述DU发送第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；以及，接收来自所述DU的第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。其中，第三指示信息指示所述多种类型分别对应的下行隧道地址的个数，也可以替换为，第三指示信息指示所述多种类型分别对应的逻辑信道的个数。
采用上述方法，CU可以配置不同类型的数据包对应的逻辑信道的个数，从而能够有效满足不同类型的数据包的传输需求。比如，第一类型对应的QoS参数表明第一类型的数据包的传输可靠性要求较高，而第二类型对应的QoS参数表明第二类型的数据包的传输可靠性要求较低，则第一类型可以在多个逻辑信道上复制/重复传输，第二类型可以在单个逻辑信道上传输，换句话说，第一类型对应的逻辑信道的个数可以大于第二类型对应的逻辑信道的个数。
在一种可能的设计中，接收来自第二核心网设备的所述第一QoS流的第一数据包；通过第一隧道向所述DU发送所述第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
第三方面，本申请实施例提供一种通信方法，该方法用于实现网络设备侧的功能，例如该方法可以应用于DU或者DU中的芯片，本申请实施例不限该方法的具体的执行主体。以该方法应用于DU为例，在该方法中，DU接收来自CU的DRB的配置信息，所述DRB对应第一QoS流，所述第一QoS流支持多种类型的数据包，所述DRB的配置信息包括所述多种类型分别对应的QoS参数；接收来自所述CU的第一数据包；根据所述第一数据包所属的类 型对应的QoS参数，对所述第一数据包进行下行调度。
在一种可能的设计中，所述方法还包括：接收来自所述CU的第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，所述第一数据包和所述第二指示信息承载于来自所述CU的第三数据包，所述第二指示信息承载于所述第三数据包的包头中。
在一种可能的设计中，所述方法还包括：接收来自所述CU的第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；以及，向CU发送第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
在一种可能的设计中，接收来自所述CU的第一数据包，包括：通过第一隧道接收来自CU的第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
第四方面，本申请实施例提供一种通信方法，该方法用于实现网络设备侧的功能，例如该方法可以应用于第一核心网设备或者第一核心网设备中的芯片，本申请实施例不限该方法的具体的执行主体。以该方法应用于第一核心网设备为例，在该方法中，第一核心网设备确定第一QoS流的配置信息，并向接入网设备或CU发送所述第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数。
第五方面，本申请实施例提供一种通信方法，该方法用于实现网络设备侧的功能，例如该方法可以应用于第二核心网设备或者第二核心网设备中的芯片，本申请实施例不限该方法的具体的执行主体。以该方法应用于第二核心网设备为例，在该方法中，第二核心网设备接收来自应用服务器的第一数据包；向接入网设备或CU发送所述第一数据包和指示信息，所述指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，向接入网设备或CU发送所述第一数据包和第一指示信息，包括：向接入网设备或CU发送第二数据包，所述第二数据包包括所述第一数据包和所述第一指示信息，所述第一指示信息承载于所述第二数据包的包头中。
需要说明的是，上述第一方面至第五方面所提供的通信方法相互对应，因此第一方面至第五方面的相关技术特征的有益效果可以相互参照，具体不再赘述。
第六方面，本申请实施例提供一种通信装置，所述通信装置可以为接入网设备或者能够设置于接入网设备内部的芯片。所述通信装置具备实现上述第一方面的功能，比如，所述通信装置包括执行上述第一方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元和通信单元，其中，通信单元可以包括接收单元和/或发送单元，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第一方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器利用所述收发器，以完成上述第一方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第一方面涉及的功能的计算机程序或指令。所述 处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面任意可能的设计或实现方式中的方法。
第七方面，本申请实施例提供一种通信装置，所述通信装置可以为CU或者能够设置于CU内部的芯片。所述通信装置具备实现上述第二方面的功能，比如，所述通信装置包括执行上述第二方面涉及操作所对应的模块或单元或手段，所述模块或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信，比如，通信单元用于接收来自终端设备的上行信息；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第二方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器利用所述收发器，以完成上述第二方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第二方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第二方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第二方面任意可能的设计或实现方式中的方法。
第八方面，本申请实施例提供一种通信装置，所述通信装置可以为DU或者能够设置于DU内部的芯片。所述通信装置具备实现上述第三方面的功能，比如，所述通信装置包括执行上述第三方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元和通信单元，其中，通信单元包括接收单元和/或发送单元，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第三方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器利用所述收发器，以完成上述第三方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第三方面涉及的功能的计算机程序或指令。所述 处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第三方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第三方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第三方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第三方面任意可能的设计或实现方式中的方法。
第九方面，本申请实施例提供一种通信装置，所述通信装置可以为第一核心网设备或者能够设置于第一核心网设备内部的芯片。所述通信装置具备实现上述第四方面的功能，比如，所述通信装置包括执行上述第四方面涉及操作所对应的模块或单元或手段，所述模块或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、通信单元，其中，通信单元可以包括接收单元和/或发送单元，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第四方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器利用所述收发器，以完成上述第四方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第四方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第四方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第四方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第四方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第四方面任意可能的设计或实现方式中的方法。
第十方面，本申请实施例提供一种通信装置，所述通信装置可以为第二核心网设备或者能够设置于第二核心网设备内部的芯片。所述通信装置具备实现上述第五方面的功能，比如，所述通信装置包括执行上述第五方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元和通信单元，其中，通信单元可以包括接收单元和/或发送单元，通信单元可以用于收发信号，以实现该通信装置和其它装置之间的通信；处理单元可以用于执行该通信装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第五方面涉及的操作相对应。
在一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器利用所述收发器，以完成上述第五方面中任意可能的设计或实现 方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第五方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第五方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第五方面涉及的功能的计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第五方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第五方面任意可能的设计或实现方式中的方法。
可以理解地，上述第六方面至第十方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第十一方面，本申请实施例提供一种通信系统，该通信系统包括上述第六方面所述的通信装置、上述第九方面所述的通信装置以及上述第十方面所述的通信装置。
第十二方面，本申请实施例提供一种通信系统，该通信系统包括上述第七方面所述的通信装置、上述第八方面所述的通信装置。可选地，还可以包括上述第九方面所述的通信装置以及上述第十方面所述的通信装置。
第十三方面，本申请实施例提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第一方面至第五方面的任一种可能的设计中的方法。
第十四方面，本申请实施例提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面至第五方面的任一种可能的设计中的方法。
第十五方面，本申请实施例提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面至第五方面的任一种可能的设计中的方法。
本申请的这些方面或其它方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例适用的一种网络架构示意图；
图2a为本申请实施例提供的终端设备与接入网设备之间的协议层结构示例图；
图2b为本申请实施例提供的一种CU-DU分离架构的示意图；
图2c为本申请实施例提供的又一种CU-DU分离架构的示意图；
图2d为本申请实施例提供的一种空口协议栈分布示意图；
图3为5G通信系统中的QoS模型示意图；
图4为PDU会话建立过程所涉及的部分流程示意图；
图5为本申请实施例一提供的通信方法所对应的流程示意图；
图6为本申请实施例二提供的通信方法所对应的流程示意图；
图7为本申请实施例三提供的通信方法所对应的流程示意图；
图8为本申请实施例中所涉及的装置的可能的示例性框图；
图9为本申请实施例提供的一种接入网设备的结构示意图；
图10为本申请实施例提供的一种核心网设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
图1为本申请实施例适用的一种网络架构示意图。如图1所示，终端设备可接入到无线网络，以通过无线网络获取外网(例如数据网络(data network，DN))的服务，或者通过无线网络与其它设备通信，如可以与其它终端设备通信。该无线网络包括(无线)接入网((radio)access network，(R)AN)和核心网(core network，CN)，其中，(R)AN(后文描述为RAN)用于将终端设备接入到无线网络，CN用于对终端设备进行管理并提供与DN通信的网关。
下面分别对图1中所涉及的终端设备、RAN、CN、DN进行详细说明。
一、终端设备
终端设备包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网与核心网进行通信，该终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、设备到设备通信(device-to-device，D2D)终端设备、车到一切(vehicle to everything，V2X)终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)终端设备、物联网(internet of things，IoT)终端设备、订户单元、订户站，移动站、远程站、接入点(access point，AP)、远程终端、接入终端、用户终端、用户代理、或用户装备等。例如，可以包括移动电话(或称为“蜂窝”电话)，具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的移动装置等。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、等设备；还可以包括受限设备，例如功耗较低的设备，或存储能力有限的设备，或计算能力有限的设备等。
二、RAN
RAN中可以包括一个或多个RAN设备(或者说接入网设备)，接入网设备与终端设备之间的接口可以为Uu接口(或称为空口)。当然，在未来通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。
接入网设备即为将终端设备接入到无线网络的节点或设备，接入网设备例如包括但不限于：5G通信系统中的新一代基站(generation node B，gNB)、演进型节点B(evolved node B，eNB)、下一代演进型节点B(next generation eNB，ng-eNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站((home evolved  nodeB，HeNB)或(home node B，HNB))、基带单元(baseBand unit，BBU)、传输接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
(1)协议层结构
接入网设备和终端设备之间的通信遵循一定的协议层结构，例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层，在一种可能的实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。
以接入网设备和终端设备之间的数据传输为例，数据传输需要经过用户面协议层，比如经过SDAP层、PDCP层、RLC层、MAC层、物理层，其中，SDAP层、PDCP层、RLC层、MAC层、物理层也可以统称为接入层。示例性地，接入网设备和终端设备之间通过建立至少一个数据无线承载(data radio bearer，DRB)来传输数据，每个DRB可以对应一组功能实体集合，比如包括一个PDCP层实体，该PDCP层实体对应的至少一个RLC层实体，至少一个RLC层实体对应的至少一个MAC层实体，至少一个MAC层实体对应的至少一个物理层实体。需要说明的是，接入网设备和终端设备之间还可以通过建立至少一个信令无线承载(signalling radio bearer，SRB)来传输信令，DRB和SRB可以统称为无线承载(radio bearer，RB)。
以下行数据传输为例，图2a为下行数据在各层间传输的示意图，图2a中向下的箭头表示数据发送，向上的箭头表示数据接收。SDAP层实体自上层取得数据后，可以根据数据的服务质量流标识(QoS flow indicator，QFI)将数据映射到相应DRB的PDCP层实体，PDCP层实体可以将数据传送到该PDCP层实体对应的至少一个RLC层实体，进而由至少一个RLC层实体传输到对应的MAC层实体，再由MAC层实体生成传输块，然后通过对应的物理层实体进行无线传输。数据在各个层中进行相对应的封装，某一层从该层的上层收到的数据视为该层的服务数据单元(service data unit，SDU)，经过层封装后成为协议数据单元(protocol data unit，PDU)，再传递给下一个层。例如PDCP层实体从上层接收到的数据称为PDCP SDU，PDCP层实体发送到下层的数据称为PDCP PDU；RLC层实体从上层接收到的数据称为RLC SDU，RLC层实体发送到下层的数据称为RLC PDU。其中，不同层之间可以通过相应的通道来传输数据，比如RLC层实体与MAC层实体之间可以通过逻辑信道(logical channel，LCH)来传输数据，MAC层实体与物理层实体之间可以通过传输通道(transport channel)来传输数据。
示例性地，根据图2a还可以看出，终端设备还具有应用层和非接入层；其中，应用层可以用于向终端设备中所安装的应用程序提供服务，比如，终端设备接收到的下行数据可以由物理层依次传输到应用层，进而由应用层提供给应用程序；又比如，应用层可以获取应用程序产生的数据，并将数据依次传输到物理层，发送给其它通信装置。非接入层可以用于转发用户数据，比如将从应用层接收到的上行数据转发给SDAP层或者将从SDAP层接收到的下行数据转发给应用层。
(2)CU和DU
本申请实施例中，接入网设备可以包括一个或多个集中式单元(centralized unit，CU)和一个或多个分布式单元(distributed unit，DU)，多个DU可以由一个CU集中控制。作 为示例，CU和DU之间的接口可以称为F1接口，其中，控制面(control panel，CP)接口可以为F1-C，用户面(user panel，UP)接口可以为F1-U。CU和DU可以根据无线网络的协议层划分：比如图2b所示，PDCP层及以上协议层的功能设置在CU，PDCP层以下协议层(例如RLC层和MAC层等)的功能设置在DU。
可以理解的，上述对CU和DU的处理功能按照协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分，比如RLC层以上协议层的功能设置在CU，RLC层及以下协议层的功能设置在DU，又比如可以将CU或者DU划分为具有更多协议层的功能，又比如CU或DU还可以划分为具有协议层的部分处理功能。在一种设计中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。在另一种设计中，还可以按照业务类型或者其他系统需求对CU或者DU的功能进行划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。在另一种设计中，CU也可以具有核心网的一个或多个功能。示例性地，CU可以设置在网络侧方便集中管理；DU可以具有多个射频功能，也可以将射频功能拉远设置。本申请实施例对此并不进行限定。
示例性地，CU的功能可以由一个实体来实现，或者也可以由不同的实体来实现。例如，如图2c所示，可以对CU的功能进行进一步切分，即将控制面和用户面分离并通过不同实体来实现，分别为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)，CU-CP实体和CU-UP实体可以与DU相耦合，共同完成RAN设备的功能。CU-CP实体与CU-UP实体之间的接口可以为E1接口，CU-CP实体与DU之间的接口可以为F1-C接口，CU-UP实体与DU之间的接口可以为F1-U接口。其中，一个DU和一个CU-UP可以连接到一个CU-CP。在同一个CU-CP控制下，一个DU可以连接到多个CU-UP，一个CU-UP可以连接到多个DU。
基于图2c，图2d为一种空口协议栈分布示意图。如图2d所示，针对用户面和控制面来说，空口协议栈都可以是RLC、MAC、PHY在DU，PDCP及以上协议层在CU。
需要说明的是：在上述图2b至图2d所示意的架构中，CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装后透传给终端设备或CU。以下实施例中如果涉及这种信令在DU和终端设备之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为物理层的数据发送给终端设备，或者，由接收到的物理层的数据转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频装置发送的。
三、CN
CN中可以包括一个或多个CN设备，以5G通信系统为例，CN中可以包括接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)网元等。
AMF网元是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF网元是由运营商网络提供的控制面网元，负责管理终端设备的PDU会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF网元负责建立、维护和删除等。SMF网元包括会话管理(如会话建立、修改和释放，包含UPF和RAN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。
UPF网元是由运营商提供的网关，是运营商网络与DN通信的网关。UPF网元包括数据包路由和传输、包检测、服务质量(quality of service，QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
PCF网元是由运营商提供的控制面功能，用于向SMF网元提供PDU会话的策略。策略可以包括计费相关策略、QoS相关策略和授权相关策略等。
AF网元是提供各种业务服务的功能网元，能够通过其它网元与核心网交互，以及能够和策略管理框架交互进行策略管理。
此外，尽管未示出，CN中还可以包括其它可能的网元，比如网络开放功能(network exposure function，NEF)、网元统一数据仓储(unified data repository，UDR)网元。
需要说明的是，本申请实施例中接入网设备和核心网设备可以统称为网络设备。
四、DN
DN也可以称为分组数据网络(packet data network，PDN)，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN中可部署有多种业务对应的应用服务器，为终端设备提供多种可能的服务。
图1中Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见相关标准协议中定义的含义，在此不做限制。
可以理解的是，图1中是以5G通信系统为例进行示意的，本申请实施例中的方案还可以适用于其它可能的通信系统中，比如LTE通信系统或者未来的第六代(the 6th generation，6G)通信系统中。上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
下面先对本申请实施例涉及的相关技术特征进行解释说明。需要说明的是，这些解释是为了让本申请实施例更容易被理解，而不应该视为对本申请所要求的保护范围的限定。
一、PDU会话及QoS流
在上述图1所示意的网络架构中，终端设备与UPF网元之间可以通过PDU会话进行数据传输，每个PDU会话中可以传输多个不同QoS要求的数据流，称为QoS流。
图3为5G通信系统中的QoS模型示意图。如图3所示，在下行方向上，数据包到达UPF网元后，UPF网元根据SMF网元配置的包检测规则(packet detection rule，PDR)中的包过滤集合(packet filter sets)将下行数据包区分到不同的QoS流，QoS流内的数据包标记有QoS流的标识(QoS flow indicator，QFI)。进而UPF网元将数据包通过N3接口传递到接入网设备，接入网设备接收到数据包后，根据数据包对应的QFI确定该数据所属的QoS流，再根据该QoS流的QoS参数，在空口上进行下行数据包的传输。在上行方向上，终端设备的应用层获取数据包后，可以根据SMF网元配置的QoS规则中的包过滤集 合将上行数据包区分成不同的QoS流，然后在空口上进行上行数据包的传输。需要说明的是，本申请实施例中将主要针对下行方向上的相关实现进行研究。
可以理解地，在采用上述QoS模型进行数据传输之前，需要先通过PDU会话建立过程建立终端设备与UPF网元之间的PDU会话。
图4为PDU会话建立过程所涉及的部分流程示意图，参见图4所示，该流程可以包括：
步骤401，AF网元向PCF网元发送业务(比如业务1)的QoS需求信息。
此处，业务1可以为VR业务或AR业务或高清视频业务或触觉互联网业务等，具体不做限定。业务1中可以包括多个数据流，比如视频数据流、音频数据流等，不同数据流可以具有不同的QoS需求信息。
步骤402，PCF网元接收业务1的QoS需求信息，并根据业务1的QoS需求信息确定业务1中不同数据流分别对应的QoS参数。
步骤403，PCF网元将业务1中不同数据流对应的QoS参数发送给SMF网元。
此处，比如当终端设备有业务1的接收需求后，终端设备可以发起PDU会话建立过程，进而SMF网元接收到来自终端设备的PDU会话建立请求后，可以向PCF网元发送请求消息，请求消息用于获取业务1中不同数据流对应的QoS参数，进而PCF网元可以将业务1中不同数据流对应的QoS参数发送给SMF网元。
步骤404，SMF网元确定待建立的PDU会话所包括的一个或者多个QoS流中每个QoS流的配置信息以及每个QoS对应的包过滤集合。
其中，每个QoS流的配置信息可以包括每个QoS流的QoS参数。比如，一个或多个QoS流中包括第一QoS流，第一QoS流用于承载业务1中的视频数据流，则第一QoS流的QoS参数即为视频数据流对应的QoS参数。
步骤405，SMF网元向UPF网元发送该PDU会话中需要建立的一个或者多个QoS流中每个QoS流对应的包过滤集合。如此，UPF网元在接收到来自应用服务器的数据包后，可以根据每个QoS流对应的包过滤集合，将数据包区分到不同的QoS流。
步骤406，SMF网元通过AMF网元向接入网设备发送PDU会话资源建立请求消息，PDU会话资源建立请求消息包括该PDU会话中需要建立的一个或者多个QoS流中每个QoS流的配置信息。如此，接入网设备可以根据每个QoS流的配置信息中包括的每个QoS流的QoS参数，在空口上进行下行数据包的传输。
二、QoS参数
QoS流可以包括保证比特速率(guaranteed bit rate，GBR)QoS流和非保证比特速率(non-guaranteed bit rate，Non-GBR)QoS流。其中，GBR QoS流所承载的业务对时延要求较为严格或者对速率要求较严格，需要保证该流的传输速率，比如会话类视频等业务；Non-GBR QoS流所承载的业务对速率要求不高，不需要实时的速率保证，比如网页浏览、文件下载等业务。
以GBR QoS流为例，每个GBR QoS流可以对应一组QoS参数，该组QoS参数可以包括5G服务质量标识(5G QoS identifier，5QI)、保证流比特率(guaranteed flow bit rate，GFBR)、最大流比特率(maximum flow bit rate，MFBR)。
其中，GFBR表示由网络保证在平均窗口上向QoS流提供的比特率；MFBR用于将比特率限制为QoS流所期望的最高比特率(例如，超过MFBR时数据包可能被UE/RAN/UPF 丢弃)。GFBR的值在上行链路(uplink，UL)和下行链路(downlink，DL)中可以是相同的，以及MFBR的值在UL和DL中也可以是相同的。
5QI是一个标量，用于索引到对应的5G QoS特征。5QI分为标准化的5QI、预配置的5QI和动态分配的5QI。其中，标准化的5QI与一组标准化的5G QoS特征一一对应；预配置的5QI对应的5G QoS特征值可以预配置在接入网设备上；动态分配的5QI对应的5G QoS特征由核心网设备发送给接入网设备。
以标准化的5QI为例，其对应的5G QoS特征可以包括：
(1)资源类型(resource type)，包括GBR、时延敏感(delay critical)的GBR和Non-GBR。其中，Non-GBR QoS流可以使用Non-GBR资源类型。GBR QoS流可以使用GBR资源类型或时延敏感的GBR资源类型。
(2)优先级水平(priority level)，表示5G QoS流间的资源调度优先级，该参数用于区分一个终端设备的各个QoS流，也可用于区分不同终端设备的QoS流。该参数值越小表示优先级越高。
(3)包时延预算(packet delay budget，PDB)，定义了终端设备和锚点UPF网元间数据包传输的时延上限。
(4)包错误率(packet error rate，PER)，定义了一个上限，也就是数据包已经被发送端的链路层(如RLC层)处理了，但没有被对应的接收端提交给上层(如PDCP层)的比率上限。包错误率也可以称为误包率，二者可以相互替换。需要说明的是，对于使用时延敏感的GBR资源类型的GBR QoS流，如果在PDB周期内发送的数据突发小于默认最大数据突发量且QoS流不超过保证流比特率，则延迟大于PDB的数据包被计为丢失。
(5)平均窗口，是针对GBR QoS流定义的，用于相关网元统计GFBR和MFBR。
(6)最大数据突发量(maximum data burst volume，MDBV)，表示5G接入网在一个5G接入网PDB期间需要服务的最大数据量；资源类型为时延敏感的GBR的每个QoS流应与一个MDBV相关联。
举个例子，标准化的5QI的取值为82时，其对应的资源类型为时延敏感的GBR，优先级水平为19，PDB为10ms，PER为10 -4，MDBV为255字节(byte)，平均窗口为2000ms。
三、视频编码
视频可以是由一张张连贯起来的图像(或者说图片、照片等)连续播放组成的，当一秒钟有24张图像快速播放，人眼就会认为这是连续的画面(即视频)。帧率是指每秒钟播放的图像数量，如24帧即每秒钟播放24张图像，60帧即每秒钟播放60张图像，以此类推。一个视频帧可以理解为一张图像(即一个视频帧中可以包括一张图像对应的多个数据包)，当帧率为60帧时，一个视频帧的时长为1000ms/60Hz，约等于16ms。
视频编码即是将视频文件从一种格式转换为另一种格式，从而实现对视频文件进行压缩，以便于视频文件的存储和传输。视频编码的方式可以有多种，比如分级编码方式和非分级编码方式。
其中，分级编码方式可以基于时域进行分级编码，或者也可以基于空间进行分级编码，又或者也可以基于质量进行分级编码，又或者也可以基于时域、空间、质量的任意组合进行分级编码，具体不做限定。在一个示例中，采用分级编码方式编码后的视频流可以包括基本层码流和增强层码流，基本层码流和增强层码流分别为可单独解码的子码流，增强层 码流可以包括一层或多层。基本层码流中可以包括基本层数据包，基本层数据包是视频播放的必要条件，在这种情况下，视频画质较差；而增强层码流中可以包括增强层数据包，增强层数据包是视频播放的补充条件；比如，基本层码流所对应的视频画质为流畅画质，则在基本层码流的基础上叠加第一增强层码流，可以达到标清画质，在高清画质的基础上叠加第二增强层码流可以达到高清画质，在高清画质的基础上叠加第三增强层码流可以达到蓝光画质。也就是说，在基本层码流的基础上叠加的增强层码流越多，则在解码后得到的视频画质越好。需要说明的是，本申请实施例中将以基本层和增强层两层为例进行描述，即本申请实施例中所涉及的增强层可以包括一层或者也可以包括多层。
非分级编码方式的具体实现可以有多种，在一个示例中，采用非分级编码方式编码后的视频流可以包括I帧、P帧和B帧。其中，I帧又称帧内编码帧，是一种自带全部信息的独立帧，无需参考其他图像便可独立进行解码，可以简单理解为一张静态画面；视频序列中的第一个帧始终都是I帧(I帧为关键帧)。P帧又称帧间预测编码帧，需要参考前面的I帧才能进行编码，表示的是当前帧画面与前一帧(前一帧可能是I帧也可能是P帧)的差别，解码时需要用之前缓存的画面叠加上本帧定义的差别，生成最终画面。B帧又称双向预测编码帧，也就是B帧记录的是本帧与前后帧的差别；也就是说，要解码B帧，不仅要取得之前的缓存画面，还要解码之后的画面，通过前后画面的与本帧数据的叠加取得最终的画面。
根据上述相关技术特征的描述，在图3所示意的QoS模型中，每个QoS流对应一组QoS参数，针对QoS流中的所有数据包，接入网设备均是按照该QoS流的QoS参数进行统一调度。然而，当引入视频编码后，映射到同一QoS流中的视频数据包可能包括不同类型的数据包(比如包括基本层数据包和增强层数据包，又比如包括I帧对应的数据包、P帧对应的数据包和B帧对应的数据包)；由于不同类型数据包的QoS要求是不同的，因此，接入网设备若是按照该QoS流的QoS参数进行统一调度，则会导致接入网设备无法精准的对每个数据包进行调度，无法满足不同类型数据包的QoS要求，影响用户的业务体验。
基于此，本申请实施例提供一种通信方法，用于实现对不同类型的数据包进行差异化调度，从而满足不同类型数据包的QoS要求，进而提升用户的业务体验。
下面结合实施例一至实施例三对本申请实施例提供的通信方法进行详细介绍。
实施例一
图5为本申请实施例一提供的通信方法所对应的流程示意图，如图5所示，该方法包括如下步骤：
S501，第一核心网设备向接入网设备发送第一QoS流的配置信息，相应地，接入网设备可以接收第一QoS流的配置信息。其中，第一QoS流的配置信息包括第一QoS流的QoS参数，第一QoS流支持多种类型的数据包，第一QoS流的QoS参数包括多种类型分别对应的QoS参数。
此处，第一核心网设备可以为SMF网元和/或AMF网元，本申请实施例中将以第一核心网设备为AMF网元为例。
(1)针对AMF网元向接入网设备发送第一QoS流的配置信息的实现进行描述。
AMF网元向接入网设备发送第一QoS流的配置信息的实现方式可以有多种。在一种可能的实现方式中，AMF网元可以通过PDU会话资源建立请求(PDU session resource setup  request)消息或者PDU会话资源修改请求(PDU session resource modification request)消息向接入网设备发送第一QoS流的配置信息。
比如，当终端设备有下行业务接收需求时，终端设备可以发起PDU会话建立过程，进而触发AMF网元向接入网设备发送PDU会话资源建立请求消息，PDU会话资源建立请求消息中可以包括待建立的PDU会话的标识以及该PDU会话中的多个QoS流的配置信息，其中多个QoS流可以包括第一QoS流。
又比如，终端设备需要修改已经建立的PDU会话中的第一QoS流，此种情形下，终端设备可以发起PDU会话资源修改过程，进而触发AMF网元向接入网设备发送PDU会话资源修改请求消息，PDU会话资源修改请求消息中可以包括第一QoS流的配置信息。
可以理解地，AMF网元也可以通过其它可能的消息向接入网设备发送第一QoS流的配置信息，具体不做限定。
(2)针对第一QoS流支持多种类型的数据包进行描述。
第一QoS流支持多种类型的数据包，也就是说，在进行数据传输时，UPF网元向接入网设备传输的第一QoS流中可以包括多种类型中的至少一种类型的数据包。
示例性地，多种类型的数据包可以是基于多种可能的依据划分得到的。比如，多种类型的数据包可以包括基本层数据包和增强层数据包(即两种类型的数据包)；又比如，多种类型的数据包可以包括I帧对应的数据包、P帧对应的数据包和B帧对应的数据包这三种类型中的至少两种类型的数据包；又比如，多种类型的数据包可以包括基于时域进行分级编码得到的不同层级对应的数据包(一个层级可以理解为一种类型)；又比如，多种类型的数据包可以包括基于质量进行分级编码得到的不同层级对应的数据包；又比如，多种类型的数据包可以包括基于空间进行分级编码得到的不同层级对应的数据包；又比如，多种类型的数据包可以包括重要数据包和非重要数据包；又比如，多种类型的数据包可以包括时延紧急的数据包和时延非紧急的数据包。本申请实施例中对划分得到多种类型的数据包的依据可以不做限定，也就是说，只要存在不同类型的数据包，且不同类型数据包的QoS参数有所不同，便可以采用本申请实施例中的方法来调度这些数据包。
需要说明的是，本申请实施例中的“类型”也可以替换为其它可能的词语，比如“组”(group)，“子流”，“子QoS流”，具体不做限定。
(3)针对第一QoS流的配置信息进行描述。
第一QoS流的配置信息可以包括第一QoS流的QoS参数，可选地，还可以包括第一QoS流的标识、第一QoS流所支持的数据包所属的多种类型的标识。其中，第一QoS流的QoS参数可以包括多种类型分别对应的QoS参数。比如，第一QoS流所支持的数据包所属的多种类型包括第一类型、第二类型和第三类型，则第一QoS流的QoS参数可以包括第一类型对应的一组QoS参数(称为第一QoS参数)、第二类型对应的一组QoS参数(称为第二QoS参数)以及第三类型对应的一组QoS参数(称为第三QoS参数)。
在一个示例中，第一QoS流的配置信息可以包括第一QoS流的标识，以及如表1所示意的第一QoS流所支持的数据包所属的多种类型的标识与QoS参数的对应关系。
表1：类型的标识与QoS参数的对应关系示例
多种类型的标识 多种类型对应的QoS参数
第一类型的标识 第一QoS参数
第二类型的标识 第二QoS参数
第三类型的标识 第三QoS参数
举例来说，第一类型的数据包可以为I帧对应的数据包，第二类型的数据包可以为P帧对应的数据包，第三型的数据包可以为B帧对应的数据包。以第一类型(即I帧)为例，I帧的标识可以为用于标识I帧的信息，具体不做限定。
示例性地，以第一类型对应的第一QoS参数为例，第一QoS参数可以包括以下至少一项：第一信息，第一信息用于指示第一类型的数据包是否允许丢弃；第二信息，第二信息用于指示第一类型的数据包在设定时间内允许丢弃的个数。比如，当第一信息用于指示第一类型的数据包不允许丢弃时，第一QoS参数也可以不再包括第二信息，或者，第一QoS参数包括的第二信息用于指示第一类型的数据包在设定时间内允许丢弃的个数为0。又比如，当第一信息用于指示第一类型的数据包不允许丢弃时，第二信息可以用于指示第一类型的数据包在设定时间内允许丢弃的个数为n(n为大于0的整数)。需要说明的是，设定时间可以为协议预先约定的一段时间，或者也可以为第二信息指示的一段时间，具体不做限定。
可选地，第一QoS参数还可以包括其它可能的信息，比如5QI、GFBR、MFBR等。
需要说明的是，针对于多种类型中的任意两种类型对应的QoS参数，比如以第一QoS参数和第二QoS参数为例，第一QoS参数与第二QoS参数可以完全不同，比如第一QoS参数所包括的第一信息、第二信息、5QI、GFBR、MFBR和第二QoS参数所包括的第一信息、第二信息、5QI、GFBR、MFBR完全不同。或者，第一QoS参数与第二QoS参数也可以部分不同，比如第一QoS参数所包括的5QI、GFBR、MFBR和第二QoS参数所包括的5QI、GFBR、MFBR相同，但第一QoS参数所包括的第一信息、第二信息和第二QoS参数所包括的第一信息、第二信息不相同。
(4)针对AMF网元获取第一QoS流的配置信息进行描述。
示例性地，在AMF网元向接入网设备发送第一QoS流的配置信息之前，AMF网元需要先获取第一QoS流的配置信息。其中，AMF网元获取第一QoS流的配置信息的实现方式可以有多种，比如，AMF网元可以从SMF网元获取第一QoS流的配置信息。示例性地，SMF网元可以从PCF网元获取业务1中不同数据流对应的QoS参数，业务1中包括视频数据流，视频数据流包括多种类型的数据包，视频数据流对应的QoS参数包括多种类型分别对应的QoS参数，若SMF网元确定第一QoS流用于承载视频数据流，则第一QoS流的QoS参数即为视频数据流对应的QoS参数；进而，SMF网元可以向AMF网元发送第一QoS流的配置信息。需要说明的是，本申请实施例中，对PCF网元生成业务1中不同数据流对应的QoS参数的具体实现可以不做限定。
此外，接入网设备接收到第一QoS流的配置信息后，可以根据第一QoS流的配置信息，对第一QoS流进行处理。示例性地，接入网设备根据第一QoS流的配置信息，对第一QoS流进行处理，可以包括，接入网设备根据第一QoS流的配置信息为第一QoS流配置相应的空口资源，比如配置第一QoS流对应的DRB。
在一个示例中，接入网设备可以根据第一QoS流的配置信息配置第一QoS流对应第一DRB，第一DRB可以关联多个逻辑信道。进一步地，接入网设备还可以配置第一QoS流所支持的多种类型与多个逻辑信道的对应关系，其中一种类型可以对应一个或多个逻辑信道，或者，一个逻辑信道也可以对应两种或两种以上类型。举例来说，第一QoS流所支 持的多种类型包括第一类型、第二类型和第三类型，第一DRB关联的多个逻辑信道包括第一逻辑信道、第二逻辑信道、第三逻辑信道和第四逻辑信道，则接入网设备可以配置第一类型对应第一逻辑信道和第二逻辑信道、第二类型对应第三逻辑信道、第三类型对应第四逻辑信道。本申请实施例中，当某一类型对应多个逻辑信道时，该多个逻辑信道可以用于传输重复的数据包。
需要说明的是，接入网设备配置多种类型与多个逻辑信道的对应关系的方式可以有多种。作为一种可能的实现，接入网设备可以根据多种类型对应的QoS参数，来配置多种类型与多个逻辑信道的对应关系。比如，第一类型对应的QoS参数表明第一类型的数据包的传输可靠性要求较高，而第二类型对应的QoS参数表明第二类型的数据包的传输可靠性要求较低，则第一类型可以在多个逻辑信道上复制/重复传输，第二类型可以在单个逻辑信道上传输，换句话说，第一类型对应的逻辑信道的个数可以大于第二类型对应的逻辑信道的个数。
可以理解地，当第一DRB关联一个逻辑信道时，接入网设备也可以将多种类型的数据包均映射到同一逻辑信道上进行传输。后续，接入网设备在MAC层可以对不同类型的数据包按照其对应的QoS参数进行下行调度，比如第一类型对应的QoS参数表明第一类型对于传输可靠性要求比较高，则MAC层可能使用较低等级的调制和编码方案对第一类型所对应数据包进行传输，或者分配更多的资源用于传输第一类型所对应的数据包。
S502，第二核心网设备向接入网设备发送第一QoS流中的第一数据包，相应地，接入网设备可以接收来自第二核心网设备的第一QoS流中的第一数据包。
示例性地，第二核心网设备可以为UPF网元，UPF网元从应用服务器接收到第一数据包后，可以根据包过滤集合将第一数据包映射至第一QoS流(此时第一数据包可以标记有第一QoS流的标识)，进而发送给接入网设备。
本申请实施例中，UPF网元还可以向接入网设备发送指示信息1，指示信息1用于指示第一数据包所属的类型。比如，指示信息1可以包括第一数据包所属的类型的标识。UPF网元向接入网设备发送第一数据包和指示信息1的方式可以有多种，比如UPF网元向接入网设备发送第二数据包，第二数据包包括第一数据包和指示信息1，指示信息1可以承载于第二数据包的包头中。在一个示例中，由于接入网设备和UPF网元之间的通信可以遵循一定的协议，比如GTP-U协议，GTP-U协议为通用分组无线服务技术(general packet radio service，GPRS)隧道传输协议(GPRS tunnel protocol，GTP)的其中一种协议，因此，UPF网元从应用服务器接收到第一数据包后，可以根据GTP-U协议对第一数据包进行封装(比如添加GTP-U包头)得到第二数据包，第二数据包可以称为GTP-U数据包，指示信息1可以承载于GTP-U包头中。
此外，UPF网元向接入网设备发送指示信息1之前，可以先确定第一数据包所属的类型。UPF网元确定第一数据包所属的类型的方式可以有多种，比如，应用服务器在向UPF网元发送第一数据包时，可以指示第一数据包所属的类型，又比如UPF网元可以根据预设规则确定第一数据包所属的类型，具体不做限定。
S503，接入网设备根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度。
此处，若接入网设备配置了第一QoS流所支持的多种类型与多个逻辑信道的对应关系，则接入网设备根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度之 前，可以根据第一数据包所标记的第一QoS流的标识，将第一数据包映射至第一QoS流对应的第一DRB，进而根据第一数据包所属的类型，将第一数据包映射至第一类型对应的逻辑信道。
作为一种可能的实现，接入网设备根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度，可以包括：接入网设备根据第一数据包所属的类型对应的QoS参数，将第一数据包发送给终端设备；或者，接入网设备根据第一数据包所属的类型对应的QoS参数，丢弃第一数据包。
在一个示例中，假设第一数据包所属的类型为第一类型，第一类型对应第一QoS参数，第一QoS参数中的第一信息指示了第一类型的数据包允许丢弃。接入网设备若确定符合以下情形1、情形2中至少一项，则可以丢弃第一数据包；若确定不符合情形1、情形2，则可以将第一数据包发送给终端设备。其中，情形1为：接入网设备的负载较重，比如接入网设备服务的终端设备的数量大于或等于数量阈值，又比如，接入网设备的资源使用率大于或等于资源使用率阈值；其中，数量阈值、资源使用率阈值可以根据实际情形进行设置，具体不做限定。情形2：接入网设备根据第一数据包的PDB，确定第一数据包超过传输时延要求。
进一步地，假设第一QoS参数中的第二信息指示了第一类型的数据包在设定时间内允许丢弃的个数，则接入网设备在确定是否丢弃第一数据包时，需要满足这个限制，即如果在设定时间内丢弃的数据包的个数已经大于或等于允许丢弃的个数，则可以不丢弃第一数据包，并将第一数据包发送给终端设备。
采用上述方法，由于第一QoS流的QoS参数可以包括多种类型分别对应的QoS参数，使得接入网设备接收到第一QoS流中的数据包后，可以根据数据包所属的类型，采用相应的QoS参数来对该数据包进行下行调度，从而实现对同一QoS流中不同类型的数据包进行差异化调度。
上述实施例一中，是将接入网设备作为一个整体设备进行描述的，在一些可能的情形中，接入网设备也可以包括分离的节点，比如CU和DU，参见图2b所示。
下面将基于上述图2b所示意的CU和DU，结合实施例二和实施例三对本申请实施例提供的通信方法进行描述。
实施例二
图6为本申请实施例二提供的通信方法所对应的流程示意图，如图6所示，该方法包括如下步骤：
S601，第一核心网设备向CU发送第一QoS流的配置信息，相应地，CU可以接收第一QoS流的配置信息。其中，第一QoS流的配置信息包括第一QoS流的QoS参数，第一QoS流支持多种类型的数据包，第一QoS流的QoS参数包括多种类型分别对应的QoS参数。此外，CU接收到第一QoS流的配置信息后，可以根据第一QoS流的配置信息，对所述第一QoS流进行处理。示例性地，CU根据第一QoS流的配置信息，对所述第一QoS流进行处理，可以包括，CU根据第一QoS流的配置信息为第一QoS流配置相应的空口资源，比如配置第一QoS流对应的DRB。
示例性地，上述S601的相关实现可以参见实施例一中S501的描述，不再赘述。
S602，CU向DU发送第一QoS流对应的DRB的配置信息，相应地，DU可以接收第 一QoS流对应的DRB的配置信息。其中，DRB的配置信息包括多种类型分别对应的QoS参数。
在一个示例中，DRB的配置信息可以包括多种类型的标识与QoS参数的对应关系，比如参见表1所示。
S603，第二核心网设备向CU发送第一QoS流中的第一数据包，相应地，CU可以接收来自第二核心网设备的第一QoS流中的第一数据包。
示例性地，S603的相关实现可以参见实施例一中S502的描述，不再赘述。
S604，CU向DU发送第一数据包和指示信息2，相应地，DU可以接收第一数据包和指示信息2。
此处，CU向DU发送第一数据包和指示信息2的方式可以有多种。比如，CU向DU发送第三数据包，第三数据包可以包括第一数据包和指示信息2，指示信息2可以承载于第三数据包的包头中。在一个示例中，第三数据包可以为GTP-U数据包，指示信息2可以承载于第三数据包的GTP-U包头中。
S605，DU根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度。
此处，DU根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度的相关实现，可以参见上述实施例一中接入网设备根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度的描述，不再赘述。
采用上述方法，CU可以向DU发送多种类型分别对应的QoS参数，使得DU接收到数据包后，可以根据数据包所属的类型，采用相应的QoS参数来对该数据包进行下行调度，从而实现同一QoS流中对不同类型的数据包进行差异化调度。
实施例三
图7为本申请实施例三提供的通信方法所对应的流程示意图，如图7所示，该方法包括如下步骤：
S701，第一核心网设备向CU发送第一QoS流的配置信息，相应地，CU接收第一QoS流的配置信息。其中，第一QoS流的配置信息包括第一QoS流的QoS参数，第一QoS流支持多种类型的数据包，第一QoS流的QoS参数包括多种类型分别对应的QoS参数。此外，CU接收到第一QoS流的配置信息后，可以根据第一QoS流的配置信息，对第一QoS流进行处理。示例性地，CU根据第一QoS流的配置信息，对所述第一QoS流进行处理，可以包括，CU根据第一QoS流的配置信息为第一QoS流配置相应的空口资源，比如配置第一QoS流对应的DRB。
示例性地，上述S701的相关实现可以参见实施例一中S501的描述，不再赘述。
S702，CU向DU发送第一QoS流对应的DRB的配置信息，相应地，DU接收第一QoS流对应的DRB的配置信息。其中，DRB的配置信息包括所述多种类型分别对应的QoS参数，可选地，还可以包括指示信息3，指示信息3指示多种类型分别对应的下行隧道地址的个数。
S703，DU向CU发送第一消息，所述第一消息包括多种类型分别对应的下行隧道地址。
本申请实施例中，针对于一个DRB，CU和DU之间可以建立一个或多个隧道，隧道用于将CU的PDCP层的数据包传输给DU的RLC实体(可以理解为下行传输)，和/或， 将DU的RLC实体接收到的数据包传输给CU的PDCP实体(可以理解为上行传输)。每个隧道可以包括上行隧道地址和下行隧道地址，上行隧道地址是指该隧道在CU侧的地址，下行隧道地址是指该隧道在DU侧的地址。
指示信息3指示多种类型分别对应的下行隧道地址的个数，也可以替换为其它可能的描述。比如，指示信息3指示多种类型分别对应的下行隧道地址的个数，可以替换为，指示信息3指示多种类型的数据包是否需要进行重复传输。此外，当指示信息3指示某一类型的数据包需要进行重复传输时，还可以进一步指示重复传输的次数。以第一类型为例，若指示信息3指示第一类型的数据包不需要进行重复传输，则说明第一类型对应的下行隧道地址的个数为1；若指示信息3指示第一类型的数据包需要进行重复传输，且重复传输的次数为k，则说明第一类型对应的下行隧道地址的个数为k。
又比如，指示信息3指示多种类型分别对应的下行隧道地址的个数，可以替换为，指示信息3指示多种类型分别对应的逻辑信道的个数。示例性地，每个下行隧道地址可以对应一个逻辑信道，其中，下行隧道地址与逻辑信道的对应关系可以是DU确定的。可选地，DU可以将下行隧道地址与逻辑信道的对应关系发送给CU；或者，DU也可以单独将第一类型所对应的逻辑信道的标识和/或逻辑信道的配置信息发送给CU；又或者，DU也可以仅将第一类型所对应的逻辑信道中的主逻辑信道的标识和/或主逻辑信道的配置信息发送给CU，以便于CU利用相关信息生成RRC消息，并发送给终端设备，使得终端设备可以获知相关信息，以接收第一类型的数据包。
需要说明的是，上述重复传输可以是指PDCP层的重复传输，具体来说，数据包在PDCP层复制成多个相同的数据包(也就是重复包)，然后这多个数据包分别递交给多个不同的RLC层实体进行传输，进而通过不同的逻辑信道传输到MAC层实体。需要注意的是，通常所说的重传是指重新传输(retransmission)，而本申请实施例中的重复传输(duplication transmission)并不是重新传输。重新传输是指同一个数据包发送失败后的再次发送，或者是同一个数据包的连续多次发送，而重复传输是将一个数据包复制多个数据包，分别放到多个逻辑信道上传输，这里的“重复”，也可以理解为“复制”。
本申请实施例中，指示信息3指示多种类型分别对应的下行隧道地址的个数的方式可以有多种，下面结合示例1至示例4描述几种可能的方式。
示例1
指示信息3可以包括多种类型分别对应的上行隧道地址，其中，多种类型中每种类型可以对应一个或多个上行隧道地址。也就是说，指示信息3通过指示多种类型分别对应的上行隧道地址的个数，来隐式指示多种类型分别对应的下行隧道地址的个数。
以第一类型为例，当第一类型对应一个上行隧道地址时，表示第一类型对应的下行隧道地址的个数为1，此种情形下，可以理解为指示信息3通过隐式的方式指示第一类型的数据包不进行重复传输；当第一类型对应两个上行隧道地址时，表示第一类型对应的下行隧道地址的个数为2，此种情形下，可以理解为指示信息3通过隐式的方式指示第一类型的数据包需要进行重复传输，且重复传输的次数为2。也就是说，指示信息3中所包括的第一类型对应的上行隧道地址的个数即为第一类型对应的下行隧道地址的个数或者第一类型对应的逻辑信道的个数。需要说明的是，第一类型对应的上行隧道地址，可以是指，DU向CU发送第一类型的数据包时，承载第一类型的数据包的隧道在CU侧的地址；第一类型对应的下行隧道地址，可以是指，CU向DU发送第一类型的数据包时，承载第一类 型的数据包的隧道在DU侧的地址。
在该示例中，假设多种类型包括第一类型、第二类型和第三类型；其中，第一类型对应第一QoS参数，第二类型对应第二QoS参数，第三类型对应第三QoS参数；第一类型对应的上行隧道地址包括上行隧道地址1，第二类型对应的上行隧道地址包括上行隧道地址2和上行隧道地址3，第三类型对应的上行隧道地址包括上行隧道地址4；则DRB的配置信息可以包括如表2所示意的内容。
表2：DRB的配置信息所包括的内容示例
Figure PCTCN2021070710-appb-000001
相应地，DU接收到DRB的配置信息后，可以针对每个上行隧道地址分配下行隧道地址，比如针对上行隧道地址1分配下行隧道地址1、针对上行隧道地址2分配下行隧道地址2、针对上行隧道地址3分配下行隧道地址3、针对上行隧道地址4分配下行隧道地址4。进而，DU向CU发送第一消息，第一消息可以包括多种类型分别对应的下行隧道地址，可选地，第一消息还可以包括下行隧道地址与上行隧道地址的对应关系。参见表3所示，为第一消息所包括的内容的一种示例。
表3：第一消息所包括的内容的示例
Figure PCTCN2021070710-appb-000002
示例2
指示信息3可以包括多种类型分别对应的下行隧道地址(或上行隧道地址)的个数。其中，多种类型中每种类型可以对应一个或多个下行隧道地址。以第一类型为例，若指示信息3所包括的第一类型对应的下行隧道地址的个数为1，则可以理解为指示信息3通过隐式的方式指示第一类型的数据包不进行重复传输，或者指示信息3通过隐式的方式指示第一类型对应的逻辑信道的个数为1；若指示信息3所包括的第一类型对应的下行隧道地址的个数为k(k为大于1的整数)，则可以理解为指示信息3通过隐式的方式指示第一类型的数据包需要进行重复传输，或者，指示信息3通过隐式的方式指示第一类型对应的逻辑信道的个数为k。
在该示例中，假设多种类型包括第一类型、第二类型和第三类型；其中，第一类型对应第一QoS参数，第二类型对应第二QoS参数，第三类型对应第三QoS参数；第一类型对应的下行隧道地址的个数为1，第二类型对应的下行隧道地址的个数为2，第三类型对应的下行隧道地址的个数为4；则DRB的配置信息可以包括如表4所示意的内容。
表4：DRB的配置信息所包括的内容示例
Figure PCTCN2021070710-appb-000003
相应地，DU接收到DRB的配置信息后，可以根据多种类型分别对应的下行隧道地址的个数来分配下行隧道地址，比如针对第一类型分配下行隧道地址1、针对第二类型分配下行隧道地址2、下行隧道地址3、针对第三类型分配下行隧道地址4。进而，向CU发送第一消息，第一消息可以包括多种类型分别对应的下行隧道地址。参见表5所示，为第一消息所包括的内容的一种示例。
表5：第一消息所包括的内容的示例
Figure PCTCN2021070710-appb-000004
示例3
指示信息3可以包括多种类型分别对应的逻辑信道的个数。其中，多种类型中每种类型可以对应一个或多个逻辑信道。以第一类型为例，若指示信息3所包括的第一类型对应的逻辑信道的个数为1，则可以理解为指示信息3通过隐式的方式指示第一类型对应的下行隧道地址的个数为1，或者指示信息3通过隐式的方式指示第一类型的数据包不进行重复传输。若指示信息3所包括的第一类型对应的逻辑信道的个数为k，则可以理解为指示信息3通过隐式的方式指示第一类型对应的下行隧道地址的个数为k，或者指示信息3通过隐式的方式指示第一类型的数据包需要进行重复传输。
示例4
指示信息3可以包括多种类型分别对应的指示信息，比如多种类型包括第一类型、第二类型和第三类型，则指示信息3可以包括第一类型对应的指示信息31、第二类型对应的指示信息32、第三类型对应的指示信息33。以第一类型为例，第一类型对应的指示信息31用于指示第一类型的数据包是否需要进行重复传输。此种情形下，可以理解为，指示信息3通过显式的方式指示多种类型的数据包是否需要进行重复传输。
需要说明的是，上述示例3和示例4的具体实现可以适应性参照示例2，不再赘述。
S704，第二核心网设备向CU发送第一QoS流中的第一数据包，相应地，CU可以接收第一数据包。
示例性地，S704的相关实现可以参见实施例一中S502的描述，不再赘述。
S705，CU通过第一隧道向DU发送第一数据包，相应地，DU可以通过第一隧道接收第一数据包。其中，第一隧道的下行隧道地址为第一数据包所属的类型对应的下行隧道地址。
此处，CU接收到第一数据包后，可以获知第一数据包所属的类型。比如，第一数据包所属的类型为第一类型，此种情形下，由于第一类型对应的下行隧道地址为下行隧道地址1，则CU可以通过下行隧道地址为下行隧道地址1的隧道(比如隧道1)向DU发送第一数据包。又比如，第一数据包所属的类型为第二类型，此种情形下，由于第一类型对应的下行隧道地址包括下行隧道地址2和下行隧道地址3，则CU可以将第一数据包复制为两个第一数据包，并分别通过下行隧道地址为下行隧道地址2的隧道(比如隧道2)和下行隧道地址为下行隧道地址3的隧道(比如隧道3)向DU发送第一数据包。
S706，DU根据第一数据包所属的类型对应的QoS参数，对第一数据包进行下行调度。
此处，假设第一数据包所属的类型为第一类型，则DU通过第一隧道接收到第一数据包后，可以根据第一隧道的下行隧道地址与逻辑信道的对应关系，将第一数据包映射至相应的逻辑信道。进一步地，由于第一隧道的下行隧道地址为第一类型对应的下行隧道地址，进而DU可以根据第一类型对应的QoS参数对第一数据包进行下行调度。
采用上述方法，CU可以向DU发送DRB的配置信息，DRB的配置信息包括所述多种类型分别对应的QoS参数和指示信息3，指示信息3用于指示多种类型分别对应的下行隧道地址的个数；进而DU可以根据DRB的配置信息为多种类型分别分配下行隧道地址，并反馈给CU。如此，CU可以根据第一数据包所属的类型，通过相应的隧道(比如第一隧道)向DU发送第一数据包，DU通过第一隧道接收到第一数据包后，可以采用相应的QoS参数对第一数据包进行下行调度，从而实现对同一QoS流中不同类型的数据包进行差异化调度。
针对于上述实施例一至实施例三，需要说明的是：
(1)实施例一至实施例三所描述的各个流程图的步骤编号仅为执行流程的一种示例，并不构成对步骤执行的先后顺序的限制，本申请实施例中相互之间没有时序依赖关系的步骤之间没有严格的执行顺序。此外，各个流程图中所示意的步骤并非全部是必须执行的步骤，可以根据实际需要在各个流程图的基础上增添或者删除部分步骤。
(2)上述侧重描述了实施例一至实施例三中不同实施例之间的差异之处，除差异之处的其它内容，实施例一至实施例三之间可以相互参照。
(3)上述实施例一至实施例三中采用了一些5G通信系统中的消息，但在具体实施中，可能使用不同的消息或消息名称，本申请实施例对此不做限制。
上述主要从设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，接入网设备、核心网设备或终端设备可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对接入网设备、核心网设备或终端设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能 单元的形式实现。
在采用集成的单元的情况下，图8示出了本申请实施例中所涉及的装置的可能的示例性框图。如图8所示，装置800可以包括：处理单元802和通信单元803。处理单元802用于对装置800的动作进行控制管理。通信单元803用于支持装置800与其他设备的通信。可选地，通信单元803也称为收发单元，可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。装置800还可以包括存储单元801，用于存储装置800的程序代码和/或数据。
该装置800可以为上述实施例中的接入网设备、或者还可以为设置在接入网设备中的芯片。处理单元802可以支持装置800执行上文中各方法示例中接入网设备的动作。或者，处理单元802主要执行方法示例中的接入网设备的内部动作，通信单元803(包括接收单元和发送单元)可以支持装置800与其它设备之间的通信。
具体地，在一个实施例中，接收单元用于：接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；接收来自第二核心网设备的所述第一QoS流的第一数据包；处理单元用于：根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
在一种可能的设计中，所述接收单元还用于：接收来自所述第二核心网设备的第一指示信息，所述第一指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，所述第一数据包和所述第一指示信息承载于来自所述第二核心网设备的第二数据包，所述第一指示信息承载于所述第二数据包的包头中。
在一种可能的设计中，所述处理单元还用于：根据所述第一数据包所属的类型和逻辑信道的对应关系，将所述第一数据包映射至所述第一数据包所属的类型对应的逻辑信道。
在一种可能的设计中，所述多种类型包括第一类型，所述第一类型对应的QoS参数包括以下至少一项：第一信息，所述第一信息用于指示所述第一类型的数据包是否允许丢弃；第二信息，所述第二信息用于指示所述第一类型的数据包在设定时间内允许丢弃的个数。
该装置800可以为上述实施例中的CU或者设置在CU中的芯片。处理单元802可以支持装置800执行上文中各方法示例中CU的动作。或者，处理单元802主要执行方法示例中的CU的内部动作，通信单元803(包括接收单元和发送单元)可以支持装置800与其它设备之间的通信。
具体地，在一个实施例中，接收单元用于：接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；发送单元用于：向DU发送所述DRB的配置信息，所述DRB的配置信息包括所述多种类型分别对应的QoS参数。
在一种可能的设计中，所述接收单元还用于：接收来自第二核心网设备的所述第一QoS流的第一数据包；所述发送单元还用于：向所述DU发送所述第一数据包和第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，所述发送单元具体用于：向所述DU发送第三数据包，所述第三数据包包括所述第一数据包和所述第二指示信息，所述第二指示信息承载于所述第三数据包的包头中。
在一种可能的设计中，所述发送单元还用于：向所述DU发送第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；所述接收单元还用于：接收来自所述DU的第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
在一种可能的设计中，所述接收单元还用于：接收来自第二核心网设备的所述第一QoS流的第一数据包；所述发送单元还用于：通过第一隧道向所述DU发送所述第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
该装置800可以为上述实施例中的DU或者设置在DU中的芯片。处理单元802可以支持装置800执行上文中各方法示例中DU的动作。或者，处理单元802主要执行方法示例中的DU的内部动作，通信单元803(包括接收单元和发送单元)可以支持装置800与其它设备之间的通信。
具体地，在一个实施例中，接收单元用于：接收来自CU的DRB的配置信息，所述DRB对应第一QoS流，所述第一QoS流支持多种类型的数据包，所述DRB的配置信息包括所述多种类型分别对应的QoS参数；以及，接收来自所述CU的第一数据包；处理单元用于：根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
在一种可能的设计中，所述接收单元还用于：接收来自所述CU的第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
在一种可能的设计中，所述第一数据包和所述第二指示信息承载于来自所述CU的第三数据包，所述第二指示信息承载于所述第三数据包的包头中。
在一种可能的设计中，所述接收单元还用于：接收来自所述CU的第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；所述发送单元用于：向CU发送第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
在一种可能的设计中，所述接收单元还用于：通过第一隧道接收来自CU的第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
该装置800可以为上述实施例中的第一核心网设备、或者还可以为设置在第一核心网设备中的芯片。处理单元802可以支持装置800执行上文中各方法示例中第一核心网设备的动作。或者，处理单元802主要执行方法示例中的第一核心网设备的内部动作，通信单元803可以支持装置800与其它设备之间的通信。
具体地，在一个实施例中，处理单元802用于：确定第一QoS流的配置信息；通信单元803用于：向接入网设备或CU发送所述第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数。
该装置800可以为上述实施例中的第二核心网设备、或者还可以为设置在第二核心网设备中的芯片。处理单元802可以支持装置800执行上文中各方法示例中第二核心网设备的动作。或者，处理单元802主要执行方法示例中的第二核心网设备的内部动作，通信单元803可以支持装置800与其它设备之间的通信。
具体地，在一个实施例中，通信单元803用于：接收来自应用服务器的第一数据包；以及，向接入网设备或CU发送所述第一数据包和指示信息，所述指示信息指示所述第一数据包所属的类型。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理 元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各操作或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是处理器，比如通用中央处理器(central processing unit，CPU)，或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
参见图9，为本申请实施例提供的一种接入网设备的结构示意图，该接入网设备(或基站)可应用于如图1所示的系统架构中，执行上述方法实施例中接入网设备的功能。接入网设备90可包括一个或多个DU 901和一个或多个CU 902。所述DU 901可以包括至少一个天线9011，至少一个射频单元9012，至少一个处理器9013和至少一个存储器9014。所述DU 901部分主要用于射频信号的收发以及射频信号与基带信号的转换，以及部分基带处理。CU902可以包括至少一个处理器9022和至少一个存储器9021。
所述CU 902部分主要用于进行基带处理，对接入网设备进行控制等。所述DU 901与CU 902可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。所述CU 902为接入网设备的控制中心，也可以称为处理单元，主要用于完成基带处理功能。例如所述CU 902可以用于控制接入网设备执行上述方法实施例中关于接入网设备的操作流程。
此外，可选的，接入网设备90可以包括一个或多个射频单元，一个或多个DU和一个或多个CU。其中，DU可以包括至少一个处理器9013和至少一个存储器9014，射频单元可以包括至少一个天线9011和至少一个射频单元9012，CU可以包括至少一个处理器9022和至少一个存储器9021。
在一个实例中，所述CU902可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器9021和处理器9022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。所述DU901可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如5G网)，也可以分别支持不同 接入制式的无线接入网(如LTE网，5G网或其他网)。所述存储器9014和处理器9013可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
图9所示的接入网设备能够实现上述方法实施例中涉及接入网设备的各个过程，图9所示的CU能够实现上述方法实施例中涉及CU的各个过程，图9所示的DU能够实现上述方法实施例中涉及DU的各个过程。图9所示的接入网设备或CU或DU中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
参考图10，为本申请实施例提供的一种核心网设备的结构示意图。其可以为以上实施例中的第一核心网设备或第二核心网设备，用于实现以上实施例中第一核心网设备或第二核心网设备的操作。
如图10所示，核心网设备1000可包括处理器1001、存储器1002以及接口电路1003。处理器1001可用于对通信协议以及通信数据进行处理，以及对通信装置进行控制。存储器1002可用于存储程序和数据，处理器1001可基于该程序执行本申请实施例中由AMF网元或SMF网元执行的方法。接口电路1003可用于核心网设备1000与其他设备进行通信，该通信可以为有线通信或无线通信，该接口电路例如可以是服务化通信接口。
以上存储器1002也可以是外接于核心网设备1000的，此时核心网设备1000可包括接口电路1003以及处理器1001。以上接口电路1003也可以是外接于核心网设备1000的，此时核心网设备1000可包括存储器1002以及处理器1001。当接口电路1003以及存储器1002均外接于核心网设备1000时，通信装置1000可包括处理器1001。
图10所示的核心网设备能够实现上述方法实施例中涉及第一核心网设备或第二核心网设备的各个过程。图10所示的核心网设备中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
本申请实施例中的术语“系统”和“网络”可被互换使用。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如“A，B和C中的至少一个”包括A，B，C，AB，AC，BC或ABC。以及，除非有特别说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或 方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (42)

  1. 一种通信方法，其特征在于，所述方法适用于接入网设备或者所述接入网设备中的芯片，所述方法包括：
    接收来自第一核心网设备的第一服务质量QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；
    接收来自第二核心网设备的所述第一QoS流的第一数据包；
    根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收来自所述第二核心网设备的第一指示信息，所述第一指示信息指示所述第一数据包所属的类型。
  3. 根据权利要求2所述的方法，其特征在于，所述第一数据包和所述第一指示信息承载于来自所述第二核心网设备的第二数据包，所述第一指示信息承载于所述第二数据包的包头中。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第一数据包所属的类型和逻辑信道的对应关系，将所述第一数据包映射至所述第一数据包所属的类型对应的逻辑信道。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述多种类型包括第一类型，所述第一类型对应的QoS参数包括以下至少一项：
    第一信息，所述第一信息用于指示所述第一类型的数据包是否允许丢弃；
    第二信息，所述第二信息用于指示所述第一类型的数据包在设定时间内允许丢弃的个数。
  6. 一种通信方法，其特征在于，所述方法适用于集中式单元CU或者所述CU中的芯片，所述方法包括：
    接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；
    向DU发送所述第一QoS流对应的数据无线承载DRB的配置信息，所述DRB的配置信息包括所述多种类型分别对应的QoS参数。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    接收来自第二核心网设备的所述第一QoS流的第一数据包；
    向所述DU发送所述第一数据包和第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
  8. 根据权利要求7所述的方法，其特征在于，向所述DU发送所述第一数据包和所述第二指示信息，包括：
    向所述DU发送第三数据包，所述第三数据包包括所述第一数据包和所述第二指示信息，所述第二指示信息承载于所述第三数据包的包头中。
  9. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    向所述DU发送第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧 道地址的个数；
    接收来自所述DU的第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    接收来自第二核心网设备的所述第一QoS流的第一数据包；
    通过第一隧道向所述DU发送所述第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
  11. 一种通信方法，其特征在于，所述方法适用于分布式单元DU或者所述DU中的芯片，所述方法包括：
    接收来自CU的DRB的配置信息，所述DRB对应第一QoS流，所述第一QoS流支持多种类型的数据包，所述DRB的配置信息包括所述多种类型分别对应的QoS参数；
    接收来自所述CU的第一数据包；
    根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    接收来自所述CU的第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
  13. 根据权利要求12所述的方法，其特征在于，所述第一数据包和所述第二指示信息承载于来自所述CU的第三数据包，所述第二指示信息承载于所述第三数据包的包头中。
  14. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    接收来自所述CU的第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；
    向CU发送第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
  15. 根据权利要求14所述的方法，其特征在于，接收来自所述CU的第一数据包，包括：
    通过第一隧道接收来自CU的第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
  16. 一种通信装置，其特征在于，所述装置包括：
    接收单元，用于接收来自第一核心网设备的第一服务质量QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；以及，接收来自第二核心网设备的所述第一QoS流的第一数据包；
    处理单元，用于根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
  17. 根据权利要求16所述的装置，其特征在于，所述接收单元还用于：接收来自所述第二核心网设备的第一指示信息，所述第一指示信息指示所述第一数据包所属的类型。
  18. 根据权利要求17所述的装置，其特征在于，所述第一数据包和所述第一指示信息承载于来自所述第二核心网设备的第二数据包，所述第一指示信息承载于所述第二数据包的包头中。
  19. 根据权利要求16至18中任一项所述的装置，其特征在于，所述处理单元还用于：根据所述第一数据包所属的类型和逻辑信道的对应关系，将所述第一数据包映射至所述第一数据包所属的类型对应的逻辑信道。
  20. 根据权利要求16至19中任一项所述的装置，其特征在于，所述多种类型包括第一 类型，所述第一类型对应的QoS参数包括以下至少一项：
    第一信息，所述第一信息用于指示所述第一类型的数据包是否允许丢弃；
    第二信息，所述第二信息用于指示所述第一类型的数据包在设定时间内允许丢弃的个数。
  21. 一种通信装置，其特征在于，所述装置包括：
    接收单元，用于接收来自第一核心网设备的第一QoS流的配置信息，所述第一QoS流的配置信息包括所述第一QoS流的QoS参数；其中，所述第一QoS流支持多种类型的数据包，所述第一QoS流的QoS参数包括所述多种类型分别对应的QoS参数；
    发送单元，用于向DU发送所述第一QoS流对应的数据无线承载DRB的配置信息，所述DRB的配置信息包括所述多种类型分别对应的QoS参数。
  22. 根据权利要求21所述的装置，其特征在于，所述接收单元还用于：接收来自第二核心网设备的所述第一QoS流的第一数据包；
    所述发送单元还用于：向所述DU发送所述第一数据包和第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
  23. 根据权利要求22所述的装置，其特征在于，所述发送单元具体用于：向所述DU发送第三数据包，所述第三数据包包括所述第一数据包和所述第二指示信息，所述第二指示信息承载于所述第三数据包的包头中。
  24. 根据权利要求21所述的装置，其特征在于，所述发送单元还用于：向所述DU发送第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；
    所述接收单元还用于：接收来自所述DU的第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
  25. 根据权利要求24所述的装置，其特征在于，所述接收单元还用于：接收来自第二核心网设备的所述第一QoS流的第一数据包；
    所述发送单元还用于：通过第一隧道向所述DU发送所述第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
  26. 一种通信装置，其特征在于，所述装置包括：
    接收单元，用于接收来自CU的DRB的配置信息，所述DRB对应第一QoS流，所述第一QoS流支持多种类型的数据包，所述DRB的配置信息包括所述多种类型分别对应的QoS参数；以及，接收来自所述CU的第一数据包；
    处理单元，用于根据所述第一数据包所属的类型对应的QoS参数，对所述第一数据包进行下行调度。
  27. 根据权利要求26所述的装置，其特征在于，所述接收单元还用于：接收来自所述CU的第二指示信息，所述第二指示信息指示所述第一数据包所属的类型。
  28. 根据权利要求27所述的装置，其特征在于，所述第一数据包和所述第二指示信息承载于来自所述CU的第三数据包，所述第二指示信息承载于所述第三数据包的包头中。
  29. 根据权利要求26所述的装置，其特征在于，所述接收单元还用于：接收来自所述CU的第三指示信息，所述第三指示信息指示所述多种类型分别对应的下行隧道地址的个数；
    所述装置还包括发送单元，所述发送单元用于：向CU发送第一消息，所述第一消息包括所述多种类型分别对应的下行隧道地址。
  30. 根据权利要求29所述的装置，其特征在于，所述接收单元还用于：通过第一隧道 接收来自CU的第一数据包，所述第一隧道的下行隧道地址为所述第一数据包所属的类型对应的下行隧道地址。
  31. 一种通信装置，其特征在于，包括用于执行如权利要求1至5中任一项所述方法的模块。
  32. 一种通信装置，其特征在于，包括用于执行如权利要求6至10中任一项所述方法的模块。
  33. 一种通信装置，其特征在于，包括用于执行如权利要求11至15中任一项所述方法的模块。
  34. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求1至5中任一项所述的方法。
  35. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求6至10中任一项所述的方法。
  36. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于实现如权利要求11至15中任一项所述的方法。
  37. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至5中任一项所述的方法。
  38. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求6至10中任一项所述的方法。
  39. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求11至15中任一项所述的方法。
  40. 一种通信系统，其特征在于，所述通信系统包括如权利要求32、35或38中任一项所述的通信装置和如权利要求33、36或39中任一项所述的通信装置。
  41. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至15中任一项所述的方法。
  42. 一种计算机程序产品，其特征在于，当计算机读取并执行所述计算机程序产品时，使得计算机执行权利要求1至15中任一项所述的方法。
PCT/CN2021/070710 2021-01-07 2021-01-07 一种通信方法及装置 WO2022147727A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2021/070710 WO2022147727A1 (zh) 2021-01-07 2021-01-07 一种通信方法及装置
EP21916785.5A EP4262314A4 (en) 2021-01-07 2021-01-07 COMMUNICATION METHOD AND DEVICE
CN202180089087.2A CN116746264A (zh) 2021-01-07 2021-01-07 一种通信方法及装置
US18/347,950 US20230354334A1 (en) 2021-01-07 2023-07-06 Communication method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/070710 WO2022147727A1 (zh) 2021-01-07 2021-01-07 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/347,950 Continuation US20230354334A1 (en) 2021-01-07 2023-07-06 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2022147727A1 true WO2022147727A1 (zh) 2022-07-14

Family

ID=82357798

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070710 WO2022147727A1 (zh) 2021-01-07 2021-01-07 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20230354334A1 (zh)
EP (1) EP4262314A4 (zh)
CN (1) CN116746264A (zh)
WO (1) WO2022147727A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065524A1 (zh) * 2022-09-29 2024-04-04 富士通株式会社 分组数据汇聚协议实体建立、分组数据汇聚协议实体建立指示装置以及方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638852A (zh) * 2011-02-12 2012-08-15 电信科学技术研究院 一种基于服务质量的调度方法、设备及系统
CN102932852A (zh) * 2011-08-11 2013-02-13 中兴通讯股份有限公司 业务调度方法及装置
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备
CN109600664A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 业务传输方法和装置
WO2020102621A1 (en) * 2018-11-16 2020-05-22 Idac Holdings, Inc. Quality of service adaptation for pc5 reference point communication
CN111343667A (zh) * 2018-12-19 2020-06-26 华为技术有限公司 一种通信方法及通信装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9055612B2 (en) * 2008-02-11 2015-06-09 Qualcomm Incorporated Quality of service continuity
US9497771B2 (en) * 2014-04-18 2016-11-15 Apple Inc. Deterministic RRC connections
EP3035759B1 (en) * 2014-12-19 2017-10-18 Wipro Limited System and method for adaptive downlink scheduling for wireless networks
EP3402282B1 (en) * 2016-01-08 2020-11-18 Fujitsu Limited Communication system, communication method and base station
US10523583B2 (en) * 2016-09-16 2019-12-31 At&T Mobility Ii Llc Media-aware radio access network packet scheduling
US10855814B2 (en) * 2017-10-20 2020-12-01 Comcast Cable Communications, Llc Non-access stratum capability information

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638852A (zh) * 2011-02-12 2012-08-15 电信科学技术研究院 一种基于服务质量的调度方法、设备及系统
CN102932852A (zh) * 2011-08-11 2013-02-13 中兴通讯股份有限公司 业务调度方法及装置
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备
CN109600664A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 业务传输方法和装置
WO2020102621A1 (en) * 2018-11-16 2020-05-22 Idac Holdings, Inc. Quality of service adaptation for pc5 reference point communication
CN111343667A (zh) * 2018-12-19 2020-06-26 华为技术有限公司 一种通信方法及通信装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
APPLE: "Handling of QoS flow description without associated QoS rule", 3GPP DRAFT; C1-205880, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20201015 - 20201023, 7 October 2020 (2020-10-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051950659 *
See also references of EP4262314A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065524A1 (zh) * 2022-09-29 2024-04-04 富士通株式会社 分组数据汇聚协议实体建立、分组数据汇聚协议实体建立指示装置以及方法

Also Published As

Publication number Publication date
US20230354334A1 (en) 2023-11-02
EP4262314A4 (en) 2024-01-10
EP4262314A1 (en) 2023-10-18
CN116746264A (zh) 2023-09-12

Similar Documents

Publication Publication Date Title
EP3447978B1 (en) Data transmission method and device
WO2021219098A1 (zh) 一种通信方法及装置
WO2021259112A1 (zh) 一种业务传输方法及装置
WO2021197251A1 (zh) 一种通信方法及装置
WO2022001640A1 (zh) 数据传输的方法和装置
WO2021114107A1 (zh) 一种数据传输方法及装置
TW201922021A (zh) 方法、設備、電腦程式產品及電腦程式
US20230354334A1 (en) Communication method and apparatus
WO2021056589A1 (zh) 一种数据传输方法及装置
WO2021218593A1 (zh) 一种通信方法及装置
WO2022012361A1 (zh) 一种通信方法及装置
JP7478749B2 (ja) 無線ベアラ確立方法及び装置
CN116723582A (zh) 通信方法和装置
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2022198613A1 (zh) 一种媒体数据传输方法及通信装置
WO2023171212A1 (ja) 無線端末、無線アクセスネットワークノード、及びこれらの方法
WO2023185769A1 (zh) 通信方法、通信装置和通信系统
WO2022178778A1 (zh) 一种数据传输方法及通信装置
WO2023070392A1 (zh) 数据传输方法、设备及存储介质
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置
WO2024027615A1 (zh) 一种通信方法，通信装置及通信系统
WO2024098267A1 (zh) 数据传输装置、数据发送装置以及方法
JP7450030B2 (ja) 基地局、基地局の制御方法、及びセルラ通信システム
WO2021254238A1 (zh) 一种通信方法及装置
WO2023171211A1 (ja) 無線端末及びその方法

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: 21916785

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180089087.2

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2021916785

Country of ref document: EP

Effective date: 20230711

NENP Non-entry into the national phase

Ref country code: DE