Random access channel reporting

Abstract

Example embodiments of the present disclosure relate to, devices, methods and computer readable medium for random access channel (RACH) reporting. In a method, a first data storage device receives a RACH report from at least one of a first network node or a second data storage device. The RACH report is transmitted by a terminal device within an area served by the first network node. The first data storage device determines that the RACH report is to be transmitted to a second network node. The first data storage device transmits the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

Description

[0001] RANDOM ACCESS CHANNEL REPORTING

[0002] FIELDS

[0003] [1] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to apparatuses, methods and computer readable medium for random access channel (RACH) reporting.

[0004] BACKGROUND

[0005] [2] RACH reporting is a technology in mobile communication systems that tracks and reports the performance and status of a random access channel. The random access channel is a channel for initial access and re-establishment of a connection between a user equipment (UE) and a base station.

[0006] SUMMARY

[0007] [3] In a first aspect of the present disclosure, there is provided a first data storage device. The first data storage device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first data storage device at least to: receive a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; determine that the RACH report is to be transmitted to a second network node; and transmit the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

[0008] [4] In a second aspect of the present disclosure, there is provided a first network node. The first network node comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network node at least to: receive a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; obtain an identifier of the second network node; and transmit the RACH report and the identifier of the second network node to a data storage device.

[0009] [5] In a third aspect of the present disclosure, there is provided a second network node. The second network node comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network node at least to: transmit, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and receive, in accordance with the subscribing request, the RACH report from the first data storage device.

[0010] [6] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; determining that the RACH report is to be transmitted to a second network node; and transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

[0011] [7] In a fifth aspect of the present disclosure, there is provided a method. The method comprises: receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; obtaining an identifier of the second network node; and transmitting the RACH report and the identifier of the second network node to a data storage device.

[0012] [8] In a sixth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and receiving, in accordance with the subscribing request, the RACH report from the first data storage device.

[0013] [9] In a seventh aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; means for determining that the RACH report is to be transmitted to a second network node; and means for transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

[0014]

[0010] In an eighth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; means for obtaining an identifier of the second network node; and means for transmitting the RACH report and the identifier of the second network node to a data storage device.

[0015]

[0011] In a ninth aspect of the present disclosure, there is provided a third apparatus. The third apparatus comprises means for transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and means for receiving, in accordance with the subscribing request, the RACH report from the first data storage device.

[0016]

[0012] In a tenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.

[0017]

[0013] In an eleventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifth aspect.

[0018]

[0014] In a twelfth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixth aspect.

[0019]

[0015] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

[0020] BRIEF DESCRIPTION OF THE DRAWINGS

[0021]

[0016] Some example embodiments will now be described with reference to the accompanying drawings, where:

[0022]

[0017] FIG. 1 illustrates an example structure of network nodes in accordance with some example embodiments of the present disclosure;

[0023]

[0018] FIG. 2 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

[0024]

[0019] FIG. 3 illustrates a signaling diagram for communication in accordance with some example embodiments of the present disclosure;

[0025]

[0020] FIG. 4 illustrates a signaling diagram for communication in accordance with some example embodiments of the present disclosure;

[0026]

[0021] FIG. 5 illustrates a signaling diagram for communication in accordance with some example embodiments of the present disclosure;

[0027]

[0022] FIG. 6 illustrates a signaling diagram for communication in accordance with some example embodiments of the present disclosure;

[0028]

[0023] FIG. 7 illustrates a signaling diagram for communication in accordance with some example embodiments of the present disclosure;

[0029]

[0024] FIG. 8 illustrates a flowchart of an example intra-DSF communication in accordance with some example embodiments of the present disclosure;

[0030]

[0025] FIG. 9 illustrates a flowchart of an example RACH report forwarding via the global DSF in accordance with some example embodiments of the present disclosure;

[0031]

[0026] FIG. 10 illustrates a flowchart of an example of requesting the address of a local DSF instance from the global DSF in accordance with some example embodiments of the present disclosure;

[0032]

[0027] FIG. 11 illustrates a flowchart of an example of a RACH report directly forwarding to a neighbor DSF in accordance with some example embodiments of the present disclosure;

[0033]

[0028] FIG. 12 illustrates a flowchart of an example method implemented at a first data storage device in accordance with some example embodiments of the present disclosure;

[0034]

[0029] FIG. 13 shows a flowchart of an example method implemented at a first network node in accordance with some example embodiments of the present disclosure;

[0035]

[0030] FIG. 14 shows a flowchart of an example method implemented at a second network node in accordance with some example embodiments of the present disclosure;

[0036]

[0031] FIG. 15 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

[0032] FIG. 16 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0037]

[0033] Throughout the drawings, the same or similar reference numerals represent the same or similar element.

[0038] DETAILED DESCRIPTION

[0039]

[0034] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

[0040]

[0035] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0041]

[0036] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0042]

[0037] It shall be understood that although the terms “first,” “second,” ..., etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0043]

[0038] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0044]

[0039] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.

[0045]

[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprise”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0041] As used in this application, the term “circuitry” may refer to one or more or all of the following:

[0046] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0047] (b) combinations of hardware circuits and software, such as (as applicable):

[0048] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and

[0049] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

[0050] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0051]

[0042] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0052]

[0043] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0053]

[0044] As used herein, the term “network device” or “network node” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

[0054]

[0045] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0055]

[0046] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0056]

[0047] RACH reporting may be used in the context of dual connectivity (DC) and carrier aggregation (CA). A user equipment (UE) may have a RACH report corresponding to a primary secondary cell (PScell) controlled by a secondary node (SN). A RACH report may provide various statistical information and performance indicators regarding to the random access channel, such as RACH attempt count, RACH success count, RACH collision count, and RACH delay.

