Connection establishment method, first node, second node and third node

Abstract

The invention relates to a connection establishment method, a first node, a second node and a third node. The method comprises the steps that a third node sends third information to a first node, then the first node sends first information to a second node, and the second node receives the first information sent by the first node. Therefore, the problem of how to select a proper core network element for a user equipment (UE) for communication is solved to a certain extent.

Description

Connection establishment method, first node, second node and third node Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method for establishing a connection, a first node, a second node, and a third node. Background Art

[0002] Integrated access and backhaul (IAB) supports millimeter-wave network equipment for wireless access and backhaul, effectively reducing the need for new fiber deployment when deploying dense networks and enabling wireless relays in next-generation (NG) radio access networks (RAN). Mobile IABs, also known as vehicle-mounted relays (VMRs), allow user equipment (UE) to access the network through vehicle-mounted relay generation nodeBs (VMR-gNBs), thereby communicating with the core network and establishing a connection.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a method for establishing a connection, a first node, a second node, and a third node, which to a certain extent solve the problem of information interaction between a VMR node and a UE served by the VMR node and a core network.

[0005] The embodiments of the present disclosure provide a method for processing information.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for establishing a connection is proposed, including:

[0007] The first node sends first information to the second node, wherein the first information is used to assist the second node in information transmission with a third node.

[0008] According to a second aspect of an embodiment of the present disclosure, a method for establishing a connection is proposed, including:

[0009] The second node receives first information sent by the first node, wherein the first information is used to assist the second node in information transmission with a third node.

[0010] According to a third aspect of an embodiment of the present disclosure, a method for establishing a connection is proposed, including:

[0011] The third node sends third information to the first node, where the third information includes capability information of the third node.

[0012] According to a fourth aspect of an embodiment of the present disclosure, a first node is provided, including:

[0013] The transceiver module is used to send first information to the second node, wherein the first information is used to assist the second node in information transmission with the third node.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a second node is provided, including:

[0015] The transceiver module is configured to receive first information sent by the first node, wherein the first information is used to assist the second node and the third node in information transmission.

[0016] According to a sixth aspect of an embodiment of the present disclosure, a third node is provided, including:

[0017] The transceiver module is configured to send third information to the first node, wherein the third information includes capability information of the third node.

[0018] According to a seventh aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0019] one or more processors;

[0020] The processor is used to call instructions to enable the communication device to execute the processing method described in any one of the first aspect, the second aspect, and the third aspect.

[0021] According to an eighth aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first node, a second node, and a third node, wherein the first node is configured to implement the processing method described in the first aspect, the second node is configured to implement the processing method described in the second aspect, and the third node is configured to implement the processing method described in the third aspect.

[0022] According to the ninth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the processing method described in any one of the first aspect, the second aspect, and the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0024] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0025] FIG2 is an interactive schematic diagram of a method for establishing a connection according to an embodiment of the present disclosure;

[0026] 3A-3C are flowcharts of a method for establishing a connection according to an embodiment of the present disclosure;

[0027] 4A-4B are flowcharts of a method for establishing a connection according to an embodiment of the present disclosure;

[0028] 5A-5B are flowcharts of a method for establishing a connection according to an embodiment of the present disclosure;

[0029] Figure 6 is a schematic diagram of an NGAP message being forwarded to the AMF via the VMR-donor through the backhaul radio link control channel;

[0030] FIG7 is an interactive schematic diagram of a method for establishing a connection according to an embodiment of the present disclosure;

[0031] FIG8A is a schematic structural diagram of a first node proposed in an embodiment of the present disclosure;

[0032] FIG8B is a schematic structural diagram of a second node proposed in an embodiment of the present disclosure;

[0033] FIG8C is a schematic structural diagram of a third node proposed in an embodiment of the present disclosure;

[0034] FIG9A is a schematic structural diagram of a communication device 9100 proposed in an embodiment of the present disclosure;

[0035] FIG9B is a schematic structural diagram of a chip 9200 according to an embodiment of the present disclosure; DETAILED DESCRIPTION

[0036] The embodiment of the present disclosure proposes a method for establishing a connection.

[0037] In a first aspect, an embodiment of the present disclosure provides a method for establishing a connection, the method comprising:

[0038] The first node sends first information to the second node, wherein the first information is used to assist the second node in information transmission with a third node.

[0039] In the above embodiment, by sending the first information to the second node, the second node can quickly obtain its own IP address.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following:

[0041] the first Internet Protocol IP address information;

[0042] usage information of the first IP address information;

[0043] identification information of the third node;

[0044] IP address information of the third node.

[0045] In the above embodiment, based on the information included in the first information, the second node can accurately transmit information to the third node.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is determined, wherein the first information is determined based on at least one of the following:

[0047] capability information of the third node;

[0048] the first request;

[0049] The second information is obtained from the operation, administration, and maintenance (OAM) node.

[0050] In the above embodiment, the first information is determined based on multiple aspects of information, so that the first information is more accurate and comprehensive.

[0051] In combination with some embodiments of the first aspect, in some embodiments, third information sent by the third node is received, wherein the third information includes capability information of the third node.

[0052] In the above embodiment, the first node can quickly learn the capability information of the third node through the third information.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information of the third node includes at least one of the following:

[0054] Whether the third node supports relay node access and whether the relay transmission capability of the third node is enabled.

[0055] In the above embodiment, the first node can accurately obtain whether the third node supports relay node access.

[0056] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second node includes:

[0057] In response to the first request sent by the second node, the first information is sent to the second node.

[0058] In combination with some embodiments of the first aspect, in some embodiments, a first message sent by the second node to the third node and / or a second message sent by the third node to the second node is relayed.

[0059] In the above embodiment, the number of nodes is increased by relaying the first message sent from the second node to the third node and / or the second message sent from the third node to the second node.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, relay transmission includes at least one of the following:

[0061] Transmitting the first IP packet to the third node according to the first IP address information in the first IP packet header and / or the IP address information of the third node, wherein the first message is included in the first IP packet;

[0062] The second IP packet is transmitted to the first node according to the first IP address information in the second IP packet header and / or the IP address information of the third node, wherein the second message is included in the second IP packet.

