Wireless access network nodes, core network nodes, and methods in wireless communication networks.

Abstract

A method is provided that is performed by a first Radio Access Network (RAN) node for processing supported Information Elements (IEs) for a procedure involving multiple network nodes to a second RAN node of a wireless communication system. The first RAN node (301) transmits a first indication towards the second RAN node. The first indication indicates whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure. The first RAN node receives (302) a response from the second RAN node that includes a second indication. The second indication indicates whether one or more second IEs that are part of the procedure are supported by the second RAN node during the procedure.

Description

Technical Field

[0001] This embodiment relates to a radio access node, a core network node, and methods therein. In some aspects, it relates to the processing of information elements (IEs) supported in procedures involving multiple network nodes in a wireless communication system.

Background Art

[0002] In a typical wireless communication network, a wireless device, also known as a mobile station, station (STA), and / or user equipment (UE), Wide area network), WiFi network Local area networks such as or 、 a cellular network including a radio access network (RAN) part and a core network (CN) part Ku communicates via. The RAN is divided into geographical area service areas or cell areas, which can also be referred to as beams or beam groups, Wireless access nodes, etc. covering each service area or cell area is served by a wireless network node such as, for example, a Wi-Fi access point or a radio base station (RBS), etc. The radio access node is also denoted as, for example, Node B, evolved Node B (eNB), or gNB in 5th generation (5G) communication in some networks. A service area or cell area is a geographical area where wireless coverage is provided by a wireless network node. The wireless network node communicates with wireless devices within the range of the wireless network node via an air interface operating at radio frequencies.

[0003] 3GPP is a standards organization that specifies standards for the evolution of cellular systems, including 3G, 4G, 5G, and future evolutions. The specifications for Advanced Packet Systems (EPS), also known as fourth-generation (4G) networks, were completed within the Third Generation Partnership Project (3GPP). As part of the ongoing evolution of networks, new releases from 3GPP specify 5G networks, also known as 5G New Radio (NR).

[0004] The 5G NR frequency band is divided into two different frequency ranges: Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 includes the sub-6GHz frequency band. While some of these bands have been used in conventional standards, they are extended to cover the potentially new spectrum from 410MHz to 7125MHz, and FR2 includes the 24.25GHz to 52.6GHz frequency band. This millimeter-wave band has a shorter communication range than the FR1 band, but offers a wider available bandwidth.

[0005] Multi-antenna technology can significantly increase the data rate and reliability of wireless communication systems. In the case of a wireless connection between a single user (such as an UE) and a base station, performance is particularly improved when both the transmitter and receiver are equipped with multiple antennas, resulting in a multi-input, multiple-output (MIMO) communication channel. This may be referred to as single-user (SU)-MIMO. In scenarios where MIMO technology is used for wireless connections between multiple users and a base station, MIMO further increases cell capacity by spatially isolating users, allowing them to communicate with the base station simultaneously using the same time-frequency resources. This may be referred to as multi-user (MU)-MIMO. Note that MU-MIMO has advantages when each UE has only one antenna. Such systems and / or related technologies are typically referred to as MIMO.

[0006] Since Release 99, 3GPP has introduced a mechanism in application protocols that specify open network interfaces such as NG Application Protocol (NGAP), S1AP, and XnAP that allows senders to control receiver behavior when understanding is essential for control.

[0007] Each elementary procedure (EP) and each information element (IE) contained in the message of the elementary procedure is assigned a "criticality," and three criticalities are defined: "reject," "ignore," and "ignore and notify." However, in 3G, 4G, and 5G, only "reject" and "ignore" are used.

[0008] If a logical node receives an information element (IE) assigned a criticality of "reject," and the logical node does not support the function associated with that information, the logical node terminates the procedure with a failure and signals an error message to the sending node that it does not support that protocol element / EP, regardless of whether the node does not support the function of the entire procedure or only the information element (IE) with a criticality of "reject."

[0009] The sending node can infer from either the procedure code or IE identifier received in the error message that the receiving node does not support any protocol elements, and can adapt future communications by not triggering any further procedures or by omitting any IEs that the receiving node does not support.

[0010] Procedures or IEs associated with the "ignore" criticality allow the receiving node to process the message content and continue performing their respective functions without informing the sending node that the IE is not supported. In this case, the receiving node discards IEs that are not supported by the "ignore" criticality; that is, functions associated with such IEs are not performed by the receiving node.

[0011] The above mechanism allows nodes configured according to a "higher" version of a particular application protocol to work together with nodes configured according to a "lower" version of the same application protocol. backward compatibility This ensures interoperability between peer nodes in future implementations at different levels. The same mechanism also guarantees forward compatibility. That is, if a newer version of the AP supports a newer IE and marks such an IE as criticality ignored, a receiving node supporting an older version of the AP can discard the unsupported IE and continue functioning according to the supported features. However, if a node supporting an older version of the AP receives a criticality "rejected" IE from a newer version of the AP, the node must terminate the process and return an error message, as described above.

[0012] In principle, the concept of "version" itself would disappear, and deployments could be selected from a set of functions regardless of the "3GPP release." [Overview of the project] [Problems that the invention aims to solve]

[0013] As part of the development of embodiments of the present invention, we will describe the problems initially identified by the inventors.

[0014] While an OAM (Operations, Management, and Maintenance) configuration and homogeneous functional deployment—that is, ensuring all nodes support the same functionality—can solve most problems, existing "criticality mechanisms" only work in a single interface instance where one node is "placed" at both ends of the interface. A criticality mechanism is a mechanism for processing criticality information set for individual IEs and / or IE groups, as defined, for example, in 3GPP TS38.413 v17.0.0.

[0015] When handover or dual connection is performed on the X2 / Xn interface, the "criticality mechanism" assigns a criticality of "deny" to critical procedures or IEs where a function cannot operate without a supporting node behind it, allowing the node to gradually learn the support level of the other node. It operates in a manner The X2 interface is a point-to-point logical interface between two eNodeBs. The Xn interface is an interface between two NG-RAN nodes.

[0016] However, in the case of mobility involving multiple interface instances, i.e., handovers that must be performed via CN, multiple interface instances of the RAN-CN interface are involved. One on the source side, one on the target side, and between CN nodes. For example, this occurs when the source RAN node and the target RAN node are NG-RAN nodes connected to different Access and Mobility Management Functions (AMFs), or when the source RAN node is an E-UTRAN (Advanced UMTS Terrestrial Radio Access Network) node connected to an EPC, and the target RAN node is an NG-RAN node and an AMF, in the case of inter-system mobility. In other words, functions such as handovers and their associated signaling procedures are involved. 3 The criticality mechanism does not function when involving more than one network node. One example is an NG-based handover involving three or more network nodes.

[0017] For application protocols defined in RAN3, up to four nodes may be involved in total: the source and target RAN nodes, and the source and target CN nodes, which may potentially have different levels of support. It should be noted that each RAN node can be split into different nodes. For example, a gNB in ​​a split RAN architecture may consist of a gNB-Central Unit (CU) User Plane (UP), a gNB-CU Control Plane (CP), and a gNB-Distributed Unit (DU). In procedures such as handover, each of these split RAN nodes is responsible for a function, and failure to support one of them can lead to the failure of the handover procedure. An example of such an architecture is shown in Figure 1, which illustrates mobility involving core network nodes.

[0018] Therefore, the problem is how to ensure that different nodes involved in supporting the functionality and signaling related to a particular function can recognize that the functionality and signaling are fully supported by all the nodes involved. , the Started by the first RAN node, which is serviced by the first CN node. Re, The second RAN node, which is serviced by the second CN node, is involved. Perform (or execute) the procedure and / or functionThis could result in failures and / or uncertain consequences, such as whether it is appropriate / possible for the first RAN node to attempt the same procedures and / or functions to the second RAN node in the future. The first RAN node retains no knowledge of the support for procedures and / or functions in either the second RAN node and / or the first CN node and / or the second CN node. There is no mechanism to support the first RAN node in avoiding repeatedly re-executing the same procedures and / or functions in the future, leading to more failures and / or undefined behavior. If functionality and signaling are not supported, the impact will be apparent in the path between the first and second RAN nodes, resulting in wasted signaling, including CN signaling between the first CN node serving the first RAN node and the second CN node serving the second RAN node.

[0019] In a specific example of a handover via a CN, the source RAN cannot determine whether all the functionalities related to the CN-based handover (HO) procedure are supported in the target RAN or target AMF.

[0020] Similarly, a source RAN node has no knowledge of the target CN node's or target RAN node's support for a function that uses a specific IE signaled to modify a session context already established between the source and the target.

[0021] The object of the embodiments of this disclosure is to improve the efficiency of wireless communication networks. [Means for solving the problem]

[0022] According to one embodiment, this objective is achieved by a method performed by a first radio access network (RAN) node. The method is for processing information elements (IEs) supported in relation to a procedure involving multiple network nodes to a second RAN node of a wireless communication system.

[0023] The first RAN node transmits a first indication to the second RAN node. The first indication indicates whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure.

[0024] The first RAN node receives a response including a second indication from the second RAN node. The second indication indicates whether one or more second IEs that are part of the procedure are supported by the second RAN node during the procedure.

[0025] According to one aspect, the objective is achieved by a method executed by a second radio access network (RAN) node. The method is for processing information elements (IEs) supported regarding a procedure involving a plurality of network nodes from a first RAN node to a second RAN node in a wireless communication system.

[0026] The second RAN node receives the first indication from the first RAN node. The first indication indicates whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure.

[0027] The second RAN node transmits a response including the second indication to the first RAN node. The second indication indicates whether one or more second IEs that are part of the procedure are supported by the second RAN node during the procedure.

[0028] According to one aspect, the objective is achieved by a method executed by a first core network (CN) node. The method is for processing information elements (IEs) supported regarding a procedure involving a plurality of network nodes from a first radio access network (RAN) node to a second RAN node in a wireless communication system. The first CN node provides services to the first RAN node.

[0029] The first CN node receives a first indication sent from the first RAN node to the second RAN node. The first indication indicates whether one or more first IEs, which are part of the procedure, are supported by the first RAN node during the procedure.

[0030] The first CN node filters out one or more first IEs included in the first indication based on whether one or more first IEs are supported by the first CN node.

[0031] The first CN node sends a filtered first indication to the second RAN node. The filtered first indication indicates whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node and the first CN node during the procedure.

[0032] According to one embodiment, the objective is achieved by a method performed by a second core network (CN) node. The method is for processing information elements (IE) supported in relation to a procedure involving multiple network nodes from a first radio access network (RAN) node to a second RAN node of a wireless communication system. The second CN node provides services to the second RAN node.

[0033] The second CN node receives a first filtered first indication sent from the first RAN node to the second RAN node via the first CN node that provides services to the first RAN node. The first filtered first indication indicates whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node and the first CN node during the procedure.

[0034] The second CN node further filters one or more first IEs included in the received first filtered first indication, based on whether one or more first IEs are supported by the second CN node.

[0035] The second CN node sends the first indication, further filtered by the second CN node, to the second RAN node, which indicates whether one or more first IEs are supported during the procedure by the first RAN node, the first CN node, and the second CN node.

