Patent Description:
As terminal devices increase and with diversity of services, networks become increasingly complex, and consequently network operation and maintenance becomes more and more difficult. Network optimization and on-demand network resource scheduling are key factors for fast service assurance and improved user experience.

Existing network optimization mechanisms all consider measures to optimize networks after network performance deterioration (for example, traffic congestion) is detected. However, network optimization is a time-consuming process, to be specific, necessary steps such as algorithm optimization, effect evaluation, decision-making, and reconfiguration need to be performed. As a result, service requirements may be affected in a specified period of time, and problems such as no user access, time-consuming user access, and frame freezing may occur in a specified period of time.

<NUM> services (for example, an enhanced mobile broadband (enhanced mobile broadband, eMBB) service, a massive machine-type communications (massive machine-type communications, mMTC) service, and a low-latency and ultra-reliable communication (ultra-reliable low-latency communication, URLLC) service) have higher dynamic requirements. How to flexibly schedule limited radio resources to ensure multiple services and massive users becomes the greatest challenge. Existing radio resources are all statically allocated, resulting in excessive or insufficient radio resources at some time points and in some areas. Consequently, resource allocation is improper, and service requirements are affected.

Document <CIT> discloses a method and an apparatus for providing a multimedia broadcast/multicast service, MBMS, to a terminal related to a vehicle by a broadcast and multicast service center, BM-SC. In particular, according to the disclosed techniques, at least one candidate service area that the terminal is predicted to pass through is identified, and a request for configuring the radio bearer of the at least one candidate service area is transmitted to an MBMS-gateway, MBMS-GW.

This application provides a traffic volume prediction method and an apparatus, so that traffic volume prediction can be performed, to help avoid impact on a service due to improper resource allocation.

For example, the first management device may continuously collect, within a period of time, and analyze at least one historical traffic volume, of the predicted object, that corresponds to the traffic type included in the first message; analyze the historical traffic volume within the period of time, to obtain a rule of the historical traffic volume; and then obtain, according to the rule of the historical traffic volume and based on the at least one historical traffic volume, a predicted traffic volume that meets the prediction requirement information, namely, the predicted traffic volume, corresponding to the traffic type, that is determined based on the prediction requirement information in this embodiment of this application.

The traffic type includes at least one of the following: a quantity of users, user distribution, a user activation ratio, coverage, a throughput, a quantity of radio resource control RRC connections, a quantity of physical resource blocks PRBs, PRB usage, or load information.

For example, the first message may carry information used to indicate the predicted object, for example, a service identifier, a network identifier, a network element identifier, a network function identifier, or a cell identifier. For example, the network identifier is used to identify an object of the current prediction service, and the network may be a subnetwork (subnetwork), a network slice (network slice), a network slice subnet (network slice subnet), or the like. Correspondingly, the network identifier may be a subnetwork identifier, a network slice instance identifier, a network slice subnet instance identifier, a network slice selection assistance identifier (single network slice selection assistance identifier, s-NSSAI), or the like.

Before the first management device determines, for the predicted object based on the prediction requirement information, a predicted traffic volume corresponding to the traffic type, the method further includes: The first management device configures traffic volume prediction service information under a managed object of the predicted object based on the first message, where the traffic volume prediction service information is used to indicate to predict a traffic volume of the traffic type based on the prediction requirement information, and the traffic volume prediction service information includes the traffic type and the prediction requirement information.

The technical solutions of embodiments of this application may be used for various communication systems, for example, a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD) system, a universal mobile telecommunications system (universal mobile telecommunications system, UMTS), a 5th generation (5th generation, <NUM>) system, a new radio (new radio, NR) system, and another evolved communication system.

<FIG> shows a system architecture <NUM> to which the embodiments of this application may be applied. The system architecture <NUM> may include a service operation system <NUM> and a network management system <NUM>.

The service operation system <NUM> is configured to provide service operation functions, including functions such as service provisioning, service assurance, and service scheduling. For example, the service operation system <NUM> may include a service operation system of a vertical industry or a service operation system of a carrier, for example, a business support system (business support system, BSS) or a system that can implement a communication service management function (communication service management function, CSMF).

The network management system <NUM> is configured to provide network operation and maintenance functions, including: network life cycle management, network deployment, network fault management, network performance management, network configuration management, network assurance, and the like. The foregoing network may include one or more network elements, or one or more subnetworks. For example, the network management system <NUM> may be a system that can implement a network slice management function (network slice management function, NSMF), or a system that can implement a management data analytics function (management data analytics function, MDAF).

Optionally, the system architecture <NUM> may further include a domain management system <NUM> and one or more network elements <NUM>. The domain management system <NUM> is configured to provide an intra-domain network operation and maintenance function, namely, an operation and maintenance function of a subnetwork or a network element. The domain management system <NUM> may provide life cycle management of the subnetwork or the network element, deployment of the subnetwork or the network element, fault management of the subnetwork or the network element, performance management of the subnetwork or the network element, assurance of the subnetwork or the network element, and the like. The foregoing subnetwork may include one or more network elements. For example, the domain management system <NUM> may be a system that can implement a network slice subnet management function (network slice subnet management function), a domain manager (domain manager, DM), an element manager (element manager, EM), or the like.

