Information transmission method, electronic device, and storage medium

Abstract

Embodiments of the present application provide an information transmission method, an electronic device, and a storage medium. The method is applied to a radio access network management network element. The method comprises: managing node information of at least one node in a radio access network; and responding to a service request from a core network on the basis of the node information. In the embodiments of the present application, information management can be performed on the radio access network by means of the radio access network management network element, thereby improving the efficiency of system network function invocation, reducing system communication load, and improving system communication quality.

Description

An information transmission method, electronic device and storage medium Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an information transmission method, electronic device, and storage medium. Background Technology

[0002] The current 3GPP network architecture adopts a service-oriented design. Referring to Figure 1, the 3GPP architecture is mainly divided into three parts: access network, core network, and terminals. The access network uses gNBs as 5G base stations, supporting both centralized and distributed deployments. A gNB can be divided into a Centralized Unit (CU) and a Decentralized Unit (DU), and the CU can include the Centralized Unit Control Plane (CP) and the Centralized Unit User Plane (UP). The access network implements basic functions such as radio resource management and mobility management, and supports interoperability between vendor equipment through open X2 interfaces. The core network decouples the original network element functions into multiple Network Functions (NFs), primarily including Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Unified Data Management (UDM), Authentication Server Function (AUSF), and Network Slice Selection Function (NSSF). These NFs communicate with each other through service-oriented interfaces, and each function can act as a service provider and service consumer. In the control plane, the AMF handles access control, mobility management, and security-related functions; the SMF handles session management, IP address allocation, and policy enforcement; the PCF formulates network policies and distributes them to other network elements; and the UDM centrally manages user data and subscription information. In the user plane, the UPF acts as the data plane anchor, responsible for packet forwarding, Quality of Service (QoS) enforcement, and billing functions. In terms of network management, a Network Data Analytics Function (NWDAF) is introduced to collect and analyze network data, providing a basis for network optimization and strategy adjustments. It supports automated network operation and maintenance, achieving network self-optimization through closed-loop control. With the continuous surge in the number of digital data applications and services, the demands and challenges on network resources and operators will continue to increase. Providing the diverse network performance characteristics required for future services has become a major challenge. Summary of the Invention

[0003] This application provides an information transmission method, electronic device, and storage medium, which aim to improve the efficient management of network functions, enhance network signaling interaction efficiency, reduce system communication load, and improve system communication quality.

[0004] This application provides an information transmission method applied to a wireless access network management element, wherein the method includes:

[0005] Manage node information for at least one node within the wireless access network;

[0006] The node information is used to respond to the core network's service requests.

[0007] This application also provides an electronic device, wherein the electronic device includes:

[0008] One or more processors;

[0009] Memory, used to store one or more programs;

[0010] When the one or more programs are executed by the one or more processors, the one or more processors implement the information transmission method as described in any of the embodiments of this application.

[0011] A computer-readable storage medium is characterized in that it stores one or more programs, which are executed by one or more processors to implement the information transmission method as described in any of the embodiments of this application.

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

[0013] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 is an example diagram of a 3GPP network architecture provided in an embodiment of this application;

[0015] Figure 2 is a flowchart of an information transmission method provided in an embodiment of this application;

[0016] Figure 3 is a flowchart of another information transmission method provided in an embodiment of this application;

[0017] Figure 4 is a schematic diagram of the deployment architecture of another wireless access network management element provided in an embodiment of this application;

[0018] Figure 5 is a flowchart of another information transmission method provided in an embodiment of this application;

[0019] Figure 6 is a flowchart of another information transmission method provided in an embodiment of this application;

[0020] Figure 7 is a flowchart of another information transmission method provided in an embodiment of this application;

[0021] Figure 8 is a schematic diagram of the deployment architecture of another wireless access network management element provided in an embodiment of this application;

[0022] Figure 9 is an example diagram illustrating the interaction between the AMF and the base station in supporting information access network management functions, according to an embodiment of this application.

[0023] Figure 10 is a schematic diagram of the deployment architecture of another wireless access network management element provided in an embodiment of this application;

[0024] Figure 11 is a flowchart of another information transmission method provided in an embodiment of this application;

[0025] Figure 12 is a flowchart of another information transmission method provided in an embodiment of this application;

[0026] Figure 13 is an example diagram of an information transmission method provided in an embodiment of this application;

[0027] Figure 14 is a schematic diagram of the structure of an information transmission device provided in an embodiment of this application;

[0028] Figure 15 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of this application.

[0030] In the following description, the use of suffixes such as “module,” “part,” or “unit” to denote elements is solely for the purpose of illustration in this application and has no particular meaning in itself. Therefore, “module,” “part,” or “unit” may be used interchangeably.

[0031] Figure 2 is a flowchart of an information transmission method provided in an embodiment of this application. This embodiment is applicable to scenarios involving the management of information transmission within an access network. The method can be executed by an information transmission device, typically integrated into a network element without an access network management system. In one embodiment, the access network management system can be a proxy network node of the access network, a network node integrating access network capability opening functions, a node integrating access network authorization management, or a network node integrating intelligent computing functions. As shown in Figure 2, the method provided in this embodiment specifically includes the following steps:

[0032] Step 110: Manage the node information of at least one node within the wireless access network.

[0033] Nodes can include different communication base stations within a Radio Access Network (RAN), and these base stations can support terminals using multiple communication standards. Node information can be information used to implement functions such as radio resource management or mobility management, and may include, but is not limited to, resource report configuration information, resource usage information, and synchronization source information.

[0034] In this embodiment of the application, the access network management element can manage one or more nodes within the radio access network, and can manage the node information of the nodes. This management can include configuration, forwarding, transmission, etc.

[0035] Step 120: Respond to the core network's service requests based on the node information.

[0036] Specifically, the access network management element can respond to core network service requests through the node information of one or more managed nodes. These service requests may include functional service requests from different network functions within the core network.

[0037] Based on the above-described embodiments, the radio access network management element is configured in the radio access network or the core network.

[0038] In this embodiment, the radio access network management element can be configured in the radio access network or the core network. Each node in the radio access network can be connected to the radio access network management element, and the radio access network management element can manage the node information of one or more of the nodes.

[0039] Figure 3 is a flowchart of another information transmission method provided in an embodiment of this application. This embodiment is a specific modification based on the above-mentioned embodiments. The radio access network management element can be configured as an independent NF in the core network. Referring to Figure 3, the method provided in this embodiment specifically includes the following steps:

[0040] Step 210: Send resource report configuration information to the node.

[0041] The resource report configuration information can be the information configured by the radio access network management element for the node's resource report. The resource report configuration information can indicate the conditions for triggering the resource report, the granularity of the resource report, the sending period of the resource report, and the content of the resource report.

[0042] In this embodiment of the application, the radio access network management element can send resource report configuration information to the node, thereby configuring the node to send resource reports.

[0043] Step 220: Receive the node's resource report.

[0044] Specifically, the wireless access network management element can receive resource reports uploaded by nodes, and the nodes that send these resource reports are configured with configuration information.

[0045] Step 230: Obtain requests from core network function consumers.

[0046] Among them, network function consumers can include various network function elements of the core network, and network function consumption can include, but is not limited to, AMF, SMF, UPF, PCF, UDM, AUSF, NSSF, etc.

[0047] In this embodiment of the application, the network function consumer of the core network will transmit the request to the radio access network management element, and the radio access network management element can receive the request.

[0048] Based on the above-described embodiments, the request includes at least one of the following:

[0049] A request to obtain resource utilization at a specified resource granularity;

[0050] A request to obtain the number of connected terminals at least one node;

[0051] A request to obtain the load status of at least one node;

[0052] A request to obtain the support capability status of at least one node, wherein the support capability status includes at least one of the following: perception capability status, artificial intelligence capability status, or positioning capability status;

[0053] A request to obtain the resource utilization rate of at least one cell;

[0054] Request to obtain the number of access terminals in at least one cell

[0055] A request to obtain the load status of at least one cell;

[0056] A request to obtain the link transmission latency of at least one cell;

[0057] A request to obtain the link transmission packet error rate of at least one cell.

[0058] In this embodiment, the radio access network element can receive requests sent by NF consumers and send response messages to the NF consumers. Requests sent by the NF consumers to the radio access network element may include: requesting to obtain the resource utilization rate of a base station or a group of base stations; requesting to obtain the number of terminals accessing a base station or a group of base stations; requesting to obtain the load status of a base station or a group of base stations; requesting to obtain the support capability status of a base station or a group of base stations, which may include the base station's support for sensing capabilities, artificial intelligence capabilities, and positioning capabilities; requesting to obtain the resource utilization rate of a cell or a group of cells; requesting to obtain the number of terminals accessing a cell or a group of cells; requesting to obtain the load status of a cell or a group of cells; requesting to obtain the link transmission delay of a cell or a group of cells; and requesting to obtain the link transmission packet error rate of a cell or a group of cells.

[0059] Step 240: Feed back the response information of the request to the network function consumer based on the resource report.

[0060] In some application embodiments, the resource report configuration information includes at least one of the following: resource report request information, or resource report sending conditions.

[0061] In this embodiment of the application, the resource report configuration sent by the access network management element may include a resource report request and / or resource report sending conditions.

[0062] In some application embodiments, the resource report configuration information is the resource report sending condition, which includes at least one of the following: report sending period, or conditions that trigger report sending.

[0063] In this embodiment of the application, when the resource report configuration information includes resource report sending conditions, the resource report sending conditions may include the report sending period or the conditions that trigger report sending.

[0064] In the above application embodiments, the resource report sending conditions include conditions that trigger report sending, and the conditions that trigger report sending include at least one of the following:

[0065] The measurement or resource statistics result is higher than the configured threshold value;

[0066] The measurement or resource statistics result is lower than the configured threshold value;

[0067] The measurement or resource statistics result has changed more than the configured threshold value compared to the previous resource report.

[0068] In this application embodiment, the conditions for triggering report sending may include the measurement or resource statistics results being higher than a threshold value, such as the uplink resource utilization rate being greater than a first threshold, the downlink resource utilization rate being greater than a second threshold, the uplink air interface transmission latency being greater than a third threshold, the downlink air interface transmission latency being greater than a fourth threshold, the uplink air interface transmission packet error rate being greater than a fifth threshold, and the downlink air interface transmission false alarm rate being greater than a sixth threshold, etc.