[0057]

[0048] FIG. 1 illustrates an example structure of network nodes in accordance with some example embodiments of the present disclosure. As shown in FIG. 1, a master node (MN) 102 may inform an SN 2 106 that its level 1 connection consists of a node SN 1 104, and that its level 2 connection consists of an SN 3 108, and an SN 4 110. Similarly, the SN 2 106 may inform the MN 102 that its level 1 connection consists of nodes SN 5 112 and SN 6 114. With this information, the MN 102 may reach the SN 3 108 to the SN 6 114 via a suitable path (such as via the SN 1 104 or the SN 2 106) if it needs to send a RACH report to any of nodes SN 3 108 to SN 6 114.

[0058]

[0049] Currently, a problem of how to forward a RACH report remains unclear in some scenarios. For example, a UE is allowed to provide the RACH report within a long time period. Within this time period, the UE may have been handed over to a new MN in a different radio access network (RAN) notification area or even a different city. Correspondingly, the communication is not in dual connectivity mode anymore. Optionally, the UE may report to the MN the PScell or a PScell list corresponding to the RACH report(s). This new MN to which the UE is now connected may not have an existing connection to the old SN for which the RACH report corresponds, and therefore it is unclear how the RACH report should be forwarded.

[0059]

[0050] Furthermore, whether and how to forward the RACH report in case the MN that retrieves the RACH report is not connected to any SN associated to the PSCells received with the RACH report is to be studied. In addition, NG and SI interfaces forwarding of the RACH report may not be considered, in order to avoid overloading the NG interface and negatively affecting the interface’s throughput and Quality of Service (QoS) provided to the UE. It is to be noted that the RACH report is desired at the old SN as it may be used to compile statistics and optimize the access procedures of its cells.

[0060]

[0051] Example embodiments of the present disclosure propose a scheme of RACH reporting. With this scheme, a first network node (for example, an MN) and / or a second data storage device transmits a RACH report to a first data storage device. The first data storage device determines the RACH report is to be transmitted to a second network node (for example, an SN). Then, the first data storage device transmits the RACH report to the second network node and / or a third data storage device associated with the second network node. The data storage device including the first data storage device, the second data storage device, or the third data storage device, for example, may be a local data storage function (DSF) instance or a global DSF instance.

[0061]

[0052] According to proposed scheme, the data storage devices are introduced into the scheme of RACH reporting. In this way, the RACH report may be transmitted through the data storage devices, avoiding the loss of RACH report.

[0062]

[0053] Example embodiments will be discussed in detailed below with reference to the accompanying figures. FIG. 2 illustrates an example communication environment 200 in which example embodiments of the present disclosure can be implemented.

[0063]

[0054] As shown in FIG.2, the communication environment 200 comprises a data storage device 240, a data storage device 250, a data storage device 260, and a global data storage device 270. For example, the data storage device 240, the data storage device 250, or the data storage device 260 may be a local DSF instance (also referred to as a DSF). The global data storage device 270, for example, may be a global DSF instance (also referred to as a global DSF).

[0064]

[0055] In the communication environment 200, one or more first network nodes (for example, a first network node 210) and one or more second network nodes (for example, a second network node 220) are located within an area 230 served by the data storage device 240. A terminal device 226 may communicate with the first network node 210. The terminal device 226, for example, may operate as a user equipment. Similarly, one or more first network nodes and one or more second network nodes (for example, a second network node 222) are located within an area 232 served by the data storage device 250. One or more first network nodes and one or more second network nodes (for example, a second network node 224) are located within an area 234 served by the data storage device 260. For example, the first network node (such as the first network node 210) may operate as a master node, and the second network node (such as the second network node 220) may operate as a secondary node.

[0056] In some example embodiments, the area 230 served by the data storage device 240 and the area 232 served by the data storage device 250 are neighboring, and the data storage device 240 and the data storage device 250 are connected. Similarly, the area 232 served by the data storage device 250 and the area 234 served by the date storage device 260 are also neighboring, and the data storage device 250 and the data storage device 260 are connected.

[0065]

[0057] As shown in FIG.2, the data storage device 240, the data storage device 250, and the data storage device 260 are all connected to a global data storage device 270. Because the data storage device 240 and the data storage device 260 are not connected with each other directly, they cannot communicate with each other directly. Therefore, a communication between the data storage device 240 and the data storage device 260 may be performed through the global data storage device 270.

[0066]

[0058] It is to be understood that the number and types of devices, equipment, or areas are shown in FIG. 2 for the purpose of illustration without suggesting any limitation. For example, the communication environment 200 may include any suitable number of data storage devices, global data storage devices, user equipment, areas, and network nodes.

[0067]

[0059] In some example embodiments, a link from the user equipment 226 to the network node 210 may be referred to as an uplink (UL), and a link from the network node 210 to the user equipment 226 may be referred to as a downlink (DL). In UL, the network node 210 is a RX device (or a receiver) and the user equipment 226 is a TX device (or a transmitter). In DL, the network node 210 is a transmitting (TX) device (or a transmitter) and the user equipment 226 is a receiving (RX) device (or a receiver).

[0068]

[0060] In some example embodiments, operations described with respect to a terminal device may be implemented at a network node or other devices, and operations described with respect to a network node may be implemented at a terminal device or other devices.

[0069]

[0061] Communications in the communication environment 200 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0070]

[0062] Reference is now made to FIG. 3, which illustrates a signaling diagram 300 for communication in accordance with some example embodiments of the present disclosure. As shown in FIG. 3, the signaling diagram 300 involves the first network node 210, the second network node 220 and the terminal device 226 in the communication environment 200. The first network node 210, for example, may comprise an MN, and the second network node 220 may comprises an SN. The terminal device 226 may comprise a UE.

