WO2019141239A1 - 通信方法、装置和*** - Google Patents
通信方法、装置和*** Download PDFInfo
- Publication number
- WO2019141239A1 WO2019141239A1 PCT/CN2019/072350 CN2019072350W WO2019141239A1 WO 2019141239 A1 WO2019141239 A1 WO 2019141239A1 CN 2019072350 W CN2019072350 W CN 2019072350W WO 2019141239 A1 WO2019141239 A1 WO 2019141239A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- path
- node
- qos flow
- bearer
- layer
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 88
- 238000004891 communication Methods 0.000 title claims abstract description 74
- 230000006978 adaptation Effects 0.000 claims abstract description 5
- 230000005540 biological transmission Effects 0.000 claims description 175
- 230000011664 signaling Effects 0.000 claims description 41
- 230000015654 memory Effects 0.000 claims description 19
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 claims 34
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 claims 34
- 238000010586 diagram Methods 0.000 description 35
- 238000013507 mapping Methods 0.000 description 17
- 230000003252 repetitive effect Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 8
- 230000009977 dual effect Effects 0.000 description 7
- 230000004913 activation Effects 0.000 description 3
- 230000003139 buffering effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
- H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- the present application relates to the field of communications and, more particularly, to communication methods, apparatus and systems.
- the master cell group (MCG) bearer In the long term evolution (LTE) dual link scenario, there are multiple bearer types. For example, the master cell group (MCG) bearer, the MCG split (split) bearer, the secondary cell group (SCG) bearer, and the SCG split bearer.
- MCG master cell group
- SCG secondary cell group
- the transmission paths supported by the protocol stacks corresponding to different bearers are different. For example, for a data packet mapped to an MCG bearer, it is transmitted through a primary base station path; a data packet mapped to an MCG split bearer may be transmitted through a primary base station path by means of a base station configuration, or transmitted through a secondary base station path or simultaneously through a primary base station. Path and secondary base station path transmission.
- Existing solutions support a path selection mechanism based on bearer granularity.
- 5G defines a framework based on quality of service (QoS) flow. How to manage the data transmission in the dual-link scenario based on the QoS flow framework and improve the quality of data transmission is an urgent problem to be solved in the industry.
- QoS quality of service
- the present application provides a communication method, apparatus and system, in order to improve communication efficiency.
- the first aspect provides a communication method, including: the node sends the first indication information to the terminal device, where the first indication information is used to indicate that the first QoS flow is transmitted by using the first bearer, where the node is a master node. Or a secondary node, the protocol stack corresponding to the first bearer supports transmitting a QoS flow by using a first path, where the first path passes a service data adaptation protocol (SDAP) layer of the primary node a protocol layer below the SDAP layer of the secondary node, or the first path passes the SDAP layer of the secondary node and a protocol layer below the SDAP layer of the primary node; the node passes the first bearer transmission station
- SDAP service data adaptation protocol
- the QoS flow may be transmitted through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, or may be transmitted through the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node.
- the flexibility of the QoS flow using the transmission path improves communication efficiency.
- the protocol stack corresponding to the first bearer further supports transmitting a QoS flow by using a second path, where the first path passes the SDAP layer of the primary node and the SDAP of the secondary node a protocol layer below the layer, where the second path is a path between the primary node and the terminal device; or the first path passes through an SDAP layer of the secondary node and below a SDAP layer of the primary node a protocol layer, where the second path is a path between the secondary node and the terminal device.
- the method further includes: the node sending path indication information to the terminal device, where the path indication information is used to indicate a path transmission mode of the first QoS flow, where the path transmission mode is Separately transmitting the first QoS flow using the first path, separately transmitting the first QoS flow using the second path, or jointly transmitting the first QoS using the first path and the second path flow.
- the QoS flow may be transmitted between the terminal device and the node by using one path, or the QoS flow may be transmitted by using two paths. It not only realizes centralized control and management of the radio access network based on QoS flow level, but also improves the flexibility of the communication system.
- the node sends path adjustment information to the terminal device, where the path adjustment information is used to indicate that the path transmission mode of the first QoS flow is changed.
- the path transmission mode of the QoS flow can be dynamically adjusted, and the transmission efficiency based on the QoS flow is improved.
- the path indication information is carried in any one of the following: radio resource control (RRC) layer signaling, SDAP layer signaling, and media access control (MAC). Layer signaling.
- RRC radio resource control
- SDAP Secure Digital
- MAC media access control
- the method further includes: the node sending configuration indication information to the terminal device, where the configuration indication information is used to indicate that the terminal device: if the first preset condition is met, use Transmitting, by the first path, the first QoS flow separately; or, if the second preset condition is met, separately transmitting the first QoS flow by using the second path; or, when the third preset is met In the case of a condition, the first QoS flow is jointly transmitted using the first path and the second path.
- the path transmission mode used by the QoS flow is indicated in a pre-configured manner, and the terminal device may select a path transmission mode of the QoS flow according to the preset condition indicated in the configuration indication information, thereby improving transmission efficiency based on the QoS flow.
- the node sends the repeated transmission indication information to the terminal device, where the repeated transmission indication information is used to indicate that the first path and the second path are used to repeatedly transmit the mapping to each other.
- the QoS flow of the first bearer is used to indicate that the first path and the second path are used to repeatedly transmit the mapping to each other.
- the repeated transmission mode of the QoS flow can be flexibly configured, and the transmission efficiency based on the QoS flow is improved.
- the method further includes: the node sending, to the terminal device, retransmission stop indication information, where the repeated transmission stop indication information is used to indicate to stop using the first path and the second path
- the QoS flows mapped to the first bearer are repeatedly transmitted to each other.
- the first QoS flow includes a sequence number of a header of a SDAP protocol data unit (PDU), where the sequence number is used to indicate the ordering of the SDAP PDU.
- PDU SDAP protocol data unit
- a sequence number is set in a frame header of a SDAP PDU included in the first QoS flow, so as to identify data packets transmitted in different paths, and improve QoS flow-based communication transmission efficiency.
- the first path passes the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, and the first path passes the SDAP layer of the primary node.
- the following protocol layer includes: the first path passes through the SDAP layer of the secondary node, and the PDCP layer of the primary node and a protocol layer below the PDCP layer.
- a second aspect of the present invention provides a communication method, including: receiving, by a terminal device, first indication information, where the first indication information is used to indicate that a first QoS flow is transmitted by using a first bearer, where the first bearer corresponds to a protocol.
- the stack supports transmitting the QoS flow by using the first path, where the first path passes the SDAP layer of the primary node and a protocol layer below the SDAP layer of the secondary node, or the first path passes the secondary node And a protocol layer below the SDAP layer of the primary node; the terminal device transmits the first QoS flow by using the first bearer.
- the QoS flow may be transmitted through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, or may be transmitted through the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node.
- the flexibility of the QoS flow using the transmission path improves communication efficiency.
- the protocol stack corresponding to the first bearer further supports transmitting a QoS flow by using a second path, where the first path passes the SDAP layer of the primary node and the SDAP of the secondary node a protocol layer below the layer, where the second path is a path between the primary node and the terminal device; or the first path passes through an SDAP layer of the secondary node and below a SDAP layer of the primary node a protocol layer, where the second path is a path between the secondary node and the terminal device.
- the method further includes: the terminal device receiving path indication information, where the path indication information is used to indicate a path transmission mode of the first QoS flow, where the path transmission mode is to use the
- the first QoS flow is separately transmitted by a path, the first QoS flow is separately transmitted using the second path, or the first QoS flow is jointly transmitted using the first path and the second path.
- the method further includes: the terminal device receiving path adjustment information, where the path adjustment information is used to indicate that the path transmission mode of the first QoS flow is changed.
- the path indication information is carried in any one of the following: RRC layer signaling, SDAP layer signaling, and MAC layer signaling.
- the method further includes: receiving, by the terminal device, configuration indication information, where the configuration indication information is used to indicate that the terminal device: when the first preset condition is met, using the first The path separately transmits the first QoS flow; or, if the second preset condition is met, the first QoS flow is separately transmitted using the second path; or, if the third preset condition is met And transmitting, by the first path and the second path, the first QoS flow.
- the method further includes: the terminal device receiving the repeated transmission indication information, where the repeated transmission indication information is used to indicate that the first path and the second path are mutually retransmitted and transmitted to the The first bearer's QoS flow.
- the method further includes: the terminal device receiving the repeated transmission stop indication information, where the repeated transmission stop indication information is used to indicate that the first path and the second path are repeatedly used to repeatedly transmit the mapping a QoS flow to the first bearer.
- the frame header of the SDAP protocol data unit PDU included in the first QoS flow includes a sequence number, where the sequence number is used to indicate the ordering of the SDAP PDU.
- the first path passes the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, and the first path passes the SDAP layer of the primary node.
- the protocol data convergence protocol PDCP layer of the secondary node and the protocol layer below the PDCP layer, or the first path passing the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node including: The first path passes through the SDAP layer of the secondary node and the PDCP layer of the primary node and a protocol layer below the PDCP layer.
- a node for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
- the node comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
- a terminal device for performing the method in any of the above possible implementations of the second aspect or the second aspect.
- the terminal device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
- a node comprising: a communication interface, a memory, and a processor.
- the memory is for storing instructions
- the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the performing causes the The processor performs the method of the first aspect or any possible implementation of the first aspect.
- a terminal device comprising: a communication interface, a memory, and a processor.
- the memory is for storing instructions
- the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and when the processor executes the instructions stored by the memory, the performing causes the The processor performs the method of the second aspect or any possible implementation of the second aspect.
- a communication system comprising the node of the above third aspect and the terminal device of the fourth aspect, or the communication system comprising the node and the sixth aspect of the fifth aspect above The terminal device described in the aspect.
- a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
- a ninth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or the second aspect of the second aspect.
- a chip for storing instructions that, when executed on a node, cause the chip to perform the method of the first aspect or any of the possible implementations of the first aspect.
- a chip that, when executed on a terminal device, causes the chip to perform the method of any of the possible aspects of the second aspect or the second aspect.
- FIG. 1 is a schematic diagram of a network architecture of an embodiment of the present application.
- FIG. 2 is a schematic structural diagram of a dual link scenario in the embodiment of the present application.
- FIG. 3 is a schematic diagram of an application scenario of a bearer type of the related art.
- FIG. 4 is a schematic diagram of a QoS flow transmission path in the related art.
- FIG. 5 is a schematic diagram of an application scenario of a bearer type according to an embodiment of the present application.
- FIG. 6 is a schematic diagram of an application scenario of a bearer type according to another embodiment of the present application.
- FIG. 7 is a schematic diagram of an application scenario of a bearer type according to another embodiment of the present application.
- FIG. 8 is a schematic diagram of a QoS flow transmission path according to an embodiment of the present application.
- FIG. 9 is a schematic diagram of a QoS flow transmission path according to still another embodiment of the present application.
- FIG. 10 is a schematic diagram of interaction of a communication method according to an embodiment of the present application.
- FIG. 11 is a schematic diagram of an application scenario of a bearer type according to another embodiment of the present application.
- FIG. 12 is a schematic diagram of a SDAP frame format according to an embodiment of the present application.
- FIG. 13 is a schematic diagram of a SDAP frame format according to still another embodiment of the present application.
- FIG. 14 is a schematic diagram of a SDAP frame format according to still another embodiment of the present application.
- 15 is a schematic diagram of a MAC layer signaling format of the present application.
- FIG. 16 is a schematic structural diagram of a node according to an embodiment of the present application.
- FIG. 17 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
- FIG. 18 is a schematic structural diagram of a node according to still another embodiment of the present application.
- FIG. 19 is a schematic structural diagram of a terminal device according to still another embodiment of the present application.
- GSM global system of mobile communication
- CDMA code division multiple access
- WCDMA wideband code division multiple access
- GPRS general packet radio service
- LTE long term evolution
- FDD LTE frequency division duplex
- TDD LTE Time division duplex
- UMTS universal mobile telecommunication system
- WiMAX worldwide interoperability for microwave access
- 5G future fifth generation
- 5G fifth generation
- NR new radio
- the terminal device in the embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile 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 User device.
- the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication.
- SIP session initiation protocol
- WLL wireless local loop
- PDA personal digital assistant
- a node for example, a primary node or a secondary node in the embodiment of the present application may be a device for communicating with a terminal device, and the node may be a global system of mobile communication (GSM) system or code division multiple access (
- GSM global system of mobile communication
- a base transceiver station (BTS) in a code division multiple access (CDMA) system may also be a node (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or may be an LTE system.
- GSM global system of mobile communication
- BTS code division multiple access
- CDMA code division multiple access
- NodeB, NB node
- WCDMA wideband code division multiple access
- the evolutional NodeB may be an LTE node, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the node may be a relay station, An access point, an in-vehicle device, a wearable device, and a base station in a future 5G network or a node in a future evolved PLMN network, for example, a new radio (NR) node.
- CRAN cloud radio access network
- NR new radio
- 5G will support various types of network deployments and application types. To meet the above requirements, 5G defines a framework based on quality of service (QoS) flows. The architecture of the QoS flow involved in the embodiment of the present application will be described below.
- QoS quality of service
- FIG. 1 is a schematic diagram of a possible network architecture 100 of an embodiment of the present application.
- Network architecture 100 is one possible implementation of a QoS flow architecture.
- the terminal device can establish one or more sessions with a core network (CN).
- a node can map packets belonging to different sessions to different bearers and map packets belonging to the same session to one or more bearers.
- the QoS flow is the minimum granularity for realizing QoS differentiation in the above session.
- the same session can include one or more QoS flows.
- a QoS flow identifier (QFI) may be assigned to each QoS flow, and a QFI may be used to indicate a QoS flow.
- QFI QoS flow identifier
- the packet header of the data packet carries the QFI.
- the communication interface between the core network and the node may be an N3 interface, or the communication interface between the core network and the node may be a next-generation user plane (NG-U). ) Tunnel.
- NG-U next-generation user plane
- the foregoing session may be a packet data unit (PDU) session
- the foregoing bearer may be a data resource bearer (DRB).
- the PDU session may be a connection established between the terminal device and the data network, and the type of the connection may be an internet protocol (IP), an Ethernet, or other types.
- IP internet protocol
- the method or apparatus of the present application will be described by taking the above-mentioned session as a PDU session and the above-mentioned bearer as a DRB.
- the foregoing core network may include a core network device, and the core network device may include any one of the following: a user plane function (UPF) entity, an access and mobility management function (AMF), Session management function (SMF).
- UPF user plane function
- AMF access and mobility management function
- SMF Session management function
- 5G defines the packet processing mechanism on the air interface based on DRB. Packets served by one DRB have the same packet handling mechanism in air interface transmission.
- a node may establish multiple DRBs with a terminal device to satisfy QoS flows with different packet processing requirements. It should be noted that the same DRB may have a mapping relationship with one QoS flow, or may have a mapping relationship with multiple QoS flows.
- the node may map the data packet included in the QoS flow to the corresponding one based on the QFI identifier of the NG-U tunnel (or the N3 interface) and the QoS rule corresponding to the QFI.
- the terminal device maps the data packet included in the QoS flow to the corresponding DRB according to the mapping relationship between the pre-configured QoS flow and the DRB, and performs uplink transmission.
- FIG. 2 is a schematic structural diagram of a dual link scenario in the embodiment of the present application.
- a dual link scenario usually includes a master node (MN) and a secondary node (SN).
- MN master node
- SN secondary node
- the foregoing primary node or secondary node may also be referred to as a primary base station and a secondary base station, respectively.
- the primary node and the secondary node can jointly serve the terminal device. In other words, for the same session established by the terminal device and the core network, the primary node and the secondary node can simultaneously perform data transmission with the terminal device.
- the master node may be responsible for the control plane signaling flow and the user plane data transmission with the terminal device, and the secondary node only needs to be responsible for the user plane data transmission with the terminal device.
- the master node can establish a data resource bearer (DRB) and a signal resource bearer (SRB) with the terminal device, and the secondary node only needs to establish a DRB with the terminal device.
- the primary node and the secondary node may be responsible for both control plane transmission and user plane data transmission with the terminal device. That is, the master node can establish a DRB and an SRB with the terminal device, and the secondary node can also establish a DRB and an SRB with the terminal device.
- a dual link scenario may include a primary node and at least one secondary node. In the following, a case in which a primary node and a secondary node are included in a dual-link scenario will be described as an example.
- both the primary node and the secondary node described above may be NR nodes.
- the foregoing primary node may be a node in LTE, and the secondary node may be an NR node.
- the foregoing primary node may be an NR node, and the secondary node may be an LTE node.
- FIG. 3 shows a schematic diagram of a bearer type of the related art.
- a node in a dual-link scenario can support the following bearer types: MCG bearer, MCG split bearer, SCG bearer, and SCG split bearer.
- MCG bearer MCG split bearer
- SCG bearer SCG bearer
- SCG split bearer SCG split bearer.
- the path corresponding to the MCG bearer passes through all the protocol layers in the master node; the path corresponding to the SCG bearer passes through all the protocol layers in the slave node; the path corresponding to the MCG split bearer passes through the SDAP layer and PDCP of the master node.
- the path corresponding to the SCG split bearer passes through the SDAP layer of the secondary node, the PDCP layer, and the RLC layer of the primary node and the protocol layer below the RLC layer.
- RLC radio
- FIG. 3 shows a partial protocol layer inside a node, which includes, in order from top to bottom, an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer.
- the wireless access protocol system is generally divided into three layers, layer one is a physical (physical, PHY) layer, layer two is a data link layer, and layer three is an RRC layer.
- the data link layer includes the following sublayers in order from bottom to top: a MAC layer, an RLC layer, and a PDCP layer.
- the foregoing SDAP layer function includes, but is not limited to, a mapping for processing a QoS flow to a DRB.
- the protocol layer inside the node or terminal device is not limited to the protocol layer shown in FIG. It may include more or fewer protocol layers. Or the names of the various protocol layers may be different. For example, in one possible protocol layer architecture, the PDCP layer described above may not be included.
- FIG. 4 shows a schematic diagram of a transmission path of an MCG split bearer in the related art.
- the MCG split bearer includes two paths, one path passes through the PDCP layer of the master node and the protocol layer below the PDCP layer of the secondary node; the other path is the path between the master node and the terminal device, that is, The path passes through the protocol layer in the primary node and does not pass through any protocol layers in the secondary node.
- the first QoS flow ie, QoS flow 1 in FIG.
- the second QoS flow (ie, QoS flow 2 in FIG. 4) and the second QoS flow (ie, QoS flow 2 in FIG. 4) are mapped to the first A DRB (ie DRB1 in Figure 4).
- the QoS flow information cannot be distinguished according to the PDCP PDU, and therefore cannot be based on The assignment of QoS flow levels can only be done at the PDCP PDU level.
- the PDCP layer of the terminal device cannot distinguish the QoS flow information, so that the QoS flow level cannot be allocated, and only the PDCP PDU level path allocation can be performed.
- the embodiments of the present application are directed to providing a communication method for implementing path selection based on QoS flow granularity in a radio access network (RAN), or implementing a certain QoS flow autonomous selection path for transmission.
- the communication method provided by the present application is applicable to a dual link scenario or a multi-link scenario. For example, it can be applied to a dual-link scenario connected to a 5G core network.
- the embodiment of the present application proposes a bearer scheme based on QoS flow granularity.
- the bearer scheme supports transmission of QoS flows over the first path.
- the first path passes through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, or the first path passes through the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node.
- the foregoing bearer scheme can be applied to both the uplink transmission scenario and the downlink transmission scenario.
- the protocol layer below the SDAP layer refers to all protocol layers below the SDAP layer and does not include the SDAP layer.
- the protocol layer below the SDAP layer includes a PDCP layer, an RLC layer, and a MAC layer.
- the bearer scheme may further support transmitting the QoS flow by using the second path, where the second path is the primary node and the first path passes the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node.
- the path between the primary path and the terminal device is that the second path only passes through the protocol layer of the primary node and the protocol layer of the terminal device, and does not pass through any protocol layer in the secondary node.
- the foregoing second path is a path between the secondary node and the terminal device, which means that the second path only passes through the protocol layer of the secondary node and the protocol layer of the terminal device, and does not pass through any protocol layer of the primary node.
- the QoS flow may be transmitted through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, or may be transmitted through the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node.
- the flexibility of the QoS flow using the transmission path improves communication efficiency.
- the QoS flow performs path selection at the SDAP layer, the QoS flow can be mapped to the bearer after the path is selected for the QoS flow, so that the path can be selected based on the granularity of the QoS flow, and the flexibility of data transmission is improved. effectiveness.
- FIG. 5 to FIG. 7 respectively illustrate three possible application scenarios of the embodiment of the present application.
- the bearer scheme may specifically include multiple bearer types according to different supported paths or paths.
- the first type of bearer-sixth type bearer introduced by the embodiment of the present application is shown in FIG. 5-7.
- the bearer type of the first application scenario shown in FIG. 5 includes: an MCG bearer, an SCG bearer, a first type bearer, a second type bearer, a third type bearer, and a fourth type bearer.
- the MCG bearer or the SCG bearer uses the second path to transmit the QoS flow;
- the first type bearer or the second type bearer only supports the use of the first path to transmit the QoS flow;
- the third type bearer or the fourth type bearer supports the use of the first path and/or Or the second path transmits the QoS flow.
- the first path corresponding to the first type bearer and the third type bearer passes through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node; the first type bearer and the first path corresponding to the fourth type bearer pass through the auxiliary path.
- Xn in FIGS. 5 to 7 represents a communication interface between base stations, that is, a communication interface between the master node and the slave node.
- three path transmission modes may be adopted to transmit the QoS flow.
- the first path transmission mode the first path is used to transmit the QoS flow; in the second path transmission mode, the second path is used.
- the QoS flow is transmitted; in the third path transmission mode, the QoS flow is jointly transmitted using the first path and the second path.
- the third path transmission mode may include two cases. In the first case, the QoS flow is repeatedly transmitted to each other using the first path and the second path. In the second case, the first path and the second path are used to transmit different data packets of the QoS flow, that is, the QoS flow is not repeatedly transmitted between the first path and the second path.
- the above three path transmission modes can also be dynamically adjusted, that is, the path transmission mode can be dynamically switched.
- the second application scenario shown in FIG. 6 includes: an MCG bearer, an SCG bearer, a third type bearer, and a fourth type bearer.
- the MCG bearer or the SCG bearer supports transmitting the QoS flow by using the second path;
- the third type bearer or the fourth type bearer supports transmitting the QoS flow through the first path and/or the second path, and supports dynamic adjustment of the path transmission mode.
- the third application scenario shown in FIG. 7 includes: an MCG bearer, an SCG bearer, a fifth type bearer, and a sixth type bearer.
- the fifth type of bearer and the sixth type of bearer support QoS flow are transmitted through the first path, the second path, and/or the third path.
- the third path passes through the PDCP layer of the primary node and the protocol layer below the PDCP layer of the secondary node, or through the PDCP layer of the secondary node and the protocol layer below the PDCP layer of the primary node.
- the protocol layer below the PDCP layer refers to all protocol layers below the PDCP layer.
- the first path corresponding to the fifth type bearer and the second path are the same as the third type bearer.
- the sixth type carries the corresponding first path, and the second path is the same as the fourth type of bearer.
- the third type carries the corresponding third path through the PDCP layer of the primary node and the protocol layer below the PDCP layer of the secondary node; the third path corresponding to the third path carries the PDCP layer of the secondary node and the protocol below the PDCP layer of the primary node Floor.
- the QoS flow may be transmitted in multiple path transmission modes, for example, the QoS flow is separately transmitted using the first path, the QoS flow is separately transmitted using the second path, and the QoS flow is separately transmitted using the third path. And using the first path and the second path to jointly transmit the QoS flow, using the second path and the third path to jointly transmit the QoS flow, using the first path and the third path to jointly transmit the QoS flow, using the first path, the second path, and the first path The three paths jointly transmit QoS flows. And in the transmission process, the above multiple path transmission modes can also be dynamically adjusted.
- the MCG bearer, the first type bearer, the third type bearer, or the fifth type bearer may be classified as a bearer terminated by a MN terminated, that is, the SDAP layer in the protocol stack corresponding to the above bearer is located at the master. node.
- the SCG bearer, the second type bearer, the fourth type bearer, and the sixth type bearer may be classified as a bearer termination (SN terminated) bearer, that is, the SDAP layer in the protocol stack corresponding to the bearer is located at the secondary node.
- SN terminated bearer termination
- FIG. 8 is a schematic diagram of a scenario for transmitting a QoS flow according to an embodiment of the present application. It shows a scenario in which a single QoS flow is downlinked using one path. In other words, at any point in the transmission, a single QoS flow is transmitted on only one path.
- the first QoS flow (QoS Flow 1) is mapped to the first DRB (DRB1)
- the second QoS flow (QoS Flow 2) is mapped to the second DRB (DRB2).
- the first DRB may be an MCG bearer
- the second DRB may be a first type of bearer, a third type of bearer, or a fifth type of bearer.
- the path transmission mode is to use the first path to transmit the QoS flow. Therefore, the data packet included in the first QoS flow will be transmitted on the path between the primary node and the terminal device.
- the data packet included in the second QoS flow is obtained after being processed by the SDAP layer of the primary node, and then the SDAP PDU is transmitted to the secondary node through the interface between the nodes, and the downlink transmission is continued by the protocol layer below the SDAP layer of the secondary node.
- the interface between the above nodes may be an Xn interface.
- the corresponding uplink transmission scenario is similar and will not be described again.
- FIG. 9 is a schematic diagram of a scenario for transmitting a QoS flow according to another embodiment of the present application. It shows a scenario in which two paths are used to jointly downlink a single QoS flow. That is, the first QoS flow (QoS Flow 1) is transmitted using the first path and the second path. The first QoS flow is mapped to the first DRB (DRB1) and the second DRB (DRB2).
- the same QoS flow mapping is transmitted on one bearer, that is, the first DRB and the second DRB may be the same bearer. For example, it may be a third type bearer or a fifth type bearer, and its path transmission mode is to use the first path and the second path to transmit together.
- the same QoS flow may be mapped to two bearers, that is, the first DRB and the second DRB may be different bearers.
- the first DRB may be an MCG bearer
- the second DRB may be a second bearer.
- the path transmission mode of the third type bearer and the fifth type bearer is to use the first path to transmit the QoS flow.
- the first QoS flow may be repeatedly transmitted to each other using the first path and the second path.
- different data packets of the first QoS flow may be separately transmitted using the first path and the second path.
- the corresponding uplink transmission scenario is similar and will not be described again.
- the terminal device needs to distinguish the QoS flow separated from the SDAP layer from the QoS flow.
- the node also needs to distinguish the QoS flow separated from the SDAP layer from the QoS flow.
- a serial number may be added to a frame header of a SDAP PDU included in the QoS flow, and the serial number is used to indicate the ordering of the SDAP PDU, so that the SDAP layer performs a reordering function to distinguish QoS using different transmission paths. Different packets of the stream.
- the sequence number in the SDAP frame header may be in two sorting manners.
- the first sorting mode an independent sequence number can be added to the SDAP PDU that allows each QoS flow transmitted on both paths.
- the second sorting mode a consistent sequence number can be added for the SDAP PDUs mapped to all QoS flows in the same bearer.
- the reordering function can also be added in the SDAP layer, and a re-ordering timer is defined.
- a reordering timer can be defined for each QoS flow.
- a reordering timer is defined to allow multiple QoS flows to be passed on both paths.
- the receiving end receives a new SDAP PDU
- the reordering timer is running and the sequence number of the SDAP PDU that triggered the reordering timer has been delivered to the upper layer, according to the sequence number of the new SDAP PDU,
- the reordering timer is reset; if the reordering timer is not started and at least one SDAP SDU is not delivered to the upper layer, the reordering timer is started.
- FIG. 10 is a schematic flowchart diagram of a communication method 1000 according to an embodiment of the present application.
- the method 1000 can be applied to the application scenarios of FIG. 5 to FIG. 9.
- the method 1000 includes:
- the node sends the first indication information to the terminal device, and the terminal device receives the first indication information, where the first indication information is used to indicate that the first QoS flow is transmitted by using the first bearer, where the node is a node or a secondary node, the protocol stack corresponding to the first bearer supports transmitting a QoS flow by using a first path, where the first path passes the service data adaptation protocol SDAP layer of the primary node and the SDAP layer of the secondary node The following protocol layer, or the first path passes the service data of the secondary node to adapt to the protocol SDAP layer and the protocol layer below the SDAP layer of the primary node.
- the protocol layer below the SDAP layer may refer to all protocol layers below the SDAP layer, and does not include the SDAP layer.
- the protocol layer below the SDAP layer includes a PDCP layer and all protocol layers below the PDCP layer.
- the protocol layer below the SDAP layer includes a PDCP layer, an RLC layer, a MAC layer, and the like.
- the protocol layer inside the node or terminal device is not limited to the protocol layer shown in FIG. It may include more or fewer protocol layers. Or the names of the various protocol layers may be different.
- the PDCP layer described above may not be included.
- the first bearer may be any one of the foregoing first type bearer to the sixth type bearer.
- the above node can be the primary node.
- the first bearer is any one of the first type bearer and the sixth type bearer
- the first indication information may be sent by the master node to the terminal device.
- the foregoing node may also be a secondary node.
- the first bearer belongs to a bearer terminated by the secondary node, for example, the second type bearer, the fourth type bearer, or the sixth type bearer may be used by the secondary node to the terminal device. Sending the above first indication information.
- the foregoing first indication information may be carried in the RRC signaling.
- the first indication information may include the following information: an identifier of the first bearer, a bearer type of the first bearer, and information of the QoS flow mapped to the first bearer.
- the bearer type may be any one of the following: a first type bearer, a second type bearer, a third type bearer, a fourth type bearer, a fifth type bearer, and a sixth type bearer.
- the first indication information may explicitly indicate the type of the first bearer, or may also indicate the type of the first bearer in the form of an index or a Boolean variable.
- the node transmits the first QoS flow by using the first bearer.
- the foregoing node transmits the first QoS flow by using the first bearer, that is, mapping the first QoS flow to the first bearer for transmission.
- the foregoing node uses the first bearer to perform the transmission of the first QoS flow, and may include the primary node and the secondary node cooperate to perform uplink transmission or downlink transmission with the terminal device. Or, it may also include that one of the primary node and the secondary node performs transmission of the first QoS flow with the terminal device.
- the first indication information may be sent by the primary node to the terminal device, and then the first QoS flow is coordinated by the primary node and the secondary node.
- the first bearer may be the first type of bearer-sixth. Any bearer in the type bearer.
- the path transmission mode of each bearer in the third type bearer-sixth type bearer may be transmitted by using the first path or jointly transmitted by using the first path and the second path.
- the first indicator information may also be sent by the secondary node to the terminal device, and then the primary node and the secondary node jointly transmit the first QoS flow.
- the first bearer may be the second type of bearer.
- the fourth type bearer, or the sixth type bearer The path transmission mode of the fourth type bearer and the sixth type bearer may be transmitted using the first path or jointly transmitted using the first path and the second path.
- the first indication information may be sent by the primary node, and the first QoS flow is transmitted by the primary node.
- the first bearer is a third type bearer or a fifth type bearer, and the path transmission mode is to use the second path transmission.
- the first indication information may be sent by the secondary node, and the first QoS flow is transmitted by the secondary node.
- the first bearer is a fourth type bearer-sixth type bearer, and the path transmission mode is transmitted using the second path.
- the above S1001 portion and the S1002 portion may also be executed by different nodes.
- the first indication information may also be sent by the primary node, and the first QoS flow is transmitted by the secondary node.
- the first bearer is a fourth type bearer or a sixth type bearer, and the path transport mode of the fourth type bearer or the sixth type bearer is transported using the second path.
- the QoS flow may be transmitted through the SDAP layer of the primary node and the protocol layer below the SDAP layer of the secondary node, or may be transmitted through the SDAP layer of the secondary node and the protocol layer below the SDAP layer of the primary node.
- the flexibility of the QoS flow using the transmission path improves communication efficiency.
- the terminal device when the underlying protocol of the bearer of the QoS flow mapping is located at the primary node, for example, an MCG bearer, a second type of bearer, or a second path in the third type of bearer, etc., the terminal device The data is transmitted by the primary node.
- the underlying protocol of the bearer of the QoS flow mapping is located at the secondary node, for example, the SCG bearer, the first type of bearer, or the first path of the third type of bearer, the terminal device transmits the data through the secondary node.
- the terminal device passes the master node. Data is transmitted together with the secondary node. Therefore, as shown in FIG. 11, for the terminal device side, there are only three types of bearers: an MCG bearer, an SCG bearer, and a split bearer.
- the MCG bearer refers to the terminal device and the master node transmitting data
- the SCG bearer refers to the terminal device and the secondary node transmitting data
- the split bearer refers to the terminal device transmitting data simultaneously with the master node and the secondary node.
- the classification type of the bearer type is different. Therefore, the first indication information may indicate the type of the first bearer according to the classification manner of the node side, or may indicate the type of the first bearer according to the classification manner of the terminal device side.
- the node further needs to further configure path indication information to indicate a path transmission mode of the first QoS flow.
- the path transmission mode may include separately transmitting the first QoS flow using the first path, separately transmitting the first QoS flow using the second path, or The first QoS flow is jointly transmitted using the first path and the second path.
- the node needs to indicate to the terminal device which path to use to transmit the first QoS flow.
- the primary node typically indicates which path the terminal device uses for transmission.
- the secondary node may also indicate which path the terminal device uses for transmission.
- the primary node and the secondary node simultaneously indicate which path the terminal device uses for transmission.
- the fifth type bearer and the sixth type bearer there are more kinds of path transmission modes. For details, refer to the example of FIG. 7. For brevity, it will not be described here.
- the node may further send path adjustment information to the terminal device, where the path adjustment information is used to indicate that the path transmission mode of the first QoS flow is changed.
- the path indication information and the path adjustment information may be indicated by using multiple signaling formats.
- RRC layer signaling For example, RRC layer signaling, SDAP layer signaling, or MAC layer signaling may be employed.
- the path transmission mode of the QoS flow is dynamically indicated or adjusted by sending path indication information or path adjustment information, and the transmission efficiency based on the QoS flow is improved.
- the node may indicate or adjust the QoS flow path transmission mode by using the following three schemes.
- the path indication information and the path adjustment information may both be carried in the RRC layer signaling.
- the path indication information may be carried in the RRC message
- the path adjustment information may be carried in the RRC connection reconfiguration message.
- the RRC message includes an initial configuration of the node to the terminal device, the initial configuration including path indication information to indicate a path transmission mode of the QoS flow.
- the node may send an RRC connection reconfiguration message to the terminal device, where the RRC connection reconfiguration message includes path adjustment information to indicate a path transmission mode of changing or reconfiguring the QoS flow.
- the QoS flow of the uplink transmission and the QoS flow of the downlink transmission may be transmitted using the same path transmission mode line, or may be transmitted using different path transmission modes.
- the path indication information may be carried in the RRC signaling, and the path adjustment information may be carried in the SDAP signaling.
- SDAP signaling can be a command for dynamically switching paths.
- the path transmission mode of the QoS flow may be initially configured through RRC signaling, and then the path transmission mode of the QoS flow is changed based on the SDAP command.
- Dynamic adjustment of the transmission path is implemented through SDAP signaling.
- the SDAP signaling described above can be implemented based on a SDAP frame.
- the SDAP frame is a PDU of the SDAP layer, that is, a SDAP PDU. It generally includes a frame header and data information.
- the frame header is usually used to indicate some control information, and the data information includes the data transmitted by the previous protocol layer.
- FIG. 12 is a schematic diagram showing a SDAP frame format of an embodiment of the present application.
- the SDAP frame may include the following identifiers: D/C identifier, QFI, and reflective QoS indication (RQI).
- QFI indicates the ID of the QoS flow
- D/C identifier indicates whether the SDAP PDU is a data packet or a control packet (D indicates a data packet, C indicates a control packet)
- the RQI is a reflection QoS indication.
- the terminal device receives the SDAP frame through a certain downlink path
- the D/C indicates that the SDAP PDU is a control packet
- the terminal device The data packet corresponding to the QFI may be transmitted through the same uplink path as the downlink path.
- the SDAP may further include: data, a sequence number, and a reserved bit.
- the serial number represents a sequence number indicating the ordering of the SDAP PDUs.
- R represents a reserved bit.
- FIG. 13 shows a schematic diagram of a SDAP frame format according to still another embodiment of the present application.
- the PDU type, the RQI, and the D/C identifier may be included in the SDAP frame.
- the PDU type indicates the control domain type.
- the indication of the path transmission mode of the QoS flow may be implemented by defining a new PDU type.
- the format of the PDU type may be as shown in Table 1 below.
- the terminal device may pass the downlink.
- the uplink path with the same path transmits the data packet corresponding to the QFI.
- the SDAP can also include: data and serial numbers. The serial number indicates the ordering of the SDAP PDUs.
- FIG. 14 is a schematic diagram showing a SDAP frame format in still another embodiment of the present application.
- the following identifiers may be included in the SDAP frame: QFI, RQI.
- the terminal device may send the corresponding uplink path through the same downlink path.
- the data package for this QFI may further include: data, a sequence number, and a reserved bit.
- the node may pre-configure rules for the terminal device, and the terminal device determines the path transmission mode currently used according to the preset rule.
- the node may indicate the path transmission mode initially used by the terminal device and the preset rule in the initial configuration.
- the terminal device may determine the path transmission mode currently used according to the preset rule.
- the node may only indicate a preset rule in the initial configuration, and the terminal device may determine the initial path transmission mode and the subsequent path transmission mode according to the preset rule.
- the node may send configuration indication information to the terminal device, where the configuration indication information is used to indicate that the terminal device uses the first path separately if the first preset condition is met.
- the first preset condition, the second preset condition, and the third preset condition may be preset pre-agreed conditions by the node and the terminal device. If the current condition meets one of the preset conditions, the terminal device performs the first QoS flow transmission by using the path transmission mode corresponding to the preset condition.
- the first preset condition, the second preset condition, and the third preset condition are not specifically limited in the embodiment of the present application.
- the preset condition may be a condition related to the current network state, such as a load condition of the current path, or a buffer condition of the first QoS flow, or a queue waiting time.
- a factor in the current network state may be considered or a plurality of factors may be considered in combination to select a path transmission mode.
- the node indicates a UL data split threshold of the QoS flow in the configuration indication information, and when the buffer of the SDAP layer about the QoS flow exceeds the threshold, Transfer on the path; otherwise select a path to transmit separately or on the initially configured path.
- the two paths are transmitted; otherwise Select a path to transmit separately or on the initially configured path.
- the node may indicate a queue waiting time threshold of a certain QoS flow in the configuration indication information, and when the QoS flow waits for the terminal device to wait for the time limit to exceed the time threshold, the QoS flow is transmitted on the two paths; Otherwise select a path to transmit separately or on the initially configured path.
- the path transmission mode used by the QoS flow is indicated in a pre-configured manner, and the terminal device may select a path transmission mode of the QoS flow according to the preset condition indicated in the current network state and the configuration indication information, thereby improving the QoS-based mode.
- the transmission efficiency of the stream is indicated in a pre-configured manner, and the terminal device may select a path transmission mode of the QoS flow according to the preset condition indicated in the current network state and the configuration indication information, thereby improving the QoS-based mode.
- the foregoing SDAP frame format may also be defined based on a bearer level.
- the QFI in the above SDAP frame format can be replaced with a bearer identifier. That is, all QoS flows mapped to the bearer may have the same SDAP format.
- the embodiment of the present application can also support the path transmission mode selection and adjustment based on the bearer level, that is, switch from one bearer type to another bearer type, or to map to All QoS flows of a certain bearer are switched to another path transmission mode.
- the method further includes: the node sends the first bearer switching indication information to the terminal device, where the first bearer switching indication information is used to indicate that the bearer of the first QoS flow mapping is switched to the second bearer.
- the second bearer is any bearer other than the first bearer.
- the first bearer modification indication information may be RRC signaling.
- the RRC signaling may include information of an identity of a second bearer to which the QoS flow is to be handed over, a type of the second bearer, and information of a QoS flow mapped to the second bearer.
- the type of the DRB is any one of the first type bearer to the sixth type bearer.
- the first bearer handover indication information may explicitly indicate the type of bearer to which the QoS flow is to be switched, or may also indicate the type of the DRB in the form of an index or a Boolean variable.
- the information mapped to the QoS flow of the second bearer may for example be an identification of the QoS flow.
- the second bearer switching indication information may be sent between the primary node and the secondary node to indicate that the bearer type of the first QoS flow is switched.
- the second bearer switching indication information can be sent through the Xn interface.
- the second bearer switching indication information may indicate a handover between various bearer types. For example, the switching between the MCG bearer and the first type bearer/third type bearer; the switching between the SCG bearer and the second type bearer/fourth type bearer, etc., are not enumerated here.
- the bearer handover occurs within the bearer type terminated by the primary node, for example, from the MCG bearer to the first type bearer or the third type bearer, or the bearer type terminated by the secondary node, for example, switching from the SCG bearer to the second
- the type bearer or the fourth type bearer since the node where the corresponding SDAP layer and the above protocol layer are located does not change, the node does not need to inform the core network to perform path conversion, thereby saving signaling overhead.
- the QoS flow may be transmitted between the terminal device and the node by using one path, or the QoS flow may be jointly transmitted by using two paths.
- the centralized control and management of the radio access network based on the QoS flow level is realized, and the flexibility of the communication system is improved.
- the node may further send, to the terminal device, retransmission indication information, where the retransmission indication indication information is used to indicate that the first path and the second path are mutually retransmitted and transmitted to the first The QoS flow carried.
- the node may further transmit the repeated transmission indication information to the terminal device.
- the node can determine whether to allow repeated transmissions based on the current network status. For example, it can be determined based on the load conditions of different paths. When the load of the first path and the second path is greater than a predetermined threshold, it may be determined that repeated transmissions are not allowed. When the load of the first path and the second path is less than a predetermined threshold, it may be determined that the repeated transmission is allowed.
- the value of the above predetermined threshold may be determined according to specific practices.
- the node may further send the repeated transmission stop indication information to the terminal device, the repeated transmission stop indication information being used to indicate to stop using the first path and the second path to repeatedly transmit the mapping to each other.
- the QoS flow of the first bearer may be used to indicate that the initial state of the QoS flow is to allow for repetitive transmission or to disallow duplicate transmission.
- the node may send repeated transmission change information to the terminal device, where the repeated transmission change information is used to indicate that the repeated transmission mode of the first QoS flow is changed.
- the repeated transmission indication information is used to indicate that the first path and the second path are repeatedly transmitted to each other to the first QoS flow.
- the repeated transmission stop indication information is used to indicate to stop using the first path and the second path to repeat transmission mapping to the first QoS flow.
- the transmission path mode of the QoS flow mapped to the first bearer can be flexibly configured, and the communication transmission efficiency based on the QoS flow is improved.
- the above-described repeated transmission indication information or repeated transmission stop indication information may be configured through RRC layer signaling.
- the above information may also be configured through SDAP layer signaling.
- the data packet corresponding to the QoS stream may be repeatedly transmitted based on the PDU type in the SDAP frame or the data packet corresponding to the stop of the QoS flow may be stopped.
- Table 2 shows another possible definition of the PDU type. If the PDU type is set to 001, the SDAP frame indicates that the data packet corresponding to the QoS flow is allowed to be repeatedly transmitted. If the PDU type is set to 002, the SDAP frame indicates that the data packet corresponding to the QoS flow is repeatedly transmitted.
- the repeated transmission indication information may also be configured through MAC layer signaling.
- FIG. 15 shows a schematic diagram of the format of MAC signaling.
- the MAC layer signaling consists of a MAC subheader and a MAC control element (CE).
- the MAC subheader includes a logical channel identifier (LCID) for indicating the identity of the logical channel or the type of MAC layer signaling for transmitting data.
- the LCID can define new index values for repeated transmissions at the QoS flow level.
- Index value (index) LCID 100001 QoS flow repeatability command
- the MAC subheader may further include at least one of the following information: R, indicating reserved bits; L, indicating a length of the MAC Control element.
- R indicating reserved bits
- L indicating a length of the MAC Control element.
- the MAC Control element can be used to indicate whether the QoS flow is for repetitive transmission.
- the MAC Control Element may include an index of the QoS flow or an identification of the QoS flow and indicate whether the QoS flow is allowed for repetitive transmission. Because in the MAC layer signaling, the terminal device cannot distinguish the PDU session ID corresponding to the MAC signaling. Therefore, the MAC layer signaling further needs to indicate the ID of the PDU session corresponding to the QoS flow.
- some of the bits P 0 , P 1 , P 2 in the MAC Control element may be used to indicate the ID of the PDU session. For example, three bits can be used to identify the index value of a PDU session.
- the remaining bits Q 0 -Q 5 in the MAC Control Element can implicitly indicate a QoS flow, respectively.
- the correspondence between the bit and the QoS flow may be pre-agreed. For example, it may be arranged in order according to the size of the ID of the QoS flow, and correspond to the lower to upper bits of the bits of the MAC control element.
- the assignment of each bit of the above remaining bits can be used to indicate whether its corresponding QoS flow allows repeated transmissions.
- the MAC control element may also not indicate the ID of the PDU session.
- a new index value can be defined by the LCID in the MAC subheader to indicate the ID of the PDU session.
- bits Q 0 -Q 8 in the MAC Control element are used to implicitly indicate a QoS flow, respectively. It is possible to indicate whether the corresponding QoS flow allows repeated transmission according to the assignment of each bit.
- the MAC control element includes a PDU session ID and a QoS flow ID, indicating that the QoS flow ID of the corresponding PDU session is repetitively transmitted or the repetitive transmission is stopped.
- the initial default is a non-repetitive transmission.
- the default is to execute a repetitive transmission command.
- the embodiment of the present application proposes a repetitive transmission scheme based on a QoS flow level. That is, the data packet corresponding to the same QoS flow can be repeatedly transmitted through the first path and the second path, thereby realizing the reliability of the QoS flow granularity in the radio access network transmission.
- the frame header of the SDAP PDU included in the first QoS flow includes a sequence number, where the sequence number is used to indicate the ordering of the SDAP PDU.
- the SDA frame formats shown in Figures 12-14 can each include a serial number.
- the transmitting end may add a sequence number in the frame header of the SDAP PDU, and perform QoS flow to the DRB. After the mapping, the SDAP PDU is transmitted to the receiving end through two paths. After receiving the QoS flows from the two paths at the SDAP layer, the receiving end may sort according to the sequence number in the SDAP frame header.
- the sorted data packet can be delivered to the core network, and for the downlink transmission, the sorted data packet can be submitted to the upper layer above the SDAP layer.
- the serial number refer to the foregoing description, and details are not described herein again.
- a sequence number is set in a frame header of a SDAP PDU included in the first QoS flow, so as to identify data packets transmitted in different paths, and improve communication transmission efficiency of the QoS flow.
- the receiving end may discard the repeatedly received SDAP PDU according to the serial number of the SDAP layer after receiving the SDAP PDU.
- the primary node and the secondary node may also perform message interaction through the communication interface.
- the type of the QoS flow or the bearer type corresponding to the QoS flow may be sent between the primary node and the secondary node.
- other information of the QoS flow may be sent between the primary node and the secondary node. For example, whether the QoS flow carries a SDAP frame header and a SDAP header size, so that the node receiving the data performs the SDAP frame header compression and decompression function according to the SDAP frame header size.
- the QoS parameter of the QoS flow or the mapping relationship between the QoS flow and the bearer may also be sent between the primary node and the secondary node.
- the present application proposes flow control based on QoS flow granularity between nodes.
- a bearer classified as a master node termination for example, a first type bearer, a third type bearer, or a fifth type bearer
- the master node may send flow control signaling based on the granularity of the QoS flow to the secondary node.
- the flow control instruction may be used to indicate at least one of the following: a QoS flow identifier, information indicating a period in which the secondary node reports QoS flow state information, or information indicating a trigger condition of the secondary node reporting QoS flow state information.
- the secondary node may report the status information of the downlink QoS flow to the primary node periodically or according to the triggering condition, for example, may be in the general packet radio service tunneling protocol user plane.
- the extension header of the GTU-U includes at least one of the following information: the maximum sequence number of the successfully transmitted SDAP packet, and the expected buffer size of the QoS flow.
- the second type bearer, the fourth type bearer, and the sixth type bearer may send a flow control signaling request based on the QoS flow granularity to the primary node by the secondary node, where relevant
- the process is similar to the bearer of the primary node termination type and will not be described here.
- the flow control based on the QoS flow granularity can better guarantee the flow control of the Xn interface and improve the system performance.
- FIG. 16 is a schematic block diagram of a node 1600 of an embodiment of the present application. It should be understood that the node 1600 is capable of performing the various steps performed by the nodes in the methods of FIGS. 1 through 15, which are not described in detail herein in order to avoid redundancy.
- the node 1600 includes: a processing unit 1601 and a communication unit 1602,
- the processing unit 1601 is configured to send first indication information to the terminal device by using the communication unit 1602, where the first indication information is used to indicate that the first QoS flow is transmitted by using the first bearer, where the node 1600 is a master node. Or a secondary node, the protocol stack corresponding to the first bearer supports transmitting a QoS flow by using a first path, where the first path passes the SDAP layer of the primary node and a protocol layer below the SDAP layer of the secondary node, Or the first path passes the SDAP layer of the secondary node and a protocol layer below the SDAP layer of the primary node; and the first QoS flow is transmitted by using the first bearer.
- FIG. 17 is a schematic block diagram of a terminal device 1700 according to an embodiment of the present application. It should be understood that the terminal device 1700 can perform the various steps performed by the terminal device in the methods of FIGS. 1 to 15 and is not described in detail herein in order to avoid repetition.
- the terminal device 1700 includes: a processing unit 1701 and a communication unit 1702,
- the processing unit 1701 is configured to receive the first indication information by using the communication unit 1702, where the first indication information is used to indicate that the first QoS flow is transmitted by using the first bearer, where the protocol stack corresponding to the first bearer is supported. Transmitting a QoS flow by using a first path, where the first path passes the SDAP layer of the primary node and a protocol layer below the SDAP layer of the secondary node, or the first path passes the SDAP of the secondary node a layer and a protocol layer below the SDAP layer of the primary node; and transmitting the first QoS flow by the first bearer.
- FIG. 18 is a schematic structural diagram of a node 1800 provided by an embodiment of the present application.
- node 1800 includes one or more processors 1830, one or more memories 1810, and one or more communication interfaces 1820.
- the processor 1830 is configured to control the communication interface 1820 to transmit and receive signals
- the memory 1810 is configured to store a computer program
- the processor 1830 is configured to call and run the computer program from the memory 1810 such that the node performs the implementation of the communication method of the present application.
- the corresponding flow and/or operation performed by the node in the example For the sake of brevity, it will not be repeated here.
- FIG. 19 is a schematic structural diagram of a terminal device 1900 according to an embodiment of the present application.
- terminal device 1900 includes one or more processors 1930, one or more memories 1910, and one or more communication interfaces 1920.
- the processor 1930 is configured to control the communication interface 1920 to send and receive signals
- the memory 1910 is configured to store a computer program
- the processor 1930 is configured to call and run the computer program from the memory 1910, such that the terminal device performs the communication method of the present application.
- the disclosed systems, devices, and methods may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
- the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
- the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
- the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种通信方法、装置和***,能够提高通信效率。该方法包括:节点向终端设备发送第一指示信息,第一指示信息用于指示使用第一承载传输第一QoS流,其中,节点为主节点或辅节点,第一承载对应的协议栈支持通过第一路径传输QoS流,其中,第一路径通过主节点的业务数据适应协议SDAP层以及辅节点的SDAP层以下的协议层,或者,第一路径通过辅节点的SDAP层以及主节点的SDAP层以下的协议层;节点通过第一承载传输第一QoS流。
Description
本申请要求于2018年01月22日提交中国专利局、申请号为201810060694.6、申请名称为“通信方法、装置和***”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信领域,并且更具体地,涉及通信方法、装置和***。
在长期演进***(long term evolution,LTE)双链接场景下,存在多种承载类型。例如主小区组(master cell group,MCG)承载,MCG分离(split)承载,辅助小区组(secondary cell group,SCG)承载,SCG分离承载。其中,不同的承载对应的协议栈支持的传输路径不同。例如,对于映射到MCG承载的数据包,通过主基站路径传输;映射到MCG分离承载的数据包,可通过基站配置的方式,经由主基站路径传输,或者经由辅基站路径传输或者同时通过主基站路径和辅基站路径传输。现有的方案支持基于承载粒度的路径选择机制。
随着下一代通信***研究的全面展开并逐渐深入,5G定义了基于服务质量(quality of service,QoS)流(flow)的框架。如何基于QoS流的框架对双链接场景下的数据传输进行管理,并提高数据传输的质量,是业界亟待解决的问题。
发明内容
本申请提供一种通信方法、装置和***,以期能够提高通信效率。
第一方面,提供了一种通信方法,包括:节点向终端设备发送第一指示信息,所述第一指示信息用于指示使用第一承载传输第一QoS流,其中,所述节点为主节点或辅节点,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的业务数据适应协议(service data adaptation protocol,SDAP)层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;所述节点通过所述第一承载传输所述第一QoS流。
在本申请实施例中,QoS流可以通过主节点的SDAP层以及辅节点的SDAP层以下的协议层进行传输,或者通过辅节点的SDAP层以及主节点的SDAP层以下的协议层进行传输,提高了QoS流使用传输路径的灵活性,进而提高了通信效率。
在一种可能的实现方式中,所述第一承载对应的协议栈还支持通过第二路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,所述第二路径为所述主节点和所述终端设备之间的路径;或所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,所述第二路径为所述辅节点 和所述终端设备之间的路径。
在一种可能的实现方式中,还包括:所述节点向所述终端设备发送路径指示信息,所述路径指示信息用于指示所述第一QoS流的路径传输模式,所述路径传输模式为使用所述第一路径单独传输所述第一QoS流,使用所述第二路径单独传输所述第一QoS流,或使用所述第一路径和所述第二路径共同传输所述第一QoS流。
在本申请实施例中,通过无线接入网的配置,终端设备和节点之间可以使用一条路径传输QoS流,也可以使用两条路径传输QoS流。既实现了无线接入网基于QoS流级别的集中控制和管理,也提高了通信***的灵活性。
在一种可能的实现方式中,所述节点向所述终端设备发送路径调整信息,所述路径调整信息用于指示更改所述第一QoS流的路径传输模式。
在本申请实施例中,通过发送路径调整信息,能够动态地调整QoS流的路径传输模式,提高了基于QoS流的传输效率。
在一种可能的实现方式中,所述路径指示信息承载于以下任一项:无线资源控制(radio resource control,RRC)层信令、SDAP层信令和媒体介入控制(media access control,MAC)层信令。
在一种可能的实现方式中,还包括:所述节点向所述终端设备发送配置指示信息,所述配置指示信息用于指示所述终端设备:在满足第一预设条件的情况下,使用所述第一路径单独传输所述第一QoS流;或,在满足第二预设条件的情况下,使用所述第二路径单独传输所述第一QoS流;或,在满足第三预设条件的情况下,使用所述第一路径和所述第二路径共同传输所述第一QoS流。
在本申请实施例中,通过预配置的方式指示QoS流使用的路径传输模式,终端设备可以根据配置指示信息中指示的预设条件选择QoS流的路径传输模式,提高了基于QoS流的传输效率。
在一种可能的实现方式中,所述节点向所述终端设备发送重复传输指示信息,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
在本申请实施例中,通过发送重复传输指示信息,可以灵活地配置QoS流的重复传输模式,提高了基于QoS流的传输效率。
在一种可能的实现方式中,还包括:所述节点向所述终端设备发送重复传输停止指示信息,所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
在一种可能的实现方式中,所述第一QoS流包括的SDAP协议数据单元(protocol data unit,PDU)的帧头中包括序列号,所述序列号用于指示所述SDAP PDU的排序。
在本申请实施例中,为第一QoS流包括的SDAP PDU的帧头中设置序列号,以便于识别在不同路径中传输的数据包,提高基于QoS流的通信传输效率。
在一种可能的实现方式中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,包括:所述第一路径通过所述主节点的SDAP层以及所述辅节点的分组数据汇聚协议(packet data convergence protocol,PDCP)层以及PDCP层以下的协议层,或,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的 协议层,包括:所述第一路径通过所述辅节点的SDAP层以及所述主节点的PDCP层以及PDCP层以下的协议层。
第二方面,提供了一种通信方法,包括:终端设备接收第一指示信息,所述第一指示信息用于指示使用第一承载传输第一QoS流,其中,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;所述终端设备通过所述第一承载传输所述第一QoS流。
在本申请实施例中,QoS流可以通过主节点的SDAP层以及辅节点的SDAP层以下的协议层进行传输,或者通过辅节点的SDAP层以及主节点的SDAP层以下的协议层进行传输,提高了QoS流使用传输路径的灵活性,进而提高了通信效率。
在一种可能的实现方式中,所述第一承载对应的协议栈还支持通过第二路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,所述第二路径为所述主节点和所述终端设备之间的路径;或所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,所述第二路径为所述辅节点和所述终端设备之间的路径。
在一种可能的实现方式中,还包括:所述终端设备接收路径指示信息,所述路径指示信息用于指示所述第一QoS流的路径传输模式,所述路径传输模式为使用所述第一路径单独传输所述第一QoS流,使用所述第二路径单独传输所述第一QoS流,或使用所述第一路径和所述第二路径共同传输所述第一QoS流。
在一种可能的实现方式中,还包括:所述终端设备接收路径调整信息,所述路径调整信息用于指示更改所述第一QoS流的路径传输模式。
在一种可能的实现方式中,所述路径指示信息承载于以下任一项:RRC层信令、SDAP层信令和MAC层信令。
在一种可能的实现方式中,还包括:所述终端设备接收配置指示信息,所述配置指示信息用于指示所述终端设备:在满足第一预设条件的情况下,使用所述第一路径单独传输所述第一QoS流;或,在满足第二预设条件的情况下,使用所述第二路径单独传输所述第一QoS流;或,在满足第三预设条件的情况下,使用所述第一路径和所述第二路径共同传输所述第一QoS流。
在一种可能的实现方式中,还包括:所述终端设备接收重复传输指示信息,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
在一种可能的实现方式中,还包括:所述终端设备接收重复传输停止指示信息,所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
在一种可能的实现方式中,所述第一QoS流包括的SDAP协议数据单元PDU的帧头中包括序列号,所述序列号用于指示所述SDAP PDU的排序。
在一种可能的实现方式中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,包括:所述第一路径通过所述主节点的SDAP层以及所述辅节点的分组数据汇聚协议PDCP层以及PDCP层以下的协议层,或,所述第一路径通过所述 辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,包括:所述第一路径通过所述辅节点的SDAP层以及所述主节点的PDCP层以及PDCP层以下的协议层。
第三方面,提供了一种节点,该节点用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地,该节点包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面,提供了一种终端设备,该终端设备用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地,该终端设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第五方面,提供了一种节点,该节点包括:通信接口、存储器和处理器。其中,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面,提供了一种终端设备,该终端设备包括:通信接口、存储器和处理器。其中,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制该通信接口接收信号和/或发送信号,并且当该处理器执行该存储器存储的指令时,该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面,提供了一种通信***,该通信***包括上述第三方面所述的节点和第四方面所述的终端设备,或者,该通信***包括上面第五方面所述的节点和第六方面所述的终端设备。
第八方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第九方面,提供了一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十方面,提供了一种芯片,用于存储指令,当所述芯片在节点上运行时,使得所述芯片执行第一方面或第一方面的的任意可能的实现方式中的方法。
第十一方面,提供了一种芯片,当所述芯片在终端设备上运行时,使得所述芯片执行第二方面或第二方面的任意可能的实现方式中的方法。
图1是本申请实施例的网络架构的示意图。
图2是本申请实施例的双链接场景的示意性架构图。
图3是相关技术的承载类型的应用场景示意图。
图4是相关技术中的QoS流传输路径示意图。
图5是本申请实施例的承载类型的应用场景示意图。
图6是本申请又一实施例的承载类型的应用场景示意图。
图7是本申请又一实施例的承载类型的应用场景示意图。
图8是本申请实施例的QoS流传输路径示意图。
图9是本申请又一实施例的QoS流传输路径示意图。
图10是本申请实施例的通信方法的交互示意图。
图11是本申请又一实施例的承载类型的应用场景示意图。
图12是本申请实施例的SDAP帧格式的示意图。
图13是本申请又一实施例的SDAP帧格式的示意图。
图14是本申请又一实施例的SDAP帧格式的示意图。
图15是本申请MAC层信令格式的示意图。
图16是本申请实施例的节点的结构示意图。
图17是本申请实施例的终端设备的结构示意图。
图18是本申请又一实施例的节点的结构示意图。
图19是本申请又一实施例的终端设备的结构示意图。
下面将结合附图,对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***,例如:全球移动通讯(global system of mobile communication,GSM)***、码分多址(code division multiple access,CDMA)***、宽带码分多址(wideband code division multiple access,WCDMA)***、通用分组无线业务(general packet radio service,GPRS)、长期演进(long term evolution,LTE)***、LTE频分双工(frequency division duplex,FDD)***、LTE时分双工(time division duplex,TDD)、通用移动通信***(universal mobile telecommunication system,UMTS)、全球互联微波接入(worldwide interoperability for microwave access,WiMAX)通信***、未来的第五代(5th generation,5G)***或新无线(new radio,NR)等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字处理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备,未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network,PLMN)中的终端设备等,本申请实施例对此并不限定。
本申请实施例中的节点(例如,主节点或辅节点)可以是用于与终端设备通信的设备,该节点可以是全球移动通讯(global system of mobile communication,GSM)***或码分多址(code division multiple access,CDMA)中的基站(base transceiver station,BTS),也可以是宽带码分多址(wideband code division multiple access,WCDMA)***中的节点(NodeB,NB),还可以是LTE***中的演进型节点(evolutional NodeB,eNB或eNodeB),或者可以成为LTE节点,还可以是云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器,或者该节点可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的基站或者未来演进的PLMN网络中的节点等,例如,新无线(new radio,NR)节点。本申请实施例并不限定。
如上文所述,5G将支持各种类型的网络部署和应用类型。为了满足上述需求,5G定义了基于服务质量(quality of service,QoS)流(flow)的框架。下面将介绍本申请实施例 涉及到的QoS流的架构。
图1是本申请实施例的一种可能的网络架构100的示意图。网络架构100是QoS流架构的一种可能的实现形式。如图1所示,终端设备可以与核心网(core network,CN)之间建立一个或多个会话。节点可以将属于不同的会话的数据包映射到不同的承载中,将属于同一会话的数据包映射到一个或多个承载中。其中,QoS流是在上述会话中实现QoS区分的最小粒度。同一会话可以包括一个或多个QoS流。可以为每个QoS流分配对应的QoS流标识(QoS flow identifier,QFI),一个QFI可以用于指示一个QoS流。在同一会话中具有相同QFI的业务将会接受相同的调度策略或接纳控制。其中,在使用核心网与节点之间的通信接口传输数据包时,数据包的封装头中携带QFI。如图1所示,上述核心网与节点之间的通信接口可以是N3接口,或者,上述核心网与节点之间的通信接口也可以是下一代用户面(next-generation user plane,NG-U)隧道(tunnel)。
需要说明的是,上述会话可以是分组数据单元(packet data unit,PDU)会话,上述承载可以是数据资源承载(data resource bearer,DRB)。其中,上述PDU会话可以是终端设备与数据网络之间建立的连接,上述连接的类型可以是互联网协议(internet protocol,IP)、以太网或其他类型。在一些实施例中,将以上述会话是PDU会话、上述承载是DRB为例对本申请的方法或装置进行描述。此外,上述核心网可以包括核心网设备,核心网设备例如可以包括以下任一:用户面功能(user plane function,UPF)实体、接入和移动性管理功能(access and mobility management function,AMF),会话管理功能(session management function,SMF)。
5G基于DRB定义了空口上的数据包处理机制。由一个DRB服务的数据包在空口传输中具有相同的包处理机制。节点可以与终端设备之间建立多个DRB以满足具有不同包处理需求的QoS流。需要说明的是,同一个DRB可以与一个QoS流具有映射关系,也可以与多个QoS流具有映射关系。具体地,对于下行数据传输(downlink,DL),节点可以基于NG-U隧道(或者说,N3接口)上QFI标识和QFI对应的QoS规则(profile),将QoS流包括的数据包映射到对应的DRB上,并进行下行传输。对应上行数据传输(uplink,UL),终端设备根据预先配置的QoS流与DRB的映射关系,将QoS流包括的数据包映射至对应的DRB上,并进行上行传输。
图2是本申请实施例的双链接场景的示意性架构图。如图2所示,双链接场景中通常包括主节点(master node,MN)和辅节点(secondary node,SN)。其中上述主节点或辅节点也可以分别称为主基站和辅基站。主节点和辅节点可以共同服务于终端设备。或者说,针对于终端设备与核心网建立的同一会话,主节点和辅节点可以与终端设备之间同时进行数据传输。在一种可能的场景中,主节点可以负责与终端设备之间的控制面信令流程以及用户面数据传输,而辅节点只需负责与终端设备之间的用户面数据传输。即主节点可以和终端设备之间建立数据资源承载(data resource bearer,DRB)以及信令资源承载(signal resource bearer,SRB),辅节点只需和终端设备之间建立DRB。或者,在另一种可能的场景中,主节点和辅节点可以同时负责与终端设备之间的控制面传输以及用户面数据传输。即主节点可以与终端设备之间建立DRB以及SRB,辅节点也可以与终端设备之间建立DRB以及SRB。通常情况下,双链接场景中可以包括一个主节点和至少一个辅节点。下文中将以双链接场景中包括一个主节点以及一个辅节点的情形为例进行说明。
示例性地,在双链接场景下,在一些实施例中,上述主节点和辅节点都可以为NR节点。或者,在另一些实施例中,上述主节点可以是LTE中的节点,上述辅节点可以是NR节点。或者,在又一些实施例中,上述主节点可以为NR节点,上述辅节点可以为LTE节点。
图3示出了相关技术的承载类型的示意图。如图3所示,双链接场景下的节点可以支持以下承载类型:MCG承载,MCG分离(split)承载,SCG承载,SCG分离(split)承载。其中,如图3所示,MCG承载对应的路径通过主节点内部的所有协议层;SCG承载对应的路径通过辅节点内部的所有协议层;MCG分离承载对应的路径通过主节点的SDAP层、PDCP层以及辅节点的无线路径控制(radio link control,RLC)层以及RLC层以下的协议层。SCG分离承载对应的路径通过辅节点的SDAP层、PDCP层以及主节点的RLC层以及RLC层以下的协议层。
图3示出了节点内部的部分协议层,其由上至下依次包括:SDAP层、PDCP层、RLC层以及MAC层。无线接入协议体系中通常分为三层,层一为物理(physical,PHY)层,层二为数据链路(data link)层,层三为RRC层。其中,数据链路层由下至上依次包括以下子层:MAC层、RLC层以及PDCP层。在本申请实施例中,在PDCP层之上还存在SDAP协议层。其中,上述SDAP层功能包括并不限于:用于处理QoS流到DRB的映射。在一些实施例中,节点或终端设备内部的协议层并不限于图3所示的协议层。其可能包括更多或更少的协议层。或者各协议层的名称也可能有所不同。例如,在一种可能的协议层架构中,可以不包括上述PDCP层。
在图3中,由于SDAP层用于处理QoS流到承载之间的映射,因此在传输至PDCP层之前,QoS流已经先映射至承载。对于MCG分离承载和SCG分离承载,现有技术在PDCP层进行路径选择,其仅支持基于承载粒度的路径选择,不能进行基于QoS流粒度的路径选择。换句话说,当决定了QoS流映射到哪种类型的承载时,就决定了经由哪条路径进行传输。对于单个的QoS流而言,无法为其实现基于QoS流粒度的路径选择,或者说无法为某个QoS流自主选择路径进行传输。此外,在该方案下,当网络决定该QoS流映射到其他类型承载时,需要告知核心网进行路径转换,因此引入了额外的信令开销。
图4示出了相关技术中的MCG分离承载的传输路径的示意图。使用SCG分离承载传输的过程与之类似,此处不再赘述。由图3和图4可见,MCG分离承载包括两条路径,其中一条路径通过主节点的PDCP层以及辅节点PDCP层以下的协议层;另一条路径为主节点与终端设备之间的路径,即该路径经过主节点中的协议层且没有经过辅节点中的任何协议层。继续参见图4,下行传输时,在主节点的SDAP层中,第一QoS流(即图4中的QoS流1)和第二QoS流(即图4中的QoS流2)均映射至第一DRB(即图4中的DRB1)。在主节点中的PDCP层,当分配PDCP PDU到上述两条路径时,由于第一QoS流和第二QoS流均映射至第一DRB,无法根据PDCP PDU分辨出QoS流信息,因此无法进行基于QoS流级别的分配,只能进行PDCP PDU级别的路径分配。相应地,在上行传输中,终端设备的PDCP层也无法分辨出QoS流信息,从而无法进行QoS流级别的分配,只能进行PDCP PDU级别的路径分配。
本申请实施例旨在提供一种通信方法,以实现在无线接入网(radio access network,RAN)中基于QoS流粒度的路径选择,或者说实现为某个QoS流自主选择路径进行传输。 本申请提供的通信方法适用于双链接场景或者多链接场景。例如,可以适用于连接到5G核心网的双链接场景。
本申请实施例提出了一种基于QoS流粒度的承载方案。该承载方案支持通过第一路径传输QoS流。其中第一路径通过主节点的SDAP层以及辅节点的SDAP层以下的协议层,或者,该第一路径通过辅节点的SDAP层以及主节点的SDAP层以下的协议层。上述承载方案既可以应用于上行传输的场景,也可以应用于下行传输的场景。
其中,上述SDAP层以下的协议层是指SDAP层以下的全部协议层且不包括SDAP层,例如,SDAP层以下的协议层包括PDCP层、RLC层以及MAC层。
进一步地,该承载方案还可以支持通过第二路径传输QoS流,其中,在第一路径通过主节点的SDAP层以及辅节点的SDAP层以下的协议层的情况下,第二路径为主节点与终端设备之间的路径;在第一路径通过辅节点的SDAP层以及主节点的SDAP层以下的协议层的情况下,第二路径为辅节点和终端设备之间的路径。
其中,上述第二路径为主节点与终端设备之间的路径,是指该第二路径仅经过主节点的协议层以及终端设备的协议层,其未经过辅节点中的任何协议层。类似地,上述第二路径为辅节点与终端设备之间的路径,是指该第二路径仅经过辅节点的协议层以及终端设备的协议层,其未经过主节点的任何协议层。
在本申请实施例中,QoS流可以通过主节点的SDAP层以及辅节点的SDAP层以下的协议层进行传输,或者通过辅节点的SDAP层以及主节点的SDAP层以下的协议层进行传输,提高了QoS流使用传输路径的灵活性,进而提高了通信效率。
进一步地,由于QoS流在SDAP层进行路径选择,因此,可以在为QoS流选择路径后,再将QoS流映射至承载,从而能够基于QoS流的粒度选择路径,提高了数据传输的灵活度和效率。
图5至图7分别示出了本申请实施例的三种可能的应用场景方案。根据支持的路径或路径数不同,该承载方案具体可以包括多种承载类型。例如,图5-图7中示出了本申请实施例引入的第一类型承载-第六类型承载。
图5示出的第一种应用场景方案的承载类型包括:MCG承载、SCG承载、第一类型承载、第二类型承载、第三类型承载以及第四类型承载。其中,MCG承载或SCG承载使用第二路径传输QoS流;第一类型承载或第二类型承载仅支持使用第一路径传输QoS流;第三类型承载或第四类型承载支持使用第一路径和/或第二路径传输QoS流。具体地,第一类型承载和第三类型承载对应的第一路径通过主节点的SDAP层以及辅节点的SDAP层以下的协议层;第二类型承载和第四类型承载对应的第一路径通过辅节点的SDAP层以及主节点的SDAP以下的协议层;第三类型承载对应的第二路径为主节点与终端设备之间的路径,第四类型承载对应的第二路径为辅节点与终端设备之间的路径。另外,图5至图7中的Xn表示基站之间的通信接口,即主节点和辅节点之间的通信接口。
对于第三类型承载和第四类型承载,可以采取三种路径传输模式传输QoS流,第一种路径传输模式中,使用第一路径传输QoS流;第二种路径传输模式中,使用第二路径传输QoS流;在第三种路径传输模式中,使用第一路径和第二路径共同传输QoS流。进一步地,第三种路径传输模式可以包括两种情况,第一种情况中,使用第一路径和第二路径互相重复传输QoS流。在第二种情况中,使用第一路径和第二路径传输QoS流的不同 数据包,即第一路径和第二路径之间不重复传输QoS流。并且在传输过程中,上述三种路径传输模式还可以进行动态调整,即可以动态地切换路径传输模式。
图6示出的第二种应用场景方案中包括:MCG承载、SCG承载、第三类型承载以及第四类型承载。其中,MCG承载或SCG承载支持使用第二路径传输QoS流;第三类型承载或第四类型承载支持通过第一路径和/或第二路径传输QoS流,并且支持路径传输模式的动态调整。
图7示出的第三种应用场景方案中包括:MCG承载、SCG承载、第五类型承载以及第六类型承载。第五类型承载和第六类型承载支持QoS流通过第一路径、第二路径和/或第三路径进行传输。其中,上述第三路径通过主节点的PDCP层以及辅节点的PDCP层以下的协议层,或通过辅节点的PDCP层以及主节点的PDCP层以下的协议层。上述PDCP层以下协议层是指PDCP层以下的全部协议层。具体地,第五类型承载对应的第一路径、第二路径与第三类型承载相同。第六类型承载对应的第一路径、第二路径与第四类型承载相同。第五类型承载对应的第三路径通过主节点的PDCP层以及辅节点的PDCP层以下的协议层;第六类型承载对应的第三路径通过辅节点的PDCP层以及主节点的PDCP层以下的协议层。
对于第五类型承载和第六类型承载,可以采取多种路径传输模式传输QoS流,例如,使用第一路径单独传输QoS流,使用第二路径单独传输QoS流,使用第三路径单独传输QoS流、使用第一路径和第二路共同传输QoS流、使用第二路径和第三路径共同传输QoS流、使用第一路径和第三路径共同传输QoS流,使用第一路径、第二路径、第三路径共同传输QoS流。并且在传输过程中,上述多种路径传输模式还可以进行动态调整。
需要说明的是,MCG承载、第一类型承载、第三类型承载或第五类型承载均可以归类为主节点终止(MN terminated)的承载,即以上承载对应的协议栈中的SDAP层位于主节点。SCG承载、第二类型承载、第四类型承载和第六类型承载均可以归类为辅节点终止(SN terminated)的承载,即以上承载对应的协议栈中的SDAP层位于辅节点。当然,上述承载无需限制于其名称,也可以采用其他可能的命名方式,本申请对此不作限制。
图8是本申请实施例的传输QoS流的场景示意图。其展示了使用一条路径对单个QoS流进行下行传输的场景。换句话说,在传输的任一时刻,仅在一条路径上传输单个QoS流。其中第一QoS流(QoS流1)映射至第一DRB(DRB1),第二QoS流(QoS流2)映射至第二DRB(DRB2)。上述第一DRB可以是MCG承载,上述第二DRB可以是第一类型承载、第三类型承载或第五类型承载。其中,当第二DRB为第三类型承载或第五类型承载时,其路径传输模式为使用第一路径传输QoS流。因此,第一QoS流包括的数据包将在主节点和终端设备之间的路径上传输。第二QoS流包括的数据包在经由主节点的SDAP层处理之后得到SDAP PDU,然后将SDAP PDU通过节点间的接口传递给辅节点,并由辅节点的SDAP层以下的协议层继续进行下行传输。其中上述节点间的接口可以是Xn接口。相应的上行传输的场景与之类似,不再赘述。
图9是本申请另一实施例的传输QoS流的场景示意图。其展示了使用两条路径共同对单个QoS流进行下行传输的场景。即使用第一路径和第二路径传输第一QoS流(QoS流1)。其中,第一QoS流映射至第一DRB(DRB1)以及第二DRB(DRB2)。在一种实施方式中,同一QoS流映射在一个承载上进行传输,即第一DRB和第二DRB可以是 同一承载。例如可以是第三类型承载或第五类型承载,其路径传输模式为使用第一路径和第二路径共同传输。在另一种实施方式中,同一QoS流可以映射至两个承载中,即第一DRB和第二DRB也可以是不同的承载,例如,第一DRB可以为MCG承载,第二DRB可以为第一类型承载、第三类型承载或第五类型承载。其中,第三类型承载和第五类型承载的路径传输模式为使用第一路径传输QoS流。可以使用第一路径和第二路径互相重复传输第一QoS流。或者,也可以使用第一路径和第二路径分开传输第一QoS流的不同数据包。相应的上行传输的场景与之类似,不再赘述。
另外,对于下行传输而言,终端设备需要从QoS流中,区分出在SDAP层分离的QoS流。对于上行传输而言,节点也需要从QoS流中,区分出在SDAP层分离的QoS流。例如,可以在QoS流包括的SDAP PDU的帧头中增加序列号(serial number),该序列号用于指示SDAP PDU的排序,以使得SDAP层执行重排序功能,从而区分使用不同传输路径的QoS流的不同数据包。
可选地,上述SDAP帧头中的序列号可以采取两种排序方式。在第一种排序方式中,可以为允许在两条路径传输的每个QoS流的SDAP PDU增加独立的序号。在第二种排序方式中,可以为映射到同一承载中的所有QoS流的SDAP PDU增加一致的序列号。进一步地,SDAP层中还可以增加重排序功能,并定义重排序定时器(re-ordering timer)。在一种实现方式中,可以为每个QoS流定义一个重排序定时器。在第二种实现方式中,为允许在两条路径上传递的多个QoS流定义一个重排序定时器。例如,当接收端收到一个新的SDAP PDU时,若重排序定时器正在运行,且触发重排序定时器的SDAP PDU的序列号已被递交到高层,则根据新的SDAP PDU的序列号,重置该重排序定时器;若重排序定时器未启动,且存在至少一个SDAP SDU未被递交到高层,则启动该重排序定时器。
图10是本申请实施例的通信方法1000的流程示意图。该方法1000可以应用于图5-图9的应用场景中,该方法1000包括:
S1001、节点向终端设备发送第一指示信息,相应地,终端设备接收该第一指示信息,所述第一指示信息用于指示使用第一承载传输第一QoS流,其中,所述节点为主节点或辅节点,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的业务数据适应协议SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的业务数据适应协议SDAP层以及所述主节点的SDAP层以下的协议层。
其中,上述SDAP层以下的协议层可以指SDAP层以下的所有协议层,且不包括SDAP层。例如,如图3所示,上述SDAP层以下的协议层包括PDCP层以及PDCP层以下的所有协议层。或者,上述SDAP层以下的协议层包括PDCP层、RLC层、MAC层等。在一些示例中,节点或终端设备内部的协议层并不限于图3所示的协议层。其可能包括更多或更少的协议层。或者各协议层的名称也可能有所不同。例如,在一种可能的协议层架构中,可以不包括上述PDCP层。
可选地,该第一承载可以是上述第一类型承载至第六类型承载中的任一种承载。
上述节点可以是主节点。例如,在第一承载为第一类型承载至第六类型承载中的任一种承载的情况下,均可以由主节点向终端设备发送第一指示信息。或者,上述节点也可以是辅节点,例如,在上述第一承载属于辅节点终止的承载情况下,例如,第二类型承载、 第四类型承载或第六类型承载,可以由辅节点向终端设备发送上述第一指示信息。
可选地,上述第一指示信息可以承载于RRC信令之中。第一指示信息可以包括如下信息:第一承载的标识,第一承载的承载类型以及映射到第一承载的QoS流的信息。承载类型可以为以下任一项:第一类型承载、第二类型承载、第三类型承载、第四类型承载、第五类型承载、第六类型承载。其中,第一指示信息可以明确指示第一承载的类型,或者也可以通过索引的形式或布尔变量的形式指示第一承载的类型。
S1002、所述节点通过所述第一承载传输所述第一QoS流。
其中,上述节点通过第一承载传输第一QoS流,即指将所述第一QoS流映射至所述第一承载进行传输。上述节点使用第一承载进行第一QoS流的传输,可以包括主节点与辅节点协同进行与终端设备之间的上行传输或下行传输。或者也可以包括主节点和辅节点中的其中一个节点与终端设备进行第一QoS流的传输。
在一个实施例中,可以由主节点向终端设备发送第一指示信息,然后由主节点和辅节点协同传输第一QoS流,这种情况下,第一承载可以是第一类型承载-第六类型承载中的任一承载。其中,第三类型承载-第六类型承载中的各承载的路径传输模式可以是使用第一路径传输、或使用第一路径与第二路径共同传输。在另一个实施例中,也可以由辅节点向终端设备发送第一指示信息,然后由主节点和辅节点协同传输第一QoS流,这种情况下,第一承载可以是第二类型承载、第四类型承载、或第六类型承载。其中,第四类型承载和第六类型承载的路径传输模式可以是使用第一路径传输或使用第一路径和第二路径共同传输。
在另一个实施例中,可以由主节点发送第一指示信息,由主节点传输第一QoS流。这种情况下,第一承载为第三类型承载或第五类型承载,且路径传输模式为使用第二路径传输。或者可以由辅节点发送第一指示信息,由辅节点传输第一QoS流。这种情况下,第一承载为第四类型承载-第六类型承载,且路径传输模式为使用第二路径传输。
此外,上述S1001部分和S1002部分也可以由不同的节点执行。例如,还可以由主节点发送第一指示信息,由辅节点传输第一QoS流。在这种情况下,第一承载为第四类型承载或第六类型承载,且第四类型承载或第六类型承载的路径传输模式为使用第二路径传输。
在本申请实施例中,QoS流可以通过主节点的SDAP层以及辅节点的SDAP层以下的协议层进行传输,或者通过辅节点的SDAP层以及主节点的SDAP层以下的协议层进行传输,提高了QoS流使用传输路径的灵活性,进而提高了通信效率。
在一些示例中,从终端设备侧来说,当QoS流映射的承载的底层协议位于主节点时,例如,MCG承载、第二类型承载、或者第三类型承载中的第二路径等,终端设备均通过主节点传输数据;而当QoS流映射的承载的底层协议位于辅节点时,例如,SCG承载、第一类型承载或第三类型承载中的第一路径等,终端设备均通过辅节点传输数据;当QoS流映射的承载的底层协议同时位于主节点和辅节点时,例如,MCG分离承载、SCG分离承载、第三类型承载同时使用第一路径和第二路径时,终端设备通过主节点和辅节点共同传输数据。因此,如图11所示,对于终端设备侧来讲,可以只存在三种承载类型:MCG承载、SCG承载以及分离承载。其中,上述MCG承载指终端设备与主节点传输数据,上述SCG承载指终端设备与辅节点传输数据,上述分离承载指终端设备同时与主节点及辅 节点传输数据。因此,对于节点侧和终端侧来说,其承载类型的分类方式不同。因此,第一指示信息可以根据节点侧的分类方式指示第一承载的类型,也可以根据终端设备侧的分类方式指示第一承载的类型。
在一些示例中,在第一承载为第三类型承载-第六类型承载的情况下,节点还需要进一步配置路径指示信息,以指示第一QoS流的路径传输模式。对于第三类型承载和第四类型承载来说,路径传输模式可以包括:使用所述第一路径单独传输所述第一QoS流,使用所述第二路径单独传输所述第一QoS流,或使用所述第一路径和所述第二路径共同传输所述第一QoS流。尤其对于上行传输来说,节点需要向终端设备指示使用哪条路径传输第一QoS流。在一些示例中,通常由主节点指示终端设备使用哪条路径进行传输。在另一些示例中,也可以由辅节点指示终端设备使用哪条路径进行传输。在一些示例中,可能存在主节点和辅节点同时指示终端设备使用哪条路径进行传输的场景。对于第五类型承载和第六类型承载来说,其具有更多种路径传输模式,详细内容可以参见图7的例子,为了简洁,此处不再说明。
可选地,所述节点还可以向所述终端设备发送路径调整信息,所述路径调整信息用于指示更改所述第一QoS流的路径传输模式。
可选地,路径指示信息、路径调整信息可以采用多种信令格式指示。例如,可以采用RRC层信令、SDAP层信令或者MAC层信令。
在本申请实施例中,通过发送路径指示信息或路径调整信息,动态地指示或调整QoS流的路径传输模式,提高了基于QoS流的传输效率。
可选地,节点可以通过以下三种方案指示或调整QoS流路径传输模式。在第一种方案中,路径指示信息和路径调整信息可以均承载于RRC层信令。例如,路径指示信息可以携带于RRC消息中,路径调整信息可以携带与RRC连接重配置消息中。在一个示例中,该RRC消息包括节点对终端设备的初始配置,该初始配置包括路径指示信息,以指示QoS流的路径传输模式。在后续过程中,节点可以向终端设备发送RRC连接重配置消息,该RRC连接重配置消息中包括路径调整信息,以指示更改或重配置QoS流的路径传输模式。其中,上行传输的QoS流和下行传输的QoS流可以使用相同的路径传输模式行传输,或者也可以使用不同的路径传输模式进行传输。
在第二种方案中,路径指示信息可以承载于RRC信令中,路径调整信息可以承载于SDAP信令中。SDAP信令可以是用于动态切换(switch)路径的命令。例如,可以通过RRC信令初始配置QoS流的路径传输模式,然后基于SDAP命令指示更改QoS流的路径传输模式。通过SDAP信令,实现传输路径的动态调整。在一些实现方式中,上述SDAP信令可以基于SDAP帧实现。其中SDAP帧为SDAP层的PDU,即SDAP PDU。其一般包括帧头以及数据信息,帧头通常用于指示一些控制信息,数据信息则包含上一个协议层传递下来的数据。下文将结合图12-图14,介绍本申请实施例的几种SDAP帧格式的示意图
图12示出了本申请实施例的SDAP帧格式的示意图。如图12所示,SDAP帧中可以包括下列标识:D/C标识、QFI、反射QoS指示(reflective QoS indication,RQI)。其中,QFI表示QoS流的ID,D/C标识表示SDAP PDU是数据包还是控制包(D表示数据包,C表示控制包),RQI为反射QoS指示。例如,若终端设备通过某个下行路径接收到该 SDAP帧,该SDAP帧中的RQI设置为激活(例如,RQI=1表示激活),且D/C指示SDAP PDU为控制包时,则终端设备可以通过与该下行路径相同的上行路径发送对应于该QFI的数据包。另外,该SDAP还可以包括:数据(data)、序列号和预留比特。该序列号表示指示SDAP PDU排序的序列号。R表示预留(reserved)比特。
又例如,图13示出了本申请又一实施例的SDAP帧格式的示意图。如图13所示,SDAP帧中可以包括PDU类型、RQI和D/C标识。其中,PDU类型表示控制域类型。可以通过为定义新的PDU类型以实现对QoS流的路径传输模式的指示,例如,PDU类型的格式可以如下表1所示。
表1
PDU类型 | 控制域类型 |
000 | 流路径切换命令 |
例如,当终端设备接收到该SDAP帧,PDU类型指示流路径切换命令(例如,PDU=000),且RQI设置为激活时(例如,RQI=1表示激活),则终端设备可以通过与该下行路径相同的上行路径发送对应于该QFI的数据包。该SDAP还可以包括:数据(data)和序列号。该序列号指示SDAP PDU的排序。
图14示出了本申请又一实施例中的SDAP帧格式的示意图。如图14所示,SDAP帧中可以包括下列标识:QFI、RQI。例如,若终端设备通过某个下行路径接收到该SDAP帧,该SDAP帧中的RQI设置为激活(例如,RQI=1表示激活),则终端设备可以通过与该下行路径相同的上行路径发送对应于该QFI的数据包。另外,该SDAP还可以包括:数据(data)、序列号和预留比特。
在第三种指示或调整路径传输模式的方案中,节点可以预先为终端设备配置规则,终端设备根据该预设的规则确定当前所使用的路径传输模式。例如,节点可以在初始配置中指示终端设备初始使用的路径传输模式以及预设的规则,在后续过程中,终端设备可以根据预设的规则自行确定当前使用的路径传输模式。或者,节点可以在初始配置中只指示预设规则,终端设备可以根据预设规则确定初始的路径传输模式以及后续的路径传输模式。在一个示例中,所述节点可以向所述终端设备发送配置指示信息,所述配置指示信息用于指示所述终端设备:在满足第一预设条件的情况下,使用所述第一路径单独传输所述第一QoS流;或,在满足第二预设条件的情况下,使用所述第二路径单独传输所述第一QoS流;或,在满足第三预设条件的情况下,使用所述第一路径和所述第二路径共同传输所述第一QoS流。
其中,上述第一预设条件、第二预设条件和第三预设条件可以指节点和终端设备预先约定好的预设条件。若当前条件满足上述预设条件中的某一个时,终端设备使用该预设条件对应的路径传输方式进行第一QoS流的传输。本申请实施例对第一预设条件、第二预设条件和第三预设条件不做具体限定。例如,预设条件可以是与当前网络状态有关的条件,比如当前路径的负载状况,或者第一QoS流的缓冲量(buffer)情况,或者队列等待时间。可以考虑上述当前网络状态中的一个因素或综合考虑多个因素以选择路径传输模式。
在一个具体实施例中,节点在配置指示信息中指示某个QoS流的上行数据分离门限(UL data split threshold),当SDAP层关于该QoS流的缓冲量(buffer)超过该门限时,在两条路径上传输;否则选择一条路径单独传输或在初始配置的路径上传输。在另一个具 体实施例中,当该QoS流在SDAP层的缓冲量、在PDCP层的缓冲量以及在RLC层的缓冲量之和超过该上行数据分离门限时,在两条路径上传输;否则选择一条路径单独传输或在初始配置的路径上传输。在另一个具体实施例中,节点可以在配置指示信息中指示某个QoS流的队列等待时间门限,当该QoS流在终端设备侧队列等待时间超过该时间门限时,在两条路径上传输;否则选择一条路径单独传输或在初始配置的路径上传输。
在本申请实施例中,通过预配置的方式指示QoS流使用的路径传输模式,终端设备可以根据当前网络状态和配置指示信息中指示的预设条件选择QoS流的路径传输模式,提高了基于QoS流的传输效率。
需要说明的是,在上述SDAP帧格式也可以基于承载级别进行定义。例如,可以将上述SDAP帧格式中的QFI替换为承载标识。即映射到该承载的所有QoS流,都可以具有相同的SDAP格式。本申请实施例除了可以支持基于QoS流级别的路径切换之外,也可以支持基于承载级别的路径传输模式选择和调整,即从一种承载类型切换为另一种承载类型,或者说,映射至某一承载的所有QoS流均切换至另一种路径传输模式。
可选地,在一些实施例中,还包括:节点向终端设备发送第一承载切换指示信息,所述第一承载切换指示信息用于指示将第一QoS流映射的承载切换为第二承载。所述第二承载为除所述第一承载之外的任一承载。
在第一承载修改指示信息可以为RRC信令。例如,该RRC信令可以包括如下信息:QoS流将要切换至的第二承载的标识、第二承载的类型以及映射到第二承载的QoS流的信息。该DRB的类型为第一类型承载至第六类型承载中的任一承载。第一承载切换指示信息可以明确指示QoS流将要切换至的承载的类型,或者也可以通过索引的形式或布尔变量的形式指示该DRB的类型。映射到第二承载的QoS流的信息例如可以是QoS流的标识。
进一步地,在第一QoS流的承载类型发生切换的情况下,主节点和辅节点之间可以发送第二承载切换指示信息,以指示第一QoS流的承载类型的发生切换。该第二承载切换指示信息可以通过Xn接口发送。
第二承载切换指示信息可以指示各种承载类型之间的切换。例如,MCG承载与第一类型承载/第三类型承载之间的切换;SCG承载与第二类型承载/第四类型承载之间的切换等,此处不再一一枚举。
另外,若承载切换发生在主节点终止的承载类型之内,例如从MCG承载切换为第一类型承载或第三类型承载,或者辅节点终止的承载类型之内,例如从SCG承载切换为第二类型承载或第四类型承载,由于承载对应的SDAP层及其以上的协议层所在节点并未改变,因此,节点无需向核心网告知进行路径转换,从而节约了信令开销。
在本申请实施例中,通过无线接入网的配置,终端设备和节点之间可以使用一条路径传输QoS流,也可以使用两条路径共同传输QoS流。实现了无线接入网基于QoS流级别的集中控制和管理,提高了通信***的灵活性。
可选地,所述节点还可以向所述终端设备发送重复传输指示信息,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。例如,在第一路径和第二路径共同传输的情况下,节点可以向终端设备进一步发送重复传输指示信息。节点可以根据当前网络状态确定是否允许重复传输。例如,可以根 据不同路径的负载状况确定。当第一路径和第二路径的负载大于预定阈值时,可以确定不允许重复传输。当第一路径和第二路径的负载小于预定阈值时,可以确定允许重复传输。其中上述预定阈值的取值可以根据具体实践确定。
在一些示例中,节点可还以向所述终端设备发送重复传输停止指示信息,所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。或者,在另一些示例中,重复传输指示信息可以用于指示QoS流的初始状态为允许重复性传输或不允许重复传输。后续过程中,所述节点可以向所述终端设备发送重复传输更改信息,所述重复传输更改信息用于指示更改所述第一QoS流的重复传输模式。
或者,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一QoS流。所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径重复传输映射至所述第一QoS流。
在本申请实施例中,通过发送重复传输指示信息,可以灵活地配置映射至第一承载的QoS流的传输路径模式,提高基于QoS流的通信传输效率。
在一些实施例中,可以通过RRC层信令配置上述重复传输指示信息或重复传输停止指示信息。在另一些实施例中,也可以通过SDAP层信令配置上述信息。例如,继续参见图13,可以基于SDAP帧中的PDU类型指示允许重复传输QoS流对应的数据包或指示停止重复传输QoS流对应的数据包。比如,表2示出了PDU类型的另一种可能的定义形式。若PDU类型设置为001时,该SDAP帧指示允许重复传输QoS流对应的数据包,若PDU类型设置为002时,该SDAP帧指示停止重复传输QoS流对应的数据包。
表2
PDU类型 | 控制域类型 |
001 | 数据包重复命令 |
002 | 停止重复传输数据包 |
在另一些实施例中,还可以通过MAC层信令配置重复传输指示信息。例如,图15示出了MAC信令的格式示意图。MAC层信令由MAC子头和MAC控制元素(control element,CE)构成。如图14所示,MAC子头包括逻辑信道标识(logic channel identifier,LCID),其用于指示传输数据的逻辑信道的标识或者MAC层信令的类型。如表3所示,LCID可以为QoS流级别的重复传输定义新的索引值。
表3
索引值(index) | LCID |
100001 | QoS流重复性命令 |
可选地,在一些示例中,MAC子头还可以包括以下信息中的至少一项:R,表示预留比特;L,表示MAC控制元素的长度。F,用于指示L的长度,例如,F=0时,表示L为8个比特,F=1时,标识L为16个比特。
MAC控制元素可以用于指示QoS流是否用于重复性传输。例如,MAC控制元素中可以包括QoS流的索引或QoS流的标识,并指示是否允许该QoS流进行重复性传输。由 于在MAC层信令中,终端设备无法区分MAC信令对应的PDU会话ID。因此,MAC层信令中还需要进一步指示QoS流对应的PDU会话的ID。
如图15中的方式一所示,MAC控制元素中的部分比特P
0,P
1,P
2可以用于指示PDU会话的ID。例如,可以采用三个比特标识PDU会话的索引值。MAC控制元素中的剩余比特Q
0~Q
5可以分别隐式地指示一个QoS流。比特位与QoS流的对应关系可以是预先约定的。例如,可以根据QoS流的ID的大小按序排列,与MAC控制元素的比特位的低位到高位一一对应。上述剩余比特的每个比特的赋值可以用于指示其对应的QoS流是否允许重复传输。例如,假设比特位Q
i指示第i个QoS流。i表示不同的比特位。若Q
i=1,则对应的第i个QoS流为允许重复性传输,Q
i=0则为不允许重复性传输。
如图15中的方式二所示,MAC控制元素也可以不指示PDU会话的ID。可以由MAC子头中的LCID定义新的索引值,以指示PDU会话的ID。与方式一类似,MAC控制元素中的比特位Q
0~Q
8用于分别隐式地指示一个QoS流。可以根据每个比特位的赋值,指示其对应的QoS流是否允许重复传输。
如图15所示的方式三所示:MAC控制元素包括PDU会话ID和QoS流ID,指示对应PDU会话的QoS流ID进行重复性传输或者停止重复性传输。在方式三的一种示例中,初始默认为非重复性传输,当UE收到该命令后,则默认为执行重复性传输命令。在方式三中的另一种示例中,还可以在MAC控制元素中设置额外比特Q指示是否执行重复传输命令,例如若Q=1,则对应的QoS流为进行重复性传输,Q=0则为不允许重复性传输。
本申请实施例提出了一种基于QoS流级别的重复性传输方案。即同一个QoS流对应的数据包,可以通过第一路径和第二路径互相重复传输,从而在无线接入网传输中实现了QoS流粒度的可靠性。
可选地,第一QoS流包括的SDAP PDU的帧头中包括序列号,该序列号用于指示SDAP PDU的排序。例如,图12-图14示出的SDA帧格式均可以包括序列号。在一个示例中,在使用第一路径和第二路径共同传输映射至所述第一承载的QoS流的情况下,发送端可以在SDAP PDU的帧头中增加序列号,在进行QoS流至DRB的映射之后,通过两条路径将SDAP PDU传输给接收端。而接收端在SDAP层接收到来自两个路径的QoS流之后,可以根据SDAP帧头中的序列号进行排序。对于上行传输来说,可以将排序之后的数据包向核心网传递,对于下行传输来说,可以向SDAP层以上的高层递交排序后的数据包。关于序列号的具体内容,可以参见前文描述,此处不再赘述。
在本申请实施例中,为第一QoS流包括的SDAP PDU的帧头中设置序列号,以便于识别在不同路径中传输的数据包,提高QoS流的通信传输效率。
在一些示例中,若使用第一路径和第二路径互相重复传输QoS流对应的数据包,接收端在接收到SDAP PDU之后,可以根据SDAP层的序列号,将重复接收的SDAP PDU丢弃。
可选地,在节点通过第一承载传输第一QoS流的过程中,由于涉及到主节点和辅节点之间的协同传输,因而主节点和辅节点之间也可以通过通信接口进行消息交互。例如,主节点和辅节点之间可以发送QoS流的类型或者QoS流对应的承载类型。或者,主节点和辅节点之间还可以发送QoS流的其他信息。例如,QoS流是否携带有SDAP帧头,SDAP帧头尺寸(SDAP header size),以便于接收数据的节点根据SDAP帧头尺寸执行SDAP 帧头压缩和解压缩功能。又例如,主节点和辅节点之间还可以发送QoS流的QoS参数,或者QoS流与承载之间的映射关系。
本申请提出了节点之间基于QoS流粒度的流量控制。对于归类于主节点终止的承载,例如,第一类型承载、第三类型承载或第五类型承载,主节点可以向辅节点发送基于QoS流的粒度的流控信令。例如,该流控指令可以用于指示如下信息中的至少一项:QoS流标识、指示辅节点报告QoS流状态信息的周期的信息,或者指示辅节点报告QoS流状态信息的触发条件的信息。相应地,辅节点可以周期性地、或根据触发条件向主节点报告其下行传递的QoS流的状态信息,例如:可以在在通用分组无线服务隧道协议用户面(General Packet Radio Service tunneling protocol user plane,GTU-U)的扩展头中包括如下信息中的至少一项:成功传输的SDAP数据包的最大序列号、该QoS流期望的缓存大小。
相应地,对于归类为辅节点终止的承载,例如,第二类型承载、第四类型承载和第六类型承载可以由辅节点向主节点发送基于QoS流粒度的流控信令请求,其相关流程与主节点终止类型的承载类似,此处不再赘述。
在本申请实施例中,基于QoS流粒度的流量控制能够更好的保障Xn接口的流量控制,提升了***性能。
上文结合图1至图15详细描述了本申请实施例的通信方法,下文将结合图16至图19详细描述本申请实施例的节点和终端设备。
图16是本申请实施例的节点1600的示意性框图。应理解,节点1600能够执行图1至图15的方法中由节点执行的各个步骤,为了避免重复,此处不再详述。节点1600包括:处理单元1601和通信单元1602,
所述处理单元1601用于通过所述通信单元1602向终端设备发送第一指示信息,所述第一指示信息用于指示使用第一承载传输第一QoS流,其中,所述节点1600为主节点或辅节点,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;以及通过所述第一承载传输所述第一QoS流。
图17是本申请实施例的终端设备1700的示意性框图。应理解,终端设备1700能够执行图1至图15的方法中由终端设备执行的各个步骤,为了避免重复,此处不再详述。终端设备1700包括:处理单元1701和通信单元1702,
所述处理单元1701用于通过所述通信单元1702接收第一指示信息,所述第一指示信息用于指示使用第一承载传输第一QoS流,其中,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;以及通过所述第一承载传输所述第一QoS流。
图18是本申请实施例提供的节点1800的示意性结构图。如图18所示,节点1800包括:一个或多个处理器1830,一个或多个存储器1810,一个或多个通信接口1820。该处理器1830用于控制通信接口1820收发信号,该存储器1810用于存储计算机程序,该处理器1830用于从存储器1810中调用并运行该计算机程序,使得该节点执行本申请的通信方法的实施例中由节点执行的相应流程和/或操作。为了简洁,此处不再赘述。
图19是本申请实施例提供的终端设备1900的示意性结构图。如图19所示,终端设备1900包括:一个或多个处理器1930,一个或多个存储器1910,一个或多个通信接口1920。该处理器1930用于控制通信接口1920收发信号,该存储器1910用于存储计算机程序,该处理器1930用于从存储器1910中调用并运行该计算机程序,使得该终端设备执行本申请的通信方法的实施例中由终端设备执行的相应流程和/或操作。为了简洁,此处不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (26)
- 一种通信方法,其特征在于,包括:节点向终端设备发送第一指示信息,所述第一指示信息用于指示使用第一承载传输第一服务质量QoS流,其中,所述节点为主节点或辅节点,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的业务数据适应协议SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;所述节点通过所述第一承载传输所述第一QoS流。
- 如权利要求1所述的通信方法,其特征在于,所述第一承载对应的协议栈还支持通过第二路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,所述第二路径为所述主节点和所述终端设备之间的路径;或所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,所述第二路径为所述辅节点和所述终端设备之间的路径。
- 如权利要求2所述的通信方法,其特征在于,所述方法还包括:所述节点向所述终端设备发送路径指示信息,所述路径指示信息用于指示所述第一QoS流的路径传输模式,所述路径传输模式为使用所述第一路径单独传输所述第一QoS流,使用所述第二路径单独传输所述第一QoS流,或使用所述第一路径和所述第二路径共同传输所述第一QoS流。
- 如权利要求3所述的通信方法,其特征在于,所述方法还包括:所述节点向所述终端设备发送路径调整信息,所述路径调整信息用于指示更改所述第一QoS流的路径传输模式。
- 如权利要求3或4所述的通信方法,所述路径指示信息承载于以下任一项:无线资源控制RRC层信令、SDAP层信令和媒体接入控制MAC层信令。
- 如权利要求2所述的通信方法,其特征在于,所述方法还包括:所述节点向所述终端设备发送配置指示信息,所述配置指示信息用于指示所述终端设备:在满足第一预设条件的情况下,使用所述第一路径单独传输所述第一QoS流;或,在满足第二预设条件的情况下,使用所述第二路径单独传输所述第一QoS流;或,在满足第三预设条件的情况下,使用所述第一路径和所述第二路径共同传输所述第一QoS流。
- 如权利要求2-6中任一项所述的通信方法,其特征在于,所述方法还包括:所述节点向所述终端设备发送重复传输指示信息,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
- 如权利要求7所述的通信方法,其特征在于,所述方法还包括:所述节点向所述终端设备发送重复传输停止指示信息,所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
- 如权利要求1-8中任一项所述的通信方法,其特征在于,所述第一QoS流包括的SDAP协议数据单元PDU的帧头中包括序列号,所述序列号用于指示所述SDAP PDU的排序。
- 如权利要求1-9中的任一项所述的通信方法,其特征在于,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,包括:所述第一路径通过所述主节点的SDAP层以及所述辅节点的分组数据汇聚协议PDCP层以及PDCP层以下的协议层,或,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,包括:所述第一路径通过所述辅节点的SDAP层以及所述主节点的PDCP层以及PDCP层以下的协议层。
- 一种通信方法,其特征在于,包括:终端设备接收第一指示信息,所述第一指示信息用于指示使用第一承载传输第一服务质量QoS流,其中,所述第一承载对应的协议栈支持通过第一路径传输QoS流,其中,所述第一路径通过所述主节点的业务数据适应协议SDAP层以及所述辅节点的SDAP层以下的协议层,或者,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层;所述终端设备通过所述第一承载传输所述第一QoS流。
- 如权利要求11所述的通信方法,其特征在于,所述第一承载对应的协议栈还支持通过第二路径传输QoS流,其中,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,所述第二路径为所述主节点和所述终端设备之间的路径;或所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,所述第二路径为所述辅节点和所述终端设备之间的路径。
- 如权利要求12所述的通信方法,其特征在于,所述方法还包括:所述终端设备接收路径指示信息,所述路径指示信息用于指示所述第一QoS流的路径传输模式,所述路径传输模式为使用所述第一路径单独传输所述第一QoS流,使用所述第二路径单独传输所述第一QoS流,或使用所述第一路径和所述第二路径共同传输所述第一QoS流。
- 如权利要求13所述的通信方法,其特征在于,所述方法还包括:所述终端设备接收路径调整信息,所述路径调整信息用于指示更改所述第一QoS流的路径传输模式。
- 如权利要求13或14所述的通信方法,所述路径指示信息承载于以下任一项:无线资源控制RRC层信令、SDAP层信令和媒体接入控制MAC层信令。
- 如权利要求12所述的通信方法,其特征在于,所述方法还包括:所述终端设备接收配置指示信息,所述配置指示信息用于指示所述终端设备:在满足第一预设条件的情况下,使用所述第一路径单独传输所述第一QoS流;或,在满足第二预设条件的情况下,使用所述第二路径单独传输所述第一QoS流;或,在满足第三预设条件的情况下,使用所述第一路径和所述第二路径共同传输所述第一QoS流。
- 如权利要求12-16中任一项所述的通信方法,其特征在于,所述方法还包括:所述终端设备接收重复传输指示信息,所述重复传输指示信息用于指示使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
- 如权利要求17所述的通信方法,其特征在于,所述方法还包括:所述终端设备接收重复传输停止指示信息,所述重复传输停止指示信息用于指示停止使用所述第一路径和所述第二路径互相重复传输映射至所述第一承载的QoS流。
- 如权利要求11-18中任一项所述的通信方法,其特征在于,所述第一QoS流包括的SDAP协议数据单元PDU的帧头中包括序列号,所述序列号用于指示所述SDAP PDU的排序。
- 如权利要求11-19中的任一项所述的通信方法,其特征在于,所述第一路径通过所述主节点的SDAP层以及所述辅节点的SDAP层以下的协议层,包括:所述第一路径通过所述主节点的SDAP层以及所述辅节点的分组数据汇聚协议PDCP层以及PDCP层以下的协议层,或,所述第一路径通过所述辅节点的SDAP层以及所述主节点的SDAP层以下的协议层,包括:所述第一路径通过所述辅节点的SDAP层以及所述主节点的PDCP层以及PDCP层以下的协议层。
- 一种节点,其特征在于,包括用于执行如权利要求1-10中任一项所述的方法的模块。
- 一种终端设备,其特征在于,包括用于执行如权利要求11-20中任一项所述的方法的模块。
- 一种节点,其特征在于,包括:存储器,用于存储计算机指令;通信接口,用于与其他设备进行通信;处理器,用于执行所述存储器中存储的计算机指令,当所述计算机指令被执行时,所述处理器用于执行如权利要求1-10中任一项所述的方法。
- 一种终端设备,其特征在于,包括:存储器,用于存储计算机指令;通信接口,用于与其他设备进行通信;处理器,用于执行所述存储器中存储的计算机指令,当所述计算机指令被执行时,所述处理器用于执行如权利要求11-20中任一项所述的方法。
- 一种可读存储介质,其特征在于,包括指令,当所述指令在节点上运行时,使得所述节点执行如权利要求1-10中任一项所述的方法。
- 一种可读存储介质,其特征在于,包括指令,当所述指令在终端设备上运行时,使得所述终端设备执行如权利要求11-20中任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19741844.5A EP3737145A4 (en) | 2018-01-22 | 2019-01-18 | COMMUNICATION PROCESS, DEVICE AND SYSTEM |
US16/934,490 US11265755B2 (en) | 2018-01-22 | 2020-07-21 | Communication methods, apparatuses, and systems for managing quality of service flows |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810060694.6 | 2018-01-22 | ||
CN201810060694.6A CN110072253B (zh) | 2018-01-22 | 2018-01-22 | 通信方法、装置和*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/934,490 Continuation US11265755B2 (en) | 2018-01-22 | 2020-07-21 | Communication methods, apparatuses, and systems for managing quality of service flows |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019141239A1 true WO2019141239A1 (zh) | 2019-07-25 |
Family
ID=67301255
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/072350 WO2019141239A1 (zh) | 2018-01-22 | 2019-01-18 | 通信方法、装置和*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US11265755B2 (zh) |
EP (1) | EP3737145A4 (zh) |
CN (1) | CN110072253B (zh) |
WO (1) | WO2019141239A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3930404A1 (en) * | 2020-06-22 | 2021-12-29 | T-Mobile USA, Inc. | Simultaneous multi-path uplink transmissions to a telecommunications network |
WO2022051970A1 (en) * | 2020-09-10 | 2022-03-17 | Qualcomm Incorporated | Quality of service flow for communications |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3797486A4 (en) * | 2018-05-22 | 2021-12-29 | Lenovo (Beijing) Limited | Redundant transmission determination |
TWI775013B (zh) * | 2018-11-25 | 2022-08-21 | 財團法人資訊工業策進會 | 基地台及主通訊裝置 |
WO2020146991A1 (zh) * | 2019-01-14 | 2020-07-23 | Oppo广东移动通信有限公司 | 一种数据流处理方法、设备及存储介质 |
US20230106809A1 (en) * | 2019-10-10 | 2023-04-06 | Lenovo (Beijing) Ltd. | Method and apparatus for hop-by-hop flow control |
CN113709821A (zh) * | 2020-05-22 | 2021-11-26 | 华为技术有限公司 | 一种通信方法及装置 |
CN115278546A (zh) * | 2021-04-30 | 2022-11-01 | 维沃移动通信有限公司 | 数据传输方法、相关设备及可读存储介质 |
CN115278654A (zh) * | 2021-04-30 | 2022-11-01 | 维沃移动通信有限公司 | Rrc连接维护方法、相关设备及可读存储介质 |
WO2024011423A1 (zh) * | 2022-07-12 | 2024-01-18 | Oppo广东移动通信有限公司 | 数据处理方法、装置、设备、存储介质及程序产品 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017174550A1 (en) * | 2016-04-05 | 2017-10-12 | Nokia Solutions And Networks Management International Gmbh | Implementing radio access network slicing in a mobile network |
CN107439037A (zh) * | 2017-04-25 | 2017-12-05 | 北京小米移动软件有限公司 | 缓存状态的上报方法及装置 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104468352B (zh) * | 2014-12-26 | 2018-05-01 | 深圳市新格林耐特通信技术有限公司 | 基于sdn的特殊流量qos保障方法 |
TWI651979B (zh) * | 2016-07-07 | 2019-02-21 | 財團法人工業技術研究院 | 無線接取網路之服務區分方法、無線網路系統及無線接取網路存取點 |
WO2018159959A1 (en) * | 2017-03-01 | 2018-09-07 | Lg Electronics Inc. | Method for transmitting tcp ack packet in wireless communication system and a device therefor |
CN108990125B (zh) * | 2017-06-01 | 2020-12-22 | 华为技术有限公司 | 数据传输的方法、终端设备和网络设备 |
-
2018
- 2018-01-22 CN CN201810060694.6A patent/CN110072253B/zh active Active
-
2019
- 2019-01-18 WO PCT/CN2019/072350 patent/WO2019141239A1/zh unknown
- 2019-01-18 EP EP19741844.5A patent/EP3737145A4/en active Pending
-
2020
- 2020-07-21 US US16/934,490 patent/US11265755B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017174550A1 (en) * | 2016-04-05 | 2017-10-12 | Nokia Solutions And Networks Management International Gmbh | Implementing radio access network slicing in a mobile network |
CN107439037A (zh) * | 2017-04-25 | 2017-12-05 | 北京小米移动软件有限公司 | 缓存状态的上报方法及装置 |
Non-Patent Citations (4)
Title |
---|
ERICSSON: "QoS Flow Relocation in NR-DC between MN and SN", 3GPP TSG-RAN WG2 #99BIS, TDOC R2-1711238, 13 October 2017 (2017-10-13), XP051343244 * |
ERICSSON: "TP for 37.340 - Introducing bearer harmonization", 3GPP TSG-RAN WG3 #98 TDOC R3-174745, 1 December 2017 (2017-12-01), XP051373471 * |
HUAWEI ET AL.: "Flow based QoS framework for E-UTRA connected to 5GC", 3GPP TSG-RAN WG2 MEETING #99 R2-1708400, 25 August 2017 (2017-08-25), XP051318264 * |
See also references of EP3737145A4 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3930404A1 (en) * | 2020-06-22 | 2021-12-29 | T-Mobile USA, Inc. | Simultaneous multi-path uplink transmissions to a telecommunications network |
US11330471B2 (en) | 2020-06-22 | 2022-05-10 | T-Mobile Usa, Inc. | Simultaneous multi-path uplink transmissions to a telecommunications network |
WO2022051970A1 (en) * | 2020-09-10 | 2022-03-17 | Qualcomm Incorporated | Quality of service flow for communications |
Also Published As
Publication number | Publication date |
---|---|
EP3737145A1 (en) | 2020-11-11 |
CN110072253B (zh) | 2020-12-18 |
US20200351700A1 (en) | 2020-11-05 |
US11265755B2 (en) | 2022-03-01 |
EP3737145A4 (en) | 2021-02-17 |
CN110072253A (zh) | 2019-07-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019141239A1 (zh) | 通信方法、装置和*** | |
US11696202B2 (en) | Communication method, base station, terminal device, and system | |
US20210289368A1 (en) | Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system | |
US10784998B2 (en) | Wireless communication in multi-rat system | |
US10721754B2 (en) | Data transmission method and apparatus | |
EP3048845B1 (en) | Device and method for data transmission | |
US20200178138A1 (en) | Communication method, base station, terminal device, and system | |
US9319320B2 (en) | Traffic flow establishment method and device and traffic flow modification method and device | |
CN108337633B (zh) | 数据分流配置方法、基站***和用户终端 | |
WO2021056589A1 (zh) | 一种数据传输方法及装置 | |
JP2022527921A (ja) | 通信方法および装置 | |
CN110691425B (zh) | 在移动通信***中的终端、基站及其方法 | |
CN113615293B (zh) | 逻辑信道优先级的协调 | |
WO2024140716A1 (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: 19741844 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019741844 Country of ref document: EP Effective date: 20200803 |