Random Access Channel Report

Abstract

Example embodiments of this disclosure relate to apparatus, methods, and computer-readable media for Random Access Channel (RACH) reporting. In one 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 the area served by the first network node. The first data storage device determines that the RACH report will 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

Technical Field

[0001] Various exemplary embodiments of this disclosure are generally related to the telecommunications field, and more particularly to apparatus, methods and computer-readable media for reporting Random Access Channel (RACH). Background Technology

[0002] RACH reporting is a technique used in mobile communication systems to track and report the performance and status of random access channels. Random access channels are used for initial access and connection reconstruction between user equipment (UE) and base stations. Summary of the Invention

[0003] In a first aspect of this disclosure, a first data storage device is provided. The first data storage device includes: 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 to at least: 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 will be transmitted to the 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.

[0004] In a second aspect of this disclosure, a first network node is provided. The first network node includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first network node to at least: 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.

[0005] In a third aspect of this disclosure, a second network node is provided. The second network node includes 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 to at least: transmit a subscription request to a first data storage device for receiving updates of a Random Access Channel (RACH) report transmitted by a terminal device and corresponding to a cell controlled by the second network node; and receive the RACH report from the first data storage device according to the subscription request.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: 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 will 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.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving a Random Access Channel (RACH) report from a terminal device within a cell controlled by a 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.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: transmitting to a first data storage device a subscription request for receiving updates to a Random Access Channel (RACH) report, the RACH report being transmitted by a terminal device and corresponding to a cell controlled by a second network node; and receiving the RACH report from the first data storage device according to the subscription request.

[0009] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components 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; components for determining that the RACH report will be transmitted to the second network node; and components 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.

[0010] In an eighth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components 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; components for obtaining an identifier of the second network node; and components for transmitting the RACH report and the identifier of the second network node to a data storage device.

[0011] In a ninth aspect of this disclosure, a third apparatus is provided. The third apparatus includes: components for transmitting to a first data storage device a subscription request for receiving updates of a Random Access Channel (RACH) report transmitted by a terminal device and corresponding to a cell controlled by a second network node; and components for receiving the RACH report from the first data storage device according to the subscription request.

[0012] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to a fourth aspect.

[0013] In the eleventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the fifth aspect.

[0014] In a twelfth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the sixth aspect.

[0015] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example structure of a network node according to some example embodiments of this disclosure is shown; Figure 2 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 3 Signaling diagrams for communication according to some example embodiments of the present disclosure are shown; Figure 4 Signaling diagrams for communication according to some example embodiments of the present disclosure are shown; Figure 5 Signaling diagrams for communication according to some example embodiments of the present disclosure are shown; Figure 6 Signaling diagrams for communication according to some example embodiments of the present disclosure are shown; Figure 7 Signaling diagrams for communication according to some example embodiments of the present disclosure are shown; Figure 8 A flowchart illustrating example intra-DSF communication according to some example embodiments of this disclosure is shown; Figure 9 A flowchart illustrating example RACH report forwarding via a global DSF according to some example embodiments of this disclosure is shown; Figure 10 A flowchart illustrating an example of requesting the address of a local DSF instance from a global DSF according to some example embodiments of this disclosure; Figure 11A flowchart illustrating an example of direct forwarding of RACH reports to adjacent DSFs according to some exemplary embodiments of this disclosure is shown; Figure 12 A flowchart is shown illustrating an example method implemented at a first data storage device according to some example embodiments of the present disclosure; Figure 13 A flowchart is shown illustrating an example method implemented at a first network node according to some example embodiments of the present disclosure; Figure 14 A flowchart is shown illustrating an example method implemented at a second network node according to some example embodiments of the present disclosure; Figure 15 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 16 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0017] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0018] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

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

[0020] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments, whether explicitly described or not, to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0021] It should be understood that although terms such as "first," "second," etc., preceding nouns 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 restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0022] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0023] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary 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, when used herein, the terms “comprise,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of a feature, element, and / or component, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0025] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device such as a mobile phone or server to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or a portion thereof) that require software (e.g., firmware) to operate, but may not exist when the software is not required to operate.

[0026] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term "circuit" also covers implementations of hardware circuitry or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware. For instance, where applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0027] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.