[0036] In another embodiment, the objective is achieved by a first radio access network (RAN) node. The first RAN node is configured to process information elements (IEs) that are supported with respect to a procedure involving multiple network nodes to a second RAN node of a wireless communication system. The first RAN node further transmits a first indication to the second RAN node, which is adapted to indicate whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure, and the second RAN node indicates whether one or more second IEs that are part of the procedure are supported by the second RAN node during the procedure. show It is configured to receive a response that includes a second indication that is adapted to the system.

[0037] In another embodiment, the objective is achieved by a second radio access network (RAN) node. The second RAN node is configured to process information elements (IEs) that are supported in relation to a procedure involving multiple network nodes from a first RAN node to the second RAN node of a radio communication system. The second RAN node is further configured to receive a first indication from the first RAN node, adapted to indicate whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure, and to transmit a response to the first RAN node, which includes a second indication adapted to indicate whether one or more second IEs that are part of the procedure are supported by the second RAN node during the procedure.

[0038] In another embodiment, the objective is achieved by a first core network (CN) node. The first CN node is configured to process information elements (IEs) that are supported in relation to a procedure involving multiple network nodes from a first radio access network (RAN) node to a second RAN node of a wireless communication system. The first CN node provides services to the first RAN node. The first CN node is further configured to receive a first indication transmitted from the first RAN node to the second RAN node, which is adapted to indicate whether one or more first IEs that are part of the procedure are supported by the first RAN node during the procedure; to filter one or more first IEs contained in the first indication based on whether one or more first IEs are supported by the first CN node; and to transmit the filtered first indication to the second RAN node, which is adapted to indicate whether one or more first IEs that are part of the procedure are supported by both the first RAN node and the first CN node during the procedure.

[0039] In another embodiment, the objective is achieved by a second core network (CN) node. The second CN node is configured to process information elements (IEs) that are supported in relation to a procedure involving multiple network nodes from a first radio access network (RAN) node to a second RAN node of a wireless communication system. The second CN node provides services to the second RAN node. The second CN node further receives a first filtered indication transmitted from the first RAN node to the second RAN node via the first CN node providing services to the first RAN node, wherein the first filtered indication is adapted to indicate whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node and the first CN node during the procedure, and one or more first IEs included in the received first filtered indication are supported by the second CN node. mosquitoThe system is configured to further filter based on the above, and to send to the second RAN node a first indication that has been further filtered by the second CN node, indicating whether one or more first IEs are supported by the first RAN node, the first CN node, and the second CN node during the procedure.

[0040] The advantages of this embodiment are, for example, 3 The objective is to enable knowledge of protocol support in all relevant logical network nodes and network functions, including RAN nodes, such as gNB-CU-CP, gNB-CU-UP, gNB-DU, and CN nodes, deployed in a split architecture, for any procedure and function involving more than one logical network node and / or network function.

[0041] A further advantage of this embodiment is that, for example, it avoids the need to introduce a per-function "support" indicator on the network interface, which would otherwise lead to explicitly indicating the status of supported functionality on the nodes involved in the procedure. [Brief explanation of the drawing]

[0042] [Figure 1] A diagram illustrating the background technology. [Figure 2] A block diagram showing an embodiment of a wireless communication system. [Figure 3] A flowchart of an embodiment of the method performed by the first RAN node. [Figure 4] A flowchart of an embodiment of the method performed by the second RAN node. [Figure 5] A flowchart illustrating an embodiment of the method performed by the first CN node. [Figure 6] A flowchart illustrating an embodiment of the method performed by the second CN node. [Figure 7]A block diagram showing an embodiment of a wireless communication system. [Figure 8] A sequence diagram illustrating an embodiment of the method. [Figure 9a] A block diagram illustrating an embodiment of the method executed by the first RAN node. [Figure 9b] A block diagram illustrating an embodiment of the method executed by the first RAN node. [Figure 10a] A block diagram illustrating an embodiment of the method performed by the second RAN node. [Figure 10b] A block diagram illustrating an embodiment of the method performed by the second RAN node. [Figure 11a] A block diagram illustrating an embodiment of the method performed by the first CN node. [Figure 11b] A block diagram illustrating an embodiment of the method performed by the first CN node. [Figure 12a] A block diagram illustrating an embodiment of the method performed by the second CN node. [Figure 12b] A block diagram illustrating an embodiment of the method performed by the second CN node. [Figure 13] A diagram showing a communication network connected to a host computer via an intermediate network. [Figure 14] A generalized block diagram of a host computer communicating with user equipment via a partial wireless connection through a base station. [Figure 15] A flowchart illustrating how to perform the operation in a communication system including a host computer, base station, and user equipment. [Figure 16] A flowchart illustrating how to perform the operation in a communication system including a host computer, base station, and user equipment. [Figure 17] A flowchart illustrating how to perform the operation in a communication system including a host computer, base station, and user equipment. [Figure 18] A flowchart illustrating how to perform the operation in a communication system including a host computer, base station, and user equipment. [Modes for carrying out the invention]

[0043] This embodiment provides a method and node configuration mechanism for exchanging indications, also called supported IE-Id information, for a predetermined procedure, during which the peer node understands the IE-Ids from different systems, and optionally, for indications of the capabilities of the nodes that support the functionality, during a predetermined procedure, such as the HO resource allocation procedure. This mechanism according to this embodiment can be generalized for inter-system mobility, including via NGAP, S1AP, and F1AP. The mechanism according to this embodiment does not necessarily depend on the criticality assigned to a particular IE, however the peer-RAN node should consider the support of serving CN nodes that generally depend on the assigned criticality.

[0044] Indications can also be referenced as data. For example, IE is represented by IE-ID.

[0045] Figure 2 shows a schematic of a wireless communication network 100 in which an embodiment may be implemented. The wireless communication network 100 has one or more RANs and one or more CNs. The wireless communication network 100 may use 5G NR, but several other different technologies, some possible implementations to mention, may further use WiFi, LTE, LTE Advanced, Wideband Code Division Multiple Access (WCDMA®), Global System for Mobile Communications / Enhanced Data Rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB).

[0046] RAN nodes such as the first RAN node 111 and the second RAN node 112 operate in the wireless communication network 100. The first RAN node 111 and / or the second RAN node 112 may each be an access point (AP), for example, providing multiple cells and using these cells for communication with a UE, for example, UE 120. The first RAN node 111 and / or the second RAN node 112 may each be a radio access network node such as a transmit point and a receive point, for example a base station, for example Node B, evolved Node B (eNB, eNodeB, eNodeB), NR Node B (gNB), base transceiver station, radio remote unit, access point base station, base station router, radio base station transmit configuration, standalone access point, wireless local area network (WLAN) access point, access point station (APSTA), access controller, UE functioning as an access point or peer in device-to-device (D2D) communication, or any other network unit. The first RAN node 111 and / or the second RAN node 112 can communicate with each other, for example, via one or more CN nodes in the wireless communication network 100.

[0047] It should be noted that the first RAN node 111 and / or the second RAN node 112 may be split into different nodes, for example. For example, RAN nodes 111 and 112 such as gNB in ​​a split RAN architecture may comprise gNB-CU-UP, gNB-CU-CP, and gNB-DU.

[0048] User devices such as UE120 operate within the wireless communication network 100. UE120 may be, for example, an NR device, mobile station, wireless terminal, NB-IoT device, eMTC device, NR RedCap device, CAT-M device, Wi-Fi device, LTE device, and non-access point (non-AP) STA, STA, communicating via base stations such as the first RAN node 111 and / or the second RAN node 112. UEs may include, for example, smartphones, laptops, mobile phones, sensors, repeaters, mobile tablets, and small base stations communicating within a cell. terminal, This is a non-restrictive term that refers to any UE, such as a wireless communication terminal, user device, D2D terminal, or node.

[0049] CN nodes such as the first CN node 131 and / or the second CN node 132 operate within the wireless communication network 100. CN nodes may be, for example, AMF nodes, MME nodes, or SMF nodes. Each of the first CN node 131 and / or the second CN node 132 can transfer messages and / or signals from or to either one or both of the first RAN node 111 and the second RAN node 112.

[0050] This method may be performed by one or more of the first RAN node 111, the second RAN node 112, the first CN node 131, and the second CN node 132. Alternatively, for example, distributed nodes (DNs) and functions included in Cloud 140, as shown in Figure 2, may be used to perform or partially perform the method of this embodiment.

[0051] This embodiment may relate to capability exchange between RAN nodes 111 and 112, for example, a CN-based handover.

[0052] Procedures involving multiple network nodes to the second RAN node 112 can be performed, for example, via the first CN node 131 and the second CN node 132. In some embodiments, for example, in relation to Solution 2, and also referring to Figure 8 later, when the first indication is sent toward the second RAN node 112, it first passes through the first CN node 131, where it is filtered so that the supported IEs include IEs supported by both the first RAN node 111 and the first CN node 131. The filtered first indication is then forwarded to the second CN node 132, passing through the second CN node, where it is filtered again so that the supported IEs include IEs supported by all of the first RAN node 111, the first CN node 131, and the second CN node 132, before forwarding the filtered first indication to the second RAN node 112. In this way, the further filtered first indication teaches the IEs supported by all nodes involved in the procedure, and optionally, the functions associated with each supported IE.

[0053] Filtering means, for example, removing IEs that are not supported by each filtering node from the first indication before forwarding them to the next node.

[0054] Next, embodiments of the method will be described one by one from different views of various related nodes, including the first RAN node 111 associated with Figure 3, the second RAN node 112 associated with Figure 4, the first CN node 131 associated with Figure 5, and the second CN node 132 associated with Figure 6.

[0055] Figure 3 shows an example of a method performed by the first RAN node 111. The method is for processing supported IEs, such as supported IE identifiers (IDs), in relation to a procedure involving multiple network nodes to the second RAN node 112 of the wireless communication system 100. This procedure may be related to, for example, an HO resource allocation procedure. A procedure involving multiple network nodes to the second RAN node 112 is also referred to as involving, or being performed through, a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112. The method includes any one or more of the actions listed below.

[0056] Action 301 The first RAN node 111 transmits the first indication to the second RAN node. The first indication may be transmitted from the first RAN node 111 to the second RAN node 112 via the first CN node 131 and the second CN node 132.

[0057] The first indication indicates whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure. This is advantageous because the first RAN node 111 can request whether either the second RAN node 112 or one of the CN nodes along the signaling path between the first RAN node 111 and the second RAN node 112 supports or does not support one or more first IEs.

[0058] In some embodiments, the first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure. The second RAN node 112 and the signaling path between the first RAN node 111 and the second RAN node 112 Ta CThis is an advantage because the first RAN node 111 can request whether any one of the N nodes supports or does not support one or more functions associated with one or more first IEs.