[0063] In the above embodiment, information is transmitted to the third node and the first node based on the third node and the first IP address information, thereby realizing relay transmission.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the first message and the second message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the NGAP message or XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0067] In the above embodiment, the relay node can be quickly determined through the information included in the NGAP message or the XnAP message.

[0068] In a second aspect, an embodiment of the present disclosure provides a method for establishing a connection, the method comprising:

[0069] The second node receives first information sent by the first node, wherein the first information is used to assist the second node in information transmission with a third node.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following:

[0071] the first Internet Protocol IP address information;

[0072] usage information of the first IP address information;

[0073] identification information of the third node;

[0074] IP address information of the third node.

[0075] In combination with some embodiments of the second aspect, in some embodiments, a first request is sent to the first node, where the first request is used to request the first information.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is determined by the first node based on at least one of the following:

[0077] capability information of the third node;

[0078] the first request;

[0079] The second information is obtained from the operation, administration, and maintenance (OAM) node.

[0080] With reference to some embodiments of the second aspect, in some embodiments, a first message is sent to the third node through the first node;

[0081] A second message sent by the third node is received through the first node.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node;

[0083] The second message is included in a second IP packet, and the header of the second IP packet contains the first IP address information.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first message and the third message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0086] In combination with some embodiments of the second aspect, in some embodiments, the NGAP message or XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0087] In a third aspect, an embodiment of the present disclosure provides a method for establishing a connection, the method comprising:

[0088] The third node sends third information to the first node, where the third information includes capability information of the third node.

[0089] In combination with some embodiments of the third aspect, in some embodiments, the capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is activated.

[0090] With reference to some embodiments of the third aspect, in some embodiments, a first message sent by a second node is received by the first node;

[0091] A second message is sent to the second node through the first node.

[0092] In conjunction with some embodiments of the third aspect, in some embodiments, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node;

[0093] The second message is included in a second IP packet, and the header of the second IP packet contains the first IP address information.

[0094] In combination with some embodiments of the third aspect, in some embodiments, the first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0095] In combination with some embodiments of the third aspect, in some embodiments, the first message and the third message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0096] In combination with some embodiments of the third aspect, in some embodiments, the NGAP message or XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0097] In a fourth aspect, an embodiment of the present disclosure proposes a first node, which includes at least one of a transceiver module and a processing module; wherein the first node is used to execute the first aspect and an optional implementation method.

[0098] In a fifth aspect, an embodiment of the present disclosure proposes a second node, which includes at least one of a transceiver module and a processing module; wherein the second node is used to execute the second aspect and optional implementation method.

[0099] In the sixth aspect, an embodiment of the present disclosure proposes a third node, which includes at least one of a transceiver module and a processing module; wherein the third node is used to execute the third aspect and optional implementation methods.

[0100] In a seventh aspect, an embodiment of the present disclosure proposes a first node, which includes: one or more processors; wherein the processors are used to execute an optional implementation method of the first aspect.

[0101] In an eighth aspect, an embodiment of the present disclosure proposes a second node, and the second node includes: one or more processors; wherein the processors are used to execute an optional implementation method of the second aspect.

[0102] In a ninth aspect, an embodiment of the present disclosure proposes a third node, and the third node includes: one or more processors; wherein the processor is used to execute an optional implementation method of the third aspect.

[0103] In the tenth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first node, a second node, and a third node; wherein the first node is configured to execute the method described in the optional implementation manner of the first aspect, the second node is configured to execute the method described in the optional implementation manner of the second aspect, and the third node is configured to execute the method described in the optional implementation manner of the third aspect.

[0104] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first, second and third aspects.

[0105] In a twelfth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect and the third aspect.

[0106] In a thirteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first, second and third aspects.

[0107] In a fourteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first, second, and third aspects above.

[0108] It is understandable that the first node, second node, third node, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0109] The present disclosure provides a method for establishing a connection. In some embodiments, the terms "connection establishing method" and "information processing method" and "communication method" are interchangeable; the terms "information transmission device" and "information processing device" and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0110] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0111] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0112] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0113] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0114] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0115] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0116] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0117] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0118] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0119] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0120] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0121] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0122] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0123] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0124] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macrocell", "smallcell", "femtocell", "picocell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0125] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station (subscriber station), mobile unit (mobile unit), subscriber unit (subscribe runit), wireless unit (wireless unit), remote unit (remote unit), mobile device (mobile device), wireless device (wireless device), wireless communication device (wireless communication device), remote device (remoted device), mobile subscriber station (mobile subscriber station), access terminal (access terminal), mobile terminal (mobile terminal), wireless terminal (wireless terminal), remote terminal (remote terminal), handset (handset), user agent (user agent), mobile client (mobile client), client (client), etc.

[0126] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0127] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0128] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0129] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0130] As shown in FIG1 , a communication system 100 includes a first node 101 , a second node 102 , and a third node 103 .

[0131] In some embodiments, the first node 101 may be a VMR-donor, which is a termination node of a network-side New Radio (NR) backhaul. The VMR-donor may be a VMR-donor of a vehicle-mounted relay (VMR).

[0132] In some embodiments, the VMR-donor is an entity on the network side that is attached with an IAB function for transmitting or receiving signals. For example, the VMR-donor can be an evolved NodeB (eNB) with an IAB function, a transmission reception point (TRP) with an IAB function, a next generation NodeB (gNB) with an IAB function in an NR system, a base station with an IAB function in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the VMR-donor. The VMR-donor provided in the embodiments of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of a network device, such as a base station, and the functions of some protocol layers are placed in the CU for centralized control, while the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0133] In some embodiments, the second node 102 may be a VMR.

[0134] In some embodiments, the VMR may include a vehicle-mounted relays generation nodeB (VMR-gNB) 1021, a user plane function (UPF) 1022, which is part of the core network function, a local data network 1023 and a vehicle-mounted relays mobile termination (VMR-MT) 1024.

[0135] In some embodiments, the VMR can also be a mobile IAB or a Mobile Base Station Relay (MBSR), any node that supports access, backhaul, and / or relay functions. Furthermore, an IAB-donor can also be referred to as an access network device that manages a second node, or an IAB host.