The network element <NUM> is an entity that provides a network service, and may include a core network element and an access network element. The core network element may be a device, for example, an access and mobility management function (access and mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a policy control function (policy control function, PCF) network element, a network data analytics unit (network data analytics function, NWDAF) network element, a network repository function (network repository function, NRF) network element, and a gateway. The access network element may be a device configured to communicate with a terminal device. The access network element may also be referred to as an access network device or a radio access network device, and may be a transmission reception point (transmission reception point, TRP), an evolved NodeB (evolved NodeB, eNB or eNodeB) in an LTE system, a home NodeB (for example, a home evolved NodeB or a home NodeB, HNB), a baseband unit (baseband unit, BBU), or a radio controller in a cloud radio access network (cloud radio access network, CRAN) scenario. Alternatively, the access network element may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a <NUM> network or a network device in a future evolved PLMN network, an access point (access point, AP) in a WLAN, or a gNB in a new radio (new radio, NR) system. This is not limited in the embodiments of this application. In a network structure, the access network element may include a centralized unit (centralized unit, CU) node, a distributed unit (distributed unit, DU) node, a RAN device including a CU node and a DU node, or a RAN device including a CU control plane node (CU-CP node), a CU user plane node (CU-UP node), and a DU node.

Related functions of the service operation system <NUM> and the network management system <NUM> in <FIG> may be implemented through a management device. For example, all functions of the service operation system <NUM> and the network management system <NUM> may be integrated into the management device by using software. In this specification, a network entity corresponding to the network management system <NUM> is a first management device, and a network entity corresponding to the service operation system <NUM> is a second management device. For ease of description, network entities configured to implement the foregoing systems are referred to as management devices in this specification, and the first management device and the second management device are used to describe the embodiments of this application. However, it should be understood that the network entities may alternatively have other names.

Network entities corresponding to the domain management system <NUM>, the service operation system <NUM>, and the network management system <NUM> are management devices. <FIG> shows an example of one domain management system <NUM> and three network elements <NUM> managed by the domain management system <NUM>. Optionally, the system architecture <NUM> may include another domain management system and another quantity of network elements managed by the another domain management system. Optionally, the system architecture <NUM> may further include other network entities such as a network controller and a mobility management entity.

In the embodiments of this application, the management device includes a hardware layer, an operating system layer running above the hardware layer, and an application layer running above the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (which is also referred to as a main memory). The operating system may be any one or more types of computer operating systems that implement service processing through a process (process), for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as a browser, an address book, word processing software, and instant messaging software. In addition, a specific structure of an execution body of a method provided in the embodiments of this application is not specifically limited in the embodiments of this application, provided that a program that records code for the method provided in the embodiments of this application can be run to perform communication according to the method provided in the embodiments of this application. For example, the method provided in the embodiments of this application may be performed by a network device, or a functional module that is in the network device and that can invoke and execute the program.

In addition, aspects or features of this application may be implemented as a method, an apparatus, or a product that uses standard programming and/or engineering technologies. The term "product" used in this application covers a computer program that can be accessed from any computer-readable component, carrier, or medium. For example, a computer-readable medium may include but is not limited to a magnetic storage component (for example, a hard disk, a floppy disk, or a magnetic tape), an optical disc (for example, a compact disc (compact disc, CD), a digital versatile disc (digital versatile disc, DVD)), a smart card, and a flash memory component (for example, an erasable programmable read-only memory (erasable programmable read-only memory, EPROM), a card, a stick, or a key drive). In addition, various storage media described in this specification may indicate one or more devices and/or other machine-readable media that are configured to store information. The term "machine-readable media" may include but are not limited to a radio channel and various other media that can store, include, and/or carry instructions and/or data.

In view of this, the embodiments of this application provide a method, so that traffic volume prediction can be performed, to help avoid impact on a service due to improper resource allocation.

<FIG> is a schematic flowchart of a traffic volume prediction method <NUM> according to an embodiment of this application. The method <NUM> may be applied to the system architecture <NUM> shown in <FIG>. However, this embodiment of this application is not limited thereto.

S210: A second management device sends a first message to a first management device, and correspondingly the first management device receives the first message from the second management device, where the first message is used to request the first management device to perform traffic volume prediction, the first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant.

S220: The first management device determines, for the predicted object based on the prediction requirement information, a predicted traffic volume corresponding to the traffic type.

S230: The first management device sends the predicted traffic volume to the second management device, and correspondingly the second management device receives the predicted traffic volume from the first management device.

According to the traffic volume prediction method in this embodiment of this application, the first management device can predict, based on the predicted object, the traffic type, and the prediction requirement information that are sent by the second management device, a traffic volume, of the predicted object, that meets the prediction requirement information. In this way, resources in a network can be allocated on demand based on the obtained predicted traffic volume. This helps avoid impact on a service due to improper resource allocation, and improves system performance.

For example, the second management device may send, to the first management device, the first message for requesting to perform traffic volume prediction, and the first message may include the predicted object, the traffic type, and the prediction requirement information, so that the first management device determines, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type. In other words, the first management device may predict the traffic volume, of the predicted object, that meets the prediction requirement information and corresponds to the traffic type, and return the predicted traffic volume to the second management device.

For example, the first management device may continuously collect, within a period of time, a historical traffic volume, of the predicted object, that corresponds to the traffic type; analyze the historical traffic volume within the period of time, to obtain a rule of the historical traffic volume; and then determine, according to the rule of the historical traffic volume, a predicted traffic volume that meets the prediction requirement information, namely, the predicted traffic volume, corresponding to the traffic type, that is determined based on the prediction requirement information in this embodiment of this application.

In this embodiment of this application, the traffic volume obtained by using the prediction method may be referred to as a predicted traffic volume, and an actual predicted traffic volume may be referred to as a traffic volume or a historical traffic volume. However, it should be understood that this is merely for ease of distinguishing an actual value of the traffic volume from a prediction value of the traffic volume. A name thereof is not limited in this embodiment of this application. The traffic volume may also be referred to as a service volume, or may have another name. This is not limited in this embodiment of this application.

It should be understood that the first message may be a message used only to request traffic volume prediction, or may reuse another message. This is not limited in this embodiment of this application. In a possible implementation, the first message is included in a traffic volume measurement control request message, in other words, the traffic volume measurement control request message not only requests the first management device to perform traffic volume measurement control, but also requests, by using the first message carried in the traffic volume measurement control request message, the first management device to perform traffic volume prediction.

The prediction granularity indicates a prediction range supported by a current prediction service, and may specifically include one or more of the following:.

The prediction period indicates maximum prediction time that the current prediction service needs to support. For example, when the prediction period is one week, the current prediction service needs to support prediction of the traffic volume within one week. For another example, when the prediction period is one day, the current prediction service needs to support prediction of the traffic volume within one day.

The traffic type indicates a type of the traffic volume that the current prediction service needs to support. In an optional embodiment, the traffic type includes at least one of the following: a quantity of users, user distribution, a user activation ratio, coverage, a throughput, a quantity of radio resource control (radio resource control, RRC) connections, a quantity of physical resource blocks (physical resource blocks, PRBs), PRB usage, or load information. The quantity of users may be a quantity of registered users or a quantity of activated users. This is not limited in this embodiment of this application.

In an optional embodiment, the predicted object includes at least one of the following: a service, a network, a network element, a network function, or a cell.

For example, prediction based on the predicted object may specifically include the following plurality of cases:
When the predicted object is the service, it indicates that a predicted traffic volume of a specified service needs to be predicted.

When the predicted object is the network, it indicates that an overall predicted traffic volume of a specified network needs to be predicted.

When the predicted object is the service and the network, it indicates that a predicted traffic volume of a specified service in a specified network needs to be predicted.

When the predicted object is the network element, it indicates that a predicted traffic volume of a specified network element needs to be predicted.

When the predicted object is the network function, it indicates that a predicted traffic volume of a specified network function needs to be predicted.

When the predicted object is the cell, it indicates that a predicted traffic volume of a specified cell needs to be predicted.

When the predicted object is the cell and the network, it indicates that a predicted traffic volume of a specified network in a specified cell needs to be predicted. One cell can support a plurality of networks.

It should be understood that there are a plurality of other possibilities for specific content of the predicted object, and the possibilities are not enumerated herein one by one.

It should be understood that the network identifier may alternatively be an identifier of a managed object of a corresponding network. For example, the network slice instance identifier may be an identifier of a managed object of a network slice, the network slice subnet instance identifier may be an identifier of a managed object of a network slice subnet, and the subnetwork identifier may be an identifier of a managed object of a subnetwork. This is not limited in this embodiment of this application.

In this embodiment of this application, the first management device may determine, in different manners based on content included in the prediction requirement information, the predicted traffic volume corresponding to the traffic type. In an optional embodiment, that the first management device determines, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type includes:
When the prediction requirement information includes the prediction granularity, the first management device collects the traffic volume based on the prediction granularity, and determines, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type at the prediction granularity.

Alternatively, when the prediction requirement information includes the prediction period, the first management device collects the traffic volume, and determines, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type in the prediction period.

Alternatively, when the prediction requirement information includes the prediction granularity and the prediction period, the first management device collects the traffic volume based on the prediction granularity, and determines, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type at the prediction granularity and in the prediction period.

The following separately describes the foregoing three cases in detail.

Case <NUM>: The prediction requirement information includes the prediction granularity, and the first management device may collect the traffic volume based on the prediction granularity, and determine the predicted traffic volume corresponding to the traffic type at the prediction granularity.

With reference to specific embodiments, the following describes in detail the foregoing traffic prediction method by using an example in which the predicted object is a network <NUM> and the traffic type is the quantity of users. Traffic volume prediction in the following embodiments refers to prediction of the quantity of users, that is, both the traffic volume and the predicted traffic volume are the quantity of users. Details are not described one by one.

Assuming that the network <NUM> can cover a plurality of areas, where the areas are respectively an area <NUM>, an area <NUM>, and an area <NUM>, and the prediction granularity is the prediction area, it indicates that the first message is to request to perform traffic volume prediction at the area granularity corresponding to the network <NUM>. Specifically, performing traffic volume prediction at the area granularity corresponding to the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, area <NUM>), (network <NUM>, area <NUM>), and (network <NUM>, area <NUM>).

