Method for obtaining enrichment information and controller

This application claims the priority benefit of Taiwan application serial no. 110139938, filed on Oct. 27, 2021. The entirety of the above-mentioned patent application is hereby incorporated by reference herein and made a part of this specification.

The disclosure relates to an enrichment information (EI) processing technology.

The characteristics of large bandwidth, low latency, multiple connections, and multiple frame structures provided by 5G may meet a variety of applications with different needs. However, due to the different requirements of various applications, device differences, environmental changes, etc., it is difficult to design the best configuration (system parameters, such as handover measurement and handover timing) in advance to achieve the best performance.

Starting from the maintenance needs of operators, the O-RAN Alliance proposes a 5G communication system architecture with software/hardware deconstruction and network function virtualization, as well as two management components: the service management and orchestration (SMO) and the radio access network (RAN) intelligent controller (RIC). According to the deployment environment and real-time usage conditions, network performance may be analyzed and predicted, and active network configuration or control may be adopted to maintain the quality required by various applications. In addition to obtaining available information from RAN, SMO and RIC are also allowed to make better judgments and decisions if the enrichment information (EI) may be supplemented from outside the network.

RIC may manage the use of wireless resources of the base stations, such as a handover policy, a change in the amount of use of the wireless resources, quality of service (QoS) limitation, and other applications. If external information and enrichment information are needed to improve performance, RIC itself must provide a unified, convenient, and efficient interface and procedures, including enrichment information type query, initiation of requests, information update, task establishment, task deletion, etc.

Therefore, how to design the abovementioned interface and program for RIC is an important issue for a person having ordinary skill in the art.

In view of the above, the disclosure provides a method for obtaining enrichment information and a controller configured to solve the above technical problems.

The disclosure provides a method for obtaining enrichment information, and the method includes an enrichment information handling circuit and a controller of a database. The method includes the following steps. In response to the enrichment information handling circuit receiving a first creation request associated with the first user device from a first application, the enrichment information handling circuit queries whether the database stores a first enrichment information corresponding to a first user device. In response to determining that the database stores the first enrichment information corresponding to the first user device, the enrichment information handling circuit triggers the first application to subscribe to the database for enrichment information corresponding to the first user device. In response to presence of a second enrichment information corresponding to the first user device in the database, the database pushes the second enrichment information to the first application.

The disclosure provides a controller for obtaining enrichment information, and the controller includes a database and an enrichment information handling circuit. The enrichment information handling circuit is coupled to the database. In response to the enrichment information handling circuit receiving a first creation request associated with the first user device from a first application, the enrichment information handling circuit queries whether the database stores a first enrichment information corresponding to a first user device. In response to determining that the database stores the first enrichment information corresponding to the first user device, the enrichment information handling circuit triggers the first application to subscribe to the database for enrichment information corresponding to the first user device. In response to presence of a second enrichment information corresponding to the first user device in the database, the database pushes the second enrichment information to the first application.

To make the aforementioned more comprehensible, several embodiments accompanied with drawings are described in detail as follows.

The accompanying drawings are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the disclosure and, together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a diagram illustrating an architecture of an open radio access network (O-RAN).

FIG. 2 is a diagram illustrating an internal architecture of a near-real-time radio access network intelligent controller (near-RT RIC).

FIG. 3 is a diagram illustrating various application programming interfaces (APIs) in the near-RT RIC.

FIG. 4 is a schematic diagram illustrating a controller according to an exemplary embodiment of the disclosure.

FIG. 5 is a flow chart illustrating a method for obtaining enrichment information according to an exemplary embodiment of the disclosure.

FIG. 6 is a diagram illustrating an application scenario according to a first embodiment of the disclosure.

FIG. 7 A is a diagram illustrating an application scenario according to a second embodiment of the disclosure.

FIG. 7 B is a diagram illustrating another application scenario according to the second embodiment of the disclosure.

FIG. 8 is a diagram illustrating an application scenario according to a third embodiment of the disclosure.

FIG. 9 A and FIG. 9 B are diagrams illustrating application scenarios according to an exemplary embodiment of the disclosure.

The O-RAN Alliance is an alliance dominated by operators, calling on equipment vendors to join to jointly define an open interface and an automatic and intelligent network management architecture. The O-RAN architecture proposed by the O-RAN Alliance is shown in FIG. 1 .