[0136] In some embodiments, the third node 103 may be any network element in the core network. Alternatively, the third node 103 may be another base station. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0137] In some embodiments, the third node 103 is, for example, an access and mobility management function (AMF) network element.

[0138] In some embodiments, the technical solution of the present disclosure can be applied to the OpenRAN architecture. In this case, the interfaces between network devices or within network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of OpenRAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0139] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0140] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0141] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (Ultra Mobile Broadband), and other technologies. Broadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), IEEE802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems based on them. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A with 5G, etc.) for application.

[0142] In communications systems, integrated access and backhaul (IAB) supports millimeter wave base stations for wireless access and backhaul. This effectively reduces the need for additional fiber deployment when deploying dense networks and enables wireless relay in next-generation (NG) radio access networks (RANs). Relay nodes, called IAB-nodes, support wireless access and backhaul over NR. The network-side NR backhaul termination node, called an IAB-donor, is a gNB with IAB functionality. The NG-RAN supports IAB by wirelessly connecting the IAB-node to a gNB capable of serving the IAB-node (called an IAB-donor). An IAB-donor consists of an IAB-donor-CU and one or more IAB-donor-DUs. When the gNB-CU-CP and gNB-CU-UP are separate, the IAB-donor may consist of one IAB-donor-CU-CP, multiple IAB-donor-CU-UPs, and multiple IAB-donor-DUs. The IAB-node connects to the upstream IAB-node or IAB-donor-DU via the terminal function subset of the NR Uu interface (called the IAB-MT function in the IAB-node). The IAB-node provides wireless backhaul to the downstream IAB-node and terminal via the network function of the NR Uu interface (called the IAB-DU function in the IAB-node). The F1-C service between the IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and optional intermediate hop IAB-nodes. The F1-U service between the IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and optional intermediate hop IAB-nodes.

[0143] FIG2 is an interactive diagram of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a method for establishing a connection, and the method includes:

[0144] Step S2101 : The third node 103 sends third information to the first node 101 .

[0145] In some embodiments, the first node receives third information sent by the third node.

[0146] In some embodiments, the third node may be a base station or any network element in a core network, which is not limited in the present disclosure.

[0147] In some embodiments, the name of the third node is not limited, and it can be, for example, "access and mobility management function (AMF) network element", "AMF", etc.

[0148] In some embodiments, the name of the first node is not limited, and may be "VMR-donor" or the like.

[0149] In some embodiments, the first node may receive the third information via an NGAP message or an XnAP message.

[0150] In some embodiments, terms such as "NGAP message" and "next generation application protocol (NGAP) message" may be used interchangeably.

[0151] In some embodiments, terms such as "XnAP message" and "Xn Application Protocol (XnAP) message" may be used interchangeably.

[0152] In some embodiments, the third information includes capability information of the third node, i.e., relay capability information of the third node. For example, when the third node is an AMF network element, the third information includes capability information of whether the AMF network element supports VMR.

[0153] In some embodiments, the capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is enabled.

[0154] In some embodiments, the third information may include the capability information of the third node itself, or may include an identifier indicating whether the capability information is turned on or off, or may also include the ability of the third node to support relay transmission, and include indication information indicating whether the capability is activated.

[0155] In some embodiments, during the process of establishing an interface between a first node and a third node, the first node may send a request message to the third node, after which the third node may return third information to the first node. Alternatively, after the interface between the first node and the third node is established, if information on the third node is updated, the third node may also send third information to the first node.

[0156] In some embodiments, the third information is included in an Xn setup feedback message or a RAN configuration update message of the XnAP.

[0157] In some embodiments, the third information is included in the NG Setup Feedback message of NGAP, or the AMF Configuration Update message.

[0158] In some embodiments, the capability information of the third node may be enabled or may not be enabled.

[0159] In some embodiments, the first node stores the third information and uses the third information for relay transmission-related configuration.

[0160] Step S2102 : The second node 102 sends a first request to the first node 101 .

[0161] In some embodiments, the first node 101 receives a first request sent by the second node 102 .

[0162] In some embodiments, the name of the message transmitting the first request is not limited, and may be, for example, an "IAB other information message" or the like.

[0163] In some embodiments, the first request includes a transport layer request message for requesting the IP address of the second node. For example, when the second node is a VMR-MT in a VMR, the first request may be for requesting the IP address of the NG-C.

[0164] In some embodiments, the name of NG-C is not limited. For example, it can also be "5G Next Generation Core Network", "5G Next Generation Core Network", "VMR-gNB", etc.

[0165] In some embodiments, the terms "VMR-MT", "vehicle-mounted relays mobile termination (VMR-MT)", "mobile IAB-MT", "MBSR UE", "MBSR-MT" and the like may be used interchangeably.

[0166] In some embodiments, terms such as "VMR-gNB", "vehicle-mounted relays generation nodeB (VMR-gNB)", "mobile IAB-gNB", "MBSR-gNB", "MBSR-RAN", and "VMR-RAN" can be used interchangeably.

[0167] In some embodiments, the first request is for requesting first information.

[0168] In some embodiments, the name of the message for transmitting the first information is not limited, and may be, for example, "first transport layer information" or the like.

[0169] In some embodiments, the first information is determined by the first node based on at least one of the following: capability information of the third node, the first request, and second information obtained from an operations, administration, and maintenance (OAM) node.

[0170] In some embodiments, the second information obtained from the operation, administration and maintenance (OAM) node is transmission configuration information of the OAM node.

[0171] In some embodiments, the first information includes at least one of the following: first Internet Protocol (IP) address information, usage information of the first IP address information, identification information of the third node, and IP address information of the third node.

[0172] In some embodiments, the first Internet Protocol (IP) address information is first IP address information allocated to the second node.

[0173] In some embodiments, the usage information of the first IP address information is used to indicate the usage of the first IP address information.

[0174] In some embodiments, the usage information of the first IP address information includes at least one of the following: used for NG-C (control plane information of NG interface) transmission, NG-U (user plane information of NG interface) transmission, non-NG (information of non-NG interface), Xn-C (control plane of Xn interface) transmission, Xn-U (user plane of Xn interface) transmission, and alltraffic (all traffic) transmission.

