CN116867000A

CN116867000A - Data transmission method and communication device

Info

Publication number: CN116867000A
Application number: CN202210309935.2A
Authority: CN
Inventors: 曹佑龙; 秦熠; 陈二凯; 范强
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-28
Filing date: 2022-03-28
Publication date: 2023-10-10
Also published as: WO2023185608A1

Abstract

The application provides a data transmission method and a communication device, wherein the method comprises the following steps: the access network equipment acquires a first QoS identifier and a second QoS identifier from the QoS configuration information, wherein the first QoS identifier and the second QoS identifier indicate that a first QoS data flow and a second QoS data flow are respectively mapped to different radio bearers; the access network device maps the first QoS data flow and the second QoS data flow to a first wireless bearing and a second wireless bearing respectively, sends the data of the first QoS data flow to the terminal device through the first wireless bearing, and sends the data of the second QoS data flow to the terminal device through the second wireless bearing. The scheme of the application can ensure that the access network equipment accurately distinguishes the data packets with different importance in the XR service, realizes the transmission of unequal importance, is beneficial to reasonably scheduling the priority of the data packets and further improves the user experience.

Description

Data transmission method and communication device

Technical Field

The present application relates to the field of communications, and more particularly, to a method of data transmission and a communication apparatus.

Background

With the development of the fifth generation (5th generation,5G) communication system, the data transmission delay is continuously reduced, the transmission capacity is larger and larger, and the 5G communication system gradually permeates some multimedia services with stronger real-time performance, for example, video transmission, cloud Gaming (CG), extended reality (XR), tactile Internet (TI), and the like, wherein XR includes Virtual Reality (VR) and augmented reality (augmented reality, AR). For a service with strong real-time performance like XR, how to guarantee the service quality (quality of service, qoS) of the user has become a key problem in current research.

Due to factors such as source end coding processing, fixed network/core network transmission and the like, qoS configuration of the current XR service in the physical layer transmission process cannot meet the transmission requirement of application layer data, so that proper transmission guarantee cannot be provided for data transmission of the XR service, and user experience is affected.

Disclosure of Invention

The application provides a data transmission method and a communication device, which are beneficial to meeting the transmission requirement of application layer data during physical layer transmission, thereby providing proper transmission guarantee for data transmission and improving user experience.

In a first aspect, a method for data transmission is provided, where the method may be performed by an access network device, or may also be performed by a chip or a circuit configured in the access network device, or may also be performed by a logic module or software that can implement all or part of the functions of the access network device. The application is not limited in this regard.

The method comprises the following steps: receiving quality of service, qoS, configuration information from a core network element, the QoS configuration information comprising a first QoS identifier and a second QoS identifier, the first QoS identifier indicating a QoS for a first QoS data flow and the second QoS identifier indicating a QoS for a second QoS data flow, the first QoS identifier and the second QoS identifier further indicating that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively; mapping the first QoS data flow and the second QoS data flow to a first radio bearer and a second radio bearer respectively, sending the data of the first QoS data flow to a terminal device through the first radio bearer, and sending the data of the second QoS data flow to the terminal device through the second radio bearer.

According to the scheme of the embodiment of the application, the access network equipment can obtain the first QoS identifier and the second QoS identifier according to the QoS configuration information, the first QoS identifier and the second QoS identifier require or suggest that the access network equipment respectively map the first QoS data flow and the second QoS data flow to different radio bearers, and respectively map the first QoS data flow and the second QoS data flow to the first radio bearer and the second radio bearer and send the first QoS data flow and the second QoS data flow to the terminal equipment, so that proper transmission guarantee is provided for data transmission of XR service, and user experience is improved.

In a second aspect, a method for data transmission is provided, where the method may be performed by a core network device, or may also be performed by a chip or a circuit configured in the core network device, or may also be performed by a logic module or software that can implement all or part of the functions of the core network device. The application is not limited in this regard.

The method comprises the following steps: sending quality of service, qoS, configuration information to an access network device, the QoS configuration information comprising a first QoS identifier and a second QoS identifier, the first QoS identifier indicating a QoS for a first QoS data flow and the second QoS identifier indicating a QoS for a second QoS data flow, the first QoS identifier and the second QoS identifier further indicating that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

According to the scheme of the embodiment of the application, the core network equipment can send QoS configuration information to the access network equipment, wherein the QoS configuration information comprises a first QoS identifier and a second QoS identifier, the first QoS identifier and the second QoS identifier are used for requiring or suggesting that the access network equipment respectively map a first QoS data flow and a second QoS data flow on different radio bearers, and respectively map the first QoS data flow and the second QoS data flow to the first radio bearer and the second radio bearer and send the first QoS data flow and the second QoS data flow to the terminal equipment, so that proper transmission guarantee is provided for data transmission of XR service, and user experience is improved. Wherein the core network device may be a session management function (session management function, SMF) network element.

In the application, when the access network equipment establishes a protocol data unit (protocol data unit, PDU) session with the SMF network element, the QoS flow with synchronous association is established, and in the establishment process, the SMF network element sends QoS configuration information to the access network equipment, wherein the QoS configuration information comprises a first QoS identifier and a second QoS identifier.

The QoS configuration information may be, for example, a QoS profile.

Illustratively, the first QoS identifier and the second QoS identifier may be 5G QoS identifiers (5G quality identifier,5QI).

Wherein the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively, and one possible understanding is that the SMF network element suggests or needs or directs or prefers that the access network device maps the first QoS data flow and the second QoS data flow to different access network resources, respectively, in other words, the access network device may not perform a corresponding mapping action after receiving the QoS identifiers. The embodiment of the present application is not limited thereto.

With reference to the first aspect and the second aspect, in certain embodiments of the first aspect and the second aspect, the method further includes: the first QoS identifier also indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow.

According to the scheme of the embodiment of the application, the first QoS identifier indicates that the wireless bearing the first QoS data flow bears only one QoS data flow, so that an independent transmission channel is directly provided for the QoS data flow, the data transmission requirement of XR service is met, and the user experience is improved.

With reference to the first aspect and the second aspect, in certain embodiments of the first aspect and the second aspect, the method further includes: the second QoS identifier also indicates that the radio bearer carrying the second QoS data flow carries only the second QoS data flow.

According to the scheme of the embodiment of the application, the second QoS identifier indicates that the wireless bearing the second QoS data flow bears only one QoS data flow, so that an independent transmission channel is directly provided for the QoS data flow, further, the data transmission requirement of XR service is met, and the user experience is improved.

With reference to the first aspect and the second aspect, in certain embodiments of the first aspect and the second aspect, the method further includes: the traffic importance of the first QoS data flow is higher than the traffic importance of said second QoS data flow.

According to the scheme of the embodiment of the application, different radio bearers are provided for two QoS data flows with different service importance to realize downlink transmission, so that the QoS guarantee requirements of each QoS data flow can be realized in a targeted manner.

The service importance of the first QoS data flow and the service importance of the second QoS data flow may be determined according to at least one parameter such as priority, data delay, packet error rate, average window, and maximum data burst. The embodiment of the present application is not limited thereto.

With reference to the first aspect and the second aspect, in certain embodiments of the first aspect and the second aspect, the method further includes: the first QoS data flow and the second QoS data flow belong to the same data unit.

Alternatively, when the data transmitted is data in video service or data in XR service, the data unit may be a video frame, a video frame slice (slice), or a video frame slice (tile).

According to the technical scheme, the first QoS data flow and the second QoS data flow can be data flows of various video coding modes, so that the technical scheme can be suitable for various video coding scenes.

Optionally, the data unit may also be an application layer data unit (application data unit), a haptic multi-stream signal, a media unit (media unit) or a protocol data unit (protocol data unit).

In a third aspect, a method for data transmission is provided, where the method may be performed by an access network device, or may also be performed by a chip or a circuit configured in the access network device, or may also be performed by a logic module or software that may implement all or part of the functionality of the access network device. The application is not limited in this regard.

The method comprises the following steps: receiving quality of service, qoS, configuration information from a core network element, the QoS configuration information comprising a first QoS identifier indicating a QoS for a first QoS data flow, the first QoS identifier further indicating that a radio bearer carrying the first QoS data flow carries only the first QoS data flow; mapping the first QoS data flow to the first wireless bearer, and sending the data of the first QoS data flow to terminal equipment through the first wireless bearer.