[0071]

[0063] The signaling diagram 300 further involves a first data storage device 310, a second data storage device 320, and a third data storage device 330. The first data storage device 310, the second data storage device 320, or the third data storage device 330 may comprise at least one of the data storage devices 240, 250 or 260, or the global data storage device 270.

[0072]

[0064] As shown in FIG. 3, the first network node 210 receives (340) a RACH report from the terminal device 226 within a cell controlled by the first network node 210. The RACH report corresponds to the second network node 220. For example, the RACH report may comprise an identifier of the second network node 220. In an example embodiment, the received RACH report may be stored by the first network node.

[0073]

[0065] In some example embodiments, the first network node 210 obtains (342) an identifier of the second network node 220. For example, the first network node 210 may obtain the identifier of the second network node 220 by reading the identifier from the received RACH report, or may receive the identifier of the second network node 220 from the terminal device 226.

[0074]

[0066] Then, the first network node 210 transmits the RACH report and the identifier of the second network node 220 to a data storage device. The data storage device may be a data storage device corresponding to the first network node 210, for example, a data storage instance serving the first network node 210.

[0067] The second network node 220 transmits (344) to the first data storage device 310, a subscribing request for receiving an update of a RACH report. The RACH report is transmitted by a terminal device and corresponds to a cell controlled by the second network node 220. For example, the subscribing request may comprise a cause (i.e., the RACH report) and a key which may be an identifier of the second network node 220.

[0075]

[0068] The first data storage device 310 receives (346) a RACH report from the first network node 310 and / or receives (348) a RACH report from the second data storage device 320. The RACH report is transmitted by a terminal device within an area served by the first network node and corresponds to a cell controlled by the second network node. In some example embodiments, the second data storage device may comprise at least one of a data storage device associated with the first network node, or a global data storage device. After that, the first data storage device determines (350) that the RACH report is to be transmitted to the second network node 220.

[0076]

[0069] Then, the first data storage device 310 transmits (352) the RACH report to the second network node 220 and / or transmits (354) the RACH report to the third data storage device 330 associated with the second network node 220. For example, the third data storage device 330 may be a DSF instance serving the second network node 220. Accordingly, in accordance with the subscribing request from the second network node 220 to the first data storage device 310, the second network node receives (352) the RACH report from the first data storage device 310.

[0077]

[0070] The embodiments of the present disclosure are based on a hierarchical DSF architecture. A subscribe-notify procedure will be introduced between a data storage device and the second network node, so that the second network node may receive the RACH report when the report has become available, thereby saving the RACH report and reducing communication hops for transmitting the RACH report.

[0078]

[0071] A process for RACH reporting in an intra-data storage device scenario will be described below with reference to FIG. 4. FIG. 4 illustrates a signaling diagram 400 for communication in accordance with some example embodiments of the present disclosure. As shown in FIG. 4, the signaling diagram 400 involves the first network node 210, the second network node 220 and the first data storage device 320 in the communication environment 200. In this scenario, both the first network node 210 and the second network node 220 may be in an area served by the first data storage device 320.

[0072] In some example embodiments, the second network node 220 transmits (344), to the first data storage device 320, a subscribing request for receiving an update of a RACH report. The RACH report is transmitted by a terminal device and corresponds to a cell controlled by the second network node 220. In an example embodiment, the first data storage device 320 may store the received subscribing request. The subscribing request may be used for subscription, get notification, event monitoring, or detection of the update of the RACH report.

[0079]

[0073] In some example embodiments, in response to receiving the subscribing request from the second network node 220, the first data storage device 320 may transmit (410), to the second network node 220, a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request. For example, the acknowledgement of the subscribing request may be a confirming message of the subscribing request. In this way, upon receiving the confirming message from the first storage device 320, the second network node 220 would know that the subscribing request has been accepted.

[0080]

[0074] In some example embodiments, the first network node 210 receives (340) the RACH report from the terminal device 226 present in a cell / area controlled by the first network node 210. Then, the first network node 210 obtains (342) an identifier of the second network node 220. The first network node 210 transmits (412) the RACH report along with the identifier of the second network node 220 to the first data storage device 320.

[0081]

[0075] In some example embodiments, the first data storage device 320 may determine, based on the identifier of the second network node 220, that the RACH report is to be transmitted to the second network node 220. Then, the first data storage device 320 transmits (352) the RACH report to the second network node 220.

[0082]

[0076] A process for RACH reporting via a global DSF will be described below with reference to FIG. 5. FIG. 5 illustrates a signaling diagram 500 for communication in accordance with some example embodiments of the present disclosure. In the signaling diagram 500, some steps such as 344-352, 410-412 are similar to those in FIG. 3 and FIG. 4, which will not be repeated here.

[0083]

[0077] As shown in FIG. 5, the signaling diagram 500 involves a UE 510, an MN 520, a DSF 1 530, a global DSF 540, a DSF 3 550, and an SN 560. The UE 510 may be an example of the terminal device 226; the MN 520 may be an example of the first network node 210; the DSF 1 530, the global DSF 540, the DSF 3 550 may be an example of the first data storage device 320, respectively. In some example embodiments, in case of the DSF 1 is the first data storage device 320, the global DSF 540 may be an example of the third data storage device 330; in case of the global DSF 540 is the first data storage device 320, the DSF 3 550 may be an example of the third data storage device 330.

[0084]