[0028] As used herein, the term "network device" or "network node" refers to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio header (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node (such as a femto, pico, or non-terrestrial network (NTN)) or non-terrestrial network equipment (such as satellite network equipment), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network equipment, etc. In some example embodiments, the radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB host node. An IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE toward the parent node, and a DU portion that behaves as a base station toward the next-hop IAB node.

[0029] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0030] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0031] RACH reports can be used in the context of dual connectivity (DC) and carrier aggregation (CA). User equipment (UE) can have RACH reports corresponding to the primary and secondary cells (PScells) controlled by the secondary node (SN). RACH reports can provide various statistics and performance indicators about the random access channel, such as RACH attempt count, RACH success count, RACH collision count, and RACH delay.

[0032] Figure 1 Example structures of network nodes according to some exemplary embodiments of this disclosure are shown. For example... Figure 1 As shown, master node (MN) 102 can inform SN 2 106 that its level 1 connection consists of node SN 1 104, and its level 2 connection consists of SN 3 108 and SN 4 110. Similarly, SN 2 106 can inform MN 102 that its level 1 connection consists of nodes SN 5 112 and SN 6 114. Using this information, if MN 102 needs to transmit a RACH report to any of the nodes SN 3 108 to SN 6 114, MN 102 can reach SN 3 108 to SN 6 114 via an appropriate path (such as via SN 1 104 or SN 2 106).

[0033] Currently, the issue of how to forward RACH reports remains unclear in some scenarios. For example, a UE might be allowed to provide RACH reports over a long period of time. During this period, the UE may have switched to a different Radio Access Network (RAN) notification area or even a new MN in a different city. Accordingly, communication is no longer in dual-connectivity mode. Optionally, the UE can report the PScell ​​or a list of PScells corresponding to the RACH report to the MN. The new MN to which the UE is now connected may not have an existing connection to the old SN corresponding to the RACH report, so it is unclear how the RACH report should be forwarded.

[0034] Furthermore, if the MN retrieving the RACH report is not connected to any SN associated with the PSCell received along with the RACH report, it will be investigated whether and how the RACH report is forwarded. Additionally, the forwarding of the RACH report on the NG and S1 interfaces can be disregarded to avoid overloading the NG interface and negatively impacting the throughput and Quality of Service (QoS) of the interfaces provided to the UE. It should be noted that the RACH report is expected at the older SN because it can be used to summarize statistics and optimize the access procedures for its cells.

[0035] An example embodiment of this disclosure presents a RACH reporting scheme. Using this scheme, a first network node (e.g., MN) and / or a second data storage device transmits a RACH report to the first data storage device. The first data storage device determines that the RACH report will be transmitted to the second network node (e.g., SN). The first data storage device then transmits the RACH report to the second network node and / or a third data storage device associated with the second network node. For example, the data storage device including the first, second, or third data storage device can be a Local Data Storage Function (DSF) instance or a global DSF instance.

[0036] According to the proposed scheme, data storage devices are incorporated into the RACH reporting scheme. In this way, RACH reports can be transmitted via data storage devices, thereby avoiding the loss of RACH reports.

[0037] The exemplary embodiments will now be discussed in detail with reference to the accompanying drawings. Figure 2 An example communication environment 200 in which example embodiments of the present disclosure may be implemented is shown.

[0038] like Figure 2 As shown, the communication environment 200 includes data storage device 240, data storage device 250, data storage device 260, and global data storage device 270. For example, data storage device 240, data storage device 250, or data storage device 260 may be a local DSF instance (also known as a DSF). Global data storage device 270 may be, for example, a global DSF instance (also known as a global DSF).

[0039] In communication environment 200, one or more first network nodes (e.g., first network node 210) and one or more second network nodes (e.g., second network node 220) are located in area 230 served by data storage device 240. Terminal device 226 can communicate with first network node 210. For example, terminal device 226 can operate as a user equipment. Similarly, one or more first network nodes and one or more second network nodes (e.g., second network node 222) are located in area 232 served by data storage device 250. One or more first network nodes and one or more second network nodes (e.g., second network node 224) are located in area 234 served by data storage device 260. For example, a first network node (such as first network node 210) can operate as a master node, and a second network node (such as second network node 220) can operate as a slave node.