The O-RAN architecture shown in FIG. 1 includes service management and orchestration (SMO), a non-real-time radio access network intelligent controller (non-RT RIC), a near-real-time radio access network intelligent controller (near-RT RIC), an O-RAN central unit (O-CU), an O-RAN distributed unit (O-DU), and an O-RAN radio unit (O-RU).

The SMO may communicate with each managed component through the O1 interface to achieve behaviors, such as (1) fault (error), configuration, accounting, performance, and fault management (FCAPS management) and safety management; (2) collection of performance data and access to a network and user performance data. In addition, the SMO may communicate with a cloud platform (O-RAN Cloud, O-Cloud) through an O2 interface to achieve behaviors such as orchestrating cloud platform resources.

The non-RT RIC may communicate with near-RT RIC through an A1 interface. In some embodiments, the non-RT RIC transmits an A1 policy to the near-RT RIC through the A1 interface. The A1 policy includes, but not limited to, quality of service (QoS), quality of experience (QoE), traffic steering, etc.

Besides, the non-RT RIC may provide enrichment information to the near-RT RIC through the A1 interface after obtaining the enrichment information from external sources. Two kinds of enrichment information objects are provided in an enrichment information related specification: (1) an enrichment information type object (ET type object) and (2) an enrichment information job object (EI job object). The enrichment information type object includes an EI type identifier and a schema. The enrichment information job object includes an EI type identifier, an enrichment information transmission uniform resource identifier (URI), and enrichment information job definition, etc. The enrichment information job definition may include a scope, requirement parameters, and conditions.

In addition, the non-RT RIC may further train a machine learning model, execute a machine learning model, or configure a machine learning model to the near-RT RIC, so that the near-RT RIC may execute the machine learning model, but it is not limited thereto.

The near-RT RIC may communicate with the O-CU and O-DU through an E2 interface to realize (1) collection, analysis, and monitoring of network information and user information from the O-CU and O-DU and (2) operations such as controlling of O-CU and O-DU behaviors or parameters.

In addition, the near-RT RIC may run applications (xApps) to realize the radio resource management (RRM) function. Further, the near-RT RIC may also provide an application programming interface (API) for interacting with the xApps.

The O-CU, O-DU, and O-RU may respectively support the functions of a centralized unit/distributed unit/and radio unit defined by 3GPP and may all support an O1 interface.

Besides, the O-CU may be further divided into a control unit (O-RAN central unit control plane, O-CU-CP) and a user unit (O-RAN central unit user plane, O-CU-UP). Moreover, the O-DU and O-RU support an open-fronthaul interface (OFH interface) defined by O-RAN.

With reference to FIG. 2 and FIG. 3 , FIG. 2 is a diagram illustrating an internal architecture of a near-RT RIC, and FIG. 3 is a diagram illustrating various APIs in the near-RT RIC. As shown in FIG. 2 and FIG. 3 , the near-RT RIC includes basic function and applications (xApps). The APIs are interfaces that support the xApps and are divided into five categories: A1 Related APIs, E2 Related APIs, management APIs, enablement APIs, and shared data layer (SDL) APIs.

Regarding the A1 interface, currently, the O-RAN Alliance has defined related APIs and procedures such as A1 policy setup, A1 policy update, and A1 policy deletion. Regarding the SDL, the O-RAN Alliance has defined APIs and procedures such as SDL client registration/deregistration, data fetching/storing/modifying, subscription/notification, subscription/push, etc.

Details of the content of FIG. 1 to FIG. 3 may be found with reference to “0-RAN.WG1.O-RAN-Architecture-Description-v04.00” and “O-RAN.WG2.A1AP-v03.00”, and the content is incorporated into the specification by reference and thus is not be repeated herein.

However, in the related specifications of O-RAN, the mechanism for the xApps to process enrichment information through APIs is not defined. In view of the above, the disclosure provides a method for obtaining enrichment information and a controller configured to solve the above technical problems.

With reference to FIG. 4 , which is a schematic diagram illustrating a controller according to an exemplary embodiment of the disclosure. In the embodiments of the disclosure, a controller 400 may be a RAN controller of various types, such as a RIC, but may not be limited thereto. As shown in FIG. 4 , the controller 400 includes an enrichment information handling circuit 401 , a database 403 , an enrichment information connection interface 405 , and a first application 407 .