[0069] In other application embodiments, the conditions for triggering report sending may include the result of measurement or resource statistics being lower than a threshold value, such as the uplink resource utilization rate being lower than a first threshold, the downlink resource utilization rate being lower than a second threshold, the uplink air interface transmission latency being lower than a third threshold, the downlink air interface transmission latency being lower than a fourth threshold, the uplink air interface transmission packet error rate being lower than a fifth threshold, and the downlink air interface transmission packet error rate being lower than a sixth threshold, etc.

[0070] In other embodiments, the conditions for triggering report transmission may include the change in the measurement or resource statistics result compared to the previous resource report exceeding a configured threshold value. This change may include an increase or decrease, for example, compared to the previous resource report, the change in uplink resource utilization is greater than a first threshold; compared to the previous report, the change in downlink resource utilization is greater than a second threshold; compared to the previous report, the change in downlink resource utilization is greater than a second threshold; compared to the previous report, the change in uplink air interface transmission latency is greater than a third threshold; compared to the previous report, the change in downlink air interface transmission latency is greater than a fourth threshold; compared to the previous report, the change in uplink air interface transmission packet error rate is greater than a fifth threshold; compared to the previous report, the change in downlink air interface transmission packet error rate is greater than a sixth threshold, etc.

[0071] Based on the above application embodiments, the resource report configuration information also includes the value of the threshold value.

[0072] In this embodiment of the application, the resource report configuration information also includes the value of the threshold value in the condition for triggering the report to be sent. The threshold value may include the result of measurement or resource statistics being higher than the configured threshold value; the result of measurement or resource statistics being lower than the configured threshold value; the change in the value of measurement or resource statistics compared to the previous resource report exceeding the configured threshold value, etc.

[0073] Based on the above application embodiments, the resource report configuration information further includes: the report granularity of the resource report, wherein the report granularity includes at least one of the following: cell, network segmentation, data packet priority, data packet type, centralized unit, distributed unit, and communication standard.

[0074] In this embodiment of the application, the wireless access network management element can also configure the reporting granularity of resource reports through resource report configuration information. For example, it can be configured that nodes report resources based on cells, based on network allocation, based on data packet priority, based on centralized units, based on distributed units, or based on the communication standards of different terminals.

[0075] For example, the access network management element can be configured to perform resource reporting based on different granularities. For instance, the base station can perform statistics and reporting based on resources of different cells, resources of different network segments, data packets of different priorities, or different types of data packets. Furthermore, if the base station has a separate CU and DU architecture, or a separate CU and Remote Unit (RU) architecture, statistics and reporting can also be performed based on different CUs, DUs, or RUs. When the base station supports multiple terminal communication standards, such as 4G Radio Access Technology (RAT), 5G RAT, 6G RAT, or non-3GPP related RATs (e.g., Wi-Fi, Bluetooth), statistical reporting can also be configured based on different communication standards.

[0076] Based on the above application embodiments, the resource report includes at least one of the following: resource utilization rate, link transmission latency, and link transmission packet error rate.

[0077] In this embodiment of the application, after configuring the resource report configuration information, the node in the radio access network can send a resource report to the radio access network management element. The radio access network management element can receive the node's resource report, which may include one or more of resource utilization, link transmission delay, and link transmission packet error rate.

[0078] In some application embodiments, resource utilization can include downlink guaranteed bit rate (GBR) physical resource block (PRB) utilization rate, uplink GBR resource block utilization rate, etc., wherein the downlink GBR PRB utilization rate can represent the percentage of downlink physical resource block usage out of the total number of physical resource blocks, and the uplink GBR PRB utilization rate can represent the percentage of uplink physical resource block usage out of the total number of physical resource blocks.

[0079] In some application embodiments, the link transmission delay may include the average uplink transmission delay between the user equipment (UE) and the base station; the average downlink transmission delay between the UE and the base station; the maximum uplink transmission delay between the UE and the base station; the maximum downlink transmission delay between the UE and the base station; the minimum uplink transmission delay between the UE and the base station; and the minimum downlink transmission delay between the UE and the base station.

[0080] In some application embodiments, the link transmission packet error rate includes at least one of the following: the uplink transmission packet error rate between the UE and the base station, and the downlink transmission packet error rate between the UE and the base station.

[0081] Based on the above application embodiments, the base station includes CU, DU, or RU.

[0082] In one exemplary implementation, resource reporting can be performed at different reporting granularities. For example, resource statistics, resource utilization, link transmission latency, and link transmission packet error rate can be reported based on different communication standards, cells, network fragments, priority data packets, or different types of data packets.

[0083] For example, if the configuration is to generate statistical reports based on different cells, then the base station needs to perform measurements and generate reports for each cell separately, and the cell identifiers need to be included in the reports accordingly.

[0084] If the configuration is based on different network segments for statistical reporting, then the base station needs to perform measurements and generate reports for each different network segment. Accordingly, the network segment identifier also needs to be included in the reports.

[0085] If the configuration is to perform statistical reporting on packets based on different priorities, then the base station needs to classify the packets by priority, perform statistical reporting on packets with different priorities, perform measurements on each packet and generate reports accordingly, and the reports also need to include packet priority identifiers.

[0086] If the system is configured to report statistics for different types of packets, the base station needs to classify the packets by category, perform measurements and statistics on packets with different priorities, and accordingly, the report also needs to include packet type identifiers.

[0087] If the configuration is based on different links for measurement or resource statistics, then the base station will perform measurements on each different link and generate a report. Accordingly, the link identifier also needs to be included in the report.

[0088] If the configuration is based on different communication standards for measurement or resource statistics, then the base station will perform measurements on each different standard and generate reports accordingly. The reports will also need to include the standard identifier.

[0089] Based on the above application embodiments, the resource report is carried in the General Packet Radio Service User Plane Tunneling Protocol header.

[0090] In this embodiment of the application, the resource report can be uploaded by the node to the radio access network management node via the General Packet Radio Service User Plane (GTP-U) header.

[0091] Based on the above application embodiments, it also includes: subscription events for network element registration support to the core network, wherein the subscription events include at least one of the following: node resource utilization rate, number of access terminals, load status, and support capability status.

[0092] In this embodiment of the application, the radio access network management element can register events that it can subscribe to with the network exposure function (NEF) element of the core network. These events may include node resource utilization, number of access terminals, load status, and support capability status, etc. The support capability status may include the support status of sensing capabilities, AI capabilities, and positioning capabilities, etc.

[0093] In one exemplary implementation, referring to Figure 4, the RAN management network element, as an independent NF, accesses the service-based architecture of the core network and simultaneously establishes connections with multiple radio access network elements (base stations) in the wireless network. In this embodiment, the RAN management network element can collect resource information, and the information transmission method may include the following process:

[0094] Step 1: The access network management element sends resource report configuration information to the base station.

[0095] The resource report configuration information shall include at least one of the following: resource report request information; resource report sending conditions.

[0096] Among them, the conditions for sending resource reports include at least one of the following: the report sending cycle; and the conditions that trigger report sending.

[0097] Based on the above application embodiments, the condition for triggering report sending is that the measurement or resource statistics result is greater than the configured threshold value, for example, including at least one of the following:

[0098] The utilization rate of uplink resources is greater than the first threshold;

[0099] The utilization rate of downlink resources is greater than the second threshold;

[0100] The uplink air interface transmission delay is greater than the third threshold;

[0101] The downlink air interface transmission delay is greater than the fourth threshold;

[0102] The packet error rate in uplink air interface transmission is greater than the fifth threshold;

[0103] The packet error rate in downlink air interface transmission is greater than the sixth threshold.

[0104] In some embodiments, the condition for triggering the report is that the measurement or resource statistics result is lower than a configured threshold, for example, including at least one of the following:

[0105] The utilization rate of uplink resources is below the first threshold;

[0106] The utilization rate of downlink resources is below the second threshold;

[0107] The uplink air interface transmission latency is below the third threshold;

[0108] The downlink air interface transmission latency is below the fourth threshold;

[0109] The packet error rate of uplink air interface transmission is lower than the fifth threshold;

[0110] The packet error rate of downlink air interface transmission is below the sixth threshold.

[0111] In one type of embodiment, the condition for triggering a report is that the change in the measurement or resource statistics result compared to the previous report exceeds a configured threshold, for example, including at least one of the following:

[0112] Compared to the previous report, the change in uplink resource utilization is greater than the first threshold;

[0113] Compared to the previous report, the change in downlink resource utilization is greater than the second threshold;

[0114] Compared to the previous report, the change in uplink air interface transmission latency is greater than the third threshold;

[0115] Compared to the previous report, the change in downlink air interface transmission latency is greater than the fourth threshold;

[0116] Compared to the previous report, the change in the packet error rate of uplink air interface transmission is greater than the fifth threshold;

[0117] Compared to the previous report, the change in the packet error rate of downlink air interface transmission is greater than the sixth threshold.

[0118] When configured as a condition to trigger report sending, the resource report configuration information also includes the aforementioned event-related threshold values.

[0119] In some implementations, the access network management element can be configured to allow the base station to report at different granularities, such as based on different cells, different network segments, different priority data packets, or different types of data packets. These different types of packets include data packets, AI training and / or analysis packets, and sensing measurement packets. If the base station has a separate CU and DU architecture, or a separate CU and RU architecture, it can also be configured to report statistics based on different CUs, DUs, or RUs. If the base station supports multiple different standards, such as 4G RAT, 5G RAT, 6G RAT, or non-3GPP related RATs (e.g., Wi-Fi, Bluetooth), it can also be configured to report statistics based on different standards.

[0120] Step 2: When a resource report request is received or the conditions for sending a resource report are met, the base station sends a report to the access network management element.

[0121] The report includes at least one of the following: resource utilization; link transmission latency; link transmission packet error rate.

[0122] The resource utilization rate includes at least one of the following: downlink GBR physical resource block (PRB) utilization rate and uplink GBR physical resource block (PRB) utilization rate.

[0123] The link transmission delay includes at least one of the following:

[0124] Average uplink transmission latency between UE and base station (including CU, DU or RU);

[0125] Average downlink transmission delay between UE and base station (including CU, DU or RU);

[0126] Maximum uplink transmission latency between UE and base station (including CU, DU or RU);

[0127] Maximum downlink transmission delay between UE and base station (including CU, DU or RU);

[0128] Minimum uplink transmission latency between UE and base station (including CU, DU or RU);

[0129] Minimum downlink transmission latency between UE and base station (including CU, DU or RU).

[0130] The link transmission packet error rate includes at least one of the following: uplink transmission packet error rate between the UE and the base station (including CU, DU or RU); downlink transmission packet error rate between the UE and the base station (including CU, DU or RU).

[0131] Based on the granularity configuration instructions in step 1, statistical analysis is performed and the above content is reported for data packets of different standards, cells, network fragments, priorities, or different types of data packets.