[0175] In some embodiments, the usage information of the first IP address information may correspond one-to-one with the third node identification information, that is, one first IP address information is used for information transmission with one specific third node.

[0176] In some embodiments, the first IP address information includes one or more IP addresses, each of which is used to transmit different information. For example, IP address 1 is used to transmit NG-C messages. When the second node sends an NGAP message to the third node, the second node sets IP address 1 as the source address of the IP packet.

[0177] In some embodiments, the identification information of the third node may be the name or identifier of the third node. For example, if the third node is an NG-RAN node, the identification information may be an NG-RAN node ID; for example, if the third node is an AMF network element, the identification information of the third node may be the name of the AMF network element.

[0178] In some embodiments, the third node may be a core network node or an NG-RAN node.

[0179] In some embodiments, the terms "NG-RAN node ID", "next generation radio access network node identification (NG-RAN node ID)" and the like may be used interchangeably.

[0180] In some embodiments, the order of the above-mentioned step S2101 and step S2102 can be interchanged, or they can be executed simultaneously, which is not limited in this disclosure.

[0181] Step S2103 : The first node 101 sends first information to the second node 102 .

[0182] In some embodiments, the first node sends the first information to the second node in response to the first request sent by the second node.

[0183] In some embodiments, the first node determines first information, where the first information is determined based on at least one of the following: capability information of the third node, the first request, and second information obtained from the operation, administration, and maintenance (OAM) node. A specific implementation of the first information is described in the description of the optional implementation of step S2102 and is not further described here.

[0184] In some embodiments, the first node receives third information sent by the third node, wherein the third information includes capability information of the third node. The receiving and processing of the third information can refer to the description of the optional implementation of step S2101 and will not be repeated here.

[0185] In some embodiments, the capability information of the third node includes at least one of the following: whether the third node supports relay node access and whether the relay transmission capability of the third node is enabled. For specific implementation methods, refer to the relevant description of the optional implementation method of step S2101 and will not be repeated here.

[0186] In some embodiments, the second node receives first information sent by the first node, wherein the first information is used to assist the second node in information transmission with a third node.

[0187] In some embodiments, the first information includes at least one of the following: first Internet Protocol IP address information, usage information of the first IP address information, identification information of the third node, and IP address information of the third node. The specific implementation method refers to the relevant description of the optional implementation method of step S2102, which will not be repeated here.

[0188] In some embodiments, if the second node is a VMR-MT, after receiving the first information, the second node can forward it to the VMR-gNB through an internal connection.

[0189] In some embodiments, if the first node 101 has not received the third information sent by the third node 103 when receiving the first request sent by the second node 102 , the first node 101 may send a rejection message to the second node 102 .

[0190] In some embodiments, if the first node 101 has not received the third information sent by the third node 103 when receiving the first request sent by the second node 102, the first node 101 can request the third information from the third node 103, and after requesting the third information, generate the first information, and then send the first information to the second node 102.

[0191] Step S2104 : The second node 102 sends a first message to the first node 101 .

[0192] In some embodiments, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node.

[0193] In some embodiments, the first IP packet is included in a first RRC message or a BH RLC channel sent by the second node to the first node.

[0194] In some embodiments, terms such as "RRC message" and "Radio Resource Control (RRC) message" may be used interchangeably.

[0195] In some embodiments, the first RRC message may be an uplink information transfer (ULInformationTransfer) message.

[0196] In some embodiments, terms such as "ULInformationTransfer message" and "uplink information transfer message" can be used interchangeably.

[0197] In some embodiments, the first message is any one of the following: NGAP message, XnAP message.

[0198] In some embodiments, the NGAP message or the XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0199] In some embodiments, the type indication information of the first node is used to indicate the type of the first node, for example, the first node is a relay node, or the first node is a relay donor, etc.

[0200] In some embodiments, the first node identifier may be the name of the first node, or may be ID information indicating the first node. For example, if the first node is a VMR-donor, the first node identifier may be the name of the VMR-donor, or the ID of the VMR-donor.

[0201] In some embodiments, if the second node is a VMR-MT, for the VMR-MT, if NG-C related information needs to be transmitted, it needs to include a dedicated infoNGc and submit a ULInformationTransfer message to the lower level for transmission.

[0202] In some embodiments, the dedicated infoNGc is an IE dedicated infof1c, which is used to transmit specific NG-C related information between the third node and the second node. The information carried consists of NGAP messages encapsulated in SCTP / IP or F1-C related (SCTP) / IP packets, and the RRC layer is transparent to this information.

[0203] In some embodiments, the terms "dedicated infoNGc", "dedicatedInfoNGc", "dedicated information next generation core (dedicatedInfoNGc)" and the like may be used interchangeably.

[0204] In some embodiments, the terms "SCTP", "stream control transmission protocol (SCTP)", etc. can be used interchangeably.

[0205] Step S2105 : The first node 101 forwards the first message to the third node 103 .

[0206] In some embodiments, the first node relays the first message sent by the second node to the third node.

[0207] In some embodiments, the first node may transmit a first IP packet to the third node based on the first IP address information in the first IP packet header and / or the IP address information of the third node, wherein the first message is included in the first IP packet.

[0208] In some embodiments, the first IP packet is included in a first RRC message or a BH RLC channel sent by the second node to the first node. For specific implementation, refer to the description of the optional implementation of step S2104, which will not be repeated here.

[0209] In some embodiments, the first message is any one of the following: an NGAP message, an XnAP message.

[0210] In some embodiments, the NGAP message or XnAP message includes at least one of the following: type indication information of the first node, first node identifier. The specific implementation method refers to the relevant description of the optional implementation method of step S2104, which will not be repeated here.

[0211] In some embodiments, the third node receives the first message sent by the second node through the first node.

[0212] In some embodiments, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node.

[0213] Step S2106 : The third node 103 sends a second message to the first node 101 .

[0214] In some embodiments, the second message is included in a second IP packet, and the header of the second IP packet contains the first IP address information.

[0215] In some embodiments, the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0216] In some embodiments, the second RRC message may be a downlink transmission information (DLInformationTransfer) message.

[0217] In some embodiments, terms such as "DLInformationTransfer message" and "downlink information transfer message" can be used interchangeably.

[0218] In some embodiments, the second message may be a response message to the first message.

