WO2018141278A1 - 无线通信方法、用户设备、接入网设备和网络系统 - Google Patents

无线通信方法、用户设备、接入网设备和网络系统 Download PDF

Info

Publication number
WO2018141278A1
WO2018141278A1 PCT/CN2018/075187 CN2018075187W WO2018141278A1 WO 2018141278 A1 WO2018141278 A1 WO 2018141278A1 CN 2018075187 W CN2018075187 W CN 2018075187W WO 2018141278 A1 WO2018141278 A1 WO 2018141278A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
data stream
downlink
uplink
downlink data
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/075187
Other languages
English (en)
French (fr)
Inventor
李宏
韩锋
晋英豪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20212340.2A priority Critical patent/EP3852324B1/en
Priority to EP18748448.0A priority patent/EP3562241B1/en
Publication of WO2018141278A1 publication Critical patent/WO2018141278A1/zh
Priority to US16/527,860 priority patent/US11489642B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2491—Mapping quality of service [QoS] requirements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H04L5/0039—Frequency-contiguous, i.e. with no allocation of frequencies for one user or terminal between the frequencies allocated to another
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • 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/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the 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, and a network system.
  • the Second System Architecture Working Group (SA2) organized by the Third Generation Partnership Project (3GPP) defines a stream-based data transmission method.
  • the transmission method specifically includes: when the downlink data packet reaches the core network user plane (Core Network User Plane, CNUP for short) function entity, the CN UP function entity sends the data packet to the access network in the form of a stream.
  • the access network (AN) then transmits the data packet to the user equipment (UE) in the form of a stream.
  • the current 3GPP access network working group defines a different architecture than the 3GPP system architecture group, and the 3GPP access network working group may reserve a bearer in the access network. Under this architecture, the stream-based data transmission method cannot be simply reused to ensure data transmission under the access network.
  • 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 ensure data transmission under an access network.
  • an embodiment of the present invention provides a wireless communication method, including the following steps: an access network device receives a first downlink data stream that is sent by a core network device in a form of a flow; and the access network device sends the information to the user equipment.
  • Information where the information includes a mapping relationship between the first downlink data stream and a downlink bearer.
  • the access network device When the access network retains the bearer, the access network device sends a mapping relationship between the first downlink data flow and the downlink bearer to the user equipment, and the mapping relationship can be used to determine the bearer to be used when sending the data flow, and the connection is ensured. Data transmission under the network.
  • the method further includes: the access network device sending, by using the downlink bearer, the first downlink data stream to the user equipment.
  • the uplink bearer used when transmitting the corresponding uplink data stream can be determined by the mapping relationship between the downlink data stream and the downlink bearer. A guarantee of quality of service (QoS) is achieved. Further, by directly receiving the mapping relationship, it is possible to avoid adding an indication to each data packet, and reducing the data transmission overhead of the air interface.
  • QoS quality of service
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the first downlink data stream received by the access network device includes a reflected quality of service identifier RQI, and the first downlink data stream sent by the access network device does not include the RQI.
  • RQI reflected quality of service identifier
  • an embodiment of the present invention provides a wireless communication method, including the following steps: a user equipment receives information, where the information includes a mapping relationship between a first downlink data stream and a downlink bearer. The user equipment receives the first downlink data stream by using the downlink bearer.
  • the method further includes: the user equipment sends a first uplink data stream by using an uplink bearer, where, if the first uplink data stream corresponds to the first downlink data stream, The uplink bearer is determined according to the downlink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • an embodiment of the present invention provides a network device.
  • the network device includes a receiving unit and a transmitting unit.
  • the receiving unit is configured to receive a first downlink data stream that is sent by the core network device in the form of a stream.
  • the sending unit is configured to send information to the user equipment, where the information includes a mapping relationship between the first downlink data stream and a downlink bearer.
  • the sending unit is further configured to send the first downlink data stream to the user equipment by using the downlink bearer.
  • the receiving unit is further configured to: receive the first uplink data stream that is sent by the user equipment by using an uplink bearer, where, if the first uplink data stream is corresponding to the first downlink data stream, The uplink bearer is determined according to the downlink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the first downlink data stream received by the receiving unit includes a reflected quality of service identifier RQI, and the first downlink data stream sent by the sending unit does not include the RQI.
  • an embodiment of the present invention provides a user equipment.
  • the user equipment includes a receiving unit.
  • the receiving unit is configured to receive information, where the information includes a mapping relationship between the first downlink data stream and a downlink bearer.
  • the receiving unit is further configured to receive the first downlink data stream by using the downlink bearer.
  • the user equipment also includes a transmitting unit.
  • the sending unit is configured to send, by using an uplink bearer, a first uplink data stream, where, if the first uplink data stream corresponds to the first downlink data stream, the uplink bearer is according to the The downlink bearer is determined.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • an embodiment of the present invention provides a wireless communication method, including the following steps: a user equipment receives information, where the information includes a mapping rule of a data stream and a bearer.
  • the user equipment sends the first uplink data stream by using an uplink bearer, where the uplink bearer is determined according to the mapping rule.
  • the access network retains the bearer
  • the user equipment receives the mapping rule of the data stream and the bearer, and the rule can determine the bearer to be used when sending the data stream, thereby ensuring data transmission under the access network.
  • the rule can determine the bearer to be used when sending the data stream, thereby ensuring data transmission under the access network.
  • the method further includes: the user equipment receiving the first downlink data stream by using a downlink bearer.
  • the mapping rule of the data flow and the bearer includes: a mapping relationship between the first downlink data flow and the downlink bearer.
  • the uplink bearer is determined according to the mapping rule, and includes: if the first uplink data stream corresponds to the first downlink data stream, the uplink bearer is determined according to the downlink bearer.
  • the uplink bearer used when transmitting the corresponding uplink data stream can be determined by the mapping relationship between the downlink data stream and the bearer.
  • the data transmission under the access network is guaranteed, and the quality of service (QoS) can be guaranteed by the bearer during uplink data transmission.
  • QoS quality of service
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the method further includes: the user equipment receiving the second downlink data stream by using a downlink bearer.
  • the user equipment sends a second uplink data stream by using the uplink bearer, where the second uplink data stream corresponds to the second downlink data stream.
  • the mapping rule of the data stream and the bearer further includes: a mapping relationship between the second downlink data stream and the downlink bearer.
  • the method further includes: the first downlink data stream includes a reflected quality of service identifier when transmitted between the core network device and the access network device.
  • the first downlink data stream includes a reflected quality of service identifier when transmitted between the core network device and the access network device.
  • the user equipment receives information, including: the user equipment receives the information from an access network device by means of RRC signaling.
  • an embodiment of the present invention provides a wireless communication method, including the following steps: an access network device sends information, where the information includes a mapping rule of a data flow and a bearer.
  • the access network device receives a first uplink data stream that is sent by the user equipment by using an uplink bearer, where the uplink bearer is determined according to the mapping rule.
  • the method further includes: the access network device sending the first downlink data stream to the user equipment by using a downlink bearer.
  • the mapping rule of the data flow and the bearer includes: a mapping relationship between the first downlink data flow and the downlink bearer.
  • the uplink bearer is determined according to the mapping rule, and includes: if the first uplink data stream corresponds to the first downlink data stream, the uplink bearer is determined according to the downlink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between an identifier ID of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first The uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the method further includes: the access network device sending a second downlink data stream to the user equipment by using a downlink bearer.
  • the access network device uses the uplink bearer to receive a second uplink data stream, where the second uplink data stream corresponds to the second downlink data stream.
  • the mapping rule of the data stream and the bearer further includes: a mapping relationship between the second downlink data stream and the downlink bearer.
  • the method further includes: the access network device receiving the second downlink data stream, and the second downlink data stream comprising an RQI.
  • the method further includes: the access network device receiving the first downlink data stream, where the first downlink data stream includes a reflected quality of service identifier RQI.
  • the access network device sends information, including: the access network device sends the information to the user equipment by means of RRC signaling.
  • a seventh aspect of the present invention provides a wireless communication method, including the following steps: a user equipment receives a downlink data stream from a downlink bearer, where the downlink data stream includes a reflected quality of service identifier (RQI); and the user equipment uses an uplink bearer to send Upstream data stream.
  • the uplink data stream corresponds to the downlink data stream, and the uplink bearer is determined according to the downlink bearer.
  • the user equipment can obtain the mapping relationship between the data stream and the bearer by using the reflected quality of service identifier RQI, which can reduce signaling interaction. Applicable to some services with infrequent packet data characteristics.
  • the uplink bearer is determined according to the downlink bearer, including: the uplink bearer and the downlink bearer are the same bearer, or the quality of service QoS attribute of the uplink bearer and the downlink bearer
  • the QoS attributes are the same.
  • the uplink data stream corresponds to the downlink data stream, and the ID of the uplink data stream is the same as the ID of the downlink data stream, or the uplink data stream is
  • the downlink data flows belong to the same service flow, or the uplink data flow and the downlink data flow belong to the same session flow.
  • an embodiment of the present invention provides a wireless communication method, including the following steps: an access network device sends a downlink data stream by using a downlink bearer, where the downlink data stream includes a reflected quality of service identifier RQI, and the access network device uses The uplink bearer receives the upstream data stream.
  • the uplink data stream corresponds to the downlink data stream, and the uplink bearer is determined according to the downlink bearer.
  • the uplink bearer is determined according to the downlink bearer, including: the uplink bearer and the downlink bearer are the same bearer, or the quality of service QoS attribute of the uplink bearer and the downlink bearer
  • the QoS attributes are the same.
  • the uplink data stream corresponds to the downlink data stream, and the ID of the uplink data stream is the same as the ID of the downlink data stream, or the uplink data stream is
  • the downlink data flows belong to the same service flow, or the uplink data flow and the downlink data flow belong to the same session flow.
  • the method further includes: the access network device receiving, in a streaming manner, the downlink data stream sent by the core network device; the access network device flowing to the core network in a streaming manner The device sends the uplink data stream.
  • an embodiment of the present invention provides a network device, including a processor, a memory, and a transceiver.
  • the processor is coupled to a memory and a transceiver, respectively.
  • the memory is for storing program instructions, and the processor causes the network device to perform the method of the first aspect or the sixth aspect or the eighth aspect described above by executing program instructions stored in the memory.
  • an embodiment of the present invention provides a user equipment, including a processor, a memory, and a transceiver.
  • the processor is coupled to a memory and a transceiver, respectively.
  • the memory is for storing program instructions, and the processor causes the user equipment to perform the method of the second aspect or the fifth aspect or the seventh aspect described above by executing program instructions stored in the memory.
  • an embodiment of the present invention provides a user equipment.
  • the user equipment comprises means for implementing the method of the above fifth aspect, such as a transmitting unit, a receiving unit.
  • the user equipment comprises means for implementing the method described in the seventh aspect above.
  • an embodiment of the present invention provides an access network device.
  • the access network device comprises means for implementing the method described in the sixth aspect above, such as a transmitting unit and a receiving unit.
  • the user equipment comprises means for implementing the method of the above eighth aspect.
  • an embodiment of the present invention provides a communication system, where the system includes the user equipment and the access network device in the foregoing aspect.
  • embodiments of the present invention provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present invention provides a computer storage medium comprising instructions that, when run on a computer, cause the computer to perform the methods involved in 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 structural diagram of a network device according to still another embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a user equipment 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.
  • FIG. 8 is a schematic structural diagram of a user equipment according to still another embodiment of the present invention.
  • system and “network” are used interchangeably herein.
  • network 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.
  • 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.
  • send herein may be sent directly or indirectly through other network elements.
  • receiving herein may be received directly or indirectly through other network elements.
  • bearer in this context is a data transmission channel established by the network to achieve differentiated data transmission and corresponding to QoS.
  • a bearer can be implemented in a data tunnel manner, for example, a GPRS Tunneling Protocol (GTP)-based logical data transmission channel established between a source node and a destination node of 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
  • data stream refers to a data stream generated by a UE or a network and associated with a certain service.
  • a QoS flow can be a form of data flow.
  • a business flow can also be a form of data flow.
  • 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 transmitting in the form of a stream or receiving in the form of a stream.
  • 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.
  • the mapping mode may also be related to the QoS attribute of the data stream.
  • a 1:1 mapping manner is used for a guaranteed bit rate (GBR) data stream, and a non-guaranteed bit rate (non-guaranteed bit rate,
  • GRR guaranteed bit rate
  • non-guaranteed bit rate non-guaranteed bit rate
  • a bearer can map one or more data streams and transmit them in a bearer manner to 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.
  • IP flow refers to a high-level (above the MAC layer) generated by a UE or an external data network (DN) and a service-related data, which may be based on an IP protocol or based on non-IP (non-IP). protocol.
  • DN external data network
  • non-IP non-IP protocol
  • QoS rule herein is a set of information based on an operator's policy based on application requirements and QoS parameters, used to detect data flows and define their associated QoS parameters, and to determine how data flows.
  • the manner in which the data stream is transmitted may include streaming or by bearer. Streaming may be by transmitting data packets of the data stream in a stream.
  • the bearer transmission may be to map one or more data streams onto one bearer for transmission.
  • the QoS rules may include QoS requirements information and/or transmission methods of the data streams, such as transmission in a bearer manner or in a streaming manner.
  • the QoS requirement information may include a data rate, a transmission delay, and the like.
  • QoS rules may also include mapping rules for 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 a QoS class of the service, a maximum bit rate (MBR), and an allocation priority (ARP), and is used to identify the manner in which the network processes the data on the bearer. 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.
  • Flow Priority Indicator refers to the processing priority for each stream when processing data corresponding to a 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.
  • 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 downlink data includes the RQI, it may be used to indicate that the corresponding uplink data transmission adopts a QoS control manner consistent with the downlink data transmission.
  • RQI can be applied to a single data stream or an aggregation of multiple data streams.
  • 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 a 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 (Distributed Unit). ; referred to as DU) and so on.
  • gNB Next-generation Node B
  • TRP Transmit and Receive Point
  • CU Central Unit
  • DU Distributed Unit
  • 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 adopt different QoS control methods to achieve their flexible QoS management functions according to their respective resource usage.
  • 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, IMS for short)
  • 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.
  • the PF generates a NAS layer filter that is used to indicate how to map the IP stream to the data stream.
  • the PF sends the over-NAS layer filter to the CN CP functional entity and the CN UP functional entity, and the CN CP functional entity forwards the NAS layer filter to the UE via the AN CP functional entity through NAS signaling.
  • PDU Protocol Data Unit
  • the data network sends the first downlink IP data packet to the CN UP functional entity.
  • the CN UP function entity receives the first downlink IP data packet.
  • IP packets can be transmitted in the form of IP streams.
  • the first downlink IP data packet may be a first downlink IP flow.
  • the CN UP function entity processes the first downlink IP flow, and maps the first downlink IP flow to the first downlink data flow.
  • the CN UP function entity sends the first downlink data stream to the AN UP function entity.
  • the AN UP function entity receives the first downlink data stream.
  • the first downlink data stream corresponds to one FPI and is recorded as FPI_1.
  • the CN UP function entity may further allocate a flow identifier (ID) for the first downlink data stream, which is denoted as Flow ID_1.
  • ID flow identifier
  • the CN UP function entity adds information of the data stream to the packet header of the first downlink data stream.
  • the information of the data stream may include: an FPI, a stream identifier.
  • the CN UP function entity may further add an RQI in a packet header of the first downlink data stream. In this way, the AN UP function entity can clearly perform the QoS attribute of the first downlink data stream when transmitting the corresponding uplink data stream.
  • the mapping of the first downlink IP flow to the first downlink data flow may adopt a template filtering-based 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 After receiving the first downlink data flow, the AN UP function entity checks whether there is a bearer that can be mapped. For example, it can be checked according to the QoS attribute of the first downlink data stream whether there is a bearer that can be mapped. If not, the AN UP functional entity initiates a bearer setup request to the AN CP functional entity, and the AN CP functional entity receives the bearer setup request.
  • the bearer setup request contains QoS information.
  • the bearer setup request may include QoS information of the first downlink data flow, for example, an FPI.
  • the bearer setup request may further include a flow ID of the first downlink data stream.
  • the AN CP function entity initiates establishing a bearer between the UE and the AN UP functional entity.
  • the AN CP function entity initiates the 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 205 may be referred to as a downlink bearer.
  • the AN CP functional entity During the establishment of the downlink bearer, the AN CP functional entity generates a bearer identifier, which can be used to identify the downlink bearer.
  • the AN CP functional entity configures QoS parameters, such as QoS levels, for the bearer.
  • the above describes the establishment of a bearer based on the downlink data flow trigger. It is worth noting that the bearer can also be pre-established, or the bearer can also be the default bearer.
  • the downlink bearer can be unidirectional. Alternatively, the downlink bearer may also be bidirectional, that is, it may also be used for uplink data transmission, that is, also an uplink bearer.
  • the AN CP functional entity sends information to the UE, where the information includes mapping rules of the data flow and the bearer. For example, the mapping relationship between the first downlink data stream and the downlink bearer.
  • the message may be sent in the form of Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the UE receives the information.
  • the data flow and bearer mapping rules will be used by the UE to determine the data flow to bearer mapping when transmitting uplink data.
  • the mapping relationship between the first downlink data stream and the downlink bearer may include: a correspondence between the identifier ID of the first downlink data stream and the ID of the downlink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a quality of service QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the mapping between the data stream and the bearer may also directly include the mapping relationship between the uplink data stream and the uplink bearer, and may specifically include: a correspondence between the identifier ID of the uplink data stream and the ID of the uplink bearer.
  • the correspondence between the quality of service QoS attribute of the uplink data stream and the ID of the uplink bearer may include: a correspondence between the identifier ID of the uplink data stream and the ID of the uplink bearer.
  • the UE sends an acknowledgement message to the AN CP function entity, confirming that the UE has received the message including the mapping rule of the data stream and the bearer.
  • the AN CP functional entity receives the acknowledgment message.
  • 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, such as QCI.
  • step 208 is also optional. For example, if step 205 is not triggered by step 204, step 208 may also be omitted.
  • the AN UP function entity maps the first downlink data stream to the downlink bearer, and sends the first downlink data stream to the UE by using the downlink bearer.
  • the UE receives the first downlink data stream.
  • the first downlink data stream transmitted on the downlink bearer does not need to include RQI and FPI.
  • the first downlink data stream transmitted on the downlink bearer may include an ID of the data stream. In this way, if there are two or more data streams transmitted on the downlink bearer, different data streams can be correctly distinguished.
  • step 209 is also optional. For example, if steps 202 and 203 do not occur, step 209 is not required.
  • the UE maps the first uplink data stream to the uplink bearer.
  • the uplink bearer is determined according to the mapping rule.
  • the mapping rule of the data flow and the bearer includes: a mapping relationship between the first downlink data flow and the downlink bearer.
  • the uplink bearer is determined according to the mapping rule, and includes: if the first uplink data stream corresponds to the first downlink data stream, the uplink bearer is determined according to the downlink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between the identifier ID of the first downlink data stream and the ID of the downlink bearer.
  • the first uplink data stream corresponds to the first downlink data stream, and includes: the ID of the first uplink data stream is the same as the ID of the first downlink data stream, or the first uplink data stream and the first
  • the downlink data stream belongs to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the first downlink data stream and the downlink bearer includes: a correspondence between a quality of service QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the first uplink data stream is corresponding to the first downlink data stream, and the QoS attribute of the first uplink data stream is the same as the QoS attribute of the first downlink data stream, or
  • the first uplink data stream and the first downlink data stream belong to the same service stream, or the first uplink data stream and the first downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the uplink bearer and the downlink bearer may be the same or different. If the uplink bearer is a bidirectional bearer, the downlink bearer and the uplink bearer may be the same.
  • the uplink bearer can also be a new bearer.
  • the downlink 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 an uplink bearer, where the uplink bearer and the downlink bearer have the same or corresponding QoS attributes.
  • the UE maps the first uplink IP stream to the first uplink data stream by using a non-access stratum (NAS) layer mapping.
  • the first uplink data stream is further mapped to the uplink bearer by using an Access Stratum (AS) layer mapping.
  • NAS non-access stratum
  • AS Access Stratum
  • the UE sends the first uplink data stream to the AN UP function entity by using an uplink bearer.
  • the AN UP function entity receives the first uplink data stream by using a downlink bearer.
  • the AN UP function entity demaps the first uplink data stream received from the downlink bearer, and the AN UP function entity may add a corresponding flow priority indication (FPI) in the data packet header of the first uplink data stream.
  • the AN UP functional entity may also add a flow ID to the packet header of the first upstream data stream.
  • the AN UP function entity streams the first uplink data stream to the CN UP function entity.
  • the CN UP function entity sends the first uplink data in the received first uplink data stream to the data network in the form of an IP data packet.
  • the flow-based data transmission mode is used in the core network and the interface between the core network and the access network, and the QoS control information is transmitted by using the user plane, and the bearer is used in the access network (including the air interface).
  • the data transmission method and the QoS control information are transmitted using the control plane.
  • 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 row bearer can be a default bearer, ie no need to be triggered by data traffic.
  • the bearer may also be triggered by the transmission of the first downlink data stream.
  • the establishment process of the bearer may refer to the description in the embodiment shown in FIG. 2 .
  • the bearer may be unidirectional, such as an uplink bearer or a downlink bearer.
  • the bearer may also be bidirectional, and has the functions of uplink transmission and downlink transmission, for example, uplink bearer and downlink bearer are combined.
  • the data network sends the second downlink IP data packet to the CN UP functional entity.
  • the CN UP function entity receives the second downlink IP data packet.
  • IP packets can be transmitted in the form of IP streams.
  • the second downlink IP data packet may be a second downlink IP flow.
  • the CN UP function entity processes the second downlink IP flow, and maps the second downlink IP flow to the second downlink data flow.
  • the CN UP function entity sends the second downlink data stream to the AN UP function entity.
  • the AN UP function entity receives the second downlink data stream. Specifically, the CN UP function entity sends the second downlink data stream to the AN UP function entity in the form of a stream.
  • the second downlink data stream corresponds to one FPI and is recorded as FPI_2.
  • the CN UP function entity may further allocate a flow identifier (ID) for the second downlink data stream, and record it as Flow ID_2.
  • ID flow identifier
  • the CN UP function entity adds information of the data stream to the packet header of the second downlink data stream.
  • the information of the data stream may include: an FPI, a stream identifier.
  • the CN UP function entity may further add an RQI in a packet header of the second downlink data stream. In this way, the AN UP function entity can clearly perform the QoS attribute of the second downlink data stream when transmitting the corresponding uplink data stream.
  • mapping of the second downlink IP flow to the second downlink data flow may be performed by using a template filtering method. For details, refer to the foregoing description.
  • the AN UP function entity After receiving the second downlink data flow, the AN UP function entity checks whether there is a bearer that can be mapped. For example, it can be checked according to the QoS attribute of the second downlink data stream whether there is a bearer that can be mapped. The AN UP function entity acknowledges that the second downlink data stream can be mapped to the downlink bearer.
  • the downlink bearer may be the bearer established in step 302. If it is determined that the first downlink data stream is mapped to the downlink bearer, both the first downlink data stream and the second downlink data stream may be mapped to the downlink bearer.
  • the AN UP function entity sends information to the AN CP function entity, where the information includes mapping rules of the data stream and the bearer.
  • the mapping relationship between the second downlink data stream and the downlink bearer may include: a correspondence between the identifier ID of the second downlink data stream and the ID of the downlink bearer.
  • the mapping relationship between the second downlink data stream and the downlink bearer includes: a correspondence between a quality of service QoS attribute of the first downlink data stream and an ID of the downlink bearer.
  • the mapping between the data stream and the bearer may also directly include the mapping relationship between the uplink data stream and the uplink bearer, and may specifically include: a correspondence between the identifier ID of the uplink data stream and the ID of the uplink bearer.
  • the correspondence between the quality of service QoS attribute of the uplink data stream and the ID of the uplink bearer may include: a correspondence between the identifier ID of the uplink data stream and the ID of the uplink bearer.
  • the AN CP function entity sends information to the UE, where the information includes mapping rules of the data stream and the bearer.
  • the UE receives the message.
  • the message may be sent in the form of Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the UE receives the information.
  • the data flow and bearer mapping rules will be used by the UE to determine the data flow to bearer mapping when transmitting uplink data. If the previous AN CP function entity sends a message including the mapping rule of the data stream and the bearer to the UE, the message in step 307 may be an update message, as long as the mapping relationship between the second downlink data stream and the downlink bearer is updated. Of course, the message can also be a separate message.
  • the UE sends an acknowledgement message to the AN CP function entity, and confirms that the UE has received the message including the mapping rule of the data stream and the bearer.
  • the AN CP functional entity receives the acknowledgment message.
  • the AN CP function entity sends the acknowledgement message to the AN UP function entity.
  • the AN UP function entity receives the acknowledgment message.
  • the AN UP function entity maps the second downlink data stream to the downlink bearer, and sends the second downlink data stream to the UE by using the downlink bearer.
  • the second downlink data stream transmitted on the downlink bearer does not need to include RQI and FPI.
  • the AN UP function entity also needs to transmit other downlink data streams (for example, the first downlink data stream), and the other downlink data streams can be mapped to the downlink bearer, the AN UP function entity also maps other downlink data streams to the downlink. Bear and send these other downstream data streams through the downlink bearer. If there are two or more downlink data streams mapped to the downlink bearer, the data of the downlink data stream transmitted in the downlink bearer should include the respective stream ID information.
  • the UE maps the second uplink data stream to the uplink bearer.
  • the uplink bearer is determined according to the mapping rule.
  • the mapping rule of the data stream and the bearer includes: a mapping relationship between the second downlink data stream and the downlink bearer.
  • the uplink bearer is determined according to the mapping rule, and includes: if the second uplink data stream corresponds to the second downlink data stream, the uplink bearer is determined according to the downlink bearer.
  • the mapping relationship between the second downlink data stream and the downlink bearer includes: a correspondence between the identifier ID of the second downlink data stream and the ID of the downlink bearer.
  • the second uplink data stream corresponds to the second downlink data stream, and includes: the ID of the second uplink data stream is the same as the ID of the second downlink data stream, or the second uplink data stream and the second downlink data stream.
  • the flow belongs to the same service flow, or the second uplink data flow belongs to the same session flow as the second downlink data flow.
  • the uplink bearer is determined according to the downlink bearer, and the downlink bearer is the same bearer as the uplink bearer, or the quality of service QoS attribute of the downlink bearer is the same as the QoS attribute of the uplink bearer.
  • the mapping relationship between the second downlink data stream and the downlink bearer includes: a correspondence between a quality of service QoS attribute of the second downlink data stream and an ID of the downlink bearer.
  • the QoS attribute of the second uplink data stream is the same as the QoS attribute of the second downlink data stream, or the second
  • the uplink data stream and the second downlink data stream belong to the same service flow, or the second uplink data flow and the second downlink data flow belong to the same session flow.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the uplink bearer and the downlink bearer may be the same or different. If the uplink bearer is a bidirectional bearer, the downlink bearer and the uplink bearer may be the same.
  • the uplink bearer can also be a new bearer.
  • the downlink 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 an uplink bearer, where the uplink bearer and the downlink bearer have the same or corresponding QoS attributes.
  • the UE also puts the other uplink data stream to be mapped to the uplink bearer according to the mapping rule of the data stream and the bearer. These other upstream data streams are mapped to the upstream bearer.
  • the UE sends a second uplink data stream to the AN UP function entity by using the uplink bearer, and the AN UP function entity receives the second uplink data stream.
  • the UE may further send the first uplink data stream to the AN UP function entity by using the uplink bearer, and the AN UP function entity receives the first uplink data stream.
  • the AN UP function entity demaps the uplink data stream received from the downlink bearer, and the AN UP function entity adds a corresponding flow priority indication (FPI) to the data packet header of the uplink data stream.
  • the AN UP functional entity can also add a flow ID to the packet header of the upstream data stream.
  • the AN UP function entity streams the second uplink data stream to the CN UP function entity.
  • the CN UP functional entity receives the second upstream data stream.
  • the AN UP function entity streams the first uplink data stream to the CN UP function entity.
  • the CN UP functional entity receives the first upstream data stream.
  • the CN UP function entity sends the uplink data in the received uplink data stream to the data network by using an IP data packet. Specifically, the CN UP function entity sends the received uplink data in the second uplink data stream to the data network through the IP data packet. Optionally, the CN UP function entity sends the received uplink data in the first uplink data stream to the data network by using the IP data packet.
  • the mapping rule of the bearer and the data stream is sent to the UE by using a signaling manner, and the UE determines, according to the mapping rule, the bearer used when transmitting the uplink data stream. This can save the transmission overhead of the data plane and save the air interface overhead. The load of the packet header can be greatly reduced, and the effective data transmission efficiency of the air interface is effectively improved.
  • 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:
  • 401-404 is basically the same as 301-304, and can refer to 301-304, and details are not described herein again.
  • the AN UP function entity determines to perform data transmission by using a reflective QoS.
  • the AN UP functional entity can determine its own way of using reflected QoS.
  • the AN UP functional entity may also request the AN CP functional entity to transmit the downlink data stream, and the AN CP functional entity informs the AN UP functional entity after determining the manner in which the reflected QoS is used.
  • the AN UP function entity checks whether there is a bearer that can be mapped. For example, according to the QoS attribute check of the second downlink data stream, it can be confirmed that the second downlink data stream can be mapped to the downlink bearer. If it is determined that the first downlink data stream is mapped to the downlink bearer, both the first downlink data stream and the second downlink data stream may be mapped to the downlink bearer.
  • the AN UP function entity maps the second downlink data stream to the downlink bearer, and sends the data packet of the second downlink data stream to the UE by using the downlink bearer.
  • the data of the second downlink data stream includes RQI. If the AN UP function entity also needs to transmit the first downlink data stream, the AN UP function entity also maps the first downlink data stream to the downlink bearer. Correspondingly, the data of the first downlink data stream includes an RQI. If there are two or more downlink data streams mapped to the downlink bearer, the data of the downlink data stream transmitted in the downlink bearer should include the respective stream ID information.
  • the UE When the UE needs to send the second uplink data stream corresponding to the second downlink data stream to the access network device, the UE sends the second uplink data stream by using the uplink bearer.
  • the data of the second downlink data stream includes an RQI, and the second uplink data stream corresponds to the second downlink data stream, and the uplink bearer is determined according to the downlink bearer.
  • the uplink data stream corresponds to the downlink data stream, and the ID of the uplink data stream is the same as the ID of the downlink data stream, or the uplink data stream and the downlink data stream belong to the same service.
  • the stream, or the upstream data stream and the downlink data stream belong to the same session stream.
  • the uplink bearer is determined according to the downlink bearer, and the uplink bearer is the same bearer as the downlink bearer, or the quality of service QoS attribute of the uplink bearer is the same as the QoS attribute of the downlink bearer.
  • the respective data streams transmitted on the uplink bearer need to include respective data stream ID information.
  • step 402 is prior to 404, that is, when the AN UP function entity receives the downlink data stream, the appropriate bearer is available for mapping.
  • the AN UP functional entity may send a bearer setup request to the AN CP functional entity to establish an appropriate bearer.
  • steps 204, 205, and 208 in the embodiment shown in FIG. 2.
  • the mapping rule of the bearer and the data stream is sent to the UE by means of the reflected QoS, and the UE determines the bearer used when transmitting the uplink data stream according to the RQI. This can reduce the transmission overhead of the signaling plane and reduce the delay.
  • the access network device may decide to notify the UE by means of signaling (the embodiment shown in FIG. 2 or FIG. 3) or the manner of reflecting QoS (the embodiment shown in FIG. 4).
  • some network devices only support specific types of services, such as Machine Type Communication or mobile broadband (MBB).
  • MBB Mobile broadband
  • the access network device can select an appropriate method according to the service characteristics of the type of service it supports. For example, machine-type communication services have infrequent packets, and such access network devices can adopt a method of reflecting QoS. For the mobile broadband service of big data, signaling can be adopted even if the core network has used the method of reflecting QoS.
  • the access network device can also select an appropriate mode according to the service characteristics of the service type.
  • the UE can also select an appropriate mode according to the service characteristics of the service type.
  • Avoidance mechanisms such as: signaling has a higher priority than reflection QoS.
  • the reflected QoS has a higher priority than the signaling.
  • the access network device can also select an appropriate mode according to the QoS attributes of the data stream. For example, if the access network device receives the data stream sent by the core network device, including the RQI, that is, the core network adopts the reflection QoS method, the access network device adopts a method of reflecting QoS, and if the data flow does not include the RQI, the access network device Signaling can be used. For example, for the data stream of the GBR, signaling may be adopted; for the data stream of the non-GBR, the method of reflecting QoS may be adopted.
  • network-to-data QoS control includes two layers of QoS mapping, which are NAS layer mapping and AS layer mapping, respectively.
  • the NAS layer mapping can map IP flows to data flows (eg, QoS flows).
  • the AS layer mapping can map data streams to bearers.
  • the downlink transmission is such that the operation is completed by the AN UP, and when the uplink transmission is performed, the operation is completed by the UE.
  • the patent application can be applied to the QoS architecture in which the access network and the core network have independent QoS control functions, and the access network can determine the QoS control mode to a greater extent, and achieve a balance between satisfying service QoS requirements and improving network resource utilization efficiency.
  • FIG. 5 is a schematic block diagram of a network device 500 according to an embodiment of the present invention. It should be understood that the network device 5 is capable of performing the various steps performed by the access network device in the methods of FIGS. 2 to 4, and is not described in detail herein to avoid repetition.
  • Network device 500 may be an access network device, which may include an AN CP functional entity and/or an AN UP functional entity.
  • the transmitting unit 501 is configured to perform a transmitting step of the AN CP functional entity and/or the AN UP functional entity in FIGS. 2 to 4.
  • the transmitting unit 501 can be configured to perform the transmitting step of the AN CP functional entity in FIG. 2 to FIG. 4, specifically including transmitting information and/or transmitting a bearer setup response.
  • the sending unit 501 may be configured to perform the sending step of the AN UP function entity in FIG. 2 to FIG.
  • the receiving unit 502 is configured to perform a receiving step of the AN CP functional entity and/or the AN UP functional entity in FIGS. 2 to 4.
  • the receiving unit 502 can be configured to perform the receiving step of the AN CP functional entity in FIG. 2 to FIG. 4, which may include receiving a bearer setup request and/or receiving the UE. Acknowledge the message and/or receive the information sent by the AN UP.
  • the receiving unit 502 may be configured to perform the receiving step of the AN UP function entity in FIG. 2 to FIG.
  • a bearer setup response may specifically include receiving a bearer setup response and/or receiving an acknowledgement message and/or Receiving data (eg, a first downlink data stream and/or a second downlink data stream and/or a first upstream data stream and/or a second upstream data stream), and the like.
  • Receiving data eg, a first downlink data stream and/or a second downlink data stream and/or a first upstream data stream and/or a second upstream data stream
  • the processing unit 503 is configured to perform other steps than the steps of transmitting and receiving the AN CP functional entity and/or the AN UP functional entity in FIG. 2 to FIG. 4, for example, confirming the bearer of the second downlink data flow mapping and the like.
  • the actions performed by the processing unit 503 can be implemented by a processor, and the actions performed by the transmitting unit 501 and the receiving unit 502 can be implemented by the transceiver under the control of the processor.
  • FIG. 6 is a schematic block diagram of a user equipment 600 according to an embodiment of the present invention. It should be understood that the user equipment 600 is capable of performing the various steps performed by the UE in the methods of FIGS. 2 through 4, and to avoid repetition, it will not be described in detail herein.
  • User equipment 600 includes:
  • the sending unit 601 is configured to perform the sending step of the UE in FIG. 2 to FIG. 4, for example, sending an acknowledgement message and/or sending data (for example, a first uplink data stream and/or a second uplink data stream).
  • the receiving unit 602 is configured to perform the receiving step of the UE in FIG. 2 to FIG. 4, for example, receiving information and/or receiving data (such as a first downlink data stream and/or a second downlink data stream).
  • the processing unit 603 is configured to perform other steps than the steps of the UE in FIG. 2 to FIG. 4 except for transmitting and receiving, for example, mapping data to a bearer (for example, mapping an uplink data stream to an uplink bearer).
  • mapping data for example, mapping an uplink data stream to an uplink bearer.
  • processing unit 603 can be implemented by a processor, and the actions performed by the transmitting unit 601 and the receiving unit 602 can be implemented by the transceiver under the control of the processor.
  • FIG. 7 is a block diagram showing the schematic structure of an apparatus of one embodiment of the present invention.
  • the apparatus 700 is capable of performing the various steps performed by the AN CP functional entity and/or the AN UP functional entity in the methods of FIGS. 2 through 4.
  • Apparatus 700 includes a memory 701, a transceiver 702, and a processor 703.
  • the memory 701 is used to store programs.
  • the transceiver 702 is configured to communicate with other devices, such as a UE.
  • the processor 703 is connected to the memory 701 and the transceiver 702, respectively, for executing programs in the memory 701.
  • device 700 is caused to perform the various actions performed by the AN CP functional entity and/or the AN UP functional entity of Figures 2 through 4.
  • FIG. 8 is a block diagram showing the schematic structure of an apparatus of one embodiment of the present invention.
  • the apparatus 800 is capable of performing the various steps performed by the UE in the methods of FIGS. 2 through 4.
  • Apparatus 800 includes a memory 801, a transceiver 802, and a processor 803.
  • the memory 801 is configured to store a program.
  • the transceiver 802 is configured to communicate with other devices, such as AN CP functional entities and/or AN UP functional entities.
  • the processor 803 is connected to the memory 801 and the transceiver 802, respectively, for executing a program in the memory 801. When the program in the memory 801 is executed, the device 8 is caused to perform the respective actions performed by the UE in FIGS. 2 to 4.
  • the processor of the foregoing device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the described systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division, and the actual implementation may have another division manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be ignored, or not carried out.
  • 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, or an electrical, mechanical or other form of connection.
  • each functional unit in each embodiment of the present invention 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 above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • When implemented in hardware it may be implemented in whole or in the form of a processor or integrated logic circuit.
  • When implemented in software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