[0132] For example, if the configuration is to generate statistical reports based on different cells, then the base station needs to perform measurements and generate reports for each cell separately, and the cell identifiers need to be included in the reports accordingly.

[0133] If the configuration is based on different network segments for statistical reporting, then the base station needs to perform measurements and generate reports for each different network segment. Accordingly, the network segment identifier also needs to be included in the reports.

[0134] If the configuration is to report statistics on packets based on different priorities, then the base station needs to classify the packets by priority, report statistics on packets with different priorities separately, perform measurements on each packet and generate a report. Accordingly, the report also needs to include the packet priority identifier.

[0135] If the system is configured to report statistics for different types of packets, the base station needs to classify the packets by category, perform measurements and statistics on packets with different priorities, and accordingly, the report also needs to include packet type identifiers.

[0136] If the configuration is based on different links for measurement or resource statistics, then the base station will perform measurements on each different link and generate a report. Accordingly, the link identifier also needs to be included in the report.

[0137] If the configuration is based on different standards for measurement or resource statistics, then the base station will perform measurements on each different standard and generate reports accordingly. The standard identifier also needs to be included in the reports.

[0138] In one embodiment, the above-mentioned reporting information is carried in the GTP-U header.

[0139] Step 3: When the RAN management network element receives a request from an NF consumer in the Service-Based Architecture (SBA), it sends a response message.

[0140] The request issued by the NF consumer includes at least one of the following:

[0141] Request to obtain the resource utilization rate of a base station (including CU, DU, or RU) or a group of base stations;

[0142] Request the number of terminals connected to a base station (including CU, DU, or RU) or a group of base stations;

[0143] Request to obtain the load status of a base station (including CU, DU, or RU) or a group of base stations;

[0144] The request is to obtain the capabilities of a base station (including CU, DU, or RU) or a group of base stations, including sensing capabilities, AI capabilities, or positioning capabilities.

[0145] Request the resource utilization rate of a single cell or a group of cells;

[0146] Request the number of terminals connected to a cell or a group of cells;

[0147] Request to obtain the load status of a cell or a group of cells;

[0148] Request the link transmission delay of a cell or a group of cells;

[0149] Request to obtain the link transmission packet error rate of a cell or a group of cells.

[0150] The response information is based on the request information and provides feedback.

[0151] Before step 3, the RAN management network element needs to register the events it can subscribe to with the NEF network element in the SBA architecture, including: resource utilization of base station nodes (including CU, DU or RU), number of connected terminals, load status, and the capabilities supported by the base station nodes, such as sensing capabilities, AI capabilities, and positioning capabilities.

[0152] Figure 5 is a flowchart of another information transmission method provided in an embodiment of this application. This embodiment of the application describes the process of resource coordination and allocation by the radio access network management element based on the above embodiments. Referring to Figure 5, the method provided in this embodiment of the application includes the following steps:

[0153] Step 310: Receive resource usage information from at least one node.

[0154] The resource usage information can be the resource usage information of each node in the access network. This resource usage information can include the load of each node on different cells, different communication standards, different network allocations, different priority data packets, and different types of data packets. The node can include base stations, CUs, DUs, RUs, etc.

[0155] In this embodiment of the application, the access network management element can receive resource usage information of each node in the radio access network.

[0156] Step 320: Send resource allocation information to the node based on resource usage information.

[0157] In this embodiment of the application, after obtaining the resource usage information of one or more nodes, the access network management element can determine the resources used by each node through reasoning calculation and can send resource allocation information to the nodes to meet the resource usage needs of the nodes.

[0158] For example, if the area managed by the access network management element supports multiple communication modes and spectrum sharing of different standards, such as supporting 3GPP 5G and 3GPP 6G to use the same spectrum resources, then the access network management element needs to be responsible for coordinating the resources used by the nodes to avoid resource conflicts or waste between different standards and different cells.

[0159] Step 330: Respond to the core network's service requests based on the node information.

[0160] In some embodiments of the application, the resource allocation information includes at least one of the following:

[0161] Indication of uplink carrier and / or transmission bandwidth for each communication standard of the node;

[0162] Indication of downlink carrier and / or transmission bandwidth for each communication standard of the node;

[0163] Indication of the location of uplink frequency domain resources or time resources for each communication standard of the node;

[0164] Indication of the location of downlink frequency domain resources or time resources for each communication standard of the node;

[0165] Indicator of communication standard for each cell

[0166] Indication of the location of frequency domain resources or time resources for each cell;

[0167] An indication of the communication standard of each cell and the location of the frequency domain resources or time resources used by the communication standard;

[0168] An indication of a resource set for a central user or a resource set for an edge user, wherein the resources in the resource set include at least one of time, frequency domain, or coding.

[0169] In this embodiment of the application, the radio access network management element can allocate resources to nodes through resource allocation information, which may include:

[0170] For each communication standard supported by the node, indicate the expected uplink carrier and / or transmission bandwidth to be used;

[0171] Indicates the expected downlink carrier and / or transmission bandwidth for each communication standard supported by the node;

[0172] For each communication standard supported by the node, indicate the expected location of uplink frequency domain resources or time resources to be used;

[0173] For each communication standard supported by the node, indicate the expected location of downlink frequency domain resources or time resources to be used;

[0174] Indicate the desired communication standard for each cell;

[0175] For each cell, indicate the desired location of frequency domain resources or time resources;

[0176] For each cell, the desired communication standard is indicated, along with the location of the frequency domain resources or time resources to be used under that communication standard.

[0177] Indicates resources for central or peripheral users, including time, frequency domain, or coding, etc.

[0178] Based on the above-described embodiments, managing node information of at least one node within a wireless access network includes: receiving resource allocation request information from at least one node.

[0179] In this embodiment of the application, the node in the radio access network may have intelligent computing capabilities. The node can predict resource usage information and send resource allocation request information to the radio access network management element based on the predicted resource usage information.

[0180] Based on the above application embodiments, it also includes: sending indication information to the node indicating whether or not to agree to the resource allocation information.

[0181] In this embodiment of the application, after receiving resource allocation information sent by a node, the wireless access network management element can send an indication message to the node indicating whether it agrees or disagrees with the resource allocation information.

[0182] For example, a base station node has the ability to perform intelligent computing. It can predict the number of UEs that have established RRC connections in the cell and each CU, DU, RU within the service range, or the number of UEs that are in RRC connected, and inform the access network management element of the above information. After obtaining the above information sent by multiple base station nodes and performing reasoning calculations, the access network management element sends the above-mentioned suggested resource allocation information to the base station.

[0183] In some embodiments, the base station node may have intelligent computing capabilities. The base station node can predict the radio resource status of cells, CUs, and RUs within its service range and can send resource allocation information to the access network management element to transmit the desired radio resource allocation to the radio access network management element. The resource allocation information includes at least one of the following:

[0184] For each standard (RAT) supported by the base station, indicate the uplink carrier and / or transmission bandwidth to be used;

[0185] For each standard supported by the base station, indicate the expected downlink carrier and / or transmission bandwidth to be used;

[0186] For each standard supported by the base station, indicate the location of the uplink frequency domain resources or time resources to be used;

[0187] For each standard supported by the base station, indicate the location of the downlink frequency domain resources or time resources to be used;

[0188] For each cell, the desired network standard is indicated;

[0189] For each cell, indicate the location of the frequency domain resources or time resources to be used;

[0190] For each cell, it indicates the expected standard to be used and the location of the frequency domain resources or time resources expected to be used for that standard.

[0191] Specifically, after obtaining the aforementioned resource allocation information sent by multiple base station nodes and performing reasoning calculations, the access network management element sends the aforementioned suggested resource allocation information to the base station or sends indication information to the base station, indicating whether it agrees to the resource allocation method desired by the base station.

[0192] Based on the above-described embodiments, managing node information of at least one node within a wireless access network includes:

[0193] Receive resource usage information from at least one node and request the core network's network data analysis function to generate resource allocation information based on the resource usage information; obtain resource allocation information sent by the core network.

[0194] In this embodiment of the application, the radio access network management element can receive resource usage information from one or more nodes and request the network data analysis unit function of the core network to analyze and process the resource usage information to obtain resource allocation information. The radio access network management element can also receive resource allocation information issued by the core network.

[0195] In one exemplary implementation, if the access network management element lacks sufficient computing power or reasoning capabilities, it needs to rely on the NWDAF (Network Window Assistance Provider) within the service-oriented architecture. The load or resource utilization information, link transmission delay information, link transmission packet error rate information, predicted UE connection count information, and / or desired resource allocation information obtained from the base station are sent to the NWDAF, along with a request for resource allocation recommendations. The NWDAF performs comprehensive reasoning calculations based on the information obtained from the access network management element and UE mobility information and trajectory information obtained from other NFs (e.g., AMF, SMF, UDM, PCF, etc.) to determine a resource allocation scheme and sends the resource allocation information to the access network management element.

[0196] Figure 6 is a flowchart of another information transmission method provided in an embodiment of this application. This embodiment is a specific embodiment based on the above embodiments, describing the process of network element synchronization of the radio access network management network element. Referring to Figure 6, the method provided in this embodiment specifically includes the following steps:

[0197] Step 410: Obtain the synchronization source information of at least one node.

[0198] The synchronization source information can be information used for clock synchronization. This synchronization source information may include clock priority, clock level, clock progress, clock stability, and Global Navigation Satellite System (GNSS) indication. The GNSS indication is used to indicate whether the base station node has GNSS or whether it is synchronized with GNSS.

[0199] In this embodiment of the application, the wireless access network management element can obtain synchronization source information of at least one node.

[0200] Step 420: Determine the synchronization source based on the synchronization source information and obtain the synchronization source's time information.

[0201] In this embodiment, the wireless access network management element can determine the synchronization source according to the synchronization source information and obtain accurate time information from the synchronization source.

[0202] Step 430: Send the time information to at least one node.

[0203] Specifically, the radio access network management element will obtain the time information and send it to one or more radio access network nodes.

[0204] Step 440: Respond to the core network's service requests based on the node information.

[0205] In the above-mentioned application embodiments, the wireless access network management element has a clock source and manages the node information of at least one node in the wireless network, including: sending the clock information of the clock source to at least one node.

[0206] In the above-mentioned application embodiments, it further includes: determining the numbers of the radio frame, subframe and time slot, and sending at least one number of the radio frame, subframe and time slot to at least one node.