[0040] In some example embodiments, region 230 served by data storage device 240 and region 232 served by data storage device 250 are adjacent, and data storage devices 240 and 250 are connected. Similarly, region 232 served by data storage device 250 and region 234 served by data storage device 260 are also adjacent, and data storage devices 250 and 260 are connected.

[0041] like Figure 2 As shown, data storage devices 240, 250, and 260 are all connected to the global data storage device 270. Because data storage devices 240 and 260 are not directly connected to each other, they cannot communicate directly. Therefore, communication between data storage devices 240 and 260 can be performed through the global data storage device 270.

[0042] It should be understood that, for the purpose of explanation, Figure 2 The quantity and type of devices, equipment, or areas are shown without implying any limitations. For example, communications environment 200 may include any suitable number of data storage devices, global data storage devices, user equipment, areas, and network nodes.

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

[0044] In some example embodiments, the operations described relative to the terminal device may be implemented at a network node or other device, and the operations described relative to the network node may be implemented at the terminal device or other device.

[0045] Communication in communication environment 200 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including 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 Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0046] Now for reference Figure 3 This illustrates signaling diagram 300 for communication according to some example embodiments of the present disclosure. For example... Figure 3 As shown, signaling diagram 300 relates to a first network node 210, a second network node 220, and a terminal device 226 in a communication environment 200. For example, the first network node 210 may include an MN, and the second network node 220 may include an SN. The terminal device 226 may include a UE.

[0047] Signaling diagram 300 also relates to 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 include at least one of data storage devices 240, 250, or 260 or a global data storage device 270.

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

[0049] In some example embodiments, the first network node 210 obtains (342) the 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 a received RACH report, or by receiving the identifier of the second network node 220 from the terminal device 226.

[0050] Then, the first network node 210 transmits the RACH report and the identifier of the second network node 220 to the 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.

[0051] The second network node 220 transmits (344) a subscription request to the first data storage device 310 for receiving updates to the RACH report. The RACH report is transmitted by the terminal device and corresponds to a cell controlled by the second network node 220. For example, the subscription request may include a reason (i.e., the RACH report) and a key that may be an identifier of the second network node 220.

[0052] 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 the terminal device within the 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 include at least one of a data storage device associated with the first network node or a global data storage device. The first data storage device then determines (350) that the RACH report will be transmitted to the second network node 220.

[0053] Then, the first data storage device 310 transmits a (352) RACH report to the second network node 220 and / or transmits a (354) 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. Therefore, based on the subscription request from the second network node 220 to the first data storage device 310, the second network node receives a (352) RACH report from the first data storage device 310.

[0054] The embodiments disclosed herein are based on a hierarchical DSF architecture. A subscription-notification process is introduced between the data storage device and the second network node, allowing the second network node to receive RACH reports when they become available, thereby saving RACH reports and reducing communication hops used to transmit RACH reports.

[0055] The following will refer to Figure 4Describes the process for RACH reporting in scenarios within data storage devices. Figure 4 Signaling diagram 400 for communication is shown according to some example embodiments of the present disclosure. For example... Figure 4 As shown, signaling diagram 400 relates to a first network node 210, a second network node 220, and a first data storage device 320 in a communication environment 200. In this case, both the first network node 210 and the second network node 220 can be in the area served by the first data storage device 320.

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

[0057] In some example embodiments, in response to receiving a subscription request from the second network node 220, the first data storage device 320 may transmit (410) a response to the second network node 220, the response including at least one of acknowledgment of the subscription request or failure of the subscription request. For example, acknowledgment of the subscription request may be a confirmation message for the subscription request. In this way, upon receiving the confirmation message from the first storage device 320, the second network node 220 will know that the subscription request has been accepted.

[0058] In some example embodiments, a first network node 210 receives (340) a RACH report from a terminal device 226 located in a cell / area controlled by the first network node 210. The first network node 210 then obtains (342) the identifier of a 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 a first data storage device 320.

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

[0060] The following will refer to Figure 5 Describes the process used for RACH reporting via the global DSF. Figure 5 Signaling diagram 500 for communication is shown according to some example embodiments of the present disclosure. In signaling diagram 500, some steps such as 344-352, 410-412 are similar to... Figure 3 and Figure 4 The steps mentioned earlier will not be repeated here.