[0059] In some embodiments, the first indication sent to the second RAN node 112 is filtered and received by the second RAN node 112 based on one or more of the following: - Whether one or more first IEs are supported during the procedure by one or more intermediate nodes, such as a first CN node 131 providing services to a first RAN node 111, and a second CN node 132 providing services to a second RAN node, and / or - Whether one or more functions associated with each of the one or more first IEs are supported during the procedure by one or more intermediate nodes, such as the first CN node 131 providing services to the first RAN node 111, and the second CN node 132 providing services to the second RAN node.

[0060] Action 302 The first RAN node 111 receives a response from the second RAN node, which is a response to the first indication sent toward the second RAN node 112. The response includes a second indication, which indicates whether one or more second IEs, which are part of the procedure, are supported by the second RAN node 112 during the procedure, and further, whether they are supported by one or more of the first CN node 131, which provides services to the first RAN node 111 during the procedure, and the second CN node 132, which provides services to the second RAN node 112. This is advantageous because the first RAN node 111 obtains information about whether the second RAN node 112 and the CN nodes along the signaling path between the first RAN node 111 and the second RAN node 112 support or do not support one or more first IEs.

[0061] In some embodiments, the second indication further indicates whether one or more second functions associated with each of the one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and further whether they are supported by one or more of, for example, the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure.

[0062] In some embodiments, one or more second IEs are selected from one or more first IEs.

[0063] In some embodiments, one or more second functions are selected from one or more first functions.

[0064] In this way, the first RAN node 111 obtains information regarding whether the CN nodes along the signaling path between the second RAN node 112 and the first RAN node 111 and the second RAN node 112 support or do not support one or more first IEs, and / or whether the CN nodes along the signaling path between the second RAN node 112 and the first RAN node 111 and the second RAN node 112 support or do not support one or more first functions associated with one or more first IEs.

[0065] Figure 4 shows an example of a method performed by the second RAN node 112 to process supported IEs in a wireless communication system 100, for example, a procedure involving multiple network nodes from a first RAN node 111 to a second RAN node 112, for example, via a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112. The method includes any one or more of the actions listed below.

[0066] Action 401 The second RAN node 112 receives a first indication from the first RAN node 111. The first indication indicates whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure.

[0067] In some embodiments, the first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure.

[0068] In some embodiments, the first indication received from the first RAN node 112 is filtered and received based on one or more of the following: - Whether one or more first IEs are supported during the procedure by one or more intermediate nodes, such as a first CN node 131 providing services to a first RAN node 111, and a second CN node 132 providing services to a second RAN node, and / or - Whether one or more functions associated with each of the one or more first IEs are supported during the procedure by one or more intermediate nodes, such as the first CN node 131 providing services to the first RAN node 111, and the second CN node 132 providing services to the second RAN node.

[0069] As described above, in some embodiments, when a first indication is transmitted toward the second RAN node 112, it first passes through the first CN node 131, where it is filtered so that the supported IEs include IEs supported by both the first RAN node 111 and the first CN node 131. The filtered first indication is then forwarded to the second CN node 132, where it passes through the second CN node, where it is filtered so that the supported IEs include IEs supported by all of the first RAN node 111, the first CN node 131, and the second CN node 132, before forwarding the further filtered first indication to the second RAN node 112.

[0070] Action 402 The second RAN node 112 sends a response to the first RAN node 111 that includes a second indication. This is a response to the first indication received from the first RAN node 111. The second indication indicates whether one or more second IEs, which are part of the procedure, are supported by the second RAN node 112 during the procedure, and whether they are further supported by one or more of the first CN node 131, which provides services to the first RAN node 111, and the second CN node 132, which provides services to the second RAN node 112 during the procedure.

[0071] In some embodiments, the second indication further indicates whether one or more second functions associated with each of the one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and further whether they are further supported by one or more of, for example, the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure.

[0072] In some embodiments, one or more second IEs are selected from one or more first IEs.

[0073] In some embodiments, one or more second functions are selected from one or more first functions.

[0074] In this way, the second RAN node 112 has one or more first IEs and / or one or more first functions associated with one or more first IEs. but The first RAN node 111 is notified whether it is supported by the second RAN node 112, by the first CN node 131 which provides services to the first RAN node 111, and by the second CN node 132 which provides services to the second RAN node 112.

[0075] Figure 5 shows an example of how the first CN node 131 performs a supported IE in the wireless communication system 100, relating to a procedure involving multiple network nodes from the first RAN node 111 to the second RAN node 112, for example, via the first CN node 131 and the second CN node 132. The first CN node 131 provides services to the first RAN node 111.

[0076] As described above, in some embodiments, when a first indication is sent toward the second RAN node 112, it first passes through the first CN node 131, where it is filtered so that the supported IEs include IEs supported by both the first RAN node 111 and the first CN node 131. The filtered first indication is then forwarded to the second CN node 132, where it is further filtered before being forwarded to the second RAN node 112.

[0077] The method includes any one or more of the actions listed below.

[0078] Action 501 The first CN node 131 receives a first indication sent from the first RAN node 111 to the second RAN node 112. The first indication indicates whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure.

[0079] In some embodiments, the first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure.

[0080] Action 502 The first CN node 131 filters out one or more first IEs included in the first indication based on whether one or more first IEs are supported by the first CN node 131.

[0081] In some embodiments, the first CN node 131 filters out one or more first functions to be included in the first indication based on whether one or more first functions are supported by the first CN node 131.

[0082] Action 503 The first CN node 131 sends a filtered first indication to the second RAN node 112. The filtered first indication indicates whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node 111 and the first CN node 131 during the procedure.

[0083] In some embodiments, the filtered first indication indicates whether one or more first functions associated with each of the one or more first IEs are supported by both the first RAN node 111 and the first CN node 131 during the procedure.

[0084] In this way, when a response arrives at the first RAN node, the first CN node 131 can provide the first RAN node with information indicating whether the first CN node supports or does not support one or more first IEs and / or one or more first functions associated with each of the one or more first IEs.

[0085] Figure 6 shows an example of how the second CN node 132 performs a procedure in the wireless communication system 100 to process supported IEs, relating to a procedure involving multiple network nodes, for example, from a first RAN node 111 to a second RAN node 112, for example, via a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112. The second CN node 132 provides services to the second RAN node 112.

[0086] As described above, in some embodiments, when a first indication is sent toward the second RAN node 112, it first passes through the first CN node 131, where it is filtered so that the supported IEs include IEs supported by both the first RAN node 111 and the first CN node 131. The filtered first indication is then forwarded to the second CN node 132, where it is further filtered before being forwarded to the second RAN node 112.

[0087] The method includes any one or more of the actions listed below.

[0088] Action 601 The second CN node 132 receives a first filtered first indication from the first RAN node 111 to the second RAN node 112, transmitted from the first RAN node 111 to the second RAN node 112 via the first CN node 131, which provides services to the first RAN node 111. The first filtered first indication indicates whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node 111 and the first CN node 131 during the procedure.

[0089] In some embodiments, the first filtered first indication indicates whether one or more first functions associated with each of the one or more first IEs are supported by both the first RAN node 111 and the first CN node 131 during the procedure.

[0090] Action 602 The second CN node 132 further filters one or more first IEs included in the received first filtered first indication based on whether one or more first IEs are supported by the second CN node 132.

[0091] In some embodiments, the second CN node 132 is further one or more first function Based on whether it is supported by the second CN node 132, filter one or more first IEs included in the received first filtered first indication.

[0092] Action 603 The second CN node 132 sends a further filtered first indication to the second RAN node 112. The first indication, further filtered by the second CN node 132, indicates whether one or more first IEs are supported by the first RAN node 111, the first CN node 131, and the second CN node 132 during the procedure.

[0093] In some embodiments, a further filtered first indication sent toward the second RAN node 112 indicates whether one or more first functions associated with each of the one or more first IEs are supported by the first RAN node 112, the first CN node 131, and the second CN node 132 during the procedure.

[0094] In this way, when a response arrives at the first RAN node, the second CN node 132 can provide the first RAN node with information indicating whether or not the second CN node 132 supports one or more first IEs and / or one or more first functions associated with each of the one or more first IEs.

[0095] Thus, the method described above, as a whole, 3 For any procedure and function involving one or more logical network nodes and / or network functions, it becomes possible to obtain knowledge of the protocol support in all relevant logical network nodes and network functions, RAN nodes such as the first RAN node 111 and the second RAN node 112, functions of RAN nodes deployed in a split architecture, such as gNB-CU-CP, gNB-CU-UP, gNB-DU, and CN nodes such as the first CN node 131 and the second CN node 132.

[0096] For example, RAN nodes such as the first RAN node 111 and / or the second RAN node 112 are 3 It is possible to derive whether a particular procedure or function, including more than one logical node and / or network function, is available, or whether such a procedure or function is fully available or partially available.

[0097] The method described above also avoids introducing feature-specific "support" indicators on the network interface, which would otherwise lead to explicitly indicating the status of supported features in the network nodes or network functions included in the procedure.

[0098] Next, the method will be further described and illustrated by the following embodiments. The embodiments can be combined in any preferred manner.

[0099] Examples of embodiments of the methods described herein are based on signaling, for example, in a list, one or more supported IEs, as part of a procedure involving multiple network nodes. Each node involved in the procedure may signal, before or during the procedure, an indication, for example, showing the IEs that are applied to and supported by the procedure, in a list. Note that, in this specification, the expressions “one or more IEs” and “list of IEs” are used interchangeably. In some embodiments, an indication (also called information) regarding the support of each IE may be supplemented by identifying whether a feature associated with the IE is supported or not. In some other embodiments, a support or non-support indication for one IE means that a feature for that IE is supported or not supported. In some other embodiments, a support or non-support indication for a certain IE means that only that IE is supported, and not necessarily that a feature associated with that IE is supported.

[0100] The method described above can be applied to multiple procedures involving multiple network nodes. However, regardless of the procedure, the method provides enriched signaling between nodes involved in a procedure, such as the first RAN node 111, the second RAN node 112, the first CN node 131, and the second CN node 132, with information that can be expressed in this exemplary form. The underlined text in the following table relates to embodiments described herein.

[0101] [Table 1]

[0102] Alternatively, there are alternative approaches such as the following (these alternatives are shown in the examples below, but are applicable to any use case, so they are reported here):

[0103] [Table 2]

[0104] In some embodiments, the one or more supported IEs described above, for example, the list of supported IEs, may be supplemented in the following ways.

[0105] The addition of the "Supported Functionality" indicator allows us to indicate, for example, whether Internet Explorer (IE) is supported but related functionalities are not. This is useful when a feature has not been developed or implemented on a particular node, but the access point (AP) message encoding has been updated to support IE.

[0106] In some other embodiments, the IE support indicator may be in the form of a bitmap, where the value "1" indicates "IE is supported" and the value "0" indicates "IE is not supported".

[0107] In some embodiments, "all" IE support indicators (e.g., all in a release) Features All IEs are shown. In other variations, the IE support indication is specific. Features All IEs, or specific Features This shows a specific IE. In this case, the node can show a structure consisting of a list, where each item in the list is Features And that Features It consists of IE indications that are supported for [the specified target]. In other words, the information shown above can be changed as follows:

[0108] [Table 3]