[0207] In this embodiment of the application, the radio access network management element can also determine one or more of the radio frame number, subframe number, and time slot number, and send at least one of the above numbers to the nodes of the radio access network, so that the clock information of the above one or more nodes is synchronized. The synchronization of the clock information includes radio frame number synchronization, subframe number synchronization, and time slot number synchronization.

[0208] In one exemplary implementation, a terminal supporting multiple standards and multiple connections can simultaneously establish connections with multiple base stations (CU, DU, or RU). If the synchronization sources among these base stations are inconsistent, the UE needs to maintain multiple clock information sets, increasing system complexity. Furthermore, if adjacent base stations use different synchronization source clocks, interference can easily occur, significantly impacting terminals at cell edges. For terminals requiring multi-cell assisted positioning, asynchrony between the multiple assisted positioning cells also greatly affects positioning accuracy. To address these issues caused by base station asynchrony, the radio access network management element can assist base stations in synchronization. This process may include the following steps:

[0209] Step 1: The access network management element obtains the synchronization source information of each base station node, including at least one of the following: clock priority, clock level, clock progress, clock stability, and GSNN indication. The GNSS indication can indicate whether the base station node has GNSS or is synchronized with GNSS.

[0210] In one embodiment, after establishing a connection with the access network management element, the base station sends the above information and the base station identifier to the access network management element.

[0211] Step 2: The access network management element determines the synchronization source based on the obtained synchronization source information and requests clock information from the synchronization source.

[0212] In one embodiment, after receiving the synchronization source request clock information, the access network management element sends accurate time information to the access network management element, which then determines the accurate time information after removing link delay.

[0213] Step 3: After determining the time information, the access network management element sends the time information to one or more base stations.

[0214] In one embodiment, the access network management element can send time information after receiving a time acquisition request from the base station, or it can periodically send time information to the base station.

[0215] In another embodiment, if the access network management element has a high-precision clock source, it does not need to obtain clock source information from the base station, but directly sends its own time information to the base station. Furthermore, the access network management element determines the radio frame, subframe, and time slot number, and sends this numbering information to the base station to synchronize the clock information and radio frame, subframe, and time slot number information of all base stations.

[0216] Figure 7 is a flowchart of another information transmission method provided in an embodiment of this application. Taking the Radio Access Network Management Unit configured in the AMF as an example, the information transmission method is described. Referring to Figure 7, the method provided in this embodiment of the application specifically includes the following steps:

[0217] Step 510: Obtain the interface configuration request message sent by the node to the access and mobility management function, wherein the interface configuration request message includes the radio access network node identifier and indication information supporting the receive resource coordination function.

[0218] In this embodiment of the application, when the Radio Access Network Management Unit is configured in the AMF, it can receive interface configuration request messages sent by nodes. The interface configuration request message can carry the radio access network node identifier of the node and indication information that supports receiving resource coordination functions. The indication information can indicate that the node supports receiving resource coordination functions of the AMF.

[0219] Step 520: Send an interface configuration response message to the node to indicate the function of the access network management element.

[0220] In this embodiment of the application, the radio access network management unit can send an interface configuration response message back to the node. The interface configuration response message may include information indicating the functions supported by the access network management element.

[0221] In one embodiment, the interface includes an NG interface, and the interface configuration request message includes an NG interface establishment request.

[0222] Step 530: Manage the node information of at least one node within the wireless access network.

[0223] Step 540: Respond to the core network's service requests based on the node information.

[0224] Based on the above application embodiments, the interface configuration response message also includes an indication of a list of supported capabilities, wherein the list of capabilities includes at least one of the following: support for synchronous clocks, support for resource allocation, and shared resource allocation for multiple communication standards.

[0225] Specifically, the interface configuration response message may include a capability list, which may indicate the capabilities supported by the radio access network management node. The information in the capability list may include information indicating the support for synchronization clocks, resource allocation, and shared resource allocation for multiple communication standards.

[0226] In an exemplary embodiment, Figure 8 is a schematic diagram of the deployment architecture of another radio access network management element provided in this application embodiment. Referring to Figure 8, the RAN management element is integrated into the AMF as a new module, and the AMF, as an NF, is connected to the service-based architecture of the core network, while establishing connections with multiple radio access network elements (CUs) in the wireless network. The AMF that integrates access network management functions can be called an advanced AMF, i.e., A-AMF. During the process of the AMF establishing a connection with the base station, it needs to interact with the base station to determine whether it supports access network management functions. The specific information interaction process can be shown in Figure 9. The base station NG-RAN node can send an interface configuration request message to the AMF, and the AMF sends an interface configuration response message back to the NG-RAN node. The information transmission method provided in this application embodiment may include the following steps:

[0227] Step 1: The base station sends an interface configuration request message to the AMF, which includes: the Global RAN Node ID and the resource coordination function that supports receiving from the AMF;

[0228] Step 2: The AMF sends an interface configuration response message, indicating whether access network management functions are supported. Furthermore, it can also indicate a list of supported capabilities, such as whether synchronous clocks are provided, resource allocation is provided, or multi-standard shared resource allocation is provided.

[0229] Based on the above-described embodiments, when the AMF supports clock synchronization, the AMF can perform the following steps:

[0230] Step 1: The access network management element obtains the synchronization source information of each base station node, including at least one of the following: clock priority, clock level, clock progress, clock stability, and GSNN indication. The GNSS indication can indicate whether the base station node has GNSS or is synchronized with GNSS.

[0231] In one embodiment, after establishing a connection with the access network management element, the base station sends the above information and the base station identifier to the access network management element.

[0232] Step 2: The access network management element determines the synchronization source based on the obtained synchronization source information and requests clock information from the synchronization source.

[0233] In one embodiment, after receiving the synchronization source request clock information, the access network management element sends accurate time information to the access network management element, which then determines the accurate time information after removing link delay.

[0234] Step 3: After determining the time information, the access network management element sends the time information to one or more base stations.

[0235] In one embodiment, the access network management element can send time information after receiving a time acquisition request from the base station, or it can periodically send time information to the base station.

[0236] In another embodiment, if the access network management element has a high-precision clock source, it does not need to obtain clock source information from the base station, but directly sends its own time information to the base station. Furthermore, the access network management element determines the radio frame, subframe, and time slot number, and sends this numbering information to the base station to synchronize the clock information and radio frame, subframe, and time slot number information of all base stations.

[0237] Based on the above-described embodiments, when the AMF supports resource allocation or multi-system shared resource allocation, the AMF can perform the following steps:

[0238] Step 1: The access network management element sends resource report configuration information to the base station.

[0239] The resource report configuration information shall include at least one of the following: resource report request information; resource report sending conditions.

[0240] Among them, the conditions for sending resource reports include at least one of the following: the report sending cycle; and the conditions that trigger report sending.

[0241] Based on the above application embodiments, the condition for triggering report sending is that the measurement or resource statistics result is greater than the configured threshold value, for example, including at least one of the following:

[0242] The utilization rate of uplink resources is greater than the first threshold;

[0243] The utilization rate of downlink resources is greater than the second threshold;

[0244] The uplink air interface transmission delay is greater than the third threshold;

[0245] The downlink air interface transmission delay is greater than the fourth threshold;

[0246] The packet error rate in uplink air interface transmission is greater than the fifth threshold;

[0247] The packet error rate in downlink air interface transmission is greater than the sixth threshold.

[0248] In some embodiments, the condition for triggering the report is that the measurement or resource statistics result is lower than a configured threshold, for example, including at least one of the following:

[0249] The utilization rate of uplink resources is below the first threshold;

[0250] The utilization rate of downlink resources is below the second threshold;

[0251] The uplink air interface transmission latency is below the third threshold;

[0252] The downlink air interface transmission latency is below the fourth threshold;

[0253] The packet error rate of uplink air interface transmission is lower than the fifth threshold;

[0254] The packet error rate of downlink air interface transmission is below the sixth threshold.

[0255] In one type of embodiment, the condition for triggering a report is that the change in the measurement or resource statistics result compared to the previous report exceeds a configured threshold, for example, including at least one of the following:

[0256] Compared to the previous report, the change in uplink resource utilization is greater than the first threshold;

[0257] Compared to the previous report, the change in downlink resource utilization is greater than the second threshold;

[0258] Compared to the previous report, the change in uplink air interface transmission latency is greater than the third threshold;

[0259] Compared to the previous report, the change in downlink air interface transmission latency is greater than the fourth threshold;

[0260] Compared to the previous report, the change in the packet error rate of uplink air interface transmission is greater than the fifth threshold;

[0261] Compared to the previous report, the change in the packet error rate of downlink air interface transmission is greater than the sixth threshold.

[0262] When configured as a condition to trigger report sending, the resource report configuration information also includes the aforementioned event-related threshold values.

[0263] In some implementations, the access network management element can be configured to allow the base station to report at different granularities, such as based on different cells, different network segments, different priority data packets, or different types of data packets. These different types of packets include data packets, AI training and / or analysis packets, and sensing measurement packets. If the base station has a separate CU and DU architecture, or a separate CU and RU architecture, it can also be configured to report statistics based on different CUs, DUs, or RUs. If the base station supports multiple different standards, such as 4G RAT, 5G RAT, 6G RAT, or non-3GPP related RATs (e.g., Wi-Fi, Bluetooth), it can also be configured to report statistics based on different standards.

[0264] Step 2: When a resource report request is received or the conditions for sending a resource report are met, the base station sends a report to the access network management element.

[0265] The report includes at least one of the following: resource utilization; link transmission latency; link transmission packet error rate.

[0266] The resource utilization rate includes at least one of the following: downlink GBR physical resource block (PRB) utilization rate and uplink GBR physical resource block (PRB) utilization rate.

[0267] The link transmission delay includes at least one of the following:

[0268] Average uplink transmission latency between UE and base station (including CU, DU or RU);

[0269] Average downlink transmission delay between UE and base station (including CU, DU or RU);

[0270] Maximum uplink transmission latency between UE and base station (including CU, DU or RU);

[0271] Maximum downlink transmission delay between UE and base station (including CU, DU or RU);

[0272] Minimum uplink transmission latency between UE and base station (including CU, DU or RU);

[0273] Minimum downlink transmission latency between UE and base station (including CU, DU or RU).

[0274] The link transmission packet error rate includes at least one of the following: uplink transmission packet error rate between the UE and the base station (including CU, DU or RU); downlink transmission packet error rate between the UE and the base station (including CU, DU or RU).

[0275] Based on the granularity configuration instructions in step 1, statistical analysis is performed and the above content is reported for data packets of different standards, cells, network fragments, priorities, or different types of data packets.