[0061] like Figure 5 As shown, signaling diagram 500 involves UE 510, MN 520, DSF 1 530, global DSF 540, DSF 3 550, and SN 560. UE 510 may be an example of terminal device 226; MN 520 may be an example of first network node 210; DSF1 530, global DSF 540, and DSF 3 550 may each be an example of first data storage device 320. In some example embodiments, when DSF 1 is the first data storage device 320, global DSF 540 may be an example of third data storage device 330; when global DSF 540 is the first data storage device 320, DSF 3 550 may be an example of third data storage device 330.

[0062] In this process, MN 520 can be in an area served by DSF 1 530, and SN 560 can be in an area served by DSF 3 550, and the areas served by DSF 1 530 and DSF 3 550 do not need to be adjacent. In some example embodiments, the DSF instance can contact the global DSF or other local DSFs to forward reports when necessary. Therefore, a global DSF 540 is introduced in this scenario so that RACH reports can be forwarded via the global DSF 540.

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

[0064] In some example embodiments, when it is determined that a RACH report should be transmitted to SN 560, DSF 1 530 may transmit (572) the RACH report and the identifier of SN 560 to global DSF 540.

[0065] In some example embodiments, global DSF 540 determines (574) that a RACH report will be transmitted to SN 560. For example, global DSF 540 may determine the DSF to be contacted based on the identifier of SN 560. Then, global DSF 540 transmits (576) the RACH report and the identifier to DSF 3550.

[0066] The following will refer to Figure 6 Describes the process of generating a RACH report based on an address requested from the global DSF. Figure 6 Signaling diagram 600 for communication is shown according to some example embodiments of the present disclosure. In signaling diagram 600, some steps such as 344-352, 410-412, and 570-572 are similar to Figures 3 to 5 The steps mentioned earlier will not be repeated here.

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

[0068] In this process, MN 520 can be in the area served by DSF 1 530, and SN 560 can be in the area served by DSF 3 550, and the areas served by DSF 1 530 and DSF 3 550 do not need to be adjacent. Therefore, a global DSF 540 is introduced in this scenario, enabling the forwarding of RACH reports via the global DSF 540.

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

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

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

[0072] The following will refer to Figure 7 Describes the process for RACH reporting between adjacent data storage devices. Figure 7 A signaling diagram 700 for communication is shown according to some example embodiments of the present disclosure. In signaling diagram 700, some steps such as 340-342 and 412 are similar to... Figure 3-4 The steps mentioned earlier will not be repeated here.

[0073] In some example embodiments, DSF 2 710 may be an example of a third data storage device 330 when DSF 1 530 is a first data storage device 320; and DSF 1 530 may be an example of a second data storage device 320 when DSF 2 710 is a first data storage device 320.

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

[0075] In some example embodiments, the first data storage device 310 (e.g., DSF 2 710) receives a subscription request from the second network node 220 (i.e., SN 560) for receiving updates to RACH reports. RACH reports are transmitted by terminal devices (e.g., UE 510) and correspond to cells controlled by the second network node 220 (SN 560). DSF 2 710 can then transmit an acknowledgment message to SN 560.

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

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

[0078] In some example embodiments, the DSF described herein can be implemented as a new entity specific to the RAN domain, or it can be implemented as an entity such as the Unstructured Data Storage Function (UDSF) in the Core Network (CN) domain. In this case, the proposed solution can be implemented in a system where a gNB (e.g., the control plane) is attached to a CN Service-Based Interface (SBI). This allows the gNB to directly contact the UDSF without going through access and mobility functions. In some example embodiments, the DSF can be implemented as a storage function in (RAN)OAM, ORAN RIC, etc.

[0079] The following will refer to Figures 8 to 11 A sample procedure for RACH reporting is described in detail. Different scenarios, such as MN and SN accessing the same or different DSF instances, will be described along with the resulting procedure, and may potentially require communication with the global DSF. Keys can be used to save and process RACH reports.

[0080] It can be assumed that communication between the base station and the DSF instance occurs on the SBI. Alternatively or additionally, communication may be based on a point-to-point (P2P) Flow Control Transport Protocol (SCTP) interface.