[0109] In some embodiments, the absence of a response indication from the target node, such as an IE-Id list, may be interpreted by a source node, such as the first RAN node 111, as indicating that this node is a legacy node that does not support the corresponding feature or function.

[0110] Below are some examples of how this method can be applied to specific procedures.

[0111] Several first embodiments referred to as Solution 1 In some common embodiments, for example, an indication of whether one or more IEs are supported as part of a procedure, such as a list of supported IE-Id information, is included in a source-to-target transparent container sent from a first RAN node, which is a source RAN node also called the source node in this example, to a second RAN node, which is a target RAN node also called the target node in this example, during an HO procedure performed via CNs such as a first CN node 131 and a second CN node 132. The target node then returns a list of its supported IE-Ids in a target-to-source transparent container, which is, for example, an IE signaled from the target RAN to the source RAN.

[0112] In one specific embodiment, a list of supported IE-IDs, defined in the application protocol used for the source-side RAN-CN interface, for example, S1AP (TS36.413) for EPS and NGAP (TS38.413 v17.0.0) for 5GS, is provided to the target RAN node by the start message of a handover resource allocation procedure, such as a HANDOVER REQUIRED start message, for example, a transparent container IE from an existing source NG-RAN to a target NG-RAN, and the start message of a handover resource allocation procedure, such as a transparent container from an existing source NG-RAN to a target NG-RAN. The target RAN node replies by sending a source NG-RAN transparent container from the target NG-RAN consisting of a list of IE-IDs related to the supported functions.

[0113] Figure 7 shows an example scenario illustrating transparent containers from source to target and from target to source. The first RAN node 111 is called source RAN111, the second RAN node 112 is called target RAN112, the first CN node 131 is called source CN131, and the second CN node 132 is called target CN132.

[0114] Whether or not a support indicator needs to be implemented Features Instead of discussing each case individually, the embodiments described herein are generalized by specifying the exchange of the Support IE ID for the HO resource allocation procedure.

[0115] The embodiments described herein can be implemented between NGAP and S1AP, and even between systems.

[0116] The embodiments described herein are applicable, for example, only to handover resource allocation procedures.

[0117] The embodiments described herein may, for example, be intended for only a limited number of IEs and may not be intended to replace an entire set of IEs.

[0118] The embodiments of this specification do not necessarily depend on the criticality assigned to a particular IE, however, peer-RAN nodes must consider their service CNs, such as the first CN node 131 and the second CN node 132.

[0119] In embodiments of this specification, for example, remote critical for an approach can be replaced or rather defined.

[0120] In some embodiments, the first RAN node 111 (the source RAN node in this example) may include an IE-Id only if the serving CN node 131 also supports IE-Ids. Each of these knowledge points to the criticality mechanism, OAM, or IE (or related). Features This can be obtained by the CN node including the respective IE in the message, by explicitly indicating that it is supported.

[0121] The second RAN node 112 (the target node in this example) also has a serving CN 132 node. Features If you gain the knowledge that it supports that Features It can respond if it is supported. Each piece of knowledge on the target side can be obtained on the source side as described above. If the target node has not yet obtained knowledge about CN side support, this information may be explicitly provided, for example, "Support Unknown". If the target RAN node does not support IE-Id, it must respond "Not Supported" in all cases.

[0122] In the case of an inter-system handover, the source RAN node can provide the IE-Id specified by the source RAN-CN interface to a list of supported IE-Ids and explicitly indicate the protocols supported by the source RAN-CN interface. Similarly, the target RAN node can provide the IE-Id specified by the target RAN-CN interface to a list of supported IE-Ids and explicitly indicate the protocols supported by the target RAN-CN interface, if a functional correspondence between IEs defined by RAN-CN interfaces specified for different systems is apparent or can be derived.

[0123] The list of IE-Ids does not need to be a comprehensive list of all supported IE-Ids; in most cases, it is a selective list. The target RAN node can only respond to IEs for which support information has been requested by the source RAN node.

[0124] Support information, specifically a list of IE-Ids, may be provided within the handover failure container if the target node is unable to successfully complete the handover resource allocation procedure.

[0125] When the source and target RAN configurations include multiple nodes (e.g., dual or multi-connectivity), the scope of information exchanged can span all involved RAN nodes, even if the control interface of the RAN-CN interface is defined only for a single RAN node (the current case of EPS and 5GS), as represented by the IE-Id. Features This may depend on the following: In some embodiments, each new IE support indicator replaces the previous one. In some other embodiments, in relation to an IE support update, only the difference to the previous indicator is sent.

[0126] In some embodiments, a node such as the first RAN node 111 or the second RAN node 112 indicates IE support only when polled. In some other embodiments, the first RAN node 111 may, in this example, actively indicate its IE support to the second RAN node 112, and in response, the second RAN node 112 also indicates its IE support to the first RAN node 111.

[0127] The following is a non-limiting example of how the underlined portion affects the specifications:

[0128] 3GPP TS38.413 Clause 9.3.1.29 Transparent container from source NG-RAN node to target NG-RAN node: This IE is generated by the source NG-RAN node (e.g., the first RAN node 111) and sent to the target NG-RAN node (e.g., the second RAN node 112). In the case of inter-system handover to 5G, the IE is sent from the external handover source to the target NG-RAN node.

[0129] This version of IE is transparent to 5GC.

[0130] [Table 4] [Table 5] [Table 6]

[0131] 3GPP TS38.413 Clause 9.3.1.30 Transparent container from target NG-RAN node to source NG-RAN node:

[0132] This IE is target NG-RAN node (for example, the 2 Generated by RAN node 112), sauce NG-RAN node (for example, the1 It is sent to RAN node 111). In the case of inter-system handover to 5G, the IE is sent from the target NG-RAN node to the external transfer source.

[0133] This version of IE is transparent to 5GC.

[0134] [Table 7] [Table 8]

[0135] In one embodiment, a list of supported IE-Id information is optionally signaled in the RAN status forwarding transparent container for intra5GC NG handover.

[0136] In a dependent embodiment, the above-mentioned list of supported IEs is supplemented in the following way:

[0137] [Table 9]

[0138] The addition of the "Supported Functionality" indicator allows us to indicate, for example, whether Internet Explorer (IE) is supported but related functionalities are not. This is useful when a feature has not been developed or implemented on a particular node, but the AP message encoding has been updated to support IE.

[0139] In some other embodiments, the IE support indicator may be in the form of a bitmap, where the value "1" indicates "IE is supported" and the value "0" indicates "IE is not supported".

[0140] In some embodiments, "all" IE support indicators (e.g., all in a release) Features All IEs are shown. In another modified example, the IE support indication is specific Features All IE or specific Features This refers to a specific IE. In this case, for example, nodes such as the first RAN node 111 and the second RAN node 112 can signal a structure consisting of a list, where each item in the list is Features And so on. Features It consists of supported IE indications. In other words, the information shown above can be changed as follows:

[0141] [Table 10]

[0142] Several second embodiments referred to as Solution 2 In these embodiments, a list of IE-Ids supported by each involved node, e.g., source / target RAN / CN nodes such as the first RAN node 111, the second RAN node 112, the first CN node 131, and the second CN node 132, is signaled by a dedicated signaling procedure, regardless of assigned criticality. That is, to collect such information, for example, a RAN configuration transfer procedure(s) is used within a single round trip between the source and target RAN nodes, and this information must be available to all involved RAN / CN nodes. Indication of supported / unsupported IEs may be achieved as in Solution 1, i.e., the various methods described above for representing IE support and their functionality may be reused in these embodiments.

[0143] In one dependent embodiment, an IE support indication during a round trip traverses the involved RAN and CN nodes, such as the first RAN node 111, the second RAN node 112, the first CN node 131, and the second CN node 132, as shown in Figure 8, with each node indicating, for example, by setting a flag or by listing or indicating IEs accordingly, such as an IE ID in the message, as illustrated. In this example, the first RAN node 111 is called RAN node 111, the second RAN node 112 is called RAN node 2112, the first CN node 131 is called CN node 111, and the second CN node 132 is called CN node 2132. For example, node X, such as the first RAN node 111, lists IE ID=5 (meaning it supports IE) and forwards the IE support indication to the next node in the chain, such as node Y, such as the first CN node 131. If node Y does not support IE, node Y removes IE ID=5 from the list (also known as filtering).

[0144] In some other embodiments, the IE support indication may be in the form of a bitmap, where a value of "1" indicates "IE is supported" and a value of "0" indicates "IE is not supported". In the context of Solution 2, as shown in Figure 8, during a round trip of the IE indication across RAN nodes and CN nodes such as the first RAN node 111, the second RAN node 112, the first CN node 131, and the second CN node 132, each node sets a bit in the bitmap corresponding to IE support to "0" or "1" depending on whether it supports IE. In the example in Figure 8, an existing UL / DL RAN configuration transfer is a specific Features It is used to transmit IE related to this.

[0145] The following is a non-limiting example of how the underlined portion affects the specifications:

[0146] Section 9.2.7.1 of 3GPP TS38.413 describes uplink RAN ​​configuration transfers. This message is sent by an NG-RAN node (e.g., the first RAN node 111) to transfer RAN configuration information. Direction: NG-RAN node → AMF (e.g., 1st CN node 131)

[0147] [Table 11] [Table 12]

[0148] Section 9.2.7.2 of 3GPP TS38.413: Downlink RAN ​​Configuration Transfer This message is sent by the AMF (e.g., the first CN node 131) to transfer RAN configuration information. Direction: AMF → NG-RAN node (e.g., 1st RAN node 111)

[0149] [Table 13] [Table 14]

[0150] In some embodiments, "all" IE support indicators (e.g., all in a release) Features All IEs are shown. In another modified example, the IE support indication is specific Features All IE or specific Features This refers to a specific version of Internet Explorer.

[0151] Several variations of the first embodiment, referred to as Solution 1-a For specific functions, such as those related to a self-organizing network (SON), two (or more) RAN nodes may be involved, with the first RAN node 111, in this example the first (source) RAN node, being part of the first radio communication system and / or the first RAT, and the second RAN node 112, in this example the second (target) RAN node, being related to the second radio communication system (and / or the second RAT). The function is fully (or partially) utilized if both the source and target RAN nodes, and potentially the CN nodes between them (e.g., the first CN node 131 and the second CN node 132, etc.), fully (or partially) support the function in question. As part of the function's operation, the source RAN node, in this example, is transparently propagated from the first RAN node to the second RAN node, and a list of optionally supported IEs is provided. The first indication The data is sent to the target RAN. The second RAN node, in this example, replies with a list of IE-Ids related to the features it supports, as a second indication. -In one example, the function may be related to energy saving, and the first RAN node 111 is an eNB (connected to the EPC) and the second RAN node 112 is a gNB (connected to the 5GC). The first RAN node 111 can request and / or propose to the second RAN node 112 to switch off one or more cells, or one or more SSB beams. For example, a first indication showing a list of option IEs corresponding to a request and / or proposal to turn off a particular cell and / or SSB beam is included in the transparent container. The method used to process the list of supported IE-Ids when the list of supported IE-Ids is signaled from the first RAN node 111 to the second RAN node 112 and back may be the same as described in Solution 1 or Solution 2. For example, as described in Solution 1, the transparent container sent from the first RAN node 111 to the second RAN node 112 (or vice versa) may be an extension of the inter-system SON configuration transfer type IE, or an extension of the EN-DC SON configuration transfer SON configuration transfer IE.