For example, after receiving the first message, the first management device may obtain area information included in the network <NUM>, namely, information about the area <NUM>, the area <NUM>, and the area <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each area, and obtain a traffic volume of each area of the network <NUM>; and analyze the traffic volume of each area corresponding to the network <NUM>, obtain a rule of the traffic volume of each area, and then calculate a predicted traffic volume of each area corresponding to the network <NUM>. For example, for traffic volumes of (network <NUM>, area <NUM>) in the morning, at noon, and in the evening every day, traffic volumes in the morning, at noon, and in the evening in a day are different, but the traffic volumes in the morning, at noon, and in the evening every day are similar. For example, a traffic volume on Monday morning is similar to that on Tuesday morning. In this case, traffic volumes in the morning, at noon, and in the evening every day thereafter can be calculated by using the foregoing method. For another example, on each Sunday morning, a traffic volume of the area <NUM> (where there is a church) is quite heavy. In this case, a predicted traffic volume of the area <NUM> on each Sunday morning thereafter can be calculated by using the foregoing method.

Assuming that the network <NUM> includes a plurality of sites, where the sites are respectively a site <NUM>, a site <NUM>, and a site <NUM>, and the prediction granularity is the prediction site, it indicates that the first message is to request to perform traffic volume prediction at the site granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the site granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, site <NUM>), (network <NUM>, site <NUM>), and (network <NUM>, site <NUM>).

For example, after receiving the first message, the first management device may obtain site information included in the network <NUM>, namely, information about the site <NUM>, the site <NUM>, and the site <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each site, and obtain a traffic volume of each site of the network <NUM>; and analyze the traffic volume of each site corresponding to the network <NUM>, obtain a rule of the traffic volume of each site, and then calculate a predicted traffic volume of each site corresponding to the network <NUM>.

Assuming that the network <NUM> includes a plurality of cells, where the cells are respectively a cell <NUM>, a cell <NUM>, and a cell <NUM>, and the prediction granularity is the prediction cell, it indicates that the first message is to request to perform traffic volume prediction at the cell granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the cell granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, cell <NUM>), (network <NUM>, cell <NUM>), and (network <NUM>, cell <NUM>).

For example, after receiving the first message, the first management device may obtain cell information included in the network <NUM>, namely, information about the cell <NUM>, the cell <NUM>, and the cell <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each cell, and obtain a traffic volume of each cell of the network <NUM>; and analyze the traffic volume of each cell corresponding to the network <NUM>, obtain a rule of the traffic volume of each cell, and then calculate a predicted traffic volume of each cell corresponding to the network <NUM>.