According to the scheme of the embodiment of the application, the access network equipment can obtain the first QoS identifier according to the QoS configuration information, the first QoS identifier requires or suggests that the access network equipment maps the first QoS data flow to a radio bearer independently, and the data packet of the data flow is sent to the terminal equipment through the radio bearer, so that proper transmission guarantee is provided for data transmission of XR service, and user experience is improved.

In a fourth aspect, a method for data transmission is provided, where the method may be performed by a core network device, or may also be performed by a chip or a circuit configured in the core network device, or may also be performed by a logic module or software that can implement all or part of the functions of the core network device. The application is not limited in this regard.

The method comprises the following steps: and sending QoS configuration information to access network equipment, wherein the QoS configuration information comprises a first QoS identifier, the first QoS identifier indicates QoS of a first QoS data flow, and the first QoS identifier also indicates that first access network resources bearing the first QoS data flow only bear the first QoS data flow.

According to the scheme of the embodiment of the application, the core network equipment can send QoS configuration information to the access network equipment, wherein the QoS configuration information comprises the first QoS identifier, and the first QoS identifier is used for requesting or suggesting that the access network equipment singly maps the first QoS data flow to a radio bearer, and the radio bearer is used for sending the data packet of the data flow to the terminal equipment, so that proper transmission guarantee is provided for the data transmission of the XR service, and the user experience is improved.

Wherein the core network device may be an SMF network element.

In the application, when the access network equipment establishes PDU session with the SMF network element, the QoS flow with synchronous association is established, and in the establishment process, the SMF network element sends QoS configuration information to the access network equipment, wherein the QoS configuration information comprises a first QoS identifier.

The QoS configuration information may be, for example, a QoS profile.

Illustratively, the first QoS identifier may be 5QI.

Wherein the first QoS identifier further indicates that the first access network resource carrying the first QoS data flow carries only the first QoS data flow, and one possible understanding is that the SMF network element suggests or needs or directs or trends the access network device to map the first QoS data flow solely to one access network resource, in other words, the access network device may not perform a corresponding mapping action after receiving the QoS identifier. The embodiment of the present application is not limited thereto.

With reference to the third aspect and the fourth aspect, in certain embodiments of the third aspect and the fourth aspect, the method further includes: the QoS configuration information further includes a second QoS identifier indicating a QoS for the second QoS data flow, the second QoS identifier further indicating that the second access network resource carrying the second QoS data flow carries only the second QoS data flow.

With reference to the third aspect and the fourth aspect, in certain embodiments of the third aspect and the fourth aspect, the method further includes: the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

With reference to the third aspect and the fourth aspect, in certain embodiments of the third aspect and the fourth aspect, the method further includes: the first QoS data flow and the second QoS data flow belong to the same data unit.

In a fifth aspect, there is provided an apparatus for data transmission, where the apparatus may be an access network device, or may be a chip or a circuit configured in the access network device, and the application is not limited thereto.

The device comprises: an interface unit, configured to receive QoS configuration information from a core network element, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates QoS of a first QoS data flow, the second QoS identifier indicates QoS of a second QoS data flow, and the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively; and the processing unit is used for mapping the first QoS data flow and the second QoS data flow to a first radio bearer and a second radio bearer respectively, sending the data of the first QoS data flow to the terminal equipment through the first radio bearer, and sending the data of the second QoS data flow to the terminal equipment through the second radio bearer.

In a sixth aspect, there is provided an apparatus for data transmission, where the apparatus may be a core network device, or may be a chip or a circuit configured in the core network device, and the application is not limited thereto.

The device comprises: an interface unit, configured to send QoS configuration information to an access network device, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates QoS of a first QoS data flow, the second QoS identifier indicates QoS of a second QoS data flow, and the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

With reference to the fifth aspect and the sixth aspect, in certain embodiments of the fifth aspect and the sixth aspect, the apparatus further includes: the first QoS identifier also indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow.

With reference to the fifth aspect and the sixth aspect, in certain embodiments of the fifth aspect and the sixth aspect, the apparatus further includes: the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

With reference to the fifth aspect and the sixth aspect, in certain embodiments of the fifth aspect and the sixth aspect, the apparatus further includes: the first QoS data flow and the second QoS data flow belong to the same data unit.

In a seventh aspect, there is provided an apparatus for data transmission, where the apparatus may be an access network device, or may be a chip or a circuit configured in the access network device, and the application is not limited thereto.

The device comprises: an interface unit, configured to receive quality of service QoS configuration information from a core network element, where the QoS configuration information includes a first QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, and where the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow; and the processing unit is used for mapping the first QoS data flow to the first wireless bearer and sending the data of the first QoS data flow to the terminal equipment through the first wireless bearer.

In an eighth aspect, there is provided an apparatus for data transmission, where the apparatus may be a core network device, or may be a chip or a circuit configured in the core network device, and the application is not limited thereto.

The device comprises: an interface unit, configured to send quality of service QoS configuration information to an access network device, where the QoS configuration information includes a first QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, and where the first QoS identifier further indicates that a first access network resource carrying the first QoS data flow carries only the first QoS data flow.

With reference to the seventh aspect and the eighth aspect, in certain embodiments of the seventh aspect and the eighth aspect, the apparatus further includes: the QoS configuration information further includes a second QoS identifier indicating a QoS for a second QoS data flow, the second QoS identifier further indicating that second access network resources carrying the second QoS data flow only carry the second QoS data flow.

With reference to the seventh aspect and the eighth aspect, in certain embodiments of the seventh aspect and the eighth aspect, the apparatus further includes: the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

With reference to the seventh aspect and the eighth aspect, in certain embodiments of the seventh aspect and the eighth aspect, the apparatus further includes: the first QoS data flow and the second QoS data flow belong to the same data unit.

In a ninth aspect, the present application provides a communication apparatus comprising: at least one processor coupled to at least one memory, the at least one processor configured to execute a computer program or instructions stored in the at least one memory, to cause the apparatus to perform the method of any one of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects.

In a tenth aspect, the present application provides a computer readable medium having stored thereon a computer program or instructions which, when run on a computer, cause the computer to implement the method of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects.

In an eleventh aspect, the present application provides a computer program product comprising a computer program or instructions for implementing the method of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects when executed.

In a twelfth aspect, the present application provides a chip system comprising: a processor for executing a computer program or instructions in the memory, such that the chip system implements the method of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects.

In a thirteenth aspect, a communication device is provided, the device comprising a processor for performing the method of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects.

Advantageous effects in the fifth to thirteenth aspects above and in any of the possible embodiments of the aspect may be referred to the advantageous effects in the first aspect and its possible embodiments.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for use in the method of an embodiment of the present application.

Fig. 2 is a further schematic diagram of a network architecture suitable for use in the method of an embodiment of the present application.

Fig. 3 is a further schematic diagram of a network architecture suitable for use in the method of an embodiment of the present application.

FIG. 4 is a schematic diagram of a hierarchical transmission process of XR service suitable for use in embodiments of the application

Fig. 5 is a schematic diagram of a QoS securing mechanism suitable for use with embodiments of the present application.

Fig. 6 is a schematic flow chart diagram of a method of data transmission suitable for use with embodiments of the present application.

Fig. 7 is a schematic diagram of a mapping relationship between QoS data flows and radio bearers according to an embodiment of the present application.

Fig. 8 is a further schematic flow chart of a method of data transmission suitable for use in embodiments of the present application.

FIG. 9 is a further schematic flow chart diagram of a method of data transmission suitable for use with embodiments of the present application

Fig. 10 is a schematic block diagram of a communication device suitable for use with embodiments of the present application.

Fig. 11 is a block diagram of a communication apparatus suitable for use in an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a universal mobile telecommunications system (universal mobile telecommunication system, UMTS), a fifth generation (5th generation,5G) system, or a New Radio (NR) or other evolving communication system, etc.

The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system and the like. The application is not limited in this regard.

The technical scheme provided by the application can be also applied to machine type communication (machine type communication, MTC), inter-machine communication long term evolution (long term evolution-machine, LTE-M), device-to-device (D2D) network, machine-to-machine (machine to machine, M2M) network, internet of things (internet of things, ioT) network or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.

Fig. 1 is a schematic diagram of a network architecture suitable for use with embodiments of the present application. As shown in fig. 1, the network architecture may include a user equipment 110, (radio) access network equipment 120, a user plane network element 130, a data network 140, an access management network element 150, a session management network element 160, a network deployment network element 170, a policy control network element 180, an application network element 190, and the like. The individual network elements involved in the network architecture are described separately below.