本发明实施例公开了一种无线通信方法、用户设备、接入网设备和网络系统。该方法包括：接入网设备接收核心网设备以流的形式发送的第一下行数据流；所述接入网设备向用户设备发送信息，所述信息包括所述第一下行数据流与下行承载的映射关系。通过该方法保障了接入网下的数据传输。

Description

无线通信方法、用户设备、接入网设备和网络系统 技术领域
本发明实施例涉及无线网络通信领域，尤其涉及一种无线通信方法、用户设备、接入网设备和网络系统。
背景技术
第三代合作伙伴计划(Third Generation Partnership Project，简称3GPP)组织的第二系统架构工作组(SA2)定义了一种基于流的数据传输方法。该传输方法具体包括：当下行数据包到达核心网用户面(Core Network User Plane，简称CN UP)功能实体时，CN UP功能实体通过流的形式将该数据包发送给接入网。接入网(AN)再通过流的形式将该数据包发送给用户设备(UE)。
当前3GPP的接入网工作组定义了一种和3GPP系统架构组不同的架构，3GPP接入网工作组可能会在接入网保留承载(bearer)。在这种架构下，基于流的数据传输方法无法简单重用，以保障接入网下的数据传输。
发明内容
本发明实施例提供一种无线通信方法、用户设备、接入网设备和网络系统，旨在保障接入网下的数据传输。
第一方面，本发明实施例提供一种无线通信方法，包括如下步骤：接入网设备接收核心网设备以流的形式发送的第一下行数据流；所述接入网设备向用户设备发送信息，所述信息包括所述第一下行数据流与下行承载的映射关系。在接入网保留承载的情况下，接入网设备向用户设备发送第一下行数据流与下行承载的映射关系，通过该映射关系即可确定发送数据流时应使用的承载，保障了接入网下的数据传输。
在一个可能的设计中，所述方法还包括：所述接入网设备通过所述下行承载向所述用户设备发送第一下行数据流。所述接入网设备接收所述用户设备通过上行承载发送的第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。通过下行数据流与下行承载的映射关系，可以确定传输相应上行数据流时所使用的上行承载。实现了服务质量(QoS)的保障。进一步地，通过直接接收映射关系，可以避免在每个数据包中添加指示，减少空口的数据传输开销。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。通过上述方案，在同一业务/会话的上行与下行数据流使用不同ID的场景下，仍可以保障接入网下的数据传输。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括： 所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述接入网设备接收的所述第一下行数据流包括反射服务质量标识RQI，所述接入网设备发送的所述第一下行数据流不包括所述RQI。利用核心网设备与接入网设备之间一般使用有线连接的特点，在数据流中使用反射服务质量标识，可以减少信令交互，从而缩短传输时延。而在接入网设备发送的所述第一下行数据流不包括所述RQI，可以减少空口开销，提高传输效率。
第二方面，本发明实施例提供一种无线通信方法，包括如下步骤：用户设备接收信息，所述信息包括第一下行数据流与下行承载的映射关系。所述用户设备通过所述下行承载接收所述第一下行数据流。
在一个可能的设计中，所述方法还包括：所述用户设备通过上行承载发送第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
第三方面，本发明实施例提供一种网络设备。该网络设备包括接收单元和发送单元。所述接收单元配置用于接收核心网设备以流的形式发送的第一下行数据流。所述发送单元配置用于向用户设备发送信息，所述信息包括所述第一下行数据流与下行承载的映射关系。
在一个可能的设计中，所述发送单元还配置用于：通过所述下行承载向所述用户设备发送第一下行数据流。所述接收单元还配置用于：接收所述用户设备通过上行承载发送的第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述接收单元接收的所述第一下行数据流包括反射服务质量标识RQI，所述发送单元发送的所述第一下行数据流不包括所述RQI。
第四方面，本发明实施例提供一种用户设备。该用户设备包括接收单元。所述接收单元被配置用于接收信息，所述信息包括第一下行数据流与下行承载的映射关系。所述接收单元还被配置通过所述下行承载接收所述第一下行数据流。
在一个可能的设计中，该用户设备还包括发送单元。所述发送单元被配置用于通过上行承载发送第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
第五方面，本发明实施例提供一种无线通信方法，包括如下步骤：用户设备接收信息，所述信息包括数据流与承载的映射规则。所述用户设备使用上行承载发送第一上行数据流；其中，所述上行承载是根据所述映射规则确定的。在接入网保留承载的 情况下，用户设备接收数据流与承载的映射规则，通过该规则即可确定发送数据流时应使用的承载，保障了接入网下的数据传输。进一步地，通过直接接收数据流与承载映射规则，可以避免在每个数据包中添加指示，减少空口的数据传输开销。
在一个可能的设计中，所述方法还包括：所述用户设备通过下行承载接收第一下行数据流。所述数据流与承载的映射规则，包括：所述第一下行数据流与所述下行承载的映射关系。所述上行承载是根据所述映射规则确定的，包括：如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。通过下行数据流与承载的映射关系，可以确定传输相应上行数据流时所使用的上行承载。保障了接入网下的数据传输，并进一步可以在上行数据传输时，通过承载实现了服务质量(QoS)的保障。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述方法还包括：所述用户设备通过下行承载接收第二下行数据流。所述用户设备使用所述上行承载发送第二上行数据流，所述第二上行数据流与所述第二下行数据流是相对应的。所述数据流与承载的映射规则，还包括：所述第二下行数据流与所述下行承载的映射关系。
在一个可能的设计中，所述方法还包括：所述第一下行数据流在核心网设备与接入网设备之间传输时包括反射服务质量标识。利用核心网设备与接入网设备之间一般使用有线连接的特点，在数据流中使用反射服务质量标识，可以减少信令交互，从而缩短传输时延。
在一个可能的设计中，所述用户设备接收信息，包括：所述用户设备通过RRC信令的方式从接入网设备接收所述信息。
第六方面，本发明实施例提供一种无线通信方法，包括如下步骤：接入网设备发送信息，所述信息包括数据流与承载的映射规则。所述接入网设备接收用户设备通过上行承载发送的第一上行数据流，其中，所述上行承载是根据所述映射规则确定的。
在一个可能的设计中，所述方法还包括：所述接入网设备通过下行承载向所述用户设备发送第一下行数据流。所述数据流与承载的映射规则，包括：所述第一下行数 据流与所述下行承载的映射关系。所述上行承载是根据所述映射规则确定的，包括：如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在一个可能的设计中，所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述方法还包括：所述接入网设备通过下行承载向所述用户设备发送第二下行数据流。所述接入网设备使用所述上行承载接收第二上行数据流，所述第二上行数据流与所述第二下行数据流是相对应的。所述数据流与承载的映射规则，还包括：所述第二下行数据流与所述下行承载的映射关系。
在一个可能的设计中，所述方法还包括：所述接入网设备接收所述第二下行数据流，所述第二下行数据流包括RQI。
在一个可能的设计中，所述方法还包括：所述接入网设备接收所述第一下行数据流，所述第一下行数据流包括反射服务质量标识RQI。
在一个可能的设计中，所述接入网设备发送信息，包括：接入网设备通过RRC信令的方式向所述用户设备发送所述信息。
第七方面，本发明实施例提供一种无线通信方法，包括如下步骤：用户设备从下行承载上接收下行数据流，所述下行数据流包括反射服务质量标识RQI；所述用户设备使用上行承载发送上行数据流。其中，所述上行数据流与所述下行数据流是相对应，所述上行承载是根据所述下行承载确定的。用户设备可以通过反射服务质量标识RQI获取数据流与承载的映射关系，可以减少信令交互。适用于一些具有不频繁小包数据特征的业务。
在一个可能的设计中，所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的服务质量QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述上行数据流与所述下行数据流是相对应的，包括：所述上行数据流的ID与所述下行数据流的ID相同，或者所述上行数据流与所述下行数据流属于同一业务流，或者所述上行数据流与所述下行数据流属于同一会话流。
第八方面，本发明实施例提供一种无线通信方法，包括如下步骤：接入网设备通过下行承载发送下行数据流，所述下行数据流包括反射服务质量标识RQI；所述接入网设备使用上行承载接收上行数据流。其中，所述上行数据流与所述下行数据流是相对应，所述上行承载是根据所述下行承载确定的。
在一个可能的设计中，所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的服务质量QoS属性与所述下行承载的QoS属性相同。
在一个可能的设计中，所述上行数据流与所述下行数据流是相对应的，包括：所述上行数据流的ID与所述下行数据流的ID相同，或者所述上行数据流与所述下行数据流属于同一业务流，或者所述上行数据流与所述下行数据流属于同一会话流。
在一个可能的设计中，所述方法还包括：所述接入网设备以流的方式接收核心网设备发送的所述下行数据流；所述接入网设备以流的方式向所述核心网设备发送所述上行数据流。
再一方面，本发明实施例提供一种网络设备，包括处理器、存储器以及收发器。所述处理器与存储器以及收发器分别耦合。所述存储器用于存储程序指令，所述处理器通过执行存储在所述存储器内的程序指令使得所述网络设备执行上述第一方面或第六方面或第八方面的方法。
再一方面，本发明实施例提供一种用户设备，包括处理器、存储器以及收发器。所述处理器与存储器以及收发器分别耦合。所述存储器用于存储程序指令，所述处理器通过执行存储在所述存储器内的程序指令使得所述用户设备执行上述第二方面或第五方面或第七方面的方法。
再一方面，本发明实施例提供了一种用户设备。所述用户设备包括用于实现上述第五方面所述的方法的单元，例如发送单元、接收单元。或者所述用户设备包括用于实现上述第七方面所述的方法的单元。
再一方面，本发明实施例提供了一种接入网设备。所述接入网设备包括用于实现上述第六方面所述的方法的单元，例如发送单元、接收单元。或者所述用户设备包括用于实现上述第八方面所述的方法的单元。
再一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的用户设备和接入网设备。
再一方面，本发明实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
再一方面，本发明实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述各方面所涉及的方法。
附图说明
图1是根据本专利申请一个实施例，一种无线通信系统的示意图。
图2是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图3是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图4是根据本专利申请另一个实施例，一种通信方法的交互示意图。
图5为根据本发明实施例又一个实施例的网络设备的结构示意图。
图6为根据本发明实施例又一个实施例的用户设备的结构示意图。
图7为根据本发明实施例又一个实施例的网络设备的结构示意图。
图8为根据本发明实施例又一个实施例的用户设备的结构示意图。
具体实施方式
本专利申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样的术语在适当情况下可以互换，以便本文描述的本发明实施例能够以在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本文中术语“系统”和“网络”可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本文中术语“连接”可以是直接连接或间接连接。“功能实体”是指实现某个功能的实体，其包含了执行该功能相应的硬件结构和/或软件模块。本文中术语“发送”可以是直接发送或通过其他网元间接发送。本文中术语“接收”可以是直接接收或通过其他网元间接接收。
本文中术语“承载”是网络为了实现差异化的数据传递，而建立的和QoS相对应的数据传输通道。一个承载可以以数据隧道的方式实现，例如在数据传输的源节点和目的节点之间建立的基于GPRS隧道协议(GPRS Tunneling Protocol；简称GTP)的逻辑数据传输通道等。一个承载上的所有数据流在QoS控制上不做区分，拥有相同的数据包转发处理方式，并按照传输通道所对应的传输协议进行数据传输。
本文中术语“数据流”是指UE或网络生成的和某个业务相关的数据流。QoS流可以是数据流的一种形式。业务流也可以是数据流的一种形式。
为了把数据传递到对端，需要经网络进行传输。网络将高层的数据转化成适合在网络传输的形式。基于流的传输方式是指，对于同一个流内的数据包，网络使用相同的数据包转发方式(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控制和区分粒度。一个承载可以映射一个或多个数据流，以承载的方式进行传输可以减少信令开销。映射到一个承载上的数据流数量越多，网络需要建立的承载数量越少，相应的信令开销也越小。
本文中术语“IP流”是指UE或外部数据网络(DN)生成的高层(MAC层以上)和某个业务相关的数据，该数据可以基于IP协议，也可以基于非IP(non-IP)协议。为了 实现区别化的QoS服务，网络根据不同IP流对应的QoS需求，把IP流映射到QoS流，不同的QoS流对应不同的数据包对待(data packet treatment)方式。
本文中术语“QoS规则”是基于运营商策略根据应用需求和QoS参数制定的一套信息集合，用来检测数据流并定义其相关的QoS参数，以及确定数据流的传输方式。数据流的传输方式可以包括以流的方式或者以承载的方式进行传输。以流的方式传输可以是将数据流的数据包按照流的方式进行传输。以承载的方式传输可以是把一个或多个数据流映射到一个承载上进行传输。
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规则来确定是否进行相应操作。
本文中术语“流优先级指示(Flow Priority Indicator，简称FPI)”是指在处理流对应的数据时，针对每个流的处理优先级。例如，FPI可以对应到拥塞时网络对流的调度优先级。FPI可以是类似一个QCI的标识。
本文中术语反射QoS(Reflective QoS)是指上行数据传输QoS是下行数据传输QoS的反射。其基本思想是根据下行数据传输的QoS信息来确定出上行数据传输的QoS信息。
本文中术语“反射QoS指示”(Reflective QoS Indication，RQI)是用于指示是否使用反射QoS的方式进行数据传输的指示信息。如果下行数据中包括RQI，则可以用来指示相应的上行数据传输采用和下行数据传输一致的QoS控制方式。RQI可以适用于单个数据流或多个数据流的聚合。
下面以具体的实施例对本发明实施例的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
图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)会话。PF会生成NAS层过滤器，该过滤器用于指示如何把IP流映射到数据流。PF把该过NAS层滤器发送给CN CP功能实体和CN UP功能实体，CN CP功能实体通过NAS信令把该NAS层过滤器经由AN CP功能实体转发给UE。
202、数据网络将第一下行IP数据包发送给CN UP功能实体。CN UP功能实体接收该第一下行IP数据包。IP数据包可以IP流的形式传输。具体地，第一下行IP数据包可以是第一下行IP流。
203、CN UP功能实体对第一下行IP流进行处理，把第一下行IP流映射到第一下行数据流。CN UP功能实体发送第一下行数据流给AN UP功能实体。AN UP功能实体接收该第一下行数据流。
该第一下行数据流对应一个FPI，记为FPI_1。可选地，CN UP功能实体还可以为该第一下行数据流分配流标识(ID)，记为Flow ID_1。CN UP功能实体在第一下行数据流的数据包头中增加数据流的信息。数据流的信息可以包括：FPI、流标识。可选地，CN UP功能实体还可以在第一下行数据流的数据包头中增加RQI。这样，AN UP功能实体就可以清楚在传输对应的上行数据流时就可以按照该第一下行数据流的QoS属性进行。
第一下行IP流映射到第一下行数据流可以采用基于模板过滤的方式。例如，定义一个参数组，并为该组中每个参数设定一个值或取值范围，当数据包的相关参数与预先设定的值相同，或落在预先设定的取值范围之内时，可以将该数据包映射到对应数据流。作为一个例子，参数组可以是IP五元组。IP五元组包括目的IP地址、源IP地址、目的端口号、源端口号和协议类型。
204、AN UP功能实体接收第一下行数据流之后，AN UP功能实体检查是否存在可以映射的承载。例如，可以根据第一下行数据流的QoS属性检查是否存在可以映射的承载。如果没有，则AN UP功能实体向AN CP功能实体发起承载建立请求，AN CP功能实体接收承载建立请求。承载建立请求中包含QoS信息。例如，承载建立请求中可以包含第一下行数据流的QoS信息，比如，FPI。承载建立请求中可以还包含第一下行数据流的流ID。
205、AN CP功能实体发起在UE和AN UP功能实体之间建立承载。AN CP功能实体 根据承载建立请求中包含的QoS信息，发起在UE和AN UP之间建立承载。在本实施例中，为方便描述，步骤205中所建立的承载可以称为下行承载。
在下行承载的建立过程中，AN CP功能实体生成一个承载标识，该标识可以用来识别下行承载。AN CP功能实体为该承载配置QoS参数，比如QoS等级。
上文介绍了根据下行数据流触发建立承载。值得注意的是，承载也可预先建立，或者承载也可以是默认承载。该下行承载可以是单向的。或者该下行承载也可以是双向的，即也可用于上行数据传输，即也是上行承载。
206、承载建立完成之后，AN CP功能实体向UE发送信息，该信息包括数据流与承载的映射规则。例如，第一下行数据流与下行承载的映射关系。该消息可以通过无线资源控制(Radio Resource Control，RRC)信令的形式发送。UE接收该信息。数据流与承载的映射规则将用于UE在发送上行数据时确定数据流到承载的映射。
数据流与承载的映射规则的具体形式可有多种。例如，第一下行数据流与下行承载的映射关系，具体可以包括：第一下行数据流的标识ID与下行承载的ID的对应关系。或者第一下行数据流与下行承载的映射关系包括：第一下行数据流的服务质量QoS属性与下行承载的ID的对应关系。数据流与承载的映射规则，还可以直接包括上行数据流与上行承载的映射关系，具体可以包括：上行数据流的标识ID与上行承载的ID的对应关系。或者上行数据流的服务质量QoS属性与上行承载的ID的对应关系。
207、UE向AN CP功能实体发送确认消息，确认UE已收到包括数据流与承载的映射规则的消息。AN CP功能实体接收该确认消息。
208、AN CP功能实体向AN UP功能实体发送承载建立响应，AN UP功能实体接收承载建立响应。承载建立响应中包含承载的信息。承载的信息包括：承载标识和承载的QoS信息。承载的QoS信息包括承载所支持的QoS等级，例如QCI。
值得注意的是，步骤208也是可选的。例如，在步骤205不是步骤204所触发的情况下，步骤208也可省略。
209、AN UP功能实体把第一下行数据流映射到下行承载，通过下行承载把第一下行数据流发送给UE。UE接收该第一下行数据流。在下行承载上传输的第一下行数据流无需包括RQI和FPI。可选地，在下行承载上传输的第一下行数据流可以包括数据流的ID。这样，如果下行承载上传输的数据流有2个或2个以上时，也可以正确区分不同的数据流。
值得注意的是，步骤209也是可选地，例如，步骤202与203未发生的情况下，也无需进行步骤209。
210、在UE需要发送第一上行数据流时，UE把第一上行数据流映射到上行承载。上行承载是根据所述映射规则确定的。
所述数据流与承载的映射规则，包括：所述第一下行数据流与所述下行承载的映射关系。所述上行承载是根据所述映射规则确定的，包括：如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一种情形下，第一下行数据流与下行承载的映射关系，包括：第一下行数据流的标识ID与下行承载的ID的对应关系。第一上行数据流与第一下行数据流是相对应的，包括：第一上行数据流的ID与第一下行数据流的ID相同，或者所述第一上行数 据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。
所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在另一种情形下，第一下行数据流与下行承载的映射关系，包括：第一下行数据流的服务质量QoS属性与下行承载的ID的对应关系。所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
值得注意的是，上行承载与下行承载可以相同，也可以不同。如果上行承载是双向承载，则下行承载与上行承载可以是相同的。
上行承载还可以是一个新的承载。例如，在下行承载是一个单向承载、或者上、下行数据需要在不同的承载上传输。UE可以向AN CP功能实体发送承载建立请求，触发AN CP功能实体建立上行承载，该上行承载和下行承载具有相同或对应的QoS属性。
UE通过非接入(Non-access stratum，简称NAS)层映射把第一上行IP流映射到第一上行数据流。再进一步通过接入(Access Stratum，简称AS)层映射把第一上行数据流映射到上行承载。
211、UE使用上行承载向AN UP功能实体发送该第一上行数据流。AN UP功能实体通过下行承载接收该第一上行数据流。
212、AN UP功能实体对从下行承载上接收的第一上行数据流进行解映射，AN UP功能实体可以在第一上行数据流的数据包包头中增加对应的流优先级指示(FPI)。AN UP功能实体还可以在第一上行数据流的数据包包头中增加流ID。AN UP功能实体通过流的方式把第一上行数据流传输给CN UP功能实体。
213、CN UP功能实体把接收到的第一上行数据流中的第一上行数据通过IP数据包的形式发送给数据网络。
值得注意的是，图2中虚线所示意的步骤是可选的。当然，这也不排除实线所示步骤也可能是可选的。
在图2所示实施例中，在核心网内部以及核心网与接入网的接口使用基于流的数据传输方式，并使用用户面传递QoS控制信息，在接入网(包括空口)使用基于承载的数据传输方式，并使用控制面传递QoS控制信息。
图3是根据本专利申请另一个实施例，一种通信方法的交互示意图。如图3所示，该方法包括如下步骤：
301、与201基本相同，可以参照201，不再赘述。
302、在UE和AN UP功能实体之间建立承载。该行承载可以是一个默认承载，即无需由数据业务触发。该承载也可能是由传输第一下行数据流而触发建立的，此种情形下承载的建立过程可以参考图2所示实施例中的描述。该承载可以是单向的，例如是上行承载或下行承载。该承载也可以是双向的，兼具上行传输和下行传输的功能， 例如上行承载和下行承载合一。
303、数据网络将第二下行IP数据包发送给CN UP功能实体。CN UP功能实体接收该第二下行IP数据包。IP数据包可以IP流的形式传输。具体地，第二下行IP数据包可以是第二下行IP流。
304、CN UP功能实体对第二下行IP流进行处理，把第二下行IP流映射到第二下行数据流。CN UP功能实体把第二下行数据流发送给AN UP功能实体。AN UP功能实体接收该第二下行数据流。具体地，CN UP功能实体以流的形式把第二下行数据流发送给AN UP功能实体。
该第二下行数据流对应一个FPI，记为FPI_2。可选地，CN UP功能实体还可以为该第二下行数据流分配流标识(ID)，记为Flow ID_2。CN UP功能实体在第二下行数据流的数据包头中增加数据流的信息。数据流的信息可以包括：FPI、流标识。可选地，CN UP功能实体还可以在第二下行数据流的数据包头中增加RQI。这样，AN UP功能实体就可以清楚在传输对应的上行数据流时就可以按照该第二下行数据流的QoS属性进行。
第二下行IP流映射到第二下行数据流可以采用基于模板过滤的方式，具体可以参考前面的描述。
305、AN UP功能实体接收第二下行数据流之后，AN UP功能实体检查是否存在可以映射的承载。例如可以根据第二下行数据流的QoS属性检查是否存在可以映射的承载。AN UP功能实体确认可以将第二下行数据流映射到下行承载。该下行承载可以是步骤302中所建立的承载。如果之前确定了第一下行数据流映射到该下行承载，即第一下行数据流和第二下行数据流都可以映射到该下行承载。
306、AN UP功能实体向AN CP功能实体发送信息，该信息包括数据流与承载的映射规则。
数据流与承载的映射规则的具体形式可有多种。例如，第二下行数据流与下行承载的映射关系，具体可以包括：第二下行数据流的标识ID与下行承载的ID的对应关系。或者第二下行数据流与下行承载的映射关系包括：第一下行数据流的服务质量QoS属性与下行承载的ID的对应关系。数据流与承载的映射规则，还可以直接包括上行数据流与上行承载的映射关系，具体可以包括：上行数据流的标识ID与上行承载的ID的对应关系。或者上行数据流的服务质量QoS属性与上行承载的ID的对应关系。
307、AN CP功能实体向UE发送信息，该信息包括数据流与承载的映射规则。UE接收该消息。该消息可以通过无线资源控制(Radio Resource Control，RRC)信令的形式发送。UE接收该信息。数据流与承载的映射规则将用于UE在发送上行数据时确定数据流到承载的映射。如果之前AN CP功能实体向UE发送过包括数据流与承载的映射规则的消息，则步骤307中的消息可以是更新消息，只要更新第二下行数据流与下行承载的映射关系即可。当然，该消息也可以是单独的消息。
308、UE向AN CP功能实体发送确认消息，确认UE已收到包括数据流与承载的映射规则的消息。AN CP功能实体接收该确认消息。
309、AN CP功能实体向AN UP功能实体发送该确认消息。AN UP功能实体接收该确认消息。
310、AN UP功能实体把第二下行数据流映射到下行承载，并通过下行承载把第二下行数据流发送到UE。在下行承载上传输的第二下行数据流无需包括RQI和FPI。如果AN UP功能实体也需传输其他下行数据流(例如，第一下行数据流)，并且该其他下行数据流可以映射到下行承载时，则AN UP功能实体也把其他下行数据流映射到下行承载，并通过下行承载发送这些其他下行数据流。如果映射到下行承载上的下行数据流有2个或2个以上的情形下，下行承载中传输的下行数据流的数据要包含各自的流ID信息。
311、在UE需要向接入网设备发送第二上行数据流时，UE把第二上行数据流映射到上行承载。上行承载是根据所述映射规则确定的。
所述数据流与承载的映射规则，包括：所述第二下行数据流与所述下行承载的映射关系。所述上行承载是根据所述映射规则确定的，包括：如果所述第二上行数据流与所述第二下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
在一种情形下，第二下行数据流与下行承载的映射关系，包括：第二下行数据流的标识ID与下行承载的ID的对应关系。第二上行数据流与第二下行数据流是相对应的，包括：第二上行数据流的ID与第二下行数据流的ID相同，或者所述第二上行数据流与所述第二下行数据流属于同一业务流，或者所述第二上行数据流与所述第二下行数据流属于同一会话流。
所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
在另一种情形下，第二下行数据流与下行承载的映射关系，包括：第二下行数据流的服务质量QoS属性与下行承载的ID的对应关系。所述第二上行数据流与所述第二下行数据流是相对应的，包括：所述第二上行数据流的QoS属性与所述第二下行数据流的QoS属性相同，或者所述第二上行数据流与所述第二下行数据流属于同一业务流，或者所述第二上行数据流与所述第二下行数据流属于同一会话流。所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
值得注意的是，上行承载与下行承载可以相同，也可以不同。如果上行承载是双向承载，则下行承载与上行承载可以是相同的。
上行承载还可以是一个新的承载。例如，在下行承载是一个单向承载、或者上、下行数据需要在不同的承载上传输。UE可以向AN CP功能实体发送承载建立请求，触发AN CP功能实体建立上行承载，该上行承载和下行承载具有相同或对应的QoS属性。
可选地，如果UE还有其他上行数据流(例如第一上行数据流)也需发送，根据数据流与承载的映射规则，该其他上行数据流也可映射到该上行承载时，UE也把这些其他上行数据流映射到该上行承载。
312、UE通过上行承载向AN UP功能实体发送第二上行数据流，AN UP功能实体接收该第二上行数据流。可选地，UE还可以通过上行承载向AN UP功能实体发送第一上行数据流，AN UP功能实体接收该第一上行数据流。
313、AN UP功能实体对从下行承载上接收的上行数据流进行解映射，AN UP功能实体在上行数据流的数据包包头中增加对应的流优先级指示(FPI)。AN UP功能实体 还可以在上行数据流的数据包包头中增加流ID。AN UP功能实体通过流的方式把第二上行数据流传输给CN UP功能实体。CN UP功能实体接收该第二上行数据流。可选地，AN UP功能实体通过流的方式把第一上行数据流传输给CN UP功能实体。CN UP功能实体接收该第一上行数据流。
314、CN UP功能实体把接收到的上行数据流中的上行数据通过IP数据包发送给数据网络。具体地，CN UP功能实体把接收到的第二上行数据流中的上行数据通过IP数据包发送给数据网络。可选地，CN UP功能实体把接收到的第一上行数据流中的上行数据通过IP数据包发送给数据网络。
在图2和图3所示实施例中，通过信令的方式将承载和数据流的映射规则发送给UE，UE根据该映射规则确定传输上行数据流时所使用的承载。这可以节省数据面的传输开销，节约空口开销。可以大幅减少数据包包头的负载，有效提高空口的有效数据传输效率。
图4是根据本专利申请另一个实施例，一种通信方法的交互示意图。如图4所示，该方法包括如下步骤：
401-404、与301-304基本相同，可以参照301-304，不再赘述。
405、AN UP功能实体接收第二下行数据流之后，确定使用反射QoS的方式进行数据传输。
AN UP功能实体可以自行确定使用反射QoS的方式。AN UP功能实体也可以向AN CP功能实体请求下行数据流的传递方式，AN CP功能实体在确定使用反射QoS的方式之后告知AN UP功能实体。
AN UP功能实体检查是否存在可以映射的承载，例如可以根据第二下行数据流的QoS属性检查，确认可以将第二下行数据流映射到下行承载。如果之前确定了第一下行数据流映射到下行承载，则第一下行数据流和第二下行数据流都可以映射到下行承载。
406、AN UP功能实体把第二下行数据流映射到下行承载，并通过下行承载把第二下行数据流的数据包发送到UE。第二下行数据流的数据包括RQI。如果AN UP功能实体也需传输第一下行数据流，则AN UP功能实体也把第一下行数据流映射到下行承载。相应地，第一下行数据流的数据包括RQI。如果映射到下行承载上的下行数据流有2个或2个以上的情形下，下行承载中传输的下行数据流的数据要包含各自的流ID信息。
407、在UE需要向接入网设备发送与第二下行数据流相对应的第二上行数据流时，UE使用上行承载发送该第二上行数据流。第二下行数据流的数据包括RQI，第二上行数据流与第二下行数据流是相对应的，则上行承载是根据下行承载确定的。
所述上行数据流与所述下行数据流是相对应的，包括：所述上行数据流的ID与所述下行数据流的ID相同，或者所述上行数据流与所述下行数据流属于同一业务流，或者所述上行数据流与所述下行数据流属于同一会话流。
所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的服务质量QoS属性与所述下行承载的QoS属性相同。
如果上行承载上还传输其他上行数据流，例如第一上行数据流，则上行承载上传输的各个数据流需要包含各自的数据流ID信息。
408-410、与312-314基本相同，可以参照312-314，不再赘述。
在图所示实施例中，步骤402在404之前，即AN UP功能实体接收下行数据流时，已有合适的承载可供映射。当然，如果步骤405之前，还没有合适的承载可供映射，则AN UP功能实体可以向AN CP功能实体发送承载建立请求，以建立适当的承载。具体可以参考图2所示实施例中的步骤204、205和208。
在图4所示实施例中，通过反射QoS的方式将承载和数据流的映射规则发送给UE，UE根据RQI确定传输上行数据流时所使用的承载。这可以节信令面的传输开销，减小时延。
在本专利申请中，接入网设备可以决定采用信令的方式(图2或图3所示实施例)或反射QoS的方式(图4所示实施例)通知UE。例如，某些网络设备只支持特定的业务类型，比如，机器类通信业务(Machine Type Communication)或移动宽带业务(mobile broadband，MBB)。接入网设备可以根据其所支持业务类型的业务特征选择合适的方式。比如，机器类通信业务具有不频繁的小包，此类接入网设备可以采用反射QoS的方式。对于大数据的移动宽带业务，可以采用信令的方式，即使核心网已经使用了反射QoS的方式。对于一个接入网设备支持多种业务类型的场景，接入网设备也可以根据业务类型的业务特征选择合适的方式，此时当UE收到两种不同的映射规则时，可以采用一定的冲突避让机制，比如：信令比反射QoS具有更高的优先级。或者，反射QoS比信令具有更高的优先级。或者，以最新收到的映射规则为准，无论映射规则的获取是通过信令方式，还是通过反射QoS。
类似地，接入网设备还可以根据数据流的QoS属性选择合适的方式。比如，如果接入网设备接收核心网设备发送的数据流包括RQI，即核心网采用了反射QoS方法，则接入网设备采用反射QoS的方式，如果数据流不包括RQI，则接入网设备可以采用信令的方式。再比如，对于GBR的数据流，可以采用信令的方式；对于non-GBR的数据流，可以采用反射QoS的方式。
在本专利申请中，网络对数据的QoS控制包含两层QoS映射，分别是NAS层映射和AS层映射。NAS层映射可以IP流映射到数据流(例如，QoS流)。下行传输时，该操作由CN UP功能实体完成，上行传输时，该操作由UE完成。AS层映射可以把数据流映射到承载。下行传输使，该操作由AN UP完成，上行传输时，该操作由UE完成。
本专利申请可以适用于接入网和核心网拥有独立QoS控制功能的QoS架构，接入网可以更大程度上决定QoS控制方式，在满足业务QoS需求和提高网络资源利用效率之间取得平衡。
上文结合图1至图4详细描述了本发明实施例的方法，下文将结合图5至图8详细描述本发明实施例的用户设备、网络设备。
图5是本发明实施例的网络设备500的示意性框图。应理解，网络设备5能够执行图2至图4的方法中由接入网设备执行的各个步骤，为了避免重复，此处不再详述。网络设备500可以是接入网设备，其可以包括AN CP功能实体和/或AN UP功能实体。
发送单元501，配置用于执行图2至图4中AN CP功能实体和/或AN UP功能实体的发送步骤。例如，当网络设备500包括AN CP功能实体时，发送单元501可以被配置用于执行图2至图4中AN CP功能实体的发送步骤，具体可以包括发送信息和/或发 送承载建立响应。当网络设备500包括AN UP功能实体时，发送单元501可以被配置用于执行图2至图4中AN UP功能实体的发送步骤，具体可以包括发送承载建立请求和/或发送信息和/或发送数据(例如，第一下行数据流和/或第二下行数据流和/或第一上行数据流和/或第二上行数据流)等。
接收单元502，配置用于执行图2至图4中AN CP功能实体和/或AN UP功能实体的接收步骤。例如，当网络设备500包括AN CP功能实体时，接收单元502可以被配置用于执行图2至图4中AN CP功能实体的接收步骤，具体可以包括接收承载建立请求和/或接收UE发送的确认消息和/或接收AN UP发送的信息。当网络设备500包括AN UP功能实体时，接收单元502可以被配置用于执行图2至图4中AN UP功能实体的接收步骤，具体可以包括接收承载建立响应和/或接收确认消息和/或接收数据(例如，第一下行数据流和/或第二下行数据流和/或第一上行数据流和/或第二上行数据流)等。
处理单元503，配置用于执行图2至图4中AN CP功能实体和/或AN UP功能实体除了发送和接收的步骤之外的其他步骤，例如确认第二下行数据流映射的承载等。
应理解，该处理单元503执行的动作可以由处理器实现，而发送单元501和接收单元502执行的动作可以在处理器的控制下由收发器实现。
图6是本发明实施例的用户设备600的示意性框图。应理解，用户设备600能够执行图2至图4的方法中由UE执行的各个步骤，为了避免重复，此处不再详述。用户设备600包括：
发送单元601，配置用于执行图2至图4中UE的发送步骤，例如发送确认消息和/或发送数据(比如，第一上行数据流和/或第二上行数据流)等。
接收单元602，配置用于执行图2至图4中UE的接收步骤，例如接收信息和/或接收数据(比如，第一下行数据流和/或第二下行数据流)等。
处理单元603，配置用于执行图2至图4中UE除了发送和接收的步骤之外的其他步骤，例如映射数据到承载(比如，映射上行数据流到上行承载)等。
应理解，该处理单元603执行的动作可以由处理器实现，而发送单元601和接收单元602执行的动作可以在处理器的控制下由收发器实现。
图7是本发明一个实施例的装置的示意性结构框图。该装置700能够执行图2至图4的方法中由AN CP功能实体和/或AN UP功能实体执行的各个步骤。装置700包括：存储器701、收发器702和处理器703。存储器701用于存储程序。收发器702，用于和其他设备，例如UE，进行通信。处理器703与所述存储器701和所述收发器702分别相连，用于执行存储器701中的程序。当执行存储器701中的程序时，使装置700执行图2至图4中AN CP功能实体和/或AN UP功能实体执行的各个动作。
图8是本发明一个实施例的装置的示意性结构框图。该装置800能够执行图2至图4的方法中由UE执行的各个步骤。装置800包括：存储器801、收发器802和处理器803。存储器801，用于存储程序。收发器802用于和其他设备，例如AN CP功能实体和/或AN UP功能实体，进行通信。处理器803，与所述存储器801和所述收发器802分别相连，用于执行存储器801中的程序。当执行存储器801中的程序时，使装置8执行图2至图4中UE执行的各个动作。
应理解，在本发明实施例中，上述装置的处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所描述的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的。例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用硬件实现时，可以全部或部门地以处理器或集成逻辑电路的形式来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (11)

  1. 一种无线通信方法，其特征在于包括如下步骤：
    接入网设备接收核心网设备以流的形式发送的第一下行数据流；
    所述接入网设备向用户设备发送信息，所述信息包括所述第一下行数据流与下行承载的映射关系。
  2. 如权1所述的无线通信方法，其特征在于所述方法还包括：
    所述接入网设备通过所述下行承载向所述用户设备发送第一下行数据流；
    所述接入网设备接收所述用户设备通过上行承载发送的第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
  3. 如权利要求1或2所述的无线通信方法，其特征在于：
    所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系；
    所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流；
    所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
  4. 如权2所述的无线通信方法，其特征在于：
    所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系；
    所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流；
    所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
  5. 如权2-4任一所述的无线通信方法，其特征在于：
    所述接入网设备接收的所述第一下行数据流包括反射服务质量标识RQI，所述接入网设备发送的所述第一下行数据流不包括所述RQI。
  6. 一种无线通信方法，其特征在于包括如下步骤：
    用户设备接收信息，所述信息包括第一下行数据流与下行承载的映射关系；
    所述用户设备通过所述下行承载接收所述第一下行数据流。
  7. 如权6所述的无线通信方法，其特征在于所述方法还包括：
    所述用户设备通过上行承载发送第一上行数据流，其中，如果所述第一上行数据流与所述第一下行数据流是相对应的，所述上行承载是根据所述下行承载确定。
  8. 如权6或7所述的无线通信方法，其特征在于：
    所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的标识ID与所述下行承载的ID的对应关系；
    所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的ID与所述第一下行数据流的ID相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流；
    所述上行承载是根据所述下行承载确定，包括：所述下行承载与所述上行承载是同一个承载，或者所述下行承载的服务质量QoS属性与所述上行承载的QoS属性相同。
  9. 如权6或7所述的无线通信方法，其特征在于：
    所述第一下行数据流与所述下行承载的映射关系，包括：所述第一下行数据流的QoS属性与所述下行承载的ID的对应关系；
    所述第一上行数据流与所述第一下行数据流是相对应的，包括：所述第一上行数据流的QoS属性与所述第一下行数据流的QoS属性相同，或者所述第一上行数据流与所述第一下行数据流属于同一业务流，或者所述第一上行数据流与所述第一下行数据流属于同一会话流；
    所述上行承载是根据所述下行承载确定，包括：所述上行承载与所述下行承载是同一个承载，或者所述上行承载的QoS属性与所述下行承载的QoS属性相同。
  10. 一种网络设备，其特征在于包括：
    接收单元，配置用于接收核心网设备以流的形式发送的第一下行数据流；
    发送单元，配置用于向用户设备发送信息，所述信息包括所述第一下行数据流与下行承载的映射关系。
  11. 一种用户设备，其特征在于包括：
    接收单元，被配置用于接收信息，所述信息包括第一下行数据流与下行承载的映射关系；
    所述接收单元还被配置通过所述下行承载接收所述第一下行数据流。