[0078] In this process, the MN 520 may be in an area served by the DSF 1 530, and the SN 560 may be in an area served by the DSF 3 550, and the area served by the DSF 1 530 and the area served by the DSF 3 550 may not be neighboring. In some example embodiments, a DSF instance is able to contact the global DSF or other local DSFs for report forwarding if necessary. Therefore, the global DSF 540 is introduced in this scenario so that the RACH report can be forwarded via the global DSF 540.

[0085]

[0079] In some example embodiments, the DSF 1 530 determines (570) that the RACH report is to be transmitted to the SN 560. For example, the DSF 1 530 may determine that the RACH report is not intended to be transmitted to a base station in the area served by the DSF 1 530 based on the received identifier. In some example embodiments, a DSF instance is able to determine whether the RACH report is intended for a base station in its area or not.

[0086]

[0080] In some example embodiments, upon determining that the RACH report is to be transmitted to the SN 560, the DSF 1 530 may transmit (572) the RACH report and the identifier of the SN 560 to the global DSF 540.

[0087]

[0081] In some example embodiments, the global DSF 540 determines (574) that the RACH report is to be transmitted to the SN 560. For example, the global DSF 540 may determine the DSF to contact based on the identifier of the SN 560. Then, the global DSF 540 transmits (576) the RACH report and the identifier to the DSF 3 550.

[0088]

[0082] A process for RACH reporting based on an address requested from a global DSF will be described below with reference to FIG. 6. FIG. 6 illustrates a signaling diagram 600 for communication in accordance with some example embodiments of the present disclosure. In the signaling diagram 600, some steps such as 344-352, 410-412, and 570- 572 are similar to those in FIG. 3 -FIG. 5, which will not be repeated here.

[0089]

[0083] In some example embodiments, in case of the DSF 1 530 is the first data storage device 320, the global DSF 540 may be an example of the third data storage device 330; in case of the global DSF 540 is the first data storage device 320, the DSF 3 550 may be an example of the third data storage device 330, and the DSF 1 may be an example of the second data storage device 320.

[0090]

[0084] In this process, the MN 520 may be in an area served by the DSF 1 530, and the SN 560 may be in an area served by the DSF 3 550, and the area served by the DSF 1 530 and the area served by the DSF 3 550 may not be neighboring. Therefore, the global DSF 540 is introduced in this scenario so that the RACH report can be forwarded via the global DSF 540.

[0091]

[0085] In some example embodiments, the DSF 1 530 may transmit (610), to the global data storage device 540, a request for an address of the third data storage device (i.e., the DSF 550 in this case). Correspondingly, the global DSF 540 receives (610), from a fourth data storage device (i.e., the DSF 1 530), the request for an address of the third data storage device (i.e., the DSF 3 550). The request, for example, may comprise the identifier of the SN 560, or the request may be transmitted along with the identifier of the SN 560. In some examples, the fourth data storage device and the first data storage device can be the same device.

[0092]

[0086] In some example embodiments, the global DSF 540 may determine (612) the address of the DSF 3 550, for example, based on the identifier of the SN 560. Then, the global DSF 540 may transmit (614), to the fourth data storage device 530 (i.e., the DSF 1 530), the address of the third data storage device 330 (i.e., the DSF 3 550). In some example embodiments, the first data storage device 310, the second data storage device 320 and the fourth data storage device may be the same device, for example, the DSF 1 530.

[0093]

[0087] In some example embodiments, in response to receiving the address of the DSF 3 550, the DSF 1 may transmit (616) the RACH report and the identifier of the SN 550 to the DSF 3 550.

[0094]

[0088] A process for RACH reporting between neighboring data storage devices will be described below with reference to FIG. 7. FIG. 7 illustrates a signaling diagram 700 for communication in accordance with some example embodiments of the present disclosure. In the signaling diagram 700, some steps such as 340-342, and 412 are similar to those in FIGs. 3-4, which will not be repeated here.

[0095]

[0089] In some example embodiments, in case of the DSF 1 530 is the first data storage device 320, the DSF 2 710 may be an example of the third data storage device 330; in case of the DSF 2 710 is the first data storage device 320, the DSF 1 530 may be an example of the second data storage device 320.

[0096]

[0090] In this process, the third data storage device (for example, the DSF 2 710) is associated with the second network node (i.e., the SN 560), and the first data storage device (for example, the DSF 1 530) is neighboring to the third data storage device. For example, the MN 520 may be in an area served by the DSF 1 530, and the SN 560 may be in an area served by the DSF 2 710, and the area served by the DSF 1 530 and the area served by the DSF 2 710 may be neighboring.

[0097]

[0091] In some example embodiments, the first data storage device 310 (for example, the DSF 2 710) receives, from the second network node 220 (i.e., the SN 560), a subscribing request for receiving an update of a RACH report. The RACH report is transmitted by a terminal device (for example, the UE 510) and corresponds to a cell controlled by the second network node 220 (the SN 560). Then, the DSF 2 710 may transmit a confirming message to the SN 560.

[0098]

[0092] In some example embodiments, the first data storage device 310 (for example, the DSF 1 530) determines (724) that the RACH report is to be transmitted to the second network node 220 (i.e., the SN 560). For example, the DSF 1 530 may determine that the RACH report is intended to be transmitted to a base station in a neighbor area of the area served by the DSF 1 530.

[0099]

[0093] In some example embodiments, the first data storage device 310 (for example, the DSF 1 530) transmits (726) the RACH report and the identifier to the third data storage device 330 (for example, the DSF 2 710). Then, the third data storage device 330 (for example, the DSF 2 710) transmits (728) the RACH report to the second network node 220 (i.e., the SN 560).

[0100]