1. User Equipment (UE) 110: a user equipment may also be called a terminal, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminals in embodiments of the present application may be mobile phones (mobile phones), tablet computers (pad), computers with wireless transceiving functionality, virtual Reality (VR) terminals, augmented reality (augmented reality, AR) terminals, wireless terminals in industrial control (industrial control), wireless terminals in unmanned aerial vehicle (self driving), wireless terminals in telemedicine (remote media), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication functionality, computing devices or other processing devices connected to a wireless modem, vehicle devices, wearable devices, terminals in a 5G network or future networks, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

2. (radio) access network device (radio access network, (R) AN) 120: the access network device may also be referred to as AN access device, where the (R) AN may be capable of managing radio resources, providing access services for the user device, and completing forwarding of user device data between the user device and the core network, and may also be understood as a base station in the network.

The access network device in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with the user equipment. The access network device includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home evolved Node B, heNB, or home Node B, HNB), a baseBand unit (BBU), an Access Point (AP) in a wireless fidelity (wireless fidelity, wiFi) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, such as a gNB in an NR system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network Node constituting a gNB or a transmission point, such as a baseBand unit (BBU), or a Distributed Unit (DU), etc. It will be appreciated that all or part of the functionality of the access network device in the present application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform, such as a cloud platform.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. The information of the RRC layer is generated by the CU and finally becomes PHY layer information through PHY layer encapsulation of DU, or is converted from the information of the PHY layer. Thus, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be sent by DUs, or by dus+aaus. It is understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (radio access network, RAN), or may be divided into access network devices in a Core Network (CN), which is not limited by the present application.

In the present application, the access network device may establish a data radio bearer (data radio bearer, DRB).

3. User plane network element 130: as an interface with the data network, the functions of user plane data forwarding, charging statistics based on session/stream level, bandwidth limitation and the like are completed. I.e. packet routing and forwarding, quality of service (quality of service, qoS) handling of user plane data, etc.

In a long term evolution (long term evolution, LTE) communication system, the user plane element may be a serving gateway user plane (serving gateway user plane, SGW-U) or a packet data gateway user plane (packet data network gateway user plane, PGW-U) or a network element in which the SGW-U and the PGW-U are combined. In a 5G communication system, the user plane network element may be a user plane function (user plane function, UPF) network element.

4. Data network 140: providing, for example, operator services, internet access, or third party services, including servers, server-side implementation of video source coding, rendering, etc.

In a 5G communication system, the data network may be a Data Network (DN).

5. Access management network element 150: the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions besides session management in the functions of a mobility management entity (mobility management entity, MME), such as legal interception, access authorization/authentication and the like.

In the LTE communication system, the access management network element may be an MME network element. In a 5G communication system, the access management network element may be an access and mobility management function (access and mobility management function, AMF), mainly performing mobility management, access authentication/authorization, etc. In addition, it is responsible for passing user policies between the terminal and the policy control function (policy control function, PCF) network elements.

6. Session management network element 160: the method is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of user equipment, terminal node of selecting manageable user plane functions, strategy control and charging function interfaces, downlink data notification and the like.

In the LTE communication system, the session management network element may be a serving gateway control plane (serving gateway control plane, SGW-C) or a packet data network gateway control plane (packet data network gateway control plane, PGW-C) or a network element in which the SGW-C and the PGW-C are combined. In the 5G communication system, the session management network element may be a session management function (session management function, SMF) network element, which performs terminal IP address allocation, UPF selection, charging and QoS policy control, and the like.

7. Network opening network element 170: in an LTE communication system, the network-released network element may be a service capability exposure function (service capability exposure function, SCEF) network element. In the 5G communication system, the network element may be a network element with a network opening function (network element function, NEF), which is mainly used for exposing services and capabilities of the 3GPP network function to the AF, and may also enable the AF to provide information to the 3GPP network function.

8. Policy control network element 180: the system comprises a user subscription data management function, a policy control function, a charging policy control function, a quality of service (quality of service, qoS) control function and the like, and is used for guiding a unified policy framework of network behaviors and providing policy rule information and the like for control plane function network elements (such as AMF, SMF network elements and the like).

In an LTE communication system, the policy control network element may be a policy control and charging function (policy control and charging function, PCRF). In a 5G communication system, the policy control network element may be a PCF.

In a 5G communication system, the application network element may be a network slice selection function (network slice selection function, NSSF) network element.

9. Application network element 190: in the 5G communication system, the application network element may be an application function (application function, AF) network element, which represents an application function of a third party or an operator, and is an interface for the 5G network to obtain external application data, and is mainly used for transferring a requirement of an application side on a network side.

In future communication systems, such as 6G communication systems, the network element or device may still use its name in the 4G or 5G communication system, or may have other names, which are not limited by the embodiments of the present application. The functions of the network element or the device can be completed by one independent network element or can be completed by a plurality of network elements together. In an actual deployment, the network elements in the core network may be deployed on the same or different physical devices. For example, as one possible deployment, the AMF and SMF may be deployed on the same physical device. For another example, the network element of the 5G core network may be deployed on the same physical device as the network element of the 4G core network. The embodiment of the present application is not limited thereto.

It should be understood that fig. 1 is only an example, and does not limit the scope of the present application. The communication method provided by the embodiment of the present application may also relate to a network element not shown in fig. 1, and of course, the communication method provided by the embodiment of the present application may also include only a part of the network elements shown in fig. 1.

In the network architecture shown in fig. 1, the terminal is connected to the AMF through AN N1 interface, (R) AN is connected to the AMF through AN N2 interface, and (R) AN is connected to the UPF through AN N3 interface. The UPFs are connected through an N9 interface, and are interconnected with the DN through an N6 interface. The SMF controls the UPF through the N4 interface.

It should be understood that the network architecture applied to the embodiments of the present application is merely illustrative, and the network architecture to which the embodiments of the present application are applied is not limited to this, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application.

For example, fig. 2 is yet another schematic diagram of a network architecture suitable for use with embodiments of the present application. As shown in fig. 2, the architecture is a terminal-network-terminal architecture scenario, which may be a Tactile Internet (TI), where one terminal is a main domain tactile user interface with a manual system, and the other terminal is a remote control robot or remote operator of a controlled domain, and the network transmission core network and the access network include LTE, 5G, or next generation air interface 6G. The master domain receives audio/video feedback signals from the slave domain, and the master domain and the slave domain are connected with the help of various commands and feedback signals via a bi-directional communication link over the network domain, thereby forming a global control loop.

As another example, fig. 3 is yet another schematic diagram of a network architecture suitable for use with embodiments of the present application. As shown in fig. 3, the architecture is a WiFi scenario in which the cloud server transmits XR media data or normal video to the terminal (XR device) through a fixed network, wiFi router/AP/set top box.

With the development of the fifth generation (5th generation,5G) communication system, the data transmission delay is continuously reduced, the transmission capacity is larger and larger, and the 5G communication system gradually permeates some multimedia services with stronger real-time performance, such as video transmission, cloud Game (CG), extended reality (XR), TI, and the like, where XR includes Virtual Reality (VR) and augmented reality (augmented reality, AR). For multimedia services with high real-time performance, how to ensure the quality of service (quality of service, qoS) of users has become an important issue in current research.

To facilitate an understanding of the embodiments of the present application, the terminology involved in the present application will be briefly described.

1. QoS flow attributes

2. QoS configuration (QoS profile):

the QoS configuration of one QoS flow contains QoS parameters as follows:

(1) QoS parameters that each QoS flow's QoS configuration will contain: 5QI, ARP;

(2) The QoS configuration for each Non-GBR QoS flow may also contain parameters: reflective Qos Attributes (RQA);

(3) The QoS configuration for each GBR QoS flow may also include parameters: guaranteed stream bit rate (GFBR), maximum stream bit rate (MFBR);

(4) The QoS configuration for each GBR QoS flow may also include: and indicating control and maximum packet loss rate.

3. QoS rules (QoS rules): the UE performs classification and marking of the uplink user plane data traffic, i.e. associates uplink data to the corresponding QoS flows according to the QoS rules. These QoS rules may be either explicit to the UE (i.e., signaled to the UE in the PDU session establishment/modification procedure), pre-configured on the UE, or implicitly derived by the UE using a reflective QoS mechanism. The QoS rules have the following characteristics:

(1) One QoS rule comprises: QFI of the associated QoS flow, packet filter set (a list of filters), priority;

(2) One QoS flow may have multiple QoS rules;

(3) Each PDU session is configured with a default QoS rule that is associated with a QoS flow.

4. Attributes of 5QI

In the embodiment of the application, for some multimedia services with stronger real-time performance, the QoS requirements of the application layer data may be different due to factors such as source end coding processing mode, core network/fixed network transmission and the like, so different QoS configurations are required to be provided to realize different QoS guarantees.

For example, fig. 4 is a schematic diagram of a layered transmission procedure of an XR service according to an embodiment of the present application. Layered coding transmits a service data frame by outputting a two-layer code stream, including a Base Layer (BL) and an enhancement layer (enhancement layer, EL). For example, XR video transmission may be divided in time, space, and quality, outputting two layers of code streams. The data frame of BL can make the decoder decode the basic video content completely and normally, ensure the basic experience of UE, BL data frame is usually smaller in data size. The data frame of the EL includes more detailed information for improving the video quality, and the data amount is larger. For layered coding video, during network transmission, two code streams are also transmitted separately, and different QoS (Quality of Service) guarantees are provided, for example, a data packet of a BL and a data packet of an EL are configured with different QoS requirements (identifier distinction is performed by 5QI (5G Quality identity) in a 5G system), as shown in fig. 4, the QoS of the data packet of the BL is configured as 5QI-1, and the QoS of the data packet of the EL is configured as 5QI-1. Then, when the base station side performs scheduling, according to the QoS requirement, the scheduling priority of the BL data packet is ensured to be higher than the scheduling priority of the EL data packet.

As another example, in h.264 video coding, a group of pictures (group of picture GoP,) may be made up of multiple types of video frames. The first frame in the GoP is an I frame (intra frame) which can contain a plurality of P frames (predicted frames), wherein the I frame is an intra reference frame, the data size is large, the image is restored according to the frame data during decoding, and the influence of errors on the video quality is large; the P-frame is a predictive encoded frame, and generally has a smaller data size, and is used to represent the data of the picture difference from the previous frame, and when decoding, the picture needs to be generated by overlapping the previously buffered picture with the difference defined by the present frame, so that the influence of errors on the video quality is relatively small. Therefore, transmission of the I frame should be preferentially secured at the time of transmission.

In the embodiment of the application, the QoS guarantee mechanism can provide QoS guarantee for the data transmission of the service flow. For example, fig. 5 shows a schematic diagram of a QoS guarantee mechanism provided by an embodiment of the present application.

As shown in fig. 5, in a 5G system (5G system,5 gs), qoS flows are controlled by the SMF network elements of the core network, which may be preconfigured or established and modified by PDU sessions. The characteristics of one QoS flow consist of 3 parts, qoS configuration (QoS profile) on AN side: these configurations are provided by the SMF over the N2 interface to the AN, or pre-configured in the AN; qoS rule (QoS rule) on UE side: these rules may be provided by the SMF to the UE through N1 or derived by the UE through a reflective QoS mechanism; UPF-side upstream and downstream packet detection rules (packet detection rule, PDR): these PDRs(s) are provided by the SMF to the user plane functions (user plane function, UPF) over the N4 interface.

In one protocol data unit (protocol data unit, PDU) session (session), qoS Flow is the minimum granularity to distinguish QoS. In 5G systems, qoS flows are identified using QoS flow identifiers (qoS flow identifier, QFI), that is, one PDU session may have multiple QoS flows, but the QFI for each QoS flow is different. In one PDU session, the same service forwarding processing manner (e.g. scheduling) is used for the service flows with the same QFI UE plane. At the configuration granularity, as shown in fig. 5, one PDU session may correspond to multiple Radio Bearers (RBs), and the service on the same RB may also use different service classes; one RB may further include a plurality of QoS flows, and data placed on the same RB is not distinguished when being transmitted on the access network device side.

For XR service, after the core network is allocated to two QoS flows, it is possible that the packets with different importance are carried on one RB at the access network device side, so that the two packets with different importance cannot be distinguished in the physical layer transmission process, and therefore, an appropriate transmission guarantee cannot be provided for the data transmission of the XR service, thereby affecting the user experience.

In view of this, the present application provides a data transmission method, which satisfies the transmission requirement of application layer data during physical layer transmission, thereby providing appropriate transmission guarantee for data transmission and further improving user experience.

Fig. 6 is a schematic flow chart of a method of data transmission provided by the present application.

In this embodiment, the access network device, the terminal device, and the core network device are taken as the execution bodies of the interactive instruction to illustrate the method, but the present application is not limited to the execution bodies of the interactive instruction. For example, the access network device in fig. 6 may also be a chip, a chip system, or a processor that supports the method that can be implemented by the access network device, or may be a logic module or software that can implement all or part of the functions of the access network device; the terminal device in fig. 6 may also be a chip, a chip system or a processor supporting the method that can be implemented by the terminal device, or may also be a logic module or software that can implement all or part of the functions of the terminal device; the core network device in fig. 6 may also be a chip, a system-on-chip or a processor supporting the method that can be implemented by the core network device, or may also be a logic module or software that can implement all or part of the functions of the core network device. It should be appreciated that the method 600 shown in fig. 6 may be used for downlink data transmission.

And S610, the core network equipment sends QoS configuration information to the access network equipment.

In the present application, the core network device may be an SMF network element.

Specifically, when the access network device establishes a PDU session with the SMF network element, the access network device establishes a QoS flow with synchronous association, and in the establishment process, the SMF network element sends QoS configuration information to the access network device, wherein the QoS configuration information comprises a first QoS identifier and a second QoS identifier.

Specifically, before the access network device establishes the QoS flow with the synchronization association with the SMF network element, the core network device may acquire importance information of the application layer XR service from the server, where the importance information includes type attributes of a data packet of the XR service and an application layer data unit, for example, belongs to a base layer/enhancement layer, an I frame/P frame, and then performs natural layering by using unequal importance of different areas of a field of view (FOV), for example, may be divided into intra-field angle data and extra-field angle data.

The QoS configuration information may be, for example, a QoS profile.

Alternatively, the QoS configuration information may include a QoS profile for the first QoS data flow and a QoS profile for the second QoS data flow.

Optionally, the QoS configuration information includes first QoS configuration information and second QoS configuration information, where the first QoS configuration information includes a QoS configuration file for the first QoS data flow, and the second QoS configuration information includes a QoS configuration file for the second QoS data flow, and the first QoS configuration information and the second QoS configuration information may be included in different messages or may be included in one message and sent.

In the present application, the first QoS data flow and the second QoS data flow belong to the same data unit, and it can be understood that the first QoS data flow is a data flow of the data unit after the first data flow of the data unit is mapped by the QoS flow, and the second QoS data flow is a data flow of the data unit after the second data flow of the data unit is mapped by the QoS flow. The first data flow is transmitted from the application server to the terminal device and may be referred to as a first data flow when passing through each node, where after the UPF performs QoS flow mapping, the first data flow may also be referred to as a first QoS data flow. Similarly, the second data flow may be referred to as a second data flow when passing through each node, where after the UPF performs QoS flow mapping, the second data flow may also be referred to as a second QoS data flow. Wherein, the first data and the second data are both data of the same service.

Wherein the first QoS identifier indicates QoS for the first QoS data flow and the second QoS identifier indicates QoS for the second QoS data flow.

Illustratively, the first QoS identifier and the second QoS identifier may be 5QI.

Wherein the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

Accordingly, the access network device receives QoS configuration information from the SMF network element, the QoS configuration information comprising a first QoS identifier and a second QoS identifier.

In the present application, the first QoS identifier and the second QoS identifier indicate that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively.

One possible insight is that a plurality of 5QI (e.g. a first QoS identifier and a second QoS identifier) are predefined and that the access network device establishes a QoS flow with a synchronization association when establishing a PDU session with the core network element. Specifically, the process includes that the SMF network element sends QoS configuration information to the access network device, including the plurality of 5QI, and the role of the plurality of 5QI may be understood as that QoS flows with different QoS transmission requirements (for example, importance of QoS data flows is different) are marked by using the plurality of 5QI, so when one PDU session includes the plurality of 5QI, it may be understood that the SMF network element instructs the access network device to map the QoS flows marked by the plurality of 5QI to different access network resources respectively.