Assuming that the network <NUM> includes a plurality of network slice instances, where the network slice instances are respectively a network slice instance <NUM>, a network slice instance <NUM>, and a network slice instance <NUM>, and the prediction granularity is the prediction slice, it indicates that the first message is to request to perform traffic volume prediction at the slice granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the slice granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, network slice instance <NUM>), (network <NUM>, network slice instance <NUM>), and (network <NUM>, network slice instance <NUM>).

For example, after receiving the first message, the first management device may obtain network slice instance information included in the network <NUM>, namely, information about the network slice instance <NUM>, the network slice instance <NUM>, and the network slice instance <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each network slice instance, and obtain a traffic volume of each network slice instance of the network <NUM>; and analyze the traffic volume of each network slice instance corresponding to the network <NUM>, obtain a rule of the traffic volume of each network slice instance, and then calculate a predicted traffic volume of each network slice instance corresponding to the network <NUM>.

Assuming that the network <NUM> includes a plurality of tenants, where the tenants are respectively a tenant <NUM>, a tenant <NUM>, and a tenant <NUM>, and the prediction granularity is the prediction tenant, it indicates that the first message is to request to perform traffic volume prediction at the tenant granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the tenant granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, tenant <NUM>), (network <NUM>, tenant <NUM>), and (network <NUM>, tenant <NUM>).

For example, after receiving the first message, the first management device may obtain tenant information included in the network <NUM>, namely, information about the tenant <NUM>, the tenant <NUM>, and the tenant <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each tenant, and obtain a traffic volume of each tenant of the network <NUM>; and analyze the traffic volume of each tenant corresponding to the network <NUM>, obtain a rule of the traffic volume of each tenant, and then calculate a predicted traffic volume of each tenant corresponding to the network <NUM>.

Assuming that the network <NUM> includes a plurality of service types, where the service types are respectively a service type <NUM>, a service type <NUM>, and a service type <NUM>, and the prediction granularity is the prediction service type, it indicates that the first message is to request to perform traffic volume prediction at the service type granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the service type granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, service type <NUM>), (network <NUM>, service type <NUM>), and (network <NUM>, service type <NUM>).

For example, after receiving the first message, the first management device may obtain service type information included in the network <NUM>, namely, information about the service type <NUM>, the service type <NUM>, and the service type <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each service type, and obtain a traffic volume of each service type of the network <NUM>; and analyze the traffic volume of each service type corresponding to the network <NUM>, obtain a rule of the traffic volume of each service type, and then calculate a predicted traffic volume of each service type corresponding to the network <NUM>.

Assuming that the network <NUM> includes a plurality of PLMNs, where the PLMNs are respectively a PLMN <NUM>, a PLMN <NUM>, and a PLMN <NUM>, and the prediction granularity is the prediction PLMN, it indicates that the first message is to request to perform traffic volume prediction at the PLMN granularity included in the network <NUM>. Specifically, performing traffic volume prediction at the PLMN granularity included in the network <NUM> may include separately performing traffic volume prediction on (network <NUM>, PLMN <NUM>), (network <NUM>, PLMN <NUM>), and (network <NUM>, PLMN <NUM>).

For example, after receiving the first message, the first management device may obtain PLMN information included in the network <NUM>, namely, information about the PLMN <NUM>, the PLMN <NUM>, and the PLMN <NUM>; collect a traffic volume of the network <NUM>, analyze a correspondence between the traffic volume of the network <NUM> and each PLMN, and obtain a traffic volume of each PLMN of the network <NUM>; and analyze the traffic volume of each PLMN corresponding to the network <NUM>, obtain a rule of the traffic volume of each PLMN, and then calculate a predicted traffic volume of each PLMN corresponding to the network <NUM>.

Case <NUM>: The prediction requirement information includes the prediction period, and the first management device may collect the traffic volume and determine the predicted traffic volume corresponding to the traffic type in the prediction period.

For example, the predicted object is a network <NUM> and the traffic type is the quantity of users. The first management device may collect a traffic volume of the network <NUM>, analyze the traffic volume of the network <NUM>, and determine the predicted traffic volume in the prediction period, and both the traffic volume and the predicted traffic volume herein refer to the quantity of users.

Case <NUM>: The prediction requirement information includes the prediction granularity and the prediction period, and the first management device may collect the traffic volume based on the prediction granularity, and determine the predicted traffic volume corresponding to the traffic type at the prediction granularity and in the prediction period. A specific method is similar to that described above, and details are not described herein again.

In an optional embodiment, before the first management device determines, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type, the method further includes: The first management device configures traffic volume prediction service information for a managed object of the predicted object based on the first message, where the traffic volume prediction service information is used to indicate to predict a traffic volume of the traffic type based on the prediction requirement information, and the traffic volume prediction service information includes the traffic type and the prediction requirement information.

For example, when the first message includes the predicted object, after the first management device receives the first message, the first management device may create a traffic prediction service for the managed object of the predicted object, that is, configure the traffic prediction service information, to predict the current traffic volume. Specifically, the first management device may include information such as the traffic type, the prediction granularity, and the prediction period in the current traffic prediction service information.

In an optional embodiment, before the first management device determines, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type, the method further includes: The first management device determines, based on the first message, a predicted sub-object associated with the predicted object; and the first management device sends a seventh message to a management device of the predicted sub-object, where the seventh message is used to request the management device of the predicted sub-object to predict a traffic volume of the predicted sub-object.

For example, the first management device may determine the predicted sub-object based on the predicted object. For example, current network traffic volume prediction may be classified into access network traffic volume prediction and core network traffic volume prediction, network traffic volume prediction of different areas, or network traffic volume prediction of different sites. The first management device may separately send, to the management device of the predicted sub-object, the seventh message for requesting to perform traffic volume prediction of the predicted sub-object. After receiving the seventh message, the management device of the predicted sub-object may configure traffic prediction service information for the predicted sub-object for the managed object of the predicted sub-object.