[0094] In some example embodiments, the DSF herein may be implemented as a new entity specific for the RAN domain, or may be implemented as an entity such as an unstructured data storage function (UDSF) in the core network (CN) domain. In this case, the proposed solution may be implemented in a system where the gNB (for example, a control plane) is attached to the CN service-based interface (SBI). This allows gNBs to directly contact the UDSF without having to go through the access and mobility function. In some example embodiments, the DSF may be implemented as a storage function in (RAN) 0AM, ORAN RICs, or the like.

[0101]

[0095] Example processes for RACH reporting will be described in detail below with reference to FIG. 8-FIG. 11. Different cases where the DSF instances that the MN and SN access are either the same or different will be described with resulting procedures, and the global DSF may be potentially required to be communicated with. A key may be used to save and handle the RACH report.

[0102]

[0096] It can be assumed that a communication between a base station and a DSF instance takes place over an SBI. Alternatively, or in addition, the communication may be based on a point-to-point (P2P) stream control transmission protocol (SCTP) interface.

[0103]

[0097] As mentioned above, a hierarchical DSF architecture for storing and fetching the RACH report is proposed. It is assumed that one DSF instance covers a given fixed geographical area. For instance, this area may be a tracking area defined in a 5G system or a multitude thereof. RAN nodes (for example, gNBs) within this given area may only access the local DSF instance. In the hierarchical DSF architecture, a global DSF acts as a coordinator of the local DSF instances may be proposed.

[0104]

[0098] FIG. 8 illustrates a flowchart of an example intra-DSF communication in accordance with some example embodiments of the present disclosure. In this example, the UE 510 may be an example of the terminal device 226; the MN 520 may be an example of the first network node 210; the DSF 1 530 may be an example of the first data storage device 310; and the SN 560 may be an example of the second network node 220.

[0105]

[0099] It is assumed that both the MN 520 and the SN 560 are served by the DSF 1 530. At 810, the SN 560 subscribes to update regarding RACH reports of any of its cells with the DSF 1 530 in an initial step, for example, at the fire-up of the SN 560. The subscribing request sent by the SN 560 to the DSF 1 530 may comprise a cause (for example, the RACH report) and a key (for example, the identifier of the SN 560 such as an SN gNB ID).

[0106]

[0100] At 820, the DSF 1 530 replies with a confirmation message. At 830, the UE 510 transmits a RACH report to the MN 520, and after receiving the RACH report from the UE 510, at 840, the MN 520 reads the SN gNB ID from the header of the RACH report.

[0107]

[0101] In some example embodiments, a DSF instance may be able to receive a request for storing a RACH report of a UE with a given key, store the RACH report and respond to the requester with a proper cause value as well as handle the subscribing request for the RACH report. The DSF instance may interpret the key and notify the subscriber when a RACH report with the corresponding key is available. In addition, a key is required to store information into or fetch information from a DSF. The header of the RACH report sent by the UE to the new MN contains the gNB identifier (ID) of the old SN, and can be used as a DSF key. In an example, the key-value pair for the RACH report saved at the local DSF would be (SN gNB ID, RACH report).

[0108]

[0102] At 850, the MN 520 saves the RACH report to the DSF 1 530 using the SN gNB ID as a key. At 860, the DSF 1 530 may then notify the SN 560 with the RACH report.

[0109]

[0103] In some example embodiments, if the SN 560 and the DSF 1 530 are connected via a P2P interface, then the subscribing request may be replaced with an event triggered reporting message, whose parameters are similar to those of the subscribe message.

[0110]

[0104] FIG. 9 illustrates a flowchart of an example RACH report forwarding via the global DSF in accordance with some example embodiments of the present disclosure. In this example, the UE 510 may be an example of the terminal device 226; the MN 520 may be an example of the first network node 210; the DSF 1 530 may be an example of the first data storage device 310, or the second data storage device 310; the global DSF 540 may be an example of the first data storage device 310, the second data storage device 310, or the third data storage device 330; the DSF 3 550 may be an example of the first data storage device 310 or the third data storage device 330; and the SN 560 may be an example of the second network node 220.

[0111]

[0105] In this example, the MN 520 and the SN 560 are connected to different DSFs. The MN 520 is in an area served by the DSF 1 530, and the SN 560 is in an area served by the DSF 3 550, and the area served by the DSF 1 530 and the area served by the DSF 3 550 may not be neighboring. In this case, the global DSF 540 is introduced for forwarding the RACH report.

[0112]

[0106] The steps 910-918 are similar to 810-815 of FIG. 8, respectively, except that the SN 560 subscribes the RACH report to the DSF 3 550 and gets a responsive confirmation from the DSF 3 550 instead of the DSF 1 530. At 920, based on the SN gNB ID, the DSF 1 530 determines that the RACH report is not intended for gNBs in its area. At 922, the DSF 1 forwards the RACH report along with the key to the global DSF 540. It is assumed that the global DSF 540 has the full knowledge of the association between identifiers of the SNs and identifiers of DSFs, for example, the association between an SN gNB ID and a DSF ID. At 924, the global DSF 540 may determine the DSF to contact (the DSF 3 550 in this case) from the received key. At 926, the global DSF 540 then sends the RACH report and the key to the DSF 3 550. At 928, in response to receiving the RACH report and the key, the DSF 3 550 replies to the global DSF 540 an acknowledgement message. At 930, the DSF 3 550 notifies the SN 560 the RACH report.

[0113]

[0107] FIG. 10 illustrates a flowchart of an example of requesting the address of a local DSF instance from the global DSF in accordance with some example embodiments of the present disclosure.

[0114]

