WO2018082431A1 - 无线通信方法、用户设备接入网设备、和核心网设备 - Google Patents

无线通信方法、用户设备接入网设备、和核心网设备 Download PDF

Info

Publication number
WO2018082431A1
WO2018082431A1 PCT/CN2017/105537 CN2017105537W WO2018082431A1 WO 2018082431 A1 WO2018082431 A1 WO 2018082431A1 CN 2017105537 W CN2017105537 W CN 2017105537W WO 2018082431 A1 WO2018082431 A1 WO 2018082431A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
qos
network device
downlink data
data
Prior art date
Application number
PCT/CN2017/105537
Other languages
English (en)
French (fr)
Inventor
李宏
韩锋
晋英豪
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17866919.8A priority Critical patent/EP3528533B1/en
Publication of WO2018082431A1 publication Critical patent/WO2018082431A1/zh
Priority to US16/403,045 priority patent/US11044629B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality

Definitions

  • the embodiments of the present invention relate to the field of wireless network communications, and in particular, to a wireless communication method, a user equipment, an access network device, a core network device, and a network system.
  • the quality of service (QoS) management of the existing LTE system is based on bearers to achieve end-to-end QoS guarantee.
  • the bearer is a logical set of one or more service data flows between a User Equipment (UE) and a Packet Data Network Gateway (P-GW).
  • UE User Equipment
  • P-GW Packet Data Network Gateway
  • the service data flows carried by the same Evolved Packet System (EPS) will be subject to the same packet forwarding processing (such as scheduling policy, queuing management policy, rate adjustment policy, RLC configuration, etc.).
  • EPS Evolved Packet System
  • the QoS guarantee can be implemented by the P-GW from the P-GW to the UE, including: S5/S8 bearer between the P-GW and the Serving Gateway (S-GW), S- The S1 bearer between the GW and the evolved base station (Evolved Node B; eNB for short) and the radio bearer between the eNB and the UE.
  • S-GW Serving Gateway
  • S1 bearer between the GW and the evolved base station (Evolved Node B; eNB for short
  • eNB evolved base station
  • the above S5/S8 bearer, S1 bearer and radio bearer are collectively referred to as an EPS bearer, and the attributes of the EPS bearer are given by the P-GW.
  • the attributes of the bearer correspond to a set of QoS processing modes, and the data in the same bearer adopts the same data packet forwarding mode.
  • the P-GW maps the service data flow to the EPS bearer.
  • the S5/S8 bearer, the S1 bearer, and the radio bearer the QoS requirements of the service are guaranteed by the attributes of the EPS bearer.
  • the existing LTE system adopts QoS control for data transmission based on bearer granularity, and multiple Internet Protocol (IP) flows are mapped to one EPS bearer.
  • IP Internet Protocol
  • the EPS bearer is the smallest unit of QoS control, that is, the data flow in the same EPS bearer is not distinguished by QoS.
  • the radio bearer, the S1 bearer, and the S5/S8 bearer between the UE and the P-GW adopt a 1:1 mapping manner.
  • the existing LTE system adopts the QoS control of data transmission based on the granularity of the EPS bearer, and multiple IP flows are mapped to one EPS bearer, and the EPS bearer is the minimum unit for the bearer level QoS control in the EPS, that is, the data flow in the same EPS bearer. Do not make QoS distinctions.
  • the air interface, AN, and CN bearers between the UE and the P-GW adopt a 1:1 mapping manner. If a new data stream needs to be transmitted and the data stream cannot be mapped to an existing data bearer, then a dedicated EPS data bearer needs to be created.
  • the LTE system For the uplink data transmission, the LTE system also uses the bearer mapping method to map the data stream to the bearer.
  • the network sends the mapping mode to the UE in the form of a template, and the network also passes the service-related QoS information.
  • the signaling is sent to the UE, such as an authorized QoS class.
  • the UE uses the template delivered by the network to perform data flow mapping. If there is no suitable bearer, the UE requests to establish a bearer to the network through signaling.
  • the uplink data transmission multiple signaling interactions between the UE and the network (including the core network and the access network) are required, and more network functional units are involved, and the signaling overhead is relatively large. It also causes a large delay.
  • Embodiments of the present invention provide a wireless communication method, a user equipment, an access network device, and a network system, which are intended to reduce delay.
  • an embodiment of the present invention provides a method for wireless communication, including the following steps: a user equipment receives downlink data from a first bearer, and a reflected quality of service QoS attribute of the first bearer is supported.
  • the user equipment When the user equipment is to send uplink data corresponding to the downlink data to the access network device, the user equipment confirms the second The bearer, wherein the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the user equipment sends the uplink data by using the second bearer.
  • the user equipment receives the downlink data from the first bearer. If the QoS attribute of the reflected quality of the first bearer is supported, the user equipment may directly transmit the uplink data corresponding to the downlink data according to the first bearer.
  • the QoS information determines the QoS information of the second bearer, and can avoid using the signaling to obtain the QoS information. Reduce signaling overhead and reduce latency.
  • the bearer QoS information used for the downlink data transmission is determined according to the bearer QoS information used for the uplink data transmission, which can ensure the user's service experience.
  • the second bearer is the same as the first bearer or the second bearer is established after the user equipment receives the downlink data.
  • the uplink data transmission may be directly used by using the first bearer to avoid the process of re-establishing the bearer. Reduce signaling overhead and reduce latency.
  • the user equipment may perform establishment of the second bearer according to characteristics of the uplink data. This can also be applied to scenarios where an uplink bearer needs to use an independent bearer and a scenario where the first bearer cannot perform uplink data transmission.
  • the method before the user equipment receives the downlink data from the first bearer, the method further includes: the user equipment receiving QoS information of the first bearer, the first The carried QoS information includes the QoS level supported by the first bearer and the reflected QoS attribute of the first bearer.
  • the user equipment obtains the QoS information of the first bearer in advance, and when the downlink data is received from the first bearer, the QoS information of the second bearer is directly determined according to the QoS information of the first bearer, and the second bearer is not required to be obtained through signaling interaction.
  • QoS information saves signaling interaction and reduces latency.
  • the user equipment needs to directly perform uplink data transmission, the data can be mapped to a suitable bearer to reduce the delay.
  • the downlink data includes a bearer quality of service indication BQI of the first bearer, and the BQI of the first bearer includes QoS information of the first bearer.
  • the user equipment can confirm the bearer it should use through BQI.
  • the QoS indication of the bearer in a manner of data transmission, the signaling overhead indicated by the signaling can be reduced.
  • the embodiment of the present invention provides a wireless communication method, including the following steps: the access network device sends the first downlink data by using the first bearer, and the reflected quality of service QoS attribute of the first bearer is supported; The access network device uses the second bearer to receive the first uplink data corresponding to the first downlink data, where the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the second bearer is the same as the first bearer or the second bearer is established after the access network device receives the downlink data.
  • the method before the access network device sends the first downlink data by using the first bearer, the method further includes: the access network device receiving the QoS of the first bearer The information, the QoS information of the first bearer includes a QoS level supported by the first bearer and a reflected QoS attribute of the first bearer. After the access network device obtains the QoS information of the first bearer, the bearer mapping of the data can be conveniently performed.
  • the first downlink data includes a bearer quality of service indication BQI of the first bearer, and the BQI of the first bearer includes QoS information of the first bearer.
  • the access network device uses the first bearer to send the first downlink number
  • the method further includes: the access network device receiving, in a form of a stream, second downlink data from a core network device, where the second downlink data includes a reflected QoS indication; Obtaining, by the second downlink data, the first downlink data, where the first downlink data does not include a reflected QoS indication; and the access network device maps the first downlink data to the first bearer.
  • the first downlink data that is mapped to the first bearer by the access network device does not need to include the reflected QoS indication, and the data transmission overhead of the air interface can be saved.
  • the method further includes: the access network device demapping the first uplink data And the access network device acquires second uplink data according to the first uplink data, where the second uplink data includes a flow priority indication FPI; and the access network device sends the first Two uplink data to the core network device.
  • This technical solution is particularly suitable for scenarios where the core network uses streams for transmission.
  • the access network device is an access network user plane device.
  • the method further includes: The access network user plane device sends a bearer setup request to the access network control plane device; the access network user plane device receives a bearer setup response, where the bearer setup response includes the identifier of the first bearer and the QoS information of the first bearer. And the reflected QoS attribute of the first bearer.
  • the bearer is established when the downlink data is transmitted, and the corresponding bearer may be established by referring to the characteristics of the first downlink data, and the QoS information is not acquired by using separate signaling.
  • the access network device uses the first bearer to send third downlink data related to the first downlink data to the UE.
  • the bearer established when transmitting the first downlink data may be reserved for transmission of the subsequent related third downlink data. Avoid duplicate builds of bearers.
  • the embodiment of the present invention provides a wireless communication method, including the following steps: a core network device sends a first downlink data by using a first bearer, and a reflective service quality QoS attribute of the first bearer is supported; The network device uses the second bearer to receive first uplink data corresponding to the first downlink data, and the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the second bearer is the same as the first bearer or the second bearer is established after the core network device receives the downlink data.
  • the method before the core network device sends the first downlink data by using the first bearer, the method further includes: the core network device receiving QoS information of the first bearer,
  • the QoS information of the first bearer includes a QoS level supported by the first bearer and a reflected QoS attribute of the first bearer.
  • the first downlink data includes a bearer quality of service indication BQI of the first bearer, and the BQI of the first bearer includes QoS information of the first bearer.
  • an embodiment of the present invention provides a user equipment, where the user equipment has a function of implementing user equipment behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the user equipment includes a transmitter, a receiver, and a processor.
  • the receiver is configured to receive downlink data from the first bearer, the reflected quality of service QoS attribute of the first bearer being supported.
  • the processor is configured to: when the uplink data corresponding to the downlink data is to be sent to the access network device, confirm the second bearer, where the QoS information of the second bearer is based on the QoS information of the first bearer definite. Place
  • the transmitter is configured to transmit the uplink data using the second bearer.
  • the receiver is further configured to receive QoS information of the first bearer, where the QoS information of the first bearer includes a QoS level supported by the first bearer and a reflective QoS attribute of the first bearer. .
  • an embodiment of the present invention provides an access network device, where the access network device has a function of implementing the behavior of the access network device in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the access network device includes a transmitter and a receiver.
  • the transmitter is configured to send the first downlink data by using the first bearer, the reflected quality of service QoS attribute of the first bearer is supported;
  • the receiver is configured to receive the downlink data by using the second bearer Corresponding first uplink data, the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the receiver is further configured to receive QoS information of the first bearer, where the QoS information of the first bearer includes a QoS level supported by the first bearer and a reflected QoS attribute of the first bearer.
  • the receiver is further configured to receive second downlink data from the core network device in the form of a stream, the second downlink data comprising a reflected QoS indication.
  • the access network device further includes a processor, the processor configured to acquire the first downlink data according to the second downlink data, where the first downlink data does not include a reflected QoS indication; The first downlink data is mapped to the first bearer.
  • the processor is further configured to: demap the first uplink data to a data stream; acquire second uplink data according to the first uplink data, where the second uplink data includes a flow priority The level indicates the FPI.
  • the transmitter is further configured to send the second uplink data to the core network device in the form of a stream.
  • the access network device is an access network user plane device.
  • the transmitter is further configured to send a bearer setup request to the access network control plane device.
  • the receiver is also configured to receive a bearer setup response.
  • the bearer setup response includes an identifier of the first bearer, QoS information of the first bearer, and a reflected QoS attribute of the first bearer.
  • the transmitter is further configured to use the first bearer to send third downlink data related to the first downlink data to the UE.
  • an embodiment of the present invention provides a core network device, where the core network device has a function of implementing a behavior of a core network device in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the core network device includes a transmitter and a receiver.
  • the transmitter is configured to send the first downlink data by using the first bearer, the reflected quality of service QoS attribute of the first bearer is supported;
  • the receiver is configured to receive the downlink data by using the second bearer Corresponding first uplink data, the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the receiver is further configured to receive QoS information of the first bearer, where the QoS information of the first bearer includes a QoS level supported by the first bearer and a reflected QoS attribute of the first bearer.
  • the embodiment of the present invention provides a communication system, where the system includes the user equipment and the access network device according to the foregoing aspect; or the system includes the access network device and the core network device according to the foregoing aspect; Alternatively, the system includes the user equipment, the access network equipment, and the core network equipment described in the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the user equipment, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the access network device, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the core network device, including a program designed to perform the above aspects.
  • FIG. 1 is a schematic diagram of a wireless communication system in accordance with an embodiment of the present patent application.
  • FIG. 2 is a schematic diagram of interaction of a communication method in accordance with another embodiment of the present patent application.
  • FIG. 3 is a schematic diagram of interaction of a communication method in accordance with another embodiment of the present patent application.
  • FIG. 4 is a schematic diagram of interaction of a communication method in accordance with another embodiment of the present patent application.
  • FIG. 5 is a schematic diagram of interaction of a communication method according to another embodiment of the present patent application.
  • FIG. 6 is a schematic structural diagram of a terminal according to still another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network device according to still another embodiment of the present invention.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • connection herein may be a direct connection or an indirect connection.
  • a “functional entity” is an entity that implements a function that includes the corresponding hardware structure and/or software modules that perform the function.
  • bearer in this context is a data transmission channel established by the network to achieve differentiated data transmission and corresponding to QoS.
  • a bearer may be implemented in a data tunnel manner, for example, a logical data transmission channel based on the GPRS Tunneling Protocol (GTP) established between the source node and the destination node of the data transmission. All data flows on a bearer do not distinguish between QoS control, have the same packet forwarding processing mode, and perform data transmission according to the transmission protocol corresponding to the transmission channel.
  • GTP GPRS Tunneling Protocol
  • QoS Reflective QoS
  • the term QoS means that the uplink data transmission QoS is a reflection of the downlink data transmission QoS.
  • the basic idea is to determine the QoS information of the uplink data transmission according to the QoS information of the downlink data transmission.
  • RQI Reflective QoS Indication
  • the term "transported QoS attribute of a bearer” herein refers to whether the bearer supports reflected QoS transmission. If a bearer supports reflection QoS, the reflected QoS attribute of the bearer is supported, and the network can map the data containing the reflected QoS indication to the bearer. If a bearer does not support reflected QoS transmission, the reflected QoS attribute of the bearer is not supported.
  • QoS class of bearer refers to the processing priority of each bearer when the access network device processes the data corresponding to the bearer.
  • the QoS class of the bearer may be embodied in the form of a QoS Classification Identifer (QCI).
  • QCI QoS Classification Identifer
  • Flow Priority Indicator refers to the processing priority of each stream when the core network or the access network device processes data corresponding to the stream.
  • the FPI can correspond to the scheduling priority of network convection when congestion occurs.
  • the FPI can be an identifier similar to a QCI.
  • BQI Bit Quality of Service
  • the term "Bearer QoS Indicator" is used to indicate the corresponding QoS information of the bearer.
  • the BQI indicates the processing priority of the data on each bearer.
  • the BQI can also be used to indicate whether the bearer supports reflection QoS.
  • the BQI can also be used to indicate to the UE how to do the data to bearer mapping.
  • the BQI may include a data-to-bearer mapping indication, and the UE may determine the bearer according to the indication of the BQI.
  • the term "data stream” as used herein refers to application data related to a certain service generated by a UE or a data network, such as an IP stream. In order to pass the data to the peer, it needs to be transmitted over the network.
  • the network transforms high-level data into a form suitable for transmission over the network.
  • the stream-based transmission method means that for the data packets in the same stream, the network uses the same packet forwarding treatment and is processed by the same QoS rule.
  • Stream-based transmission methods may include transmission in the form of streams or in the form of streams. Different from the bearer-based QoS control mode, different data flows may be mapped to the same bearer, and the data flows in the same bearer are not distinguished by QoS.
  • the mapping of data streams and bearers can be 1:1 or N:1. Mapping method is also possible and data flow
  • the QoS attribute is related to, for example, a 1:1 mapping manner for a guaranteed bit rate (GBR) data stream, and a non-guaranteed bit rate (non-guaranteed bit rate, non-GBR) data stream. Use the N:1 mapping method.
  • a bearer may be a mapping of one or more data streams, and transmitting in a bearer manner may reduce signaling overhead. The more the number of data flows mapped to a bearer, the smaller the number of bearers that the network needs to establish, and the smaller the corresponding signaling overhead.
  • QoS rule in this context is a set of information based on operator requirements based on application requirements and QoS parameters, used to detect service data flows or data and define its associated QoS parameters, and to determine how data flows or data are transmitted.
  • the manner in which the data stream is transmitted may include streaming or by bearer. Streaming may be the transmission of data packets of the data stream in accordance with an IP transport protocol.
  • the bearer transmission may be to map one or more data streams onto one bearer for transmission.
  • the QoS rules may include QoS requirement information of the data stream and/or transmission mode of the data stream, for example, transmission in a bearer manner or transmission in a data stream manner.
  • the QoS requirement information may include a data rate, a transmission delay, and the like.
  • the QoS rules may also include mappings between bearers and data flows.
  • mapping refers to mapping one or more data streams having the same or similar QoS to one bearer, each bearer corresponding to a set of QoS parameters.
  • the QoS parameter may include the QoS class of the service, the maximum bit rate (MBR), and the allocation and retention priority (ARP), and is used to identify the network to process the data on the bearer. the way. The same data forwarding processing method is adopted for the data on the same bearer.
  • the Core Network Control Plane (AN CP) functional entity and the UE user plane functional entity may map multiple data flows with different QoS to one or more bearers.
  • the CN UP functional entity, the AN CP functional entity, and the UE user plane functional entity may perform a flow demapping operation.
  • mapping in this paper is the inverse of "mapping", that is, demapping a data on a bearer to a different data stream. It is worth noting that the mapping and demapping processes are optional operations, and each user plane functional entity determines whether to perform corresponding operations according to the obtained QoS rules.
  • pre-authorization QoS means that the network pre-authorizes the data transmission of certain specific services of the UE to correspond to a specified level of QoS. It can be used as part of the user's subscription content.
  • the network may pre-authorize the corresponding UE to directly correspond to a higher QoS level when initiating the health monitoring service, so that when the UE initiates the corresponding service, the network side can directly establish a dedicated bearer for the user. There is no need to re-do the business authorization process.
  • pre-authorized QoS bearer in this document means that for some data with pre-authorized QoS attributes, the network will directly establish corresponding bearers for such data after the session establishment is completed, even if there is no such data at this time. send. Thereby reducing the delay of waiting for the bearer to be established after the data arrives.
  • FIG. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present invention.
  • the wireless communication system includes a UE, an Access Network (AN) device, and a Core Network (CN) device.
  • the UE and the AN device are connected through an air interface.
  • the AN device and the CN device can be connected by wire or wirelessly.
  • the UE implements data communication service through the AN device and the CN device.
  • the UE in this embodiment may also refer to a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol ("SIP") phone, a Wireless Local Loop (WLL) station, or a personal digital assistant (Personal Digital Assistant, Referred to as "PDA”), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, or a future evolved public land mobile communication network ( Terminal devices in the Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • the AN device in the embodiment of the present application may be a device for communicating with a terminal device, where the AN device may be a Base Transceiver Station ("BTS”) in GSM or CDMA, or may be a base station in a WCDMA system (
  • BTS Base Transceiver Station
  • NB may also be an evolved base station (Evolutional NodeB, hereinafter referred to as “eNB or eNodeB”) in the LTE system, or may be a cloud radio access network (CRAN) scenario.
  • eNB evolved base station
  • CRAN cloud radio access network
  • the underlying wireless controller, or the AN device may be a relay station, an access point, an in-vehicle device, a wearable device, and an AN device in a future 5G network, or may be an AN device in a future evolved network.
  • the AN device may also be a Next-generation Node B (gNB), a Transmit and Receive Point (TRP), a Central Unit (CU), or a distributed unit device. (Distributed Unit; referred to as: DU) and so on.
  • the AN device includes an Access Network Control Plane (AN CP) functional entity and an Access Network User Plane (AN UP).
  • the AN CP functional entity is connected to the AN UP functional entity.
  • the AN CP functional entity has QoS control functions that can control the QoS processing of the AN UP functional entity.
  • the AN CP functional entity may send the QoS rule to the AN UP functional entity.
  • the AN UP functional entity performs data transmission according to the received QoS rules.
  • the CN device can be a gateway, a router, a data center, a server, a network management device, or the like.
  • the CN device includes a Core Network Control Plane (CN CP) functional entity and a Core Network User Plane (CN UP) functional entity.
  • CN CP Core Network Control Plane
  • CN UP Core Network User Plane
  • the CN CP functional entity is connected to the CN UP functional entity.
  • the CN CP functional entity has a QoS control function that can control the QoS processing of the CN UP functional entity.
  • the CN CP functional entity can send QoS rules to the CN UP functional entity.
  • the CN UP functional entity performs data transmission according to the received QoS rules.
  • the CN device may further include a policy function entity.
  • the policy function entity is configured to formulate a corresponding QoS control policy according to the subscription information of the user and the policy of the operator, and perform service QoS authorization on the received QoS authorization request.
  • the policy function entity can be connected separately from the AN CP functional entity and the CN CP functional entity.
  • the policy function entity is configured to send QoS authorization information to the AN CP functional entity and the CN CP functional entity.
  • the policy function entity may also be separately connected to the AN UP function entity and the CN UP function entity, and configured to send the QoS authorization information to the AN UP function entity and the CN UP function entity.
  • both the AN device and the CN device have logically independent QoS control functions, which are implemented by the AN CP functional entity and the CN CP functional entity, respectively.
  • the AN CP functional entity and the CN CP functional entity have similar QoS control functions, but the scope of control is different.
  • the CN CP functional entity mainly controls the QoS processing of the CN UP functional entity
  • the AN CP functional entity mainly controls the QoS processing of the AN UP functional entity.
  • the resources of the core network and the access network are different.
  • the core network and the access network should be able to implement different QoS control methods according to their respective resource usage. Flexible QoS management capabilities.
  • the AN device has a QoS management function, can manage and control data transmission of the AN user plane, improves the flexibility of service QoS management in the wireless communication network, and provides the possibility of independent evolution of the respective QoS frameworks of the CN and the AN. Sex.
  • the above wireless communication system can also communicate with an Application Function (AF) entity and a Data Network (DN).
  • An AF entity can provide data flow services with specific QoS requirements similar to an application server. It can be a network operator deployment or a third-party deployment.
  • a data network can provide some type of data service, generally an external network, similar to a Packet Data Network (PDN). Types of data networks include but are not limited to: Internet (English: Internet), IP Multimedia Subsystem (English: IP Multimedia Subsystem, referred to as: IMS)
  • FIG. 2 is a schematic diagram of interaction of a communication method in accordance with an embodiment of the present patent application. As shown in FIG. 2, the method includes the following steps:
  • the UE After the user successfully accesses the network, the UE establishes a session between the wireless communication system and the data network. In this process, the UE obtains an identity, such as an IP address, for communicating with the data network.
  • the session can be a Protocol Data Unit (PDU) session.
  • PDU Protocol Data Unit
  • the AN CP function entity initiates establishing a bearer between the UE and the AN UP functional entity.
  • the bearer in step 202 may be a default bearer or a pre-authorized QoS bearer.
  • the AN CP functional entity During the establishment of the bearer, the AN CP functional entity generates a bearer identifier, which can be used to identify the bearer.
  • the AN CP functional entity configures QoS information, such as QoS class, for the bearer.
  • QoS information such as QoS class
  • the AN CP functional entity may also allocate corresponding network resources to the bearers according to the QoS information.
  • Network resources can be bandwidth, storage resources, and the like.
  • the AN CP functional entity can also classify bearers.
  • the bearers can be divided into two types: bearer of Reflective QoS Enabled (RQ Enabled) and bearer of Refractal QoS (Non-RQ Enabled).
  • RQ Enabled Reflective QoS Enabled
  • Non-RQ Enabled The bearer of RQ Enabled can be used to support reflection QoS, and its reflection QoS attribute is supported.
  • the bearer of Non-RQ Enabled cannot be used to support reflection QoS, and its reflection QoS attribute is not supported.
  • a classification method may be that the AN CP functional entity classifies the bearers that have been established. For example, if 10 bearers have been established, the bearers can be divided into RQ Enabled bearers and Non-RQ Enabled bearers according to a certain number of proportions.
  • Another classification method can be a static classification method. That is, fixed numbered bearers are defined as RQ enabled bearers or Non-RQ Enabled bearers. For example, if up to 10 bearers are supported for the UE, the 10 bearers can be numbered. For simplicity, in one example, the numbers can be defined as 1, 2, 3...10.
  • the static classification method can fixedly define or reserve the bearer 1 to the bearer 5 as RQ Enabled, and the bearer 6 to the bearer 10 is defined as or reserved as Non-RQ Enabled. After the subsequent bearer is established, the appropriate number is selected for the bearer according to the reflected QoS attribute of the bearer.
  • the UE can confirm that the reflected QoS is used in the corresponding uplink data according to the bearer type of the data transmission. This can save the data transmission overhead of the air interface and improve the effective data transmission efficiency of the network.
  • the AN CP function entity sends the bearer information to the AN UP function entity.
  • the AN UP functional entity receives the The information carried.
  • the bearer information includes: bearer identifier and bearer QoS information.
  • the bearer's QoS information includes the attributes of the supported QoS class and RQ.
  • the bearer identity may be a flag of the bearer established in step 202.
  • the QoS level supported by the bearer can be embodied in the form of QCI.
  • the RQ attribute can be RQ Enabled or Non-RQ Enabled.
  • the AN CP function entity sends the bearer information to the UE.
  • the UE receives the information of the bearer.
  • the information carried in can be referred to the description in step 203.
  • the data network sends the downlink data to the CN UP functional entity in the form of a data packet.
  • the CN UP function entity receives the downlink data.
  • the CN UP function entity processes the downlink data and matches the downlink data to the data stream.
  • the CN UP function entity sends the downlink data to the AN UP functional entity in the form of a stream.
  • the AN UP function entity receives the downlink data.
  • the CN UP function entity adds QoS information of the data stream to the header of the downlink data. Includes: FPI and RQI.
  • the CN UP function entity may also add a data stream ID in the header of the downlink data.
  • the matching manner may adopt a template filtering manner. For example, define a parameter group and set a value or range of values for each parameter in the group. When the relevant parameters of the data packet are the same as the preset values, or fall within the preset value range. The packet can be mapped to the corresponding data stream.
  • the parameter group can be an IP quintuple.
  • the IP quintuple includes the destination IP address, source IP address, destination port number, source port number, and protocol type.
  • the AN UP function entity processes the received downlink data, and maps the processed downlink data to the first bearer.
  • the first bearer may be one of the bearers established in step 202.
  • the processing procedure of the AN UP function entity may be: acquiring the downlink data that needs to be sent in step 208 according to the downlink data received in step 206.
  • the downlink data mentioned in step 208 may be referred to as first downlink data
  • the downlink data mentioned in step 206 may be referred to as second downlink. data.
  • the AN UP function entity can remove the RQI in the first downlink packet header. That is, the second downlink data includes the RQI, and the first downlink data does not include the RQI.
  • the second downlink data may further include an FPI
  • the first downlink data does not include the FPI. That is, there is no FPI and RQI in the header of the first downlink data.
  • the AN UP functional entity can also generate a new packet header.
  • the data stream ID can be included in the new packet header.
  • BQI can also be included in the new header.
  • the way to generate a new packet header can be to replace each old packet header with a new header.
  • the AN UP functional entity When the AN UP functional entity receives more than one data stream, if some data streams have the same or similar QoS requirements, the AN UP functional entity can map these data streams to the same bearer. If these data streams contain RQI, the bearer can be of type RQ Enabled.
  • the AN UP functional entity may also record an FPI indication for each data stream.
  • the uplink data transmission when the AN UP function entity sends the uplink data to the CN UP function entity in the form of a stream, the corresponding FPI is added in the header of the data.
  • the AN UP function entity sends the processed downlink data to the UE by using the first bearer.
  • the UE receives the downlink data by using the first bearer.
  • the downlink data in this step may include a BQI.
  • the QoS attribute of the first bearer may be further indicated to the UE by the BQI.
  • the BQI can also be used to indicate to the UE how to do the mapping of the upper and lower data to the bearer.
  • the UE checks the uplink data, if the uplink is The data corresponds to the downlink data received in step 208, and the second bearer may be confirmed by referring to the first bearer used in step 208.
  • the QoS information of the second bearer is determined according to the QoS information of the first bearer.
  • the uplink data corresponds to the downlink data, and the uplink data and the downlink data belong to the same service flow.
  • a session may contain multiple service flows, one for each service type and one for QoS control.
  • the uplink data corresponds to the downlink data, and the uplink data belongs to the same session stream as the downlink data.
  • the QoS information of the second bearer is determined according to the QoS information of the first bearer, for example, the QoS level of the second bearer is determined according to the QoS level of the first bearer. Certainly, corresponding other QoS information of the second bearer may also be determined according to other QoS information of the first bearer.
  • the QoS level of the second bearer is the same as the QoS level of the first bearer, that is, the two are in one-to-one correspondence.
  • the level of the second bearer can be determined directly from the level of the first bearer.
  • the QoS level of the second bearer and the QoS level of the first bearer correspond to each other.
  • the channel corresponding to the uplink bearer and the downlink bearer may be asymmetric.
  • the bandwidth of the downlink channel is greater than that of the uplink channel.
  • different definitions may be used for the uplink and downlink.
  • the maximum bit rate of the downlink bearer may be greater than the maximum bit rate of the uplink and downlink bearers.
  • the QoS level of the downlink bearer may be more than the QoS class of the uplink bearer. Then, when determining the QoS level of the uplink bearer according to the QoS class of the downlink bearer, the one-to-one correspondence manner is not adopted, but only one correspondence relationship exists between the two. Referring to this correspondence, the level of the second bearer can be determined from the level of the first bearer.
  • first bearer and the second bearer may be the same or different. If the first bearer is a bidirectional bearer, the second bearer and the first bearer may be the same.
  • the second bearer can also be a new bearer.
  • the first bearer is a unidirectional bearer, or the uplink and downlink data need to be transmitted on different bearers.
  • the UE may send a bearer setup request to the AN CP function entity, and trigger the AN CP function entity to establish a new bearer, where the new bearer and the first bearer have the same or corresponding QoS characteristics.
  • the new bearer is established after the UE receives the downlink data.
  • the UE may also confirm the second bearer according to the BQI.
  • the BQI may also include a mapping manner of the data stream to the bearer, for example, a mapping template, and the UE may map the uplink data stream to the existing bearer according to the indication of the BQI.
  • step 209 the UE can match the uplink data to the data stream. For the matching manner, refer to the description of step 206.
  • the UE then maps the data stream to the second bearer. It is worth noting that the UE can also directly map the uplink data to the second bearer.
  • the UE sends uplink data to the AN UP function entity by using the second bearer.
  • the AN UP function entity receives the uplink data.
  • the AN UP function entity processes the uplink data, and demaps the processed uplink data to the data stream.
  • the processing of the AN UP function entity may be: acquiring the uplink data that needs to be sent in step 212 according to the uplink data received in step 210.
  • the uplink data mentioned in step 210 may be referred to as first uplink data
  • the uplink data referred to in step 212 may be referred to as second uplink data.
  • the header of the first uplink data does not include the FPI, and the AN UP function entity can process it, and the packet of the second uplink data
  • the header increases its corresponding FPI, that is, the second uplink data includes the FPI.
  • the AN UP function entity sends the processed uplink data to the CN UP function entity in a stream manner.
  • the CN UP function entity receives the uplink data.
  • the CN UP function entity sends the received uplink data to the data network.
  • step 204 is optional, and in some cases, step 204 may not be performed.
  • step 204 can be omitted.
  • steps 203 and 204 are not limited. Step 203 may be performed first and then step 204 may be performed first or step 204 may be performed before step 203 or step 203 and step 204 may be performed simultaneously.
  • FIG. 3 is a schematic diagram of interaction of a communication method in accordance with another embodiment of the present patent application. As shown in FIG. 3, the method includes the following steps:
  • 301 substantially the same as 201, can refer to 201, and will not be described again.
  • the data network sends the first downlink data to the CN UP functional entity.
  • the CN UP function entity receives the first downlink data.
  • the CN UP function entity processes the first downlink data, and matches the first downlink data to the data stream.
  • the CN UP function entity sends the first downlink data to the AN UP function entity in the form of a stream.
  • the AN UP function entity receives the downlink data. This step can also refer to the description of step 206, and will not be described again.
  • the AN UP function entity sends a bearer setup request to the AN CP function entity.
  • the AN CP functional entity receives the bearer setup request.
  • the bearer setup request includes the requested QoS information, and the requested QoS information is the same as the QoS information included in the first downlink data.
  • the AN CP function entity initiates establishing a bearer between the UE and the AN UP functional entity.
  • the AN CP function entity initiates establishment of a bearer between the UE and the AN UP according to the QoS information contained in the bearer setup request.
  • the bearer established in step 305 may be referred to as a first bearer.
  • the AN CP functional entity During the establishment of the bearer, the AN CP functional entity generates a bearer identifier, which can be used to identify the bearer.
  • the AN CP function entity configures QoS parameters, such as QoS levels, for the bearer.
  • QoS parameters such as QoS levels
  • the AN CP function entity also allocates corresponding network resources to the bearers according to the pre-authorization QoS information.
  • Network resources can be bandwidth, storage resources, and the like.
  • the bearer attribute may be identified as RQI Enabled.
  • the AN CP function entity sends a bearer setup response to the AN UP function entity, and the AN UP function entity receives the bearer setup response.
  • the bearer setup response contains the information of the bearer.
  • the bearer information includes: bearer identifier and bearer QoS information.
  • the bearer's QoS information includes the QoS level supported by the bearer.
  • the carried QoS information may also include attributes of the RQ. In this embodiment, the attribute of the RQ of the bearer established in step 305 is RQ Enabled.
  • the AN CP function entity sends the bearer information to the UE, and the UE receives the information about the bearer.
  • the bearer information includes: bearer identifier and bearer QoS information.
  • the bearer's QoS information includes the attributes of the supported QoS class and RQ. In this embodiment, the attribute of the RQ is RQ Enabled. It is worth noting that steps 306 and 307 can be performed simultaneously.
  • the AN UP function entity processes the received first downlink data, and maps the processed first downlink data to the first bearer.
  • the first bearer is the bearer established in step 305.
  • the AN UP function entity sends the processed first downlink data to the UE by using the first bearer.
  • the UE receives the downlink data.
  • the UE checks the uplink data when the UE needs to perform uplink data transmission. If the uplink data corresponds to the downlink data received in step 309, reference may be made to the first used in step 309. Bearer, confirm the second bearer. The second bearer and the first bearer may be the same or a newly established bearer. For details, refer to the introduction in step 209.
  • the UE sends uplink data to the AN UP function entity by using the second bearer.
  • the AN UP function entity receives the uplink data.
  • the AN UP function entity processes the uplink data, and demaps the processed uplink data to the data stream.
  • the processing procedure of the AN UP function entity may be: acquiring the uplink data that needs to be sent in step 313 according to the uplink data received in step 311.
  • the uplink data mentioned in step 311 may be referred to as first uplink data
  • the uplink data referred to in step 313 may be referred to as second uplink data.
  • the header of the first uplink data does not include the FPI
  • the AN UP function entity can process it, and the corresponding FPI is added to the header of the first uplink data, that is, the first
  • the second uplink data includes the FPI.
  • the AN UP function entity sends the processed uplink data to the CN UP function entity in a stream manner.
  • the CN UP function entity receives the uplink data.
  • the CN UP function entity sends the received uplink data to the data network.
  • the definition of the bearer for RQ Enabled is dynamic.
  • the bearer that the AN UP function entity maps to after receiving the first data stream with the RQI indication is defined as the RQ Enabled bearer.
  • the AN UP function entity receives a new data stream and the new data stream is related to the first data stream with the RQI indication, for example: having the same or similar QoS requirements, and the new data stream
  • the RQI indication is also included, and the AN UP function entity can also map the new data stream to the RQ Enabled bearer.
  • the bearer established when the first downlink data is transmitted may be reserved for subsequent transmission.
  • the embodiment of the present invention may further include the following steps:
  • the data network sends the downlink data to the CN UP functional entity.
  • the CN UP function entity receives the downlink data.
  • the downlink data in step 315 may also be referred to as third downlink data.
  • the CN UP function entity processes the third downlink data, and matches the downlink data to the data stream.
  • step 316 reference may be made to step 206.
  • the AN UP function entity processes the received third downlink data, and maps the processed downlink data to the first bearer.
  • the AN UP function entity may remove the RQI in the downlink packet header, and the downlink data processed by the AN UP function entity does not include the RQI.
  • the header of the downlink data in step 315 includes the FPI, and the header of the downlink data processed by the AN UP functional entity may not include the FPI. That is, there is no FPI and RQI in the processed downlink data, and when the downlink data is transmitted, air interface resources can be saved.
  • the third bearer may also be used to perform the third downlink data transmission.
  • the third downlink data has the same or similar QoS requirements as the first downlink data, and the third downlink data also includes an RQI indication
  • the AN UP function entity may also map the third downlink data to the first bearer.
  • the AN UP function entity sends the processed downlink data to the UE by using the first bearer.
  • the UE receives the downlink data by using the first bearer.
  • step 318 reference may be made to step 208.
  • steps 310-314 may be performed after step 318.
  • the embodiment of the present invention can be applied to a scenario in which the AN uses the bearer and the CN uses the data stream. This scenario is illustrated above using Figures 2 and 3. It should be noted that the embodiment of the present invention can also be applied to scenarios in which both AN and CN use bearers. This scenario is explained below.
  • FIG. 4 is a schematic diagram of interaction of a communication method in accordance with another embodiment of the present patent application. As shown in FIG. 4, the method includes the following steps:
  • step 401 is substantially the same as step 201 and will not be described again.
  • the CN CP function entity initiates establishment of a bearer between the UE and the AN UP functional entity and between the AN UP functional entity and the AN CP functional entity.
  • the bearer in step 202 may be a default bearer or a pre-authorized QoS bearer.
  • the CN CP functional entity During the establishment of the bearer, the CN CP functional entity generates a bearer identifier, which can be used to identify the bearer.
  • the CN CP functional entity configures QoS information, such as QoS class, for the bearer.
  • QoS information such as QoS class
  • the CN CP functional entity may also allocate corresponding network resources to the bearers according to the QoS information.
  • Network resources can be bandwidth, storage resources, and the like.
  • the CN CP functional entity can also classify bearers.
  • the bearers can be divided into two types: bearer of Reflective QoS Enabled (RQ Enabled) and bearer of Refractal QoS (Non-RQ Enabled).
  • RQ Enabled Reflective QoS Enabled
  • Non-RQ Enabled The bearer of RQ Enabled can be used to support reflection QoS, and its reflection QoS attribute is supported.
  • the bearer of Non-RQ Enabled cannot be used to support reflection QoS, and its reflection QoS attribute is not supported.
  • a classification method may be that the CN CP functional entity classifies the bearers that have been established.
  • Another classification method can be a static classification method. For details, please refer to the previous introduction.
  • the CN CP function entity sends the bearer information to the CN UP function entity.
  • the CN UP function entity receives the information of the bearer.
  • the bearer information includes: bearer identifier and bearer QoS information.
  • the bearer's QoS information includes the attributes of the supported QoS class and RQ.
  • the bearer identity may be a flag of the bearer established in step 402.
  • the QoS level supported by the bearer can be embodied in the form of QCI.
  • the RQ attribute can be RQ Enabled or Non-RQ Enabled.
  • the CN CP function entity sends the bearer information to the UE.
  • the UE receives the information of the bearer.
  • the CN CP functional entity may send the bearer information to the UE through the AN CP functional entity.
  • the information carried in can be referred to the description in step 403.
  • the data network sends the downlink data to the CN UP functional entity in the form of a data packet.
  • the CN UP function entity receives the downlink data.
  • the CN UP function entity maps the downlink data to the first bearer.
  • the first bearer can be of the RQ Enabled type.
  • the CN UP function entity may also include a BQI in the header of the downlink data.
  • the CN UP may determine whether to transmit the reflected QoS to the downlink data. the way.
  • the method may be determined by the CN UP function entity sending a request to the CN CP function entity, and the CN CP function entity determines the result and then sends the result to the CN UP function entity.
  • the basis for determination can be based on the type of business, or the attributes of the business. For example, for some services whose service requirements may change frequently, the transport mode of Reflective QoS can be adopted.
  • the CN UP function entity sends the downlink data to the AN UP function entity by using the first bearer.
  • the AN UP function entity then sends the downlink data to the UE.
  • the UE receives the downlink data by using the first bearer.
  • the downlink data in this step may include a BQI.
  • the QoS attribute of the first bearer may be further indicated to the UE by the BQI.
  • the BQI can also be used to indicate to the UE how to do the mapping of the upper and lower data to the bearer.
  • the UE checks the uplink data. If the uplink data corresponds to the downlink data received in step 407, the first bearer may be referenced to confirm the second bearer. .
  • first bearer and the second bearer may be the same or different. If the first bearer is a bidirectional bearer, the second bearer and the first bearer may be the same.
  • the second bearer can also be a new bearer.
  • the first bearer is a unidirectional bearer, or the uplink and downlink data need to be transmitted on different bearers.
  • the UE may send a bearer setup request to the CN CP function entity by using the AN CP function entity, and trigger the CN CP function entity to establish a new bearer, where the new bearer and the first bearer have the same QoS characteristics.
  • the new bearer is established after the UE receives the downlink data.
  • the UE may also confirm the second bearer according to the BQI.
  • the UE sends uplink data to the AN UP function entity by using the second bearer.
  • the AN UP function entity then sends uplink data to the CN UP function entity through the second bearer.
  • the CN UP function entity receives the uplink data.
  • the CN UP function entity sends the received uplink data to the data network.
  • FIG. 5 is a schematic diagram of interaction of a communication method according to another embodiment of the present patent application. As shown in FIG. 3, the method includes the following steps:
  • 501 substantially the same as 201, can refer to 201, and will not be described again.
  • the data network sends the first downlink data to the CN UP functional entity.
  • the CN UP function entity receives the first downlink data.
  • the CN UP function entity sends a bearer setup request to the CN CP function entity.
  • the CN CP functional entity receives the bearer setup request.
  • the bearer setup request includes the requested QoS information, and the requested QoS information is the same as the QoS information included in the first downlink data.
  • the CN CP function entity initiates establishment of a bearer between the UE and the AN UP functional entity and between the AN UP functional entity and the AN CP functional entity. Refer to the introduction of step 402 for this step.
  • step 505 is substantially the same as step 403 and will not be described again.
  • step 506 is substantially the same as step 404 and will not be described again.
  • step 507. Map the first downlink data to the first bearer. Refer to the introduction of step 406 for this step.
  • step 508 is substantially the same as step 407 and will not be described again.
  • the UE checks the uplink data. If the uplink data corresponds to the downlink data received in step 407, the first bearer may be referenced to confirm the second bearer. .
  • step 510 is substantially the same as step 409 and will not be described again.
  • step 511 is substantially the same as step 410 and will not be described again.
  • step 512 is substantially the same as step 315 and will not be described again.
  • the CN UP function entity may also Mapping the third downlink data to the first bearer.
  • step 514 The method is basically the same as step 409, except that the data transmitted on the first bearer is the third downlink data.
  • steps 509-511 may be performed after step 514.
  • the method of the embodiment of the present invention can be applied to the network architecture shown in FIG. 1.
  • the method of the embodiment of the present invention can also be applied to other types of network architectures.
  • the network architecture includes a core network device and an access network device.
  • the AN UP function entity may send a request to the AN CP function entity, and the AN CP function entity determines the result and then sends the result to the AN UP function. entity.
  • the basis for the determination can be referred to the description in the embodiment shown in FIG.
  • the UE maps the uplink data to the bearer, and two methods may be used.
  • the first method is that the UE directly maps the uplink data to the bearer.
  • Another method is that the UE first maps the uplink data into a data stream and then maps the data stream to the bearer.
  • the bearer that supports the reflected QoS may be used for air interface transmission.
  • the QoS level of the corresponding uplink data transmission can be confirmed according to the QoS class of the bearer used for downlink data transmission.
  • the level of uplink data transmission is confirmed without signaling interference, and the signaling overhead is reduced.
  • the header of the downlink data may not carry the RQI, thereby reducing the load of the packet header and improving the effective data transmission efficiency of the air interface.
  • FIG. 6 is a schematic structural diagram of a terminal according to still another embodiment of the present invention.
  • the terminal 600 may include a receiver 601, a processor 602, and a transmitter 603.
  • Receiver 601 and transmitter 603 are coupled to processor 602, respectively.
  • the receiver 601 can perform the receiving step of the UE in the foregoing method embodiment, the transmitter 603 can perform the sending step of the UE in the embodiment, and the processor 602 can perform the processing steps of the UE in the embodiment, for example, check Upstream data and confirmation of the second bearer and the like.
  • FIG. 7 is a schematic structural diagram of a network device according to still another embodiment of the present invention.
  • the network device 700 can include a receiver 701, a processor 702, and a transmitter 703.
  • Receiver 701 and transmitter 703 are coupled to processor 702, respectively.
  • the network device 700 can include an access network device, for example, can include an access network user plane device (corresponding to the access network user plane functional entity in the above).
  • the receiver 701 can perform the receiving step of the access network user plane function entity in the foregoing method embodiment, and the transmitter 703 can perform the access network user plane function in this embodiment.
  • the transmitting step of the entity, the processor 702 may perform the processing steps of the access network user plane function entity in the embodiment, for example, processing the downlink data and mapping to the first bearer, processing the uplink data, and de-mapping to the data stream Wait for steps.
  • the network device 700 may also include a core network device, for example, may include a core network user plane device (corresponding to the core network user plane functional entity in the above).
  • a core network user plane device corresponding to the core network user plane functional entity in the above.
  • the receiver 701 can perform the receiving step of the core network user plane function entity in the foregoing method embodiment, and the sender 703 can perform the sending of the core network user plane function entity in this embodiment.
  • the processor 702 can perform the processing steps of the core network user plane function entity in the embodiment, for example, mapping the downlink data to the first bearer.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present patent application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM, a RandomAcces slice manager emory), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.

Abstract

本发明实施例公开了一种无线通信方法、用户设备、接入网设备、核心网设备和网络系统。该方法包括：用户设备从第一承载上接收下行数据，所述第一承载的反射服务质量QoS属性是支持。当所述用户设备要向接入网设备发送与所述下行数据相对应的上行数据，所述用户设备确认第二承载，其中所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。所述用户设备使用所述第二承载发送所述上行数据。使用该方法可以减少信令开销，降低时延。

Description

无线通信方法、用户设备接入网设备、和核心网设备 技术领域
本发明实施例涉及无线网络通信领域，尤其涉及一种无线通信方法、用户设备、接入网设备、核心网设备和网络系统。
背景技术
现有的LTE系统的服务质量(Quality of Service；简称：QoS)管理是基于承载来实现端到端的QoS保证。在LTE系统中，承载是用户设备(User Equipment；简称：UE)和分组数据网络网关(Packet Data Network Gateway；简称：P-GW)间的一个或者多个业务数据流的逻辑集合。映射到同一个演进分组系统(Evolved Packet System；简称：EPS)承载的业务数据流，将受到同样的分组转发处理(如调度策略、排队管理策略、速率调整策略、RLC配置等)。在LTE系统中，从P-GW到UE可以由几段承载来实现QoS保证，包括：在P-GW和服务网关(Serving Gateway；简称：S-GW)之间的S5/S8承载，S-GW和演进型基站(Evolved Node B；简称eNB)之间的S1承载，以及eNB到UE之间的无线承载。上述S5/S8承载、S1承载和无线承载统称为EPS承载，其中EPS承载的属性由P-GW给出。承载的属性对应一套QoS处理方式，同一个承载内的数据采用相同的数据分组转发方式。在下行方向，P-GW将业务数据流映射到EPS承载，在S5/S8承载、S1承载以及无线承载上，都是以EPS承载的属性来保证业务的QoS需求。现有LTE系统采用基于承载的粒度进行数据传输的QoS控制，多个因特网协议(Internet Protocol；简称：IP)流映射到一个EPS承载。EPS承载是QoS控制的最小单位，即同一EPS承载内的数据流不做QoS区分。UE和P-GW之间的无线承载、S1承载以及S5/S8承载采用1:1的映射方式。
现有LTE系统采用基于EPS承载的粒度进行数据传输的QoS控制，多个IP Flow映射到一个EPS承载，EPS承载是EPS中用于承载级别QoS控制的最小单位，即同一EPS承载内的数据流不做QoS区分。UE和P-GW之间的空口、AN、CN承载采用1:1的映射方式。如果有新的数据流需要进行传输，而该数据流无法映射到已有的数据承载上去，那么就需要新建一个专用的EPS数据承载。
对于上行数据的传输，LTE系统同样采用承载映射的方式，把数据流映射到承载，网络把映射的方式以模板的形式通过信令下发给UE，同时网络会把业务相关的QoS信息也通过信令下发给UE，比如授权的QoS等级等。UE使用网络下发的模板进行数据流映射。如果没有合适的承载，UE通过信令向网络请求建立承载。
在进行上行数据传输，需要在UE和网络(包括核心网和接入网)之间进行多次的信令交互，涉及到的网络功能单元较多，信令开销比较大。同时也会造成较大的时延。
发明内容
本发明实施例提供一种无线通信方法、用户设备、接入网设备和网络系统，旨在降低时延。
第一方面，本发明实施例提供一种无线通信方法，包括如下步骤：用户设备从第一承载上接收下行数据，所述第一承载的反射服务质量QoS属性是支持。当所述用户设备要向接入网设备发送与所述下行数据相对应的上行数据，所述用户设备确认第二 承载，其中所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。所述用户设备使用所述第二承载发送所述上行数据。
本发明实施例中，用户设备从第一承载上接收下行数据，如果第一承载的反射服务质量QoS属性是支持，则可以在传输与该下行数据相对应的上行数据时，直接根据第一承载的QoS信息确定第二承载的QoS信息，可以避免使用信令来获取QoS信息。减少信令开销，降低时延。此外，在进行相对应的上、下行数据的传输时，下行数据传输所采用的的承载的QoS信息是根据上行数据传输所述采用的承载的QoS信息确定的，这可以保证用户的业务体验。
在一个可能的设计中，所述第二承载和所述第一承载相同或者所述第二承载是在所述用户设备接收所述下行数据之后建立的。当所述第二承载和所述第一承载相同，在进行与下行数据相对应的上行数据传输时，可以直接使用第一承载进行上行数据传输，避免重新建立承载的过程。减少信令开销，降低时延。当所述第二承载是在所述用户设备接收所述下行数据之后建立的，则用户设备可以根据上行数据的特性进行第二承载的建立。这也可以适用于上下行需要使用独立承载的场景和第一承载无法进行上行数据传输的场景。
在一个可能的设计中，在所述用户设备从所述第一承载上接收所述下行数据之前，所述方法还包括：所述用户设备接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
用户设备提前获取第一承载的QoS信息，当从第一承载上接收下行数据时就可以直接根据第一承载的QoS信息确定第二承载的QoS信息，无需再通过信令交互获取第二承载的QoS信息，节约了信令交互，降低了时延。此外，如果用户设备需要直接进行上行数据传输时，就可以把数据映射到合适的承载上，减少时延。
在一个可能的设计中，所述下行数据包含第一承载的承载服务质量指示BQI，所述第一承载的BQI包括所述第一承载的QoS信息。用户设备通过BQI即可确认其应该使用的承载。而且，通过数据传输的方式发送承载的QoS指示，可以减少通过信令指示的信令开销。
第二方面，本发明实施例提供一种无线通信方法，包括如下步骤：接入网设备使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；所述接入网设备使用第二承载接收与所述第一下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
在一个可能的设计中，所述第二承载和所述第一承载相同或者所述第二承载是在所述接入网设备接收所述下行数据之后建立的。
在一个可能的设计中，在所述接入网设备使用所述第一承载发送所述第一下行数据之前，所述方法还包括：所述接入网设备接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。接入网设备获取第一承载的QoS信息后，可以方便进行数据的承载映射。
在一个可能的设计中，所述第一下行数据包含第一承载的承载服务质量指示BQI，所述第一承载的BQI包括所述第一承载的QoS信息。
在一个可能的设计中，在所述接入网设备使用所述第一承载发送所述第一下行数 据之前，所述方法还包括：所述接入网设备以流的形式接收来自核心网设备的第二下行数据，所述第二下行数据包括反射QoS指示；所述接入网设备根据所述第二下行数据获取所述第一下行数据，所述第一下行数据不包括反射QoS指示；所述接入网设备将所述第一下行数据映射到所述第一承载。接入网设备映射到第一承载的第一下行数据，无需包括反射QoS指示，可以节省空口的数据传输开销。
在一个可能的设计中，在所述接入网设备使用所述第二承载接收所述第一上行数据之后，所述方法还包括：所述接入网设备将所述第一上行数据解映射到数据流；所述接入网设备根据所述第一上行数据获取第二上行数据，所述第二上行数据包括流优先级指示FPI；所述接入网设备以流的形式发送所述第二上行数据到核心网设备。这种技术方案特别适用于核心网使用流进行传输的场景。
在一个可能的设计中，所述接入网设备是接入网用户面设备。所述接入网设备以流的形式接收所述第一下行数据后、所述接入网设备将所述第一下行数据映射到所述第一承载前，所述方法还包括：所述接入网用户面设备向接入网控制面设备发送承载建立请求；所述接入网用户面设备接收承载建立响应，所述承载建立响应包括第一承载的标识、第一承载的QoS信息和第一承载的反射QoS属性。在进行下行数据传输时建立承载，可以参考第一下行数据的特性进行相应的承载建立，不需使用单独的信令获取QoS信息。
在一个可能的设计中，所述接入网设备使用所述第一承载向所述UE发送与第一下行数据相关的第三下行数据。在传输第一下行数据的时候所建立的承载，可以保留下来供后续相关的第三下行数据的传输使用。避免承载的重复建立。
第三方面，本发明实施例提供一种无线通信方法，包括如下步骤：核心网设备使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；所述核心网设备使用第二承载接收与所述第一下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
在一个可能的设计中，所述第二承载和所述第一承载相同或者所述第二承载是在所述核心网设备接收所述下行数据之后建立的。
在一个可能的设计中，在所述核心网设备使用所述第一承载发送所述第一下行数据之前，所述方法还包括：所述核心网设备接收第一承载的QoS信息，所述所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
在一个可能的设计中，所述第一下行数据包含第一承载的承载服务质量指示BQI，所述第一承载的BQI包括所述第一承载的QoS信息。
第四方面，本发明实施例提供了一种用户设备，该用户设备具有实现上述方法中用户设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，所述用户设备包括发送器、接收器和处理器。所述接收器被配置为从第一承载上接收下行数据，所述第一承载的反射服务质量QoS属性是支持。所述处理器被配置为当要向接入网设备发送与所述下行数据相对应的上行数据，确认第二承载，其中所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。所 述发送器被配置为使用所述第二承载发送所述上行数据。
在一个可能的设计中，所述接收器还被配置为接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
第五方面，本发明实施例提供了一种接入网设备，该接入网设备具有实现上述方法中接入网设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，所述接入网设备包括发送器和接收器。所述发送器被配置为使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；所述接收器被配置为使用第二承载接收与所述下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
在一个可能的设计中，所述接收器还用于接收第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
在一个可能的设计中，所述接收器还被配置为以流的形式接收来自核心网设备的第二下行数据，所述第二下行数据包括反射QoS指示。所述接入网设备还包括处理器，所述处理器被配置为根据所述第二下行数据获取所述第一下行数据，所述第一下行数据不包括反射QoS指示；将所述第一下行数据映射到所述第一承载。
在一个可能的设计中，所述处理器还被配置为将所述第一上行数据解映射到数据流；根据所述第一上行数据获取第二上行数据，所述第二上行数据包括流优先级指示FPI。所述发送器还被配置为以流的形式发送所述第二上行数据到核心网设备。
在一个可能的设计中，所述接入网设备是接入网用户面设备。所述发送器还被配置为向接入网控制面设备发送承载建立请求。所述接收器还被配置为接收承载建立响应。所述承载建立响应包括第一承载的标识、第一承载的QoS信息和第一承载的反射QoS属性。
在一个可能的设计中，所述发送器还被配置为使用所述第一承载向所述UE发送与第一下行数据相关的第三下行数据。
第六方面，本发明实施例提供了一种核心网设备，该核心网设备具有实现上述方法中核心网设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，所述核心网设备包括发送器和接收器。所述发送器被配置为使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；所述接收器被配置为使用第二承载接收与所述下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
在一个可能的设计中，所述接收器还用于接收第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的用户设备和接入网设备；或者，该系统包括上述方面所述的接入网设备和核心网设备；或者，该系统包括上述方面所述的用户设备、接入网设备和核心网设备。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述用户设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述接入网设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述核心网设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明实施例的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是根据本专利申请一个实施例，一种无线通信系统的示意图。
图2是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图3是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图4是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图5是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图6为根据本发明实施例又一个实施例的终端的结构示意图。
图7为根据本发明实施例又一个实施例的网络设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚地描述，显然，所描述的实施例仅仅是本发明实施例一部分实施例，而不是全部的实施例。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。基于本发明实施例中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明实施例保护的范围。
在本申请中，“示例性”一词用来表示“用作例子、例证或说明”。本申请中被描述为“示例性”的任何实施例不一定被解释为比其它实施例更具优势。为了使本领域任何技术人员能够实现和使用本发明实施例，给出了以下描述。在以下描述中，为了解释的目的而列出了细节。应当明白的是，本领域普通技术人员可以认识到，在不使用这些特定细节的情况下也可以实现本发明实施例。在其它实例中，不会对公知的结构和过程进行详细阐述，以避免不必要的细节使本发明实施例的描述变得晦涩。因此，本发明实施例并非旨在限于所示的实施例，而是与符合本申请所公开的原理和特征的最广范围相一致。
本发明实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明实施例的实施例能够以在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本文中术语“连接”可以是直接连接或间接连接。“功能实体”是指实现某个功能的实体，其包含了执行该功能相应的硬件结构和/或软件模块。
本文中术语“承载”是网络为了实现差异化的数据传递，而建立的和QoS相对应的数据传输通道。一个承载可以以数据隧道的方式实现，例如在数据传输的源节点和目的节点之间建立的基于GPRS隧道协议(GPRS Tunneling Protocol；简称：GTP)的一个逻辑数据传输通道等。一个承载上的所有数据流在QoS控制上不做区分，拥有相同的数据包转发处理方式，并按照传输通道所对应的传输协议进行数据传输。
本文中术语反射QoS(Reflective QoS)是指上行数据传输QoS是下行数据传输QoS的反射。其基本思想是根据下行数据传输的QoS信息来确定出上行数据传输的QoS信息。
本文中术语“反射QoS指示”(Reflective QoS Indication，RQI)是用于指示是否使用反射QoS的方式进行数据传输的指示信息。其如果用在下行数据传输时，则可以用来指示相应的上行数据传输是否要采用和下行数据传输一致的QoS控制方式。RQI可以适用于单个数据流或多个数据流的聚合。
本文中术语“承载的反射QoS属性”是指该承载是否支持反射QoS传输。如果某个承载支持反射QoS，则该承载的反射QoS属性是支持，此时网络可以把包含有反射QoS指示的数据映射到该承载。如果某个承载不支持反射QoS传输，则该承载的反射QoS属性是不支持。
本文中术语“承载的QoS等级”是指接入网设备在处理承载对应的数据时，针对每个承载的处理优先级。在一个例子中，承载的QoS等级可以业务质量的索引(QoS Classification Identifer，QCI)的形式来体现。
本文中术语“流优先级指示(Flow Priority Indicator，简称FPI)”是指核心网或接入网设备在处理流对应的数据时，针对每个流的处理优先级。例如，FPI可以对应到拥塞时网络对流的调度优先级。FPI可以是类似一个QCI的标识。
本文中术语“承载服务质量指示”(Bearer QoS Indicator，简称BQI)是用来指示承载对应的QoS信息。在处理承载对应的数据时，BQI指示了每个承载上的数据的处理优先级。BQI还可以用来指示该承载是否支持反射QoS。BQI还可以用来向UE指示如何做数据到承载的映射。例如，BQI中可以包含有数据到承载的映射指示，UE可以根据BQI的指示来确定承载。
本文中术语“数据流”是指UE或数据网络生成的和某个业务相关的应用数据，比如IP流。为了把数据传递到对端，需要经网络进行传输。网络将高层的数据转化成适合在网络传输的形式。基于流的传输方式是指，对于同一个流内的数据包，网络使用相同的数据包转发方式(packet forwarding treatment)，用相同的QoS规则处理。基于流的传输方式可以包括以流的形式发送或以流的形式传输。区分于基于承载的QoS控制方式，不同的数据流可能映射到同一个承载，同一个承载内的数据流不做QoS区分。数据流和承载的映射方式可以是1:1，也可以是N:1。映射方式还有可能和数据流 的QoS属性相关，比如，对于保证比特速率(guaranteed bit rate，简称GBR)的数据流使用1:1的映射方式，对于非保证比特速率(non-guaranteed bit rate，简称non-GBR)的数据流使用N:1的映射方式。
以数据流的方式进行传输可以做到更精细的QoS控制和区分粒度。一个承载可以是一个或多个数据流的映射，以承载的方式进行传输可以减少信令开销。映射到一个承载上的数据流数量越多，网络需要建立的承载数量越少，相应的信令开销也越小。
本文中术语“QoS规则”是基于运营商策略根据应用需求和QoS参数制定的一套信息集合，用来检测业务数据流或数据并定义其相关的QoS参数，以及确定数据流或数据的传输方式。数据流的传输方式可以包括以流的方式或者以承载的方式进行传输。以流的方式传输可以是将数据流的数据包按照IP传输协议进行传输。以承载的方式传输可以是把一个或多个数据流映射到一个承载上进行传输。
QoS规则可以包括数据流的QoS需求信息和/或数据流的传输方式，比如，以承载方式进行传输或以数据流方式进行传输。QoS需求信息可以包括数据率，传输时延等。QoS规则还可以包括承载和数据流的映射关系。
本文中术语“映射”是指把一个或多个具有相同或相似QoS的数据流映射到一个承载，每个承载对应一套QoS参数。QoS参数可以包含业务的QoS等级、最大比特速率(Maximum Bit Rate；简称：MBR)、分配保持优先级(Allocation and Retention Priority；简称：ARP)等，用于标识网络对该承载上的数据的处理方式。同一个承载上的数据采用相同的数据转发处理方式。核心网用户面(Core Network Control Plane，简称AN CP)功能实体和UE用户面功能实体可以将多个具有不同QoS的数据流映射到一个或多个承载。CN UP功能实体、AN CP功能实体和UE用户面功能实体可执行流解映射操作。
本文中术语“解映射”是“映射”的逆过程，即把一个承载上的数据进行解映射还原到不同的数据流。值得注意的是，映射以及解映射过程都是可选的操作，由各用户面功能实体根据获取的QoS规则来确定是否进行相应操作。
本文中术语“预授权QoS”指：网络预先授权UE某些特定业务的数据传输对应到指定级别的QoS。其可以作为用户签约内容的一部分，当UE发起该特定业务时，不用再进行业务的QoS授权。比如，对于某些用户，网络可以预先授权相应的UE在发起健康监测业务时，直接对应到较高的QoS级别，这样，UE在发起相应业务时，网络侧可以直接为其建立专用承载，而不需重新进行业务授权过程。
本文中术语“预授权QoS承载”是指，某些对于具有预授权QoS属性的数据，网络会在会话建立完成之后为这类数据，直接建立相应的承载，即使这时还没有这类数据的发送。从而减少等到数据到达后再建立承载的时延。
下面以具体地实施例对本发明实施例的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图1示出了本发明实施例提供的一种无线通信系统示意图。所述无线通信系统包括UE、接入网(Access Network；简称：AN)设备以及核心网(Core Network；简称：CN)设备。UE与AN设备通过空中接口进行连接。AN设备与CN设备可以有线或无线连接。UE通过AN设备以及CN设备实现数据的通信服务。
本申请实施例中的UE也可以指终端设备、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，简称“SIP”)电话、无线本地环路(Wireless Local Loop，简称“WLL”)站、个人数字处理(Personal Digital Assistant，简称“PDA”)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，简称“PLMN”)中的终端设备等。
本申请实施例中的AN设备可以是用于与终端设备通信的设备，该AN设备可以是GSM或CDMA中的基站(Base Transceiver Station，简称“”BTS)，也可以是WCDMA系统中的基站(NodeB，简称“NB”)，还可以是LTE系统中的演进型基站(Evolutional NodeB，简称“eNB或eNodeB”)，还可以是云无线接入网络(Cloud Radio Access Network，简称“CRAN”)场景下的无线控制器，或者该AN设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的AN设备，也可以是未来演进的网络中的AN设备等。AN设备还可以是下一代基站(Next-generation Node B；简称：gNB)、收发节点(Transmit and Receive Point；简称：TRP)、中心单元设备(Central Unit；简称：CU)、或分布式单元设备(Distributed Unit；简称：DU)等。
在图1所示实施例中，AN设备包括接入网控制面(Access Network Control Plane，简称AN CP)功能实体和接入网用户面功能实体(Access Network User Plane，简称AN UP)。AN CP功能实体和AN UP功能实体连接。AN CP功能实体具有QoS控制功能，可以控制AN UP功能实体的QoS处理。可选地，AN CP功能实体可以把QoS规则发送给AN UP功能实体。AN UP功能实体根据收到的QoS规则进行数据传输。
CN设备可以是网关、路由器、数据中心、服务器、网管设备等。在图1所示的实施例中，CN设备包括核心网控制面(Core Network Control Plane，简称CN CP)功能实体和核心网用户面(Core Network User Plane，简称CN UP)功能实体。
CN CP功能实体和CN UP功能实体连接。CN CP功能实体具有QoS控制功能，可以控制CN UP功能实体的QoS处理。CN CP功能实体可以把QoS规则发送给CN UP功能实体。CN UP功能实体根据收到的QoS规则进行数据传输。
可选地，CN设备还可以包括策略功能实体。策略功能实体用于根据用户的签约信息和运营商的策略制定相应的QoS控制策略，对接收到的QoS授权请求进行业务QoS授权等。策略功能实体可以与AN CP功能实体、CN CP功能实体之间分别连接。策略功能实体用于将QoS授权信息发送给AN CP功能实体、CN CP功能实体。策略功能实体还可以与AN UP功能实体、CN UP功能实体之间分别连接，用于将QoS授权信息发送给AN UP功能实体、CN UP功能实体。
在图1所示实施例中，AN设备和CN设备都存在逻辑上独立的QoS控制功能，分别通过AN CP功能实体和CN CP功能实体实现。AN CP功能实体和CN CP功能实体的QoS控制功能类似，但二者控制的范围不同。CN CP功能实体主要控制CN UP功能实体的QoS处理，AN CP功能实体主要控制AN UP功能实体的QoS处理。核心网和接入网的资源各不相同，核心网和接入网应可以根据各自的资源使用情况采用不同的QoS控制方法来实现各自 灵活的QoS管理功能。
在本实施例中，AN设备具有QoS管理功能，可以管理和控制AN用户面的数据传输，提高了无线通信网络中业务QoS管理的灵活度，并且提供了CN和AN各自QoS框架独立演进的可能性。
上述无线通信系统还可以与应用功能(Application Function，简称AF)实体和数据网络(Data Network，简称DN)通信。AF实体可以提供特定QoS需求的数据流业务，其类似于应用服务器。可以是网络运营商部署也可以是第三方部署。数据网络，可以提供某种类型数据业务，一般是外部网络，类似于分组数据网络(Packet Data Network，简称PDN)。数据网络的类型包括但不限于：因特网(英文：Internet)、IP多媒体子系统(英文：IP Multimedia Subsystem，简称：IMS)
图2是根据本专利申请一个实施例，一种通信方法的交互示意图。如图2所示，该方法包括如下步骤：
201、用户成功接入网络后，UE通过无线通信系统和数据网络之间建立会话(session)。在该过程中，UE获得用于和数据网络进行通信的标识，比如IP地址。该会话可以是协议数据单元(Protocol Data Unit，PDU)会话。
202、AN CP功能实体发起在UE和AN UP功能实体之间建立承载。
对于某些类型的承载，可以在会话建立完成之后就开始建立，而不必等数据到达了再触发承载建立。步骤202中的承载可以是默认承载或者是预授权QoS承载。
在该承载的建立过程中，AN CP功能实体生成一个承载标识，该标识可以用来识别该承载。AN CP功能实体为该承载配置QoS信息，比如QoS等级。AN CP功能实体还可以根据QoS信息为承载分配相应的网络资源。网络资源可以是带宽、存储资源等。
AN CP功能实体还可以对承载进行分类。在一个实施例中，可以将承载分成两类：反射QoS使能(Reflective QoS Enabled，RQ Enabled)的承载和非反射QoS使能(Reflective QoS，Non-RQ Enabled)的承载。RQ Enabled的承载可以用来支持反射QoS，其反射QoS属性是支持。Non-RQ Enabled的承载不可以用来支持反射QoS，其反射QoS属性是不支持。
关于分类的方法可以有多种，下面以举例的方式进行说明。一种分类方法可以是AN CP功能实体对已经建立完成的承载进行分类。比如，假定已经建立有10个承载，则可以按照一定的数量比例，对承载进行划分，分成RQ Enabled的承载和Non-RQ Enabled的承载。还有一种分类方法可以是静态分类的方法。即固定将某些编号的承载定义为RQ enabled承载或Non-RQ Enabled承载。比如，假如最多支持为UE建立10个承载，那么可以为这10个承载进行编号，简单起见，在一个例子中，编号可以定义为1、2、3…10。静态分类的方法可以固定地把承载1到承载5定义为或预留为RQ Enabled，承载6到承载10定义为或预留为Non-RQ Enabled。后续承载建立后，根据承载的反射QoS属性，为承载选取适当的编号。
对于在RQ Enabled的承载上进行传输的数据，无需在每个下行数据中包含RQI，而UE直接根据数据传输所在的承载类型，即可确认在对应的上行数据中采用反射QoS。这可以节省空口的数据传输开销，提高网络的有效数据传输效率。
203、AN CP功能实体向AN UP功能实体发送承载的信息。AN UP功能实体接收该 承载的信息。承载的信息包括：承载标识和承载的QoS信息。承载的QoS信息包括承载所支持的QoS等级和RQ的属性。该承载标识可以是步骤202中所建立的承载的标志。承载所支持的QoS等级可以QCI的形式体现。RQ属性可以是RQ Enabled或Non-RQ Enabled。
204、AN CP功能实体向UE发送承载的信息。UE接收该承载的信息。承载的信息可以参考步骤203中的描述。
205、数据网络将下行数据以数据包的形式发送给CN UP功能实体。CN UP功能实体接收该下行数据。
206、CN UP功能实体对下行数据进行处理，把下行数据匹配到数据流。CN UP功能实体以流的形式发送下行数据给AN UP功能实体。AN UP功能实体接收该下行数据。CN UP功能实体会在下行数据的包头中增加数据流的QoS信息。包括：FPI和RQI。可选地，CN UP功能实体还可以在下行数据的包头中增加数据流ID。
在步骤206中，匹配的方式可以采用模板过滤的方式。例如，定义一个参数组，并为该组中每个参数设定一个值或取值范围，当数据包的相关参数与预先设定的值相同，或落在预先设定的取值范围之内时，可以将该数据包映射到对应数据流。作为一个例子，参数组可以是IP五元组。IP五元组包括目的IP地址、源IP地址、目的端口号、源端口号和协议类型。
207、AN UP功能实体对接收到的下行数据进行处理，把处理后的下行数据映射到第一承载。第一承载可以是步骤202中所建立的承载中的一个。
AN UP功能实体的处理过程可以是：根据步骤206中所接收到的下行数据获取步骤208中所需要发送的下行数据。为了更清楚地区分步骤206-208中的下行数据，可以将在步骤208中所提到的下行数据称为第一下行数据，而在步骤206中所提到的下行数据称为第二下行数据。AN UP功能实体可以去掉第一下行数据包头中的RQI。即，第二下行数据包括RQI，而第一下行数据不包括RQI。在AN使用承载进行传输而CN使用流进行传输的场景下，第二下行数据还可以包括FPI，而第一下行数据不包括FPI。即第一下行数据的包头中没有FPI和RQI。或者，AN UP功能实体还可以生成新的数据包头。新的数据包头中可以包含数据流ID。新的数据包头中也可以包含BQI。生成新的数据包包头的方式可以是用新的数据包头代替每一个旧的数据包头。
当AN UP功能实体接收到了超过一个的数据流，如果某些数据流之间具有相同或类似的QoS需求，AN UP功能实体可以把这些数据流映射到相同的的承载。如果这些数据流都包含有RQI，该承载可以是RQ Enabled类型的。
可选地，AN UP功能实体还可以记录每个数据流的FPI指示。方便在上行数据传输时，在AN UP功能实体将上行数据以流的形式发送给CN UP功能实体时，在数据的包头增加对应的FPI。
208、AN UP功能实体通过第一承载把处理后的下行数据发送给UE。UE通过第一承载接收该下行数据。该处理后的下行数据中没有FPI和RQI，可以节约空口资源。可选地，在本步骤中的下行数据可以包括BQI。通过BQI可以进一步向UE指示第一承载的QoS属性。BQI还可以用来向UE指示如何做上下数据到承载的映射。
209、在UE需要进行上行数据的传输时，UE对该上行数据进行检查，如果该上行 数据与在步骤208中收到的下行数据是相对应的，则可以参考该步骤208中所使用的第一承载，确认第二承载。其中，第二承载的QoS信息是根据第一承载的QoS信息确定的。
在一个实施例中，上行数据与下行数据相对应是指属于上行数据与下行数据属于同一个业务流。一个会话可能包含多个业务流，每个业务流对应一种业务类型以及一种QoS控制方式。在另一个实施例中，上行数据与下行数据相对应是指属于上行数据与下行数据属于同一个会话流。
第二承载的QoS信息是根据第一承载的QoS信息确定的，例如是：第二承载的QoS等级是根据第一承载的QoS等级确定的。当然，还可以根据第一承载的其他QoS信息确定第二承载的相应的其他QoS信息。
在一个实施例中，第二承载的QoS等级与第一承载的QoS等级相同，即两者是一一对应的。从第一承载的等级直接就可以确定出第二承载的等级。在另一个实施例中，第二承载的QoS等级与第一承载的QoS等级是相互对应的。例如，上行承载和下行承载对应的信道有可能是不对称的，一般的，下行信道的带宽大于上行信道。在定义QoS等级时，上下行有可能使用不同的定义，比如下行承载的最大比特速率可以大于上下承载的最大比特速率，因此下行承载的QoS等级可以多于上行承载的QoS等级。那么在根据下行承载的QoS等级来确定上行承载的QoS等级时，就不采用一一对应的方式，而是两者只要有一个对应关系即可。参考这个对应关系，从第一承载的等级就可以确定出第二承载的等级。
值得注意的是，第一承载与第二承载可以相同，也可以不同。如果第一承载是双向承载，则第二承载与第一承载可以是相同的。
第二承载还可以是一个新的承载。例如，在第一承载是一个单向承载、或者上、下行数据需要在不同的承载上传输。UE可以向AN CP功能实体发送承载建立请求，触发AN CP功能实体建立一个新的承载，该新的承载和第一承载具有相同或对应的QoS特性。该新的承载是在UE接收下行数据之后建立的。
如果在步骤208中所接收的数据包中包括BQI，则在步骤209中，UE还可以根据该BQI确认第二承载。BQI还可以包含数据流到承载的映射方式，比如，映射模板，UE可以根据BQI的指示把上行数据流映射到已有的承载上去。
在步骤209中，UE可以把上行数据匹配到数据流，匹配的方式可以参考步骤206的描述。UE再把数据流映射到第二承载。值得注意的是，UE也可以直接将上行数据映射到第二承载。
210、UE通过第二承载向AN UP功能实体发送上行数据。AN UP功能实体接收该上行数据。
211、AN UP功能实体对上行数据进行处理，把处理后的上行数据解映射到数据流。
AN UP功能实体的处理过程可以是：根据步骤210中所接收到的上行数据获取步骤212中所需要发送的上行数据。为了更清楚地区分步骤210-212中的上行数据，可以将在步骤210中所提到的上行数据称为第一上行数据，而在步骤212中所提到的上行数据称为第二上行数据。在AN使用承载进行传输而CN使用流进行传输的场景下，第一上行数据的包头不包括FPI，AN UP功能实体可以对其处理，在第二上行数据的包 头增加其对应的FPI，即第二上行数据包括FPI。
212、AN UP功能实体以流的方式把处理后的上行数据发送给CN UP功能实体。CN UP功能实体接收该上行数据。
213、CN UP功能实体把接收到的上行数据发送给数据网络。
值得注意的是，步骤204是可选的，在某些情况下，可以不进行步骤204。例如，如果步骤208中的下行数据包括BQI，而该BQI又可以反映承载的QoS信息的话，步骤204即可省去。
此外，步骤203和204的先后顺序不做限定。可以先进行步骤203再进行步骤204或者先进行步骤204再进行步骤203或者同时进行步骤203和步骤204。
图3是根据本专利申请另一个实施例，一种通信方法的交互示意图。如图3所示，该方法包括如下步骤：
301、与201基本相同，可以参照201，不再赘述。
302、数据网络将第一下行数据发送给CN UP功能实体。CN UP功能实体接收该第一下行数据。
303、CN UP功能实体对第一下行数据进行处理，把第一下行数据匹配到数据流。CN UP功能实体以流的形式发送第一下行数据给AN UP功能实体。AN UP功能实体接收该下行数据。本步骤也可以参照步骤206的描述，不再赘述。
304、AN UP功能实体向AN CP功能实体发送承载建立请求。AN CP功能实体接收承载建立请求。承载建立请求中包含请求的QoS信息，请求的QoS信息与第一下行数据中包含的QoS信息相同。
305、AN CP功能实体发起在UE和AN UP功能实体之间建立承载。AN CP功能实体根据承载建立请求中包含的QoS信息，发起在UE和AN UP之间建立承载。在本实施例中，为方便描述，步骤305中所建立的承载可以称为第一承载。
在该承载的建立过程中，AN CP功能实体生成一个承载标识，该标识可以用来识别该承载。AN CP功能实体为该承载配置QoS参数，比如QoS等级，AN CP功能实体还会根据预授权QoS信息为承载分配相应的网络资源。网络资源可以是带宽、存储资源等。
如果第一下行数据的QoS信息中包含有RQI指示，则该承载属性可以被标识为RQI Enabled。
306、AN CP功能实体向AN UP功能实体发送承载建立响应，AN UP功能实体接收承载建立响应。承载建立响应中包含承载的信息。承载的信息包括：承载标识和承载的QoS信息。承载的QoS信息包括承载所支持的QoS等级。承载的QoS信息还可以包括RQ的属性。在本实施例中，步骤305中所建立的承载的RQ的属性是RQ Enabled。
307、AN CP功能实体向UE发送承载的信息，UE接收该承载的信息。承载的信息包括：承载标识和承载的QoS信息。承载的QoS信息包括承载所支持的QoS等级和RQ的属性。在本实施例中，RQ的属性是RQ Enabled。值得注意的是，步骤306和307可以同时进行。
308、AN UP功能实体对接收到的第一下行数据进行处理，把处理后的第一下行数据映射到第一承载。第一承载是步骤305中所建立的承载。
309、AN UP功能实体通过第一承载把处理后的第一下行数据发送给UE。UE接收该下行数据。
310、在UE需要进行上行数据的传输时，UE对该上行数据进行检查，如果该上行数据与在步骤309中收到的下行数据是相对应的，则可以参考步骤309中所使用的第一承载，确认第二承载。第二承载与第一承载可以是相同的，或者是新建立的承载。具体可以参考步骤209中对其的介绍。
311、UE通过第二承载向AN UP功能实体发送上行数据。AN UP功能实体接收该上行数据。
312、AN UP功能实体对上行数据进行处理，把处理后的上行数据解映射到数据流。
AN UP功能实体的处理过程可以是：根据步骤311中所接收到的上行数据获取步骤313中所需要发送的上行数据。为了更清楚地区分步骤311-313中的上行数据，可以将在步骤311中所提到的上行数据称为第一上行数据，而在步骤313中所提到的上行数据称为第二上行数据。在AN使用承载进行传输而CN使用流进行传输的场景下，第一上行数据的包头不包括FPI，AN UP功能实体可以对其处理，在第一上行数据的包头增加其对应的FPI，即第二上行数据包括FPI。
313、AN UP功能实体以流的方式把处理后的上行数据发送给CN UP功能实体。CN UP功能实体接收该上行数据。
314、CN UP功能实体把接收到的上行数据发送给数据网络。
在图3所示的实施例中，RQ Enabled的承载的定义是动态的。AN UP功能实体收到第一个具有RQI指示的数据流后所建立映射到的承载，被定义为RQ Enabled承载。后续，如果AN UP功能实体收到新的数据流，并且该新的数据流与第一个具有RQI指示的数据流是相关的，例如：具有相同或类似的QoS需求，并且该新的数据流也包含RQI指示，则AN UP功能实体也可以把该新的数据流映射到该RQ Enabled承载。在本发明实施例中，在传输第一下行数据的时候所建立的承载，可以保留下来供后续传输使用。可选地，本发明实施例还可以包括如下步骤：
315、数据网络将下行数据发送给CN UP功能实体。CN UP功能实体接收该下行数据。为了与步骤302中的下行数据进行区分，步骤315中的下行数据也可以称为第三下行数据。
316、CN UP功能实体对第三下行数据进行处理，把下行数据匹配到数据流。关于步骤316的详细介绍，可以参考步骤206。
317、AN UP功能实体对接收到的第三下行数据进行处理，把处理后的下行数据映射到第一承载。AN UP功能实体可以去掉下行数据包头中的RQI，经AN UP功能实体处理后的下行数据不包括RQI。在AN使用承载进行传输而CN使用流进行传输的场景下，步骤315中的下行数据的包头包括FPI，而经AN UP功能实体处理后的下行数据的包头可以不包括FPI。即处理后的下行数据中没有FPI和RQI，在传输该下行数据时，可以节约空口资源。在本实施例中，如果第三下行数据与第一下行数据可以是相关的，则也可以使用第一承载进行第三下行数据的传输。例如，如果第三下行数据与第一下行数据具有相同或类似的QoS需求，并且该第三下行数据也包含RQI指示，则AN UP功能实体也可以把第三下行数据映射到第一承载。
318、AN UP功能实体通过第一承载把处理后的下行数据发送给UE。UE通过第一承载接收该下行数据。关于步骤318的详细介绍，可以参考步骤208。
在本实施例中，如果UE需要进行上行数据传输，可以在步骤318之后再进行步骤310-314。
本发明实施例可以适用于AN使用承载，CN使用数据流的场景。上面使用图2和图3对这种场景进行了说明。值得注意的是，本发明实施例也可以适用于AN、CN都使用承载的场景。下面对这种场景进行说明。
图4是根据本专利申请另一个实施例，一种通信方法的交互示意图。如图4所示，该方法包括如下步骤：
401、与步骤201基本相同，不再赘述。
402、CN CP功能实体发起在UE和AN UP功能实体之间以及AN UP功能实体和AN CP功能实体之间建立承载。
对于某些类型的承载，可以在会话建立完成之后就开始建立，而不必等数据到达了再触发承载建立。步骤202中的承载可以是默认承载或者是预授权QoS承载。
在该承载的建立过程中，CN CP功能实体生成一个承载标识，该标识可以用来识别该承载。CN CP功能实体为该承载配置QoS信息，比如QoS等级。CN CP功能实体还可以根据QoS信息为承载分配相应的网络资源。网络资源可以是带宽、存储资源等。
CN CP功能实体还可以对承载进行分类。在一个实施例中，可以将承载分成两类：反射QoS使能(Reflective QoS Enabled，RQ Enabled)的承载和非反射QoS使能(Reflective QoS，Non-RQ Enabled)的承载。RQ Enabled的承载可以用来支持反射QoS，其反射QoS属性是支持。Non-RQ Enabled的承载不可以用来支持反射QoS，其反射QoS属性是不支持。
关于分类的方法可以有多种，下面以举例的方式进行说明。一种分类方法可以是CN CP功能实体对已经建立完成的承载进行分类。还有一种分类方法可以是静态分类的方法。具体也可以参考前面的介绍。
403、CN CP功能实体向CN UP功能实体发送承载的信息。CN UP功能实体接收该承载的信息。承载的信息包括：承载标识和承载的QoS信息。承载的QoS信息包括承载所支持的QoS等级和RQ的属性。该承载标识可以是步骤402中所建立的承载的标志。承载所支持的QoS等级可以QCI的形式体现。RQ属性可以是RQ Enabled或Non-RQ Enabled。
404、CN CP功能实体向UE发送承载的信息。UE接收该承载的信息。在一个例子中，CN CP功能实体可以通过AN CP功能实体向UE发送承载的信息。承载的信息可以参考步骤403中的描述。
405、数据网络将下行数据以数据包的形式发送给CN UP功能实体。CN UP功能实体接收该下行数据。
406、CN UP功能实体把下行数据映射到第一承载。
该第一承载可以是RQ Enabled类型的。可选地，CN UP功能实体在下行数据的包头中也可以包含BQI。
可选地，在步骤406中，CN UP可以确定是否对该下行数据采用反射QoS的传输 方式。确定的方式可以是由CN UP功能实体向CN CP功能实体发送请求，CN CP功能实体确定之后再把结果发给CN UP功能实体。确定的依据可以根据业务的类型，或业务的属性。比如，对于某些业务需求可能会发生频繁变化的业务，可以采用Reflective QoS的传输方式。
407、CN UP功能实体通过第一承载把下行数据发送给AN UP功能实体。AN UP功能实体再把该下行数据发送给UE。UE通过第一承载接收该下行数据。可选地，在本步骤中的下行数据可以包括BQI。通过BQI可以进一步向UE指示第一承载的QoS属性。BQI还可以用来向UE指示如何做上下数据到承载的映射。
408、在UE需要进行上行数据的传输时，UE对该上行数据进行检查，如果该上行数据与在步骤407中收到的下行数据是相对应的，则可以参考第一承载，确认第二承载。
值得注意的是，第一承载与第二承载可以相同，也可以不同。如果第一承载是双向承载，则第二承载与第一承载可以是相同的。
第二承载还可以是一个新的承载。例如，在第一承载是一个单向承载、或者上、下行数据需要在不同的承载上传输。UE可以通过AN CP功能实体向CN CP功能实体发送承载建立请求，触发CN CP功能实体建立一个新的承载，该新的承载和第一承载具有相同的QoS特性。该新的承载是在UE接收下行数据之后建立的。
如果在步骤407中所接收的数据包中包括BQI，则在步骤408中，UE还可以根据该BQI确认第二承载。
409、UE通过第二承载向AN UP功能实体发送上行数据。AN UP功能实体再通过第二承载向CN UP功能实体发送上行数据。相应地，CN UP功能实体接收该上行数据。
410、CN UP功能实体把接收到的上行数据发送给数据网络。
图5是根据本专利申请另一个实施例，一种通信方法的交互示意图。如图3所示，该方法包括如下步骤：
501、与201基本相同，可以参照201，不再赘述。
502、数据网络将第一下行数据发送给CN UP功能实体。CN UP功能实体接收该第一下行数据。
503、CN UP功能实体向CN CP功能实体发送承载建立请求。CN CP功能实体接收承载建立请求。承载建立请求中包含请求的QoS信息，所请求的QoS信息与第一下行数据中包含的QoS信息相同。
504、CN CP功能实体发起在UE和AN UP功能实体之间以及AN UP功能实体和AN CP功能实体之间建立承载。关于本步骤可以参考步骤402的介绍。
505、与步骤403基本相同，不再赘述。
506、与步骤404基本相同，不再赘述。
507、把第一下行数据映射到第一承载。关于本步骤可以参考步骤406的介绍。
508、与步骤407基本相同，不再赘述。
509、在UE需要进行上行数据的传输时，UE对该上行数据进行检查，如果该上行数据与在步骤407中收到的下行数据是相对应的，则可以参考第一承载，确认第二承载。
510、与步骤409基本相同，不再赘述。
511、与步骤410基本相同，不再赘述。
512、与步骤315基本相同，不再赘述。
513、如果第三下行数据与第一下行数据是相关的，例如具有相同或类似的QoS需求，并且CN UP功能实体确定对第三下行数据也采用反射QoS传输，则CN UP功能实体也可以把第三下行数据映射到第一承载。
514、与步骤409基本相同，只是在第一承载上进行传输的数据是第三下行数据。
在本实施例中，如果UE需要进行上行数据传输，可以在步骤514之后再进行步骤509-511。
值得注意的是，本发明实施例的方法可以应用在图1所示的网络架构中。当然，本发明实施例的方法也可以应用在其他类型的网络架构中。只要该网络架构包括核心网设备、接入网设备即可。
在图2、3所示实施例中，如果需要确定是否采用反射QoS的传输方式，可以由AN UP功能实体向AN CP功能实体发送请求，AN CP功能实体确定之后再把结果发给AN UP功能实体。确定的依据可以参考图4所示实施例中的说明。
在本发明实施例中，UE将上行数据映射到承载上，可以采用两种方法。第一种方法是UE直接将上行数据映射到承载上。另一种方法是UE先将上行数据映射成数据流再讲数据流映射到承载上。
在本发明实施例中，在核心网设备和接入网设备之间进行传输的下行数据如果包含RQI，可以使用对反射QoS进行支持的承载进行空口传输。而相应的上行数据传输的QoS等级可以根据下行数据传输所使用的承载的QoS等级确认。而不需通过信令交互的方式，确认上行数据传输的等级，减少信令开销。此外，在空口传输时，下行数据的包头可以不携带RQI，从而可以减少数据包包头的负载，提高空口的有效数据传输效率。
图6为根据本发明又一个实施例的终端的结构示意图。如图6所示，终端600可以包括：接收器601、处理器602和发送器603。接收器601和发送器603分别和处理器602相连接。
其中，接收器601可以执行上述方法实施例中的UE的接收步骤，发送器603可以执行该实施例中的UE的发送步骤，处理器602可以执行该实施例中的UE的处理步骤，例如检查上行数据并确认第二承载等步骤。
图7为根据本发明又一个实施例的网络设备的结构示意图。如图7所示，网络设备700可以包括：接收器701、处理器702和发送器703。接收器701和发送器703分别和处理器702相连接。
该网络设备700可以包括接入网设备，例如可以包括接入网用户面设备(对应上文中的接入网用户面功能实体)。当网络设备700包括接入网用户面设备，接收器701可以执行上述方法实施例中的接入网用户面功能实体的接收步骤，发送器703可以执行该实施例中的接入网用户面功能实体的发送步骤，处理器702可以执行该实施例中的接入网用户面功能实体的处理步骤，例如对下行数据进行处理并映射到第一承载、对上行数据进行处理并解映射到数据流等步骤。
该网络设备700还可以包括核心网设备，例如可以包括核心网用户面设备(对应上文中的核心网用户面功能实体)。当网络设备700包括核心网用户面设备，接收器701可以执行上述方法实施例中的核心网用户面功能实体的接收步骤，发送器703可以执行该实施例中的核心网用户面功能实体的发送步骤，处理器702可以执行该实施例中的核心网用户面功能实体的处理步骤，例如对下行数据进映射到第一承载等步骤。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本专利申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本专利申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包含若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本专利申请各个实施例方法的全部或部分步骤。而前述的存储介质包含：U盘、移动硬盘、只读存储器(ROM，Read-OnlyMemory)、随机存取存储器(RAM，RandomAcces切片管理器emory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，仅为本专利申请的具体实施方式，但本专利申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本专利申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本专利申请的保护范围之内。因此，本专利申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种无线通信方法，其特征在于包括如下步骤：
    用户设备从第一承载上接收下行数据，所述第一承载的反射服务质量QoS属性是支持；当所述用户设备要向接入网设备发送与所述下行数据相对应的上行数据，所述用户设备确认第二承载，其中所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的；和
    所述用户设备使用所述第二承载发送所述上行数据。
  2. 如权1所述的无线通信方法，其特征在于：
    所述第二承载和所述第一承载相同或者所述第二承载是在所述用户设备接收所述下行数据之后建立的。
  3. 如权1或2所述的无线通信方法，其特征在于：
    在所述用户设备从所述第一承载上接收所述下行数据之前，所述方法还包括：
    所述用户设备接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
  4. 一种无线通信方法，其特征在于包括如下步骤：
    接入网设备使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；和
    所述接入网设备使用第二承载接收与所述第一下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
  5. 如权4所述的无线通信方法，其特征在于：
    在所述接入网设备使用所述第一承载发送所述第一下行数据之前，所述方法还包括：所述接入网设备接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
  6. 如权4或5所述的无线通信方法，其特征在于：
    在所述接入网设备使用所述第一承载发送所述第一下行数据之前，所述方法还包括：所述接入网设备以流的形式接收来自核心网设备的第二下行数据，所述第二下行数据包括反射QoS指示；
    所述接入网设备根据所述第二下行数据获取所述第一下行数据，所述第一下行数据不包括反射QoS指示；和
    所述接入网设备将所述第一下行数据映射到所述第一承载。
  7. 如权4-6任一所述的无线通信方法，其特征在于：
    在所述接入网设备使用所述第二承载接收所述第一上行数据之后，所述方法还包括：
    所述接入网设备将所述第一上行数据解映射到数据流；和
    所述接入网设备根据所述第一上行数据获取第二上行数据，所述第二上行数据包括流优先级指示；
    所述接入网设备以流的形式发送所述第二上行数据到核心网设备。
  8. 如权7所述的无线通信方法，其特征在于：
    所述接入网设备是接入网用户面设备；
    所述接入网设备以流的形式接收所述第一下行数据后、所述接入网设备将所述第一下 行数据映射到所述第一承载前，所述方法还包括：
    所述接入网用户面设备向接入网控制面设备发送承载建立请求；和
    所述接入网用户面设备接收承载建立响应，所述承载建立响应包括第一承载的标识、所述第一承载的QoS信息和第一承载的反射QoS属性。
  9. 一种无线通信方法，其特征在于包括如下步骤：
    核心网设备使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；和
    所述核心网设备使用第二承载接收与所述第一下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
  10. 如权9所述的无线通信方法，其特征在于：
    在所述核心网设备使用所述第一承载发送所述第一下行数据之前，所述方法还包括：所述核心网设备接收第一承载的QoS信息，所述所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
  11. 一种用户设备，其特征在于包括：
    接收器，被配置为从第一承载上接收下行数据，所述第一承载的反射服务质量QoS属性是支持；
    处理器，被配置为当要向接入网设备发送与所述下行数据相对应的上行数据，确认第二承载，其中所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的；和发送器，被配置为使用所述第二承载发送所述上行数据。
  12. 如权11所述的用户设备，其特征在于：
    所述第二承载和所述第一承载相同或者所述第二承载是在接收所述下行数据之后建立的。
  13. 如权11或12所述的用户设备，其特征在于：
    所述接收器还被配置为接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
  14. 一种接入网设备，其特征在于包括：
    发送器，被配置为使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；和
    接收器，被配置为使用第二承载接收与所述第一下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
  15. 如权14所述的用户设备，其特征在于：
    所述接收器还被配置为接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
  16. 如权14或15所述的接入网设备，其特征在于：
    所述接收器还被配置以流的形式接收来自核心网设备的第二下行数据，所述第二下行数据包括反射QoS指示；
    所述接入网设备还包括处理器，所述处理器还被配置为根据所述第二下行数据获取所述第一下行数据，将所述第一下行数据映射到所述第一承载；所述第一下行数据不包括反射QoS指示。
  17. 如权16所述的接入网设备，其特征在于：
    所述处理器还被配置为将所述第一上行数据解映射到数据流，和根据所述第一上行数据获取第二上行数据；所述第二上行数据包括流优先级指示；
    所述发送器还被配置为以流的形式发送所述第二上行数据到核心网设备。
  18. 如权14-17任一所述的接入网设备，其特征在于：
    所述接入网设备是接入网用户面设备；
    所述发送器还被配置为向接入网控制面设备发送承载建立请求；和
    所述接收器还被配置为接收承载建立响应，所述承载建立响应包括第一承载的标识、第一承载的QoS信息和第一承载的反射QoS属性。
  19. 一种核心网设备，其特征在于包括：
    发送器，被配置为使用第一承载发送第一下行数据，所述第一承载的反射服务质量QoS属性是支持；和
    接收器，被配置为使用第二承载接收与所述下行数据相对应的第一上行数据，所述第二承载的QoS信息是根据所述第一承载的QoS信息确定的。
  20. 如权19所述的核心网设备，其特征在于：
    所述接收器还被配置为接收所述第一承载的QoS信息，所述第一承载的QoS信息包括第一承载所支持的QoS等级和第一承载的反射QoS属性。
PCT/CN2017/105537 2016-11-04 2017-10-10 无线通信方法、用户设备接入网设备、和核心网设备 WO2018082431A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17866919.8A EP3528533B1 (en) 2016-11-04 2017-10-10 Wireless communication method, user equipment, access network device, and system
US16/403,045 US11044629B2 (en) 2016-11-04 2019-05-03 Wireless communication method, user equipment, access network device, and core network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610976971.9A CN108024284B (zh) 2016-11-04 2016-11-04 无线通信方法、用户设备接入网设备、和核心网设备
CN201610976971.9 2016-11-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/403,045 Continuation US11044629B2 (en) 2016-11-04 2019-05-03 Wireless communication method, user equipment, access network device, and core network device

Publications (1)

Publication Number Publication Date
WO2018082431A1 true WO2018082431A1 (zh) 2018-05-11

Family

ID=62075771

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105537 WO2018082431A1 (zh) 2016-11-04 2017-10-10 无线通信方法、用户设备接入网设备、和核心网设备

Country Status (4)

Country Link
US (1) US11044629B2 (zh)
EP (1) EP3528533B1 (zh)
CN (1) CN108024284B (zh)
WO (1) WO2018082431A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109804663B (zh) * 2016-10-11 2021-02-12 华为技术有限公司 一种数据传输的方法及其装置
WO2019101100A1 (en) * 2017-11-21 2019-05-31 Mediatek Inc. Reflective qos control in wireless communications
CN112154686A (zh) * 2018-05-18 2020-12-29 上海诺基亚贝尔股份有限公司 用于执行无线通信的方法和装置
CN112205022B (zh) * 2018-05-28 2024-04-12 三菱电机株式会社 无线接入网络的管理装置
CN110557750B (zh) * 2018-06-04 2021-08-03 华为技术有限公司 信息传输方法、网关设备、核心网设备以及存储介质
CN110635880B (zh) 2018-06-22 2021-12-21 华为技术有限公司 信号传输方法、网络设备及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102791007A (zh) * 2011-05-17 2012-11-21 中兴通讯股份有限公司 上行数据的处理方法及装置
CN103096314A (zh) * 2011-11-01 2013-05-08 中兴通讯股份有限公司 一种实现反射QoS机制的方法、系统和PCRF
CN105766022A (zh) * 2013-08-29 2016-07-13 瑞典爱立信有限公司 Wifi上基于3gpp承载的qos模型支持

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9521679B2 (en) * 2014-03-06 2016-12-13 Cisco Technology, Inc. Systems and methods for implementing reflective EPS bearers to ensure uplink quality of service
WO2018070689A1 (ko) * 2016-10-11 2018-04-19 엘지전자(주) 무선 통신 시스템에서의 반영형 서비스 퀄리티 적용 방법 및 이를 위한 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102791007A (zh) * 2011-05-17 2012-11-21 中兴通讯股份有限公司 上行数据的处理方法及装置
CN103096314A (zh) * 2011-11-01 2013-05-08 中兴通讯股份有限公司 一种实现反射QoS机制的方法、系统和PCRF
CN105766022A (zh) * 2013-08-29 2016-07-13 瑞典爱立信有限公司 Wifi上基于3gpp承载的qos模型支持

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON, LG ELECTRONICS: "TS 23.139: Correction of Procedures for WLAN access", 3GPP DRAFT; SA WG2 MEETING #S2-86 S2-113282, 11 - 15 JULY 2011, NAANTALI, FINLAND, 5 July 2011 (2011-07-05), XP050548575 *
See also references of EP3528533A4 *

Also Published As

Publication number Publication date
CN108024284A (zh) 2018-05-11
EP3528533A1 (en) 2019-08-21
CN108024284B (zh) 2020-09-08
EP3528533B1 (en) 2022-01-19
US20190261212A1 (en) 2019-08-22
EP3528533A4 (en) 2019-08-21
US11044629B2 (en) 2021-06-22

Similar Documents

Publication Publication Date Title
WO2018082431A1 (zh) 无线通信方法、用户设备接入网设备、和核心网设备
US11546771B2 (en) Communication method, communications apparatus, and system
US10856341B2 (en) Wireless communication method, user equipment, and access network device
US11510223B2 (en) Wireless data priority services
US10721754B2 (en) Data transmission method and apparatus
US20200280871A1 (en) Optimization of resource allocation based on received quality of experience information
WO2019062499A1 (zh) 一种策略确定的方法及通信装置
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
EP3468258B1 (en) Data transmission control method and device
US11489642B2 (en) Wireless transmission using data flow bearers
WO2018059223A1 (zh) 一种通信方法及装置
WO2014071881A1 (zh) 回程网络承载管理方法及设备
WO2021037115A1 (zh) 无线网络资源的管理方法，网络系统及相关产品
CN108632892B (zh) 无线通信方法、终端、接入网设备和网络系统
WO2017193363A1 (zh) 业务数据流发送方法及装置
KR20170013673A (ko) 패킷 트래픽 제어 방법 및 이를 위한 장치

Legal Events

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

Ref document number: 17866919

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017866919

Country of ref document: EP

Effective date: 20190514