In FIG. 4 , the enrichment information handling circuit 401 , the database 403 , and the enrichment information connection interface 405 may be connected to one another. In some embodiments, the enrichment information connection interface 405 may be configured to be connected to an enrichment information provider 499 outside the controller 400 . In an embodiment, after obtaining enrichment information of specific devices, the enrichment information provider 499 may send the obtained enrichment information to the enrichment information connection interface 405 , and the enrichment information connection interface 405 may, for example, provide the enrichment information to the enrichment information handling circuit 401 and the database 403 for subsequent use, but it is not limited thereto.

In some embodiments, the database 403 is, for example, a database corresponding to the SDL, and may be used to store the abovementioned enrichment information, but it is not limited thereto.

In the embodiments of the disclosure, the controller 400 may run a plurality of applications (i.e., the xApps), and the first application 407 is, for example, one of these xApps. For ease of understanding, the following takes the first application 407 as an example to illustrate the way it interacts with the enrichment information handling circuit 401 , the database 403 , and the enrichment information connection interface 405 , and a person having ordinary skill in the art should be able to deduce other ways for the xApps to interact with the enrichment information handling circuit 401 , the database 403 , and the enrichment information connection interface 405 accordingly.

With reference to FIG. 5 , which is a flow chart illustrating a method for obtaining enrichment information according to an exemplary embodiment of the disclosure. The method provided by this embodiment may be executed by the controller 400 in FIG. 4 , and each step in FIG. 5 is described in detail together with the elements shown in FIG. 4 .

First, in step S 510 , in response to the enrichment information handling circuit 401 receiving a first creation request CRQ 1 associated with a first user device D 1 from the first application 407 , the enrichment information handling circuit 401 queries whether the database 403 stores a first enrichment information corresponding to the first user device D 1 .

In step S 520 , in response to determining that the database 403 stores the first enrichment information corresponding to the first user device D 1 , the enrichment information handling circuit 401 triggers the first application 407 to subscribe to the database 403 for enrichment information corresponding to the first user device D 1 .

In step S 530 , in response to presence of a second enrichment information corresponding to the first user device D 1 in the database 403 , the database 403 pushes the second enrichment information to the first application 407 .

In order to make the above concepts easier to understand, the following is supplemented with FIG. 6 for further explanation, and FIG. 6 is a diagram illustrating an application scenario according to a first embodiment of the disclosure.

In FIG. 6 , it is assumed that the first application 407 needs the enrichment information of the first user device D 1 , so the first application 407 may send the first creation request CRQ 1 associated with the first user device D 1 to the enrichment information handling circuit 401 in step S 601 .

In an embodiment, the first creation request CRQ 1 may instructs at least one of an enrichment information type, a device identity of the first user device D 1 , an enrichment information format, a reply instruction, a reply period, and a timestamp instruction. In some embodiments, the reply instruction may instruct whether to reply to the first application 407 immediately after the enrichment information of the first user device D 1 is obtained. The reply period may instruct a period for obtaining the enrichment information of the first user device D 1 . The timestamp instruction may instruct whether to add a timestamp to the enrichment information of the first user device D 1 .

In an embodiment, the first creation request CRQ 1 may be configured to request creation of a first enrichment information job object OB 1 corresponding to the first user device D 1 . Further, the first enrichment information job object OB 1 includes at least one of the enrichment information type, a job return URL (e.g., URI), a job status reminder URL, an information format type, the reply instruction, the reply period, and the timestamp instruction.

When the enrichment information handling circuit 401 receives the first creation request CRQ 1 , the enrichment information handling circuit 401 may send a first query request QRQ 1 to the database 403 in response to the first creation request CRQ 1 in step S 602 . The first query request QRQ 1 may be configured to query whether the database 403 stores the first enrichment information corresponding to the first user device D 1 .

Correspondingly, the database 403 may query whether the database 403 stores the first enrichment information corresponding to the first user device D 1 in response to the first query request QRQ 1 and sends a first query response QRR 1 to the enrichment information handling circuit 401 according to a first query result of the first query request QRQ 1 in step S 603 .