PCT/CN2018/075187 2017-02-03 2018-02-03 无线通信方法、用户设备、接入网设备和网络系统 Ceased WO2018141278A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20212340.2A EP3852324B1 (en) 2017-02-03 2018-02-03 Wireless communication methods, user equipment and access network device
EP18748448.0A EP3562241B1 (en) 2017-02-03 2018-02-03 Wireless communication method and access network equipment
US16/527,860 US11489642B2 (en) 2017-02-03 2019-07-31 Wireless transmission using data flow bearers

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710063714.0 2017-02-03
CN201710063714.0A CN108390746B (zh) 2017-02-03 2017-02-03 无线通信方法、用户设备、接入网设备和网络系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/527,860 Continuation US11489642B2 (en) 2017-02-03 2019-07-31 Wireless transmission using data flow bearers

Publications (1)

Publication Number Publication Date
WO2018141278A1 true WO2018141278A1 (zh) 2018-08-09

Family

ID=63039249

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075187 Ceased WO2018141278A1 (zh) 2017-02-03 2018-02-03 无线通信方法、用户设备、接入网设备和网络系统

Country Status (4)

Country Link
US (1) US11489642B2 (zh)
EP (2) EP3852324B1 (zh)
CN (2) CN108390746B (zh)
WO (1) WO2018141278A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10917901B2 (en) * 2017-03-23 2021-02-09 Qualcomm Incorporated Quality of service configurations for radio bearers with multiple data flows
EP4436247B1 (en) * 2018-04-06 2025-11-26 Telefonaktiebolaget LM Ericsson (publ) Qos flow management over e1
CN110430599B (zh) * 2018-09-28 2020-10-16 华为技术有限公司 数据传输的方法和装置
WO2021226930A1 (en) * 2020-05-14 2021-11-18 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Qos control method for ue to access network through relay
CN114125950B (zh) * 2020-08-11 2025-10-03 中国移动通信有限公司研究院 数据传输方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080095037A1 (en) * 2006-10-20 2008-04-24 Samsung Electronics Co., Ltd. Apparatus and method for communicating control information in broadband wireless access system
CN101998668A (zh) * 2009-08-27 2011-03-30 中兴通讯股份有限公司 一种无线连接的gtp-u实体间传输数据的方法和装置
CN101998296A (zh) * 2009-08-17 2011-03-30 大唐移动通信设备有限公司 一种空口服务质量QoS的控制方法和系统
CN102045853A (zh) * 2009-10-22 2011-05-04 华为技术有限公司 一种信息传递方法、设备及系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557614A (zh) * 2008-04-10 2009-10-14 华为技术有限公司 一种实现传输服务质量保证的方法、装置及系统
CN101932102B (zh) * 2009-06-19 2013-01-23 华为技术有限公司 业务承载映射方法及通信设备
CN102625377B (zh) * 2011-01-31 2014-06-18 电信科学技术研究院 一种无线承载的建立方法、接入点设备、用户设备及系统
TWI626855B (zh) * 2012-04-27 2018-06-11 內數位專利控股公司 最佳化鄰近資料路徑設置方法及裝置
WO2013174422A1 (en) * 2012-05-23 2013-11-28 Nokia Siemens Networks Oy Methods, computer program products and apparatuses enabling symmetric bearer enforcement
CN103546984A (zh) * 2012-07-13 2014-01-29 北京三星通信技术研究有限公司 接入移动通信系统的方法及设备
EP2800417B1 (en) * 2013-04-29 2023-03-01 Alcatel Lucent End-to-End QoS when integrating trusted non-3GPP Access Networks and 3GPP Core Networks
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
EP3373534A4 (en) * 2015-11-05 2019-05-01 LG Electronics Inc. METHOD FOR TRANSMITTING / RECEIVING DATA IN A WIRELESS COMMUNICATION SYSTEM AND DEVICE FOR SUPPORTING THEREOF
CN107295575B (zh) * 2016-04-01 2020-02-28 中兴通讯股份有限公司 一种服务质量的控制方法和装置
EP3536095A1 (en) * 2016-11-04 2019-09-11 Telefonaktiebolaget LM Ericsson (publ) Reflective mapping of flows to radio bearers
JP2020507976A (ja) * 2017-02-01 2020-03-12 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて反映式サービス品質（ＱｏＳ）を行うための方法及びそのための装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080095037A1 (en) * 2006-10-20 2008-04-24 Samsung Electronics Co., Ltd. Apparatus and method for communicating control information in broadband wireless access system
CN101998296A (zh) * 2009-08-17 2011-03-30 大唐移动通信设备有限公司 一种空口服务质量QoS的控制方法和系统
CN101998668A (zh) * 2009-08-27 2011-03-30 中兴通讯股份有限公司 一种无线连接的gtp-u实体间传输数据的方法和装置
CN102045853A (zh) * 2009-10-22 2011-05-04 华为技术有限公司 一种信息传递方法、设备及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL: "Summary of Email Discussion on QoS Framework", 3GPP SA WG2 MEETING #116 , S2-163427, 15 July 2016 (2016-07-15), XP051121139 *
See also references of EP3562241A4 *