It should be understood that one managed object corresponds to only one management device, but one management device may correspond to a plurality of managed objects. In a possible implementation, the management device of the predicted sub-object in this embodiment of this application may be the domain management device <NUM> in <FIG>, and the managed object may be the network element <NUM> in <FIG>.

In this embodiment of this application, the second management device may predict the traffic volume in a plurality of manners.

In an optional embodiment, after the first management device determines, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type, the method further includes: The first management device sends a second message to the second management device, where the second message is used to indicate a traffic volume prediction result, and the second message carries at least one predicted traffic volume corresponding to the traffic type.

Correspondingly, that the second management device receives the predicted traffic volume from the first management device includes: The second management device receives the second message from the first management device.

It should be understood that the first management device may send the traffic volume prediction result including the at least one predicted traffic volume to the second management device. The at least one predicted traffic volume may be determined by the first management device based on the predicted object, the traffic type, and the prediction requirement information. For example, if the second message carries a plurality of predicted traffic volumes, the plurality of predicted traffic volumes may each correspond to one piece of time information. For example, a quantity of the plurality of predicted traffic volumes is <NUM>, respectively corresponding to <NUM> hours in a day. The predicted traffic volume may be a maximum value, a minimum value, an average value, or the like of predicted traffic volumes in each hour. This is not limited in this embodiment of this application. In a possible implementation, the time information and the plurality of predicted traffic volumes may be carried in the second message, and the time information and the predicted traffic volumes are bound in a one-to-one manner. In another possible implementation, the first management device and the second management device may pre-agree on a sending sequence of a plurality of predicted traffic volumes, so that the sending sequence of the plurality of predicted traffic volumes corresponds to an agreed time sequence, and the second management device may obtain, according to an agreement, a predicted traffic volume corresponding to specific time.

In this embodiment of this application, the first management device may send the second message to the second management device based on an agreed reporting period, for example, send the second message every two days or every a week. Optionally, the reporting period may be a prediction period carried in the first message, that is, the second management device may indicate, by using the first message, the first management device to report the predicted traffic volume based on the prediction period.

In an optional embodiment, after the second management device sends the first message to the first management device, the method further includes: The second management device sends a third message to the first management device, where the third message is used to request the first management device to return the predicted traffic volume, and the third message carries information about a to-be-queried object and information about a query granularity. Correspondingly the first management device receives the third message from the second management device. The first management device sends a fourth message to the second management device based on the third message, where the fourth message is used to indicate a predicted traffic volume of the to-be-queried object at the query granularity. Correspondingly, that the second management device receives the predicted traffic volume from the first management device includes: The second management device receives the fourth message from the first management device.

It should be understood that the to-be-queried object includes all or a part of the predicted objects, and the query granularity includes all or a part of the prediction granularities. In this way, the first management device can obtain the corresponding predicted traffic volume based on the to-be-queried object and the query granularity. Optionally, the third message further includes query time, and is used to predict a traffic volume at a specific time point or a specific time period.

For example, prediction based on the to-be-queried object may specifically include the following plurality of cases:
When the to-be-queried object is the network identifier, it indicates that an overall predicted traffic volume of a specified network is queried.

When the to-be-queried object is the area information or the longitude and latitude information of the area, it indicates that a predicted traffic volume in a specified area is to be queried.

When the to-be-queried object is the area information or the network identifier, it indicates that a predicted traffic volume of a corresponding network in a specified area is to be queried. It should be understood that one area can correspond to a plurality of networks.

When the to-be-queried object is the site information, it indicates that a predicted traffic volume of a specified site is queried.

When the to-be-queried object is the site information and the network identifier, it indicates that a predicted traffic volume of a corresponding network in a specified site is queried. It should be understood that one site can support a plurality of networks.

When the to-be-queried object is the cell information, it indicates that a predicted traffic volume of a specified cell is queried.

When the to-be-queried object is the cell information and the network identifier, it indicates that a predicted traffic volume of a corresponding network in a specified cell is queried. It should be understood that one cell can support a plurality of networks.

When the to-be-queried object is the slice information, it indicates that a predicted traffic volume of a specified slice is queried.

When the to-be-queried object is the slice information and the network identifier, it indicates that a predicted traffic volume of a specified slice supported by a specified network is queried. It should be understood that one network can support a plurality of slices.

When the to-be-queried object is the tenant information, it indicates that a predicted traffic volume of a specified tenant is queried.

When the to-be-queried object is the tenant information and the network identifier, it indicates that a traffic volume of a specified tenant supported by a specified network is queried. It should be understood that one network can support a plurality of tenants.

When the to-be-queried object is the service type, it indicates that a predicted traffic volume of a specified service type is queried.

When the to-be-queried object is the service type and the network identifier, it indicates that a predicted traffic volume of a specified service type in a specified network is queried.

It should be understood that there are a plurality of other possibilities for specific content of the to-be-queried object, and the possibilities are not enumerated herein one by one.

In an optional embodiment, after the second management device sends the first message to the first management device, the method further includes: The second management device sends a fifth message to the first management device, where the fifth message is to request to perform traffic volume evaluation, and the fifth message carries information about an evaluated object, information about evaluation time, and a traffic volume requirement value. Correspondingly, the first management device receives the fifth message from the second management device, and the first management device determines, based on the fifth message, whether the evaluated object can meet the traffic volume requirement value within the evaluation time. The first management device sends a sixth message to the second management device, where the sixth message is used to indicate a traffic volume evaluation result. Correspondingly, that the second management device receives the predicted traffic volume from the first management device includes: The second management device receives the sixth message from the first management device, where the sixth message is used to indicate the traffic volume evaluation result.

It should be understood that the evaluated object includes all or a part of the predicted objects. A specific evaluation situation is similar to that of the to-be-queried object. In this embodiment of this application, the fifth message sent by the second management device to the first management device may carry the traffic volume requirement value, and the first management device may directly determine, based on the traffic volume requirement value and with reference to the evaluated object and the evaluation time, whether a traffic volume of the evaluated object can meet the traffic volume requirement value within the evaluation time. Therefore, the traffic volume evaluation result in this embodiment of this application is "yes" or "no".