[0108] As shown in FIG. 10, the UE 510 may be an example of the terminal device 226; the MN 520 may be an example of the first network node 210; the DSF 1 530 may be an example of the first data storage device 310, or the second data storage device 310; the global DSF 540 may be an example of the first data storage device 310, the second data storage device 310, or the third data storage device 330; the DSF 3 550 may be an example of the first data storage device 310 or the third data storage device 330; and the SN 560 may be an example of the second network node 220.

[0115]

[0109] In this example, the MN 520 and the SN 560 are connected to different DSFs. The MN 520 is in an area served by the DSF 1 530, and the SN 560 is in an area served by the DSF 3 550, and the area served by the DSF 1 530 and the area served by the DSF 3 550 may not be neighboring. In this case, the global DSF 540 is introduced for forwarding the RACH report. It is to be noted that the steps 910-920 in FIG. 10 are similar to those of FIG. 9, respectively, which will not be repeated here.

[0116] [HO] In some example embodiments, as shown in FIG. 10, instead of forwarding the RACH report via the global DSF 540, at 1010, the DSF 1 530 sends the report key to the global DSF 540 with a request for the address of the DSF instance to contact. At 1020, the global DSF 540 may determine the address of the DSF instance to contact (i.e., the DSF 3 550 in this case) if the address is provided and a direct communication is authorized for the DSF 1 530 towards the DSF 3 550. At 1030, the global DSF 540 transmits the address of the DSF 3 550 to the DSF 1 530. After a successful response from the global DSF 540, at 1040, the DSF 1 530 may forward the RACH report and the key to the DSF 3 550. At 1050, in response to receiving the RACH report and the key, the DSF 3 550 may reply an acknowledgement message to the DSF 1 530. At 1060, the DSF 3 550 notifies the SN 560 the RACH report.

[0117]

[0111] According to the embodiments of the present disclosure, because the RACH report is sent directly to the desired DSF without going through an extra global DSF hop, the solution presented in FIG. 10 may reduce backhaul traffic.

[0118]

[0112] FIG. 11 illustrates a flowchart of an example of a RACH report directly forwarding to a neighbor DSF in accordance with some example embodiments of the present disclosure.

[0119]

[0113] As shown in FIG. 11, the UE 510 may be an example of the terminal device 226; the MN 520 may be an example of the first network node 210; the DSF 1 530 may be an example of the first data storage device 310 and / or the second data storage device 310; the DSF 2 710 may be an example of the first data storage device 310 or the third data storage device 330; and the SN 560 may be an example of the second network node 220.

[0120]

[0114] In this example, the MN 520 and the SN 560 are connected to different DSFs. The MN 520 is in an area served by the DSF 1 530, and the SN 560 is in an area served by the DSF 2 710. The DSF 1 530 and the DSF 2 710 are connected, and the area served by the DSF 1 530 and the area served by the DSF 2 710 may be neighboring. In this case, a local DSF instance may transmit the RACH report to a neighbor DSF instance directly. It is to be noted that the steps 1010-1150 in FIG. 11 are similar to 810-815 of FIG. 8, respectively, except that the SN 560 subscribes the RACH report to the DSF 2 710 and gets a responsive confirmation from the DSF 2 710 instead of from the DSF 1 530.

[0121]

[0115] In some example embodiments, a DSF may either be preconfigured with addresses of other neighboring local DSFs or may be configured accordingly during the operation of the network (for example, via the global DSF). Furthermore, a local DSF instance may be aware of the association between the SN gNB ID and the DSF ID for neighbor areas. At 1160, the DSF 1 530 determines that the RACH report is intended to be transmitted to a gNB served by the neighbor DSF 2 710. At 1170, the DSF 1 530 may directly contact the DSF 2 710 with the RACH report and the key. At 1180, in response to receiving the RACH report and the key, the DSF 2 710 may replay to the DSF 1 530 with an acknowledgement message. At 1190, the DSF 2 710 notifies the SN 560 the RACH report.

[0122]

[0116] In addition to the usage of the hierarchical DSF architecture as mentioned above, the shared and distributed hierarchical database architectures may be further used for many purposes, such as data retention, payload optimization on critical interfaces handling UEs, resiliency, or the like. Such an architecture has potential enablement in the RAN domain.

[0123]

[0117] FIG. 12 shows a flowchart of an example method 1200 implemented at the first data storage device 310 in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the first data storage device 310 in FIG. 3.

[0124]

[0118] At block 1210, receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node.

[0125]

[0119] At block 1220, determining that the RACH report is to be transmitted to a second network node.

[0126]

[0120] At block 1230, transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

[0127]

[0121] In some example embodiments, the first data storage device is associated with the second network node. The method 1200 further comprises: receiving, from the second network node, a subscribing request for receiving an update of a RACH report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node, wherein the RACH report is transmitted to the second network node in accordance with the received subscribing request.

[0128]

[0122] In some example embodiments, the second data storage device comprises at least one of a data storage device associated with the first network node, or a global data storage device.

[0129]

[0123] In some example embodiments, the method 1200 further comprises: in response to receiving the subscribing request, transmit, to the second network node, a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

[0130]

[0124] In some example embodiments, the subscribing request for the update of the RACH report comprises an identifier of the second network node. The method 1200 further comprises: determining, based on the identifier of the second network node, that the RACH report is to be transmitted to the second network node.

[0125] In some example embodiments, the RACH report is received by the first data storage device along with an identifier of the second network node.

[0131]

[0126] In some example embodiments, the RACH report is transmitted by the first data storage device along with an identifier of the second network node.

[0132]

[0127] In some example embodiments, the third data storage device is associated with the second network node, and the first data storage device is neighboring to the third data storage device.

[0133]

[0128] In some example embodiments, the first data storage device is a global data storage device.

[0134]