[0276] For example, if the configuration is to generate statistical reports based on different cells, then the base station needs to perform measurements and generate reports for each cell separately, and the cell identifiers need to be included in the reports accordingly.

[0277] If the configuration is based on different network segments for statistical reporting, then the base station needs to perform measurements and generate reports for each different network segment. Accordingly, the network segment identifier also needs to be included in the reports.

[0278] If the configuration is to report statistics on packets based on different priorities, then the base station needs to classify the packets by priority, report statistics on packets with different priorities separately, perform measurements on each packet and generate a report. Accordingly, the report also needs to include the packet priority identifier.

[0279] If the system is configured to report statistics for different types of packets, the base station needs to classify the packets by category, perform measurements and statistics on packets with different priorities, and accordingly, the report also needs to include packet type identifiers.

[0280] If the configuration is based on different links for measurement or resource statistics, then the base station will perform measurements on each different link and generate a report. Accordingly, the link identifier also needs to be included in the report.

[0281] If the configuration is based on different standards for measurement or resource statistics, then the base station will perform measurements on each different standard and generate reports accordingly. The standard identifier also needs to be included in the reports.

[0282] In one embodiment, the above-mentioned reporting information is carried in the GTP-U header.

[0283] Step 3: When the RAN management network element receives a request from the NF consumer in the SBA architecture, it sends a response message.

[0284] The request issued by the NF consumer includes at least one of the following:

[0285] Request to obtain the resource utilization rate of a base station (including CU, DU, or RU) or a group of base stations;

[0286] Request the number of terminals connected to a base station (including CU, DU, or RU) or a group of base stations;

[0287] Request to obtain the load status of a base station (including CU, DU, or RU) or a group of base stations;

[0288] The request is to obtain the capabilities of a base station (including CU, DU, or RU) or a group of base stations, including sensing capabilities, AI capabilities, or positioning capabilities.

[0289] Request the resource utilization rate of a single cell or a group of cells;

[0290] Request the number of terminals connected to a cell or a group of cells;

[0291] Request to obtain the load status of a cell or a group of cells;

[0292] Request the link transmission delay of a cell or a group of cells;

[0293] Request to obtain the link transmission packet error rate of a cell or a group of cells.

[0294] The response information is based on the request information and provides feedback.

[0295] Before step 3, the RAN management network element needs to register the events it can subscribe to with the NEF network element in the SBA architecture, including: resource utilization of base station nodes (including CU, DU or RU), number of connected terminals, load status, and the capabilities supported by the base station nodes, such as sensing capabilities, AI capabilities, and positioning capabilities.

[0296] Alternatively, the process may include:

[0297] Step 1: The access network management element obtains the capability information of each base station, such as which standards the base station (including CU, DU, RU) supports, whether it supports the coexistence of multiple standards, and whether it supports spectrum sharing of different standards; The access network management element receives information such as load, resource utilization, link transmission delay, and link transmission packet error rate from each base station (CU, DU, RU) or each cell.

[0298] If the area managed by the access network management element supports the coexistence of multiple standards and supports spectrum sharing between different standards, such as supporting 3GPP 5G and 3GPP 6G to use the same spectrum resources, then the access network management element needs to coordinate to avoid resource conflicts or waste between different standards and different cells.

[0299] Step 2: After obtaining the above information and performing reasoning calculations, the access network management element sends at least one of the following suggested resource allocation information to the base station:

[0300] 1. For each standard (RAT) supported by the base station, indicate the available uplink carriers and / or transmission bandwidth;

[0301] 2. For each standard supported by the base station, indicate the downlink carrier and / or transmission bandwidth that can be used;

[0302] 3. For each standard supported by the base station, indicate the location of available uplink frequency domain resources or time resources;

[0303] 4. For each standard supported by the base station, indicate the location of the downlink frequency domain resources or time resources that can be used;

[0304] 5. For each community, specify the applicable network standards;

[0305] 6. For each cell, indicate the location of available frequency domain resources or time resources;

[0306] 7. For each cell, indicate the available network standards and the location of the frequency or time resources available for that standard;

[0307] Furthermore, resources (time, frequency domain, coding) available to central users or resources available to edge users can be specified separately.

[0308] In one embodiment, the base station node has intelligent computing capabilities. It can predict the number of UEs that have established RRC connections in the cell and each CU, DU, RU within the service range, or the number of UEs that are in RRC connected, and inform the access network management element of the above information. After obtaining the above information sent by multiple base station nodes and performing reasoning calculations, the access network management element sends the above-mentioned suggested resource allocation information to the base station.

[0309] In an exemplary embodiment, Figure 10 is a schematic diagram of the deployment architecture of another radio access network management element provided in the embodiments of this application. Referring to Figure 10, the RAN management element is a node at the layer above the base station. It can establish connections with radio access communication nodes of various standards, such as 5G 3GPP base stations, 6G 3GPP base stations, 7G and other future versions of 3GPP base stations. It can also establish connections with other non-3GPP base stations and is responsible for coordinating and managing all radio access communication nodes in a certain area. The RAN management element can be referred to as a radio access network proxy node.

[0310] In this embodiment, the wireless access network proxy node can establish connections with multiple base stations and is responsible for providing clock synchronization, resource allocation, and multi-standard shared resource allocation functions. The implementation steps of the clock synchronization, resource allocation, and multi-standard shared resource allocation functions provided by the wireless access network proxy node can be the same as those in the above embodiments.

[0311] Figure 11 is a flowchart of another information transmission method provided in an embodiment of this application. This embodiment is a specific embodiment based on the above embodiments, describing the deployment of the access network management network element in the wireless access network to realize the information forwarding function. Referring to Figure 11, the method provided in this embodiment specifically includes the following steps:

[0312] Step 610: Manage the node information of at least one node within the wireless access network.

[0313] Step 620: Respond to the core network's service requests based on the node information.

[0314] Step 630: Forward the transmission messages between the core network elements and the radio access network.

[0315] In this embodiment of the application, the access network management network element can forward transmission messages between the core network element and the radio access network. This forwarding may include forwarding messages from the core network element to the terminal, or forwarding messages from the core network element to the base station node of the access network, or forwarding information from the base station node of the access network to other base station nodes.

[0316] Based on the above-described embodiments, forwarding transmission messages between core network elements and the radio access network includes:

[0317] Receive non-access stratum messages transmitted by the receiving node; determine the target node based on the type of non-access stratum message or the target node identification information; forward the non-access stratum message to the target node in the core network.

[0318] In this embodiment of the application, the access network management element is configured in the radio access network and can forward the transmission messages between the core network element and the radio access network. The access network management element can receive non-access stratum messages uploaded by nodes and identify the type or target node identifier of the non-access stratum message. It can determine the target node according to the type or target node identifier and forward the received non-access stratum message to the target node.

[0319] Based on the above-described embodiments, forwarding transmission messages between core network elements and the radio access network includes:

[0320] The node receives a non-access stratum message and a target node identifier transmitted by the node, wherein the target node identifier is determined by the node based on the type of the non-access stratum message; and transmits the non-access stratum message to the target node according to the target node identifier.

[0321] In this embodiment of the application, the access network management network element configured in the wireless access network can receive non-access stratum messages and target node identifiers transmitted by nodes within the wireless access network. The target node identifier is determined by the node through the type of non-access stratum message. The target node can be determined according to the target node identifier, and the non-access stratum message can be transmitted to the target node.

[0322] Based on the above-described embodiments, forwarding transmission messages between core network elements and the radio access network includes:

[0323] Obtain the non-access stratum message issued by the core network element; transmit the non-access stratum message to the target terminal through the nodes of the wireless access network.

[0324] In this embodiment of the application, the radio access network management element can be configured in the radio access network, receive non-access stratum messages issued by the core network element, and transmit the non-access stratum messages to the target terminal through the radio access network.

[0325] Based on the above-described embodiments, non-access stratum messages are transmitted via radio resource control messages, which also include at least one of a non-access stratum message type indicator and a core network user plane element identifier.

[0326] In this embodiment of the application, non-access stratum messages can be transmitted through radio resource control messages. The radio resource control messages may also include non-access stratum message type indications or core network user plane element identifiers. The radio resource control messages can be used to identify the type of non-access stratum messages or target node identifiers.

[0327] In some application embodiments, the target terminal determines the message type or bearer mapping configuration relationship of the node based on the non-access stratum message.

[0328] In this embodiment of the application, the target terminal to which the non-access stratum message is transmitted can be determined by the node based on the message type or bearer mapping configuration relationship of the non-access stratum message. The bearer mapping configuration relationship can include the correspondence between different bearers and different terminals. The base station can determine the target terminal corresponding to the non-access stratum message by receiving the bearer of the non-access stratum message. It is understood that the bearer can include data bearer, control bearer or other bearers, etc.

[0329] Based on the above application embodiments, the message types of non-access stratum messages include at least one of the following: user plane type messages, control plane type messages, data plane type messages, and computation plane type messages.

[0330] In an exemplary implementation, a radio access network management element can be configured in the radio access network, as shown in Figure 10. This radio access network management element can act as a radio access network proxy node. This radio access network proxy node can directly establish connections with the network elements responsible for managing access control (e.g., AMF), the network elements responsible for managing session functions (e.g., SMF), and other network elements (e.g., the network elements responsible for managing positioning functions) in the core network architecture. When the radio access network proxy node receives messages sent from various base stations to the core network, it needs to perform routing functions to determine which core network element the received message should be forwarded to. This message forwarding process can include the following scheme:

[0331] 1. The base station performs message identification:

[0332] When the base station receives a Non-Access Stratum (NAS) message from the UE, it identifies the target node of the message based on the type of the NAS message, and sends the NAS message and the core network target node identifier together to the radio access network proxy node. The proxy node then sends the message to the core network node based on the identifier information.

[0333] 2. The wireless access network proxy node performs message identification:

[0334] After receiving a NAS message forwarded from a base station, the wireless access network proxy node identifies the target node based on the type of the NAS message or the target node identification information in the NAS message, and then sends the NAS message to the target node in the core network.

[0335] Furthermore, to facilitate the identification of the target node of the NAS message by the base station and the radio access network agent node, the UE can add some indications.

[0336] In one embodiment, the terminal can add a NAS message type indicator to the RRC message carrying the NAS message. The NAS message type indicator can be used to instruct the NAS message to be sent to the core network user plane element. When the UE establishes a connection with multiple core network user planes, the RRC message can also carry the identifier of the core network user plane element.

