This application relates to wireless communication technology, and in particular to an interactive device and method between a base station and a user equipment.
To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.
The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud Radio Access Networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like.
In the 5G system, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.
Wireless communication is one of the most successful innovations in modern history. Recently, the number of user equipments of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, the demand for wireless data traffic is growing rapidly. In order to meet the rapid growth of mobile data traffic and support new applications and deployments, it is critical to improve the efficiency and coverage of wireless interfaces.
In the 5G network, in order to extend the coverage of the network, the subject of Integrated Access and Backhaul (IAB) is proposed. The main purpose of the subject is to build a multi-hop network architecture, that is, user data is transmitted through one or more intermediate nodes (such as IAB nodes). At the same time, in order to ensure the reliability of user data transmission, in the 5G system, a data packet duplication function (such as Packet Data Convergence Protocol (PDCP) duplication function) is introduced, that is, a data packet may be duplicated into multiple copies, which are then transmitted in the network. When a 5G base station comprises a central unit and a distributed unit, the duplicated data packets may be transmitted between the central unit and the distributed unit through multiple tunnels.
In the prior art, in order to support the duplication function of a user data packet, the enhancement of the central unit and the distributed unit of the base station and the enhancement of the air interface between the base station and the user equipment are mainly considered. However, the data transmission between the central unit and the distributed unit of the base station is performed according to the existing wired network mechanisms. After the introduction of the IAB network, the duplicated data packets need to be forwarded through one or more intermediate nodes, which is done through radio links between the intermediate nodes. Therefore, the prior art does not consider how to forward these duplicated data packets through a radio link. For example, the prior art does not consider how to duplicate the data packets among the intermediate nodes, and how to transmit the data packets received by the node to which the user accesses to other nodes or users.
In addition to the data packet duplication function, for the transmission of control signaling messages (such as RRC messages), the 5G system also introduces the segmentation feature of the control signaling messages. The main function of this feature is to divide a larger control signaling message into multiple segments, and then each of the segments is transmitted by another control signaling message. This feature is proposed to adapt to the limitation of the data packet size in the existing protocol systems. Through the segmentation feature, the control signaling may be efficiently transmitted between the base station and the user equipment, avoiding the problem that the user equipment or the base station cannot be configured due to the limitation of the data packet size. This segmentation feature may be applied not only to common single-hop networks, but also to multi-hop networks (such as IAB networks).
In the prior art, the segmentation feature of the control signaling messages is only for the base station with a non-split structure (that is, the base station is not composed of a central unit and a distributed unit, rather is an integral functional entity). However, when the base station comprises a central unit and a distributed unit, or when a user equipment is served by multiple base stations, since the information in the control signaling messages may be generated by different nodes, and these nodes do not know the limitation of the size of the control signaling messages, the information generated by one of the nodes thus may cause the size of the control signaling messages to exceed the limitation, leading to failure of transmission of the control signaling. Therefore, in the case of a base station split architecture or service by multiple base stations, the prior art still fails to well support the segmentation feature of the control signaling messages.
The aspect of the present disclosure is to address the issue that how to duplicate a data packet of a user and transmitted the duplicated data packets over radios links between intermediate nodes when the user accesses a network through one or more intermediate nodes.
The present disclosure provides a method and apparatus for communication in a communication system supporting integrated access and backhaul (IAB).
The present disclosure comprises four aspects: configuration of user data transmission on base station side; configuration of user data transmission on central unit side of base station; activation and deactivation of downlink data packet duplication; and activation and deactivation of uplink data packet duplication.
According to an aspect of the present disclosure A method performed by a receiving node in a communication system supporting integrated access and backhaul (IAB) is provided, wherein the method may comprise: receiving a configuration request message from a transmitting node; and performing a data duplication configuration on a radio bearer based on the received configuration request message;
Wherein the configuration request message may be a first resource configuration request message, wherein the first resource configuration request message may comprise at least one of the following: first configuration information related to the radio bearer; and first configuration information related to a backhaul link channel, for the receiving node to generate configuration information related to the backhaul link channel.
Alternatively, the configuration request message is a second resource configuration request message, which is used to notify the receiving node of configuration information about downlink data transmission, wherein the second resource configuration request message comprises at least one of the following: the identification information of the radio bearer and the information related to the tunnel of the radio bearer.
Alternatively, the configuration request message may be a first configuration message, which is used to help the receiving node determine a transmission method of user data on the access link, wherein the first configuration message may comprise at least one of the following: indication information of duplication of data; and indication information of the number of copies that data to be duplicated into.
Alternatively, the configuration request message may be a second configuration message, which is used to help the receiving node determine a transmission method of user data on the backhaul link, wherein the second configuration message may comprise at least one of the following: indication information of duplication of data; and indication information of the number of copies that data to be duplicated into.
According to an aspect of the present disclosure, there is provided a receiving node in a communication system supporting integrated access and backhaul (IAB), which may comprise: a transceiver; and a processor configured to receive a configuration request message from a transmitting node through the transceiver, and perform configuration of data duplication on a radio bearer based on the received configuration request message., wherein the receiving node may be a relay node or a distributed unit function of the relay node or a distributed unit of an anchor node or a user plane part of a central unit of the anchor node.
According to an aspect of the present disclosure, there is provided a transmitting node, which may comprise: a transceiver; and a processor configured to: transmit a configuration request message to a receiving node through the transceiver, for the receiving node to perform configuration of duplication of data of a radio bearer, wherein the transmitting node may be a central unit of an anchor node, control plane part of the central unit of the anchor node, or user plane part of the central unit of the anchor node.
According to another aspect of the present disclosure, an advantage of the present disclosure is to ensure that a size of a control signaling message does not exceed a limit among multiple nodes.
A data transmission method among multiple nodes that ensures a size of a control signaling message does not exceed a limit is provided, the method comprising: receiving by a fifth node a configuration request message from a fourth node; and transmitting by the fifth node a configuration response message to the fourth node.
The configuration request message may be a first data configuration request message. The first data configuration request message is used to notify the fifth node of configuration information required in generating information in the control signaling message;
wherein, the first data configuration request message comprises at least one of the following information: first capability information, which is used to indicate whether a node that generates the control signaling message has an ability to perform segmentation; first information indicating a size, which is used to indicate an allowed size of the control information when the fifth node generates the control information; second information indicating a size, which is used to indicate a size of the control information generated by the fourth node; first signaling information, which contains a first control signaling message and/or a second control signaling message generated by the fourth node; and second signaling information, which contains control signaling messages generated by other nodes.
In a further embodiment, the first signaling information may comprise multiple containers, each of which may comprise a second control signaling message that carries a segment of the first control signaling message;
wherein, the configuration response message may be a first data configuration response message, which is used to notify the fourth node of information in the control signaling message generated, and the message comprises at least one of the following information: cause information, a function of which is to indicate cause information of the information contained in the first data configuration response message; and first configuration control information, which is configuration information generated by the fifth node, and information contained in this configuration information may be included in the first control signaling message or the second control signaling message and then transmitted to a user equipment.
In a further embodiment, in the case of the F1 interface, the first configuration control information may comprise multiple DU to CU RRC Information IEs, and these IEs include all the control information required to configure the user; while in the case of the Xn/X2 interface, the first configuration control information may include multiple Secondary Node to Master Node container IEs, and these IEs contain all the control information required to configure the user equipment.
In an embodiment, the fourth node and the fifth node may be a central unit (or control plane part of the central unit) of the base station and a distributed unit of the base station, respectively, and a size limit of the control information generated by the distributed unit is configured by the central unit.
In another embodiment, the information of a size allowed when the distributed unit of the base station generates the control information is configured by OAM, and therefore, the distributed unit may generate control information based on this information.
In another embodiment, the fourth node and the fifth node may be a master node and a secondary node, respectively, or a source node and a target node, respectively.
In another embodiment, the fourth node and the fifth node may be a master node and a secondary node, respectively, or a source node and a target node, respectively, wherein OAM configures the information of the size allowed when the secondary node (or target node) generate the control information.
In another embodiment, the fourth node and the fifth node may be central units (or control plane part of the central units) of a master node (or a source node) and a secondary node (or a target node), respectively; or may be a central unit (or control plane part of the central unit) of a secondary node (or a target node) and a distributed unit of the secondary node (or a target node), respectively.
In another embodiment, the fourth node and the fifth node may be central units (or control plane part of the central units) of a master node (or source node) and a secondary node (or target node), respectively; or may be a central unit (or control plane part of the central unit) of a secondary node (or a target node) and a distributed unit of the secondary node (or the target node), respectively, wherein, a size limit of the control information is set by OAM.
In an embodiment, a method comprises: transmitting by a fourth node a first data configuration request message to a fifth node; and transmitting by the fifth node the received control signaling messages to a user equipment one by one;
Wherein the fourth node and the fifth node may be a central unit and a distributed unit of a base station, respectively.
In a further embodiment, the first data configuration request message comprises first information containing a plurality of segments of the first control signaling message.
In an embodiment, the first data configuration request message may be a DL RRC Message Transfer message of the F1 interface.
In one embodiment, for a dual connectivity scenario, the fourth node may be a master node (or a central unit of the master node, or control plane part of the central unit of the master node), and the fifth node may be a secondary node (or a central unit of the secondary node, or control plane part of the central unit of the secondary node).
In another embodiment, for a handover scenario, the fourth node may be a source node (or a central unit of the source node, or control plane part of the central unit of the source node), and the fifth node may be a target node (or a central unit of the target node, or control plane part of the central unit of the target node).
In another embodiment, the first data configuration request message and the first data configuration response message may be non-user equipment-associated messages. Specifically, they may be: a Xn/X2 Setup Request and a Xn/ X2 Setup Response message, a NG-RAN Node/eNB Configuration Update and a NG-RAN Node/eNB Configuration Update Acknowledge message, respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be user equipment-associated messages. Specifically, they may be: Handover Request and Handover Request Acknowledge messages respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be newly defined messages.
In various embodiments, for a base station with a CU-DU split architecture, the fourth node may be a central unit of the base station, and the fifth node may be a distributed unit of the base station.
According to another aspect of the present disclosure, a method is provided, the method comprising: transmitting by a sixth node a second data configuration request message to a fourth node, transmitting by the fourth node a first data configuration request message to a fifth node, transmitting by the fifth node a first data configuration response message to the fourth node, and transmitting by the fourth node a second data configuration response message to the sixth node.
In a further embodiment, the size limit of the control information used to generate a control signaling message of an appropriate size is set by the master node and/or the central unit of the master node or the control plane part of the central unit of the master node and/or OAM.
In a further embodiment, the sixth node may be a source node or the central unit of the source node, or the control plane part of the central unit of the source node, the fourth node may be the central unit of the target node or the control plane part of the central unit, and the fifth node may be the distributed unit of a target node.
In a further embodiment, the size limit of the control information used to generate a control signaling message of an appropriate size is set by the source node and/or the central unit of the source node and/or the control plane part of the central unit of the source node and/or the OAM.
In a further embodiment, the sixth node may be the master node or the central unit of the master node, or the control plane part of the central unit of the master node, the fourth node may be the central unit of the secondary node or the control plane part of the central unit, and the fifth node may be the distributed unit of the secondary node.
In a further embodiment, the first data configuration request message and the first data configuration response message may be non-user equipment-associated F1 messages. Specifically, they may be: a GNB-CU Configuration Update and a GNB-CU Configuration Update Acknowledge message respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be user equipment-associated F1 messages. Specifically, they may be: a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message, respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be newly defined messages.
In a further embodiment, the second data configuration request message and the second data configuration response message may be non-user equipment-associated messages. Specifically, they may be: a Xn/X2 Setup Request and a Xn/X2 Setup Response message, respectively; or they may be: NG-RAN Node/eNB Configuration Update and NG-RAN Node/eNB Configuration Update Acknowledge message, respectively. In an alternative embodiment, the second data configuration request message and the second data configuration response message may also be user equipment-associated messages. Specifically, they may be: a S-Node Addition/Modification Request and S-Node Addition/Modification Response message, respectively; or they may be: a Handover Request and a Handover Request Acknowledge message, respectively. In an alternative embodiment, the second data configuration request message and the second data configuration response message may also be newly defined messages. According to another aspect of the present disclosure, there is provided a method, the method comprising: transmitting by a fourth node a third data configuration request message to a seventh node, the message being used to transmit configuration information related to user equipment’s handover; and after receiving the above message, transmitting by the seventh node a first handover configuration information related to the handover to a target node.
In a further embodiment, the seventh node may be a node of the core network, which comprises at least one of the following: Access and Mobility Management Function (AMF) and Mobility Management Entity (MME).
In a further embodiment, the third data configuration request message may be a Handover Required message in TS38.413 or TS36.423.
According to another aspect of the present disclosure, there is provided a method, the method comprising: transmitting a fourth data configuration request message by a seventh node to a fifth node, the message being used to transmit configuration information related to user equipment’s handover; and after receiving the above message, generating by the fifth node second handover configuration information related to the handover.
In a further embodiment, the seventh node is a node of the core network, and comprises at least one of the following: AMF and MME.
In a further embodiment, the fourth data configuration request message may be a Handover Request message in TS38.413 or TS36.423.
The embodiments are described below only by referring to the figures to explain various aspects. As used herein, the term “and/or” comprises any and all combinations of one or more of the associated listed items. Expressions such as “at least one” when preceding a list of elements modify the entire list of elements without modifying individual elements of the list, so that expressions of “at least one of a, b, and c” or similar expressions comprise only a, only b, only c, only a and b, only a and c, only b and c, and all of a, b, and c.
The terms used in this specification will be briefly described, and the present disclosure will be described in detail.
Regarding the terms in the various embodiments of the present disclosure, in consideration of the functions of the structural elements in the various embodiments of the present disclosure, general terms that are currently widely used are selected. However, the meaning of terms may be changed according to intentions, judicial precedents, the emergence of new technologies, etc. In addition, in some cases, uncommon terms may be chosen. In such a case, the meanings of the terms will be described in detail in the corresponding part in the description of the present disclosure. Therefore, the terms used in the various embodiments of the present disclosure should be defined based on the meaning and description of the terms provided herein.
Any embodiment disclosed herein may be combined with any other embodiments, and references to “an embodiment”, “some embodiments”, “alternative embodiments”, “various embodiments”, “one embodiment”, etc. are not mutually exclusive, but it is intended to indicate that a particular feature, structure, or characteristic described in connection with this embodiment may be included in at least one embodiment. Such terms used herein do not necessarily all refer to the same embodiment. Any embodiment may be combined inclusively or exclusively with any other embodiment in a manner consistent with the aspects and embodiments disclosed herein.
References to “or” may be construed as inclusive, so that any term described using “or” can indicate any one of a single, more than one, and all of the items.
Terms including ordinal numbers (such as first, second, etc.) may be used to describe various elements, but these elements are not limited by the terms. The above terms are only used to distinguish one element from another element. For example, without departing from the scope of the present disclosure, a first element may be referred to as a second element, and similarly, a second element may also be referred to as a first element. The term “and/or” comprises any combination of multiple related items or any one of the multiple related items.
User equipment (UE) 201 is a terminal device for receiving data. The next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (gNB or an eNB connected to a 5G Core network (5GC) which is also called ng-gNB) that provides UE with an interface for accessing the radio network. An access control and mobility management functional entity (AMF) 203 is responsible for managing the mobility context and security information of the UE. A user plane function entity (UPF) 204 mainly provides functions of a user plane. A session management function entity (SMF) 205 is responsible for session management. A data network (DN) 206 includes services of operators, Internet access and services of third parties.
(a) The number of copies of user data transmitted on the backhaul link is the same as the number of copies transmitted on the access link. As shown in (a) of
(b) The number of copies of user data transmitted on the backhaul link is less than the number of copies transmitted on the access link. As shown in (b) of
(c) The number of copies of user data transmitted on the backhaul link is greater than the number of copies transmitted on the access link. As shown in (c) of
Different from the prior art, the above three methods show that the user data packets will be transmitted between the relay node that the user equipment accesses and the anchor node through the backhaul link. Since the backhaul link is a radio link, the prior art does not have a corresponding mechanism to support the transmission of duplicated data packets on the backhaul link yet, and there is even no corresponding mechanism to support transmission of the duplicated data packets in the backhaul link and access link. Therefore, the present disclosure aims to propose to support transmission of duplicated user data packets on the backhaul link and the access link.
In the NR system, as the functions supported by the system increase, the size of the control signaling messages (such as RRC messages) exchanged between the user equipment and the base station will gradually increase. However, when the control signaling messages are transmitted over the air interface, the size of the data packets is limited (for example, the size of a PDCP SDU containing control signaling messages is 9000 bytes). Therefore, in order to transmit a relatively large control signaling message, NR Rel-16 introduces the control signaling message segmentation feature. Specifically, this feature divides a relatively large RRC message into several smaller data packets, which are then transmitted by multiple RRC messages. Taking the downlink control signaling as an example, the base station divides a larger RRC message (such as RRCReconfiguration or RRCResume) into several data packets, which are then included in multiple RRC messages (such as DLDedicatedMessageSegment) in the form of containers respectively and transmitted to the user equipment. On the user equipment side, the user equipment extracts the data packets contained in these RRC messages, and then assembles them into a complete larger RRC message, and decodes this RRC message.
The message names in the present disclosure are merely examples, and other message names can also be used. The “first”, “second”, etc. in the message names are only used to distinguish different messages, and do not represent the order to transmit the messages.
The different types of nodes involved in the present disclosure include: the base station, a central unit of the base station, control plane part of the central unit of the base stations, user plane part of the central unit of the base station, a distributed unit of the base station, an anchor node, a central unit of the anchor node, control plane part of the central unit of the anchor node, user plane part of the central unit of the anchor node, a distributed unit of the anchor node and a relay node, etc. The above node types are just examples, and the content of the present disclosure is also applicable to other types of nodes.
The data packet duplication function mentioned in the present disclosure is to duplicate a data packet into multiple copies and then transmit them through the network. One embodiment thereof is the duplication of the user data packets of the PDCP layer introduced in the 5G system; but the present disclosure is not limited to this duplication method, and other implementations for duplicating user data may also be applicable.
In the present disclosure, detailed descriptions of steps not related to the present disclosure are omitted.
The present disclosure also uses the following definitions:
Access link: the link used by the user equipment to access the network. If the user equipment accesses the network through the relay node, the access link is the link used by the user equipment to access the distributed unit function of the relay node. In order to implement the transmission of user data on the access link, the network side will provide the user equipment with one or more sets of configuration information (such as RLC-BearerConfig defined in TS38.331). The configuration information comprises at least one of the following information: configuration information of a PDCP entity, configuration information of a RLC entity, and configuration information of a logical channel, etc. In one implementation, the access link channel may represent the PDCP entity and/or RLC entity and/or logical channel used to serve user data; and in another embodiment, the access link channel is used to represent the RLC entity and/or logical channel used to serve user data. The above-mentioned set of configurations is used to configure an access link channel. The network side will configure one or more access link channels for the user equipment. In the prior art, if a radio bearer is not configured with the duplication function, one access link channel is used to serve one radio bearer; and if a radio bearer is configured with the duplication function, two or more access link channels may be configured to serve a radio bearer, each access link channel being used to transmit one copy of a data packet.
Backhaul link: the link used by other nodes that transmit user data. The other nodes may be a node directly connected to the node serving the user equipment access link, or a node that is indirectly connected to the node serving the link accessed by the user equipment (a node connected through one or more nodes). If the user equipment accesses the network through a relay node, the backhaul link is the link used by the mobile terminal function of the relay node. The network side may configure one or more backhaul links to serve a user equipment. For a backhaul link, it may correspond to a set of configuration information. For the content contained in the configuration information, please refer to “Configuration Information related to Backhaul Link” below.
Uplink: the case in which user data is transmitted from the user equipment side to the network side.
Downlink: the case in which user data is transmitted from the network side to the user equipment side.
Configuration Information related to Backhaul Link: this information may include configuration information of one or more backhaul link. For a backhaul link, this information indicates the configuration used when serving user data (such as data on a tunnel). The information comprises at least one of the following information (such as Backhaul Information, BH Information IE in TS38.473):
- Routing identification information (such as routing ID, BAP routing ID). This information indicates the information that needs to be added to the data packet when transmitting data, and furthermore, this information also indicates the routing information used for data transmission. This information comprises path identification information (such as path ID) and/or address information of the target receiving node (such as BAP address). The target receiving node may be the distributed unit of the anchor node or other types of nodes.
- Indication information of backhaul link channel. There may be one or more backhaul link channels, which are the channels on the backhaul link served by a node in the network. In one embodiment, if the node is a distributed unit of an anchor node, the channel is the channel on the backhaul link served by the distributed unit of the anchor node; in another embodiment, if the node is a relay node, the channel is the channel on the backhaul link served by the distributed unit function of the relay node; and in yet another embodiment, if the node is a relay node, the channel is the channel on the backhaul link served by the mobile terminal function of the relay node. For a backhaul link channel, the information comprises at least one of the following information:
Other identification information. This information is used to identify an access link channel.
In the prior art, only one backhaul link is configured for one tunnel (or uplink tunnel). If the above-mentioned “Configuration Information related to Backhaul Link” is included in the configuration of a tunnel, it is allowed to configure multiple backhaul links for a tunnel, that is, one tunnel may be served by multiple backhaul links. In order to distinguish from the existing technology, in the actual configuration process, a new IE (such as Additional BH information) may be added on the basis of TS38.473 BH Information IE. The function of this IE is to include configuration of one or more additional backhaul links.
Information related to tunnel. For a tunnel, the information comprises at least one of the following information:
The above-mentioned information related to the tunnel may be related to the uplink tunnel, or may be related to the downlink tunnel. For an uplink tunnel, the above-mentioned “node where one end of the tunnel is located” may be a base station, a central unit of a base station, a user plane part of a central unit of a base station, an anchor node, a central unit of an anchor node, and a user plane part of a central unit of an anchor node. For a downlink tunnel, the above-mentioned “node where one end of the tunnel is located” may be a distributed unit of a base station, a distributed unit of an anchor node, a relay node, or a distributed unit function of a relay node.
This process involves two nodes, namely a first node and a second node, and the type of the two nodes may be any of the above-mentioned node types. Hereinafter, description is made by way of an example of the first node being the central unit of the anchor node, and the second node being the distributed unit of the anchor node, or the relay node, or the distributed unit function of the relay node.
As shown in
Step 701: the first node transmits a first resource configuration request message to the second node, the message is used for the second node to perform resource configuration, and the message comprises at least one of the following information:
The function of one or more of the above information is to help the second node generate configuration information related to the radio bearer on the access link side (such as generate the configuration of the RLC entities, generate the configuration of the logical channels, where the number of RLC entities and/or the number of logical channels is the same as the number of the duplicated data packets indicated in the above information). This configuration information is used to transmit the data packets of radio bearer of the user equipment on the access link of the second node. Another function is to help the second node duplicate the data packets of the radio bearer. For example, when the second node receives a data packet, it may determine the number of copies duplicated from the received data packet according to one or more of the above information (If the above information of number indicates 4, then the received data packet is duplicated into four copies), and transmit these duplicated data packets on the access link of the second node. In one implementation, the second node receives a downlink data packet from other nodes, and duplicates the data packet into a corresponding number according to the above information, and then transmit them to the user equipment.
Another implicit indication method is that when configuration information of multiple backhaul links in contained in the tunnel configuration information corresponding to the access link channel, backhaul links corresponding to the access link channel are the multiple backhaul links.
The above-mentioned mapping relationship information may implement the following two possible mapping modes:
Mapping mode 1: Multiple backhaul links are mapped to one access link channel. That is, a data packet on one access link channel is transmitted by multiple backhaul links (for example, an uplink data packet on one access link channel is transmitted by multiple backhaul links, or downlink data packets on multiple backhaul links are transmitted by the same access link channel). In one embodiment, the data packet is duplicated and then transmitted by multiple backhaul links.
Mapping mode 2: One backhaul link is mapped to multiple access link channels. That is, a data packet on a backhaul link is transmitted by multiple access link channels (for example, a downlink data packet on a backhaul link is transmitted by multiple access link channels, or data packets on multiple access link channels are transmitted by a backhaul link). In one embodiment, a data packet is duplicated and then transmitted by multiple access link channels.
- First configuration information related to backhaul link channel, which is one or more backhaul link channels served by the second node, and a channel(s) used in serving other nodes (such as other relay nodes) accessing the second node. In one implementation, when the second node is a relay node, the backhaul link channel is a channel served by the distributed unit function of the relay node. One of the functions of the first configuration information is that when the second node receives this information, it generates configuration information related to the backhaul link channel. In one implementation, the second node configures different serving cells for different backhaul link channels, wherein the different backhaul link channels may be backhaul link channels associated with each other. The configuration information comprises at least one of the following information:
> Information of backhaul link channel group. This information is used to indicate backhaul link channels that are associated with each other. In one embodiment, the backhaul link channels that are associated with each other jointly serve the same user equipment. In another implementation, the backhaul link channels that are associated with each other are of one type of data (such as a radio bearer, a data radio bearer DRB, or a signaling radio bearer SRB) that jointly serves a user equipment. In another implementation, when a radio bearer of a user equipment is configured as a bearer that supports duplication function, the backhaul link channels that are associated with each other jointly serve the radio bearer. In another implementation, when a radio bearer of a user equipment is configured as a bearer that supports duplication function, the backhaul link channels that are associated with each other jointly serve the radio bearer, and a backhaul link channel is used to serve a copy of the radio bearer (for example, serve data on a tunnel of the radio bearer). This information may comprise information of one or more backhaul link channels that are associated with each other. For a backhaul link channel, this information comprises at least one of the following information:
Step 702 (optional): The second node transmits a first resource configuration response message to the first node, wherein the message contains resource configuration information generated by the second node. The message comprises at least one of the following information:
The main function of the above two steps is to help the second node to configure transmission of user data. Furthermore, when the user data needs to be duplicated, the above process helps the second node to configure duplication of the user data. According to the above configuration, in one implementation, the second node only generates the related configuration, but does not duplicate the user data. Whether to perform the duplication or not needs to be based on other configuration information, such as configuration information given in third and fourth aspects of the present disclosure. In another implementation in which the second node performs transmission and duplication of the user data, following steps may also be comprised:
Step 703 (optional)(not depicted in
In order to implement configuration of the number of copies on the access link channel and the backhaul link of the radio bearer, possible implementations are described in combination with specific embodiments. However, it should be noted that the following implementations are only examples and other possible implementations are not excluded.
Embodiment 1: The number of copies of the backhaul link is equal to the number of copies of the access link.
Possible implementations of the above step 701 are as follows:
This embodiment is the same as the prior art. That is, the second node determines the number of access link channels according to the number of tunnels included in the first resource configuration request message, and the second node does not need to duplicate a data packet; and the second node transmits a data packet received from a tunnel (backhaul link) to corresponding access link channel, or transmits a data packet received from the access link channel through the corresponding tunnel (backhaul link).
In this mode, for a tunnel, one or more backhaul links are configured in the message of step 701. In order to indicate to the second node the number of access link channels that need to be established, “Indication information of duplication of data packet” may be included in this information. After the second node receives the information, in one embodiment, the number of access link channels may be determined according to the number of backhaul links configured in this information; and in another embodiment, the number of access link channels corresponding to a tunnel may be determined according to the number of backhaul links configured for the tunnel.
In another implementation of this mode, for a tunnel, the information contains one or more routing identification information, and the number of access channels is determined according to the number of routing identifications contained in this information. In another embodiment, the number of access link channels corresponding to a tunnel may be determined according to the number of routing identifications configured for the tunnel.
Embodiment 2: The number of copies of the backhaul link is greater than the number of copies of the access link.
Possible implementations are as follows:
Mode 1: The number of copies on the backhaul link is determined according to the number of configured tunnels, and the number of the access link channel is determined according to the number of available tunnels configured.
In this mode, the “first information related to tunnel of radio bearer” may be included in the above step 701. The number of available tunnels configured in this information is equal to the number of access link channels, but the number of tunnels included in this information is the number of copies on the backhaul link.
Mode 2: The number of access link channels is determined according to the number of configured tunnels, and the number of copies of the backhaul link is determined according to the number of configured backhaul links.
In this mode, the number of access link channels may be determined according to the number of tunnels configured in the “first information related to tunnel of radio bearer” included in the above step 701. For a tunnel, this information may configure multiple backhaul links, wherein the number of configured backhaul links determines the number of copies of the backhaul link. In another implementation, the number of copies of backhaul link is determined from “Information related to backhaul link that serves the radio bearer” included in step 701.
Embodiment 3: The number of copies of the backhaul link is less than the number of copies of the access link.
The possible implementations are as follows:
In this mode, “first information related to tunnel of radio bearer” may be included in the above step 701, wherein the number of tunnels configured in this information is equal to the number of access link channels, but unavailable tunnels (that is, tunnels that do not need to be used on the backhaul link) are determined by including “Indication information of using tunnel” in this information.
In this mode, “first information related to tunnel of radio bearer” may be included in the above step 701. For a tunnel, the number of copies that a data packet on the tunnel is to be duplicated into is determined by including “Indication information of duplication of data packet” in this information. In another implementation, the number of the access link channels is determined by including “Information related to access link serving the radio bearer” in step 701.
In the above process, the first resource configuration request message and the first resource configuration response message may be UE Context Setup/Modification Request message and UE Context Setup/Modification Response message of the existing F1 interface, respectively. Alternatively, it may also be a RRC message or other messages.
The beneficial effects of the above steps are:
This process involves two nodes, the first node and a third node, and the type of the two nodes may be any of the above-mentioned node types. In an implementation, the first node is the control plane part of the central unit of the anchor node, and the third node is the user plane part of the central unit of the anchor node. This interaction process is used to help the third node determine the number of copies to be duplicated into when transmitting downlink data. As shown in
Step 801: The first node transmits a second resource configuration request message to the third node, wherein the message is used to notify the third node of configuration information about downlink data transmission, and the message comprises at least one of the following information:
In the prior art, for one tunnel, there is only one set of QoS mapping information. However, in the present disclosure, it is allowed to realize configuration of multiple QoS mapping information for one tunnel. In the actual system, in order to configure multiple QoS mapping information, one possible approach is to introduce a new IE based on the existing QoS Mapping Information IE defined in TS38.463, such as the additional QoS Mapping Information IE, wherein this IE comprises one or more additional QoS mapping information.
Step 802(optional): The third node transmits a second resource configuration response message to the first node. The message is used to confirm the configuration requested in step 701 and provide configuration information generated at the third node, such as information related to tunnel at the third node.
The main function of the above two steps is to help the third node configure transmission of user data. Furthermore, when the user data needs to be duplicated, the above process helps the third node configure duplication of the user data. According to the above configuration, in one implementation, the third node only generates the relevant configuration, but does not duplicate the user data. Whether to perform the duplication is based on other configuration information, such as configuration information given in third and fourth aspects of the present disclosure. In another implementation, the third node performs transmission and duplication of the user data, in which case the following steps may be further included:
Step 803(not depicted in
The above modes are only examples, and other possible modes are not excluded.
In the above process, the second resource configuration request message and the second resource configuration response message may be Bearer Context Setup/Modification Request message and Bearer Context Setup/Modification Response message of the existing E1 interface, respectively, or may be other messages.
The beneficial effects of the above steps are:
In the prior art, if transmission of user data is configured with a duplication feature, when transmitting downlink data, the central unit of the base station or the user plane part of the central unit of the base station decides, of its own accord, whether to duplicate the user data. In the present disclosure, considering that the transmission of user data may pass through multiple nodes (such as transmission in a relay network), the duplications of downlink data performed on the backhaul link (the link between the central unit of the anchor node or the distributed unit of the anchor and an access node of the user equipment or distributed unit part of the access node) and the access link may differ from each other. In order to support such features, the present disclosure proposes a variety of new methods for activating or deactivating downlink data duplication.
The nodes involved in this aspect include a first node, a second node and a third node, and the types of the three nodes may be any of the above-mentioned node types. In an implementation, the first node is the central unit of the anchor node or the control plane part of the central unit of the anchor node, the second node is the relay node or the distributed unit function of the relay node or the distributed unit of the anchor node, and the third node is the user plane part of the central unit of the anchor node.
As shown in
Step 901: The first node or the third node transmits a first configuration message to the second node, wherein the message is used to help the second node determine a transmission method of user data on the access link, and the message comprises at least one of the following information:
After receiving the above-mentioned first configuration message, the second node performs duplication and transmission of the user data according to the configuration information in the messages. The above-mentioned first configuration message may be a control plane message or a user plane message. If it is a user plane message, it may be transmitted using the existing TRANSFER USER DATA message in TS38.425, or it may be transmitted with other messages.
In this method, the third node, of its own accord, duplicates the data packets, which are then transmitted by the corresponding downlink tunnels or by different routes serving the downlink tunnels. The third node may perform duplication of user data according to the configuration performed in the second aspect of the present disclosure. In one embodiment, if a radio bearer of the user equipment is configured with multiple downlink tunnels, the third node determines to duplicate a data packet of the radio bearer of the user equipment into multiple copies, and then hands them over to different downlink tunnels for transmission, wherein the number of copies to be duplicated into is the number of downlink tunnels configured for the radio bearer. In another embodiment, if a downlink tunnel of a radio bearer of the user equipment is configured with multiple QoS mapping information (see the second aspect of the present disclosure for details), the third node duplicates a data packet of the radio bearer of the user equipment into multiple copies, each setting the relevant field of the data packet according to one of the QoS mapping information, and then transmit them. The number of copies that the data packet is to be duplicated into is the number of configured QoS mapping information.
Beneficial effect of the above steps is:
1) Duplicating and transmitting user data packet(s) by the nodes, wherein the transmitting may be performed on the access links.
According to the existing mechanisms, on an access link, activation and deactivation of uplink data packet duplication is controlled by the distributed unit serving the access link. In a multi-hop network, an uplink data packet transmitted by the access link may need to be transmitted by an uplink backhaul link, and thus is eventually transmitted to the anchor node. Therefore, different from the existing mechanisms, in a multi-hop network, it is also necessary to determine how to activate and deactivate duplication of an uplink data packet on the backhaul link. In order to support such features, the present disclosure proposes a variety of new methods for activating or deactivating duplication of uplink data.
The nodes involved in this aspect include a first node, a second node and a third node, and the types of the three nodes may be any of the above-mentioned node types. In an implementation, the first node is the central unit of the anchor node or the control plane part of the central unit of the anchor node, the second node is the relay node or the distributed unit function of the relay node or the distributed unit of the anchor node, and the third node is the user plane part of the central unit of the anchor node.
Method 1: The first node or the third node transmits a second configuration message to the second node.
As shown in
Step 1001: The first node or the third node transmits a second configuration message to the second node, wherein the message is used to help the second node determine a transmission method of user data on the backhaul link, and the message comprises at least one of the following information:
After receiving the above-mentioned second configuration message, the second node performs duplication and transmission of the user data according to the configuration information in the messages (for example, a data packet received from an access link channel is duplicated and transmitted on respective backhaul links). The above-mentioned second configuration message may be a control plane message or a user plane message. If it is a user plane message, it may be transmitted using the existing TRANSFER USER DATA message in TS38.425, or it may be transmitted with other messages.
In this method, the configuration information may refer to the configuration process of the first aspect of the present disclosure. If the configuration information configures the mapping relationships between the access link channels and the backhaul links, the data packets transmitted on the activated access link channels need to be transmitted on the corresponding backhaul links. If a data packet on an access link channel corresponds to multiple backhaul links, the second node needs to duplicate the data packet and then transmit them through the corresponding multiple backhaul links. If data packets on multiple access link channels correspond to the same backhaul link, in one embodiment, it is sufficient that the second node hands over a data packet received from one of the access link channels to the respective backhaul link for transmission. Furthermore, the other same data packets received from other access link channels may be discarded by the second node. In another embodiment, it is sufficient that the second node hands over all of the data packets received from multiple access link channels to corresponding backhaul link for transmission.
In this method, if the configuration information configures the number of copies that a data packet on the backhaul link is to be duplicated into, the second node duplicates the data packet received from the access link channel, wherein the number of copies to be duplicated into is the number configured, and then, the second node hands over the duplicated data packets for transmission over the backhaul link. In one embodiment, the second node decides the selected backhaul link. In another embodiment, if the configuration information also configures mapping relationships between the access link channels and the backhaul links, the second node transmits data packets according to the mapping relationships.
Beneficial effect of the above steps is:
1) Duplicating and transmitting user data packets by the nodes, wherein the transmitting may be performed on the backhaul link.
As shown in
The above configuration request message may be at least one of the above first resource configuration request message, the second resource configuration request message, the first configuration message, or the second configuration message.
In an embodiment, the transmitting node may be the first node described above, more specifically, the first node may be a central unit of an anchor node or control plane part of the central unit of the anchor node, and the receiving node may be the second node described above. More specifically, the second node may be a relay node, a distributed unit function of the relay node, or a distributed unit of an anchor node. At this point, the configuration request message may be at least one of the foregoing first resource configuration request message, first configuration message, or second configuration message. In another embodiment, the transmitting node may be the first node described above, more specifically, the first node may be control plane part of a central unit of an anchor node, and the receiving node may be the third node described above. More specifically, the third node may be user plane part of a central unit of an anchor node. At this point, the configuration request message may be the foregoing second resource configuration request message.
In yet another embodiment, the transmitting node may be the third node described above. More specifically, the third node may be user plane part of a central unit of an anchor node, and the receiving node may be the second node described above. More specifically, the second node may be a relay node, a distributed unit function of the relay node, or a distributed unit of an anchor node. At this point, the configuration request message may be at least one of the foregoing first resource configuration request message, first configuration message, or second configuration message.
Based on the five aspects of the present disclosure, beneficial effects achieved by the present disclosure include:
According to an aspect of the present disclosure, a data transmission method is provided, wherein the method may comprise: receiving by a receiving node a configuration request message from a transmitting node; and performing by the receiving node a data duplication configuration on a radio bearer based on the received configuration request message.
In an embodiment, the configuration request message may be a first resource configuration request message, where the first resource configuration request message may comprise at least one of the following: first configuration information related to the radio bearer; and first configuration information related to a backhaul link channel, for the receiving node to generate configuration information related to the backhaul link channel.
In an embodiment, the first configuration information related to the radio bearer may comprise first information related to a tunnel of the radio bearer, and the first information related to the tunnel of the radio bearer may comprise identification indication information for indicating an access link channel corresponding to the tunnel.
In one embodiment, the method may further comprise: transmitting by the receiving node a first resource configuration response message to the transmitting node, the message comprising resource configuration information generated by the receiving node; and
In an embodiment, the method may further comprise: performing by the receiving node transmission of user data on the radio bearer according to a configuration in at least one of the first resource configuration request message and the resource configuration information generated by the receiving node.
In an embodiment, the first configuration information related to the radio bearer may comprise at least one of the following: identification information of the radio bearer, first information related to the tunnel of the radio bearer, information related to the access link, information related to the backhaul link and mapping relationship information indicating a mapping relationship between the backhaul link and the access link channel.
Furthermore, the above-mentioned information related to the access link may comprise first indication information of data packet duplication. Still furthermore, the first indication information of data packet duplication may comprise at least one of the following: first indication information for configuring a duplication function; first information related to a number of copies to be duplicated into, the first information indicating a number of copies that a data packet of the radio bearer is to be duplicated into on an access link side; information of a number of RLC entities; information of a number of logical channels; information of a number of paths (Paths/Legs); and information of a number of access link channels.
Furthermore, the above-mentioned information related to the backhaul link may comprise second indication information of data packet duplication. Still furthermore, the second indication information of data packet duplication may comprise at least one of the following: second indication information for configuring a duplication function; and second information related to number of copies to be duplicated into, the second information indicating a number of copies that a data packet of the radio bearer is to be duplicated into on a backhaul link side.
The foregoing first configuration information related to the backhaul link channel may comprise at least one of the following: information of a group of backhaul link channels and configuration information of the backhaul link channels.
In an embodiment, the number of backhaul links configured in the first information related to the tunnel of the radio bearer may be used to determine second information related to number of copies to be duplicated into, the second information indicating a number of copies that a data packet of the radio bearer is to be duplicated into on a backhaul link side.
In an embodiment, the transmitting node may be a central unit of an anchor node, and the receiving node may be a distributed unit of the anchor node, or a relay node, or a distributed unit function of the relay node.
In an embodiment, the first resource configuration request message and the first resource configuration response message may be a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message of the existing F1 interface, respectively, or may be RRC messages.
In an embodiment, the configuration request message is a second resource configuration request message, which is used to notify the receiving node of configuration information about downlink data transmission, wherein the second resource configuration request message comprises at least one of the following: the identification information of the radio bearer and the information related to the tunnel of the radio bearer.
In an embodiment, the information related to the tunnel of the radio bearer may comprise at least one of the following: Internet Protocol (IP) address, tunnel endpoint identifier of data, indication information of use of a tunnel, one or more QoS mapping information and information related to duplication of data.
In an embodiment, the method may further comprise: transmitting by the receiving node a second resource configuration response message to the transmitting node, wherein the second resource configuration response message is used to confirm a configuration requested by the transmitting node and comprises configuration information generated at the receiving node.
In an embodiment, the method may further comprise: transmitting by the receiving node user data according to a configuration in at least one of the second resource configuration request message and the second resource configuration response message.
In an embodiment, the method may further comprise: if a radio bearer is configured with multiple available tunnels according to the information related to the tunnel of the radio bearer, the receiving node determines the number of copies to be duplicated into according to a number of available tunnels, with each copy being transmitted by a tunnel.
In an embodiment, the method may further comprise: if a tunnel of a radio bearer is configured with multiple quality of service (QoS) mapping information according to the information related to the tunnel of the radio bearer, the receiving node may determine the number of copies to be duplicated into according to the number of the QoS mapping information, with each copy setting a field in an IP packet according to a piece of QoS mapping information.
In one embodiment, the transmitting node may be control plane part of a central unit of an anchor node, and the receiving node may be user plane part of the central unit of the anchor node.
In an embodiment, the second resource configuration request message and the second resource configuration response message may be a Bearer Context Setup/Modification Request message and a Bearer Context Setup/Modification Response message of the existing E1 interface, respectively.
In an embodiment, the receiving node further receives a first configuration message from the transmitting node, the message being used to help the receiving node determine a transmission method of user data on the access link.
In an embodiment, the receiving node further receives a second configuration message from the transmitting node, the message helping the receiving node determine a transmission method of user data on the backhaul link.
In an embodiment, the configuration request message may be a first configuration message, and the message may be used to help the receiving node determine a transmission method of user data on the access link, wherein the first configuration message comprises at least one of the following: indication information of duplication of data; and indication information of the number of copies that data is to be duplicated into.
In an embodiment, the method further comprises: after receiving the above-mentioned first configuration message, the receiving node may perform duplication and transmission of user data according to configuration information therein.
In an embodiment, the first configuration message may be a TRANSFER USER DATA message.
In an embodiment, the transmitting node may be a central unit of an anchor node or control plane part of the central unit of the anchor node, and the receiving node may be a relay node, a distributed unit function of the relay node, or a distributed unit of the anchor node.
In another embodiment, the transmitting node may be user plane part of a central unit of an anchor node, and the receiving node may be a relay node or a distributed unit function of the relay node or a distributed unit of the anchor node.
In an embodiment, the configuration request message may be a second configuration message, and the message may be used to help the receiving node determine a transmission method of user data on the backhaul link, wherein the second configuration message comprises at least one the following: indication information of duplication of data; and indication information of the number of copies that data to be duplicated into.
In an embodiment, the method may further comprise: after receiving the above-mentioned second configuration message, the receiving node performs duplication and transmission of user data according to configuration information therein.
In an embodiment, the transmitting node may be a central unit of an anchor node or control plane part of the central unit of the anchor node, and the receiving node may be a relay node or a distributed unit function of the relay node or a distributed unit of the anchor node.
In another embodiment, the transmitting node may be user plane part of a central unit of an anchor node, and the receiving node may be a relay node or a distributed unit function of the relay node or a distributed unit of the anchor node.
In an embodiment, the data duplication of the radio bearer may comprise: duplication of a user data packet of Packet Data Convergence Protocol (PDCP) layer.
According to an aspect of the present disclosure, there is provided a receiving node, which may comprise: a transceiver; and a processor configured to control the transceiver to perform the methods as described above.
In an embodiment, the receiving node may be the second node or the third node described above. More specifically, the second node may be a relay node or a distributed unit function of the relay node or a distributed unit of an anchor node, and the third node may be user plane part of a central unit of the anchor node.
According to an aspect of the present disclosure, there is provided a transmitting node, which may comprise: a transceiver; and a processor configured to: control the transceiver to transmit a configuration request message to a receiving node, for the receiving node to perform configuration of duplication of data of a radio bearer.
In an embodiment, the transmitting node may be the first node or the third node described above. More specifically, the first node may be a central unit of an anchor node or control plane part of the central unit of the anchor node, and the third node may be user plane part of the central unit of the anchor node.
Although one or more embodiments have been described with reference to the accompanying drawings, those of ordinary skill in the art will understand that various changes in forms and details may be made without departing from the spirit and scope defined by the appended claims.
According to the existing mechanisms, when a control signaling message (such as a RRC message) is transmitted between a base station and a user equipment, if the control signaling message is large, it may be segmented and then transmitted. However, when the content of a control signaling message is generated by multiple nodes, because these nodes do not know sizes of the control signaling message allowed by each other, the information in the control signaling message generated by the nodes may cause the size of the control signaling message to exceed the limit. Therefore, a sixth aspect of the present disclosure provides a method for ensuring that a size of a control signaling message does not exceed a limit among multiple nodes. The nodes involved in this method comprise:
In one embodiment, for the Dual Connectivity scenario, the fourth node is a master node (or a central unit of the master node, or control plane part of the central unit of the master node), and the fourth node eventually generates a control signaling message and transmits it to a user; and the fifth node is a secondary node (or a central unit of the secondary node, or control plane part of the central unit of the secondary node), and the fifth node generates part of information in the control signaling message.
In another embodiment, for the handover scenario, the fourth node is a source node (or a central unit of the source node, or control plane part of the central unit of the source node), and transmits a control signaling message to a user; and the fifth node is a target node (or a central unit of the target node, or control plane part of the central unit of the target node), and is a node that generates a control signaling message.
In another embodiment, for a base station with a CU-DU split architecture, the fourth node is a central unit of the base station, and the fifth node is a distributed unit of the base station. In one embodiment, the base station may be a base station serving a user equipment in single connectivity. In this case, the fourth node is the node that generates a control signaling message (such as a RRC messages) and transmits the message to the user; and the fifth node is the node that generates part of information in the control signaling message. In another embodiment, the base station may be a secondary base station in dual connectivity. In this case, both the fourth node and the fifth node are nodes that generate part of information of the control signaling message; and the control signaling message may eventually be generated by other nodes (such as the master base station), and transmitted to the user equipment by other nodes (such as the master base station) (furthermore, in one embodiment, the central unit of the master base station and the central unit of the secondary base station are the same node, but the distributed units thereof are two different nodes). In another embodiment, the base station is the target base station in the handover process. In this case, the fourth node is the node that eventually generates the control signaling message, and the fifth node is the node that generates part of information in the control signaling message. The control signaling message is transmitted by other nodes (such as the source base station) to the user equipment (furthermore, in one embodiment, the central unit of the source base station and the central unit of the target base station are the same node, but the distributed units thereof are two different nodes).
This aspect relates to segmentation of a control signaling message, and each segment may be included in another control signaling message. Therefore, for the convenience of description, the present disclosure defines the following descriptions:
In addition, in one embodiment, the first or second control signaling messages are a RRC message.
The method of this aspect is not only applicable to single-hop networks, but also applicable to multi-hop networks (such as IAB network).
In order to support the segmentation of the control signaling message, the interaction process between the foregoing fourth node and fifth node comprises following steps:
Step 1201 in
In order to distinguish from the prior art, the above-mentioned “first signaling information” may contain multiple containers, and each container may contain a second control signaling message that carries a segment of the first control signaling message (such as, a DLDedicatedMessageSegment message containing a segment of RRCReconfiguration/RRCResume message). In the prior art, the fourth node can only transmit a container containing the RRC message to the fifth node. For example, there is only one RRC-Container IE in the F1AP message, which contains only one RRC message. However, in the present disclosure, the above-mentioned “first signaling information” contains multiple containers, and each container contains a RRC message. In one embodiment, in order to continue using the existing signaling design, the fourth node may comprise in the existing RRC-Container IE a RRC message (such as a DLDedicatedMessageSegment message). Furthermore, the RRC message contains a segment of the first control signaling message, and then the above-mentioned “first signaling information” is a newly added IE (such as named as Additional RRC-Container, or Additional RRC-Container List). This IE carries one or more additional RRC-Containers, and this new IE and the segments of the RRC message carried in the existing IE may form a complete first control signaling message.
In an embodiment, the aforementioned “second capability information” may also be included in the control signaling message contained in the aforementioned “second control information container”.
Step 1202 in
After receiving this information, the fourth node may learn that the cause for the failure is not that the resources of the fifth node are insufficient, so the fourth node may continue requesting the fifth node to establish a SRB, or establish a DRB, or increase PDU session resources, or establish a cell, or modify the SRB, or modify the DRB, or modify the PDU session resources, etc.
When the above-mentioned “first configuration control information” comprises a plurality of “first control information”, the “first configuration control information” is different from that in the prior art. Specifically, taking the F1 interface as an example, in the prior art, the message transmitted by the distributed unit to the central unit may contain a DU to CU RRC Information IE. In contrast, in the present disclosure, it is allowed to contain multiple DU to CU RRC Information IEs, which contain all the control information required to configure a user equipment. Accordingly, in addition to the existing DU to CU RRC Information IE, a new IE may also be defined to carry control information that is not contained in the existing “DU to CU RRC Information IE” in the above-mentioned “first control information”. In an embodiment, the new IE may be “Additional DU to CU RRC Information” or “Additional DU to CU RRC Information List” etc. Taking the signaling interactions related to the dual connectivity on the Xn/X2 interface as an example, in the prior art, the message transmitted by a secondary node to a master node may contain a Secondary Node to Master Node container IE (the IE containing CG-Config). In contrast, in the present disclosure, it is allowed to include multiple Secondary Node to Master Node container IEs. These IEs contain all the control information required to configure the user equipment. Accordingly, in addition to the existing Secondary Node to Master Node container IE, a new IE may also be defined to carry control information that is not contained in the existing “Secondary Node to Master node container IE” in the above-mentioned “first control information”. In an embodiment, the new IE may be “Additional Secondary Node to Master Node Container” or “Additional Secondary Node to Master Node Container List” etc.
For different types of the fourth node and the fifth node, there may be several embodiments of the above process as follows. In the following embodiments 12-a to 12-f, detailed descriptions for the information contained in each message may be found in the above steps 1201 and 1202 of
Embodiment 12-a (Single connectivity scenario, where CU and DU are split, the fourth node is a central unit (CU) of a base station, the fifth node is a distributed unit (DU) of the base station, and a size limit of the control information is set by the CU)
In this embodiment 12-a, the fourth node and the fifth node are the central unit of the base station (or control plane part of the central unit) and the distributed unit of the base station, respectively, and the size limit of the control information generated by the distributed unit is configured by the central unit. This embodiment 12-a may comprise the following processes:
Step 12-a-1201: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
Step 12-a-1202: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
In this embodiment 12-a, the distributed unit of the base station may determine the generated control information according to the information transmitted by the central unit of the base station (such as the size information of the control information), so as to help the central unit of the base station generate a control signaling message of an appropriate size (such as RRCReconfiguration, RRCResume, CG-Config, HandoverCommand, etc.).
Embodiment 12-b (Single connectivity scenario, where CU and DU are split, the fourth node is the central unit of the base station, the fifth node is the distributed unit of the base station, and the size limit of the control information is set by OAM)
In this embodiment 12-b, the information of the size allowed when the distributed unit of the base station generates the control information is configured by the OAM. Therefore, the distributed unit may generate the control information based on this information. This embodiment 12-b may comprise the following processes:
Step 12-b-1201: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
Step 12-b-1202: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
In this embodiment 12-b, the distributed unit of the base station may determine the generated control information according to the size information of the control information configured by the OAM, so as to help the central unit of the base station generate a control signaling message of an appropriate size.
In an optional embodiment, the above steps 12-a-1202 and 12-b-1202 may be optional steps.
In the processes of the above embodiments 12-a and 12-b, the first data configuration request message and the first data configuration response message may be non-user equipment-associated F1 messages, such as a GNB-CU Configuration Update and a GNB-CU Configuration Update Acknowledge message, respectively, or may be user equipment-associated F1 messages, such as a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message, respectively, or may be newly defined messages.
Embodiment 12-c (dual connectivity scenario, where the fourth node is the master node or the central unit of the master node, or the control plane part of the central unit of the master node, and the fifth node is the secondary node, or the central unit of the secondary node, or the control plane part of the central unit of the secondary node, and the size limit of the control information is set by the master node or the central unit of the master node, or the control plane part of the central unit of the master node)
In this embodiment 12-c, the master node may inform the secondary node of information of the size allowed when generating the control information, such that the secondary node generates the control information based on this information. This embodiment 12-c may comprises the following processes:
In this embodiment 12-c, the secondary node may determine the generated control information according to the information transmitted by the master node (such as size information of the control information), thereby helping the master node generate a control signaling message of an appropriate size.
Embodiment 12-d (dual connectivity scenario, where the fourth node is the master node or the central unit of the master node, or the control plane part of the central unit of the master node, and the fifth node is the secondary node, or the central unit of the secondary node, or the control plane part of the central unit of the secondary node, and the size limit of the control information is set by OAM)
In this embodiment 12-d, the OAM configures information of the size allowed when generating the control information by the secondary node, such that the secondary node generates control information based on this information. This embodiment 12-d may comprise the following processes:
In this embodiment 12-d, the secondary node may determine the size of the generated control information according to the configuration by the OAM, so as to help the master node generate a control signaling message of an appropriate size.
In an optional embodiment, the above steps 12-c-1202 and 12-d-1202 may be optional steps.
In the processes of the above embodiments 12-c and 12-d, the first data configuration request message and the first data configuration response message may be non-user equipment-associated messages, such as a Xn/X2 Setup Request and a Xn/X2 Setup Response message respectively, a NG-RAN Node/eNB Configuration Update and a NG-RAN Node/eNB Configuration Update Acknowledge message respectively; or may also be user equipment-associated messages, such as a S-Node (SgNB) Addition/Modification Request and a S-Node (SgNB) Addition/Modification Response message, or may be newly defined messages.
Embodiment 12-e (Handover scenario, where the fourth node is the source node or the central unit of the source node, or the control plane part of the central unit of the source node, and the fifth node is the target node, or the central unit of the target node, or the control plane part of the central unit of the target node; and the size limit of the control information is set by the source node or the central unit of the source node, or the control plane part of the central unit of the source node)
In this embodiment 12-e, the source node may inform the target node of information of the size allowed when generating control information, such that the target node generates the control information or control signaling messages according to this information. This embodiment 12-e may comprise the following processes:
In this embodiment 12-e, the target node may determine the generated control information according to the information transmitted by the source node (such as size information of the control information), thereby helping the source node generate a control signaling message of an appropriate size.
Embodiment 12-f (Handover scenario, where the fourth node is the source node or the central unit of the source node, or the control plane part of the central unit of the source node, and the fifth node is the target node, or the central unit of the target node, or the control plane part of the central unit of the target node; and the size limit of the control information is set by OAM)
In this embodiment 12-f, the OAM configures information of the size allowed when the target node generating the control information, such that the target node generates the control information according to this information. This embodiment comprises the following processes:
In this embodiment 12-f, the target node may determine the size of the generated control information according to the configuration by the OAM, thereby helping the source node generate a control signaling message of an appropriate size.
In an optional embodiment, the above steps 12-e-1202 and 12-f-1202 may be optional steps.
In the processes of the above embodiments 12-e and 12-f, the first data configuration request message and the first data configuration response message may be non-user equipment-associated messages, such as Xn/X2 Setup Request and Xn/X2 Setup Response messages, NG-RAN Node/eNB Configuration Update and NG-RAN Node/eNB Configuration Update Acknowledge messages, or may be user equipment-associated messages, such as Handover Request and Handover Request Acknowledge messages, or may be newly defined messages.
In embodiments 13-g, 13-h, 13-i and 13-j, example flowcharts for dual connectivity scenarios and handover scenarios are respectively given, wherein in the same scenarios, the size limit of the control information may be set by different entities.
Description is made below with respect to different scenarios and different size restriction setting subjects.
Embodiment 13-g (dual connectivity scenario, where the fourth node is the central unit of the secondary node or the control plane part of the central unit, the fifth node is the distributed unit of the secondary node, and the size restriction of the control information is set by the master node, the central unit of the master node, or the control plane part of the central unit of the master node)
This embodiment 13-g also involves a sixth node, which may be the master node or the central unit of the master node, or the control plane part of the central unit of the master node. This embodiment 13-g comprises the following processes:
Step 13-g-1301: The sixth node transmits a second data configuration request message to the fourth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-g-1302: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-g-1303: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
Step 13-g-1304: The fourth node transmits a second data configuration response message to the sixth node, wherein the message comprises at least one of the following information:
In this embodiment 13-g, the central unit of the secondary node and the distributed unit of the secondary node may generate control information according to the configuration information of the master node, and then forward it to the master node to generate a control signaling message of an appropriate size.
Embodiment 13-h (dual connectivity scenario, where the fourth node is the central unit of the secondary node or the control plane part of the central unit of the secondary node, the fifth node is the distributed unit of the secondary node, and the size restriction of the control information is set by OAM)
This embodiment further involves a sixth node, which may be the master node or the central unit of the master node, or the control plane part of the central unit of the master node. This embodiment 13-h may comprise the following processes:
Step 13-h-1301: The sixth node transmits a second data configuration request message to the fourth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-h-1302: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-h-1303: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
Step 13-h-1304: The fourth node transmits a second data configuration response message to the sixth node, wherein the message comprises at least one of the following information:
In this embodiment 13-h, the central unit of the secondary node and the distributed unit of the secondary node may generate control information according to the configuration by the OAM, and then forward it to the master node to generate a control signaling message of an appropriate size.
In the processes of the above embodiments 13-g and 13-h, the first data configuration request message and the first data configuration response message may be non-user equipment-associated F1 messages, such as a GNB-CU Configuration Update and a GNB-CU Configuration Update Acknowledge message respectively, or may be user equipment-associated F1 messages, such as a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message respectively, or may be newly defined messages. In an optional embodiment, the above steps 13-g-1303 and 13-h-1303 may be optional steps.
In the processes of the above embodiments 13-g and 13-h, the second data configuration request message and the second data configuration response message may be non-user equipment-associated messages, such as a Xn/X2 Setup Request and a Xn/X2 Setup Response message respectively, a NG -RAN Node/eNB Configuration Update and a NG-RAN Node/eNB Configuration Update Acknowledge message respectively, or may be user equipment-associated messages, such as a S-Node Addition/Modification Request and a S-Node Addition/Modification Response, or may be newly defined messages.
Embodiment 13-i (Handover scenario, where the fourth node is the central unit of the target node or the control plane part of the central unit, the fifth node is the distributed unit of the target node, and the size restriction of the control information is set by the source node or the central unit of the source node or the control plane part of the central unit of the source node)
This embodiment 13-i further involves a sixth node, which may be the source node or the central unit of the source node, or the control plane part of the central unit of the source node. This embodiment 13-i comprises the following processes:
Step 13-i-1301: The sixth node transmits a second data configuration request message to the fourth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-i-1302: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-i-1303: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
Step 13-i-1304: The fourth node transmits a second data configuration response message to the sixth node, wherein the message comprises at least one of the following information:
In this embodiment 13-i, the central unit of the target node and the distributed unit of the target node may generate the control information according to the configuration information of the source node, and then forward it to the source node to generate a control signaling message of an appropriate size.
Embodiment 13-j (Handover scenario, where the fourth node is the central unit of the target node or the control plane part of the central unit, the fifth node is the distributed unit of the target node, and the size restriction of the control information is set by OAM)
This embodiment 13-j further involves a sixth node, which may be the source node or the central unit of the source node, or the control plane part of the central unit of the source node. This embodiment 13-j comprises the following processes:
Step 13-j-1301: The sixth node transmits a second data configuration request message to the fourth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-j-1302: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
For the content contained in the above information, please refer to the descriptions in the above step 1201 in
Step 13-j-1303: The fifth node transmits a first data configuration response message to the fourth node, wherein the message comprises at least one of the following information:
Step 13-j-1304: The fourth node transmits a second data configuration response message to the sixth node, wherein the message comprises at least one of the following information:
In this embodiment 13-j, the central unit of the target node and the distributed unit of the target node may generate the control information according to the configuration by the OAM, and then forward it to the source node to generate a control signaling message of an appropriate size.
In an optional embodiment, the above steps 13-i-1303 and 13-j-1303 may be optional steps.
In the processes of the above embodiments 13-i and 13-j, the first data configuration request message and the first data configuration response message may be non-user equipment-associated F1 messages, such as GNB-CU Configuration Update and GNB-CU Configuration Update Acknowledge messages, or may be user equipment-associated F1 messages, such as a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message respectively, or may be newly defined messages.
Embodiment 14-k (CU-DU, transmitting a message containing multiple segments)
This embodiment 14-k occurs between the central unit and the distributed unit of the base station. When a RRC message is segmented, the central unit of the base station may transmit all the segments of the message to the distributed unit through a F1AP message, and then the distributed unit may transmit the segments to a user equipment one by one. The advantage of this is to speed up the transmission of the control signaling messages.
Step 1401: The fourth node transmits a first data configuration request message to the fifth node, wherein the message comprises at least one of the following information:
Step 1402: The fifth node transmits the received control signaling messages to the user equipment one by one.
In the above process, the first data configuration request message may be a DL RRC Message Transfer message of the F1 interface, or may be other information.
Beneficial effects of the sixth aspect of the present disclosure comprise:
Embodiment 15-1, for the handover scenario, when there is no Xn/X2 interface between the source node and the target node, in order to transmit the configuration information required to generate the control information, a seventh node is further involved, which is a node of the core network, such as AMF and MME, and which may forward the configuration information required to generate the control information from the source node to the target node.
1) Interaction process between fourth node (such as source node) and seventh node:
Step 1501 of
Step 1502 of
2) Interaction process between seventh node and fifth node (such as target node):
Step 1601 of
Step 1602 of
The beneficial effect of the above two processes is that during the handover process, if the handover on the X2/Xn interface cannot be performed, the above two processes may transfer the configuration information that generates the control signaling message, thereby avoiding the size of the control signaling message from exceeding the limit, since exceeding the limit may in turn make it impossible to configure the user equipment.
Each node according to embodiments of the present disclosure may operate as a transmitting node or a receiving node, and the transmitting node or the receiving node may be implemented by including a transceiver and a processor configured to control an operation according to one or more embodiments in the above
According to another aspect of the present disclosure, one of the advantages of the present disclosure is to ensure that the size of the control signaling message does not exceed the limit among multiple nodes.
A data transmission method among multiple nodes that ensures a size of a control signaling message does not exceed a limit is provided, the method comprising: receiving by a fifth node a configuration request message from a fourth node; and transmitting by the fifth node a configuration response message to the fourth node.
The configuration request message may be a first data configuration request message. The first data configuration request message is used to notify the fifth node of configuration information required in generating information in the control signaling message.
wherein the first data configuration request message comprises at least one of the following information: first capability information, which is used to indicate whether a node that generates the control signaling message has an ability to perform segmentation; first information indicating a size, which is used to indicate an allowed size of the control information when the fifth node generates the control information; second information indicating a size, which is used to indicate a size of the control information generated by the fourth node; first signaling information, which contains a first control signaling message and/or a second control signaling message generated by the fourth node; and second signaling information, which contains control signaling messages generated by other nodes.
In a further embodiment, the first signaling information may comprise multiple containers, each of which may comprise a second control signaling message that carries a segment of the first control signaling message;
Wherein the configuration response message may be a first data configuration response message, which is used to notify the fourth node of information in the control signaling message generated, and the message comprises at least one of the following information: cause information, a function of which is to indicate cause information of the information contained in the first data configuration response message; and first configuration control information, which is configuration information generated by the fifth node, and information contained in this configuration information may be included in the first control signaling message or the second control signaling message and then transmitted to a user equipment.
In a further embodiment, in the case of the F1 interface, the first configuration control information may comprise multiple DU to CU RRC Information IEs, and these IEs include all the control information required to configure the user; while in the case of the Xn/X2 interface, the first configuration control information may include multiple Secondary Node to Master Node container IEs, and these IEs contain all the control information required to configure the user equipment.
In an embodiment, the fourth node and the fifth node may be a central unit (or control plane part of the central unit) of the base station and a distributed unit of the base station, respectively, and a size limit of the control information generated by the distributed unit is configured by the central unit.
In another embodiment, the information of a size allowed when the distributed unit of the base station generates the control information is configured by OAM, and therefore, the distributed unit may generate control information based on this information.
In another embodiment, the fourth node and the fifth node may be a master node and a secondary node, respectively, or a source node and a target node, respectively.
In another embodiment, the fourth node and the fifth node may be a master node and a secondary node, respectively, or a source node and a target node, respectively, wherein OAM configures the information of the size allowed when the secondary node (or target node) generate the control information.
In another embodiment, the fourth node and the fifth node may be central units (or control plane part of the central units) of a master node (or a source node) and a secondary node (or a target node), respectively; or may be a central unit (or control plane part of the central unit) of a secondary node (or a target node) and a distributed unit of the secondary node (or a target node), respectively.
In another embodiment, the fourth node and the fifth node may be central units (or control plane part of the central units) of a master node (or source node) and a secondary node (or target node), respectively; or may be a central unit (or control plane part of the central unit) of a secondary node (or a target node) and a distributed unit of the secondary node (or the target node), respectively, wherein, a size limit of the control information is set by OAM.
In an embodiment, a method comprises: transmitting by a fourth node a first data configuration request message to a fifth node; and transmitting by the fifth node the received control signaling messages to a user equipment one by one;
Wherein the fourth node and the fifth node may be a central unit and a distributed unit of a base station, respectively.
In a further embodiment, the first data configuration request message comprises first information containing a plurality of segments of the first control signaling message.
In an embodiment, the first data configuration request message may be a DL RRC Message Transfer message of the F1 interface.
In one embodiment, for a dual connectivity scenario, the fourth node may be a master node (or a central unit of the master node, or control plane part of the central unit of the master node), and the fifth node may be a secondary node (or a central unit of the secondary node, or control plane part of the central unit of the secondary node).
In another embodiment, for a handover scenario, the fourth node may be a source node (or a central unit of the source node, or control plane part of the central unit of the source node), and the fifth node may be a target node (or a central unit of the target node, or control plane part of the central unit of the target node).
In another embodiment, the first data configuration request message and the first data configuration response message may be non-user equipment-associated messages. Specifically, they may be: a Xn/X2 Setup Request and a Xn/ X2 Setup Response message, a NG-RAN Node/eNB Configuration Update and a NG-RAN Node/eNB Configuration Update Acknowledge message, respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be user equipment-associated messages. Specifically, they may be: a Handover Request and a Handover Request Acknowledge messages respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be newly defined messages.
In various embodiments, for a base station with a CU-DU split architecture, the fourth node may be a central unit of the base station, and the fifth node may be a distributed unit of the base station.
According to another aspect of the present disclosure, a method is provided, the method comprising: transmitting by a sixth node a second data configuration request message to a fourth node, transmitting by the fourth node a first data configuration request message to a fifth node, transmitting by the fifth node a first data configuration response message to the fourth node, and transmitting by the fourth node a second data configuration response message to the sixth node.
In a further embodiment, the size limit of the control information used to generate a control signaling message of an appropriate size is set by the master node and/or the central unit of the master node or the control plane part of the central unit of the master node and/or OAM.
In a further embodiment, the sixth node may be a source node or the central unit of the source node, or the control plane part of the central unit of the source node, the fourth node may be the central unit of the target node or the control plane part of the central unit, and the fifth node may be the distributed unit of a target node.
In a further embodiment, the size limit of the control information used to generate a control signaling message of an appropriate size is set by the source node and/or the central unit of the source node and/or the control plane part of the central unit of the source node and/or the OAM.
In a further embodiment, the sixth node may be the master node or the central unit of the master node, or the control plane part of the central unit of the master node, the fourth node may be the central unit of the secondary node or the control plane part of the central unit, and the fifth node may be the distributed unit of the secondary node.
In a further embodiment, the first data configuration request message and the first data configuration response message may be non-user equipment-associated F1 messages. Specifically, they may be: a GNB-CU Configuration Update and a GNB-CU Configuration Update Acknowledge message respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be user equipment-associated F1 messages. Specifically, they may be: a UE Context Setup/Modification Request message and a UE Context Setup/Modification Response message, respectively. In an alternative embodiment, the first data configuration request message and the first data configuration response message may be newly defined messages.
In a further embodiment, the second data configuration request message and the second data configuration response message may be non-user equipment-associated messages. Specifically, they may be: a Xn/X2 Setup Request and a Xn/X2 Setup Response message, respectively; or they may be: NG-RAN Node/eNB Configuration Update and NG-RAN Node/eNB Configuration Update Acknowledge message, respectively. In an alternative embodiment, the second data configuration request message and the second data configuration response message may also be user equipment-associated messages. Specifically, they may be: a S-Node Addition/Modification Request and S-Node Addition/Modification Response message, respectively; or they may be: a Handover Request and a Handover Request Acknowledge message, respectively. In an alternative embodiment, the second data configuration request message and the second data configuration response message may also be newly defined messages. According to another aspect of the present disclosure, there is provided a method, the method comprising: transmitting by a fourth node a third data configuration request message to a seventh node, the message being used to transmit configuration information related to user equipment’s handover; and after receiving the above message, transmitting by the seventh node a first handover configuration information related to the handover to a target node.
In a further embodiment, the seventh node may be a node of the core network, which comprises at least one of the following: AMF and MME.
In a further embodiment, the third data configuration request message may be a Handover Required message in TS38.413 or TS36.423.
According to another aspect of the present disclosure, there is provided a method, the method comprising: transmitting a fourth data configuration request message by a seventh node to a fifth node, the message being used to transmit configuration information related to user equipment’s handover; and after receiving the above message, generating by the fifth node second handover configuration information related to the handover.
In a further embodiment, the seventh node is a node of the core network, and comprises at least one of the following: AMF and MME.
In a further embodiment, the fourth data configuration request message may be a Handover Request message in TS38.413 or TS36.423.
Number | Date | Country | Kind |
---|---|---|---|
202010694687.9 | Jul 2020 | CN | national |
202110026268.2 | Jan 2021 | CN | national |
This application is a U.S. National Stage application under 35 U.S.C. § 371 of an International application number PCT/KR2021/009203, filed on Jul. 16, 2021, which is based on and claims priority of a Chinese patent application number 202010694687.9, filed on Jul. 17, 2020, in the Chinese Intellectual Property Office, and of a Chinese patent application number 202110026268.2, filed on Jan. 8, 2021, in the Chinese Intellectual Property Office, the disclosure of each of which is incorporated by reference herein in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/KR2021/009203 | 7/16/2021 | WO |