Optionally, if the traffic volume evaluation result is "no", the second management device may adjust the traffic volume requirement value, and perform reevaluation. However, this is not limited in this embodiment of this application.

It should be understood that terms "first", "second", "third", "fourth", and various numbers in the foregoing embodiments are merely used for differentiation for ease of description, and are not used to limit the scope of the embodiments of this application, for example, differentiate different messages.

An example in which the first management device is a network management system and the second management device is a service running system is used below to describe in detail the embodiments of this application with reference to a domain management system.

<FIG> is a schematic flowchart of another traffic volume prediction method <NUM> according to an embodiment of this application. The method <NUM> may be applied to the system architecture <NUM> shown in <FIG>. However, this embodiment of this application is not limited thereto.

S301: A service operation system sends a first message to a network management system, and correspondingly the network management system receives the first message. The first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant.

S302: The network management system configures traffic volume prediction service information based on the first message, where the traffic volume prediction service information includes the traffic type and the prediction requirement information.

S303: The network management system sends a seventh message to the domain management system, and correspondingly a domain management system receives the seventh message, where the seventh message is used to request a management device of a predicted sub-object to predict a traffic volume of the predicted sub-object.

S304: The domain management system configures traffic volume prediction subservice information based on the seventh message.

S305: The domain management system sends a configuration acknowledgment message to the network management system, to indicate that a corresponding traffic volume prediction subservice is successfully configured, and correspondingly the network management system receives the configuration acknowledgment message.

S306: The network management system sends a configuration acknowledgment message to the service operation system, to indicate that a traffic volume prediction service is successfully configured, and correspondingly the service operation system receives the configuration acknowledgment message.

Optionally, S307 to S309 show a process in which the service operation system queries a service volume.

S307: The service operation system sends a third message to the network management system, and correspondingly the network management system receives the third message, where the third message is used to request the network management system to return a predicted traffic volume, and the third message carries information about a to-be-queried object and information about a query granularity.

S308: The network management system performs query, that is, performs query based on the related traffic volume prediction service information and traffic volume prediction subservice information, to determine the predicted traffic volume.

S309: The network management system sends a fourth message to the service operation system, and correspondingly the service operation system receives the fourth message, where the fourth message is used to indicate the predicted traffic volume of the to-be-queried object at the query granularity.

Optionally, S310 to S312 show a process in which the service operation system evaluates the service volume.

S310: The service operation system sends a fifth message to the network management system, and correspondingly the network management system receives the fifth message, where the fifth message is to request to perform traffic volume evaluation, and the fifth message carries information about an evaluated object, information about evaluation time, and a traffic volume requirement value.

S311: The network management system performs evaluation, that is, invokes the related traffic volume prediction service and traffic volume prediction subservice, to determine a traffic volume evaluation result, where the traffic volume evaluation result indicates whether the evaluated object can meet the traffic volume requirement value within the evaluation time.

S312: The network management system sends a sixth message to the service operation system, where the sixth message carries the traffic volume evaluation result. Correspondingly, the service operation system receives the sixth message.

S401: A service operation system sends, to a network management system, a request for subscribing to a traffic volume prediction service of unmanned aerial vehicle flight, where the request is equivalent to the first message in the foregoing embodiments, and the request carries requirement information of an unmanned aerial vehicle service, for example, a maximum quantity of users, a delay, and area information. Correspondingly, the network management system receives the request.

S402: The network management system interacts with a domain management system corresponding to the unmanned aerial vehicle service, to configure related information of the traffic volume prediction service.

S403: The network management system sends a configuration acknowledgment message to the service operation system, to indicate that the traffic volume prediction service is successfully configured, and correspondingly the service operation system receives the configuration acknowledgment message.

Optionally, S404 to S406 show a process in which the service operation system queries a service volume of an unmanned aerial vehicle.

S404: The service operation system sends a flight intent of the unmanned aerial vehicle to the network management system, where the flight intent of the unmanned aerial vehicle may specifically include information such as flight time, a departure place, and a destination. Correspondingly, the network management system receives the flight intent of the unmanned aerial vehicle.

S405: The network management system performs query based on the flight intent of the unmanned aerial vehicle, to determine a traffic volume prediction value.

S406: The network management system determines a flight route of the unmanned aerial vehicle based on the traffic volume prediction value, and sends the flight route of the unmanned aerial vehicle to the service operation system, and correspondingly the service operation system receives the flight route of the unmanned aerial vehicle.

Optionally, S407 to S410 show a process in which the service operation system evaluates the service volume of the unmanned aerial vehicle.

S407: The service operation system sends a flight route of the unmanned aerial vehicle to the network management system, where the flight route of the unmanned aerial vehicle may specifically include information such as flight time, a departure place, a destination, and a passing flight area. Correspondingly, the network management system receives the flight route of the unmanned aerial vehicle.

S408: The network management system performs evaluation based on the flight route of the unmanned aerial vehicle, and determines whether a traffic volume of the passing flight area can support a flight task of the unmanned aerial vehicle, to determine a traffic volume evaluation result.

S409: The network management system sends the traffic volume evaluation result to the service operation system, and correspondingly the service operation system receives the traffic volume evaluation result.

Optionally, when the traffic volume evaluation result is "no", S410 may be continued, to be specific, the service operation system adjusts the flight route of the unmanned aerial vehicle, and continues to perform evaluation until the traffic volume evaluation result is "yes".

According to the traffic volume prediction method in this embodiment of this application, a traffic volume prediction service of an unmanned aerial vehicle service is configured by the network management system, so that the service operation system can determine a proper flight route based on the flight task. This improves network resource usage.

It should be understood that sequence numbers of the foregoing processes do not indicate an execution sequence. The execution sequence of the processes is determined based on functions and internal logic of the processes, and is not construed as any limitation on the implementation processes of the embodiments of this application.

The traffic volume prediction method according to the embodiments of this application is described in detail above with reference to <FIG>, and an apparatus according to the embodiments of this application is described in detail below with reference to <FIG>.