[0219] In some embodiments, the second message is any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0220] In some embodiments, the NGAP message or the XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0221] In some embodiments, the type indication information of the first node is used to indicate the type of the first node, for example, the first node is a relay node, or the first node is a relay donor, etc.

[0222] In some embodiments, the first node identifier may be the name of the first node, or may be ID information indicating the first node. For example, if the first node is a VMR-donor, the first node identifier may be the name of the VMR-donor, or the ID of the VMR-donor.

[0223] Step S2107 : The first node 101 forwards the second message to the second node 102 .

[0224] In some embodiments, the first node relays the second message sent by the third node to the second node.

[0225] In some embodiments, the first node may transmit a second IP packet to the first node based on the first IP address information in the second IP packet header and / or the IP address information of the third node, wherein the second message is included in the second IP packet.

[0226] In some embodiments, the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node. For specific implementations, refer to the description of the optional implementation of step S2106 and will not be repeated here.

[0227] In some embodiments, the second message is any one of the following: NGAP message, XnAP message.

[0228] In some embodiments, if the second node is a VMR-MT, after receiving the DLInformTransfer message, if the DLInformTransfer message contains a dedicated infoNGc, the second node forwards the dedicated infoNGc to the collocated VMR-gNB.

[0229] In some embodiments, the order of the above steps S2104, S2105, S2106, and S2107 can be interchanged. For example, step S2106 and step S2107 are performed first, and then step S2104 and step S2105 are performed.

[0230] In some embodiments, the above steps S2104, S2105, S2106, and S2107 may also be performed in parallel, for example, step S2104 and step S2106 are performed simultaneously, and step S2105 and step S2107 are performed simultaneously. Alternatively, step S2104 and step S2107 are performed simultaneously, or step S2105 and step S2106 are performed simultaneously, etc., which is not limited in this disclosure.

[0231] The communication method according to the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, and steps S2101+S2102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0232] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0233] FIG3A is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a method for processing information, which is used by a first node 101 and includes:

[0234] Step S3101: receiving capability information of the third node sent by the third node 103.

[0235] In some embodiments, the first node receives capability information of the third node sent by the third node.

[0236] Step S3102, generate first information.

[0237] In some embodiments, the first node generates the first information based on capability information of the third node.

[0238] In some embodiments, the first node generates the first information based on the second information obtained from the operations, administration and maintenance (OAM) node.

[0239] Step S3103: Receive the first request sent by the second node 102.

[0240] In some embodiments, the first node receives a first request sent by the second node.

[0241] Step S3104: Send the first information to the second node 102.

[0242] Step S3105 , receiving the first message sent by the second node 102 .

[0243] Step S3106: forward the first message to the third node 103.

[0244] Step S3107: Receive the second message sent by the third node 103.

[0245] Step S3108: forward the second message to the second node 102.

[0246] For a detailed description of steps S3101 - S3108 , please refer to the above embodiment description.

[0247] The communication method according to the embodiments of the present disclosure may include at least one of steps S3101 to S3108. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, step S3103 may be implemented as an independent embodiment, and steps S3101+S3102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0248] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0249] FIG3B is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a method for processing information, which is used by the first node 101 and includes:

[0250] Step S3201: Receive third information sent by the third node 103.

[0251] In some embodiments, the first node receives third information sent by the third node.

[0252] Step S3202: Generate first information.

[0253] Step S3203: Send first information to the second node 102.

[0254] Step S3204: relay the first message sent by the second node 102 to the third node 103 and / or the second message sent by the third node 103 to the second node 102.

[0255] In some embodiments, the first node relays a first message sent by the second node to the third node and / or a second message sent by the third node to the second node.

[0256] For a detailed description of steps S3201 - S3204 , please refer to the above embodiment description.

[0257] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, step S3203 may be implemented as an independent embodiment, and steps S3201+S3202 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0258] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0259] FIG3C is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to a method for processing information, which is used by the first node 101 and includes:

[0260] Step S3301: Send first information to the second node.

[0261] In some embodiments, the first node sends first information to the second node.

[0262] Optionally, the first information includes at least one of the following:

[0263] First Internet Protocol IP address information;

[0264] Usage information of the first IP address information;

[0265] identification information of the third node;

[0266] IP address information of the third node.

[0267] Optionally, first information is determined, wherein the first information is determined based on at least one of the following:

[0268] Capability information of the third node;

[0269] First request;

[0270] The second information is obtained from the operation, administration, and maintenance (OAM) node.

[0271] Optionally, third information sent by a third node is received, where the third information includes capability information of the third node.

[0272] Optionally, the capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is enabled.

[0273] Optionally, sending the first information to the second node includes:

[0274] In response to the first request sent by the second node, the first information is sent to the second node.

[0275] Optionally, a first message sent by the second node to the third node and / or a second message sent by the third node to the second node is relayed.

[0276] Optionally, the relay transmission includes at least one of the following:

[0277] Transmitting a first IP packet to the third node according to the first IP address information in the first IP packet header and / or the IP address information of the third node, wherein the first message is included in the first IP packet;

[0278] A second IP packet is transmitted to the first node according to the first IP address information in the second IP packet header and / or the IP address information of the third node, wherein the second message is included in the second IP packet.

[0279] Optionally, the first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0280] Optionally, the first message and the second message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0281] Optionally, the NGAP message or the XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0282] For a detailed description of step S3301, please refer to the above embodiment description.

[0283] The communication method involved in the embodiment of the present disclosure may include step S3301.

[0284] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0285] FIG4A is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for processing information, which is used by the second node 102 and includes:

[0286] Step S4101: Send a first request to the first node 101.

[0287] In some embodiments, the second node sends the first request to the first node.

[0288] Step S4102: Receive the first information sent by the first node 101.

[0289] In some embodiments, the second node receives the first information sent by the first node.

[0290] Step S4103: Send a first message to the first node 101.

[0291] In some embodiments, the second node sends the first message to the first node.

[0292] Step S4104: Receive the second message forwarded by the first node 101.

[0293] In some embodiments, the second node receives the second message forwarded by the first node.

[0294] For a detailed description of steps S4101 - S4104 , please refer to the above embodiment description.