[0337] In one embodiment, the terminal adds the identifier of the core network element associated with the NAS message to the RRC message carrying the NAS message. In another embodiment, the base station can configure bearers for transmitting various NAS messages for the UE. For example, it can instruct the UE to use a first bearer to transmit NAS messages associated with core network control plane elements, and instruct the UE to use a second bearer to transmit NAS messages associated with core network user plane elements. Furthermore, if the UE has multiple NAS messages, and different NAS messages are sent to different core network elements, such as control panel elements, user plane elements, session management elements, mobility management elements, data management elements, etc., then the UE can report all supported NAS message types or associated core network element identifiers. After receiving this message, the base station configures different mapping relationships between NAS messages and bearers for the UE. Subsequently, the UE selects the associated bearer for transmission of the NAS message based on this configuration information.

[0338] In an exemplary implementation, a radio access network management element can be configured in the radio access network, as shown in Figure 10. This radio access network management element can act as a radio access network proxy node. In addition to coordinating resources between different radio access communication nodes, the access network proxy node also needs to forward messages between the UE and other network elements of the core network.

[0339] For downlink messages transmitted from core network user plane elements to the UE, the following methods can be adopted:

[0340] Method 1: After receiving the message sent to the UE by the core network, the access network proxy node forwards the message and message type to the radio access network element (base station). The message type includes at least one of the following: NAS message type; core network element identifier that sent the NAS message; wherein the NAS message type includes: user plane type message, control plane type message, data plane type message, computing plane type message, etc.

[0341] After identifying the target UE and message type of the NAS message, the base station transmits the message to the UE. In one example, the base station carries the type of the NAS message or the identifier of the core network element that sent the NAS message in the RRC message. Subsequently, the UE can confirm the core network element associated with the message or the type of the message based on this identifier.

[0342] In another example, the base station sends the downlink message to the UE in at least one of the following ways: a Protocol Data Unit (PDU) Service Data Adaptation Protocol (SDAP) header, a data PDU SDAP header, or a new protocol layer PDU header.

[0343] Method 2: The access network proxy node establishes a communication tunnel with the wireless network access network element (e.g., base station). This communication tunnel is specifically used to transmit information related to the UE. When the access network proxy node obtains NAS messages related to the UE, it transmits the NAS messages and NAS message types to the base station through the tunnel. The base station identifies the target UE based on the tunnel identifier and then transmits the NAS messages and NAS message types to the UE.

[0344] In one example, the base station carries the type of the NAS message or the identifier of the core network element that sent the NAS message in the RRC message. The UE can then use this identifier to confirm the core network element associated with the message or the type of the message.

[0345] In another example, the base station sends the downlink message to the UE in at least one of the following ways: control PDU SDAP header, data PDU SDAP, new protocol layer PDU header.

[0346] In another example, the base station configures the mapping relationship between bearers (including data bearers, control bearers, or other new bearers) and NAS messages of core network elements. For example, the base station configures NAS messages of core network user plane elements through a first bearer, NAS messages of core network session management elements through a second bearer, NAS messages of core network computing elements through a third bearer, NAS messages of core network location management elements through a fourth bearer, and so on, and sends the configuration information to the UE. Subsequently, when NAS messages of core network elements arrive, the base station sends them to the UE through the associated bearer. The UE determines the type of NAS message or the core network element that sent the message based on the received bearer.

[0347] Figure 12 is a flowchart of another information transmission method provided in an embodiment of this application. This embodiment is a specific embodiment based on the above embodiment, describing the process by which the access network management element obtains analysis and prediction information from the Network Data Analysis Function (NWDAF). Referring to Figure 12, the method provided in this embodiment specifically includes the following steps:

[0348] Step 710: Manage the node information of at least one node within the wireless access network.

[0349] Step 720: Respond to the core network's service requests based on the node information.

[0350] Step 730: Send an analysis request to the network data analysis function.

[0351] In this embodiment of the application, the access network management element can send an analysis request to the network data analysis function to request the network data analysis function to perform predictive analysis on the network element nodes of the wireless access network. The analysis request can carry information indicating the predicted network element nodes. The analysis request can include a request to predict the load, a request to predict the number of access terminals, a request to predict the resource requirements under each communication standard, etc.

[0352] Step 740: Obtain the analysis results provided by the network analysis function, wherein the analysis results are determined based on the data collected by the network analysis function.

[0353] In this embodiment, the network analysis function can collect data from the NF provider and analyze the requests from the access network management element based on the collected data to obtain analysis results. The network analysis function can then feed these results back to the access network management element, which can receive the analysis results provided by the network analysis function. The data collected by the network analysis function when generating the analysis results may include historical load information of the wireless access point, historical resource utilization information, and the number of historical terminal access terminals.

[0354] Based on the above application embodiments, the analysis request includes indication information for prediction information, wherein the prediction information includes at least one of the following:

[0355] Uplink and / or downlink load forecast information;

[0356] Forecast information on resources required for uplink and / or downlink;

[0357] Predicted number of access terminals;

[0358] Uplink and / or downlink load prediction information for each of the multiple communication standards;

[0359] Under multiple communication standards, the uplink and / or downlink resource prediction information for each communication standard, wherein the resources in the resource prediction information include at least one of bandwidth resources, radio resource block resources, carrier resources and time domain resources;

[0360] Predicted number of access terminals for each of the multiple communication standards.

[0361] In this embodiment of the application, the analysis request from the radio access network management element to the network analysis function includes at least indication information for prediction information. This indication information can indicate the prediction information required by the radio access network management element. The prediction information may include uplink and / or downlink load prediction information; uplink and / or downlink resource prediction information; access terminal number prediction information; uplink and / or downlink load prediction information for each of the multiple communication standards; uplink and / or downlink resource prediction information for each of the multiple communication standards, wherein the resources include at least one of bandwidth resources, radio resource block resources, carrier resources, and time domain resources; and access terminal number prediction information for each of the multiple communication standards, etc.

[0362] Based on the above-described embodiments, the data collected includes at least one of the following:

[0363] Historical uplink and / or downlink load information for each wireless access node;

[0364] Historical uplink and / or downlink resource utilization information for each wireless access node;

[0365] Historical predictions of the number of access terminals for each wireless access node;

[0366] Historical uplink and / or downlink load information of each wireless access node under various communication standards;

[0367] Under multiple communication standards, the historical uplink and / or downlink resource utilization information of each wireless access node for each communication standard;

[0368] Historical access terminal prediction information for each wireless access node under various communication standards;

[0369] Historical movement information of terminals within the area;

[0370] Historical throughput information of terminals within the region.

[0371] In an exemplary embodiment, FIG13 is an example diagram of an information transmission method provided in an embodiment of this application. Referring to FIG13, when the access network management element needs to obtain analysis and prediction information from the NWDAF, it can send an analysis request to the NWDAF as an NF consumer. The process is as follows:

[0372] Step 1: When the RAN management network element acts as a consumer NF, it sends an analysis request to the NWDAF;

[0373] The analysis request includes an analysis ID, which indicates a request to analyze predictive information of a radio access network element, including at least one of the following:

[0374] Uplink and / or downlink load forecast information;

[0375] Forecast information on resources required for uplink and / or downlink;

[0376] Predicted number of access terminals;

[0377] Uplink and / or downlink load prediction information for each of the multiple standards;

[0378] Forecast information on the uplink and / or downlink resource requirements for each of the multiple standards;

[0379] Predicted number of access terminals for each of the multiple standards;

[0380] The resources in the required resource prediction information include bandwidth resources, radio resource block resources, carrier resources, time domain resources, etc.

[0381] Step 2: NWDAF collects data from the NF provider;

[0382] The collected data includes at least one of the following:

[0383] Historical uplink and / or downlink load information for each wireless access node;

[0384] Historical uplink and / or downlink resource utilization information for each wireless access node;

[0385] Historical predictions of the number of access terminals for each wireless access node;

[0386] Historical uplink and / or downlink load information for each wireless access node under various standards;

[0387] Under multiple standards, the historical uplink and / or downlink resource utilization information of each wireless access node for each standard;

[0388] Historical access terminal prediction information for each wireless access node under various standards;

[0389] Historical movement information of terminals within the area;

[0390] Historical throughput information of terminals within the region.

[0391] Step 3: NWDAF provides analysis results to the access network management elements.

[0392] The analysis result is one or more analysis results requested in step 1.

[0393] Afterwards, the access network management element can allocate resources to each wireless access node based on the analysis results.

[0394] Based on the above-described embodiments, the method further includes: obtaining device information of the terminal device.

[0395] In this embodiment of the application, the access network management element can obtain terminal device information from other network elements in the core network. The device information can indicate the terminal device status and may include at least one of the following: expected user equipment activity behavior, mobility mode information, expected handover behavior, expected user equipment mobility, and expected user equipment movement trajectory.

[0396] In some embodiments of the application, obtaining device information of the terminal device includes at least one of the following:

[0397] Predict device information based on measurement reports from terminal devices; obtain device information from other functional network elements within the core network; obtain device information predicted by nodes in the radio access network.

[0398] In the embodiments of this application, the device information of the terminal device can be predicted and generated by the radio access network through the measurement report of the terminal device, or it can be obtained by other functional network elements in the core network, or it can be obtained by the radio access network within the radio access network node. The device information can be predicted and generated by the radio access network node.

[0399] Based on the above-described embodiments, it also includes at least one of the following:

[0400] Send user equipment handover instructions to the terminal device; send prediction information to the source service node of the terminal device; send the handover decision based on the prediction information to the source service node or target service node of the terminal device.

[0401] In this embodiment, the radio access network management element can send a user equipment handover instruction to the terminal device, enabling the terminal device to change the connected radio access network node. Alternatively, it can send the handover decision corresponding to the prediction information to the source service node or target service node of the terminal device, so that the source service node and target service node support the terminal device to handover.

[0402] In one exemplary implementation, the access network node determines, based on the measurement report sent by the UE, that the UE may need to change its access network node (CU, DU, or RU). If so, it sends the measurement report to the access network management element, or the access network management element sends measurement report reporting conditions (these conditions can be consistent with the conditions used by the UE to report measurement reports). The access network then sends measurement reports that meet the conditions to the access network management element. Further, the access network management element obtains UE information from other network elements in the service-oriented architecture, including:

[0403] "Expected UE activity behavior", for example, the expected pattern of user equipment changing between connection management connected state and connection management idle state;

[0404] Mobility pattern information, such as user historical movement records, user behavior analysis, movement trajectory records, etc.

[0405] "Expected HO behavior", for example: predicting the time interval between CU / DU handovers for users.

[0406] "Expected UE mobility", for example: predicting whether the user is moving or stationary.

[0407] "Expected UE moving trajectory": Predicted user movement trajectory information.

