WO2019096044A1 - Procédé, appareil, et système de traitement de flux de données - Google Patents

Procédé, appareil, et système de traitement de flux de données Download PDF

Info

Publication number
WO2019096044A1
WO2019096044A1 PCT/CN2018/114333 CN2018114333W WO2019096044A1 WO 2019096044 A1 WO2019096044 A1 WO 2019096044A1 CN 2018114333 W CN2018114333 W CN 2018114333W WO 2019096044 A1 WO2019096044 A1 WO 2019096044A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
node
stream
terminal
configuration information
Prior art date
Application number
PCT/CN2018/114333
Other languages
English (en)
Chinese (zh)
Inventor
晋英豪
韩锋
谭巍
李宏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019096044A1 publication Critical patent/WO2019096044A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • 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
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a communication method, apparatus, and system, and more particularly to a method, apparatus, and system for processing a data stream.
  • 5G will support various types of network deployments and application types. These include: higher speed experience and greater bandwidth access capabilities, such as enhanced mobile broadband (eMBB); access and management of larger, lower cost machine-like devices, such as large-scale machines Massive machine type communication (mMTC); lower latency and highly reliable information interaction, such as ultra reliable and low latency communication (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra reliable and low latency communication
  • QoS quality of service
  • the embodiment of the invention provides a communication method, device and system, so as to ensure normal communication.
  • a communication method includes the first node transmitting a request message for requesting transfer of the first stream and the second stream to the second node. If the second node accepts the first flow and rejects the second flow, the first node maps the first flow to the first offload bearer and the second flow to the first bearer. The first node notifies the terminal by using a notification message: a mapping relationship between the first stream and the first offloading bearer, and a mapping relationship between the second stream and the first bearer. In a case that the second node accepts the first flow and rejects the second flow, the first node maps the first flow to a first offload bearer and maps the second flow to a first bearer. In this way, the data of the second stream and the first stream can be distinguished by the bearer without confusion. The first node does not send the data of the second stream to the second node. This ensures normal data transmission, thus ensuring normal communication.
  • the first node may be a primary node, and the second node may be a secondary node.
  • the request message may be a secondary node addition request message or a secondary node modification request message.
  • the first node may also be a secondary node, and the second node may also be a primary node.
  • the request message may be an SN modification request message.
  • the first node may also be a centralized unit, and the second node may also be.
  • the request message may be a terminal context setup request message or a terminal context modification request message.
  • the request message carries a bearer type corresponding to the first stream and the second stream, and the bearer type is a offload bearer.
  • the method also includes the first node receiving a response message indicating that the first stream is accepted by the second node and/or the second stream is rejected by the second node.
  • the reference request message carries the bearer type, and the second node can make correct admission control and map the flow to the correct bearer.
  • the response message indicates that the first stream is accepted by the second node and/or the second stream is rejected by the second node, so that the first node is more clear which streams are accepted and which streams are rejected, further securing the first
  • the node maps the first stream and the second stream to the correct, different bearers. Guarantee the normal transmission of data.
  • the response message carries the first configuration information that the second node configures for the first offloading bearer.
  • the notification message further carries one or more of the following: the second node is the first configuration information configured by the first offloading bearer, and the first node is the first The second configuration information of the offloading bearer configuration and the third configuration information that the first node is configured for the first bearer.
  • the terminal can understand the latest configuration information after the mapping between the flow and the bearer, ensuring normal data transmission and improving data transmission performance.
  • the first node maps the first stream to a first offload bearer and maps the second stream to a first bearer
  • the first stream and the second stream are The first node is mapped to the second bearer.
  • the identifier ID of the first offload bearer is the same as the ID of the second bearer.
  • the second node needs to correspond the first bearer configuration information to the ID of the first offload bearer. If the first offload bearer ID and the second bearer ID are the same, the ID of the second bearer may be sent to the second in the request message.
  • the node so that the second node can correspond the first configuration information to the ID of the second bearer without requiring an additional process for notification. This saves signaling overhead and improves data transmission efficiency.
  • the ID of the first bearer is allocated when the first node maps the second stream to the first bearer.
  • the first bearer is a new bearer, which can better meet the QoS requirements of the second stream.
  • the first bearer is a bearer that has been established by the first node. In this case, it is no longer necessary to assign an ID to the first bearer, which can save resources.
  • the request message further carries first indication information, where the first indication information is used to indicate the granularity of the second node to perform admission control.
  • the first node informs the second node of the granularity of the admission control by using the first indication information, and prevents the second node from determining the granularity of the access control by itself.
  • the second node is prevented from performing partial stream access, so as to ensure normal data transmission.
  • the granularity of the admission control is the flow granularity.
  • the granularity of the admission control is the bearer granularity.
  • a communication method includes: receiving, by the terminal, a notification message from the first node, where the notification message carries a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the terminal maps the first stream to a first offload bearer and the second stream to a first bearer. In this way, when the terminal transmits the data of the second stream and the first stream, the terminal can distinguish by the bearer without confusion.
  • the terminal does not send the data of the second stream to the second node. This ensures normal data transmission, thus ensuring normal communication.
  • the notification message further carries one or more of the following: the second node is the first configuration information configured by the first offloading bearer, and the first node is the first offloading bearer.
  • the method further includes: configuring, by the terminal, one or more of the first configuration information, the second configuration information, and the third configuration information.
  • the terminal maps the first stream to a first offload bearer and maps the second stream to the first bearer
  • the first stream and the second stream are Mapped by the terminal to the second bearer.
  • the identifier ID of the first offload bearer is the same as the ID of the second bearer.
  • an apparatus in a third aspect, includes a processing element.
  • the processing element is configured to send a request message for requesting transfer of the first stream and the second stream to the second node. If the second node accepts the first stream and rejects the second stream, the processing component is further configured to map the first stream to the first offload bearer and the second stream to the first bearer; The processing component is further configured to notify the terminal by using a notification message: a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the device may be a communication device such as a network device, or a communication chip.
  • the request message carries a bearer type corresponding to the first stream and the second stream, and the bearer type is a offload bearer.
  • the processing element is further configured to receive a response message indicating that the first stream is accepted by the second node and/or the second stream is rejected by the second node.
  • the notification message further carries one or more of the following: the second node is the first configuration information configured by the first offloading bearer, and the processing component is the first offloading
  • the second configuration information of the bearer configuration and the processing element are third configuration information of the first bearer configuration.
  • the processing element maps the first stream to a first offload bearer and maps the second stream to a first bearer
  • the first stream and the second stream are The processing element is mapped to the second bearer.
  • the identifier ID of the first offload bearer is the same as the ID of the second bearer.
  • the ID of the first bearer is allocated when the processing element maps the second stream to the first bearer, or the first bearer is a bearer that the processing element has established.
  • the request message further carries first indication information, where the first indication information is used to indicate the granularity of the second node to perform admission control.
  • the granularity of the admission control is the flow granularity.
  • the device also includes a radio frequency device.
  • the processing component is further configured to notify the terminal by using a notification message, including: the processing component notifying the terminal by sending the notification message by using the radio frequency device.
  • an apparatus in a fourth aspect, includes a processing element.
  • the processing component is configured to obtain, from the notification message from the first node, a mapping relationship between the first flow and the first offload bearer, and a mapping relationship between the second flow and the first bearer.
  • the processing component is further configured to map the first stream to a first offload bearer and map the second stream to a first bearer.
  • the device may be a communication device such as a terminal, or a communication chip.
  • the processing component is further configured to: acquire one or more of the following: the first configuration information configured by the second node for the first offloading bearer, the first The second configuration information configured by the node for the first offload bearer and the third configuration information that the first node is configured for the first bearer.
  • the processing component is further configured to configure according to one or more of the first configuration information, the second configuration information, and the third configuration information carried in the notification information. .
  • the processing element is further configured to map the first stream and the first stream before mapping the first stream to a first offload bearer and mapping the second stream to a first bearer The second stream is mapped to the second bearer.
  • the identifier ID of the first offload bearer is the same as the ID of the second bearer.
  • a radio frequency device is also included.
  • the processing component is configured to obtain, from the notification message from the first node, a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer, where the processing component is further used to pass the radio frequency
  • the device receives the notification message, where the notification message includes: a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • a communication method includes the first node transmitting a request message for requesting transfer of the first stream and the second stream to the second node.
  • the offloading carries the configuration information of the configuration. If the first node cannot map the first stream and the second stream to different bearers, the first node sends a notification message to the terminal, where the notification message carries the configuration information and indication information, where the indication The information is used to instruct the terminal to ignore the configuration information.
  • the first node cannot map the first stream and the second stream to different bearers, the first node cannot establish a corresponding offload bearer. And carry out normal configuration. If the terminal is not instructed to make the terminal ignore the configuration information, the terminal configures according to the configuration information, and the terminal may transmit the uplink data to the second node, but the second node does not establish a corresponding offload bearer. It is also impossible to transmit the data packets carried by the offload to the core network, which will result in data loss and waste of air interface resources. This method can effectively avoid this situation and ensure the normal transmission of data.
  • a communication method includes the terminal receiving a notification message from a first node, the notification message carrying configuration information and indication information.
  • the configuration information is configured by the second node to accept the first flow and reject the second flow, and is configured for the offload bearer corresponding to the first flow.
  • the indication information is used to instruct the terminal to ignore the configuration information. The terminal ignores the configuration information.
  • an apparatus in a seventh aspect, includes a processing element.
  • the processing element is for transmitting a request message.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the processing component is further configured to receive a response message sent by the second node. If the first stream is accepted and the second stream is rejected, the response message carries configuration information that the second node is configured for the offloading bearer corresponding to the first stream. If the processing element is unable to map the first stream and the second stream to different bearers, the processing element is further configured to send a notification message to the terminal, where the notification message carries the configuration information and the indication information. The indication information is used to instruct the terminal to ignore the configuration information.
  • an apparatus in an eighth aspect, includes a processing element.
  • the processing component is configured to receive a notification message sent by the first node, where the notification message carries configuration information and indication information.
  • the configuration information is configured by the second node to accept the first flow and reject the second flow, and is configured for the offload bearer corresponding to the first flow.
  • the indication information is used to instruct the terminal to ignore the configuration information.
  • the processing element is also operative to ignore the configuration information.
  • a communication method includes the first node sending a request message to a second node, the request message for requesting to transfer the first stream and the second stream to the second node.
  • the first configuration information of the bearer configuration is distributed. If the first node cannot map the first stream and the second stream to different bearers, the first node notifies the second node: information about the second stream, information about the offloaded bearer, And at least one of the information of the first stream.
  • the first node cannot map the first stream and the second stream to different bearers, the first node cannot establish a corresponding offload bearer. And carry out normal configuration. Notifying, by the first node, the second node: at least one of information of the second stream, information of the first offload bearer, and information of the first stream, that the second node may be deleted as
  • the first traffic distribution corresponding to the first flow carries the first configuration information of the configuration and the corresponding reserved resources, thereby improving resource utilization.
  • the request message carries a bearer type corresponding to the first stream and the second stream, and the bearer type is a offload bearer.
  • the first node notifying the second node includes: the first node notifying the second node by using an SN reconfiguration complete message.
  • the first node notifying the second node includes: the first node notifying the second node by using a second request message, where the second request message is used to request the The two nodes delete or modify the first configuration information.
  • the first node receives a second response message of the second node, where the second response message is used to notify that the first configuration information has been deleted, or the first configuration information Has been modified.
  • a communication method includes the second node receiving a request message sent by the first node, the request message being used to request to transfer the first stream and the second stream to the second node.
  • the first configuration information of the configuration is carried. If the first node cannot map the first stream and the second stream to different bearers, the second node receives: information about the second stream, information about the offloaded bearer, and the first flow At least one of the information.
  • the receiving, by the second node includes: the second node receiving the message through the SN reconfiguration.
  • the receiving, by the second node includes: the second node is received by a second request message, where the second request message is used to request the second node to delete or modify the first configuration. information.
  • the method further includes: the second node sending a second response message to the first node, where the second response message is used to notify that the first configuration information has been deleted, or The first configuration information has been modified.
  • a communication device in an eleventh aspect, includes a processing element.
  • the processing element is configured to send a request message to the second node, the request message being used to request to transfer the first stream and the second stream to the second node.
  • the processing component is further configured to receive a response message sent by the second node, if the first flow is accepted, the second flow is rejected, and the response message carries the second node as the first flow The corresponding traffic distribution configuration first configuration information. If the processing element is unable to map the first stream and the second stream to different bearers, the processing element is further configured to notify the second node: information of the second stream, information of the offloading bearer And at least one of the information of the first stream.
  • the processing element is configured to notify the second node, comprising: the processing element to notify the second node by an SN reconfiguration complete message.
  • the processing element is configured to notify the second node, comprising: the processing component is configured to notify the second node by using a second request message, where the second request message is used to request a location
  • the second node deletes or modifies the first configuration information.
  • the processing component is further configured to receive a second response message of the second node, where the second response message is used to notify that the first configuration information has been deleted, or the first The configuration information has been modified.
  • an apparatus in a twelfth aspect, includes a processing element.
  • the processing element is configured to receive a request message sent by the first node, the request message being used to request to transfer the first stream and the second stream to the processing element.
  • the processing component is further configured to send a response message to the first node. If the first stream is accepted and the second stream is rejected, the response message carries the first configuration information that the processing component is configured for the offloading bearer corresponding to the first stream. If the first node cannot map the first stream and the second stream to different bearers, the processing component is further configured to receive: information about the second stream, information about the first offload bearer, and At least one of the information of the first stream.
  • the processing element is for receiving, comprising: the processing element for completing message reception by SN reconfiguration.
  • the processing element is for receiving, comprising: the processing element for receiving by a second request message.
  • the second request message is used to request the processing component to delete or modify the first configuration information.
  • the processing component is further configured to send a second response message to the first node, where the second response message is used to notify that the first configuration information has been deleted, or the first The configuration information has been modified.
  • a communication method includes the first node transmitting a request message to a second node.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the request message carries a bearer type corresponding to the first stream and the second stream, where the bearer type is a traffic bearer, and the request message further carries first indication information, where the first indication information is used to indicate the
  • the second node performs information on the granularity of admission control.
  • the first node can clearly inform the second node of the granularity of the admission control, and avoid the signaling overhead caused by the second node adopting the wrong access control granularity.
  • the second node adopts the flow granularity access control to accept only the first flow and rejects the second flow, and the first node cannot map the first flow and the second flow to different bearers, then the first node The first stream and the second stream cannot be properly configured, resulting in configuration errors and data transfer errors. This error can be avoided by the first indication. Guarantee the normal transmission of data.
  • the first node receives a response message sent by the second node, and the response message is used to respond to the request message.
  • the granularity of the admission control is the flow granularity.
  • the indication information is specifically used to indicate that one or more bearers in the offloading bearer perform admission control of flow granularity.
  • the granularity of the admission control is the bearer granularity.
  • the indication information is specifically used to indicate that all bearers in the offloaded bearer perform flow granularity admission control.
  • a communication method includes the second node receiving a request message sent by the first node.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the request message carries a bearer type corresponding to the first stream and the second stream.
  • the bearer type is a split bearer.
  • the request message further carries first indication information, where the indication information is used to indicate information about the granularity of admission control by the second node.
  • the second node performs admission control with reference to the first indication information.
  • an apparatus in a fifteenth aspect, includes a processing element.
  • the processing element is configured to send a request message to the second node.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the request message carries a bearer type corresponding to the first stream and the second stream.
  • the bearer type is a split bearer.
  • the request message also carries first indication information.
  • the first indication information is used to indicate that the second node performs granularity of admission control.
  • the processing component is further configured to receive a response message sent by the second node, where the response message is used to respond to the request message.
  • an apparatus in a sixteenth aspect, includes a processing element.
  • the processing component is configured to receive a request message sent by the first node.
  • the request message is for requesting transfer of the first stream and the second stream to the processing element for use.
  • the request message carries a bearer type corresponding to the first stream and the second stream.
  • the bearer type is a split bearer.
  • the request message further carries first indication information, which is used to indicate information used by the processing element to perform granularity of admission control.
  • the processing component is further configured to perform admission control with reference to the first indication information.
  • a communication method includes the first node transmitting a request message to a second node.
  • the request message is for requesting to transfer a third stream to the second node.
  • the request message carries a set of bearer IDs that can be used by the second node or a set of bearer IDs that the first node has used.
  • the first node receives a response message sent by the second node.
  • the response message is a response to the request message.
  • the second node can directly use the bearer ID in the bearer ID set by using the request message to inform the second node of the set of bearer IDs available.
  • the second node can avoid using the bearer ID that the first node has used, and directly use its available bearer ID. In this way, no additional requests are required, thereby reducing the overhead of signaling and improving data transmission efficiency.
  • the number of IDs in the set of bearer IDs that the second node can use is a first threshold or a second threshold or a third threshold.
  • the first threshold is the number of the third stream.
  • the second threshold is the number of available bearers.
  • the third threshold is a smaller of the first threshold and the second threshold.
  • the number of available bearers is the difference between the maximum number of bearers that can be established by the terminal and the number of bearers currently established by the terminal.
  • the response message carries a set of IDs of bearers not used by the second node in a set of IDs that can be used by the second node, or carries a bearer used by the second node. Collection of IDs.
  • the response message is used to inform the MN side of the unused DRB ID, so that the MN side can continue to allocate the DRB IDs to the newly added bearers, thereby improving the utilization efficiency of the DRB ID.
  • the bearer type corresponding to the third stream is a secondary cell group bearer or a secondary cell component stream bearer.
  • a communication method includes the second node receiving a request message sent by the first node.
  • the request message is for requesting to transfer a third stream to the second node.
  • the request message carries a set of bearer IDs that can be used by the second node or a set of bearer IDs that the first node has used.
  • the second node sends a response message to the first node.
  • the response message is a response to the request message.
  • an apparatus in a nineteenth aspect, includes a processing element.
  • the processing element is configured to send a request message to the second node.
  • the request message is for requesting to transfer a third stream to the second node.
  • the request message carries a set of bearer IDs that can be used by the second node or the processing element is used for a set of used bearer IDs.
  • the processing component is further configured to receive a response message sent by the second node, where the response message is a response to the request message.
  • an apparatus in a twentieth aspect, includes a processing element.
  • the processing component is configured to receive a request message sent by the first node.
  • the request message is used to request to transfer the third stream.
  • the request message carries a set of bearer IDs that the device can use or a set of bearer IDs that cannot be used.
  • the processing component is further configured to send a response message to the first node.
  • the response message is a response to the request message.
  • the apparatus further includes In the storage element of the stored program, the program is called by the processing element.
  • a computer readable storage medium is provided.
  • the computer readable storage medium is for storing a program.
  • the program is called by a processing element, it is used to perform the method as described in any one of the above-mentioned first, second, fifth, sixth, ninth, tenth, thirteenth, fourteenth, seventeenth or eighteenth aspects.
  • a program product in a twenty second aspect, includes a computer program.
  • the computer program is stored in a readable storage medium, the processing element can read the computer program from the readable storage medium, the processing element executing the computer program to perform the first, second, fifth, sixth, Method according to any of the nine, ten, thirteenth, fourteenth, seventeenth or eighteenth aspects
  • a twenty-third aspect a communication device comprising the method for performing any one of the foregoing first, second, fifth, sixth, ninth, tenth, thirteenth, fourteenth, seventeenth or eighteenth aspects
  • the unit or means of each step in the process comprising the method for performing any one of the foregoing first, second, fifth, sixth, ninth, tenth, thirteenth, fourteenth, seventeenth or eighteenth aspects.
  • the processing element is used to send a message, and it can be understood that the processing element sends a message directly or sends a message through a radio frequency device. As long as the processing component outputs a message, it can be considered to have sent a message.
  • the processing element is configured to receive the message, and it can be understood that the processing element receives the message directly or receives the message through the radio frequency device. As long as the processing component enters a message, it can be considered to have received the message.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a possible implementation form of a communication system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a communication system employing dual connections according to an embodiment of the present invention.
  • 4A is a block diagram showing the architecture of a protocol stack in a dual connectivity scenario, in accordance with one embodiment of the present invention.
  • 4B is a block diagram showing the architecture of a protocol stack in a dual connectivity scenario, in accordance with another embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a secondary node accepting a flow in a dual connectivity scenario, in accordance with an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a communication method according to an embodiment of the present invention.
  • Figure 7 is a schematic illustration of mapping performed in accordance with one embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • Figure 12 is a schematic diagram of the separation of a centralized unit and a distributed unit in a communication system.
  • FIG. 13 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a communication apparatus according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of another communication apparatus according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application.
  • the wireless communication system includes a terminal 120, an access network (AN) device 140, and a core network (CN) device 160.
  • the terminal and the AN device are connected through an air interface.
  • the AN device and the CN device can be connected by wire or wirelessly.
  • the structure of the above wireless communication system is merely an example.
  • the embodiments of the present application are applicable to other wireless communication systems in addition to the above-described wireless communication system, for example, a Long Term Evolution (LTE) system, a next-generation 5G mobile communication system, or a new communication system that will appear in the future.
  • LTE Long Term Evolution
  • 5G mobile communication system a new communication system that will appear in the future.
  • the terminals involved in the embodiments of the present application may include various handheld devices, in-vehicle devices, wearable devices, or computer devices having wireless communication functions.
  • the terminal may be an MS (Mobile Station), a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, or a tablet.
  • MS Mobile Station
  • PDA personal digital assistant
  • MTC Machine Type Communication
  • the AN device in the embodiment of the present application may be a device for communicating with the terminal, or a device that communicates with the terminal through a remote antenna or RRU.
  • the AN device may be an evolved base station (Evolutional NodeB, hereinafter referred to as "eNB or eNodeB") in the LTE system, or may be a wireless control in a cloud radio access network (CRAN) scenario.
  • the AN device may be a relay station, an access point, an in-vehicle device, a wearable device, and an AN device in a future 5G network, or may be an AN device in a future evolved network.
  • the AN device may also be a Next-generation Node B (gNB), a Transmit and Receive Point (TRP), a Central Unit (CU), or a Distributed Unit (Distributed Unit). , referred to as DU) and so on.
  • the CN device may be a User Plane Function (UPF).
  • the CN device may also be a control plane functional entity, such as an Access and Mobility Management Function (AMF).
  • AMF Access and Mobility Management Function
  • FIG. 2 is a possible implementation form of a wireless communication system according to an embodiment of the present application.
  • the terminal can establish one or more sessions with the core network device.
  • the flow is the minimum granularity of quality of service (QoS) in the above session.
  • the access network device may map flows belonging to different sessions to different bearers, or may map flows belonging to the same session to one or more bearers.
  • the foregoing session may be a packet data unit (PDU session), and the bearer may be a data resource bearer (DRB).
  • DRB data resource bearer
  • the above stream may be a QoS stream or a data stream.
  • the base station can establish multiple DRBs with the terminal to satisfy QoS flows with different processing requirements. The same DRB can correspond to one QoS flow or multiple QoS flows.
  • the access network device may include a first node 310 and a second node 320.
  • the first node 310 and the second node 320 collectively provide services to the terminal 330, which can increase the data transmission rate or improve reliability.
  • the first node 310 is a master node (MN)
  • the second node is a secondary node (SN).
  • the master node 310 has a control plane connection and/or a user plane connection with a Core Network (CN) 340 device.
  • the secondary node 320 and the core network 140 may also have a control plane connection and/or a user plane connection.
  • the data of the terminal 330 may be offloaded by the master node 310 to the secondary node 320 at the Packet Data Convergence Protocol (PDCP) layer.
  • the primary node and the secondary node may be a primary access network device and a secondary access network device, or a primary base station and a secondary base station, or a corresponding functional module in the cloud wireless access network.
  • a dual connectivity scenario may include a primary node and at least one secondary node.
  • the following describes an example in which a primary node and a secondary node are included in a dual connectivity scenario. However, this application does not limit the number of secondary nodes.
  • 4A is a block diagram showing the architecture of a protocol stack in a dual connectivity scenario, in accordance with one embodiment of the present invention.
  • 4B is a block diagram showing the architecture of a protocol stack in a dual connectivity scenario, in accordance with another embodiment of the present invention.
  • the MN can support a master cell group (MCG) bearer and a primary cell component bearer (MCG split bearer).
  • MCG split bearer The data on the MCG split bearer is processed by the MN's service data adaptation protocol (SDAP) layer and the PDCP layer.
  • SDAP service data adaptation protocol
  • One is transmitted to the SN through an interface (for example, an Xn interface), and the SN passes its radio link control (RLC) layer, media access control (MAC) layer, and physical (physical, PHY for short). After layer processing, it is transmitted to the terminal.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • the data on the MCG bearer is processed by the MN's own SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer, and then transmitted to the terminal.
  • the data on the MCG split bearer is processed by the SDAP layer, the PDCP layer, and the RLC layer of the MN, and then transmitted in two paths.
  • One is transmitted to the SN (SN) through an interface (for example, an Xn interface), and is processed by the SN through its MAC layer and PHY layer, and then transmitted to the terminal.
  • the other is processed by the MN through its own MAC layer and PHY layer and transmitted to the terminal.
  • the SN can support a secondary cell group (SCG) bearer and a secondary cell component bearer (SCG split bearer).
  • SCG split bearer The data carried on the SCG split bearer is processed by the SDAP layer and the PDCP layer of the SN, and then transmitted in two paths. One is transmitted to the MN through the interface, and is processed by the MN through its RLC layer, MAC layer and PHY layer, and then transmitted to the terminal. The other is processed by the SN through its own RLC layer, MAC layer and PHY layer and transmitted to the terminal.
  • the data on the SCG bearer is processed by the SDAP layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the SN itself, and then transmitted to the terminal.
  • any one of the following protocol layers of the SDAP layer can be offloaded.
  • the data carried on the SCG split bearer is processed by the SDAP layer, the PDCP layer, the RLC layer, and the PHY layer of the SN, and then transmitted in two paths. One is transmitted to the MN through the interface, and is processed by the MN through its MAC layer and PHY layer, and then transmitted to the terminal. The other is processed by the SN through its own MAC layer and transmitted to the terminal.
  • a split bearer can be split at the PDCP layer.
  • the offloading bearer corresponds to one SDAP layer and PDCP layer, and corresponds to two or more RLC/MAC/PHY layers.
  • the corresponding two or more RLC/MAC/PHY layers are distributed over two or more different transport nodes.
  • one SDAP layer and the PDCP layer corresponding to the MCG offloading bearer are distributed in the MN, and the two RLC/MAC/PHY layers corresponding to the MCG offloading bearer are respectively distributed in the MN and the SN.
  • one SDAP layer and a PDCP layer corresponding to the offloading bearer are distributed in the CU, and the corresponding two RLC/MAC/PHY layers are respectively distributed in different DUs.
  • the offloading bearer can also be offloaded at any of the following protocol layers of the SDAP layer. It can be understood that the offloading bearer can also be split in the RLC layer, the MAC layer, or other layers, which is not limited in this application. In this application, we take the PDCP layer shunt as an example.
  • the offloaded bearer can transmit the same data on two or more nodes, and can also transmit different data.
  • the MN needs to forward part of the data stream to the SN for transmission in some cases.
  • the MN may send a SN addition request message or a SN modification request to the SN for requesting to transfer part of the data stream of the MN to the SN for transmission.
  • the message will carry the information of the flow that needs to be transferred (for example, the flow identifier).
  • the SN After the SN receives the request, it must perform admission control. And what kind of granularity to accept control is a problem that needs to be discussed. It now appears that there are two granularities: bearer granularity or flow granularity.
  • a bearer (for example, a DRB) may correspond to one or more flows. If the SN performs admission control based on the bearer granularity, it means that the SN can only accept or reject the transfer of all the flows corresponding to the bearer. For example, stream 1 and stream 2 are mapped on DRB1, and the MN requests stream 1 and stream 2 to be transferred to the SN for transmission by SN addition request or SN modification request. If the SN performs admission control at the bearer granularity, the SN either accepts Flow 1 and Flow 2, or rejects Flow 1 and Flow 2.
  • the SN may receive the partial flow corresponding to the DRB. Of course, all the flows may also be received or rejected at the same time. For example, stream 1 and stream 2 are mapped on DRB1, and MN side requests stream 1 and stream 2 to be transferred to SN for transmission by SN addition request or SN modification request. If the SN is admission control at the flow granularity, the SN may accept Flow 1 and reject Flow 2, or accept Flow 2 and reject Flow 1. Of course, it is also acceptable to accept stream 1 and stream 2, or reject stream 1 and stream 2.
  • a session for example, a PDU session
  • DRB1 DRB1
  • Flow 1 Flow 1
  • Flow 2 Flow 2
  • the SDAP layer of the MN will send the data of stream 1 and stream 2 to the PDCP layer of the MN, and the PDCP layer has no way to distinguish whether the received data belongs to stream 1 or belongs to stream 2. Only the data of stream 1 and stream 2 can be forwarded to the SN, and transmitted by the SN to the terminal through the air interface.
  • the SN is admission control with a bearer granularity, then there is no problem. Assuming that the SN receives both stream 1 and stream 2, since the bearer in the SN and the stream transmitted by the bearer in the MN are the same, the data can be transmitted normally.
  • the SN If the SN is admission control at the flow granularity, it will cause some problems. For example, if the SN accepts the flow 1 and rejects the flow 2, the SN configures the DRB1 of the SN according to the case of the flow 1, and may specifically include the configuration of the RLC, the MAC, and the PHY layer, and/or the configuration of the air interface resource.
  • the flow2 packet since the PDCP layer of the MN cannot distinguish which stream the data received from the SDAP layer belongs to, the flow2 packet may be forwarded to the SN, and the SN may be transmitted through the DRB1 on the SN side. In this case, The SN does not take into account the transmission of stream 2, so its configuration of DRB1 will be unreasonable.
  • the data transmission of stream 2 occupies the resources of data transmission of stream 1, resulting in the SN failing to meet the QoS requirements of data transmission of stream 1.
  • an embodiment of the present invention provides a communication method to ensure normal transmission of data.
  • FIG. 6 is a schematic diagram of a communication method according to an embodiment of the present invention.
  • the communication method can be used in a communication system that includes a first node and a second node that collectively provide services to the terminal.
  • the first node may be the primary node, and the second node may be the secondary node; of course, the first node may be the secondary node, and the second node is the primary node.
  • the first node and the second node can be two separate network devices. In some cases, the first node and the second node may also be integrated into one network device.
  • the method includes the following steps:
  • the first node sends a request message to the second node, and the second node receives the request message.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the request message may carry a bearer type corresponding to the first stream and the second stream, where the bearer type is a split bearer.
  • the offload bearer may be carried by the primary cell component flow bearer or the secondary cell component flow.
  • the request message may further carry the first indication information.
  • the first indication information is used to indicate that the second node performs granularity of admission control.
  • the granularity of admission control can be either flow granularity or bearer granularity.
  • the first indication information is “0” for the second node to perform the admission control of the bearer granularity
  • the first indication information is “1” for the second node to perform the admission control of the flow granularity.
  • the second node performs the admission control of the flow granularity, and does not carry the first indication information, and performs the admission control of the bearer granularity on behalf of the second node. On the contrary, it can be.
  • the first node informs the second node of the granularity of the admission control by using the first indication information, and prevents the second node from using the access control of the flow granularity to perform partial flow access, and cannot guarantee normal data transmission.
  • the first indication information may be used to indicate that the second node performs flow granularity admission control on all bearers.
  • An indication information is used for all bearers, which can reduce the number of indication information and save resources.
  • the first indication information may be used to indicate that the second node performs flow granularity admission control on one or more bearers of all bearers. This allows for more precise admission control.
  • the request message may be a SN addition request message.
  • the secondary node addition request message may carry information of the flow that the MN requests to transfer to the SN, and the MN needs a PDU sessions To Be Added List.
  • the secondary node addition request message may also carry the bearer that needs to be added in each session that needs to be added by the SN, including the MCG offload bearer and/or the SCG bearer.
  • the cells included in the above-mentioned secondary node addition request message may be as shown in any of the following lists 1 to 7.
  • PDU Sessions To Be Added List >PDU Sessions To Be Added Item >>PDU Session ID >>DRB To Be Added List >>>DRB To Be Added Item >>>CHOICE Bearer Option >>>>>Split Bearer >>>>>>DRB ID >>>>>>indicator
  • PDU Sessions To Be Added List means “list of PDU sessions to be added.”
  • PDU session to be Added Item means “items included in the list of PDU sessions to be added (also It may be referred to as an information element.”
  • PDU session ID means “PDU session identifier”, where ID is an abbreviation of identification.
  • DRB To Be Added List means “data bearer to be added.”
  • DRB to be Added Item means “the information element included in the data bearer to be added.”
  • DRB ID means “data bearer identifier.”
  • "CHOICE Bearer Option indicates the type of bearer corresponding to the stream that needs to be transferred. For example, the bearer type corresponding to the flow to be transferred may be selected among the three types of the MCG split bearer, the SCG bearer, and the SCG split bearer.
  • the first indicator is used to indicate the granularity of the secondary base station to perform admission control on a certain offloaded bearer.
  • the bearer type corresponding to the stream to be transferred is a offload bearer.
  • the first indication information is used to indicate the granularity of the secondary base station for admission control of all the offloaded bearers.
  • PDU Sessions To Be Added List >PDU Sessions To Be Added Item >>PDU Session ID >>CHOICE Bearer Option >>>Split Bearer >>>>indicator
  • the first indication information is used to indicate the granularity of the secondary base station to perform admission control on a certain offload bearer.
  • PDU sessions To Be Added List >PDU sessions To Be Added Item >>CHOICE Bearer Option >>>SCG Bearer >>>>PDU session ID >>>Split Bearer >>>>PDU session ID >>>>DRB To Be Added List >>>>DRB To Be Added Item >>>>>DRB ID >>>>>indicator
  • the specific form of the SN addition request message is illustrated by way of example above. Wherein, the cells included in Tables 1 to 7 are not necessarily required in the request message in step S610. For example, the DRB ID may not be used as the case may be. "CHOICE Bearer Option" can be omitted.
  • the foregoing SN addition request message may also be in other forms, which is not limited in this application.
  • the request message may be a secondary node modification request message.
  • the secondary node modification request message may carry information of the flow that the MN requests to transfer to the SN, and the MN needs a PDU sessions To Be Modified List.
  • the secondary node addition request message may also carry a bearer that needs to be modified in each session that needs to be added by the SN, including an MCG offload bearer and/or an SCG bearer.
  • the cells included in the secondary node modification request message can refer to Tables 1 to 7 above.
  • S620 The second node sends a response message to the first node.
  • the first node receives the response message.
  • the response message is for responding to the request message.
  • the second node After receiving the request message, the second node performs admission control.
  • the second node may accept the first stream and reject the second stream.
  • the response message may indicate that the first stream is accepted by the second node and/or the second stream is rejected by the second node.
  • the response message may carry information of the first stream. This may indicate that the first stream is accepted, and the unaccepted stream is the rejected stream.
  • the response message may carry information of the second stream. This may indicate that the second stream is rejected, and the unrejected stream is the accepted stream.
  • the response message may further carry information of the first stream and information of the second stream.
  • the information of the first stream may specifically be the ID of the first stream.
  • the information of the second stream may specifically be the ID of the second stream.
  • the information of the first stream and/or the second stream may be embodied in the form of a list. If the request message in S610 carries the first indication information, the second node may refer to the first indication information when performing the admission control. There are many reasons why the second node accepts a part of the stream and rejects part of the stream, possibly without resources.
  • the response message carries the first configuration information that the second node is configured for the first offloading bearer. Specifically, if the second node receives the partial stream, the response message further carries the first configuration information that the second node is configured for the offloading bearer corresponding to the partial stream. For example, at least one of RLC layer protocol stack configuration information, MAC layer protocol stack configuration information, and PHY layer protocol stack configuration information.
  • the response message may also carry a session successfully accepted by the SN and a successfully accepted bearer included in the successfully accepted session.
  • the first node may perform mapping. Specifically, the first node may map the first stream to the first offload bearer and map the second stream to the first bearer.
  • the first node Before the first node maps the first stream to the first offload bearer and maps the second stream to the first bearer, the first stream and the second stream are mapped by the first node to the second node Hosted.
  • the first stream and the second stream can be mapped to different bearers, thereby avoiding the flow rejected by the second node to the second node, thereby ensuring normal data transmission.
  • the identifier ID of the first offload bearer is the same as the ID of the second bearer.
  • the first bearer can be newly established.
  • the ID of the first bearer is allocated when the first node maps the second stream to the first bearer. It should be noted that this does not necessarily mean that the first node allocates the second stream to the first bearer at this moment, and can also allocate before this moment. It can be understood that other bearer identifier allocation modes may also be adopted, and no limitation is imposed herein.
  • the first bearer may also be a bearer that the first node has established. In this way, the first node does not need to create a new bearer for the second stream.
  • the protocol stacks corresponding to the first bearers are distributed on one node.
  • the first bearer may be an MCG bearer or an SCG bearer.
  • FIG. 7 is a schematic diagram of performing step S630 in accordance with an embodiment of the present patent application.
  • the MN requests to transfer the first stream (Flow 1) and the second stream (Flow 2) corresponding to the second bearer (MCG bearer 1) to the SN, the SN accepts the first stream and rejects the second stream, and the MN maps the first stream to The first shunt bearer (MCG-Split bearer 1).
  • the second stream is mapped to the first bearer (MCG bearer 2).
  • the PDCP layer of the MN will transmit the first stream to the RLC layer of the MN and the RLC layer of the SN.
  • the ID of the MCG-Split Bearer 1 can use the ID of the MCG Bearer 1.
  • the ID of the second bearer is the new ID, which is newly allocated by the MN.
  • the process shown in Figure 7 can also be referred to as remapping.
  • the first stream and the second stream may be streams (eg, MCG bearers) that have been mapped onto the bearer. It can also be a stream that has not been mapped to a bearer.
  • S640 The first node sends a notification message to the terminal.
  • the terminal receives the notification message.
  • the notification message may carry a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the terminal may map the first flow to the first offload bearer and map the second flow to the first bearer.
  • the first stream and the second stream are mapped by the terminal to the second bearer of.
  • the notification message may further carry one or more of the following: the second node is the first configuration information configured by the first offloading bearer, and the first node is configured as the second configured by the first offloading bearer.
  • the first configuration information includes one or more of the following: RLC layer protocol stack configuration information, MAC layer protocol stack configuration information, and PHY layer protocol stack configuration information.
  • the second configuration information includes one or more of the following: SDAP layer protocol stack configuration information, PDCP layer protocol stack configuration information, RLC layer protocol stack configuration information, MAC layer protocol stack configuration information, and PHY layer protocol stack configuration information.
  • the notification message may be a Radio Resource Control (RRC) connection reconfiguration message.
  • RRC Radio Resource Control
  • the foregoing communication method may further include the following steps:
  • the first node determines a granularity of the second node performing admission control.
  • the MN may determine the granularity of the admission control performed by the offload bearer on the SN side according to the current resource usage status, the number of established bearers, and the like.
  • the granularity of admission control can be either bearer granularity or flow granularity.
  • Step S650 is an optional step. It can be triggered on a case-by-case basis. Step S650 can occur before step S610.
  • the foregoing communication method may further include the following steps:
  • S660 The terminal sends a measurement report to the first node.
  • the first node receives the measurement report.
  • the measurement report may carry information about channel conditions between the terminal and the cell included in the second node, for example, reference signal received power (RSRP) or reference signal received quality of the terminal for a certain cell (Reference Signal Received Quality) , RSRQ).
  • RSRP reference signal received power
  • RSRQ Reference Signal Received Quality
  • the measurement result of the corresponding cell beam level may also be included, for example, the identifier of the beam and the beam of the corresponding terminal measurement may be included.
  • RSRP or RSRQ where the identifier of the beam may be indicated by a time-frequency resource of a cell-level reference signal (CRS), or may be indicated by a time index, and may be indicated by other identifiers. .
  • CRS cell-level reference signal
  • the first node may send a request message to the second node. For example, the measurement report indicates that the channel condition of the terminal and the one or more cells of the second node is higher than a certain threshold, and the first node may send an SN increase request to the second node. If the measurement report indicates that the channel condition of the terminal and the one or more cells of the second node is better than the current primary serving cell, the first node may send an SN modification request, requesting to transfer more flows to the second node for transmission. . Of course, the first node may directly proceed to step S610 without performing step S660.
  • FIG. 8 is a schematic diagram of a communication method according to another embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:
  • S810-S820 See the previous description of S610-S620.
  • the notification message may be an RRC Connection Reconfiguration message.
  • the MN wishes to transfer the stream 1 and the stream 2 to the SN.
  • Stream 1 and Stream 2 currently belong to MCG DRB1.
  • the MN expects the SN to establish an MCG-Split bearer for the MCG DRB1.
  • the SN only accepts stream 1, and performs the configuration of the MCG-Split bearer for stream 1.
  • the SN informs the MN that the flow 1 is accepted, the flow 2 is rejected, and the SN is the first configuration information of the MCG-Split bearer configuration. After the stream 1 is accepted by the SN, the MN needs to map it to the MCG-Split bearer.
  • the notification message in step 830 carries the second indication information. After receiving the second indication information, the terminal ignores the first configuration information. That is, the terminal does not perform the relevant configuration corresponding to the first configuration information.
  • the MN actively deletes the stream 2 in the MCG DRB1, and informs the terminal through step 830, so that the MCG-split bearer for the MCG DRB1 is the same as the SN and the MN.
  • the foregoing communication method may further include the following steps:
  • step S840 If the second node accepts the first flow and rejects the second flow, the first node determines whether it can map the first flow and the second flow to different bearers, and if it is determined that it cannot map the first flow and the second flow to On different bearers, step S830 is performed.
  • the MN may determine whether the first stream and the second stream can be mapped to different bearers according to the status of the resource.
  • the foregoing communication method may further include steps S850 and/or S860.
  • S850 refer to the foregoing description of the S650.
  • S860 refer to the foregoing description of the S660.
  • FIG. 9 is a schematic diagram of a communication method according to another embodiment of the present invention. As shown in Figure 9, the method includes the following steps:
  • S910-S920 Refer to the previous description of S610-S620.
  • the message carries at least one of the following: information of the second stream, information of the first offload bearer, and information of the first stream.
  • the information of the second stream may include the identifier information of the second stream
  • the information of the first stream bearer may include the identifier information of the first stream
  • the information of the first stream may include the identifier information of the first stream.
  • the first configuration information of the first offloading bearer is not configured at the terminal.
  • the message can also carry reason indication information.
  • the reason indication information may indicate the reason why the first node cannot map the second flow to the bearer, for example, the current number of bearers has reached the upper limit, or the resource is limited.
  • the foregoing communication method may further include the following steps:
  • Step S940 If the second node accepts the first flow and rejects the second flow, the first node determines whether it can map the first flow and the second flow to different bearers, and if it is determined that it cannot map the first flow and the second flow to On different bearers, step S930 is performed. Step S940 can refer to the introduction of step S840.
  • the stream requested to be transferred by the request message in S910 may further include a third stream.
  • the MN requests the SN to change the bearer corresponding to the third flow from the MCG bearer to the SCG bearer by using the request message, or changes the bearer corresponding to the third flow from the MCG bearer to the MCG-Split bearer. If the second node accepts the third flow, and the bearer corresponding to the third flow is configured. Then, the response message in S920 may carry the fourth configuration information that the second node is configured for the bearer corresponding to the third stream.
  • the above communication method may further include the following steps:
  • the first node sends a notification message to the terminal.
  • the terminal receives the notification message.
  • the notification message can be used to inform the terminal that the data of the third stream can be transmitted through the second node.
  • the notification message may carry the fourth configuration information.
  • the notification message may be an RRC Connection Reconfiguration message.
  • the RRC connection reconfiguration message is described as an example in FIG. 9, but is not limited thereto.
  • the notification message in S950 may also be another name.
  • a response message is sent to the first node, where the message is used to inform the terminal that the configuration is completed.
  • the message may be an RRC Connection Reconfiguration Complete message.
  • the RRC connection reconfiguration complete message is described as an example in FIG. 9, but is not limited thereto.
  • the response message in S960 can also be other names.
  • step S950 occurs, step S950 and step S930 have no sequential relationship. Step S930 may be performed first or step S950 may be performed first, or step S930 and step S950 may be performed simultaneously. If step S930 occurs after S960, the type of the notification message in S930 may be an SN reconfiguration complete message.
  • the message in step S930 may also be a command message or a second request message.
  • the command message or the second request message may be a newly defined one signaling message between the first node and the second node. If it is a second request message, step S930 may be used to request the second node to delete or modify the first configuration information. After receiving the message, the second node may delete the first configuration information or accept the rejected flow again. The second node may also modify the first configuration information. If the second node deletes the first configuration information or modifies the first configuration information, the foregoing communication method may further include the following steps:
  • S970 The second node notifies the first node that the first configuration information has been deleted, or the first configuration information has been modified.
  • S970 may be a response message of the second request.
  • the foregoing communication method may further include steps S980 and/or S990.
  • Step S980 can refer to the introduction of step S660.
  • Step S990 can refer to the introduction of step S650.
  • the first node may be a master node, and the second node may be a secondary node.
  • the first node is a secondary node
  • the second node is a primary node.
  • FIG. 10 is a schematic diagram of a communication method according to another embodiment of the present invention.
  • the embodiment of the present invention will be further described with the first node as the secondary node and the second node as the primary node.
  • the method includes the following steps:
  • S1010 The first node (SN) sends a request message to the second node (MN), and the second node receives the request message.
  • the request message is for requesting to transfer the first stream and the second stream to the second node.
  • the request message may be an SN modification request message.
  • the first stream and the second stream are currently mapped to the SCG bearer at the SN.
  • the request message may be used to indicate that the SN wishes to change the SCG bearer to an SCG-Split bearer.
  • the request message may include a mapping relationship between the SCG bearer and the flow that needs to be changed.
  • S1020 The second node (MN) sends a response message to the first node (SN).
  • the first node receives the response message.
  • the response message is for responding to the request message.
  • the MN After receiving the request message, the MN performs admission control.
  • the MN may accept a partial stream and reject another part of the stream.
  • the MN can accept the first stream and reject the second stream.
  • the response message may indicate that the first stream is accepted by the MN and/or the second stream is rejected by the MN.
  • the response message may carry information of the first stream and/or the second stream.
  • the first-class information can be the ID of the first stream.
  • the information of the second stream may specifically be the ID of the second stream.
  • the response message may also carry information of the DRB ID.
  • the number of the DRB IDs may be one or more, or may be the number of rejected streams, or may be the number of available DRB IDs.
  • the SN may map the first flow to the first offload bearer and map the second stream to the first bearer.
  • the SN maps the second stream to the SCG bearer (first bearer) and maps the first stream to the SCG-Split bearer (the first offload bearer).
  • the SN can also be configured for SCG bearers, such as protocol stack parameter configuration.
  • the SN can also modify the configuration information of the SCG-Split bearer.
  • the first bearer may be a bearer newly created by the SN, or may be a bearer originally existing on the SN.
  • the SN sends a notification message to the MN.
  • the MN receives the notification message.
  • the notification message carries a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the notification message may be an SN modification confirmation message.
  • the notification message in the step S1040 may further carry the second configuration information that the SN is configured for the first offloading bearer and the third configuration information that the SN is configured for the first bearer.
  • the message can also carry DRB ID information that is not used by the SN.
  • the message may further include a mapping relationship between the DRB ID of the newly generated SCG bearer and the flow rejected by the MN side.
  • the message may further include the modified configuration information of the SN to the SCG-Split bearer.
  • the MN sends a notification message to the terminal, and the terminal receives the notification message.
  • the notification message carries a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the notification message may further carry one or more of the following: the first configuration information that the MN is configured for the first offloading bearer, the second configuration information that the SN is configured for the first offloading bearer, and the SN is the first A third configuration information carrying a configuration.
  • the notification message in step S1050 may be an RRC connection reconfiguration message. Of course, it may be other types of messages.
  • FIG. 11 is a schematic diagram of a communication method according to another embodiment of the present invention. As shown in FIG. 11, the method includes the following steps:
  • the first node sends a request message to the second node.
  • the second node receives the request message.
  • the request message is for requesting transfer of a third stream to the second node.
  • the request message also carries a set of IDs of bearers that the second node can use or a set of IDs of bearers that the first node has used.
  • the first node can perform unified allocation of the bearer ID, so that the IDs of all bearers established by the first node and the second node for a certain terminal are unique, and the first node is avoided.
  • the bearers allocated by the two nodes for the terminal overlap. Avoid data mapping confusion and ensure normal data transmission.
  • the number of IDs in the set of bearer IDs that the second node can use is a first threshold or a second threshold or a third threshold.
  • the first threshold is the number of the third stream, and the third stream may be one or more.
  • the second threshold is the number of available bearers.
  • the number of available bearers is the difference between the maximum number of bearers that can be established by the terminal and the number of bearers currently established by the terminal.
  • the third threshold is a smaller of the first threshold and the second threshold.
  • the number of IDs in the set of bearer IDs that the second node can use can also be other values.
  • the second node may determine how the third stream is mapped on the second node side. If the set of IDs of the bearers that the second node can use is the first threshold, the second node can be guaranteed to map each third stream to a single bearer according to specific needs. If the set of bearer IDs that the second node can use is a third threshold, the second node knows that the number of bearers to which all third flows are mapped may not exceed a third threshold. For example, the MN side needs to transfer the stream 3a, the stream 3b, and the stream 3c to the SN. If the number of currently available DRB IDs is 4, the MN can carry 3 DRB IDs in the set of DRB IDs, because the SN can only Use 3.
  • the MN can carry 2 DRB IDs in the set of DRB IDs. After receiving the set, the SN can only map the 3 flows to the two bearers. Because the load that can be established has reached the upper limit.
  • the first node may be an MN, and the second node may be an SN.
  • the request message may be an SN addition request or an SN modification request message.
  • the bearer type corresponding to the third stream is an SCG bearer or an SCG split bearer.
  • S1120 The second node sends a response message to the first node, where the first node receives the response message.
  • the second node decides to receive the third flow, and creates a bearer, and allocates a bearer ID for the bearer.
  • the assigned bearer ID is an ID in a set of IDs of bearers that the second node can use.
  • the allocated bearer ID is an ID in a set of IDs of bearers used by the second node and the first node to be removed from the set of IDs of bearers that the first node has used.
  • the response message carries a set of IDs of bearers not used by the second node in a set of IDs that can be used by the second node, or an ID of a bearer used by the second node. Collection. If the SN accepts all or part of the third flows that need to be transferred, and maps the flows to the corresponding SCG bearers or SCG split bearers, and assigns DRB IDs to these bearers. If the IDs in the set of bearer IDs that the second node can use are not exhausted, the unused DRB ID sets are returned to the MN in step S1102, so that the MN can continue to use the DRB IDs.
  • step S1102 the DRB ID set used by the SN is returned to the MN, so that the MN can know which DRB IDs are not used by the SN, and thus can continue to use the DRB IDs. This improves the utilization efficiency of the DRB ID.
  • the MN adds an MCG bearer or subsequently transfers a new stream to the SN for use by the SN.
  • the second node may also inform the first node of both the set of IDs of the used bearers and the set of IDs of the used bearers.
  • the second node may further allocate a physical random access channel (PRACH) resource to the terminal.
  • the response message in step S1120 may further include a PRACH resource allocated by the second node to the terminal.
  • the response message may further include an identifier of the beam that the second node specifies for the terminal to initiate the RACH.
  • the identifier of the beam may be indicated by a time-frequency resource of a cell-level reference signal (CRS), or may be indicated by a time index, and may be indicated by other identifiers.
  • CRS cell-level reference signal
  • the response message includes multiple beam identifiers that can initiate the RACH
  • one PRACH resource may be allocated for each beam identifier, or the PRACH resources may be uniformly allocated or the PRACH resources may be allocated only on part of the beam identifier. It can be understood that if multiple beam identifiers are carried, the second node can sort the multiple beam identifiers. For example, the beam identifier that most favors the terminal for random access is ranked first.
  • the first node sends a notification message to the terminal, and the terminal receives the notification message.
  • the notification message may be an RRC Connection Reconfiguration message.
  • the notification message may include a DRB ID allocated by the SN for the newly established bearer, and the DRB ID is an ID selected by the SN from the DRB ID set.
  • the notification message includes a physical random access channel (PRACH) resource allocated by the second node to the terminal. Based on the received PRACH resources, the terminal can perform non-contention random access, thereby reducing access delay.
  • the notification message may further include an identifier of the beam.
  • the PRACH resource and the beam identifier in step S1130 may be the same as the information in step S1120.
  • the foregoing communication method may further include step S1140.
  • Step S1140 may refer to the introduction of step S660.
  • the request message in step S1110 may further include a measurement report.
  • the SN can know the channel status between the terminal and the cell included in the SN, and can determine which cell to select as the serving cell of the terminal based on the measurement report and the resource usage status of each cell included in the SN.
  • the request message may also carry information of the cell with the best channel condition (one or more).
  • the cell information may be a cell identifier, such as a Cell Global Identifier (CGI) or a Physical Cell Identifier (PCI).
  • CGI Cell Global Identifier
  • PCI Physical Cell Identifier
  • the first node informs the second node by using the request information: the one or more cells with the best channel condition between the terminal and the cell included in the second node.
  • the channel conditions may be arranged in order from good to bad (for example, the cell identifiers are arranged from good to bad to form a cell identification class table), or may be in accordance with channel conditions from poor to good. Arrangement, of course, can also be out of order.
  • the request message in step S1110 may further include information of the beam.
  • the information of the beam may indicate one or more cell beams with the best channel conditions in the one or more cells included in the second node. If it is a plurality of cell beams, it may be arranged in order from good to bad according to channel conditions, or may be arranged in order of difference from good to good according to channel conditions, or may be arranged in disorder.
  • the information of the beam may be the identifier of the beam. If multiple beams are included, the information of the beam may be embodied in the form of a list.
  • FIG. 12 is a schematic diagram of CU-DU separation in a communication system.
  • the access network device may include a CU and a DU.
  • the functions of the original access network device are split, some functions are deployed in one CU, the remaining functions are deployed in the DU, and multiple DUs can share one CU. This saves costs and makes network expansion easy.
  • the CU and the DU are connected through an interface (for example, an F1 interface), and the CU represents an access network through an interface (for example, an Ng interface) and a core network.
  • the sharding of the CU and the DU can be split according to the protocol stack.
  • One possible way is to deploy the SDAP and PDCP layers in the CU, the RLC layer, the MAC layer, and the PHY layer in the DU.
  • FIG. 13 is a schematic diagram of a communication method provided by another embodiment of the present patent application.
  • the CU is the first node
  • DU2 is the second node
  • DU1 is the third node.
  • DU1 is not required.
  • DU1 is required only in a DC scenario.
  • the method includes the following steps:
  • S1310 The CU sends a request message to the DU2, and the DU2 receives the request message.
  • the request message is used to request that the first stream and the second stream be transferred to the DU2.
  • the request message may further carry first indication information, where the first indication information is used to indicate that the second node performs granularity of admission control.
  • the request message may be a terminal context setup request message or a terminal context modification request message. Of course, it can be other message names, which are not limited herein.
  • the request message may be used to request to add DU2 as a new DC transport node, or to request DU2 to modify the configuration of the bearer or session, or to request that the terminal be handed over from DU1 to DU2.
  • the request message may carry DRB identification information or session identification information that needs to be established or modified, and the DRB or the stream included in the session.
  • the request message may also carry the third indication information.
  • the third indication information is used to indicate that it is desired to add the DU2 as a new DC transmission node, or to indicate that it is desired to switch the terminal to the DU2, or to indicate that the terminal is required to initially access the DU2. Different situations can be distinguished by the third indication information. In this way, the second node can prioritize. For example, in the case of limited resources, DU2 preferentially receives the terminal that is initially accessed.
  • step S1310 For the introduction of the request message in step S1310, reference may be made to the specific description in step S610.
  • the DU2 sends a response message to the CU.
  • the CU receives the response message.
  • the response message is for responding to the request message.
  • DU2 After receiving the request message, DU2 performs admission control. DU2 may accept the first stream and reject the second stream. At this time, the response message may indicate that the first stream is accepted by the second node and/or the second stream is rejected by the second node.
  • the response message in step S1320 may be a terminal context setup request reply message or a terminal context modification reply message.
  • the DU2 may also allocate a PRACH resource to the terminal.
  • the response message in step S1320 may further include a PRACH resource allocated by the DU2 for the terminal.
  • the response message may further include a beam identifier that the DU2 specifies for the terminal to initiate the RACH.
  • the response message may further include a beam identifier that the second node specifies for the terminal to initiate the RACH.
  • the beam identifier can be a time index, a CSI time-frequency resource location, or a beam index or other.
  • the message includes multiple beam identifiers that can initiate the RACH
  • one PRACH resource may be allocated for each beam identifier, or the PRACH resources may be uniformly allocated or the PRACH resources may be allocated only on part of the beam identifier.
  • the second node can sort the multiple beam identifiers. For example, the beam identifier that most favors the terminal for random access is ranked first.
  • step S1320 For the description of the response message in step S1320, reference may be made to the specific description in step S620.
  • Step 1330 If the request message in S1310 is for adding DU2 as a new DC transmission node, and DU2 accepts the first stream and rejects the second stream, the CU may map the first stream to one bearer (first offload bearer), and the second stream Map to another bearer (first bearer). Step 1330 can refer to the specific description in step S630.
  • Step 1340 The CU sends a notification message to the terminal.
  • the terminal receives the notification message. If the step S1330 occurs, the notification message may carry a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the notification message may be an RRC Connection Reconfiguration message.
  • the CU can send a notification message to the terminal through DU1 or DU2.
  • Step 1340 can refer to the specific description in step S640.
  • the foregoing communication method may further include the following steps:
  • the CU sends a terminal context modification request message to the DU1.
  • the terminal context modification request message includes a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the second bearer.
  • the DU1 sends a terminal context modification response to the CU.
  • the CU receives the response.
  • the foregoing communication method may further include the following steps:
  • the terminal sends a measurement report to the CU.
  • the CU receives the measurement report.
  • the terminal may send a measurement report to the CU through the DU1 or the DU2.
  • Step S1370 is an optional step. If step S1310 is based on handover, for example, the terminal is switched from DU1 to DU2; or the new DU is added as a new transmission node, for example, adding DU2, so that DU2 and DU1 simultaneously transmit data for the terminal, then Step S1370 may be added before step S1310. If DU1 and DU2 have already served the terminal at the same time, step S1310 merely modifies the context of the terminal, for example, increasing or decreasing the DRB that needs to be supported in DU2, step S1370 may not be needed.
  • the request message in step S1310 may further include a measurement report by which the DU2 may know the channel condition between the terminal and the cell it contains, and thus may be based on the measurement report and each of the self-contained The resource usage status of the cell, etc., determines which cell is selected as the serving cell of the terminal. It is worth noting that this requires the DU2 to be able to read the measurement report.
  • the request message may further include a cell (one or more) with the best channel condition. That is, the CU informs the DU2 through the request information that the one or more cells with the best channel conditions between the terminal and the cell included in the DU2, if it is multiple cells, may be arranged in the order of good to bad according to the channel conditions.
  • the DU2 is notified (for example, the cell identifiers are arranged on the basis of the good to the bad to form the cell identification class table), or the DU2 may be arranged according to the channel conditions in the order of the difference to the good, or the out-of-order notification may be used.
  • the request message in step S1310 may further include information of the beam.
  • the information of the beam may indicate one or more cell beams with the best channel conditions in the one or more cells included in the DU2. If it is a plurality of cell beams, it may be arranged in order from good to bad according to channel conditions, or may be arranged in order of difference from good to good according to channel conditions, or may be arranged in disorder.
  • the information of the beam may be the identity of the beam. If multiple beams are included, the information of the beam can be represented by a list.
  • the CU may also determine the admission control granularity of the DU2.
  • Embodiments of the present application also provide an apparatus for implementing any of the above methods.
  • an apparatus is provided that includes means or means for implementing the various steps performed by a terminal in any of the above methods.
  • another apparatus is provided, including means or means for implementing the various steps performed by one or more of the first node, the second node, and the third node in any of the above methods.
  • the division of the units in the device is only a division of logical functions, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated.
  • the units in the device may all be implemented by software in the form of processing component calls; or may be implemented entirely in hardware; some units may be implemented in software in the form of processing component calls, and some units may be implemented in hardware.
  • each unit may be a separately set processing element, or may be integrated in one chip of the device, or may be stored in a memory in the form of a program, which is called by a processing element of the device and executes the unit.
  • All or part of these units can be integrated or implemented independently.
  • the processing element described herein can be an integrated circuit that has signal processing capabilities. In the implementation process, each step of the above method or each of the above units may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software.
  • a unit in a device can be one or more integrated circuits configured to implement the above methods.
  • the integrated circuit may be an Application Specific Integrated Circuit (ASIC), a digital singnal processor (DSP), a Field Programmable Gate Array (FPGA), or a general array logic (GAL). ), a programmable logic device (PLD), or any combination thereof.
  • ASIC Application Specific Integrated Circuit
  • DSP digital singnal processor
  • FPGA Field Programmable Gate Array
  • GAL general array logic
  • PLD programmable logic device
  • the processing element can be a general purpose processor, such as a central processing unit (CPU) or other processor that can invoke the program.
  • CPU central processing unit
  • these units can be integrated and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • FIG. 14 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device includes a processing component 1410.
  • the processing element 1410 is configured to perform the method performed by the first node or the second node or the third node provided by the above method embodiments.
  • the network device may also include a storage element 1420 for storing a program for the processing element 1410 to invoke.
  • Processing component 1410 may perform some or all of the steps (first manner) performed by the first node or the second node or the third node in the above method embodiments in a manner that invokes the program stored by storage element 1420.
  • the processing component 1410 may also perform some or all of the steps (second mode) performed by the first node or the second node or the third node in the above method embodiment by means of its internal integrated logic circuit in combination with the instructions.
  • some or all of the steps performed by the first node or the second node or the third node in the foregoing method embodiment may also be performed in combination with the first mode and the second mode.
  • the network device may further include a radio frequency device 1430.
  • the processing component can receive/send an air interface message through the radio frequency device 1430.
  • processing component 1420 and radio frequency device 1430 can exchange information via interface 1440.
  • the interface 1440 can be a common public radio interface (CPRI).
  • the network device can also include an antenna 1450.
  • Antenna 1450 is coupled to radio frequency device 1430.
  • the radio frequency device 1430 receives/transmits information through the antenna 1450.
  • the network device includes a processing element 1410.
  • the processing element 1410 is configured to send a request message. For example, processing component 1410 generates a request message and transmits it to the second node via an interface between the first node and the second node. The request message is for requesting to transfer the first stream and the second stream to the second node. If the second node accepts the first stream and rejects the second stream, the processing element 1410 is further configured to map the first stream to the first offload bearer and the second stream to the first bearer. The processing component 1410 is further configured to notify the terminal by using a notification message: a mapping relationship between the first stream and the first offload bearer, and a mapping relationship between the second stream and the first bearer.
  • the notification message further carries one or more of the following: the second node is the first configuration information configured by the first offloading bearer, and the processing component 1410 is configured for the first offloading bearer
  • the second configuration information and the processing component 1410 are third configuration information configured by the first bearer.
  • the processing element 1410 maps the first stream to the first offload bearer and maps the second stream to the first bearer
  • the first stream and the second stream are processed by the processing Element 1410 is mapped to the second bearer.
  • the ID of the first bearer is allocated when the processing component 1410 maps the second stream to the first bearer, or the first bearer is a bearer that the processing component 1410 has established.
  • the processing component 1410 is further configured to notify the terminal by sending a notification message by using the radio frequency device 1430.
  • the radio frequency device here may also be called a radio frequency unit, which may be a dedicated radio frequency circuit or a radio frequency chip.
  • the radio frequency device may be located in a network device or may be located outside the network device and connected to the network device through a wired manner.
  • FIG. 15 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • the terminal includes a processing component 1510.
  • the processing component 1510 is configured to perform the method performed by the terminal provided by the foregoing method embodiments.
  • the terminal may also include a storage element 1520 for storing a program for the processing element 1510 to invoke.
  • the processing element 1510 can execute some or all of the steps (first mode) performed by the terminal in the above method embodiments in a manner that calls the program stored in the storage element 1520.
  • the processing component 1510 may also perform some or all of the steps (second mode) performed by the terminal in the above method embodiment by means of its internal integrated logic circuit in combination with the instructions.
  • some or all of the steps performed by the terminal in the foregoing method embodiment may be performed in combination with the first mode and the second mode.
  • the terminal may further include a radio frequency device 1530.
  • the processing component 1510 is coupled to the radio frequency device 1530, and the processing component 1510 can receive/transmit air interface messages via the radio frequency device 1530.
  • the terminal may also include an antenna 1550.
  • the antenna 1550 is coupled to the radio frequency device 1530.
  • the radio frequency device 1530 receives/transmits information through the antenna 1550.
  • the radio frequency device 1530 can be a dedicated radio frequency circuit or a radio frequency chip.
  • the terminal may further include an input unit 1590.
  • the input unit 1590 can be used to receive numeric or character information input by the user.
  • the input unit 1590 can include a touch panel 1591 and other input devices 1592.
  • the touch panel 1591 also referred to as a touch screen, can collect touch operations on or near the user (such as a user using a finger, a stylus, or the like on the touch panel 1591 or near the touch panel 1591. Operation), and drive the corresponding connecting device according to a preset program.
  • the input unit 1590 can implement the touch panel 1591 by using various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • Input unit 1590 can also include other input devices 1592.
  • other input devices 1592 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
  • the terminal may also include a display unit 1540.
  • the display unit 1540 can be used to display information input by the user or information provided to the user as well as various menus of the terminal.
  • the display unit 1540 can include a display screen 1541.
  • the display screen 1541 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the touch panel 1591 can cover the display screen 1541. When the touch panel 1591 detects a touch operation thereon or nearby, the touch panel 1591 transmits to the processing component 1510 to determine the type of the touch event, and then the processing component 1510 according to the touch event. The type provides a corresponding visual output on display screen 1541.
  • the touch panel 1591 and the display screen 1541 are two separate components to implement the input and input functions of the terminal, in some embodiments, the touch panel 1591 can be integrated with the display 1541. Realize the input and output functions of the terminal.
  • the terminal may also include a Wireless Local Area Networks (WLAN) module 1560 for providing wireless broadband Internet access to the user.
  • the WLAN is a short-range wireless transmission technology.
  • the terminal can access the WLAN hotspot through the WLAN module 1560.
  • the WLAN hotspot can be enabled by the WLAN module 1560 to forward the mobile bandwidth service to other terminals.
  • the WLAN module 1560 can also perform wireless fidelity (WiFi) broadcast and scanning to enable wireless communication with other nearby terminals.
  • WiFi wireless fidelity
  • the terminal may also include a power source 1570 (such as a battery) that supplies power to the various components.
  • a power source 1570 such as a battery
  • the power source may be logically coupled to the processing component 1510 via a power management system to manage functions such as charging, discharging, and power consumption through the power management system.
  • the terminal may also include a Bluetooth module 1580.
  • the Bluetooth module 1580 can establish a connection with the Bluetooth modules of other terminals.
  • the terminal may further include a camera, a speaker, etc., and details are not described herein again.
  • the processing elements described above may be general purpose processors, such as a Central Processing Unit (CPU), or may be one or more integrated circuits configured to implement the above methods.
  • the integrated circuit can be an ASIC, DSP, FPGA, GAL, PLD, or any combination thereof.
  • the above storage element may be a memory or a collective name of a plurality of memories.
  • the memory may include a volatile memory such as a random-access memory (RAM).
  • the memory may also include a non-volatile memory such as a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD).
  • the storage element may also include a combination of the above types of memory.
  • This patent application also provides a chip. Processing elements can be integrated into the chip.
  • the chip can also integrate storage and processing components.
  • the chip can be a SOC chip.
  • the terms "comprises” and “comprises” and “the” and “the” are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.
  • system and “network” are used interchangeably herein.
  • Multiple as referred to herein means two or more.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the term “connected” herein may be a direct connection or an indirect connection.
  • bearing in this context is the transmission channel established by the network to achieve differentiated data transfer. All flows on a bearer do not distinguish between QoS control, have the same packet forwarding processing mode, and perform data transmission according to the transmission protocol corresponding to the transmission channel.
  • the term "stream” herein may refer to a QoS flow generated by a UE or a network.
  • the "stream” can also be a data stream or a business stream.
  • the QoS flow can be viewed as the smallest quality of service division in a session (eg, a PDU session), which is identified using the QoS flow ID.