The SMF network element indicates the access network device to map the QoS flows marked by the 5QI to different access network resources, which may be understood that the SMF network element requires the access network device to map the QoS flows marked by the 5QI to different access network resources, or may be understood that the SMF network element suggests the access network device to map the QoS flows marked by the 5QI to different access network resources.

For example, in the case that the SMF network element requires the access network device to map the QoS flows marked by the plurality of 5QI to different access network resources, the access network device performs the mapping operation according to the SMF requirement. For another example, in the case where the SMF network element suggests that the access network device maps the QoS flows marked by the plurality of 5QI to different access network resources, the access network device may perform mapping operation according to the SMF requirement, or may not perform mapping operation according to the SMF requirement.

By way of example and not limitation, in the scenario where the SMF network element suggests that the access network device map the plurality of 5 QI-tagged QoS flows to different access network resources, respectively, the access network device determines from the radio bearer resources whether to perform a mapping operation according to the SMF suggestion. For example, when the access network device determines that the radio bearer resources are sufficient, the access network device maps the QoS flows marked by the plurality of 5QI to different radio bearers respectively; when the access network device determines that the radio bearer resources are limited, such as only one radio bearer, the access network device does not map the plurality of QoS flows marked with 5QI to different radio bearers, respectively.

It will be appreciated that, in the case of sufficient radio bearer resources, the access network device may not map the plurality of QoS flows denoted by 5QI to different radio bearers, respectively.

Accordingly, the access network device receives QoS configuration information, where the QoS configuration information includes a plurality of newly defined 5QI, and the access network device may map QoS flows marked by the plurality of predefined 5QI to different radio bearers respectively, or may map QoS flows marked by the plurality of 5QI to some radio bearers according to implementation of the access network device.

It should be noted that, as the indication information of the core network device to the access network device, the predefined 5QI (e.g., the first QoS identifier and the second QoS identifier), the access network device may map the QoS flows marked by the plurality of 5QI to different radio bearers according to the predefined rule, or may perform its implementation to map the QoS flows marked by the plurality of 5QI to some radio bearers, but when sending the QoS configuration information, the core network device indicates or suggests or is a mapping access network resource that is prone to the predefined 5QI marked QoS flows by the predefined 5 QI.

As an example, a new (predefined) 5QI is added in the attribute list of 5QI, e.g. the value of this new added 5QI is X1, X2, X3. The attribute list of 5QI is updated as follows in table 1:

TABLE 1

As shown in table 1, the predefined values are 5QI of X1, X2, X3, and the QoS flows with different transmission requirements can be identified by the use of the values of X1, X2, X3, where "Note1" (Note 1) included in X1, X2, X3 indicates a specific transmission requirement and transmission mode (detailed description of fig. 7 in step S620 below). For example, X1 may identify the QoS flow of the base layer data frame, X2 may identify the QoS flow of the enhancement layer data frame, and X3 may identify the QoS flow of the video data frame, it will be appreciated that the base layer data frame may enable the decoder to decode the base video content completely normally, guaranteeing the base experience of the UE, and the EL data frame may include more detailed information. For layered coding video, in the network transmission process, two code streams can be transmitted separately, and different QoS (Quality of Service) guarantees are provided, for example, a BL data packet is configured with an X1-identified QoS data stream, an EL data packet is configured with an X2-identified QoS data stream, X1 and X2 define different QoS requirements, and when an access network device performs scheduling, the QoS requirements of X1 and X2 are determined according to Note1, so that the scheduling priority of the BL data packet is higher than the scheduling priority of the EL data packet.

In a possible embodiment, the QoS configuration information may include a plurality of QoS identifiers, (i.e. a plurality of 5QI identifiers are predefined to identify a plurality of QoS flows), which may belong to the same application layer service, and the UPF network element and the RAN of the core network may ensure that the QoS flows are transmitted synchronously as much as possible, in other words, reduce the delay of transmitting the QoS flows as much as possible, and also understand that the time interval between transmitting the data packets included in the QoS flows as much as possible. Further, when the network is congested, the network can uniformly reject the transmission tasks of the QoS flows, so as to avoid resource waste caused by that the transmission of part of QoS flows cannot meet the user experience.

The foregoing is merely exemplary and embodiments of the present application are not limited in terms of the specific indication of predefined 5 QI.

S620, the access network device maps the first QoS data flow and the second QoS data flow to the first radio bearer and the second radio bearer, respectively.

In the present application, the predefined QoS data flows with 5QI identification, and the access network device can map these QoS flows onto different radio bearers for sending, so as to provide different QoS guarantees.

In one implementation, the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

By way of example and not limitation, the traffic importance of the first QoS data flow and the traffic importance of the second QoS data flow are determined based on at least one parameter such as priority, data latency, packet error rate, average window, and maximum data burst size.

For example, the access network device may determine the traffic importance of the first QoS data flow according to the latency requirement of the first QoS data flow, determine the traffic importance of the second QoS data flow according to the latency requirement of the second QoS data flow, and in particular, may determine that the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow when the latency requirement of the first QoS data flow is higher than the latency requirement of the second QoS data flow.

For another example, the access network device may determine the traffic importance of the first QoS data flow based on the packet error rate of the first QoS data flow, determine the traffic importance of the second QoS data flow based on the packet error rate of the second QoS data flow, and specifically determine that the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow when the packet error rate requirement of the first QoS data flow is lower than the packet error rate of the second QoS data flow.

It should be understood that the foregoing examples are merely illustrative, and in a specific implementation, the access network device may determine the service importance of the data flow according to a specific parameter that may embody the service importance, or may determine the service importance according to a plurality of parameters, where embodiments of the present application are not limited herein.

By way of example and not limitation, the access network device may determine configuration information such as modulation and coding (modulation and coding scheme, MCS) order, allocated time-frequency resources, retransmission times, etc. for data stream transmission according to QoS requirements (e.g., corresponding bit error rate, delay requirement, etc.) of different importance streams and channel conditions fed back by users, thereby providing different QoS guarantees and implementing transmission of unequal importance protection.

In a possible implementation, the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow.

For example, as shown in fig. 7 (a), the access network device may map the QoS data flow identified by X1 to RB1, and RB1 may only carry the QoS data flow identified by X1, and the access network device may map the QoS data flow identified by X2 to RB2, but may carry a QoS flow on RB2 that is not predefined and identified by 5 QI.

In yet another possible implementation, the second QoS identifier further indicates that a radio bearer carrying the second QoS data flow carries only the second QoS data flow.

For example, as shown in fig. 7 (b), the access network device may map the QoS data flow identified by X2 to RB2, and RB2 may only carry the QoS data flow identified by X2, and the access network device may map the QoS data flow identified by X1 to RB1, but may carry a QoS flow on RB1 that is not predefined and identified by 5 QI.

In yet another possible implementation, the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow, and the second QoS identifier further indicates that a radio bearer carrying the second QoS data flow carries only the second QoS data flow.

For example, as shown in fig. 7 (c), the access network device may map the QoS data flow identified by X1 to RB1, and RB1 may only carry the QoS data flow identified by X1, the access network device may map the QoS data flow identified by X2 to RB2, and RB2 may only carry the QoS data flow identified by X2.

In the present application, the first QoS data flow and the second QoS data flow are only exemplary, and are not limited to only two QoS data flows, in actual transmission, there may be multiple data flows in a PDU session of the XR service, and a plurality of 5QI may be defined to indicate a transmission requirement, which is not limited in the embodiment of the present application.

In a possible implementation manner, in uplink transmission, a predefined QoS flow with 5QI identification may be separately divided into one logical channel group when performing logical channel group division.

S630, the access network device sends the first QoS data flow and the second QoS data flow data to the terminal device through the first wireless bearer and the second wireless bearer respectively.

Specifically, the access network device sends data of the first QoS data flow to the terminal device through the first radio bearer, and the access network device sends data of the second QoS data flow to the terminal device through the second radio bearer.

It should be noted that, after the access network device maps the QoS data flow to the radio bearer, the QoS data flow needs to be further processed based on the radio bearer before being sent to the terminal device. The manner in which the QoS data flows are further processed based on the radio bearer is not limited in any way by the embodiments of the present application.

By way of example and not limitation, further processing of the QoS data flow based on the radio bearer may be processing of coded modulation or the like of data packets in the QoS data flow, which is not limiting in the embodiments of the present application.

Fig. 8 is a further schematic flow chart of a method of data transmission provided by the present application.