[0408] The aforementioned information (such as Expected HO behavior) can also be derived by the access network management element itself.

[0409] The access network management element, combining the measurement reports obtained from the UE, the resource status reports obtained from each access network node (including CU / DU / RU), and the UE behavior prediction information obtained from the core network, can perform at least one of the following:

[0410] 1. Decide whether to initiate a UE handover:

[0411] When the access network management element decides to handover, it sends a handover request or connection establishment request to the target access network node and a UE connection release indication to the source access network node. Specifically, if the UE changes its DU or RU but not its CU, the connection establishment request and connection release information are sent to the same access network node. Optionally, if the target access node refuses to perform the handover or establish a connection with the UE, it sends a reason for refusal to the access network management element, and the handover is terminated.

[0412] 2. Assist UE handover decision:

[0413] The access network management element obtains the UE information from other network elements in the service architecture and sends it to the UE's source service node, or sends the suggested handover decision (including handover indication and target access node identifier) ​​to the source service node. If the source access node decides to initiate a handover, it sends a handover confirmation to the access network management element, and then the access network management element sends the handover request to the target access node.

[0414] After receiving the handover request, the target access node needs to provide RRC configuration information to the UE. This RRC configuration information can then be forwarded to the source access node through the RAN management network element, and the source access node will then send it to the UE.

[0415] Figure 14 is a schematic diagram of an information transmission device provided in an embodiment of this application. This device can execute the information transmission method provided in any embodiment of this application, and possesses the corresponding functional modules and beneficial effects of the method. This device can be implemented by software and / or hardware. The device provided in this embodiment specifically includes:

[0416] Information management module 910 is used to manage node information of at least one node within the wireless access network;

[0417] The request-response module 920 is used to respond to the core network's service requests based on the node information.

[0418] Based on the above-described embodiments, the wired access network management element is configured in the wireless access network or the core network.

[0419] Based on the above-described embodiments, the information management module 910 includes:

[0420] The report configuration unit is used to send resource report configuration information to nodes.

[0421] The report receiving unit is used to receive the resource reports from the node.

[0422] Based on the above application embodiments, the resource report configuration information includes at least one of the following: resource report request information, or resource report sending conditions.

[0423] Based on the above application embodiments, the resource report configuration information is the resource report sending condition, and the resource report configuration information includes at least one of the following: report sending period, or conditions that trigger report sending.

[0424] Based on the above application embodiments, the resource report sending conditions include conditions that trigger report sending, and the conditions that trigger report sending include at least one of the following:

[0425] The measurement or resource statistics result is higher than the configured threshold value;

[0426] The measurement or resource statistics result is lower than the configured threshold value;

[0427] The measurement or resource statistics result has changed more than the configured threshold value compared to the previous resource report.

[0428] Based on the above application embodiments, the resource report configuration information also includes the value of the threshold value.

[0429] Based on the above application embodiments, the resource report configuration information further includes: the report granularity of the resource report, wherein the report granularity includes at least one of the following: cell, network segmentation, data packet priority, data packet type, centralized unit, distributed unit, and communication standard.

[0430] Based on the above application embodiments, the resource report includes at least one of the following: resource utilization rate, link transmission latency, and link transmission packet error rate.

[0431] Based on the above application embodiments, the resource report is carried in the General Packet Radio Service User Plane Tunneling Protocol header.

[0432] Based on the above application embodiments, the request response module 920 includes:

[0433] The request acquisition unit is used to acquire requests from network function consumers in the core network.

[0434] The response feedback unit is used to provide the network function consumer with response information for the request based on the resource report.

[0435] Based on the above application embodiments, the request includes at least one of the following: a request to obtain resource utilization at a specified resource granularity;

[0436] A request to obtain the number of access terminals of at least one of the nodes;

[0437] A request to obtain the load status of at least one of the nodes;

[0438] A request to obtain the support capability status of at least one of the nodes, wherein the support capability status includes at least one of perception capability status, artificial intelligence capability status, or positioning capability status;

[0439] A request to obtain the resource utilization rate of at least one cell;

[0440] Request to obtain the number of access terminals in at least one cell

[0441] A request to obtain the load status of at least one cell;

[0442] A request to obtain the link transmission latency of at least one cell;

[0443] A request to obtain the link transmission packet error rate of at least one cell.

[0444] Based on the above application embodiments, it further includes: an event subscription module, used to register supported subscription events with the network open function network elements of the core network, wherein the subscription events include at least one of the following: node resource utilization rate, number of access terminals, load status and support capability status.

[0445] Based on the above application embodiments, the information management module 910 is further configured to: receive resource usage information of at least one of the nodes, and send resource allocation information to the nodes according to the resource usage information.

[0446] Based on the above application embodiments, the information management module 910 is further configured to: receive resource allocation request information from at least one of the nodes.

[0447] Based on the above-described embodiments, the resource allocation information includes at least one of the following:

[0448] Indication of uplink carrier and / or transmission bandwidth for each communication standard of the node;

[0449] Indication of downlink carrier and / or transmission bandwidth for each communication standard of the node;

[0450] Indication of the location of uplink frequency domain resources or time resources for each communication standard of the node;

[0451] Indication of the location of downlink frequency domain resources or time resources for each communication standard of the node;

[0452] Indicator of communication standard for each cell

[0453] Indication of the location of frequency domain resources or time resources for each cell;

[0454] An indication of the communication standard of each cell and the location of the frequency domain resources or time resources used by the communication standard;

[0455] An indication of a resource set for a central user or a resource set for an edge user, wherein the resources in the resource set include at least one of time, frequency domain, or coding.

[0456] Based on the above application embodiments, it further includes: an information indication unit, used to send indication information of agreeing or disagreeing with the resource allocation information to the node.

[0457] In some embodiments, the information management module 910 is further configured to: receive resource usage information of at least one of the nodes, and request the network data analysis function of the core network to generate the resource allocation information based on the resource usage information; and obtain the resource allocation information sent by the core network.

[0458] In some embodiments, the information management module 910 is further configured to: obtain synchronization source information of at least one of the nodes; determine a synchronization source based on the synchronization source information and obtain time information of the synchronization source; and send the time information to at least one of the nodes.

[0459] In some embodiments, the information management module 910 is further configured to: send the clock information of the clock source to at least one of the nodes.

[0460] Based on the above-mentioned application embodiments, the device further includes: a synchronization module, used to determine the numbers of the radio frame, the subframe, and the time slot, and send at least one number of the radio frame, the subframe, and the time slot to at least one of the nodes.

[0461] Based on the above-described embodiments, the radio access network management element is integrated into the access and mobility management function of the core network. The device further includes: a configuration module, configured to acquire an interface configuration request message sent by a node to the access and mobility management function, wherein the interface configuration request message includes a radio access network node identifier and indication information supporting the resource coordination function; and to send an interface configuration response message to the node to indicate the function of the access network management element.

[0462] Based on the above application embodiments, the interface configuration response message also includes an indication of a list of supported capabilities, wherein the list of capabilities includes at least one of the following: support for synchronous clocks, support for resource allocation, and shared resource allocation for multiple communication standards.

[0463] Based on the above-described embodiments, the node includes at least one of the following: a base station, a centralized unit, a distributed unit, a radio frequency unit, a virtual node representing a resource set, and a cell.

[0464] Based on the above-described embodiments, the apparatus further includes: an information forwarding module, used to forward transmission messages between core network elements and the wireless access network.

[0465] Based on the above application embodiments, the information forwarding module is used to: receive non-access stratum messages transmitted by the node; determine the target node according to the type of the non-access stratum message or target node identification information; and forward the non-access stratum message to the target node in the core network.

[0466] Based on the above application embodiments, the information forwarding module is configured to: receive a non-access stratum message transmitted by the node and a target node identifier, wherein the target node identifier is determined by the node based on the type of the non-access stratum message; and transmit the non-access stratum message to the target node according to the target node identifier.

[0467] Based on the above application embodiments, the information forwarding module is used to: obtain non-access stratum messages issued by the core network element; and transmit the non-access stratum messages to the target terminal through the nodes of the wireless access network.

[0468] Based on the above application embodiments, non-access stratum messages are transmitted through radio resource control messages, wherein the radio resource control messages include at least one of a non-access stratum message type indication and a core network user plane element identifier.

[0469] Based on the above application embodiments, the target terminal determines the message type or bearer mapping configuration relationship of the non-access stratum message at the node.

[0470] Based on the above application embodiments, the message types of non-access stratum messages include at least one of the following: user plane type messages, control plane type messages, data plane type messages, and computation plane type messages.

[0471] Based on the above-described embodiments, the apparatus further includes: an analysis and processing module, configured to send an analysis request to a network data analysis function; and obtain analysis results provided by the network analysis function, wherein the analysis results are determined based on the data collected by the network analysis function.

[0472] Based on the above application embodiments, the analysis request includes indication information for prediction information, wherein the prediction information includes at least one of the following:

[0473] Uplink and / or downlink load forecast information;

[0474] Forecast information on resources required for uplink and / or downlink;

[0475] Predicted number of access terminals;

[0476] Uplink and / or downlink load prediction information for each of the multiple communication standards;

[0477] Under multiple communication standards, the uplink and / or downlink resource prediction information for each communication standard, wherein the resources in the resource prediction information include at least one of bandwidth resources, radio resource block resources, carrier resources and time domain resources;

[0478] Predicted number of access terminals for each of the multiple communication standards.

[0479] Based on the above-described embodiments, the data collected includes at least one of the following:

[0480] Historical uplink and / or downlink load information for each wireless access node;

[0481] Historical uplink and / or downlink resource utilization information for each wireless access node;

[0482] Historical predictions of the number of access terminals for each wireless access node;

[0483] Historical uplink and / or downlink load information of each wireless access node under various communication standards;

[0484] Under multiple communication standards, the historical uplink and / or downlink resource utilization information of each wireless access node for each communication standard;

[0485] Historical access terminal prediction information for each wireless access node under various communication standards;

[0486] Historical movement information of terminals within the area;

[0487] Historical throughput information of terminals within the region.

[0488] Based on the above-described embodiments, the device further includes: an information acquisition module, used to acquire device information of the terminal device.

[0489] Based on the above-described embodiments, the device information includes at least one of the following:

[0490] Expected user equipment activity behavior, mobility mode information, expected handover behavior, expected user equipment mobility, and expected user equipment movement trajectory.

[0491] Based on the above-described embodiments, the information acquisition module is specifically used for at least one of the following:

[0492] The device information is predicted based on the measurement report of the terminal device; the device information is obtained from other functional network elements within the core network; and the device information predicted by the nodes of the radio access network is obtained.

[0493] Based on the above-described embodiments, the device is further configured to: send a user equipment handover instruction to the terminal device; send the prediction information to the source service node of the terminal device; and send a handover decision based on the prediction information to the source service node or target service node of the terminal device.

[0494] Figure 15 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device includes a processor 10, a memory 11, an input device 12, and an output device 13. The number of processors 10 in the electronic device can be one or more. Figure 15 shows one processor 10 as an example. The processor 10, memory 11, input device 12, and output device 13 in the electronic device can be connected by a bus or other means. Figure 15 shows a connection via a bus as an example.

[0495] The memory 11, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the modules corresponding to the device in this embodiment (information management module 910 and request response module 920). The processor 10 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 11, thereby realizing the above-described information transmission method.

[0496] The memory 11 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 11 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 11 may further include memory remotely located relative to the processor 10, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0497] Input device 12 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the electronic device. Output device 13 may include display devices such as a display screen.

[0498] This application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform an information transmission method, the method comprising:

[0499] Manage node information for at least one node within the wireless access network;

[0500] The node information is used to respond to the core network's service requests.

[0501] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0502] It is worth noting that in the embodiments of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0503] Those skilled in the art will understand that all or some of the steps, apparatuses, or functional modules / units in the methods disclosed above can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0504] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. The corresponding software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital video disc (DVD) or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0505] The above description, with reference to the accompanying drawings, illustrates optional embodiments of this application and does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. An information transmission method, applied to a wireless access network management element, the method comprising: Manage node information for at least one node within the wireless access network; The node information is used to respond to the core network's service requests.

2. The method according to claim 1, wherein, The wireless access network management element is configured in the wireless access network or the core network.

3. The method according to claim 1, wherein, The management of node information for at least one node within the wireless access network includes: Send resource report configuration information to the node; Receive resource reports from the node.

4. The method according to claim 3, wherein, The resource report configuration information includes at least one of the following: resource report request information, or resource report sending conditions.

5. The method according to claim 3, wherein, The resource report configuration information defines the conditions for sending resource reports, and the resource report configuration information includes at least one of the following: Report sending cycle, or conditions that trigger report sending.

6. The method according to claim 4, wherein, The resource report sending conditions include conditions that trigger report sending, and the conditions that trigger report sending include at least one of the following: The measurement or resource statistics result is higher than the configured threshold value; The measurement or resource statistics result is lower than the configured threshold value; The measurement or resource statistics result has changed more than the configured threshold value compared to the previous resource report.

7. The method according to claim 6, wherein, The resource report configuration information also includes the value of the threshold.

8. The method according to claim 6, wherein, The resource report configuration information also includes: The reporting granularity of the resource report includes at least one of the following: cell, network fragmentation, data packet priority, data packet type, centralized unit, distributed unit, and communication standard.

9. The method according to claim 3, wherein, The resource report includes at least one of the following: Resource utilization, link transmission latency, and link transmission packet error rate.

10. The method according to claim 3, wherein, The resource report is carried in the General Packet Radio Service User Plane Tunneling Protocol header.

11. The method according to claim 3, wherein, The step of responding to the core network service request based on the node information includes: Obtain network function requests from consumers in the core network; The network function consumer is fed back the response information of the request based on the resource report.

12. The method according to claim 11, wherein, The request includes at least one of the following: A request to obtain resource utilization at a specified resource granularity; A request to obtain the number of access terminals of at least one of the nodes; A request to obtain the load status of at least one of the nodes; A request to obtain the support capability status of at least one of the nodes, wherein the support capability status includes at least one of perception capability status, artificial intelligence capability status, or positioning capability status; A request to obtain the resource utilization rate of at least one cell; Request to obtain the number of access terminals in at least one cell A request to obtain the load status of at least one cell; A request to obtain the link transmission latency of at least one cell; A request to obtain the link transmission packet error rate of at least one cell.

13. The method according to claim 3, further comprising: The network open function element registration supports subscription events to the core network, and the subscription events include at least one of the following: node resource utilization, number of access terminals, load status, and support capability status.

14. The method according to claim 1, wherein, The management of node information for at least one node within the wireless access network includes: Receive resource usage information from at least one of the nodes. Resource allocation information is sent to the node based on the resource usage information.

15. The method according to claim 1, wherein, The management of node information for at least one node within the wireless access network includes: Receive resource allocation request information from at least one of the nodes.

16. The method according to claim 14, wherein, The resource allocation information includes at least one of the following: Indication of uplink carrier and / or transmission bandwidth for each communication standard of the node; Indication of downlink carrier and / or transmission bandwidth for each communication standard of the node; Indication of the location of uplink frequency domain resources or time resources for each communication standard of the node; Indication of the location of downlink frequency domain resources or time resources for each communication standard of the node; Indicator of communication standard for each cell Indication of the location of frequency domain resources or time resources for each cell; An indication of the communication standard of each cell and the location of the frequency domain resources or time resources used by the communication standard; An indication of a resource set for a central user or a resource set for an edge user, wherein the resources in the resource set include at least one of time, frequency domain, or coding.

17. The method of claim 14, further comprising: Send an indication message to the node indicating whether you agree to or disagree with the resource allocation information.

18. The method according to claim 1, wherein, The management of node information for at least one node within the wireless access network includes: Receive resource usage information from at least one of the nodes, and request the network data analysis function of the core network to generate the resource allocation information based on the resource usage information; Obtain the resource allocation information sent by the core network.

19. The method according to claim 1, wherein, The node information for managing at least one node within the wireless network includes: Obtain synchronization source information for at least one of the nodes; The synchronization source is determined based on the synchronization source information, and the time information of the synchronization source is obtained; The time information is sent to at least one of the nodes.

20. The method according to claim 1, wherein, The wireless access network management element has a clock source, and the node information of at least one node within the managed wireless network includes: The clock information of the clock source is sent to at least one of the nodes.

21. The method according to claim 19 or 20, further comprising: The number of the radio frame, the number of the subframe, and the number of the time slot are determined, and at least one of the number of the radio frame, the number of the subframe, and the number of the time slot is sent to at least one of the nodes.

22. The method according to claim 2, wherein, The radio access network management element is integrated into the access and mobility management functions of the core network, and also includes: The interface configuration request message sent by the node to the access and mobility management function includes a radio access network node identifier and indication information supporting the receive resource coordination function. Send an interface configuration response message to the node to indicate the function of the access network management element.

23. The method according to claim 22, wherein, The interface configuration response message also includes a list of supported capabilities, which includes at least one of the following: support for synchronous clocks, support for resource allocation, and shared resource allocation for multiple communication standards.

24. The method according to claim 1, wherein, The nodes include at least one of the following: base station, centralized unit, distributed unit, radio frequency unit, virtual node representing a resource set, and cell.

25. The method according to claim 1, further comprising: Forward transmission messages between core network elements and the wireless access network.

26. The method according to claim 25, wherein, The forwarding of transmission messages between the core network element and the radio access network includes: Receive non-access stratum messages transmitted by the node; The target node is determined based on the type of the non-access stratum message or the target node identification information; The non-access stratum message is forwarded to the target node in the core network.

27. The method according to claim 25, wherein, The forwarding of transmission messages between the core network element and the radio access network includes: The node receives a non-access stratum message and a target node identifier transmitted by the node, wherein the target node identifier is determined by the node based on the type of the non-access stratum message; Transmit the non-access stratum message to the target node according to the target node identifier.

28. The method according to claim 25, wherein, The forwarding of transmission messages between the core network element and the radio access network includes: Obtain non-access stratum messages issued by the core network element; The non-access stratum message is transmitted to the target terminal through the nodes of the wireless access network.

29. The method according to any one of claims 26-28, wherein, The non-access stratum messages are transmitted via radio resource control messages, which include at least one of a non-access stratum message type indicator and a core network user plane element identifier.

30. The method according to claim 28, wherein, The target terminal is determined by the node based on the message type or bearer mapping configuration relationship of the non-access stratum message.

31. The method according to any one of claims 26-28, wherein, The message types of the non-access stratum messages include at least one of the following: user plane type messages, control plane type messages, data plane type messages, and compute plane type messages.

32. The method according to claim 1, further comprising: Send an analysis request to the network data analysis function; Obtain the analysis results provided by the network analysis function, wherein the analysis results are determined based on the data collected by the network analysis function.

33. The method according to claim 32, wherein, The analysis request includes indication information for prediction information, which includes at least one of the following: Uplink and / or downlink load forecast information; Forecast information on resources required for uplink and / or downlink; Predicted number of access terminals; Uplink and / or downlink load prediction information for each of the multiple communication standards; Under multiple communication standards, the uplink and / or downlink resource prediction information for each communication standard, wherein the resources in the resource prediction information include at least one of bandwidth resources, radio resource block resources, carrier resources and time domain resources; Predicted number of access terminals for each of the multiple communication standards.

34. The method according to claim 32, wherein, The collected data includes at least one of the following: Historical uplink and / or downlink load information for each wireless access node; Historical uplink and / or downlink resource utilization information for each wireless access node; Historical predictions of the number of access terminals for each wireless access node; Historical uplink and / or downlink load information of each wireless access node under various communication standards; Under multiple communication standards, the historical uplink and / or downlink resource utilization information of each wireless access node for each communication standard; Historical access terminal prediction information for each wireless access node under various communication standards; Historical movement information of terminals within the area; Historical throughput information of terminals within the region.

35. The method according to claim 1, further comprising: Obtain device information from the terminal device.

36. The method according to claim 35, wherein, The device information includes at least one of the following: Expected user equipment activity behavior, mobility mode information, expected handover behavior, expected user equipment mobility, and expected user equipment movement trajectory.

37. The method according to claim 35, wherein, The acquisition of device information of the terminal device includes at least one of the following: Predict the device information based on the measurement report of the terminal device; The device information is obtained from other functional network elements within the core network. Obtain the device information predicted by the nodes of the wireless access network.

38. The method of claim 35, further comprising at least one of the following: Send a user equipment switching command to the terminal device; Send the prediction information to the source service node of the terminal device; The switching decision based on the predicted information is sent to the source service node or target service node of the terminal device.

39. An electronic device, the electronic device comprising: One or more processors; Memory, used to store one or more programs; When the one or more programs are characterized by the one or more processors, the one or more processors implement the information transmission method as described in any one of claims 1-38.

40. A computer-readable storage medium storing one or more programs, the one or more programs being executed by one or more processors to implement the information transmission method as described in any one of claims 1-38.

Images