<FIG> shows an apparatus <NUM> according to an embodiment of this application. The apparatus <NUM> may be a first management device, or may be an apparatus that can support the first management device in implementing a function of the first management device, for example, may be a chip or a chip system that may be used in the first management device. The apparatus <NUM> includes a transceiver unit <NUM> and a processing unit <NUM>. Further, the transceiver unit <NUM> may include a receiving unit and a sending unit, where the receiving unit is configured to perform the following receiving procedure corresponding to the transceiver unit <NUM>, and the sending unit is configured to perform the following sending procedure corresponding to the transceiver unit <NUM>.

The transceiver unit <NUM> is configured to receive a first message from a second management device, where the first message is used to request the first management device to perform traffic volume prediction, the first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant. The processing unit <NUM> is configured to determine, for the predicted object based on the prediction requirement information, a predicted traffic volume corresponding to the traffic type.

Optionally, the traffic type includes at least one of the following: a quantity of users, user distribution, a user activation ratio, coverage, a throughput, a quantity of radio resource control RRC connections, a quantity of physical resource blocks PRBs, PRB usage, or load information.

Optionally, the predicted object includes at least one of the following: a service, a network, a network element, a network function, or a cell.

Optionally, before determining, for the predicted object based on the prediction requirement information, the predicted traffic volume corresponding to the traffic type, the processing unit <NUM> is further configured to configure traffic volume prediction service information for a managed object of the predicted object based on the first message, where the traffic volume prediction service information is used to indicate to predict a traffic volume of the traffic type based on the prediction requirement information, and the traffic volume prediction service information includes the traffic type and the prediction requirement information.

Optionally, the processing unit <NUM> is specifically configured to: when the prediction requirement information includes the prediction granularity, collect the traffic volume based on the prediction granularity, and determine, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type at the prediction granularity; or when the prediction requirement information includes the prediction period, collect the traffic volume, and determine, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type in the prediction period; or when the prediction requirement information includes the prediction granularity and the prediction period, collect the traffic volume based on the prediction granularity, and determine, based on the collected traffic volume, the predicted traffic volume corresponding to the traffic type at the prediction granularity and in the prediction period.

Optionally, the transceiver unit <NUM> is further configured to send a second message to the second management device, where the second message is used to indicate a traffic volume prediction result, and the second message carries at least one predicted traffic volume corresponding to the traffic type.

Optionally, the transceiver unit <NUM> is further configured to: receive a third message from the second management device, where the third message is used to request the first management device to return the predicted traffic volume, and the third message carries information about a to-be-queried object and information about a query granularity; and send a fourth message to the second management device based on the third message, where the fourth message is used to indicate a predicted traffic volume of the to-be-queried object at the query granularity.

Optionally, the transceiver unit <NUM> is further configured to: receive a fifth message from the second management device, where the fifth message is to request to perform traffic volume evaluation, and the fifth message carries information about an evaluated object, information about evaluation time, and a traffic volume requirement value; the processing unit <NUM> is further configured to: determine, based on the fifth message, whether the evaluated object can meet the traffic volume requirement value within the evaluation time; and the transceiver unit <NUM> is further configured to: send a sixth message to the second management device, where the sixth message is used to indicate a traffic volume evaluation result.

It should be understood that the apparatus <NUM> herein is implemented in a form of a functional unit. A term "unit" herein may refer to an application-specific integrated circuit (application-specific integrated circuit, ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor, or a group processor) configured to execute one or more software or firmware programs, a memory, a merge logic circuit, and/or another suitable component that supports the described function. In an optional example, a person skilled in the art may understand that the apparatus <NUM> may be specifically the terminal device or the network device in the foregoing embodiments, and the apparatus <NUM> may be configured to perform procedures and/or steps corresponding to the first management device in the foregoing method embodiments. To avoid repetition, details are not described herein again.

<FIG> shows an apparatus <NUM> according to an embodiment of this application. The apparatus <NUM> may be a second management device, or may be an apparatus that can support the second management device in implementing a function of the second management device, for example, may be a chip or a chip system that may be used in the second management device. The apparatus <NUM> includes a sending unit <NUM> and a receiving unit <NUM>.

The sending unit <NUM> is configured to send a first message to a first management device, where the first message is used to request a first management device to perform traffic volume prediction, the first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant. The receiving unit <NUM> is configured to receive a predicted traffic volume from the first management device.

Optionally, the receiving unit <NUM> is specifically configured to: receive a second message from the first management device, where the second message is used to indicate a traffic volume prediction result, and the second message carries at least one predicted traffic volume corresponding to the traffic type.

Optionally, the sending unit <NUM> is specifically configured to: send a third message to the first management device, where the third message is used to request the first management device to return the predicted traffic volume, and the third message carries information about a to-be-queried object and information about a query granularity; and the receiving unit <NUM> is specifically configured to: receive a fourth message from the first management device, where the fourth message is used to indicate a predicted traffic volume of the to-be-queried object at the query granularity.

Optionally, the sending unit <NUM> is specifically configured to: send a fifth message to the first management device, where the fifth message is to request to perform traffic volume evaluation, and the fifth message carries information about an evaluated object, information about evaluation time, and a traffic volume requirement value; and the receiving unit <NUM> is specifically configured to: receive a sixth message from the first management device, where the sixth message is used to indicate a traffic volume evaluation result.

The apparatus <NUM> in the foregoing solutions has a function of implementing corresponding steps performed by the first management device in the foregoing methods. The apparatus <NUM> has a function of implementing corresponding steps performed by the second management device in the foregoing methods. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or the software includes one or more modules corresponding to the foregoing functions. For example, a sending unit and a receiving unit may be replaced by a communication interface, and another unit, for example, the processing unit, may be replaced by a processor, to separately perform a sending operation, a receiving operation, and a related processing operation in the method embodiments. In the embodiments of this application, the communication interface may be an apparatus, for example, a circuit, a module, a bus, a bus interface, or a transceiver, that can implement a communication function.