In some embodiments, the first query request QRQ 1 may include the device identity of the first user device D 1 and an object identity of the first enrichment information job object OB 1 . In addition, the first query response QRR 1 may include the device identity of the first user device, the object identity of the first enrichment information job object OB 1 , and a query status field. The query status field may instruct whether the database 403 stores the first enrichment information corresponding to the first user device D 1 . In an embodiment, when the query status field is a first value (e.g., 1), it may mean that the database 403 stores the first enrichment information corresponding to the first user device D 1 . Further, when the query status field is a second value (e.g., 0), it may mean that the database 403 does not store the first enrichment information corresponding to the first user device D 1 , but it is not limited thereto.

For ease of description, it is assumed that the database 403 stores the first enrichment information corresponding to the first user device D 1 in FIG. 6 . In this case, the query status field of the first query response QRR 1 may be set to the first value through the database 403 , so as to notify the enrichment information handling circuit 401 .

When the enrichment information handling circuit 401 receives the first query response QRR 1 , the enrichment information handling circuit 401 may determine that the first query response QRR 1 instructs that the database 403 stores the first enrichment information corresponding to the first user device D 1 according the query status field presented as the first value, so as to further determine that the database 403 stores the first enrichment information corresponding to the first user device D 1 .

In this case, the enrichment information handling circuit 401 may send a first creation response CRR 1 to the first application 407 in step S 604 . In an embodiment, the first creation response CRR 1 may include the enrichment information type, the object identity of the first enrichment information job object OB 1 , job content of the first enrichment information job object OB 1 , and a creation status field. The creation status field may instruct whether the first enrichment information job object OB 1 is successfully created.

In an embodiment, when the creation status field is the first value (e.g., 1), it may mean that the first enrichment information job object OB 1 is successfully created. Further, when the creation status field is the second value (e.g., 0), it may mean that the first enrichment information job object OB 1 is not successfully created, but it is not limited thereto.

In the scenario of FIG. 6 , since the database 403 stores the first enrichment information corresponding to the first user device D 1 , this means that the first enrichment information work object OB 1 is created. Therefore, the enrichment information handling circuit 401 may set the creation status field of the first creation response CRR 1 to the first value to notify the first application 407 .

In an embodiment, in response to the first application 407 determines that the first creation response CRR 1 instructs that the first enrichment information job object OB 1 is successfully created, the first application may send a first tracking message TM 1 corresponding to the first enrichment information job object OB 1 to the enrichment information handling circuit 401 in step S 605 . In an embodiment, the first tracking message TM 1 may instruct the object identity of the first enrichment information job object OB 1 and is configured to register and track the enrichment information of the first user device D 1 with the enrichment information handling circuit 401 .

Next, in step S 606 , the first application 407 may send a first subscription message SM 1 to the database 403 . The first subscription message SM 1 instructs to subscribe to the database 403 for the enrichment information corresponding to the first user device D 1 .

Next, in step S 607 , in response to presence of the second enrichment information corresponding to the first user device D 1 in the database 403 , the database 403 may push the second enrichment information to the first application 407 .

In FIG. 6 , the first application 407 and the enrichment information handling circuit 401 may send various requests/responses/messages as shown through APIs related to the enrichment information. Besides, the first application 407 and the enrichment information handling circuit 401 may individually exchange various data as shown with the database 403 through APIs related to the SDL.

With reference to FIG. 7 A , which is a diagram illustrating an application scenario according to a second embodiment of the disclosure. In step S 701 , the first application 407 may send the first creation request CRQ 1 associated with the first user device D 1 to the enrichment information handling circuit 401 . In step S 702 , the enrichment information handling circuit 401 may send the first query request QRQ 1 to the database 403 in response to the first creation request CRQ 1 . In step S 703 , the database 403 may send the first query response QRR 1 to the enrichment information handling circuit 401 according to a first query result of the first query request QRQ 1 . The content of steps S 701 to S 703 may be found with reference to the description related to steps S 601 to S 603 in FIG. 6 , so description thereof is not repeated herein.

In the scenario of FIG. 7 A , it is assumed that in the database 403 does not store the first enrichment information corresponding to the first user device D 1 . In this case, the query status field of the first query response QRR 1 may be set to the second value through the database 403 , so as to notify the enrichment information handling circuit 401 .