[0081] As described above, a hierarchical DSF architecture for storing and retrieving RACH reports is proposed. It is assumed that a DSF instance covers a given fixed geographical area. For example, this area could be a tracking area defined in a 5G system or multiple such areas. RAN nodes (e.g., gNBs) within this given area can access only the local DSF instance. In the hierarchical DSF architecture, a global DSF can be proposed to act as the coordinator for the local DSF instances.

[0082] Figure 8 A flowchart illustrating example intra-DSF communication according to some example embodiments of the present disclosure is shown. In this example, UE 510 may be an example of terminal device 226; MN 520 may be an example of first network node 210; DSF 1 530 may be an example of first data storage device 310; and SN 560 may be an example of second network node 220.

[0083] Assume that both MN 520 and SN 560 are served by DSF 1 530. At 810, SN 560 subscribes to RACH report updates about any of its cells from DSF 1 530 during the initial steps (e.g., at SN 560's startup). The subscription request transmitted by SN 560 to DSF 1 530 may include a reason (e.g., RACH report) and a key (e.g., SN 560's identifier, such as the SNgNB ID).

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

[0085] In some example embodiments, the DSF instance may be able to receive requests to store a RACH report of the UE using a given key, store the RACH report and respond to the requester with an appropriate reason value, and process subscription requests for the RACH report. The DSF instance can interpret the key and notify the subscriber when a RACH report with the corresponding key is available. Additionally, a key is required to store information in or retrieve information from the DSF. The header of the RACH report transmitted by the UE to the new MN contains the gNB identifier (ID) of the old SN and can be used as the DSF key. In the example, the key-value pair of the RACH report stored in the local DSF would be (SN gNBID, RACH report).

[0086] At 850, MN 520 saves the RACH report to DSF 1 530 using the SN gNB ID as the key. At 860, DSF 1 530 can then notify SN 560 of the RACH report.

[0087] In some example embodiments, if SN 560 and DSF 1 530 are connected via a P2P interface, the subscription request can be replaced with an event-triggered report message with parameters similar to those of the subscription message.

[0088] Figure 9A flowchart illustrating example RACH report forwarding via a global DSF according to some example embodiments of this disclosure is shown. In this example, UE 510 may be an example of terminal device 226; MN 520 may be an example of first network node 210; DSF 1 530 may be an example of first data storage device 310 or second data storage device 310; global DSF 540 may be an example of first data storage device 310, second data storage device 310 or third data storage device 330; DSF 3 550 may be an example of first data storage device 310 or third data storage device 330; and SN 560 may be an example of second network node 220.

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

[0090] Steps 910-918 are similar to Figure 8 In steps 810-815, SN 560 subscribes to RACH reports from DSF 3 550 and receives response confirmation from DSF 3 550 instead of DSF 1 530. At step 920, based on the SN gNB ID, DSF 1 530 determines that the RACH report is not intended for a gNB in ​​its area. At step 922, DSF 1 forwards the RACH report along with the key to global DSF 540. It is assumed that global DSF 540 fully understands the association between the SN's identifier and the DSF's identifier, e.g., the association between the SN gNBID and the DSF ID. At step 924, global DSF 540 can determine from the received key which DSF to contact (in this case, DSF 3 550). At step 926, global DSF 540 then transmits the RACH report and key to DSF 3 550. At 928, in response to receiving the RACH report and key, DSF 3 550 replies with an acknowledgment message to global DSF 540. At 930, DSF 3550 notifies SN 560 of the RACH report.

[0091] Figure 10 A flowchart illustrating an example of requesting the address of a local DSF instance from a global DSF according to some example embodiments of this disclosure is shown.

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

[0093] In this example, MN 520 and SN 560 are connected to different DSFs. MN 520 is in an area served by DSF 1 530, and SN 560 is in an area served by DSF 3 550. The areas served by DSF 1 530 and DSF 3 550 may not be adjacent. In this case, a global DSF 540 is introduced for forwarding RACH reports. It should be noted that... Figure 10 Steps 910-920 in the text are respectively similar to Figure 9 The steps will not be repeated here.