[0129] In some example embodiments, the method 1200 further comprises: receiving, from a fourth data storage device, a request for an address of the third data storage device; and transmitting, to the fourth data storage device, the address of the third data storage device.

[0135]

[0130] In some example embodiments, the first data storage device is associated with the first network node, and the third data storage device is associated with the second network node. The method 1200 further comprises: transmitting, to a global data storage device, a request for an address of the third data storage device; and receiving, from the global data storge device, the address of the third data storage device.

[0136]

[0131] In some example embodiments, the method 1200 further comprises: storing the received RACH report.

[0137]

[0132] In some example embodiments, the method 1200 further comprises: storing the received subscribing request, wherein the subscribing request is used for subscription, get notification, event monitoring, or detection of the update of the RACH report.

[0138]

[0133] FIG. 13 shows a flowchart of an example method 1300 implemented at the first network node 210 in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the first network node 210 in FIG. 3.

[0139]

[0134] At block 1310, receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node.

[0140]

[0135] At block 1320, obtaining an identifier of the second network node.

[0136] At block 1330, transmitting the RACH report and the identifier of the second network node to a data storage device.

[0141]

[0137] In some example embodiments, the identifier of the second network node is read from a header of the RACH report.

[0142]

[0138] FIG. 14 shows a flowchart of an example method 1400 implemented at the second network node 220 in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1400 will be described from the perspective of the second network node 220 in FIG. 3.

[0143]

[0139] At block 1410, transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node.

[0144]

[0140] At block 1410, receiving, in accordance with the subscribed request, the RACH report from the first data storage device.

[0145]

[0141] In some example embodiments, the method 1400 further comprises: in response to transmitting the subscribing request, receive a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

[0146]

[0142] In some example embodiments, the subscribing request for the update of the RACH report comprises an identifier of the second network node.

[0147]

[0143] In some example embodiments, a first apparatus capable of performing any of the method 1200 (for example, the first data storage device 310 in FIG. 3 may comprise means for performing the respective operations of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first data storage device 310 in FIG. 3.

[0148]

[0144] In some example embodiments, the first apparatus comprises means for receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by at least one of the first data storage device or the second data storage device; means for determining that the RACH report is to be transmitted to a second network node; and means for transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

[0149]

[0145] In some example embodiments, the first data storage device is associated with the second network node. The first apparatus comprises means for receiving, from the second network node, a subscribing request for receiving an update of a RACH report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node, wherein the RACH report is transmitted to the second network node in accordance with the received subscribing request.

[0150]

[0146] In some example embodiments, the second data storage device comprises at least one of a data storage device associated with the first network node, or a global data storage device.

[0151]

[0147] In some example embodiments, the first apparatus comprises means for, in response to receiving the subscribing request, transmitting, to the second network node, a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

[0152]

[0148] In some example embodiments, the subscribing request for the update of the RACH report comprises an identifier of the second network node. The first apparatus comprises means for determining, based on the identifier of the second network node, that the RACH report is to be transmitted to the second network node.

[0153]

[0149] In some example embodiments, the RACH report is received by the first data storage device along with an identifier of the second network node.

[0154]

[0150] In some example embodiments, the RACH report is transmitted by the first data storage device along with an identifier of the second network node.

[0155]

[0151] In some example embodiments, the third data storage device is associated with the second network node, and the first data storage device is neighboring to the third data storage device.

[0156]

[0152] In some example embodiments, the first data storage device is a global data storage device.

[0157]

[0153] In some example embodiments, the first apparatus comprises means for receiving, from a fourth data storage device, a request for an address of the third data storage device; and means for transmitting, to the fourth data storage device, the address of the third data storage device.

[0158]

[0154] In some example embodiments, the first data storage device is associated with the first network node, and the third data storage device is associated with the second network node. The first apparatus comprises means for transmitting, to a global data storage device, a request for an address of the third data storage device; and means for receiving, from the global data storge device, the address of the third data storage device.

[0159]

[0155] In some example embodiments, the first apparatus comprises means for storing the received RACH report.

[0160]

[0156] In some example embodiments, the first apparatus comprises means for storing the received subscribing request, wherein the subscribing request is used for subscription, get notification, event monitoring, or detection of the update of the RACH report.

[0161]

[0157] In some example embodiments, a second apparatus capable of performing any of the method 1300 (for example, the first network node 210 in FIG. 3 may comprise means for performing the respective operations of the method 1300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the first network node 210 in FIG. 3.

[0162]

[0158] In some example embodiments, the second apparatus comprises means for means for receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; means for obtaining an identifier of the second network node; and means for transmitting the RACH report and the identifier of the second network node to a data storage device.

[0163]

[0159] In some example embodiments, the identifier of the second network node is read from a header of the RACH report.

[0164]

[0160] In some example embodiments, a third apparatus capable of performing any of the method 1400 (for example, the second network node 220 in FIG. 3 may comprise means for performing the respective operations of the method 1400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second network node 220 in FIG. 3.

[0161] In some example embodiments, a third apparatus comprises means for transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and means for, receiving, in accordance with the subscribed request, the RACH report from the first data storage device.

[0165]

[0162] In some example embodiments, the third apparatus comprises means for, in response to transmitting the subscribing request, receiving a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

[0166]

[0163] In some example embodiments, the subscribing request for the update of the RACH report comprises an identifier of the second network node.

[0167]

[0164] FIG. 15 is a simplified block diagram of a device 1500 that is suitable for implementing example embodiments of the present disclosure. The device 1500 may be provided to implement a communication device, for example, the first data storage device 310, the second data storage device 320, the first network node 210, the second network node 220, the third data network node 330, or the terminal device 226 as shown in FIG. 3. As shown, the device 1500 includes one or more processors 1510, one or more memories 1520 coupled to the processor 1510, and one or more communication modules 1540 coupled to the processor 1510.

[0168]

[0165] The communication module 1540 is for bidirectional communications. The communication module 1540 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1540 may include at least one antenna.

[0169]

[0166] The processor 1510 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1500 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0167] The memory 1520 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1524, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1522 and other volatile memories that will not last in the power-down duration.

[0170]

[0168] A computer program 1530 includes computer executable instructions that are executed by the associated processor 1510. The instructions of the program 1530 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1530 may be stored in the memory, e.g., the ROM 1524. The processor 1510 may perform any suitable actions and processing by loading the program 1530 into the RAM 1522.

[0171]

[0169] The example embodiments of the present disclosure may be implemented by means of the program 1530 so that the device 1500 may perform any process of the disclosure as discussed with reference to FIG. 1 to FIG. 14. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0172]

[0170] In some example embodiments, the program 1530 may be tangibly contained in a computer readable medium which may be included in the device 1500 (such as in the memory 1520) or other storage devices that are accessible by the device 1500. The device 1500 may load the program 1530 from the computer readable medium to the RAM 1522 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0173]