When the enrichment information handling circuit 401 receives the first query response QRR 1 , the enrichment information handling circuit 401 may determine that the first query response QRR 1 instructs that the database 403 does not store the first enrichment information corresponding to the first user device D 1 according the query status field presented as the second value, so as to further determine that the database 403 does not store the first enrichment information corresponding to the first user device D 1 (i.e., the first enrichment information job object OB 1 is not created yet).

In this case, the enrichment information handling circuit 401 may send a second query request QRQ 2 to the enrichment information connection interface 405 . The second query request QRQ 2 may instruct the enrichment information type. Correspondingly, in step S 705 , the enrichment information connection interface 405 may query whether the enrichment information provider 499 supports the enrichment information type.

In different embodiments, the enrichment information provider 499 may return a first response message RM 1 to the enrichment information connection interface 405 in step S 706 based on whether the enrichment information provider 499 itself supports the aforementioned enrichment information type.

In the scenario of FIG. 7 A , it is assumed that the first response message RM 1 instructs that the enrichment information provider 499 supports the enrichment information type. In this case, the enrichment information connection interface 405 may request the enrichment information provider 499 to create the first enrichment information job object OB 1 in step S 707 . In other embodiments, if the first response message RM 1 instructs that the enrichment information provider 499 does not support the enrichment information type, the mechanism shown in FIG. 7 B may be correspondingly executed in this embodiment, and details thereof is to be described in following paragraphs.

In FIG. 7 A , after the enrichment information provider 499 completes creation of the first enrichment information job object OB 1 according to the request made by the enrichment information connection interface 405 , the enrichment information provide 499 may return a second response message RM 2 to the enrichment information connection interface 405 to notify the enrichment information connection interface 405 in step S 708 .

Thereafter, the enrichment information connection interface 405 may send the second query response QRR 2 to the enrichment information handling circuit 401 in step S 709 . In an embodiment, the second query response QRR 2 may instruct successful creation of the first enrichment information job object OB 1 and includes the enrichment information type, the object identity of the first enrichment information job object OB 1 , and the job content of the first enrichment information job object OB 1 .

Next, in step S 710 , the enrichment information handling circuit 401 may send the first creation response CRR 1 to the first application 407 . In step S 711 , the first application may send the first tracking message TM 1 corresponding to the first enrichment information job object OB 1 to the enrichment information handling circuit 401 . In step S 712 , the first application 407 may send the first subscription message SM 1 to the database 403 .

The content of steps S 710 to S 712 may be found with reference to the description related to steps S 604 to S 606 in FIG. 6 , so description thereof is not repeated herein.

In step 7 A, when the enrichment information provider 499 obtains the second enrichment information of the first user device D 1 , the enrichment information provider 499 may send the second enrichment information to the enrichment information connection interface 405 in step S 713 . In an embodiment, the second enrichment information may include the device identity of the first user device D 1 , status information of the first user device D 1 , and a timestamp. In some embodiments, the status information of the first user device D 1 includes, for example, location information of the first user device D 1 corresponding to the timestamp, but it is not limited thereto.

In an embodiment, when the enrichment information connection interface 405 receives the second enrichment information from the enrichment information provider 499 in step S 713 , the enrichment information connection interface 405 may store the second enrichment information to the database 403 in step S 714 .

Next, in step S 715 , in response to presence of the second enrichment information corresponding to the first user device D 1 in the database 403 , the database 403 may push the second enrichment information to the first application 407 .

With reference to FIG. 7 B , which is a diagram illustrating another application scenario according to the second embodiment of the disclosure. In FIG. 7 B , the content of steps S 701 to S 706 may be found with reference to the description related to FIG. 7 A , so description thereof is not repeated herein. In this embodiment, it is assumed that the first response message RM 1 instructs that the enrichment information provider 499 does not support the enrichment information type. In this case, the enrichment information connection interface 405 may send a third query response QRR 3 to the enrichment information handling circuit 401 in step S 716 . The third query response QRR 3 instructs unsuccessful creation of the first enrichment information job object OB 1 and includes the enrichment information type, the object identity of the first enrichment information job object OB 1 , and the job content of the first enrichment information job object OB 1 .

Thereafter, in step S 717 , in response to the enrichment information handling circuit 401 receives the third query response QRR 3 , the enrichment information handling circuit 401 may send a second creation response CRR 2 to the first application 407 . The second creation response CRR 2 instructs that the first enrichment information job object OB 1 is not successfully created.