[0094] In some example embodiments, such as Figure 10 As shown, instead of forwarding the RACH report via global DSF 540, at 1010, DSF 1 530 transmits the report key along with a request for the address of the DSF instance to be contacted to global DSF 540. At 1020, global DSF 540 can determine the address of the DSF instance to be contacted (i.e., DSF 3 550 in this case), if that address is provided and direct communication from DSF 1 530 to DSF 3 550 is authorized. At 1030, global DSF 540 transmits the address of DSF 3 550 to DSF 1 530. After a successful response from global DSF 540, at 1040, DSF 1 530 can forward the RACH report and key to DSF 3 550. At 1050, in response to receiving the RACH report and key, DSF 3 550 can reply with an acknowledgment message to DSF 1 530. At 1060, DSF 3 550 notifies SN 560 of the RACH report.

[0095] According to embodiments of this disclosure, because the RACH report is transmitted directly to the desired DSF without additional global DSF hops, Figure 10 The solutions presented can reduce backhaul traffic.

[0096] Figure 11A flowchart illustrating an example of direct forwarding of RACH reports to neighboring DSFs according to some example embodiments of this disclosure is shown.

[0097] like Figure 11 As shown, UE 510 may be an example of terminal device 226; MN 520 may be an example of first network node 210; DSF 1 530 may be an example of first data storage device 310 and / or second data storage device 310; DSF 2710 may be an example of first data storage device 310 or third data storage device 330; and SN 560 may be an example of second network node 220.

[0098] In this example, MN 520 and SN 560 are connected to different DSFs. MN 520 is in an area served by DSF 1 530, and SN 560 is in an area served by DSF 2 710. DSF 1 530 and DSF 2 710 are connected, and the areas served by DSF 1 530 and DSF 2 710 can be adjacent. In this case, the local DSF instance can directly transmit RACH reports to the adjacent DSF instance. It should be noted that... Figure 11 Steps 1010-1150 in the text are respectively similar to Figure 8 810-815, except that SN 560 subscribes to RACH reports from DSF 2 710 and receives response confirmation from DSF 2 710 instead of DSF 1 530.

[0099] In some example embodiments, the DSF may be pre-configured with the addresses of other neighboring local DSFs, or may be configured accordingly during network operation (e.g., via a global DSF). Furthermore, the local DSF instance may know the association between the SN gNB ID and the DSF IDs of neighboring areas. At 1160, DSF 1 530 determines that the RACH report is intended to be transmitted to the gNB served by the neighboring DSF 2 710. At 1170, DSF 1 530 may directly contact DSF 2 710 using the RACH report and key. At 1180, in response to receiving the RACH report and key, DSF 2 710 may reply with an acknowledgment message to DSF 1 530. At 1190, DSF 2 710 notifies SN 560 of the RACH report.

[0100] In addition to using the hierarchical DSF architecture described above, shared and distributed hierarchical database architectures can be used for many purposes, such as data retention, payload optimization on critical interfaces for processing UEs, and resiliency. This architecture has potential implementations in the RAN domain.

[0101] Figure 12 A flowchart of an example method 1200 implemented at a first data storage device 310 according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 3 Angle description method 1200 for the first data storage device 310 in the middle.

[0102] At box 1210, a random access channel (RACH) report is received 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 the area served by the first network node.

[0103] At box 1220, determine that a RACH report will be transmitted to the second network node.

[0104] At box 1230, a RACH report is transmitted to at least one of the second network node or the third data storage device associated with the second network node.

[0105] In some example embodiments, the first data storage device is associated with a second network node. Method 1200 further includes receiving from the second network node a subscription request for receiving updates to a RACH report transmitted by a terminal device and corresponding to a cell controlled by the second network node, wherein the RACH report will be transmitted to the second network node according to the received subscription request.

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

[0107] In some example embodiments, method 1200 further includes: in response to receiving a subscription request, transmitting to a second network node a response including at least one of an acknowledgment of the subscription request or a failure of the subscription request.

[0108] In some example embodiments, the subscription request for an update to the RACH report includes an identifier of the second network node. Method 1200 further includes determining, based on the identifier of the second network node, that the RACH report will be transmitted to the second network node.

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

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

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

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

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

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

[0115] In some example embodiments, method 1200 further includes storing the received RACH report.

[0116] In some example embodiments, method 1200 further includes: storing the received subscription request, wherein the subscription request is used to subscribe to, receive notifications, monitor events, or detect RACH report updates.

[0117] Figure 13 A flowchart of an example method 1300 implemented at a first network node 210 according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 3 Method 1300 is described from the perspective of the first network node 210 in the network.

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