Landscapes

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

Abstract

L'invention concerne un procédé, un appareil et un système de traitement de flux de données. Le procédé comprend les étapes suivantes : un premier nœud envoie un message de demande à un second nœud pour demander le transfert de flux sur un support au second nœud ; le second nœud réalise une commande d'admission, et décide d'accepter certains flux et de rejeter certains flux ; le premier nœud mappe les flux acceptés par le second nœud à un support de dérivation, et mappe les flux rejetés par le second nœud avec un autre support ; le premier nœud notifie à un terminal la relation de mappage au moyen d'un message de reconfiguration de connexion RRC ; et le terminal utilise la relation de mappage pour effectuer un mappage de flux. Le message de demande peut être une demande d'ajout de nœud secondaire (SN), une demande de modification de SN, une demande d'établissement de contexte de terminal, ou une demande de modification de contexte de terminal ; le premier nœud peut également déterminer la granularité à laquelle le second nœud effectue une commande d'admission, par exemple, une granularité de flux ; le message de demande peut également comporter des informations d'indication, les informations d'indication étant utilisées pour indiquer la granularité de la commande d'admission.
PCT/CN2018/114333 2017-11-17 2018-11-07 Procédé, appareil, et système de traitement de flux de données WO2019096044A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711148248.2A CN109803316B (zh) 2017-11-17 2017-11-17 一种处理数据流的方法、装置及系统
CN201711148248.2 2017-11-17