In FIG. 7 A and FIG. 7 B , the first application 407 and the enrichment information handling circuit 401 may send various requests/responses/messages as shown through APIs related to the enrichment information. Besides, the first application 407 , the enrichment information handling circuit 401 , and the enrichment information connection interface 405 may individually exchange various data as shown with the database 403 through APIs related to the SDL. Moreover, the enrichment information handling circuit 405 and the enrichment information connection interface 405 may send various requests/responses/messages as shown through APIs related to the A1 interface.

With reference to FIG. 8 , which is a diagram illustrating an application scenario according to a third embodiment of the disclosure. In this embodiment, when the first application 407 intends to stop tracking the enrichment information of the first user device D 1 , the first application 407 may send a first delete request DQ 1 to the enrichment information handling circuit 401 in step S 801 to request deletion of the first enrichment information job object OB 1 .

Next, in step S 802 , in response to the enrichment information handling circuit 401 receives the first delete request DQ 1 of deleting the first enrichment information job object OB 1 from the first application 407 , the enrichment information handling circuit 401 may cancel tracking of the enrichment information of the first user device by the first application 407 .

Moreover, in step S 803 , the first application 407 may send a first subscription cancellation message USM 1 to the database 403 . The first subscription cancellation message USM 1 instructs to unsubscribe to the database 403 for the enrichment information corresponding to the first user device D 1 .

In an embodiment, after receiving the first delete request DQ 1 , the enrichment information handling circuit 401 may determine whether other applications in the controller 400 still need to access the enrichment information of the first user device D 1 .

In an embodiment, if other applications in the controller 400 still need to access the enrichment information of the first user device D 1 , the enrichment information handling circuit 401 may not continue to request the enrichment information provider 499 to delete the first enrichment information job object OB 1 through the enrichment information connection interface 405 .

In another embodiment, if there is no other application in the controller 400 that needs to access the enrichment information of the first user device D 1 , the enrichment information handling circuit 401 may send a second deletion request DQ 2 to the database 403 in step S 803 . The second delete request DQ 2 includes the object identity of the first enrichment information job object OB 1 .

In addition, if there is no other application in the controller 400 that needs to access the enrichment information of the first user device D 1 , the enrichment information handling circuit 401 may further send a third deletion request DQ 3 to the enrichment information connection interface 405 in step S 804 . The third delete request DQ 3 includes the object identity of the first enrichment information job object OB 1 .

Correspondingly, in step S 805 , the enrichment information connection interface 405 may request the enrichment information provider 499 maintaining the first enrichment information job object OB 1 to delete the first enrichment information job object OB 1 in response to the third delete request DQ 3 . In an embodiment, after the enrichment information provider 499 deletes the first enrichment information job object OB 1 , a third response message RM 3 may be returned in step S 806 to notify the enrichment information connection interface 405 .

In step S 807 , the enrichment information handling circuit 401 may send a delete success response DR to the first application 407 . The delete success response DR instructs that the first enrichment information job object OB 1 is deleted.

In FIG. 8 , the first application 407 and the enrichment information handling circuit 401 may send various requests/responses/messages as shown through APIs related to the enrichment information. Besides, the first application 407 , the enrichment information handling circuit 401 , and the enrichment information connection interface 405 may individually exchange various data as shown with the database 403 through APIs related to the SDL. Moreover, the enrichment information handling circuit 401 and the enrichment information connection interface 405 may send various requests/responses/messages as shown through APIs related to the A1 interface.

Through the mechanism taught in the foregoing embodiments, it can be seen that in the disclosure, the xApps may conveniently and effectively create/delete the enrichment information job object and obtain the interface/mechanism/procedure of the enrichment information. In this way, the xApps may further execute other applications based on the obtained enrichment information.

For instance, when a communication device is moving, its serving base station may need to be handed over to a target base station through a handover procedure as the communication device moves. The principle of determining whether to handover the communication device to the target base station is based on the difference of the reference signal receiving power (RSRP) measured by the communication device on the serving base station and other neighbor base stations.

In applications such as a flying machine racing competition, the lens image of the flying machine (a user device, for example) needs to be transmitted to the person controlling the flying machine through relevant mobile communication technology (e.g., the 4th/5th generation communication system (hereinafter referred to as 4G/5G)). In the competition venue, there are other devices other than the flying machine that need to be connected to the 4G/5G network, so two small base stations may be required to be set up.