[0152] In another scenario, related to a specific function, for example, a self-organizing network (SON), two RAN nodes are involved, both belonging to the same wireless communication system or the same RAT, and the function uses an indirect signaling connection between the RAN nodes. Both the first RAN node 111 (the source RAN node in this example) and the second RAN node 112 (the target RAN node in this example), and potentially in between The CN nodes (for example, the first CN node 131 and the second CN node 132, etc.) fully support (or partially support) the function in question. and The functionality is fully utilized (or partially utilized). As part of the functionality's operation, the source RAN node sends a first indication (in this example, a list of optionally supported IEs) to the target RAN, which is transparently transmitted from the first RAN node to the second RAN node. 2R The AN node returns a list of IE-Ids related to the second indication, in this example, the features to be supported. -In one example, the function may be related to energy saving, and the first RAN node 111, in this example the first (source) NG-RAN node, requests or proposes to the second RAN node 112, in this example the second (target) NG-RAN node, to switch one or more cells or SSB beams of the second NG-RAN node on or off, and the Xn link between the RAN nodes is not defined, unavailable, or temporarily unavailable. Indications such as a list of optional IEs corresponding to the request / proposal to switch a specific cell(s) or SSB beam(s) on or off can be included in a transparent container. The method used to process the list of supported IE-Ids when the list of supported IE-Ids is signaled from the first RAN node 111 to the second RAN node 112 and back may be the same as described in Solution 1 or Solution 2. For example, as described in Solution 1, the transparent container sent from the first RAN node 111 to the second RAN node 112 may be an extension of a transparent container IE from source to target or a SON configuration transfer IE, and the transparent container sent from the second RAN node 112 to the first RAN node 111 may be an extension of a transparent container IE from target to source.

[0153] In another example, a feature might relate to cell resource coordination between nodes, where the first RAN node 111 is a gNB and the second RAN node 112 is an ng-eNB (or vice versa), and the Xn link between the RAN nodes is either undefined, unavailable, or temporarily unavailable. In one embodiment, an IE support indication is shown for "all" IEs (e.g., all IEs for all features in a release). In another embodiment, an IE support indication refers to all IEs for a particular feature or a specific IE for a particular feature.

[0154] Several third embodiments referred to as Solution 3 - Method applicable in the case of multiple receivers The methods of the embodiments described herein can be applied to the following scenarios: - The first RAN node 111, in this example the first (source) network node (or network function), sends the same type (or different types) of requests to two (or more) second RAN nodes 112, in this example two or more target RAN nodes (or network functions), and the requests(s) may traverse other network nodes in between, such as CN nodes like the first CN node 131 and the second CN node 132. The requests(s) may consist of IE-Ids associated with support for a particular function, and the IE-Ids are signaled in one of the forms described in other embodiments. Retoku(For example, a list of IE-Ids, the same list, separate lists, or partially overlapping lists are sent to all targets.) The target network node (or function) replies to the first network node. The first network node infers full or partial support of the function based on the reply. Failure of a reply from the second network node (or second network function) to the first network node (or first network function) (for example, due to a timer expiring) may be used by the first network node (or first network function) as an explicit or implicit indication that the function is not supported at the second network node (or second network function). The request consists of an IE-Id associated with support for a particular function, and the IE-Id may be signaled in one of the forms described in other embodiments. Based on the received request and the received IE-Id, the second network node sends a second request to the third network node (which may include a portion of the first request, for example, forwarding the received IE-Id potentially "filtered" based on the second network node's support for that function). Based on the received request and IE-Id, the third network node sends a final response (which may include parts of the first and second requests, e.g., the received IE-Id potentially "filtered" based on the support for the function at both the second and third network nodes) as a second indication to the first network node. The first network node infers full or partial support for the function based on the response. Failure or absence of a response (e.g., due to a timer expiring) can be used to explicitly or implicitly indicate a lack of support for the function.

[0155] Embodiments relating to gNB-DU NG base mobility As described above, the first RAN node 111 and the second RAN node 112 may be split RAN nodes. In previous embodiments, the focus was on indicating IE support for unsplit RAN nodes (i.e., gNBs) or CUs by using signaling for NG-based mobility of UEs. However, in Rel-18, NG-based mobility of DUs such as IAB-DUs and arbitrary mobile DUs is likely to be supported, making the indication of IE support between mobile DUs and target CUs important.

[0156] In one embodiment, DU mobility (vinegar PritRANNode Assuming In the case of ) and NG-based handovers, the IE support indication refers to IE support for the DU. In another embodiment, the IE support indication relates to both the source CU and the moving DU.

[0157] In one dependent embodiment relating to a mobile IAB (Integrated Access and Backhaul) node, IE support for the DU is indicated as part of the handover signaling for the IAB-MT (Integrated Access and Backhaul-Mobile Termination) coexisting with the DU. In another variation, a dedicated, extended existing signal or a newly defined signal is used, separate from the handover signal for the IAB-MT.

[0158] In one dependent embodiment, IE support related to IAB-DU is indicated separately (e.g., using a different dedicated message) for the IAB-DU of the first RAN node 111, in this example the mobile IAB node, and for the IAB-DUs of the descendants of the mobile IAB node. In another sub-variation, IE support is indicated together (e.g., using group signaling) for the IAB-DU of the mobile IAB node and its descendants.

[0159] In one dependent embodiment according to the above embodiment, the IE support indication of the first RAN node 111, in this example the mobile DU, uses a source-to-target container. In another modification, the IE support indication of the first RAN node 111, in this example the mobile DU, is explicitly transmitted via an interface, such as the NG, S1, AMF interface.

[0160] The embodiments presented in this chapter may use the encoding proposed in the previous chapter (i.e., IE ID), or they may use a different encoding.

[0161] The embodiments presented in this chapter may apply to mobile IAB-DUs or to mobile DUs (i.e., non-IAB DUs).

[0162] According to some embodiments of this specification, based on the functions supported on the target NG-RAN side associated with the NGAP IE based on each IE-Id, Features A new approach is introduced to obtain information regarding the support level for [the specified element]. In the following example, the target NG-RAN is represented by the second RAN node 112, and the source NG-RAN node is represented by the first RAN node 111.

[0163] These embodiments, based on the information provided within the CN transparent handover container, determine the specific functions supported on the target NG-RAN side, associated with the NGAP IE based on its respective IE-ID. Features This introduces the possibility of obtaining information such as the first and second indications regarding the support level.

[0164] In some embodiments, a new NGAP IE support information request list IE is introduced into a transparent container IE from the source NG-RAN node to the target NG-RAN node, where, for example, a second indication ("Supported" or "Not Supported")Accordingly, either the transparent container IE from the target NG-RAN node to the source NG-RAN node, or the transparent failure transparent container IE from the target NG-RAN node to the source NG-RAN node, includes a list of NGAP protocol IE-Ids for which the target NG-RAN node must provide supporting information. Furthermore, information is also provided regarding whether the reported IE was actually received by the target NG-RAN node within the HANDOVER REQUEST message.

[0165] If a HANDOVER REQUEST message contains an NGAP IE support information request list IE within a transparent container IE from the source NG-RAN node to the target NG-RAN node, the target NG-RAN node, if supported and if the target NG-RAN node accepts the handover request, will, for each NGAP protocol IE-Id contained within the transparent container IE from the target NG-RAN node to the source NG-RAN node in the HANDOVER REQUEST ACKNOWLEDGE message, for example according to a second indication, the receiving node of the HANDOVER REQUEST message. tough On the instance, - If the target NG-RAN node has information indicating that the IE-related functions shown are supported, set the NGAP protocol IE support information IE to "Supported". -If the target NG-RAN node has information that the IE-related functionality shown is not supported, set the NGAP protocol IE support information IE to "Not supported". - If the target NG-RAN node receives the respective NGAP protocol IE-Id in the HANDOVER REQUEST message, set the NGAP protocol IE existence information IE to "existent"; otherwise, set it to "not existed". " Set to this.

[0166] If the HANDOVER REQUEST message contains an NGAP IE support information request list IE within a transparent container IE from the source NG-RAN node to the target NG-RAN node, the target NG-RAN node will, if supported, and the target NG-RAN node will Ba If the request is not accepted, for each NGAP protocol IE-Id contained within the transparent failure container IE from the target NG-RAN node to the source NG-RAN node in the HANDOVER REQUEST FAILURE message, on the interface instance that received the HANDOVER REQUEST message, for example, according to the second indication, - If the target NG-RAN node has information indicating that the IE-related functions shown are supported, set the NGAP protocol IE support information IE to "Supported". - If the target NG-RAN node has information that the IE-related functions shown are not ported, set the NGAP protocol IE support information IE to "Not supported". - If the target NG-RAN node receives the respective NGAP protocol IE-Id in the HANDOVER REQUEST message, set the NGAP protocol IE existence information IE to "existent"; otherwise, set it to "not existed".

[0167] Figures 9a and 9b show an example configuration of the first RAN node 111.

[0168] The first RAN node 111 is configured to communicate with other networking entities in the wireless communication network 100, such as the second RAN node 112, the first CN node 131, and the second CN node 132, via input / output inputs. tough May include faces. Input / Output Input tough The face may include, for example, a wired and / or wireless receiver (not shown) and, for example, a wired and / or wireless transmitter (not shown).

[0169] The first RAN node 111 may consist of one or more acquisition units and reception units for performing method actions as described herein.

[0170] This embodiment can be implemented by a processor or one or more processors, such as at least one processor in the processing circuit of the first RAN node 111 shown in Figure 9a, and computer program code that performs the functions and actions of the embodiment herein. The program code may also be provided as a computer program product, for example, in the form of a data carrier that carries the computer program code that performs this embodiment when loaded into the first RAN node 111. One form of such carrier is a CD-ROM. However, other data carriers such as a memory stick are also possible. The computer program code is also provided as pure program code on a server and downloaded to the first RAN node 111.

[0171] The first RAN node 111 may further include memory, which includes one or more memory units. The memory includes instructions that can be executed by a processor within the first RAN node 111. The memory includes, for example, instructions for executing the method described herein when executed on the first RAN node 111. instruction, It is configured to store data, configurations, and applications.

[0172] In some embodiments, the computer program, when executed by at least one processor, includes instructions that cause at least one processor of the first RAN node 111 to perform the above action.

[0173] In some embodiments, each carrier has its own computer program, and the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0174] Those skilled in the art will also understand that the following functional modules within the first RAN node 111 may refer to one or more processors comprising a combination of analog and digital circuits and / or software and / or firmware, for example, the software and / or firmware stored in the first RAN node 111 and executed by the aforementioned at least one processor, causing each of the at least one processors to perform an action according to any of the above actions. One or more of these processors, and other digital hardware, may be contained in a single application-specific integrated circuit (ASIC), or they may be individually packaged or assembled into a system-on-a-chip (SoC), and multiple processors and various digital hardware may be distributed across various individual components.