In this embodiment, the access network device, the terminal device, and the core network device are taken as the execution bodies of the interactive instruction to illustrate the method, but the present application is not limited to the execution bodies of the interactive instruction. For example, the access network device in fig. 8 may also be a chip, a chip system, or a processor that supports the method that can be implemented by the access network device, or may be a logic module or software that can implement all or part of the functions of the access network device; the terminal device in fig. 8 may also be a chip, a chip system or a processor supporting the method that can be implemented by the terminal device, or may also be a logic module or software that can implement all or part of the functions of the terminal device; the core network device in fig. 8 may also be a chip, a system-on-chip or a processor supporting the method that can be implemented by the core network device, or may also be a logic module or software that can implement all or part of the functions of the core network device. It should be appreciated that the method 800 illustrated in fig. 8 may be used for downlink data transmission.

And S810, the core network equipment sends QoS configuration information to the access network equipment.

In this embodiment, the manner in which the core network device sends the QoS configuration information to the access network device is similar to S610 in the method 600, which is not described herein.

In the present application, the QoS configuration information includes a QoS profile for the first QoS data flow.

Wherein the QoS configuration information includes a first QoS identifier.

Wherein the first QoS identifier indicates a QoS for the first QoS data flow, the first QoS identifier further indicating that access network resources carrying the first QoS data flow only carry the first QoS data flow.

One possible insight is to predefine a 5QI (e.g. first QoS identifier) and the access network device establishes QoS flows with a synchronization association when establishing a PDU session with the core network element. Specifically, the procedure includes that the SMF network element sends QoS configuration information to the access network device, including the 5QI, and the role of the 5QI may be understood as that the QoS flow with QoS transmission requirement (for example, the importance of the first QoS data flow is higher) is marked by using the 5QI, so when a PDU session includes the 5QI, it may be understood that the SMF network element instructs the access network device to map the QoS flow marked by the 5QI to one access network resource alone, in other words, the access network resource only carries the QoS flow marked by the only 5 QI.

Wherein, the SMF network element instructs the access network device to map the predefined 5 QI-labeled QoS flow to an access network resource alone may be understood that the SMF network element requires the access network device to map the 5 QI-labeled QoS flow to an access network resource alone, or may be understood that the SMF network element suggests the access network device to map the 5 QI-labeled QoS flow to an access network resource alone.

Accordingly, the access network device receives QoS configuration information, where the QoS configuration information includes a predefined 5QI, and the access network device may map the QoS flows with multiple 5QI labels to one radio bearer separately, or may map the QoS flows with multiple 5QI labels to a radio bearer according to implementation of the access network device.

In a possible implementation, the QoS configuration information further comprises a second QoS identifier indicating a QoS for the second QoS data flow, the second QoS identifier further indicating that the second access network resource carrying the second QoS data flow carries only the second QoS data flow.

Specifically, the QoS configuration information further includes a QoS profile for the second QoS data flow.

One possible insight is that 5QI (e.g. a first QoS identifier and a second QoS identifier) are predefined, and that the access network device establishes a QoS flow with a synchronization association when establishing a PDU session with the core network element. Specifically, the procedure includes that the SMF network element sends QoS configuration information to the access network device, including the 5QI, and the role of the 5QI may be understood that using the 5QI to label a QoS flow with QoS transmission requirements (for example, the importance of the first QoS data flow and the importance of the second QoS flow are different), so when one PDU session includes the 5QI, it may be understood that the SMF network element instructs the access network device to map two QoS flows labeled with the 5QI to two access network resources separately, respectively, in other words, the two access network resources only carry the QoS flows labeled with the 5 QI.

The SMF network element instructs the access network device to map the two predefined QoS flows marked by 5QI to the two access network resources separately, which may be understood that the SMF network element requires the access network device to map the two QoS flows marked by 5QI to the two access network resources separately, or may be understood that the SMF network element suggests the access network device to map the two QoS flows marked by 5QI to the two access network resources separately.

Accordingly, the access network device receives QoS configuration information, where the QoS configuration information includes two predefined 5QI, and the access network device may map the predefined 5QI marked QoS flows to different radio bearers separately, or may map the 5QI marked QoS flows to a radio bearer according to the implementation of the access network device, which is not limited in the embodiment of the present application.

S620, the access network device maps the first QoS data flow to the first radio bearer, and sends the data of the first QoS data flow to the terminal device through the first radio bearer.

In the present application, the predefined QoS data flows with 5QI identifiers can be mapped to one radio bearer by the access network device for transmission, so as to provide different QoS guarantees.

As an example, the predefined 5QI may be X1 in table 1. The access network device may map the X1 identified QoS data flow to RB1 and RB1 can only carry the X1 identified QoS data flow.

In a possible implementation, the QoS configuration information further comprises a second QoS identifier, the second QoS identifier further indicating that the second access network resource carrying the second QoS data flow carries only the second QoS data flow.

As an example, the predefined 5QI includes X2 in table 1 in addition to X1 in table 1. The access network device may map the QoS data flow identified by X1 to RB1, and RB1 can only carry the QoS data flow identified by X1; the access device may map the X2 identified QoS data flow to RB2 and RB2 can only carry the X2 identified QoS data flow.

In this case, the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

By way of example and not limitation, the traffic importance of the first QoS data flow and the traffic importance of the second QoS data flow are determined based on at least one parameter such as priority, data latency, packet error rate, average window, and maximum data burst size. Specific examples may refer to step S620 in method 600.

S630, the access network device sends the data of the first QoS data flow to the terminal device through the first wireless bearer.

Specifically, the access network device sends corresponding data to the terminal device through a first QoS data stream unique to the first radio bearer.

In a possible embodiment, the access network device further transmits corresponding data to the terminal device via a second QoS data flow unique to the second radio bearer.

According to the scheme of the embodiment of the application, the access network equipment can obtain the first QoS identifier according to the QoS configuration information, the first QoS identifier requires or suggests that the access network equipment maps the first QoS data flow on one radio bearer independently, and the data of the QoS data flow is sent to the terminal equipment through the radio bearer, so that proper transmission guarantee is provided for the data transmission of the XR service, and the user experience is improved.

In the embodiment of the application, aiming at some multimedia services with stronger real-time performance, the integrity of the application layer data needs to be considered in the network transmission process, thereby ensuring the complete transmission of the service data and ensuring the user experience.

For example, in XR services, at the network transport layer, a frame of XR video may be divided into tens of IP (Internet Protocol) packets, e.g., 50 IP packets, for transmission to the fixed network/core network, after which the IP packets are transmitted to the UE via the radio access network. In the network transmission process, if an IP packet is transmitted in error, the whole picture frame cannot be recovered. Therefore, during the transmission process, it is necessary to ensure that the IP packet of one frame is successfully transmitted as completely as possible. In some possible video coding schemes, the block (tile) or slice (slice) may be performed, and the corresponding IP packets of each block or slice need to be completely and correctly transmitted.

In view of this, the present application provides a data transmission method, which satisfies the integrity transmission requirement of the application layer data during the physical layer transmission, thereby providing appropriate transmission guarantee for data transmission and further improving user experience.

Fig. 9 is a further schematic flow chart of a method of data transmission provided by the present application.

In this embodiment, the access network device, the terminal device, and the core network device are taken as the execution bodies of the interactive instruction to illustrate the method, but the present application is not limited to the execution bodies of the interactive instruction. For example, the access network device in fig. 9 may also be a chip, a chip system, or a processor that supports the method that can be implemented by the access network device, or may be a logic module or software that can implement all or part of the functions of the access network device; the terminal device in fig. 9 may also be a chip, a chip system or a processor supporting the method that can be implemented by the terminal device, or may also be a logic module or software that can implement all or part of the functions of the terminal device; the core network device in fig. 9 may also be a chip, a chip system or a processor supporting the method that can be implemented by the core network device, or may also be a logic module or software that can implement all or part of the functions of the core network device. It should be appreciated that the method 900 shown in fig. 9 may be used for downlink data transmission.

S910, the core network device sends QoS configuration information to the access network device.

Specifically, when the access network device establishes a PDU session with the SMF network element, the access network device establishes a QoS flow with synchronous association, and in the establishment process, the SMF network element sends QoS configuration information to the access network device, wherein the QoS configuration information comprises a third QoS identifier.