Publications (1)

Publication Number Publication Date
WO2019096044A1 true WO2019096044A1 (fr) 2019-05-23

Family

ID=66539375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/114333 WO2019096044A1 (fr) 2017-11-17 2018-11-07 Procédé, appareil, et système de traitement de flux de données

Country Status (2)

Country Link
CN (1) CN109803316B (fr)
WO (1) WO2019096044A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312415A (zh) * 2019-07-25 2021-02-02 中国移动通信有限公司研究院 上行数据分流方法及终端
CN118118949A (zh) * 2022-11-30 2024-05-31 华为技术有限公司 一种通信方法以及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104427554A (zh) * 2013-08-29 2015-03-18 中兴通讯股份有限公司 一种协作多流传输数据的方法及基站
CN104469869A (zh) * 2013-09-23 2015-03-25 中兴通讯股份有限公司 一种小小区切换方法和基站
CN104918329A (zh) * 2014-03-13 2015-09-16 中国移动通信集团公司 一种通信处理方法、装置及基站
US20150358945A1 (en) * 2014-01-31 2015-12-10 Telefonaktiebolaget L M Ericsson (Publ) A UE, A Secondary ENB and a Master ENB and Respective Method Performed Thereby for Providing System Information of a Communication System to the UE

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101287285B (zh) * 2007-04-10 2011-12-21 华为技术有限公司 电路域呼叫建立、触发方法、系统及设备
US20120252355A1 (en) * 2011-04-04 2012-10-04 Qualcomm Incorporated Apparatus and method for handing over relays
CN104010370B (zh) * 2014-04-28 2019-07-09 北京邮电大学 异构系统融合控制方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104427554A (zh) * 2013-08-29 2015-03-18 中兴通讯股份有限公司 一种协作多流传输数据的方法及基站
CN104469869A (zh) * 2013-09-23 2015-03-25 中兴通讯股份有限公司 一种小小区切换方法和基站
US20150358945A1 (en) * 2014-01-31 2015-12-10 Telefonaktiebolaget L M Ericsson (Publ) A UE, A Secondary ENB and a Master ENB and Respective Method Performed Thereby for Providing System Information of a Communication System to the UE
CN104918329A (zh) * 2014-03-13 2015-09-16 中国移动通信集团公司 一种通信处理方法、装置及基站