[0295] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4103. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, and steps S4101+S4102 may be implemented as independent embodiments, but are not limited thereto.

[0296] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0297] FIG4B is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a method for processing information, which is used by the second node 102 and includes:

[0298] Step S4201, receiving first information.

[0299] In some embodiments, the second node receives the first information sent by the first node.

[0300] Optionally, the first information includes at least one of the following:

[0301] First Internet Protocol IP address information;

[0302] Usage information of the first IP address information;

[0303] identification information of the third node;

[0304] IP address information of the third node.

[0305] Optionally, a first request is sent to the first node, where the first request is used to request first information.

[0306] Optionally, the first information is determined by the first node based on at least one of the following:

[0307] Capability information of the third node;

[0308] First request;

[0309] The second information is obtained from the operation, administration, and maintenance (OAM) node.

[0310] Optionally, sending a first message to the third node through the first node;

[0311] A second message sent by the third node is received through the first node.

[0312] Optionally, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node;

[0313] The second message is included in a second IP packet, and the header of the second IP packet includes the first IP address information.

[0314] Optionally, the first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0315] Optionally, the first message and the third message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0316] Optionally, the NGAP message or the XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0317] For a detailed description of step S4201, please refer to the above embodiment description.

[0318] The communication method involved in the embodiment of the present disclosure may include step S4201.

[0319] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0320] FIG5A is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a method for processing information, which is used by the third node 103 and includes:

[0321] Step S5101: Send third information to the first node 101.

[0322] In some embodiments, the third node sends third information to the first node.

[0323] Step S5102 , receiving a first message forwarded by the first node 101 .

[0324] In some embodiments, the third node receives the first message forwarded by the first node.

[0325] Step S5103: Send a second message to the first node 101.

[0326] In some embodiments, the third node sends the second message to the first node.

[0327] For a detailed description of steps S5101 - S5103 , please refer to the above embodiment description.

[0328] The communication method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5103. For example, step S5101 may be implemented as an independent embodiment, step S5102 may be implemented as an independent embodiment, and steps S5101+S5102 may be implemented as independent embodiments, but are not limited thereto.

[0329] The steps in the embodiments of the present disclosure and their optional implementations may be arbitrarily combined with part or all of the steps in other embodiments, and may also be arbitrarily combined with the optional implementations of other embodiments.

[0330] FIG5B is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to a method for processing information, which is used by the third node 103 and includes:

[0331] Step S5201: Send third information to the first node 101.

[0332] In some embodiments, the third node sends third information to the first node.

[0333] Optionally, the capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is enabled.

[0334] Optionally, receiving, through the first node, a first message sent by the second node;

[0335] A second message is sent to the second node through the first node.

[0336] Optionally, the first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node;

[0337] The second message is included in a second IP packet, and the header of the second IP packet includes the first IP address information.

[0338] Optionally, the first IP packet is included in a first RRC message or a BH RLC channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

[0339] Optionally, the first message and the second message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

[0340] Optionally, the NGAP message or the XnAP message includes at least one of the following: type indication information of the first node, and the first node identifier.

[0341] For a detailed description of step S5201, please refer to the above embodiment description.

[0342] The communication method involved in the embodiment of the present disclosure may include step S5201.

[0343] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0344] The following is an exemplary introduction to the above method.

[0345] The present disclosure provides a method for solving the information interaction problem between a VMR node and a UE served by the VMR node and a core network. Optional implementation solutions are as follows:

[0346] The NGAP message can be forwarded to the AMF via the backhaul radio link control channel (BH RLC channel) via the VMR-donor, as shown in Figure 6. Figure 6 is a schematic diagram of the NGAP message being forwarded to the AMF via the backhaul radio link control channel via the VMR-donor.

[0347] 1. A first node sends first transport layer information to a second node, wherein the first transport layer information is used for information exchange between the second node and a third node through the first node.

[0348] 2. Based on 1, the first node receives the IP packet from the second node, and forwards the IP packet to the third node according to the second transport layer information in the IP packet header.

[0349] The second transmission layer information is generated according to the first transmission layer information.

[0350] In some embodiments, the second transport layer information may include: source IP address information and destination IP address information.

[0351] 3. Based on 1 or 2, the information of the interaction between the first node and the third node includes at least one of the following:

[0352] -NGAP messages;

[0353] -XnAP messages;

[0354] 4. Based on 3, wherein the NGAP message or XnAP message is included in an RRC message or a BH RLC channel sent by the second node to the first node, such as ULInformationTransfer or DLInformationTransfer.

[0355] 5. Based on 3, the NGAP message or XnAP message includes information about the relay node, wherein the relay node information is used by the third node to send information to the first node based on the information.

[0356] 6. Based on 5, the relay node information includes at least one of the following:

[0357] - Relay node indication;

[0358] - Relay node identification;

[0359] In some embodiments, the first node is a relay node.

[0360] 7. Based on 1, the first node determines the first transport layer information based on at least one of the following information:

[0361] -Relay capability information of the third node;

[0362] -Transport layer request information of the second node;

[0363] -OAM transmission configuration information;

[0364] 8. Based on 7, the “relay capability information of the third node” includes:

[0365] The first node receives relay capability information of the third node from the third node.

[0366] The relay capability information is used to indicate whether the third node supports relay node access.

[0367] 9. Based on 7, the “transport layer request information of the second node” includes:

[0368] The first node receives transport layer request information from the second node, and sends transport layer information to the second node in response to the transport layer request information from the second node.

[0369] 10. Based on 9, the "transport layer request information" includes at least one of the following information:

[0370] -IP address request;

[0371] -Third node information request;

[0372] 11. Based on 1-3, the “first transport layer information” includes at least one of the following information:

[0373] -IP address information;

[0374] -Information on the use of IP addresses;

[0375] - identification information of the third node;

[0376] -IP address information of the third node;

[0377] In some embodiments, the IP address information refers to one or more IP addresses used for different information transmissions, such as an IP address used for NG-C transmission, or an IP address used for XN-C transmission.

[0378] As shown in FIG7 , FIG7 is an interactive schematic diagram of a method for establishing a connection according to an embodiment of the present disclosure.