[0175] Figures 10a and 10b show an example configuration of the second RAN node 112.

[0176] The second RAN node 112 is configured to communicate with other networking entities in the wireless communication network 100, such as the first RAN node 111, the first CN node 131, and the second CN node 132, via input / output inputs. tough May include faces. Input / Output Input tough The face may include, for example, a wired and / or wireless receiver (not shown) and, for example, a wired and / or wireless transmitter (not shown).

[0177] The second RAN node 112 may consist of one or more acquisition units and reception units for performing method actions as described herein.

[0178] This embodiment can be implemented by a processor or one or more processors, such as at least one processor in the processing circuit of the second RAN node 112 shown in Figure 10a, and computer program code that performs the functions and actions of the embodiment herein. The program code may also be provided as a computer program product, for example, in the form of a data carrier that carries the computer program code that performs this embodiment when loaded into the second RAN node 112. One form of such carrier is a CD-ROM. However, other data carriers such as a memory stick are also possible. The computer program code is also provided as pure program code on a server and downloaded to the second RAN node 112.

[0179] The second RAN node 112 may further include memory, which includes one or more memory units. The memory contains instructions that can be executed by a processor within the second RAN node 112. The memory contains, for example, instructions for executing the method described herein when executed on the second RAN node 112. instruction, It is configured to store data, configurations, and applications.

[0180] In some embodiments, the computer program, when executed by at least one processor, includes instructions that cause at least one processor in the second RAN node 112 to perform the above action.

[0181] In some embodiments, each carrier has its own computer program, and the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0182] Those skilled in the art will also understand that the following functional modules within the second RAN node 112 may refer to one or more processors comprising a combination of analog and digital circuits and / or software and / or firmware, for example, the software and / or firmware stored in the second RAN node 112 and executed by the aforementioned at least one processor, causing each of the at least one processors to perform an action according to any of the above actions. One or more of these processors, and other digital hardware, may be contained in a single application-specific integrated circuit (ASIC), or they may be individually packaged or assembled into a system-on-a-chip (SoC), and multiple processors and various digital hardware may be distributed across various individual components.

[0183] Figures 11a and 11b show an example configuration of the first CN node 131.

[0184] The first CN node 131 is configured to communicate with other networking entities in the wireless communication network 100, such as the first RAN node 111, the second RAN node 112, and the second CN node 132, via input / output inputs. tough May include faces. Input / Output Input tough The face may include, for example, a wired and / or wireless receiver (not shown) and, for example, a wired and / or wireless transmitter (not shown).

[0185] The first CN node 131 may consist of one or more of the acquisition unit, receiving unit, and filtering unit for performing the method actions described herein.

[0186] This embodiment can be implemented by a processor or one or more processors, such as at least one processor in the processing circuit of the first CN node 131 shown in Figure 11a, and computer program code that performs the functions and actions of the embodiment herein. The program code may also be provided as a computer program product, for example, in the form of a data carrier that carries the computer program code that performs this embodiment when loaded into the first CN node 131. One form of such carrier is a CD-ROM. However, other data carriers such as a memory stick are also possible. The computer program code is also provided as pure program code on a server and downloaded to the first CN node 131.

[0187] The first CN node 131 may further include memory comprising one or more memory units. The memory contains instructions executable by a processor within the first CN node 131. The memory contains, for example, instructions for executing the method described herein when executed on the first CN node 131. instruction, It is configured to store data, configurations, and applications.

[0188] In some embodiments, the computer program, when executed by at least one processor, includes instructions that cause at least one processor of the first CN node 131 to perform the above action.

[0189] In some embodiments, each carrier has its own computer program, and the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0190] Those skilled in the art will also understand that the following functional modules within the first CN node 131 may refer to one or more processors comprising a combination of analog and digital circuits and / or software and / or firmware, for example, the software and / or firmware stored in the first CN node 131 and executed by the aforementioned at least one processor, causing each of the at least one processors to perform an action according to any of the above actions. One or more of these processors, and other digital hardware, may be contained in a single application-specific integrated circuit (ASIC), or they may be individually packaged or assembled into a system-on-a-chip (SoC), and multiple processors and various digital hardware may be distributed across various individual components.

[0191] Figures 12a and 12b show an example configuration of the second CN node 132.

[0192] The second CN node 132 is configured to communicate with other networking entities in the wireless communication network 100, such as the first RAN node 111, the second RAN node 112, and the first CN node 131, via input / output inputs. tough May include faces. Input / Output Input tough The face may include, for example, a wired and / or wireless receiver (not shown) and, for example, a wired and / or wireless transmitter (not shown).

[0193] The second CN node 131 may consist of one or more of the acquisition unit, receiving unit, and filtering unit for performing the method actions described herein.

[0194] This embodiment can be implemented by a processor or one or more processors, such as at least one processor in the processing circuit of the second CN node 132 shown in Figure 12a, and computer program code that performs the functions and actions of the embodiment herein. The program code may also be provided as a computer program product, for example, in the form of a data carrier that carries the computer program code that performs this embodiment when loaded into the second CN node 132. One form of such carrier is a CD-ROM. However, other data carriers such as a memory stick are also possible. The computer program code is also provided as pure program code on a server and downloaded to the second CN node 132.

[0195] The second CN node 132 may further include memory, which includes one or more memory units. The memory includes instructions that can be executed by a processor within the second CN node 132. The memory includes, for example, instructions for executing the method described herein when executed on the second CN node 132. instruction, It is configured to store data, configurations, and applications.

[0196] In some embodiments, the computer program, when executed by at least one processor, includes instructions that cause at least one processor in the second CN node 132 to perform the above action.

[0197] In some embodiments, each carrier has its own computer program, and the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0198] Those skilled in the art will also understand that the following functional modules within the second CN node 132 may refer to one or more processors comprising a combination of analog and digital circuits and / or software and / or firmware, for example, the software and / or firmware stored in the second CN node 132 and executed by the aforementioned at least one processor, causing each of the at least one processors to perform an action according to any of the above actions. One or more of these processors, and other digital hardware, may be contained in a single application-specific integrated circuit (ASIC), or they may be individually packaged or assembled into a system-on-a-chip (SoC), and multiple processors and various digital hardware may be distributed across various individual components.

[0199] When the words "equip" or "include" are used, they shall be interpreted as non-restrictive, meaning "include at least one."

[0200] The embodiments described herein are not limited to the preferred embodiments described above. Various alternatives, modifications, and equivalents can be used.

[0201] Embodiment Several exemplary embodiments 1 to 32 are briefly described below. For example, please refer to Figures 2, 3, 4, 5, 6, 7, 8, 9a, 9b, 10a, 10b, 11a, 11b, 12a, and 12b.

[0202] Embodiment 1. A method performed by a first radio access network (RAN) node 111 to process information elements (IE) supported in relation to a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to a first RAN node 111 and a second CN node 132 providing services to the second RAN node 112 of a wireless communication system 100, wherein the method is: The first indication 301 is to send a first indication to the second RAN node 112, the first indication indicating whether one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure, The process involves receiving a response from the second RAN node 112 including a second indication, the second indication indicating whether one or more second IEs, which are part of the procedure, are supported by the second RAN node 112 during the procedure, and further, whether they are supported by one or more of the first CN node 131, which provides services to the first RAN node 111, and the second CN node 132, which provides services to the second RAN node 112 during the procedure. Includes one or more of the following.

[0203] Embodiment 2. The method described in Embodiment 1, The first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure. The second indication further involves one or more second functions associated with each of the one or more second IEs that are part of the procedure, which are supported by the second RAN node 112 during the procedure. ru This indicates whether or not, and further, whether or not it is supported by one or more of the following: for example, the first CN node 131 which provides services to the first RAN node 111 during the procedure, and the second CN node 132 which provides services to the second RAN node 112.

[0204] Embodiment 3. The method according to Embodiment 1 or 2, One or more secondary IEs are selected from one or more primary IEs, One or more secondary functions are selected from one or more primary functions, It is one or more of the following.

[0205] Embodiment 4. A method according to any one of Embodiments 1 to 3, The first indication transmitted to the second RAN node 112 is: One or more first IEs are supported during the procedure by one or more intermediate nodes, such as a first CN node 131 providing services to a first RAN node 111, and a second CN node 132 providing services to a second RAN node, and / or One or more first functions associated with each of the one or more first IEs are supported during the procedure by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111, and a second CN node 132 providing services to the second RAN node. The data is filtered based on one or more of the above criteria and received by the second RAN node 112.

[0206] Embodiment 5. A computer program that, when executed on a processor, includes instructions that cause the processor to perform any one of Embodiments 1 to 4.

[0207] Embodiment 6. A carrier comprising the computer program described in Embodiment 5, wherein the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0208] Embodiment 7. A method performed by the second RAN node 112 to process information elements (IE) supported in relation to a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112 of the wireless communication system 100, the procedure being carried out by the second RAN node 112, Receiving a first indication 401 from the first RAN node 111, wherein the first indication indicates whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure. Sending a response to the first RAN node 111 including a second indication 402, wherein the second indication indicates whether one or more second IEs, which are part of the procedure, are supported by the second RAN node 112 during the procedure, and further, whether they are supported by, for example, one or more of the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure. Includes one or more of the following.

[0209] Embodiment 8. The method described in Embodiment 7, The first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure. The second indication further indicates whether one or more second functions associated with each of the one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and whether they are supported by one or more of the following, for example, the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure.

[0210] Embodiment 9. The method described in Embodiment 7 or 8, One or more secondary IEs are selected from one or more primary IEs, One or more secondary functions are selected from one or more primary functions. It is one or more of the following.

[0211] Embodiment 10. A method according to any one of Embodiments 7 to 9, A first indication received from the first RAN node 111 is supported in the process by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node, and / or each of the one or more first IEs is associated with one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node. One or more The first function is filtered and received based on one or more of the following: whether it is supported during the procedure.

[0212] Embodiment 11. A computer program that, when executed on a processor, includes instructions that cause the processor to perform any one of Embodiments 7 to 10.

[0213] Embodiment 12. A carrier comprising the computer program described in Embodiment 11, wherein the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0214] Embodiment 13. A method performed by a first CN node 131 to process information elements (IEs) supported in relation to a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112 of a wireless communication system 100, wherein the first CN node 131 provides services to the first RAN node 111, and the method is performed by a first CN node 131 providing Receiving a first indication transmitted from the first RAN node 111 to the second RAN node 112, wherein the first indication indicates whether one or more first IEs, which are part of a procedure, are supported by the first RAN node 111 during the procedure. Filter 502 one or more first IEs included in the first indication based on whether one or more first IEs are supported by the first CN node 131, The filtered first indication is transmitted 503 to the second RAN node 112, wherein the filtered first indication indicates whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node 111 and the first CN node 131 during the procedure. Includes one or more of the following.