Also Published As

Publication number Publication date
CN109803316B (zh) 2022-04-22
CN109803316A (zh) 2019-05-24

Similar Documents

Publication Publication Date Title
US10925106B2 (en) Mobile communication system, control apparatus, base station, and user terminal supporting dual connectivity
WO2019157885A1 (fr) Procédé et dispositif de communication sous une architecture d'unité distribuée par unité centralisée
WO2019214739A1 (fr) Procédé et dispositif de communication
US9906994B2 (en) Handover method, master base station and slave base station
KR102527135B1 (ko) 통신 방법 및 장치
JP7038815B2 (ja) 通信方法および通信デバイス
JP2022553672A (ja) 無線通信システムにおけるエンドツーエンドのスライシング
WO2019029643A1 (fr) Procédé de communication, station de base, dispositif terminal et système
US20190069247A1 (en) Information Transmission Apparatus and Method and Communication System
CN114079995A (zh) 一种中继管理方法及通信装置
WO2022033543A1 (fr) Procédé de communication de relais, et appareil de communication
US20220217593A1 (en) Communication method and apparatus
WO2018228311A1 (fr) Procédé et dispositif de réorientation de données
WO2019096044A1 (fr) Procédé, appareil, et système de traitement de flux de données
WO2020063401A1 (fr) Procédé de commutation de mode et procédé et appareil de distribution de flux de données
TW201836382A (zh) 通信方法、輔網絡節點和終端
EP4152807A1 (fr) Procédé et appareil de communication
WO2023056938A1 (fr) Procédé de resélection de cellule et appareil de communication
CN116368916A (zh) 用于通信的方法及装置
WO2016091125A1 (fr) Procédé pour améliorer la capacité de traitement d'une station de base, dispositif de bande de base, station de base et système
CN110139324B (zh) 消息传输方法及装置、计算机存储介质
CN113939044A (zh) 一种通信方法和装置
CN114503719A (zh) 一种通信方法、装置和系统
WO2023246746A1 (fr) Procédé de communication et dispositif associé
WO2023141877A1 (fr) Procédés, dispositifs et systèmes pour effectuer un remplacement de tranche de réseau pendant une mobilité

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18879481

Country of ref document: EP

Kind code of ref document: A1