Specifically, before the access network device establishes a QoS flow with a synchronization association with the SMF network element, the core network device may obtain, from the server, the belonging relationship between the application layer unit of the XR service and the data packet. The application layer unit and the data packet belong to a relationship comprising which data packets of the XR service the application layer data unit comprises. Further, the core network may obtain the relationship between the application layer unit and the data packet by detecting the relevant identification information by marking the IP packet or the upper layer data packet at the server side, such as the data packet group ID (Packet Group ID), and integrating the data flag (the application layer unit).

The QoS configuration information may be, for example, a QoS profile.

Alternatively, the QoS configuration information may include a QoS profile for the third QoS data flow.

Wherein the third QoS identifier indicates QoS of the third QoS data flow, and the third QoS identifier further indicates that data packets of the third QoS data flow are transmitted in their entirety to the terminal device.

The third QoS identifier may be, for example, 5QI.

One possible insight is that a plurality of 5 QI's are predefined and that the access network device establishes QoS flows with a synchronization association when establishing a PDU session with the core network element. Specifically, the process includes that the SMF network element sends QoS configuration information to the access network device, including the plurality of 5QI, and simultaneously notifies the access network device of the relationship of the application unit data packet. The role of the plurality of 5QI may be understood as that QoS flows with integrity transmission requirements are marked with the plurality of 5QI, so when one PDU session includes the plurality of 5QI, it may be understood that the access network device may completely transmit data packets of the QoS flows identified by the plurality of 5QI to the terminal device.

The QoS flow with the integrity transmission requirement, one possible understanding is that the data frame transmitted by the QoS flow may include a plurality of data packets, so when the access network side schedules, the plurality of data packets corresponding to the data frame need to be completely scheduled, so that frame image decoding can be implemented at the terminal device.

For example, when 50 data packets of the same video frame are transmitted, 49 data packets are correctly transmitted, a single data packet does not arrive at the receiving terminal in time, and when the data packet is scheduled at the RAN side, the scheduling priority of the data packet which is not transmitted is increased, so that all the data packets are guaranteed to arrive at the receiving terminal in time, and the problem that frame image decoding cannot be performed due to incorrect transmission of one data packet, and therefore invalid transmission of 49 data packets is caused, and air interface resources are wasted is avoided.

As an example, a new (predefined) 5QI is added in the attribute list of 5QI, for example, the value of this new added 5QI is Y1, Y2, Y3. The attribute list of 5QI is updated as follows in table 2:

TABLE 2

As shown in table 2, the predefined value is 5QI of Y1, Y2, Y3, which Y1, Y2, Y3 uses QoS flows that may have transmission requirements, wherein "Note2" (Note 2) included in Y1, Y2, Y3 indicates that the QoS data flows noted Y1, Y2, Y3 have a need for integrity transmission. When the access network equipment identifies Y1, Y2 and Y3, the QoS flows marked by Y1, Y2 and Y3 can be subjected to integrity transmission protection according to the belonging relation between the application layer unit and the data packet.

S920, the access network device transmits the data packet of the third QoS data flow to the terminal device.

In the application, the access network equipment identifies the third QoS identifier, determines the belonged relation between the application layer unit of the third QoS data flow and the data packet, and carries out complete transmission on the data packet of the third QoS data flow to the terminal equipment.

In the present application, the third QoS data flow is only illustrated by way of example, and is not limited to only one QoS data flow, and in actual transmission, there may be multiple data flows in a PDU session of the XR service, and multiple 5QI may be defined to indicate a transmission requirement, which is not limited by the embodiment of the present application.

According to the scheme of the embodiment of the application, the access network equipment can obtain the third QoS identifier according to the QoS configuration information, the access network equipment carries out integrity transmission on the data packet of the third QoS data flow marked by the third QoS identifier, and all the data packets included in the application layer unit are completely sent to the terminal equipment, so that proper transmission guarantee is provided for the data transmission of the XR service, and the user experience is improved.

The various embodiments described herein may be separate solutions or may be combined according to inherent logic, which fall within the scope of the present application.

For example, by indicating that the first QoS flow and the second QoS flow are mapped to different radio bearers respectively through the first identifier and the second identifier, and meanwhile, the first QoS flow and/or the second QoS flow also have a need for integrity transmission, the scheme may be implemented in combination with the method 600 and the method 900, and specific execution steps are described in detail in the method 600 and the method 900, which are not repeated herein for brevity.

It should be understood that each step in the foregoing embodiments is only one possible implementation, and embodiments of the present application are not limited thereto.

The above description has been mainly made on the schemes provided by the embodiments of the present application from the respective interaction points of view. It will be appreciated that each network element, e.g. the transmitting device or the receiving device, in order to implement the above-mentioned functions, comprises corresponding hardware structures and/or software modules for performing each function. Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application can divide the function modules of the transmitting end equipment or the receiving end equipment according to the method example, for example, each function module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules described above may be implemented either in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation. The following description will be given by taking an example of dividing each function module into corresponding functions.

The method provided by the embodiment of the application is described in detail above with reference to fig. 6 to 9. The following describes the device provided in the embodiment of the present application in detail with reference to fig. 10 to 11. It should be understood that the descriptions of the apparatus embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details not described may be referred to the above method embodiments, which are not repeated herein for brevity.

Fig. 10 is a schematic block diagram of a communication device provided by the present application. As shown in fig. 10, the communication device 1000 may include an interface unit 1010 and/or a processing unit 1020.

The interface unit 1010 may also be referred to as a transceiver unit, including a transmitting unit and/or a receiving unit. The interface unit 1010 may be a transceiver (including a transmitter and/or a receiver), an input/output interface (including an input and/or output interface), pins or circuitry, and the like. The interface unit 1010 may be used to perform the steps of transmitting and/or receiving in the method embodiments described above.

The processing unit 1020 may be a processor (may include one or more), a processing circuit with a processor function, etc., and may be configured to perform steps other than transmitting and receiving in the above-described method embodiments.

Optionally, the communication device may further include a storage unit, which may be a memory, an internal storage unit (e.g., a register, a cache, etc.), an external storage unit (e.g., a read-only memory, a random access memory, etc.), and so on. The storage unit is configured to store instructions, and the processing unit 1020 executes the instructions stored in the storage unit, so that the communication device performs the above method.

In one design, the communication apparatus 1000 may correspond to the access network devices in the methods 600, 800, and 900 described above, and may perform the operations performed by the access network devices or ANs in the methods 600, 800, and 900.

For example, the interface unit 1010 is configured to receive quality of service QoS configuration information from a core network element, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, and the second QoS identifier indicates a QoS of a second QoS data flow, and where the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively; a processing unit 1020, configured to map a first QoS data flow and a second QoS data flow to a first radio bearer and a second radio bearer, respectively, send data of the first QoS data flow to a terminal device through the first radio bearer, and send data of the second QoS data flow to the terminal device through the second radio bearer.

Optionally, the first QoS identifier further indicates that the radio bearer carrying the first QoS data flow carries only the first QoS data flow.

Optionally, the second QoS identifier further indicates that the radio bearer carrying the second QoS data flow carries only the second QoS data flow.

Optionally, the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

Optionally, the first QoS data flow and the second QoS data flow belong to the same data unit.

It should be appreciated that the interface unit 1010 and the processing unit 1020 may also perform other operations performed by the access network device, AN, in any of the methods 600, 800, and 900 described above, which are not described in detail herein.

In one design, the communication apparatus 1000 may correspond to the core network devices in the methods 600, 800, and 900 described above, and may perform the operations performed by the core network devices in the methods 600, 800, and 900.

For example, the interface unit 1010 is configured to send quality of service QoS configuration information to an access network device, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, the second QoS identifier indicates a QoS of a second QoS data flow, and the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

It should be appreciated that the interface unit 1010 and the processing unit 1020 may also perform other operations performed by the core network device in any of the methods 600, 800, and 900 described above, and are not described in detail herein.

Fig. 11 is a block diagram of a communication device 1000 according to an embodiment of the present application. The communication apparatus 1100 shown in fig. 11 includes: a processor 1110, a memory 1120, and a transceiver 1130. The processor 1110 is coupled to the memory 1120 for executing instructions stored in the memory 1120 to control the transceiver 1130 to transmit signals and/or receive signals.

It should be appreciated that the processor 1110 and the memory 1120 may be combined into one processing device, and the processor 1110 is configured to execute program codes stored in the memory 1120 to implement the functions described above. In particular implementations, the memory 1120 may also be integrated into the processor 1110 or separate from the processor 1110. It is to be appreciated that the processor 1110 may also correspond to various processing elements in a prior communication device, and the transceiver 1130 may correspond to various receiving and transmitting elements in a prior communication device.