[0215] Embodiment 14. The method described in Embodiment 13, The first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure, and the method further Filtering 502 further involves filtering one or more first functions included in the first indication based on whether one or more first functions are supported by the first CN node 131. and , Send filtered first indications to the second RAN node 112 indicating whether one or more first functions associated with each of the one or more first IEs are supported by both the first RAN node 111 and the first CN node 131 during the procedure 503. and, one or more of the Includes.

[0216] Embodiment 15. A computer program that, when executed on a processor, includes instructions that cause the processor to perform the actions described in Embodiment 13 or 14.

[0217] Embodiment 16. A carrier comprising the computer program according to Embodiment 15, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a wireless signal, a microwave signal, or a computer-readable storage medium.

[0218] Embodiment 17. A method executed by a second core network (CN) node 132 to process an information element (IE) supported with respect to a procedure in which a plurality of network nodes such as a first CN node 131 providing services to a first radio access network (RAN) node 111 and a second CN node 132 providing services to a second RAN node 112 are involved, for example, from the first RAN node 111 to the second RAN node 112 in the wireless communication system 100, wherein the second CN node 132 provides services to the second RAN node 112, and the method includes: Receiving a first indication filtered by a first CN node 131 and transmitted from the first RAN node 111 toward the second RAN node 112 via the first CN node 131 providing services to the first RAN node 111, wherein the first indication filtered by the first filtering indicates whether one or more first IEs that are part of the procedure are supported by both the first RAN node 111 and the first CN node 131 during the procedure; and Further filtering 602 the one or more first IEs included in the received first indication filtered by the first filtering based on whether the one or more first IEs are supported by the second CN node 132; and Transmitting 603 the first indication further filtered by the second CN node 132, which indicates whether one or more first IEs are supported by the first RAN node 111, the first CN node 131, and the second CN node 132 during the procedure, toward the second RAN node 112. 3 Including one or more of the above.

[0219] ​Embodiment 18. The method described in Embodiment 17, The first filtered first indication further includes one or more first functions associated with each of the one or more first IEs during the procedure, the first RAN node 1 1 The method indicates whether it is supported by both 1 and the first CN node 131, and further, Further filtering of one or more first IEs included in the received first filtered first indication 602 is based on whether one or more first functions are supported by the second CN node 132. and , Sending a further filtered first indication to the second RAN node 112, indicating whether one or more first functions associated with each of the one or more first IEs are supported by the first RAN node 112, the first CN node 131, and the second CN node 132 during the procedure, one or more of the Includes.

[0220] Embodiment 19. A computer program that, when executed on a processor, includes instructions that cause the processor to perform the actions described in Embodiment 17 or 18.

[0221] Embodiment 20. A carrier comprising the computer program described in Embodiment 19, wherein the carrier is one of the following: an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0222] Embodiment 21. A first RAN node 111 of a wireless communication system 100 is configured to process information elements (IEs) that support procedures involving multiple network nodes, such as a first core network (CN) node 131 that provides services to a first RAN node 111 and a second CN node 132 that provides services to the second RAN node 112, wherein the first RAN node 111 further... For example, a means of a transmission unit included in the first RAN node 111 to transmit a first indication to the second RAN node 112, wherein the first indication is one or more first IEs that are part of the procedure during the procedure D1 1 1 Therefore, it is adapted to indicate whether or not it is supported, For example, a receiving unit included in the first RAN node 111 receives a response from the second RAN node 112 including a second indication. believe The second indication indicates whether one or more second IEs, which are part of the procedure, are supported by the second RAN node 112 during the procedure, and further whether they are further supported by, for example, one or more of the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure. It is configured to perform one or more of the following actions.

[0223] Embodiment 22. The first RAN node 111 as described in Embodiment 21, The first indication is further adapted to indicate whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure. The second indication is further adapted to indicate whether one or more second functions associated with each of the one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and whether they are ported by, for example, one or more of the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure.

[0224] Embodiment 23. The first RAN node 111 as described in Embodiment 21 or 22, One or more secondary IEs are selected from one or more primary IEs, One or more secondary functions are selected from one or more primary functions, It is one or more of the following.

[0225] Embodiment 24. A first RAN node 111 according to any one of Embodiments 21 to 23, For example, a first indication transmitted to a second RAN node 112 by means of a transmission unit included in a first RAN node 111 may be supported in the process by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node, and / or a first function associated with each of the one or more first IEs may be supported in the process by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node. ru The data is filtered based on one or more of the following criteria and received by the second RAN node 112.

[0226] Embodiment 25. A second RAN node 112 of a wireless communication system 100, configured to process information elements (IEs) supported by a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112, wherein the second RAN node 112 further... For example, the receiving unit included in the second RAN node receives a first indication from the first RAN node 111, wherein the first indication is adapted to indicate whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure. For example, by means of a transmission unit included in the second RAN node 112, transmitting a response including a second indication towards the first RAN node 111, wherein the second indication is adapted to indicate whether one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and further, for example, whether it is supported by one or more of the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure, configured to perform one or more of the following.

[0227] Embodiment 26. The second RAN node 112 according to Embodiment 25, where the first indication is further adapted to indicate whether one or more first functions associated with each of one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure, where the second indication is further adapted to indicate whether one or more second functions associated with each of one or more second IEs that are part of the procedure are supported by the second RAN node 112 during the procedure, and further, for example, whether it is supported by one or more of the first CN node 131 that provides services to the first RAN node 111 and the second CN node 132 that provides services to the second RAN node 112 during the procedure.

[0228] Embodiment 27. The second RAN node 112 according to Embodiment 25 or 26, where one or more second IEs are selected from one or more first IEs, where one or more second functions are selected from one or more first functions, and is one or more of the following.

[0229] Embodiment 28. The second RAN node 112 according to any one of Embodiments 25 to 27, For example, a first indication received from the first RAN node 111 by means of a receiving unit included in the second RAN node 112 is received filtered based on one or more of the following: one or more first IEs are supported in the process by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node; and / or a first function associated with each of the one or more first IEs is supported in the process by one or more intermediate nodes, such as a first CN node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node.

[0230] Embodiment 29. A first CN node 131 configured to process information elements (IE) supported by a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112, from a first radio access network (RAN) node 111 to a second RAN node 112 of a wireless communication system 100, wherein the first CN node provides services to the first RAN node 111, and the first CN node further... For example, receiving a first indication transmitted from a first RAN node 111 to a second RAN node 112 by means of a receiving unit included in the first CN node 131, wherein the first indication is adapted to indicate whether one or more first IEs, which are part of the procedure, are supported by the first RAN node 111 during the procedure, For example, a filtering unit included in the first CN node 131 filters one or more first IEs included in the first indication based on whether one or more first IEs are supported by the first CN node 131, For example, a transmission unit included in the first CN node 131 transmits a filtered first indication to the second RAN node 112, wherein the filtered first indication is adapted to indicate whether one or more first IEs, which are part of the procedure, are supported by both the first RAN node 111 and the first CN node 131 during the procedure. It is configured to perform one or more of the following actions.

[0231] Embodiment 30. The first CN node 131 described in Embodiment 29, The first indication further indicates whether one or more first functions associated with each of the one or more first IEs that are part of the procedure are supported by the first RAN node 111 during the procedure, and the first CN node 131 further, For example, the filtering unit included in the first CN node 131 is configured to filter by filtering one or more first functions included in the first indication based on whether one or more first functions are supported by the first CN node 131. For example, a means of a transmission unit included in the first CN node 131 is configured to transmit a filtered first indication to the second RAN node 112, and the filtered first indication is adapted to indicate whether one or more first functions associated with each of one or more first IEs are supported by both the first RAN node 111 and the first CN node 131 during the procedure. It is configured to perform one or more of the following actions.

[0232] Embodiment 31. A second CN node 132 configured to process information elements (IEs) supported by a procedure involving multiple network nodes, such as a first core network (CN) node 131 providing services to the first RAN node 111 and a second CN node 132 providing services to the second RAN node 112, from a first radio access network (RAN) node 111 to a second RAN node 112, wherein the second CN node 132 provides services to the second RAN node 112, and the second CN node 132 further... For example, receiving a first filtered first indication transmitted from the first RAN node 111 to the second RAN node 112 via the first CN node 131 which provides services to the first RAN node 111, by means of a receiving unit included in the second CN node 132, wherein the first filtered first indication is adapted such that one or more first IEs, which are part of the procedure, indicate whether or not they are supported by both the first RAN node 111 and the first CN node 131 during the procedure. For example, a filtering unit included in the first CN node 132 further filters one or more first IEs included in the first indication based on whether one or more first IEs are supported by the second CN node 132, For example, a means of a transmission unit included in the second CN node 132 transmits to the second RAN node 112 a first indication that has been further filtered by the second CN node 112, which indicates whether one or more first IEs are supported by the first RAN node 111, the first CN node 131, and the second CN node 132 during the procedure. It is configured to perform one or more of the following actions.

[0233] Embodiment 32. The second CN node 132 described in Embodiment 31, The first filtered first indication further indicates whether one or more first functions associated with each of the one or more first IEs are supported by both the first RAN node 131 and the first CN node 131 during the procedure, and the second CN node (132) further indicates, For example, a filtering unit included in the first CN node 132 filters one or more first IEs included in the received first filtered first indication based on whether one or more first functions are supported by the second CN node 132, For example, the means of a transmitting unit included in the second CN node 132 transmits to the second RAN node 112 a first indication adapted to indicate whether one or more first functions associated with each of the one or more first IEs are supported by the first RAN node 131, the first CN node 131, and the second CN node 132 during the procedure, It is configured to perform one or more of the following actions.

[0234] Further expansion and variations Referring to Figure 13 according to one embodiment, the communication system includes a communication network 3210 such as a wireless communication network 100 such as a 3GPP type cellular network, which includes an access network 3211 such as an IoT network, WLAN, or wireless access network, and a core network 3214. The access network 3211 includes a first RAN node 111 or a second RAN node 112, access nodes, APs. STA 、The system includes multiple base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE), such as a non-APSTA UE 120 located in coverage area 3213c, is configured to wirelessly connect to or be paged by a corresponding base station 3212c. A second UE 3292, such as a non-APSTA UE 120 located in coverage area 3213a, is connectable wirelessly to a corresponding base station 3212a. Although several UEs 3291 and 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in a coverage area or where a single UE is connected to a corresponding base station 3212.

[0235] The communication network 3210 itself is connected to a host computer 3230, which may be embodied by standalone server, cloud implementation server, distributed server hardware and / or software, or as a processing resource in a server farm. The host computer 3230 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 3221, 3222 between the communication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or via an optional intermediate network 3220. The intermediate network 3220 may be one or more combinations of public, private, or hosted networks, and the intermediate network 3220 (if any) may be a backbone network or the internet, and in particular, the intermediate network 3220 may have two or more subnetworks (not shown).