[0119] At box 1320, obtain the identifier of the second network node.

[0120] At box 1330, the RACH report and the identifier of the second network node are transmitted to the data storage device.

[0121] In some example implementations, the identifier of the second network node is read from the header of the RACH report.

[0122] Figure 14 A flowchart of an example method 1400 implemented at a second network node 220 according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 3 Method 1400 is described from the perspective of the second network node 220 in the network.

[0123] At box 1410, a subscription request for receiving updates of random access channel (RACH) reports transmitted by a terminal device and corresponding to a cell controlled by a second network node is transmitted to a first data storage device.

[0124] At box 1410, a RACH report is received from the first data storage device according to the subscription request.

[0125] In some example embodiments, method 1400 further includes: receiving a response in response to transmitting a subscription request, the response including at least one of an acknowledgment of the subscription request or a failure of the subscription request.

[0126] In some example implementations, the subscription request for updates to the RACH report includes the identifier of the second network node.

[0127] In some example embodiments, a first device capable of performing any method 1200 (e.g., Figure 3 The first data storage device 310 may include components for performing the corresponding operations of method 1200. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 3 The first data storage device 310 in the middle.

[0128] In some example embodiments, the first apparatus includes: components 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 or second data storage devices; components for determining that the RACH report will be transmitted to the second network node; and components 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.

[0129] In some example embodiments, a first data storage device is associated with a second network node. The first apparatus includes components for receiving from the second network node a subscription request for receiving updates of RACH reports transmitted by a terminal device and corresponding to a cell controlled by the second network node, wherein the RACH reports are transmitted to the second network node according to the received subscription request.

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

[0131] In some example embodiments, the first device includes a component for transmitting a response to a second network node in response to receiving a subscription request, including at least one of an acknowledgment of the subscription request or a failure of the subscription request.

[0132] In some example embodiments, the subscription request for an update to the RACH report includes an identifier of a second network node. The first apparatus includes components for determining, based on the identifier of the second network node, that the RACH report will be transmitted to the second network node.

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

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

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

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

[0137] In some example embodiments, the first device includes components for receiving a request for an address of a third data storage device from a fourth data storage device; and components for transmitting the address of the third data storage device to the fourth data storage device.

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

[0139] In some example embodiments, the first device includes components for storing received RACH reports.

[0140] In some example embodiments, the first device includes components for storing received subscription requests, wherein the subscription requests are used to subscribe to, receive notifications, monitor events, or detect RACH report updates.

[0141] In some example embodiments, a second device capable of performing any method 1300 (e.g., Figure 3The first network node 210 may include components for performing the corresponding operations of method 1300. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 3 In the first network node 210.

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

[0143] In some example implementations, the identifier of the second network node is read from the header of the RACH report.

[0144] In some example embodiments, a third device capable of performing any method 1400 (e.g., Figure 3 The second network node 220 may include components for performing the corresponding operations of method 1400. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 3 In the second network node 220.

[0145] In some example embodiments, the third apparatus includes: components for transmitting to a first data storage device a subscription request for receiving updates of a Random Access Channel (RACH) report transmitted by a terminal device and corresponding to a cell controlled by a second network node; and components for receiving the RACH report from the first data storage device according to the subscription request.

[0146] In some example embodiments, the third device includes a component for receiving a response, including at least one of an acknowledgment of the subscription request or a failure of the subscription request, in response to transmitting a subscription request.

[0147] In some example implementations, the subscription request for updates to the RACH report includes the identifier of the second network node.

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

[0149] Communication module 1540 is used for bidirectional communication. Communication module 1540 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1540 may include at least one antenna.

[0150] As a non-limiting example, processor 1510 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1500 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0151] Memory 1520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1524, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1522 and other volatile memories that cannot be retained during power loss.

[0152] Computer program 1530 includes computer-executable instructions that are executed by an associated processor 1510. The instructions of program 1530 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1530 may be stored in memory (e.g., ROM 1524). Processor 1510 can perform any suitable actions and processes by loading program 1530 into RAM 1522.

[0153] Example embodiments of this disclosure can be implemented by program 1530, enabling device 1500 to execute as described in the reference. Figures 1 to 14 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0154] In some example embodiments, program 1530 may be tangibly contained in a computer-readable medium, which may be included in device 1500 (such as memory 1520) or other storage device accessible by device 1500. Device 1500 may load program 1530 from the computer-readable medium into RAM 1522 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0155] Figure 16 An example of a computer-readable medium 1600 is shown, which may be in the form of a CD, DVD, or other optical storage disc. A program 1530 is stored on the computer-readable medium 1600.