Generally, there are no large-scale shelters in the competition field of the flying machines, so the junction of the two base stations may be set as the handover zone. In this scenario, the difference between the RSRP received by the flying machine from the two base stations is only a decimal level, but the RSRP must be an integer value in the format of the related measurement report defined in the 4G/5G system standard. Besides, coupled with the environmental changes and measurement errors that may be caused by random factors, it may lead to inaccurate handover decisions and delays. In the flying machine racing application scenarios where fast speed is required, improper handover or handover failure may lead to delay or intermittent transmission of the lens image of the flying machine, and control accuracy of the flying machine and competition results may thus be affected.

In the case that RSRP is not appropriate as a method for handover judgment, if the accurate location of the flying machine may be obtained, the handover judgment procedure should be made more accurate, and the above situation is thus prevented from occurring.

With reference to FIG. 9 A and FIG. 9 B , which are diagrams illustrating application scenarios according to an exemplary embodiment of the disclosure. In FIG. 9 A and FIG. 9 B , it is assumed that the first user device D 1 is the above-mentioned flying machine, and the first user device D 1 may be equipped with a lens and a communication circuit. The communication circuit is, for example, a circuit capable of performing 4G/5G communication and may be used to stream an image captured by the lens to a person controlling the first user device D 1 , but it is not limited thereto. In addition, a base station 901 and a base station 902 are, for example, 4G/5G base stations installed in a flying machine competition field 999 .

Further, compared to the controller 400 in FIG. 4 , a controller 900 in FIG. 9 may further include a base station connection interface 409 connected to the base stations 901 and 902 .

In FIG. 9 A and FIG. 9 B , a location detection device may be installed on the first user device D 1 , which can measure the location of the first user device D 1 in the flying machine competition field 999 through technologies such as ultra wideband (UWB), Bluetooth, Zigbee, etc., for example. In an embodiment, a plurality of anchor stations P 1 to P 4 may be provided in the flying machine competition field 999 , which may individually emit beacon signals. In this case, the location detection device may perform triangulation based on these beacon signals, so as to detect the location of the first user device D 1 in the flying machine competition field 999 and correspondingly send this location to the enrichment information provider 499 .

In an embodiment, the enrichment information provider 499 may treat the location of the first user device D 1 as the enrichment information corresponding to the first user device D 1 and provide it to the controller 900 , so that the controller 900 is allowed to execute a handover policy associated with the first user device D 1 .

In an embodiment, since the controller 900 may not know that the communication circuit on the first user device D 1 corresponds to the enrichment information provided by the location detection device, the controller 900 may perform the following operations first, to find the association between the communication circuit and the enrichment information.

In an embodiment, the enrichment information handling circuit 401 may receive a reference signal power sequence of a plurality of nearby base stations measured by the communication circuit from the base station connection interface 4096 . In an embodiment, assuming that there are k base stations near the communication circuit, and the reference signal power sequence from the t th time point to the t-M th time point may be characterized as R={R BS1 (t), R BS2 (t), . . . , R BSk (t), R BS1 (t−1), R BS2 (t−1), . . . , R BSk (t−1), . . . , RR BS1 (−t M), R BS2 (t−M), . . . , R BSk (t−M)}.