[0379] Step 100: The AMF (third node) sends an NGAP message (e.g., NG Setup Feedback message) to the VMR-donor (first node). The message may include information about whether the AMF supports VMR capabilities (relay capability information of the third node). The VMR-donor stores the information and uses it for relay transmission-related configuration.

[0380] Step 101: The VMR-MT (second node) of the VMR sends an IAB other information message to the VMR-donor. The message includes transport layer request information, such as the IP address of the requested NG-C or the information of the AMF.

[0381] In step 102, the VMR-donor sends the first transport layer information to the VMR-MT. The VMR-MT receives the first transport layer information and forwards it to the VMR-gNB through an internal connection.

[0382] The first transport layer information includes at least one of the following information:

[0383] -IP address information, used to indicate the first IP address information allocated to the VMR;

[0384] - Information about the purpose of the IP address (e.g., NG-C, NG-U);

[0385] - Identification information of the third node (e.g. AMF name, NG-RAN node ID);

[0386] -IP address information of the third node;

[0387] Step 103: The VMR-gNB (the second subnode in the second node) selects the AMF according to the first transport layer information and sends an NGAP message (e.g., an NG establishment request message) to the AMF.

[0388] The NGAP message is included in an IP packet, a header of the IP packet includes second transport layer information, and the second transport layer information is generated according to the first transport layer information.

[0389] The message always includes a VMR indication and / or a VMR-donor identifier.

[0390] In some embodiments, the NGAP message is included in an RRC message or a BH RLC channel sent by the VMR-MT to the VMR-donor. The RRC message may be a ULInformationTransfer message.

[0391] Possible spec impacts are as follows:

[0392] 1> For VMR-MT, if NG-C related information needs to be transmitted:

[0393] 2> Contains dedicatedInfoNGc (NG-C dedicated information);

[0394] 1>Submit the ULInformationTransfer message to the lower level for transmission, and this process ends.

[0395] After receiving the ULInformationTransfer message, the VMR-donor forwards the IP packet to the AMF based on the second transmission information in the IP header of the encapsulated NGAP message. The AMF receives the NGAP message in the IP packet.

[0396] Step 104: The AMF sends an NGAP message (e.g., NG setup feedback message) to the VMR-gNB.

[0397] In some embodiments, the AMF sends an IP packet including the NGAP message to the VMR-donor, and the VMR-donor forwards the IP packet to the VMR-gNB based on the information in the IP packet header.

[0398] The NGAP message is included in an RRC message or a BH RLC channel sent by the VMR-donor to the VMR-MT. The RRC message may be a DLInformationTransfer message.

[0399] Possible spec impacts are as follows:

[0400] After receiving the DLInformationTransfer message, the VMR-MT shall:

[0401] 1> If dedicatedInfoNGc is included:

[0402] 2> Forward the dedicated information of NG-C to the collocated VMR-gNB. In some embodiments, the dedicatedInfoNGc message is described as follows:

[0403] DedicatedInfoNGc

[0404] IE dedicated infof1c is used to transmit VMR-gnb specific NG-C related information between the network and VMR nodes. The information carried consists of NGAP messages encapsulated in SCTP / IP or F1-C related (SCTP) / IP packets, and the RRC layer is transparent to this information.

[0405] Step 105: The UE establishes an RRC connection through the VMR.

[0406] In step 106, the VMR selects an AMF for the UE based on the first transmission information. The VMR-gNB sends an NGAP message (e.g., an Initial UE message) to the selected AMF. The information that may be included in the NGAP message is the same as in step 103 and is not further described here.

[0407] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0408] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0409] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0410] Figure 8A is a schematic diagram of the structure of the first node proposed in an embodiment of the present disclosure. As shown in Figure 8A, the first node 8100 may include: at least one of a transceiver module 8101, a processing module 8102, etc. In some embodiments, the transceiver module 8101 is used to send the first information to the second node. Optionally, the transceiver module 8101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first node 101 in any of the above methods (for example, step S2101, step S2102, step S2104, step S2105, step S2106, step S2107, but not limited thereto), which will not be repeated here.

[0411] Figure 8B is a schematic diagram of the structure of the second node 102 proposed in an embodiment of the present disclosure. As shown in Figure 8B, the second node 8200 may include at least one of a transceiver module 8201 and a processing module 8202. In some embodiments, the transceiver module 8201 is configured to send a first request to the first node. Optionally, the transceiver module 8201 is configured to execute at least one of the communication steps (e.g., steps S2101, S2103, S2104, and S2107, but not limited thereto) performed by the second node 102 in any of the above methods, which will not be further described here.

[0412] Figure 8C is a schematic diagram of the structure of the third node 103 proposed in an embodiment of the present disclosure. As shown in Figure 8C, the third node 8300 may include at least one of a transceiver module 8301 and a processing module 8302. In some embodiments, the transceiver module 8301 is configured to send third information to the first node. Optionally, the transceiver module 8301 is configured to perform at least one of the communication steps (such as sending and / or receiving) performed by the third node 103 in any of the above methods (e.g., steps S2105 and S2106, but not limited thereto), which will not be further described here.

[0413] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0414] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0415] Figure 9A is a schematic diagram of the structure of a communication device 9100 proposed in an embodiment of the present disclosure. Communication device 9100 can be a first node, a second node, or a third node. It can also be a chip, chip system, or processor that supports the first node to implement any of the above methods. It can also be a chip, chip system, or processor that supports the second node to implement any of the above methods. It can also be a chip, chip system, or processor that supports the third node to implement any of the above methods. Communication device 9100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0416] As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 9100 is used to perform any of the above methods.

[0417] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 may be located outside the communication device 9100.

[0418] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the transceiver 9103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2103, and step S2105, but not limited thereto), and the processor 9101 performs at least one of the other steps (for example, step S2102, step S2104).

[0419] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0420] In some embodiments, the communication device 9100 may include one or more interface circuits 9104. Optionally, the interface circuit 9104 is connected to the memory 9102. The interface circuit 9104 may be configured to receive signals from the memory 9102 or other devices, and may be configured to send signals to the memory 9102 or other devices. For example, the interface circuit 9104 may read instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0421] The communication device 9100 described in the above embodiments may be a first node, a second node, or a third node, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9A . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0422] 9B is a schematic diagram of the structure of a chip 9200 according to an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9B , but the present disclosure is not limited thereto.