[0156] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0157] Some exemplary embodiments of this 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 computer-executable instructions that execute on a target physical or virtual processor within a device, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0158] Program code used to perform the methods of this 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 when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0159] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0160] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0161] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0162] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A first data storage device, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the first data storage device to at least: 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 the area served by the first network node; It is determined that the RACH report will be transmitted to the second network node; as well as The RACH report is transmitted 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 enable the first data storage device to: The terminal device receives a subscription request from the second network node for receiving updates to RACH reports, which are transmitted by the terminal device and correspond to a cell controlled by the second network node. The RACH report is transmitted to the second network node in accordance with the received subscription request.

3. The first data storage device according to claim 2, wherein the second data storage device includes 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 according to claim 2 or 3, wherein the at least one memory and the at least one processor further enable the first data storage device to: In response to receiving the subscription request, a response is transmitted to the second network node, the response including at least one of acknowledgment of the subscription request or failure of the subscription request.

5. The first data storage device according to any one of claims 2 to 4, wherein the subscription request for the update of the RACH report includes the identifier of the second network node, and the at least one memory and the at least one processor further enable the first data storage device to: The identifier of the second network node is used to determine that the RACH report will be transmitted to the second network node.

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

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

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

9. The first data storage device according to claim 8, wherein the at least one memory and the at least one processor further enable the first data storage device to: Receive a request for the address of the third data storage device from the fourth data storage device; and The address of the third data storage device is transmitted to the fourth 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 processor further enable the first data storage device to: Transmit a request for the address of the third data storage device to the global data storage device; and Receive the address of the third data storage device from the global data storage device.

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

12. The first data storage device according to claim 2, wherein the at least one memory and the at least one processor further enable the first data storage device to: The received subscription request is stored, wherein the subscription request is used to subscribe to, receive notifications, monitor events, or detect updates to the RACH report.

13. A first network node, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the first network node to at least: 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 the second network node; Obtain the identifier of the second network node; as well as The RACH report and the identifier of the second network node are transmitted to the data storage device.

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

15. A second network node, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the second network node to at least: A subscription request for receiving updates of Random Access Channel (RACH) reports is transmitted to a first data storage device, the RACH reports being transmitted by a terminal device and corresponding to a cell controlled by the second network node; as well as The RACH report is received from the data storage device according to the subscription request.

16. The second network node of claim 15, wherein the at least one memory and the at least one processor further enable the second network node to: In response to transmitting the subscription request, a response is received, the response including at least one of acknowledgment of the subscription request or failure of the subscription request.

17. The second network node according to claim 15 or 16, wherein the subscription request for receiving the update of the RACH report includes an identifier of the second network node.

18. A method comprising: 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 the area served by the first network node; It is determined that the RACH report will be transmitted to the second network node; as well as The RACH report is transmitted 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: 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 the second network node; Obtain the identifier of the second network node; as well as The RACH report and the identifier of the second network node are transmitted to the data storage device.

20. A method comprising: A subscription request for receiving updates of Random Access Channel (RACH) reports is transmitted to a first data storage device, the RACH reports being transmitted by a terminal device and corresponding to a cell controlled by the second network node; as well as The RACH report is received from the first data storage device according to the subscription request.

21. A first device, comprising: A component 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 the area served by the first network node; Components used to determine that the RACH report will be transmitted to the second network node; as well as A component 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 device, comprising: A component 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 the second network node; A component for obtaining the identifier of the second network node; as well as A component for transmitting the RACH report and the identifier of the second network node to the data storage device.

23. A third device, comprising: Components for transmitting to a first data storage device a subscription request for receiving updates of random access channel (RACH) reports, the RACH reports being transmitted by a terminal device and corresponding to a cell controlled by the second network node; as well as A component for receiving the RACH report from the first data storage device in accordance with the subscription request.

24. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method according to any one of claims 18 to 20.

Images