Further, the enrichment information handling circuit 401 may receive the enrichment information (i.e., the location of the first user device DO of the first user device D 1 provided by the enrichment information provider 499 from the enrichment information connection interface 405 . In an embodiment, the location from the t th time point to the t-N th time point of the first user device D 1 may be characterized as P={x(t), y(t), z(t), x(t−1), y(t−1), z(t−1), . . . , x(t−N), y(t−N), z(t−N)}.

Next, the enrichment information handling circuit 401 may build a specific association between the enrichment information of the first user device D 1 and the communication circuit based on the reference signal power sequence (i.e., R) and the enrichment information (i.e., P) of the first user device D 1 and records the specific association into the database 403 .

In an embodiment, the enrichment information handling circuit 401 may input R and P into a classifier, where the classifier may be implemented as a first neural network. In an embodiment, an input layer of the first neural network may be the aforementioned R and P, and a dimension of the input layer may be a (k(M+1)+3(N+1)) vector. Besides, an output layer dimension of the first neural network may be 2, representing Class 1 and Class 0. In some embodiments, the first neural network may further include a plurality of hidden layers, but it is not limited thereto.

In an embodiment, after the enrichment information handling circuit 401 inputs R and P into the classifier, if an output value of Class 1 is greater than an output value of Class 0, the enrichment information handling circuit 401 may determine that a specific association is provided between R and P and may record the specific association into the database 403 . In contrast, if the output value of Class 1 is not greater than the output value of Class 0, the enrichment information handling circuit 401 may determine that a specific association is not provided between R and P.

In an embodiment, supervised learning may be adopted for the training of the first neural network, and a plurality of sets of location data and their corresponding RSRP data may be retrieved in advance. In the process of training this first neural network, when the inputted location data is its corresponding RSRP data, the output value of Class 1 is 1 and the output value of Class 0 is 0, and when the inputted location data is not its corresponding RSRP data, the output value of Class 1 is 0 and the output value of Class 0 is 1, but it is not limited thereto.

In another embodiment, the enrichment information handling circuit 401 may input R and P into a correlator, where the correlator may be implemented as a second neural network. In an embodiment, an input layer of the second neural network may be the aforementioned R and P, and the dimension of the input layer may be a (k(M+1)+3(N+1)) vector. Besides, the output layer dimension of the second neural network may be 1, representing correlation (between 0 and 1). In some embodiments, the output layer may be implemented through selection of an activation function that meets this range, such as a Sigmoid function, but it is not limited thereto. In some embodiments, the second neural network may further include a plurality of hidden layers, but it is not limited thereto.

In an embodiment, supervised learning may be adopted for the training of the second neural network, and a plurality of sets of location data and their corresponding RSRP data may be retrieved in advance. In the process of training this second neural network, when the inputted location data is its corresponding RSRP data, the output value is 1, and when the inputted location data is not its corresponding RSRP data, the output value is 0, but it is not limited thereto.

In the scenarios of FIG. 9 A and FIG. 9 B , since the enrichment information of the first user device D 1 is assumed to be the location of the first user device D 1 , the information format type in the corresponding first enrichment information job object OB 1 may instruct the location of the first user device D 1 in terms of coordinates or latitude and longitude. Besides, the reply instruction in the first enrichment information job object OB 1 may instruct whether to reply to the location of the first user device D 1 immediately. The reply period in the first enrichment information job object OB 1 may instruct a period for replying the location of the first user device D 1 . The timestamp instruction in the first enrichment information job object OB 1 may instruct whether to mark the location of the first user device D 1 with a corresponding timestamp.

In an embodiment, assuming that the first enrichment information job object OB 1 is provided with the form illustrated in Table 1 below, and the enrichment information of the corresponding first user device D 1 may be provided with the content illustrated in Table 2 below.

In an embodiment, the controller 900 may determine whether the communication circuit needs to be handed over from a serving base station (e.g., the base station 901 ) among the aforementioned base stations) to a target base station (e.g., the base station 902 ) according to the enrichment information (i.e., location) of the first user device D 1 . In response to determining that the communication circuit needs to be handed over from the serving base station to the target base station, the controller 900 may, through the base station connection interface 409 , control the serving base station to handover the communication circuit to the target base station. For instance, when the controller 900 determines that the location of the first user device D 1 is located at the junction of the base stations 901 and 902 , the controller 900 may determine that the communication circuit needs to be handed over from the serving base station to the target base station and further controls the serving base station to handover the communication circuit to the target base station through the base station connection interface 409 , but it is not limited thereto.

In other embodiments, the concepts of FIG. 9 A and FIG. 9 B may also be applied to other occasions. For instance, when a self-driving car moves in a specific field, the controller 900 that manages the self-driving car may determine whether to perform a handover operation for the self-driving car according to the above teachings and the enrichment information (e.g., location) of the self-driving car.

In view of the foregoing, through the mechanism provided by the embodiments of the disclosure, the applications in the RIC may conveniently and effectively create/delete the enrichment information job object and obtain the interface/mechanism/procedure of the enrichment information. In this way, the applications in the RIC may further execute other applications based on the obtained enrichment information.

It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed embodiments without departing from the scope or spirit of the disclosure. In view of the foregoing, it is intended that the disclosure covers modifications and variations provided that they fall within the scope of the following claims and their equivalents.