[0423] The chip 9200 includes one or more processors 9201 , and the chip 9200 is configured to execute any of the above methods.

[0424] In some embodiments, the chip 9200 further includes one or more interface circuits 9202. Optionally, the interface circuit 9202 is connected to the memory 9203. The interface circuit 9202 can be used to receive signals from the memory 9203 or other devices, and can be used to send signals to the memory 9203 or other devices. For example, the interface circuit 9202 can read instructions stored in the memory 9203 and send the instructions to the processor 9201.

[0425] In some embodiments, the interface circuit 9202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2103, step S2105, but not limited to this), and the processor 9201 executes at least one of the other steps (for example, step S2102, step S2104, etc.).

[0426] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0427] In some embodiments, the chip 9200 further includes one or more memories 9203 for storing instructions. Alternatively, all or part of the memories 9203 may be located outside the chip 9200.

[0428] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0429] The present disclosure also provides a program product, which, when executed by the communication device 9100, enables the communication device 9100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0430] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A method for establishing a connection, characterized in that: include: The first node sends first information to the second node, wherein the first information is used to assist the second node in information transmission with a third node.

2. The method according to claim 1, characterized in that The first information includes at least one of the following: the first Internet Protocol IP address information; usage information of the first IP address information; identification information of the third node; The IP address information of the third node.

3. The method according to any one of claims 1-2, characterized in that: Also includes: Determine the first information, wherein the first information is determined based on at least one of the following: capability information of the third node; the first request; The second information is obtained from the operation, administration and maintenance (OAM) node.

4. The method according to claim 3, characterized in that Also includes: Receive third information sent by the third node, wherein the third information includes capability information of the third node.

5. The method according to claim 3 or 4, characterized in that The capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is enabled.

6. The method according to any one of claims 1 to 5, characterized in that: The sending the first information to the second node includes: In response to the first request sent by the second node, the first information is sent to the second node.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: Relay transmission is performed on a first message sent by the second node to the third node and / or a second message sent by the third node to the second node.

8. The method according to claim 7, characterized in that Relay transmission, including at least one of the following: Transmitting the first IP packet to the third node according to the first IP address information in the first IP packet header and / or the IP address information of the third node, wherein the first message is included in the first IP packet; The second IP packet is transmitted to the first node according to the first IP address information in the second IP packet header and / or the IP address information of the third node, wherein the second message is included in the second IP packet.

9. The method according to claim 8, characterized in that The first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

10. The method according to any one of claims 7 to 9, characterized in that: The first message and the second message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

11. The method according to claim 10, characterized in that The NGAP message or the XnAP message includes at least one of the following: type indication information of the first node and the first node identifier.

12. A method for establishing a connection, characterized in that: include: The second node receives first information sent by the first node, wherein the first information is used to assist the second node in information transmission with a third node.

13. The method according to claim 12, characterized in that The first information includes at least one of the following: the first Internet Protocol IP address information; The purpose information of the first IP address information; identification information of the third node; The IP address information of the third node.

14. The method according to claim 12 or 13, characterized in that Also includes: A first request is sent to the first node, wherein the first request is used to request the first information.

15. The method according to claim 14, characterized in that The first information is determined by the first node based on at least one of the following: capability information of the third node; the first request; The second information is obtained from the operation, administration and maintenance (OAM) node.

16. The method according to any one of claims 12 to 15, characterized in that: Also includes at least one of the following: Sending a first message to the third node through the first node; A second message sent by the third node is received through the first node.

17. The method according to claim 16, characterized in that The first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node; The second message is included in a second IP packet, and the packet header of the second IP packet contains the first IP address information.

18. The method according to claim 17, characterized in that The first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

19. The method according to any one of claims 16 to 18, characterized in that: The first message and the third message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

20. The method of claim 19, wherein: The NGAP message or the XnAP message includes at least one of the following: type indication information of the first node and the first node identifier.

21. A method for establishing a connection, characterized in that: include: The third node sends third information to the first node, wherein the third information includes capability information of the third node.

22. The method according to claim 21, characterized in that The capability information of the third node includes at least one of the following: whether the third node supports relay node access, and whether the relay transmission capability of the third node is enabled.

23. The method of claim 18, wherein: Also includes at least one of the following: receiving, through the first node, a first message sent by the second node; A second message is sent to the second node through the first node.

24. The method of claim 23, The first message is included in a first IP packet, and a header of the first IP packet includes IP address information of the third node; The second message is included in a second IP packet, and the packet header of the second IP packet contains the first IP address information.

25. The method of claim 24, wherein: The first IP packet is included in a first RRC message or a backhaul radio link control (BH RLC) channel sent by the second node to the first node, and the second IP packet is included in a second RRC message or a BH RLC channel sent by the third node to the first node.

26. The method according to any one of claims 23 to 25, characterized in that: The first message and the second message are any one of the following: NG interface protocol NGAP message, Xn application protocol XnAP message.

27. The method of claim 26, wherein: The NGAP message or the XnAP message includes at least one of the following: type indication information of the first node and the first node identifier.

28. A first node, characterized in that: The device comprises: The transceiver module is used to send first information to the second node, wherein the first information is used to assist the second node in information transmission with a third node.

29. A second node, characterized in that: The device comprises: The transceiver module is used to receive first information sent by the first node, wherein the first information is used to assist the second node and the third node in information transmission.

30. A third node, characterized in that: The device comprises: The transceiver module is used to send third information to the first node, wherein the third information includes capability information of the third node.

31. A node, characterized in that: include: one or more processors; The processor is used to execute the information processing method described in any one of claims 1-11, or to execute the information processing method described in any one of claims 12-20, or to execute the information processing method described in any one of claims 21-27.

32. A communication system, characterized in that: It includes a first node, a second node, and a third node, wherein the first node is configured to implement the information transmission method described in any one of claims 1-11, the second node is configured to implement the information processing method described in any one of claims 12-20, and the third node is configured to implement the information transmission method described in any one of claims 21-27.

33. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the information processing method according to any one of claims 1-11, 12-20 or 21-27.

Images