In the embodiments of this application, each of the apparatus in <FIG> and the apparatus in <FIG> may alternatively be a chip or a chip system, for example, a system on chip (system on chip, SoC). Correspondingly, the receiving unit and the sending unit may be a transceiver circuit of the chip. This is not limited herein.

<FIG> shows another apparatus <NUM> according to an embodiment of this application. The apparatus <NUM> includes a processor <NUM> and a transceiver <NUM>. Optionally, the apparatus <NUM> may further include a memory <NUM>. Optionally, the memory <NUM> may be included in the processor <NUM>. The processor <NUM>, the transceiver <NUM>, and the memory <NUM> communicate with each other through an internal connection path. The memory <NUM> is configured to store instructions. The processor <NUM> is configured to execute the instructions stored in the memory <NUM>, to implement the method provided in the embodiments of this application.

In a possible implementation, the apparatus <NUM> is configured to perform procedures and steps corresponding to a first management device in the method provided in the embodiments of this application.

The processor <NUM> is configured to: receive a first message from a second management device through the transceiver <NUM>, where the first message is used to request the first management device to perform traffic volume prediction, the first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant; and determine, based on the prediction requirement information, a traffic volume corresponding to the traffic type.

In a possible implementation, the apparatus <NUM> is configured to perform procedures and steps corresponding to a second management device in the method provided in the embodiments of this application.

The processor <NUM> is configured to: send a first message to a first management device through the transceiver <NUM>, where the first message is used to request the first management device to perform traffic volume prediction, the first message includes a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information includes a prediction granularity and/or a prediction period, where the prediction granularity includes at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant; and receive a predicted traffic volume from the first management device through the transceiver <NUM>.

It should be understood that the apparatus <NUM> may be specifically the first management device or the second management device in the foregoing embodiments, and may be configured to perform steps and/or procedures corresponding to the first management device or the second management device in the foregoing method embodiments. Optionally, the memory <NUM> may include a read-only memory and a random access memory, and provide instructions and data for the processor. A part of the memory may further include a nonvolatile random access memory. For example, the memory may further store information about a device type. The processor <NUM> may be configured to execute the instructions stored in the memory; and when the processor <NUM> executes the instructions stored in the memory, the processor <NUM> is configured to perform steps and/or procedures corresponding to the first management device or the second management device in the method embodiments.

It should be understood that in this embodiment of this application, the processor of the foregoing apparatus may be a central processing unit (central processing unit, CPU), or the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

In an implementation process, steps in the foregoing methods can be implemented by using a hardware integrated logic circuit in the processor or by using instructions in a form of software. With reference to the steps of the method disclosed in the embodiments of this application may be directly performed by a hardware processor, or may be performed and completed by using a combination of hardware and software units in the processor. The software unit may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor executes the instructions in the memory and completes the steps of the foregoing method in combination with the hardware of the processor. To avoid repetition, details are not described herein again.

It may be understood that the memory in the embodiments of this application may be a volatile memory or a nonvolatile memory, or may include a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM), used as an external cache. Through example but not limitative descriptions, RAMs in many forms may be available, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that the memories in the systems and method described in this specification include but are not limited to these memories and any memory of another proper type.

According to the method provided in the embodiments of this application, this application further provides a computer program product. The computer program product includes computer program code. When the computer program code is run on a computer, the computer is enabled to perform the method in any one of the foregoing embodiments.

According to the method provided in the embodiments of this application, this application further provides a computer-readable medium. The computer-readable medium stores program code. When the program code is run on a computer, the computer is enabled to perform the method in any one of the embodiments shown in <FIG>.

According to the methods provided in the embodiments of this application, this application further provides a system. The system includes the foregoing one or more terminal devices and the foregoing one or more network devices.

In this application, "at least one" refers to one or more, and "a plurality of" refers to two or more. The term "and/or" describes an association relationship between associated objects, and represents that three relationships may exist. For example, A and/or B may represent the following cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. The character "/" generally represents an "or" relationship between the associated objects. "At least one of the following items (pieces)" or a similar expression thereof means any combination of these items, including any combination of singular items (pieces) or plural items (pieces). For example, at least one (piece) of a, b, or c may indicate the following cases: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, method steps and units can be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the interchangeability between the hardware and the software, the foregoing has generally described steps and composition of each embodiment according to functions. Whether the functions are performed by hardware or software depends on a particular application and a design constraint condition of the technical solutions.

A person skilled in the art may clearly understand that, for the purpose of convenient and brief description, for detailed working processes of the foregoing system, apparatus, and unit, refer to corresponding processes in the foregoing method embodiments. In the embodiments of this application, on a premise that there is no logical contradiction, the embodiments may be mutually referenced. For example, methods and/or terms in the method embodiments may be mutually referenced, functions and/or terms in the apparatus embodiments may be mutually referenced, and functions and/or terms in the apparatus embodiments and the method embodiments may be mutually referenced.

For example, the described apparatus embodiments are merely examples. For example, division into the units is merely logical function division and may be other division during actual implementation. In addition, displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections through some interfaces, apparatuses, or units, and may be connections in an electrical form, a mechanical form, or another form.

Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments in this application.

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium.

Claim 1:
A traffic volume prediction method, comprising:
receiving (S210), by a first management device, a first message from a second management device, wherein the first message is used to request the first management device to perform traffic volume prediction, the first message comprises a predicted object, a traffic type, and prediction requirement information, and the prediction requirement information comprises a prediction granularity and/or a prediction period, wherein the prediction granularity comprises at least one of the following: a prediction area, a prediction service type, a prediction slice, a prediction cell, a prediction public land mobile communications network PLMN, or a prediction tenant; and
determining (S220), by the first management device for the predicted object based on the prediction requirement information, a predicted traffic volume corresponding to the traffic type;
wherein the predicted object comprises at least one of the following:
a service, a network, a network element, a network function, or a cell;
wherein the traffic type comprises at least one of the following:
a quantity of users, user distribution, a user activation ratio, coverage, a throughput, a quantity of radio resource control RRC connections, a quantity of physical resource blocks PRBs, PRB usage, or load information.