It should also be appreciated that the transceiver 1130 may include a receiver (or receiver) and a transmitter (or transmitter). The transceiver may further include antennas, the number of which may be one or more. The transceiver may also be a communication interface or interface circuit.

In particular, the communication apparatus 1100 may correspond to an access network device, a core network device in the methods 600, 800 and 900 according to embodiments of the present application. The communication apparatus 1100 may comprise elements of the methods 600, 800 and 900 performed by an access network device or elements of the methods 600, 800 and 900 performed by a core network device. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

When the communication device 1100 is a chip, the chip includes an interface unit and a processing unit. The interface unit can be an input/output circuit or a communication interface; the processing unit may be an integrated processor or microprocessor or an integrated circuit on the chip.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method. To avoid repetition, a detailed description is not provided herein.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capability. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

The application also provides a computer readable medium having stored thereon a computer program which when executed by a computer performs the functions of any of the method embodiments described above.

The application also provides a computer program product which, when executed by a computer, implements the functions of any of the method embodiments described above.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

In embodiments of the application, words such as "exemplary," "for example," and the like are used to indicate by way of example, illustration, or description. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

It should be appreciated that reference throughout this specification to "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, various embodiments are not necessarily referring to the same embodiments throughout the specification. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The names of all nodes and messages in the present application are only names set for the convenience of description of the present application, and names in actual networks may be different, and it should not be understood that the present application is limited to the names of various nodes and messages, but any names having the same or similar functions as those of the nodes or messages used in the present application are regarded as methods or equivalent alternatives of the present application, and are within the scope of protection of the present application.

It should also be understood that, in the present application, "when …," "if," and "if" all refer to that the UE or the base station will make a corresponding process under some objective condition, and are not limited in time, nor do they require that the UE or the base station must have a judgment action when it is implemented, nor are they meant to have other limitations.

In addition, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The term "at least one of … …" or "at least one of … …" herein means all or any combination of the listed items, e.g., "at least one of A, B and C," may mean: there are six cases where A alone, B alone, C alone, both A and B, both B and C, and both A, B and C. The term "at least one" as used herein means one or more. "plurality" means two or more.

It should be understood that in embodiments of the present application, "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

It should be understood that in the various embodiments of the present application, the first, second and various numbers are merely for ease of description and are not intended to limit the scope of the embodiments of the present application. For example, different information is distinguished, etc.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of data transmission, comprising:

receiving quality of service, qoS, configuration information from a core network element, the QoS configuration information comprising a first QoS identifier and a second QoS identifier, the first QoS identifier indicating a QoS for a first QoS data flow and the second QoS identifier indicating a QoS for a second QoS data flow, the first QoS identifier and the second QoS identifier further indicating that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively;

mapping the first QoS data flow and the second QoS data flow to a first radio bearer and a second radio bearer respectively, sending the data of the first QoS data flow to a terminal device through the first radio bearer, and sending the data of the second QoS data flow to the terminal device through the second radio bearer.

2. A method of data transmission, comprising:

sending quality of service, qoS, configuration information to an access network device, the QoS configuration information comprising a first QoS identifier and a second QoS identifier, the first QoS identifier indicating a QoS for a first QoS data flow and the second QoS identifier indicating a QoS for a second QoS data flow, the first QoS identifier and the second QoS identifier further indicating that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

3. A method according to claim 1 or 2, wherein the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow.

4. A method according to any of claims 1-3, wherein the second QoS identifier further indicates that a radio bearer carrying the second QoS data flow carries only the second QoS data flow.

5. The method according to any of claims 1-4, wherein the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

6. The method according to any of claims 1-5, wherein the first QoS data flow and the second QoS data flow belong to the same data unit.

7. A method of data transmission, comprising:

receiving quality of service, qoS, configuration information from a core network element, the QoS configuration information comprising a first QoS identifier indicating a QoS for a first QoS data flow, the first QoS identifier further indicating that a radio bearer carrying the first QoS data flow carries only the first QoS data flow;

mapping the first QoS data flow to the first wireless bearer, and sending the data of the first QoS data flow to terminal equipment through the first wireless bearer.

8. A method of data transmission, comprising:

and sending QoS configuration information to access network equipment, wherein the QoS configuration information comprises a first QoS identifier, the first QoS identifier indicates QoS of a first QoS data flow, and the first QoS identifier also indicates that first access network resources bearing the first QoS data flow only bear the first QoS data flow.

9. The method according to claim 7 or 8, wherein the QoS configuration information further comprises a second QoS identifier indicating a QoS for a second QoS data flow, the second QoS identifier further indicating that a second access network resource carrying the second QoS data flow carries only the second QoS data flow.

10. The method of claim 9 wherein the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

11. A method according to claim 9 or 10, characterized in that the first QoS data flow and the second QoS data flow belong to the same data unit.

12. A communication device, comprising:

an interface unit, configured to receive QoS configuration information from a core network element, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates QoS of a first QoS data flow, the second QoS identifier indicates QoS of a second QoS data flow, and the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different radio bearers, respectively;

and the processing unit is used for mapping the first QoS data flow and the second QoS data flow to a first radio bearer and a second radio bearer respectively, controlling the device to send the data of the first QoS data flow to terminal equipment through the first radio bearer, and controlling the device to send the data of the second QoS data flow to the terminal equipment through the second radio bearer.

13. A communication device, comprising:

an interface unit, configured to send QoS configuration information to an access network device, where the QoS configuration information includes a first QoS identifier and a second QoS identifier, where the first QoS identifier indicates QoS of a first QoS data flow, the second QoS identifier indicates QoS of a second QoS data flow, and the first QoS identifier and the second QoS identifier further indicate that the first QoS data flow and the second QoS data flow are mapped to different access network resources, respectively.

14. The communication apparatus according to claim 12 or 13, wherein the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow.

15. The communication apparatus according to any of claims 12-14, wherein the second QoS identifier further indicates that a radio bearer carrying the second QoS data flow carries only the second QoS data flow.

16. The communication apparatus according to any of claims 12-15, wherein the traffic importance of the first QoS data flow is higher than the traffic importance of the second QoS data flow.

17. The communication apparatus according to any of claims 12-16, wherein the first QoS data flow and the second QoS data flow belong to the same data unit.

18. A communication device, comprising:

an interface unit, configured to receive quality of service QoS configuration information from a core network element, where the QoS configuration information includes a first QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, and where the first QoS identifier further indicates that a radio bearer carrying the first QoS data flow carries only the first QoS data flow;

and the processing unit is used for mapping the first QoS data flow to the first wireless bearer and controlling the device to send the data of the first QoS data flow to the terminal equipment through the first wireless bearer.

19. A communication device, comprising:

an interface unit, configured to send quality of service QoS configuration information to an access network device, where the QoS configuration information includes a first QoS identifier, where the first QoS identifier indicates a QoS of a first QoS data flow, and where the first QoS identifier further indicates that a first access network resource carrying the first QoS data flow carries only the first QoS data flow.

20. The apparatus according to claim 18 or 19, wherein the QoS configuration information further comprises a second QoS identifier indicating a QoS for a second QoS data flow, the second QoS identifier further indicating that a second access network resource carrying the second QoS data flow carries only the second QoS data flow.

21. The apparatus of claim 20, wherein traffic importance of the first QoS data flow is higher than traffic importance of the second QoS data flow.

22. The apparatus according to claim 20 or 21, wherein the first QoS data flow and the second QoS data flow belong to the same data unit.

23. A communication device comprising a processor coupled to a memory for storing a computer program or instructions, the processor for executing the computer program or instructions in memory, causing the device to perform the method of any one of claims 1 to 6 or to perform the method of any one of claims 7 to 11.

24. A computer readable storage medium, characterized in that it has stored thereon a computer program or instructions, which when run on a computer, cause the computer to perform the method according to any of claims 1 to 6; or, a method as claimed in any one of claims 7 to 11.

25. A chip system, comprising: a processor for calling and running a computer program from a memory, causing a communication device in which the chip system is installed to perform the method of any one of claims 1 to 6 or to perform the method of any one of claims 7 to 11.

26. A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the steps of the method according to any one of claims 1 to 6 or to perform the steps of the method according to any one of claims 7 to 11.