[0236] The communication system in Figure 13, as a whole, enables a connection between one of the connected UEs 3291, 3292 and the host computer 3230. The connectivity can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and / or signaling over the OTT connection 3250 using the access network 3211, the core network 3214, an optional intermediate network 3220, and possible further infrastructure as intermediaries (not shown). The OTT connection 3250 can be transparent in the sense that participating communication devices through which the OTT connection 3250 passes are unaware of the routing of uplink and downlink communications. For example, base station 3212 is not notified of, or does not need to be notified of, the past routing of incoming downlink communications with data originating from host computer 3230 that is forwarded (e.g., handed over) to connected UE 3291. Similarly, base station 3212 does not need to be aware of the future routing of outgoing uplink communications from UE3291 to host computer 3230.

[0237] An exemplary implementation of the UE, base station, and host computer described in the preceding paragraph, according to one embodiment, will be described with reference to Figure 14. In the communication system 3300, the host computer 3310 controls the input of different communication devices of the communication system 3300. tough A communication input configured to set up and maintain a wired or wireless connection with the face. toughThe host computer 3310 comprises hardware 3315, including face 3316. The host computer 3310 further comprises processing circuitry 3318 which may have memory and / or processing capabilities. In particular, processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. Software 3311 includes a host application 3312. The host application 3312 connects to a remote device such as the UE3330 via an OTT connection 3350 terminated at the UE3330 and the host computer 3310. Toyu It may be possible to operate in a way that provides services to the remote user. The When providing the service, the host application 3312 uses the OTT connection 3350 to send the user Zade We can provide data.

[0238] The communication system 3300 further includes a base station 3320 equipped with hardware 3325 that enables communication with the host computer 3310 and the UE 3330. Hardware 3325 enables communication with different communication devices of the communication system 3300. tough Communication input for setting up and maintaining a wired or wireless connection with the face. tough A wireless input for setting up and maintaining a wireless connection 3370 between face 3326 and UE 3330 located in a coverage area (not shown) where base station 3320 provides service. tough May include Face 3327. Communication input toughFace 3326 may be configured to facilitate a connection 3360 to a host computer 3310. The connection 3360 may be direct or may pass through a core network of the communication system (not shown in Figure 14) and / or one or more intermediate networks outside the communication system. In embodiments, the hardware 3325 of the base station 3320 further comprises a processing circuit 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. The base station 3320 may have internally stored software 3321 or software 332 accessible via an external connection. 1 Furthermore, it possesses

[0239] The communication system 3300 further includes the UE 3330 already mentioned. Its hardware 3335 is configured to set up and maintain a radio connection 3370 with a base station that provides service to the coverage area where the UE 3330 is currently located. toughThe UE3330 may include a face 3337. The hardware 3335 of the UE3330 further comprises a processing circuit 3338, the processing circuit 3328 which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. The UE3330 further comprises software 3331, the software 3311 which is stored in or accessible by the UE3330 and executable by the processing circuit 3338. The software 3331 includes a host application 3332. The client application 3332 may be operated to provide services to human or non-human users through the UE3330 with the support of a host computer 3310. On the host computer 3310, the running host application 3312 can communicate with the running client application 3332 via an OTT connection 3350 terminating at the UE3330 and the host computer 3310. When providing services to a user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 receives the request data and user data. Zade It can transfer both data. Client application 3332 is The Dialogue and provide Zade It is possible to generate data.

[0240] It should be noted that the host computer 3310, base station 3320, and UE3330 shown in Figure 14 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, and 3212c, and one of the UE3291 and 3292, respectively, in Figure 13. In other words, the internal operation of these entities will be as shown in Figure 14, and independently, the surrounding network topology may be as shown in Figure 13.

[0241] In Figure 14, the OTT connection 3350 is depicted abstractly to illustrate communication between the host computer 3310 and the radio device 3330 via the base station 3320, without explicitly referring to the intermediate devices and the precise routing of messages through these devices. The network infrastructure may determine the routing, and the routing may be configured to be hidden from the service provider operating the UE 3330 or the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further make decisions to dynamically change the routing, for example, based on considerations or reconfiguration of the network load balancing.

[0242] The radio connection 3370 between the UE3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more different embodiments improve the performance of the OTT service provided to the UE3330 by using an OTT connection 3350 in which the radio connection 3370 forms the final segment. More precisely, the teachings of these embodiments can improve applicable RAN effects, namely data rate, latency, and power consumption, thereby providing corresponding effects on the OTT service, such as reduced user latency, relaxed file size limitations, better responsiveness, and extended battery life.

[0243] Measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that may be improved by one or more embodiments. Furthermore, there may be optional network functions for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to variations in the measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) are located in or in connection with a communication device through which the OTT connection 3350 passes, and the sensors can participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities that the software 3311, 3331 can calculate or estimate the monitored quantities of. Reconfiguration of the OTT connection 3350 may include message format, retransmission settings, preferred routing, etc., and the reconfiguration may not affect the base station 3320 and may be unknown or imperceptible to the base station 3320. Such procedures and functions may be known and practiced in the art. In certain embodiments, the measurement may include proprietary UE signaling to facilitate host computer 3310 measurements such as throughput, propagation time, latency, etc. The measurement can be implemented so that software 3311, 3311 sends messages, particularly empty or "dummy" messages, while monitoring propagation time, errors, etc., using an OTT connection 3350.

[0244] Figure 15 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station such as a first RAN node 111 or a second RAN node 112, and a UE such as UE 120, which may be described with reference to Figures 13 and 14. For the sake of simplicity, only the reference drawing to Figure 15 is included in this section. In the first action 3410 of this method, the host computer is a UE ZadehIn an optional sub-action 3411 of the first action 3410, the host computer provides user data by executing a host application. In the second action 3420, the host computer initiates a transmission that carries the user data to the UE. In an optional third action 3430, the base station transmits the user data carried in the transmission initiated by the host computer to the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth action 3440, the UE executes a client application related to the host application executed by the host computer.

[0245] Figure 16 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a non-AP STA, which may be described with reference to Figures 13 and 14. For the sake of simplicity, only the reference drawing to Figure 16 is included in this section. In the first action 3510 of this method, the host computer is a UE Zadeh The host computer provides user data by executing a host application in an optional substep (not shown). In a second action 3520, the host computer initiates a transmission that carries the user data to the UE. The transmission may pass through a base station in accordance with the teachings of the embodiments described through this disclosure. In an optional third action 3530, the UE receives the user data carried in the transmission. Zade Receive data.

[0246] Figure 17 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station such as AP STA, and a UE such as a non-AP STA, which may be described with reference to Figures 13 and 14. For the sake of simplicity, only the reference drawing to Figure 17 is included in this section. In the optional first action 3610 of this method, the UE is a host computer Ta Receive the input data provided. In addition or alternatively, in the optional second action 3620, UE will Zade The UE provides user data. In an optional sub-action 3621 of the second action 3620, the UE provides user data by running a client application. In a further optional sub-action 3611 of the first action 3610, the UE runs a client application that provides user data in response to incoming input data provided by the host computer. While providing user data, the client application being run may further consider user input received from the user. Regardless of the particular way the user data is provided, in an optional third sub-action 3630, the UE initiates sending the user data to the host computer. In a fourth action 3640 of the method, the host computer Ta is The system receives user data transmitted from the UE in accordance with the teachings of the embodiments described through this disclosure.

[0247] Figure 18 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a non-AP STA, which may be described with reference to Figures 13 and 14. For the sake of simplicity, only the reference drawing to Figure 18 is included in this section. In the first action 3710 of the optional method, according to the teachings of the embodiments described throughout this disclosure, the base station receives a UE from the UE. Zade The base station receives the user. In the optional second action 3720, the base station receives the user. Zade Data host computer Tahe The transmission is initiated. In the third action 3730, the host computer controls the user that is carried in the transmission initiated by the base station. Zade Receive data.

[0248] Definitions of Abbreviations and Acronyms as Used in This Specified Abbreviations: Explanation AMF: Access and Mobility Management Function MME: Mobility Management Entity RAT: Wireless Access Technology EPS: Advanced Packet System 5GS: 5G system HO: Handover CN: Core Network NW: Network NAS: Non-accessible Stratum IAB: Integrated Access and Backhaul

Claims

1. A method performed by a first RAN node in a handover procedure with a second radio access network (RAN) node via a core network (CN) node of a wireless communication system, An application protocol (AP) used between the first RAN node and the CN node transmits a message to the CN node containing a first container information element (IE) to be forwarded to the second RAN node, wherein the first container IE includes a first list of IE identifiers of the AP for obtaining information regarding the support level of a particular feature at the second RAN node. The CN node receives a response from the CN node that includes a second container IE obtained from the second RAN node, wherein the second container IE includes a second list of IE identifiers of the AP, and for each IE identifier in the second list, (i) a support indication if the second RAN node has information that the functionality related to the indicated IE is supported, or (ii) a non-support indication if the second RAN node has information that the functionality related to the indicated IE is not supported. A method that includes this.

2. The method according to claim 1, The aforementioned message is a HANDOVER Required message, in this manner.

3. The method according to claim 1, The CN node is an Access and Mobility Management Function (AMF), in this method.

4. The method according to claim 1, The support indication or non-support indication is a method included in the Next Generation AP (NGAP) Protocol IE Support Information IE.

5. A method performed by a second RAN node in a handover procedure initiated by a first radio access network (RAN) node via a core network (CN) node of a wireless communication system, An application protocol (AP) used between the second RAN node and the CN node receives a request message from the CN node that includes a first container information element (IE) obtained from the first RAN node, wherein the first container IE includes a first list of IE identifiers of the AP for obtaining information regarding the support level of a particular feature in the second RAN node. Sending a response message to the CN node that includes a second container IE to be forwarded to the first RAN node, wherein the second container IE includes a second list of IE identifiers of the AP, and for each IE identifier in the second list, (i) a support indication if the second RAN node has information that the functionality related to the indicated IE is supported, or (ii) a non-support indication if the second RAN node has information that the functionality related to the indicated IE is not supported. Methods that include...

6. The method according to claim 5, The IE identifier of the AP corresponds to the next-generation AP (NGAP) protocol IE identifier.

7. The method according to claim 5, The aforementioned request message is a HANDOVER Request message, The method wherein the response message is a HANDOVER Request acknowledgment or a HANDOVER Failure message.

8. The method according to claim 7, The method wherein the second container IE is a transparent container IE from the target next-generation RAN (NG-RAN) node included in the HANDOVER Request acknowledgment to the source NG-RAN node, or the second container IE is a transparent failure transparent container IE from the target NG-RAN node included in the HANDOVER Failure message to the source NG-RAN node.

9. The method according to claim 5, The CN node is an Access and Mobility Management Function (AMF), in this method.

10. The method according to Claim 5, The support indication or non-support indication is a method included in the Next Generation AP (NGAP) Protocol IE Support Information IE.

11. The method according to claim 5, A method wherein the second list includes all of the IE identifiers in the first list.

12. A first RAN node configured to process information elements (IEs) supported by procedures involving multiple network nodes to a second radio access network (RAN) node of a wireless communication system, The first RAN node is further configured to perform the method according to any one of claims 1 to 4.

13. The second RAN node is configured to process information elements (IEs) supported in relation to a procedure involving multiple network nodes from a first radio access network (RAN) node to a second RAN node of a wireless communication system, The second RAN node is further configured to perform the method according to any one of claims 5 to 11.

Images