[0171] FIG. 16 shows an example of the computer readable medium 1600 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1600 has the program 1530 stored thereon.

[0174]

[0172] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0175]

[0173] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non- transitory computer readable medium. The computer program product includes computerexecutable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0176]

[0174] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0177]

[0175] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0176] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0178]

[0177] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

[0179]

[0178] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A first data storage device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first data storage device at least to: receive a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; determine that the RACH report is to be transmitted to a second network node; and transmit the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

2. The first data storage device of claim 1, wherein the first data storage device is associated with the second network node, and the at least one memory and the at least one processor further cause the first data storage device to: receive, from the second network node, a subscribing request for receiving an update of a RACH report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node, wherein the RACH report is transmitted to the second network node in accordance with the received subscribing request.

3. The first data storage device of claim 2, wherein the second data storage device comprises at least one of a data storage device associated with the first network node, or a global data storage device.

4. The first data storage device of claim 2 or 3, wherein the at least one memory and the at least one processor further cause the first data storage device to:in response to receiving the subscribing request, transmit, to the second network node, a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

5. The first data storage device of any of claims 2-4, wherein the subscribing request for the update of the RACH report comprises an identifier of the second network node, and the at least one memory and the at least one processor further cause the first data storage device to: determine, based on the identifier of the second network node, that the RACH report is to be transmitted to the second network node.

6. The first data storage device of claim 1, wherein the RACH report is received by the first data storage device along with an identifier of the second network node.

7. The first data storage device of claim 1, wherein the RACH report is transmitted by the first data storage device along with an identifier of the second network node.

8. The first data storage device of claim 1, wherein the first data storage device is a global data storage device.

9. The first data storage device of claim 8, wherein the at least one memory and the at least one processor further cause the first data storage device to: receive, from a fourth data storage device, a request for an address of the third data storage device; and transmit, to the fourth data storage device, the address of the third data storage device.

10. The first data storage device of claim 1, wherein the first data storage device is associated with the first network node, and the third data storage device is associated with the second network node, and the at least one memory and the at least one processorfurther cause the first data storage device to: transmit, to a global data storage device, a request for an address of the third data storage device; and receive, from the global data storge device, the address of the third data storage device.

11. The first data storage device of claim 1, wherein the at least one memory and the at least one processor further cause the first data storage device to: store the received RACH report.

12. The first data storage device of claim 2, wherein the at least one memory and the at least one processor further cause the first data storage device to: store the received subscribing request, wherein the subscribing request is used for subscription, get notification, event monitoring, or detection of the update of the RACH report.

13. A first network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network node at least to: receive a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; obtain an identifier of the second network node; and transmit the RACH report and the identifier of the second network node to a data storage device.

14. The first network node of claim 13, wherein the identifier of the second network node is read from a header of the RACH report.

15. A second network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network node at least to: transmit, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and receive, in accordance with the subscribing request, the RACH report from data storage device.

16. The second network node of claim 15, wherein the at least one memory and the at least one processor further cause the second network node to: in response to transmitting the subscribing request, receive a response comprising of at least one of an acknowledgement of the subscribing request or failure of the subscribing request.

17. The second network node of claim 15 or 16, wherein the subscribing request for receiving the update of the RACH report comprises an identifier of the second network node.

18. A method comprising: receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; determining that the RACH report is to be transmitted to a second network node; and transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

19. A method comprising: receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; obtaining an identifier of the second network node; and transmitting the RACH report and the identifier of the second network node to a data storage device.

20. A method comprising: transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and receiving, in accordance with the subscribing request, the RACH report from the first data storage device.

21. A first apparatus comprising: means for receiving a random access channel (RACH) report from at least one of a first network node or a second data storage device, the RACH report being transmitted by a terminal device within an area served by the first network node; means for determining that the RACH report is to be transmitted to a second network node; and means for transmitting the RACH report to at least one of the second network node or a third data storage device associated with the second network node.

22. A second apparatus comprising: means for receiving a random access channel (RACH) report from a terminal device within a cell controlled by the first network node, the RACH report corresponding to a second network node; means for obtaining an identifier of the second network node; andmeans for transmitting the RACH report and the identifier of the second network node to a data storage device.

23. A third apparatus comprising: means for transmitting, to a first data storage device, a subscribing request for receiving an update of a random access channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by the second network node; and means for receiving, in accordance with the subscribing request, the RACH report from the first data storage device.

24. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of any of the claims 18 to 20.

Images