Also Published As

Publication number Publication date
US11489642B2 (en) 2022-11-01
CN108390746B (zh) 2022-05-10
EP3562241A1 (en) 2019-10-30
EP3852324A1 (en) 2021-07-21
EP3562241B1 (en) 2021-08-04
CN112653543A (zh) 2021-04-13
EP3852324B1 (en) 2024-04-03
US20190356453A1 (en) 2019-11-21
CN112653543B (zh) 2022-04-12
EP3562241A4 (en) 2020-01-08
CN108390746A (zh) 2018-08-10

Similar Documents

Publication Publication Date Title
US10856341B2 (en) Wireless communication method, user equipment, and access network device
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
US11202338B2 (en) Session establishment method and apparatus
US11489642B2 (en) Wireless transmission using data flow bearers
JP2016531489A (ja) サービス層サウスバウンドインターフェースおよびサービスの質
JP2014521234A (ja) プロービングに基づくベアラ制御
US11044629B2 (en) Wireless communication method, user equipment, access network device, and core network device
WO2022110214A1 (zh) 通信方法及装置
US20200015114A1 (en) Method for reducing overhead of air interface data transmission
US12402029B2 (en) Communication method, apparatus, and system
CN116866981A (zh) 通信方法和装置
WO2014101505A1 (zh) 一种WLAN和分组核心网之间的QoS对齐的方法
WO2020169039A1 (zh) 一种策略管理的方法及装置
CN105682014B (zh) 通信方法与系统，以及接入网设备与应用服务器
CN110719611A (zh) 一种报文发送方法和装置
WO2022151107A1 (zh) 信号的发送和接收方法、装置和通信系统
CN103501513B (zh) 一种处理信令消息的方法及系统
CN116266904A (zh) 确定应用服务器的方法和装置
WO2017193344A1 (zh) 访问资源的方法、装置和系统
WO2019085888A1 (zh) 专有承载流的处理方法、装置及系统
WO2016150115A1 (zh) 一种承载建立方法、分组数据网关、服务网关及系统

Legal Events

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

Ref document number: 18748448

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018748448

Country of ref document: EP

Effective date: 20190722

NENP Non-entry into the national phase

Ref country code: DE