Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. The method comprises: acquiring a first data volume of a first network element, and the total power consumption and a second data volume of the first network element; and determining first power consumption on the basis of the total power consumption, the first data volume and the second data volume of the first network element. The first data volume is the data volume of first data transmitted by the first network element, the first data is data of a target area or data of a target application, and the second data volume is the total amount of data transmitted by the first network element. According to the solution, power consumption information of a network element can be collected at the granularity of areas or applications.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application with application number 202410409174.7 filed with the State Intellectual Property Office of China on April 3, 2024, and priority to the Chinese patent application with the invention name “Communication Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and device. Background Art

[0003] Operators can deploy carrier networks in certain areas. After terminal devices in these areas connect to the carrier networks, they can communicate with application servers through network elements (NEs) within the carrier networks and use the applications provided by these servers. In some scenarios, the carrier network may need to collect the power consumption generated by NEs serving a specific area or application. This can be done, for example, to adjust the power consumption level in a specific area or to bill an application based on its power consumption. Therefore, collecting NE power consumption information at a regional or application-level granularity is an urgent issue. Summary of the Invention

[0004] The present application provides a communication method and apparatus that can collect power consumption information of network elements at a granularity of area or application.

[0005] In a first aspect, a communication method is provided. The method can be executed by a sixth network element, or can also be executed by a chip or circuit of the sixth network element, and this application does not limit this. For ease of description, the following is an example of execution by the sixth network element. Exemplarily, the sixth network element can be a network data analytics function (NWDAF) network element or an energy efficiency control function (EECF) network element.

[0006] The method includes: obtaining a first data volume of a first network element, total power consumption of the first network element and a second data volume, and determining the first power consumption according to the total power consumption of the first network element, the first data volume and the second data volume.

[0007] The first data volume mentioned above is the data volume of first data transmitted by the first network element, where the first data is data of the target area or data of the target application, and the second data volume is the total amount of data transmitted by the first network element.

[0008] The first power consumption is the power consumption of the first network element for transmitting the first data. Alternatively, the first power consumption is the power consumption of a network for transmitting the first data, and the network includes the first network element.

[0009] In the embodiment of the present application, power consumption may also be referred to as energy consumption, energy consumption, etc.

[0010] In the above technical solution, based on the amount of data of the target area or target application transmitted by the first network element, the total amount of data transmitted by the first network element and the total power consumption of the first network element, the power consumption corresponding to the target area or target application can be determined, thereby achieving the purpose of collecting power consumption information of the first network element at the granularity of area or application.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, the data in the target area includes: data of a terminal device located in the target area. For example, the first network element includes an access network device, the access network device serves the terminal device, and the first data transmitted by the first network element includes downlink data sent by the access network device to the terminal device, and / or uplink data from the terminal device received by the access network device from the terminal device. For another example, the first network element includes a user plane network element, the user plane network element serves the terminal device, that is, serves a session of the terminal device, and the first data transmitted by the first network element includes data of the session transmitted by the user plane network element.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the data of the target area includes: data of the cell corresponding to the target area or the corresponding tracking area (TA). For example, the first network element includes an access network device, and the access network device is located in the target area, or in other words, the coverage area or service range of the access network device includes the target area, and the first data transmitted by the first network element includes one or more of the following data: downlink data sent by the access network device to the terminal device in the cell or TA, uplink data received by the access network device from the terminal device in the cell or TA, or data broadcast by the access network device to the cell or TA. For another example, the first network element includes a user plane network element, and the user plane network element serves one or more terminal devices in the cell or TA, that is, serves the sessions of the one or more terminal devices, and the first data transmitted by the first network element includes the data of the sessions of the one or more terminal devices transmitted by the user plane network element.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a first request message to a second network element, the first request message including information for indicating the target area or the target application; and receiving the first data volume from the second network element.

[0015] In conjunction with the first aspect, in certain implementations of the first aspect, before sending the first request message to the second network element, the method further includes: sending a fourth request message to a third network element, the fourth request message including information indicating the target area or the target application; and receiving information about the second network element from the third network element, for example, receiving a fourth response message from the third network element, the fourth response message responding to the fourth request message, the fourth response message including information about the second network element. In this implementation, sending the first request message to the second network element includes sending the first request message to the second network element based on the information about the second network element.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the first data is data of the target area, the second network element is a session management network element, and the service area of ​​the second network element includes the target area; or, the first data is data of the target application, the second network element is a policy control network element, and the second network element provides policy control for the session used to transmit the data of the target application.

[0017] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving identification information of the one or more user plane network elements from the second network element.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: receiving identification information of one or more sessions from the second network element, the data of the one or more sessions including the first data; obtaining identification information of the one or more user plane network elements based on the identification information of the one or more sessions, the one or more user plane network elements being used to transmit data of at least one of the one or more sessions.

[0019] In combination with the first aspect, in certain implementations of the first aspect, a second request message is sent, which includes identification information of the one or more user plane network elements; and the total power consumption of each user plane network element in the one or more user plane network elements and the total amount of data transmitted by each user plane network element are received.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the first network element includes one or more access network devices, and the method further includes: sending a third request message to the access and mobility management network element, the third request message being used to request that the service area include identification information of access network devices in the first area, wherein the first area is the target area, or the first area is the area where the terminal device using the target application is located; and receiving identification information of the one or more access network devices from the access and mobility management network element.

[0021] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving area information covered by the one or more access network devices from the access and mobility management network element.

[0022] In a second aspect, a communication method is provided. The method may be executed by a second network element, or may be executed by a chip or circuit of the second network element, which is not limited in this application. For ease of description, the following description is based on an example of execution by the second network element. Exemplarily, the second network element may be a session management function (SMF) network element.

[0023] The method includes: receiving a first request message, which includes information for indicating a target area or a target application; sending a first data volume of a first network element, which is the data volume of first data transmitted by the first network element, and the first data is data of the target area or data of the target application.

[0024] In the above technical solution, the session management network element can obtain and send the data volume of the target area or target application transmitted by the first network element based on the first request message, so that the sixth network element can determine the power consumption corresponding to the target area or target application based on the data volume of the target area or target application transmitted by the first network element, thereby achieving the purpose of collecting the power consumption information of the first network element at the granularity of area or application.

[0025] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending identification information of the first network element.

[0026] In combination with the second aspect, in certain implementations of the second aspect, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving a third data volume, the third data volume including the data volume of the first data of each session in one or more sessions; determining the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements based on the third data volume, and the one or more user plane network elements are used to transmit data of at least one session in the one or more sessions.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving identification information of the one or more sessions; and determining identification information of the one or more user plane network elements based on the identification information of the one or more sessions.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the first data is data of the target application, and the method further includes: sending information for indicating a first area, where the first area is an area where a terminal device using the target application is located.

[0030] In a third aspect, a communication method is provided. The method may be executed by a sixth network element, or by a chip or circuit of the sixth network element, although this application does not limit this. For ease of description, the following description uses the sixth network element as an example. Exemplarily, the sixth network element may be an NWDAF network element or an EECF network element.

[0031] The method includes: obtaining total power consumption and a second data volume of a first network element; and determining a first power consumption according to the total power consumption and the second data volume of the first network element, wherein the first network element includes one or more access network devices.

[0032] The second data volume mentioned above is the total amount of data transmitted by the first network element.

[0033] The first power consumption is the power consumption of the first network element for transmitting the first data. Alternatively, the first power consumption is the power consumption of a network for transmitting the first data, and the network includes the first network element.

[0034] In the above technical solution, based on the total amount of data transmitted by the first network element and the total power consumption of the first network element, the power consumption corresponding to the target area or target application can be determined, thereby achieving the purpose of collecting power consumption information of the first network element at the granularity of area or application.

[0035] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: obtaining a first data volume of a first network element; the above-mentioned determination of the first power consumption based on the total power consumption of the first network element and the second data volume includes: determining the first power consumption based on the total power consumption of the first network element, the first data volume and the second data volume.

[0036] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending a third request message to the access and mobility management network element, the third request message being used to request that the service area include identification information of access network devices in a first area, wherein the first area is the target area, or the first area is the area where the terminal device using the target application is located; and receiving identification information of the one or more access network devices from the access and mobility management network element.

[0037] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: receiving information from the access and mobility management network element for indicating areas respectively covered by the one or more access network devices.

[0038] In combination with the third aspect, in certain implementations of the third aspect, the data of the target area includes: data of terminal devices located in the target area.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the data of the target area includes: data of a cell or tracking area (TA) corresponding to the target area.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the first network element also includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0041] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending a first request message to a second network element, the first request message including information for indicating the target area or the target application; and receiving the first data volume from the second network element.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the first data is data of the target area, the second network element is a session management network element, and the service area of ​​the second network element includes the target area; or, the first data is data of the target application, the second network element is a policy control network element, and the second network element provides policy control for the session used to transmit the data of the target application.

[0043] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: receiving identification information of the one or more user plane network elements from the second network element.

[0044] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving identification information of one or more sessions from the second network element, the data of the one or more sessions including the first data; obtaining identification information of the one or more user plane network elements based on the identification information of the one or more sessions, the one or more user plane network elements being used to transmit data of at least one of the one or more sessions.

[0045] In combination with the third aspect, in certain implementations of the third aspect, a second request message is sent, which includes identification information of the one or more user plane network elements; and the total power consumption of each user plane network element in the one or more user plane network elements and the total amount of data transmitted by each user plane network element are received.

[0046] In a fourth aspect, a communication method is provided. The method can be executed by a second network element, or can also be executed by a chip or circuit of the second network element, which is not limited in this application. For ease of description, the following is an example of execution by the second network element. Exemplarily, the second network element can be a session management function (SMF) network element.

[0047] It should be understood that the SMF network element can also be called a session management network element.

[0048] The method includes: receiving a message from a sixth network element for requesting to obtain power consumption information of a target area; obtaining the position of a terminal device (e.g., UE), or the relationship between the terminal device (e.g., UE) and the target area; obtaining a first data volume of the user plane network element based on the position of the terminal device (e.g., UE), or the relationship between the terminal device (e.g., UE) and the target area, the first data volume being the data volume of first data transmitted by the user plane network element, and the first data being the data volume of data of the target area; and sending the first data volume of the user plane network element to the sixth network element.

[0049] One implementation method of obtaining the first data amount of the user plane network element based on the position of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area is: when the position of the terminal device (e.g., UE) is located in the target area, or the relationship between the terminal device (e.g., UE) and the target area is that the terminal device (e.g., UE) is located in the target area, the session management network element obtains the first data amount of the terminal device transmitted by the user plane network element.

[0050] In the above technical solution, the session management network element can obtain the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area, thereby obtaining the first data volume of the user plane network element based on the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area, and sending the first data volume of the user plane network element to the sixth network element. In this way, the sixth network element can determine the power consumption corresponding to the target area based on the data volume of the target area data transmitted by the user plane network element, thereby achieving the purpose of collecting power consumption information of the user plane network element at a regional granularity.

[0051] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned session management network element obtains the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area, including: the session management network element sends a message to the access network device to request the power consumption information of the target area, and the session management network element receives the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area from the access network device.

[0052] For example, the session management network element sends a message for requesting power consumption information of the target area to the access network device through the access and mobility management network element, and the session management network element receives the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area from the access network device through the access and mobility management network element.

[0053] In combination with the fourth aspect, in certain implementations of the fourth aspect, the UPF sends the amount of data transmitted by the UPF for the target area to the session management network element.

[0054] In combination with the fourth aspect, in certain implementations of the fourth aspect, the session management network element sends a request message to the UPF, which is used to request the UPF to transmit the amount of data for the target area, and the UPF sends the amount of data transmitted by the UPF for the target area to the session management network element in response to the request message.

[0055] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the session management network element aggregates and updates local record information.

[0056] The record information summarized and updated by the above-mentioned session management network element includes: the data volume of the terminal device's session, the location information related to the terminal device, and the identification information of the UPF network element related to the terminal device's session.

[0057] In a fifth aspect, a communication method is provided. The method can be executed by a second network element, or can also be executed by a chip or circuit of the second network element, which is not limited in this application. For ease of description, the following is an example of execution by the second network element. Exemplarily, the second network element can be a session management function (SMF) network element.

[0058] The method includes: receiving a message for requesting power consumption information of a target application; obtaining a first data volume of a user-plane network element in response to the message, the first data volume being the data volume of first data transmitted by the user-plane network element, the first data being the data volume of data of the target application, and sending the first data volume to a sixth network element.

[0059] In the above technical solution, the session management network element can obtain a message based on obtaining the power consumption information of the target application, obtain the first data volume of the user-plane network element, and send the first data volume of the user-plane network element to the sixth network element. In this way, the sixth network element can determine the power consumption corresponding to the target application based on the data volume of the target application data transmitted by the user-plane network element, thereby achieving the purpose of collecting power consumption information of the user-plane network element at the application granularity.

[0060] In combination with the fifth aspect, in certain implementations of the fifth aspect, the UPF sends the amount of data transmitted by the UPF for the target application to the session management network element.

[0061] The amount of data transmitted by the UPF for the target application sent by the above-mentioned UPF to the session management network element can be the amount of data transmitted by the UPF for the target application sent by the UPF to the session management network element according to certain events or periodically.

[0062] In combination with the fifth aspect, in certain implementations of the fifth aspect, the session management network element sends a request message to the UPF, which is used to request the UPF to transmit the amount of data for the target application. In response to the request message it received, the UPF sends the amount of data transmitted by the UPF for the target application to the session management network element.

[0063] The above request message includes information about the target application.

[0064] In combination with the fifth aspect, in certain implementations of the fifth aspect, the session management network element aggregates and updates local record information.

[0065] In a sixth aspect, a communication device is provided, including: a processing module and a transceiver module, wherein the processing module is used to obtain a first data volume of a first network element, for example, obtaining the first data volume of the first network element through the transceiver module, the first data volume being the data volume of first data transmitted by the first network element, the first data being the data of a target area or the data of a target application; the processing module is also used to obtain the total power consumption and the second data volume of the first network element, for example, obtaining the total power consumption and the second data volume of the first network element through the transceiver module, the second data volume being the total amount of data transmitted by the first network element; the processing module is also used to determine a first power consumption based on the total power consumption of the first network element, the first data volume and the second data volume, the first power consumption being the power consumption of the first network element for transmitting the first data.

[0066] In combination with the sixth aspect, in certain implementations of the sixth aspect, the data of the target area includes: data of terminal devices located in the target area.

[0067] In combination with the sixth aspect, in certain implementations of the sixth aspect, the data of the target area includes: data of a cell corresponding to the target area.

[0068] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0069] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver module is also used to send a first request message to the second network element, and the first request message includes information for indicating the target area or the target application; the transceiver module is also used to: receive the first data volume from the second network element.

[0070] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first data is data of the target area, the second network element is a session management network element, and the service area of ​​the second network element includes the target area; or, the first data is data of the target application, the second network element is a policy control network element, and the second network element provides policy control for the session used to transmit the data of the target application.

[0071] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver module is further used to receive identification information of the one or more user-plane network elements from the second network element.

[0072] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver module is also used to receive identification information of one or more sessions from the second network element, and the data of the one or more sessions includes the first data; the processing module is also used to obtain identification information of the one or more user-plane network elements based on the identification information of the one or more sessions, and the one or more user-plane network elements are used to transmit data of at least one of the one or more sessions.

[0073] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver module is also used to: send a second request message, which includes identification information of the one or more user plane network elements; the transceiver module also receives the total power consumption of each user plane network element in the one or more user plane network elements and the total amount of data transmitted by each user plane network element.

[0074] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first network element includes one or more access network devices, and the transceiver module is also used to send a third request message to the access and mobility management network element, and the third request message is used to request that the service area include identification information of the access network device of the first area, wherein the first area is the target area, or the first area is the area where the terminal device using the target application is located; the transceiver module is also used to receive identification information of the one or more access network devices from the access and mobility management network element.

[0075] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver module is further used to receive area information covered by the one or more access network devices from the access and mobility management network element.

[0076] In the seventh aspect, a communication device is provided, which includes: a processing module and a transceiver module, wherein the transceiver module is used to receive a first request message, and the first request message includes information for indicating a target area or a target application; the processing module is used to obtain a first data volume of a first network element, and the transceiver module is used to send the first data volume of the first network element, and the first data volume is the data volume of the first data transmitted by the first network element, and the first data is the data of the target area or the data of the target application.

[0077] In combination with the seventh aspect, in some implementations of the seventh aspect, the transceiver module is further used to send identification information of the first network element.

[0078] In combination with the seventh aspect, in certain implementations of the seventh aspect, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0079] In combination with the seventh aspect, in certain implementations of the seventh aspect, the transceiver module is also used to receive a third data volume, which includes the data volume of the first data of each session in one or more sessions; the processing module is also used to determine the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements based on the third data volume, and the one or more user plane network elements are used to transmit data of at least one session in the one or more sessions.

[0080] In combination with the seventh aspect, in certain implementations of the seventh aspect, the transceiver module is also used to receive identification information of the one or more sessions; the processing module is also used to determine the identification information of the one or more user plane network elements based on the identification information of the one or more sessions.

[0081] In combination with the seventh aspect, in certain implementations of the seventh aspect, the first data is data of the target application, and the transceiver module is further used to send information indicating a first area, which is an area where a terminal device using the target application is located.

[0082] In the eighth aspect, a communication device is provided, including: a processing module and a transceiver module, wherein the processing module is used to obtain the total power consumption and the second data volume of the first network element, for example, the total power consumption and the second data volume of the first network element are obtained through the transceiver module, and the processing module is also used to determine the first power consumption based on the total power consumption of the first network element and the second data volume, wherein the first network element includes one or more access network devices.

[0083] In combination with the eighth aspect, in certain implementations of the eighth aspect, the processing module is also used to obtain the first data volume of the first network element, for example, obtaining the first data volume of the first network element through the transceiver module; the processing module is also used to determine the first power consumption based on the total power consumption of the first network element, the first data volume and the second data volume.

[0084] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is also used to send a third request message to the access and mobility management network element, where the third request message is used to request that the service area include identification information of the access network device of the first area, wherein the first area is the target area, or the first area is the area where the terminal device using the target application is located; the transceiver module is also used to receive identification information of the one or more access network devices from the access and mobility management network element.

[0085] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is further used to receive information from the access and mobility management network element for indicating the areas respectively covered by the one or more access network devices.

[0086] In combination with the eighth aspect, in certain implementations of the eighth aspect, the data of the target area includes: data of terminal devices located in the target area.

[0087] In combination with the eighth aspect, in certain implementations of the eighth aspect, the data of the target area includes: data of a cell or tracking area (TA) corresponding to the target area.

[0088] In combination with the eighth aspect, in certain implementations of the eighth aspect, the first network element also includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0089] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is also used to send a first request message to the second network element, where the first request message includes information indicating the target area or the target application; the transceiver module is also used to receive the first data volume from the second network element.

[0090] In combination with the eighth aspect, in certain implementations of the eighth aspect, the first data is data of the target area, the second network element is a session management network element, and the service area of ​​the second network element includes the target area; or, the first data is data of the target application, the second network element is a policy control network element, and the second network element provides policy control for the session used to transmit the data of the target application.

[0091] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is further used to receive identification information of the one or more user plane network elements from the second network element.

[0092] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is also used to receive identification information of one or more sessions from the second network element, and the data of the one or more sessions includes the first data; the processing module is also used to obtain identification information of the one or more user-plane network elements based on the identification information of the one or more sessions, and the one or more user-plane network elements are used to transmit data of at least one of the one or more sessions.

[0093] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver module is also used to send a second request message, which includes identification information of the one or more user plane network elements; the transceiver module is also used to receive the total power consumption of each user plane network element in the one or more user plane network elements and the total amount of data transmitted by each user plane network element.

[0094] In the ninth aspect, a communication device is provided, including: a processing module and a transceiver module, wherein the transceiver module is used to receive a message from a sixth network element for requesting to obtain power consumption information of a target area; the processing module is used to obtain the position of a terminal device (for example, UE), or the relationship between the terminal device (for example, UE) and the target area; the processing module is also used to obtain a first data volume of the user plane network element based on the position of the terminal device (for example, UE), or the relationship between the terminal device (for example, UE) and the target area, the first data volume being the data volume of the first data transmitted by the user plane network element, and the first data being the data volume of the data of the target area; the transceiver module is also used to send the first data volume of the user plane network element to the sixth network element.

[0095] In combination with the ninth aspect, in certain implementations of the ninth aspect, the above-mentioned session management network element obtains the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area, including: the transceiver module is also used to send a message to the access network device for requesting to obtain the power consumption information of the target area, and the transceiver module is also used to receive the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area from the access network device.

[0096] For example, the session management network element sends a message for requesting power consumption information of the target area to the access network device through the access and mobility management network element, and the session management network element receives the location of the terminal device (e.g., UE) or the relationship between the terminal device (e.g., UE) and the target area from the access network device through the access and mobility management network element.

[0097] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver module is also used to send a request message to the UPF, which is used to request the UPF to transmit the amount of data for the target area. The UPF sends the amount of data transmitted by the UPF for the target area to the session management network element based on the request message it received.

[0098] In combination with the ninth aspect, in certain implementations of the ninth aspect, the session management network element aggregates and updates local record information.

[0099] In the tenth aspect, a communication device is provided, including: a transceiver module and a processing module, wherein the transceiver module is used to receive a message from a PCF network element requesting to obtain power consumption information of a target area; the processing module is used to obtain a first data volume of the user plane network element based on the received message, the first data volume being the data volume of the first data transmitted by the user plane network element, the first data being the data volume of the data of the target application, and the transceiver module is also used to send the first data volume to the sixth network element.

[0100] In combination with the tenth aspect, in certain implementations of the tenth aspect, the UPF proactively sends the amount of data transmitted by the UPF for the target area to the session management network element.

[0101] The above-mentioned amount of data that the UPF actively sends to the session management network element for the target area refers to the amount of data that the UPF sends to the session management network element for the target application according to certain events or periodically.

[0102] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver module is also used to send a request message to the UPF, which is used to request the UPF to transmit the amount of data for the target application. The UPF sends the amount of data transmitted by the UPF for the target application to the session management network element based on the request message it received.

[0103] The above request message includes information about the target application.

[0104] In combination with the tenth aspect, in certain implementations of the tenth aspect, the session management network element aggregates and updates local record information.

[0105] In the eleventh aspect, a communication device is provided, comprising a processor, wherein the processor is configured to cause the communication device to execute the method described in the first aspect and any one of the implementations of the first aspect by executing a computer program or instruction, or through a logic circuit; or to cause the communication device to execute the method described in the second aspect and any one of the implementations of the second aspect; or to cause the communication device to execute the method described in the third aspect and any one of the implementations of the third aspect; or to cause the communication device to execute the method described in the fourth aspect and any one of the implementations of the fourth aspect; or to cause the communication device to execute the method described in the fifth aspect and any one of the implementations of the fifth aspect.

[0106] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.

[0107] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.

[0108] In the twelfth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any one of the implementations of the first aspect; or the logic circuit being used to execute the method described in the second aspect and any one of the implementations of the second aspect; or the logic circuit being used to execute the method described in the third aspect and any one of the implementations of the third aspect; or the logic circuit being used to execute the method described in the fourth aspect and any one of the implementations of the fourth aspect; or the logic circuit being used to execute the method described in the fifth aspect and any one of the implementations of the fifth aspect.

[0109] In the thirteenth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any one of the implementations of the first aspect is executed; or, the method described in the second aspect and any one of the implementations of the second aspect is executed; or, the method described in the third aspect and any one of the implementations of the third aspect is executed; or, the method described in the fourth aspect and any one of the implementations of the fourth aspect is executed; or, the method described in the fifth aspect and any one of the implementations of the fifth aspect is executed.

[0110] In the fourteenth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, causes the method described in the first aspect and any implementable embodiment of the first aspect to be executed; or, causes the method described in the second aspect and any implementation embodiment of the second aspect to be executed; or, causes the method described in the third aspect and any implementation embodiment of the third aspect to be executed; or, causes the method described in the fourth aspect and any implementation embodiment of the fourth aspect to be executed; or, causes the method described in the fifth aspect and any implementation embodiment of the fifth aspect to be executed.

[0111] In the fifteenth aspect, a chip is provided, comprising a processor and an interface, for calling and running a computer program stored in a memory from the memory to execute the method described in the first aspect and any one of its implementations; or execute the method described in the second aspect and any one of its implementations; or execute the method described in the third aspect and any one of its implementations; or execute the method described in the fourth aspect and any one of its implementations; or execute the method described in the fifth aspect and any one of its implementations.

[0112] In the sixteenth aspect, a communication system is provided, comprising the communication device in the sixth aspect and any one of the implementations of the sixth aspect, and / or the communication device in the seventh aspect and any one of the implementations of the seventh aspect, and / or the communication device in the eighth aspect and any one of the implementations of the eighth aspect, and / or the communication device in the ninth aspect and any one of the implementations of the ninth aspect, and / or the communication device in the tenth aspect and any one of the implementations of the tenth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0113] Figure 1 is a schematic diagram of the 5G network architecture based on a service-oriented architecture.

[0114] FIG2 is a schematic diagram of network elements included in a target area provided in an embodiment of the present application.

[0115] FIG3 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0116] FIG4 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0117] FIG5 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0118] FIG6 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0119] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0120] FIG8 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0121] FIG9 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0122] FIG10 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0123] FIG11 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0124] FIG12 is a schematic structural diagram of a communication device 1300 provided in an embodiment of the present application.

[0125] FIG13 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application.

[0126] FIG14 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application. DETAILED DESCRIPTION

[0127] The technical solution in this application will be described below with reference to the accompanying drawings.

[0128] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0129] 1. In this application, unless otherwise specified, "plurality" means two or more.

[0130] 2. In this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0131] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0132] At the same time, any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0133] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0134] 5. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. This application does not limit the specific implementation method.

[0135] 6. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0136] 7. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, for example, it may include the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, the sixth generation (6G) network protocol and related protocols used in future communication systems. This application does not limit this.

[0137] 8. The dotted arrows or boxes in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0138] 9. In this application, unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. “And / or” in this application is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0139] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, universal mobile telecommunication system (UMTS), world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) mobile communication system or new radio (NR). Among them, the 5G mobile communication system can be a non-standalone (NSA) or a standalone (SA) network.

[0140] The technical solution provided in this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device to device (D2D) network, machine to machine (M2M) network, Internet of Things (IoT) network or other networks. Among them, the IoT network can include, for example, the Internet of Vehicles. Among them, the communication mode in the Internet of Vehicles system is collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

[0141] The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6G) mobile communication system, etc. This application does not limit this.

[0142] As an example, Figure 1 shows a schematic diagram of a 5G network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1 includes three components: the terminal device component, the data network (DN), and the operator network component. The following briefly describes the functions of some of these network elements.

[0143] In an embodiment of the present application, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.

[0144] A terminal device may be a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connection capabilities. Currently, some examples of terminals include: mobile phones, tablet computers, computers with wireless transceiver capabilities (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes (such as home appliances such as televisions, smart boxes, and game consoles), cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and so on. assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMN), etc.

[0145] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0146] Furthermore, terminal devices can also be end devices in the Internet of Things (IoT) system. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the Internet through communications technology, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. IoT technology, for example, utilizes narrowband (NB) technology to achieve massive connectivity, deep coverage, and power-saving terminals.

[0147] In an embodiment of the present application, the terminal device can also be a vehicle or a whole vehicle, which can achieve communication through the Internet of Vehicles, or it can be a component located in the vehicle (for example, placed in the vehicle or installed in the vehicle), that is, a vehicle-mounted terminal device, a vehicle-mounted module or an on-board unit (OBU).

[0148] In addition, terminal devices can also include sensors such as smart printers, train detectors, and gas stations. Their main functions include collecting data (part of the terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0149] The operator network may include one or more of the following network elements: charging function (CHF) network element, policy control function (PCF) network element, unified data management (UDM) network element, network repository function (NRF) network element, operations, administration and maintenance (OAM) network element, network data analytics function (NWDAF) network element, energy efficiency control function (EECF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, radio access network (RAN) and user plane function (UPF) network element, etc.

[0150] It should be understood that, in the above-mentioned operator network, the part other than the radio access network part can be referred to as the core network part.

[0151] The functions of the above network elements are described in detail below.

[0152] RAN: Used to implement radio-related functions. It includes one or more access network devices or access network elements, which can also be called network equipment.

[0153] As an example, the access network element may be any device with wireless transceiver functions. The device includes but is not limited to: an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or a home Node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It can also be a gNB in ​​a 5G, such as NR, system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), or a base station in a next-generation communication 6G system, etc.

[0154] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), medium access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by both the DU and the CU. It is understood that a network device can be a device that includes one or more of a CU node, a DU node, or an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or may be classified as a network device in a core network (core network, CN), which is not limited in this application.

[0155] Network equipment provides services for cells, and terminal devices communicate with cells through transmission resources allocated by the network equipment (for example, frequency domain resources, or spectrum resources). The cell can belong to a macro base station (for example, a macro eNB or macro gNB), or to a base station corresponding to a small cell. Small cells here can include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0156] AMF network element: responsible for the mobility management of terminal devices, including mobile status management, allocation of temporary identity identifiers for terminal devices, and authentication and authorization of terminal devices.

[0157] SMF network element: responsible for the selection and reselection of UPF network elements, allocation of Internet Protocol (IP) addresses, establishment, modification and release of bearers, and quality of service (QoS) control.

[0158] UDM network element: responsible for managing contract data and notifying the corresponding network element when the contract data is modified.

[0159] UPF network element: responsible for supporting all or part of the following functions: communicating with SMF network elements, forwarding and processing user-plane data according to the rules issued by the SMF network element based on the packet forwarding control policy (PFCP); responsible for routing and forwarding of user-plane data packets in the 5G core network; identifying different data and service types so that the network can distinguish different types of traffic; based on the identified data and service types, executing corresponding actions and policies, such as traffic shaping, priority adjustment, etc., to meet network management and service needs; recording traffic forwarding volume, and being responsible for QoS processing to ensure that data of different service types can receive corresponding service quality guarantees; UPF serves as the connection anchor point, and all core network data can only flow to the external network after being forwarded by UPF.

[0160] CHF network element: also known as the billing network element, is responsible for maintaining billing-related information, including interacting with the SMF network element to obtain billing information and returning information such as billing quota values.

[0161] OAM network element: It is a general term for a group of network management functions, including fault monitoring, fault reporting, fault location, and fault repair.

[0162] NRF network elements: These support network function registration, enabling various functional entities in the network to register with the NRF network element. They also provide discovery capabilities, allowing other network functions to query and discover registered network functions. Furthermore, the NRF network element is responsible for function selection, selecting the most appropriate network function entity for other network functions to interact with based on specific policies or rules.

[0163] The PCF network element is responsible for providing policy control rules for terminal device sessions, including session policies and mobility policies. These policy control rules ensure the effectiveness and security of network services. Furthermore, the PCF network element provides a unified policy framework to implement the policy rules of control plane functions.

[0164] NWDAF network element: Based on network data, it automatically senses and analyzes the network. It can also make decisions based on the current network status and terminal device needs, such as dynamically adjusting network resource allocation and optimizing routing. Furthermore, the NWDAF network element participates in the entire lifecycle of network planning, construction, maintenance, optimization, and operations, making the network easier to maintain and control and improving the efficiency of network resource utilization.

[0165] EECF network element: responsible for real-time monitoring and management of devices in the network to optimize energy utilization and reduce energy consumption.

[0166] The network architecture shown in Figure 1 also includes an application function (AF) network element, which is responsible for providing certain application layer services to terminal devices. When providing services to terminal devices, the AF network element has requirements for the quality of service (QoS) policy and billing policy, and needs to notify the core network. At the same time, the AF network element also needs application-related information fed back by the core network. The AF network element can be a core network element or a network element deployed by a third party. The power consumption collection proposed by the R19 EnergySys project includes but is not limited to: area-based power consumption collection and application-based power consumption collection. The following explains the power consumption collection based on regional granularity and the power consumption collection based on application granularity.

[0167] 1. Area-based power consumption collection:

[0168] Area-based power consumption collection refers to collecting power consumption information of network elements located in a certain area, and / or information on the power consumption consumed by network elements for communicating with devices or network elements in a certain area. For example, in the following scenarios, the operator network needs to collect power consumption at a regional granularity: a) Network elements deployed in remote areas may not be able to connect to the power transmission grid and can only rely on energy sources such as diesel for power supply. The supply of diesel and other energy sources in remote areas is also limited. Therefore, the operator network needs to monitor the power consumption of the area. When it exceeds a certain threshold, it may be necessary to take certain measures to save energy; b) An enterprise rents an operator network to serve the area where a production department of the enterprise is located. If the enterprise wants to monitor the power consumption of this production department to identify whether the equipment of this production department has abnormalities, then the operator network needs to collect and open the power consumption corresponding to the area where this production department is located.

[0169] For example, as shown in Figure 2, the network includes SMF, UPF1, UPF2, UPF3, RAN1, RAN2, and RAN3. SMF controls UPF1, UPF2, and UPF3. UPF1 is connected to RAN1, RAN2, and RAN3, and UPF2 is connected to RAN3.

[0170] Assuming that the target area includes RAN2, RAN3 and UPF2, the power consumption of the target area includes: the power consumption of RAN2 and RAN3, the power consumption of UPF2, and the power consumption of UPF1 caused by sending data to network elements located in the target area (i.e., RAN2 and RAN3) or receiving data from network elements in the target area (i.e., RAN2 and RAN3).

[0171] 2. Application-based power consumption collection:

[0172] Application-based power consumption collection refers to collecting power consumption information for a specific application served by a carrier network. For example, the power consumption generated when the carrier network transmits application data between a terminal device and the server providing the application.

[0173] The purpose of collecting area-based power consumption includes but is not limited to: a) the operator network needs to bill an application based on the power consumption information of the application; b) the application server requests the operator network to open the power consumption information corresponding to the application.

[0174] In view of this, an embodiment of the present application provides a communication method, which can collect power consumption information of network elements at a granularity of area or application.

[0175] Figure 3 is a schematic flow chart of a communication method provided in an embodiment of the present application. The method can be executed by the sixth network element, or by a module and / or device (for example, a chip or integrated circuit, etc.) with corresponding functions installed in the sixth network element, and the present application is not limited thereto. For ease of description, the sixth network element is used as the execution subject for explanation below. Exemplarily, the sixth network element can be an NWDAF network element or an EECF network element. As shown in Figure 3, the method can include steps 410-430, and steps 410-430 are described in detail below. For parts not described in detail, please refer to the above description and existing protocols.

[0176] Step 410: Obtain a first data volume of a first network element.

[0177] In an embodiment of the present application, the sixth network element can obtain the first data volume of the first network element, wherein the first data volume can be the data volume of the first data transmitted by the first network element, and the first data is data of the target area or data of the target application.

[0178] The data of the above-mentioned target area may include data of terminal devices located in the target area, or may also include data of the cell corresponding to the target area, or may also include data of the tracking area (TA) corresponding to the target area. This application does not make specific restrictions on this.

[0179] The above-mentioned first network element may include one or more user plane network elements, or may also include one or more access network devices, and this application does not make specific limitations on this.

[0180] As an example, assuming that the first network element includes one or more user plane network elements, the above-mentioned first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0181] As another example, assuming that the first network element includes one or more access network devices, the first data volume includes the data volume of the first data transmitted by each of the one or more access network devices.

[0182] In a possible implementation manner, the sixth network element obtaining the first data volume from the first network element includes: the sixth network element receiving the first data volume from the second network element.

[0183] In another possible implementation, the sixth network element obtaining the first data volume of the first network element includes: the sixth network element receiving the fourth data volume from the second network element, and determining the first data volume based on the fourth data volume. Exemplarily, the first network element is a user plane network element, the second network element includes session management network element #1 and session management network element #2, and the fourth data volume includes the data volume (denoted as data volume #1) of data transmitted by sessions served by the first network element in sessions managed by session management network element #1, and the data volume (denoted as data volume #2) of data transmitted by sessions served by the first network element in sessions managed by session management network element #2. That is, the sixth network element receiving the fourth data volume sent from the second network element includes: the sixth network element receiving data volume #1 from session management network element #1 and receiving data volume #2 from session management network element #2. In this example, the first data volume includes data volume #1 and data volume #2. The above-mentioned session may be a protocol data unit (PDU) session.

[0184] Exemplarily, the first network element is a user plane network element that serves a session of a terminal device located in a target area, and the fourth data volume is the amount of data transmitted by the user plane network element for the session of the terminal device. In this example, the first data volume includes the amount of data transmitted by the user plane network element for all sessions that meet the above conditions.

[0185] Exemplarily, the first network element is a user-plane network element that serves a session of a terminal device, where the session of the terminal device is used to transmit data of a target application. The fourth data volume is the amount of data in the session of the terminal device transmitted by the user-plane network element that is used to transmit data of the target application. In this example, the first data volume includes the amount of data transmitted by the user-plane network element for all sessions that meet the above conditions.

[0186] Exemplarily, the first network element is a user plane network element, which serves a session of a terminal device, and the fourth data volume is the data volume of the session of a terminal device located in a target area, which is transmitted by the user plane network element and managed by the second network element.

[0187] Exemplarily, the first network element is a user plane network element, which serves a session of a terminal device, and the session of the terminal device is used to transmit data of a target application. The fourth data volume is the data volume transmitted by the user plane network element and managed by the second network element for transmitting data of the target application.

[0188] Optionally, when the sessions managed by session management network element #1 and served by the first network element include multiple sessions, data volume #1 may include the data volume of data transmitted by each of the multiple sessions, or may include the total amount of data transmitted by the multiple sessions. This embodiment of the present application does not limit this. Data volume #2 is similar to data volume #1 and will not be further described.

[0189] In another possible implementation, the sixth network element obtaining the first data amount of the first network element includes: the sixth network element receiving a fifth data amount from the first network element, and determining the first data amount according to the fifth data amount.

[0190] Exemplarily, the first network element is a user plane network element that serves a session of a terminal device located in a target area, and the fifth data volume is the amount of data transmitted by the user plane network element for the session of the terminal device. In this example, the first data volume includes the amount of data transmitted by the user plane network element for all sessions that meet the above conditions.

[0191] Exemplarily, the first network element is a user-plane network element that serves a session of a terminal device, where the session of the terminal device is used to transmit data of a target application. The fifth data volume is the amount of data in the session of the terminal device transmitted by the user-plane network element that is used to transmit data of the target application. In this example, the first data volume includes the amount of data transmitted by the user-plane network element for all sessions that meet the above conditions.

[0192] In an embodiment of the present application, before the sixth network element receives the first amount of data from the second network element, the sixth network element may also send a first request message to the second network element, where the first request message includes information indicating the target area or the target application, and the first request message is used to request the amount of first data transmitted by the first network element.

[0193] For example, the information used to indicate the target area may include but is not limited to: information used to identify one or more cells included in the target area, such as identifiers (IDs) of one or more cells, such as a list of cell identifiers (List of Cell IDs); information on one or more tracking areas (TAs) included in the target area, such as one or more tracking area codes (TACs), such as a list of TACs (List of TACs), etc.

[0194] For example, the information used to indicate the target application may include but is not limited to: address information corresponding to the target application (for example, the IP address of the target application, information used to describe the characteristics of the service data flow of the target application, such as a service data flow description), or identification information of the target application (for example, ApplicationID), etc.

[0195] Optionally, before the sixth network element sends the first request message to the second network element, the method further includes: the sixth network element obtaining information about the second network element. In this implementation, the sixth network element sending the first request message to the second network element may be: the sixth network element sending the first request message to the second network element based on the information of the second network element.

[0196] For example, the sixth network element may obtain the information of the second network element through the following steps 411 to 412 (not shown in FIG. 3 ).

[0197] Step 411: The sixth network element sends a fourth request message to the third network element. Correspondingly, the third network element receives the fourth request message from the sixth network element.

[0198] The fourth request message includes information indicating the target area or the target application, and the fourth request message is used to request information of the second network element.

[0199] Step 412: The third network element sends a fourth response message to the sixth network element. Correspondingly, the sixth network element receives a fourth response message from the third network element. The fourth response message includes information about the second network element.

[0200] For example, after receiving the fourth request message, the third network element obtains the information of the second network element according to the information indicating the target area or the target application.

[0201] In one example, the first data is data of the target area, the second network element is an SMF network element, the service area of ​​the second network element includes the target area, and the third network element is a network repository function (NRF) network element.

[0202] In another example, the first data is the data of the target application, the second network element is a policy control function (PCF) network element, the second network element provides policy control for the session used to transmit the data of the target application, and the third network element is a binding support function (BSF) network element.

[0203] In the case where the first data is data of the target area, the above steps 411 to 412 may be replaced by the following steps 413 to 416 (not shown in FIG. 3 ).

[0204] Step 413: The sixth network element sends a seventh request message to the fourth network element. Correspondingly, the fourth network element receives the seventh request message from the sixth network element.

[0205] The seventh request message includes information indicating the target area, and the seventh request message is used to obtain information for identifying the terminal device located in the target area.

[0206] Step 414: The fourth network element sends a seventh response message to the sixth network element. The seventh response message includes information for identifying the terminal device located in the target area.

[0207] For example, after the fourth network element receives the seventh request message, it obtains information for identifying the terminal device located in the target area based on the information of the target area indicated by the seventh request message, and sends a seventh response message to the sixth network element in response to the seventh request message, and the seventh response message includes information for identifying the terminal device located in the target area.

[0208] Step 415: The sixth network element sends an eighth request message to the fifth network element. Correspondingly, the fifth network element receives the eighth request message from the sixth network element.

[0209] The eighth request message includes information for identifying the terminal device located in the target area, and the eighth request message is used to request information of the second network element.

[0210] Step 416: The fifth network element sends an eighth response message to the sixth network element. The eighth response message includes information about the second network element.

[0211] For example, after the fifth network element receives the eighth request message, it obtains the information of the second network element based on the information used to identify the terminal device located in the target area, and sends an eighth response message to the sixth network element in response to the eighth request message, and the eighth response message includes the information of the second network element.

[0212] In one example, the first data is data of the target area, the second network element is an SMF network element, the second network element manages sessions of terminal devices located in the target area, the fourth network element is an access and mobility management function (AMF) network element, and the fifth network element is a unified data management (UDM) network element.

[0213] Optionally, in some embodiments, the sixth network element may also obtain identification information of the first network element. Different implementations are described below with examples.

[0214] Example 1: The first network element includes one or more user plane network elements. In the embodiment of the present application, the sixth network element can obtain identification information of the one or more user plane network elements. There are many specific implementation methods, and three possible implementation methods are described below.

[0215] In a possible implementation, after receiving the first request message sent by the sixth network element, the second network element may also obtain identification information of one or more user plane network elements and send the identification information of the one or more user plane network elements to the sixth network element.

[0216] Illustratively, the second network element may obtain identification information of the one or more user-plane network elements based on context information of a session stored by the second network element, where the service areas of the one or more user-plane network elements overlap with the target area, and the one or more user-plane network elements serve the session managed by the second network element. For example, the second network element obtains identification information of the one or more user-plane network elements based on identification information of the user-plane network elements included in context information of each session managed by the second network element.

[0217] Exemplarily, the second network element may obtain identification information of the one or more user-plane network elements based on context information of a session stored by the second network element. The one or more user-plane network elements serve the session managed by the second network element, and the one or more user-plane network elements are used to transmit data of the target application. For example, the second network element obtains identification information of the one or more user-plane network elements based on identification information of the user-plane network elements included in context information of each session managed by the second network element.

[0218] In another possible implementation, after receiving the first request message sent by the sixth network element, the second network element may further obtain identification information of one or more sessions and send the identification information of the one or more sessions to the sixth network element. After receiving the identification information of the one or more sessions, the sixth network element may obtain the identification information of the one or more user plane network elements based on the identification information of the one or more sessions. Exemplarily, the sixth network element sends an eleventh request message to the billing network element, and the eleventh request message includes the identification information of one or more sessions. After receiving the request message, the billing network element obtains the identification information of one or more user plane network elements serving the one or more sessions based on the identification of the one or more sessions from its stored information (including the context information of the session), and sends an eleventh response message in response to the eleventh request message to the sixth network element, and the eleventh response message includes the identification information of the one or more user plane network elements.

[0219] In another possible implementation, the first request message sent by the sixth network element includes address information of the sixth network element. After receiving the first request message sent by the sixth network element, the second network element sends a ninth request message to the first network element. The ninth request message includes address information of the first network element. The first network element is an anchor user plane network element for a session of a terminal device located in a target area and managed by the second network element, or is one or more user plane network elements for a session requested by a terminal device located in the target area and managed by the second network element. After receiving the ninth request message, the first network element sends the fifth data volume and identification information of the first network element to the sixth network element based on the sixth address information.

[0220] It should be noted that, in the embodiment of the present application, “reporting” may also mean “sending.” For example, the first network element sends the fifth data volume and the identification information of the first network element to the sixth network element.

[0221] It should be understood that the data of the one or more sessions include the first data, and the one or more user-plane network elements are used to transmit the data of at least one of the one or more sessions.

[0222] Example 2: Assuming that the first network element includes one or more access network devices, the sixth network element in an embodiment of the present application can obtain identification information of the one or more access network devices. In one possible implementation, the sixth network element can send a third request message to the access and mobility management network element, where the third request message is used to request identification information of access network devices whose service area includes the first area. After receiving the third request message, the access and mobility management network element queries the identification information of the one or more access network devices serving the first area, and sends the identification information of the one or more access network devices to the sixth network element.

[0223] It should be understood that the first area may be the target area mentioned above, or may also be the area where the terminal device using the target application mentioned above is located, and the embodiment of the present application does not specifically limit this.

[0224] Optionally, in some embodiments, the sixth network element may further obtain the area information covered by the one or more access network devices. In one possible implementation, the sixth network element may further obtain the area information covered by the one or more access network devices based on the above-mentioned third request message, and send the area information covered by the one or more access network devices to the NWDAF network element or the EECF network element. The area information covered by the access network device may include but is not limited to: information for identifying one or more cells included in the target area, such as one or more cell identifiers (IDs), such as a list of cell identifiers (List of Cell IDs); information on one or more tracking areas (TAs) included in the target area, such as one or more tracking area codes (TACs), such as a list of TACs (List of TACs), etc.

[0225] Step 420: Obtain the total power consumption of the first network element and the second data volume.

[0226] In an embodiment of the present application, the sixth network element may obtain the total power consumption and the second data volume of the first network element. The second data volume may be the total amount of data transmitted by the first network element, the total power consumption of the first network element may be the total power consumption of the first network element for transmitting data, or the total power consumption of the first network element may be the total power consumption of a physical network function (PNF) of the first network element, or the total power consumption of the first network element may be the total power consumption of a virtual network function (VNF) of the first network element.

[0227] As an example, taking the first network element including one or more user plane network elements, the total power consumption of the above-mentioned first network element includes the total power consumption of each user plane network element in the one or more user plane network elements, and the above-mentioned second data volume includes the total amount of data transmitted by each user plane network element in the one or more user plane network elements.

[0228] In one possible implementation, after obtaining identification information of one or more user plane network elements, the sixth network element may send a second request message to the OAM network element, where the second request message includes the identification information of the one or more user plane network elements. After receiving the second request message, the OAM network element may send the total power consumption of each of the one or more user plane network elements and the total amount of data transmitted by each user plane network element to the sixth network element.

[0229] As another example, taking the case where the first network element includes one or more access network devices, the total power consumption of the first network element includes the total power consumption of each of the one or more access network devices, and the second data volume includes the total amount of data transmitted by each of the one or more access network devices.

[0230] In one possible implementation, after obtaining identification information of one or more access network devices, the sixth network element may send a fifth request message to the OAM network element, where the fifth request message includes the identification information of the one or more access network devices. After receiving the fifth request message, the OAM network element may send the total power consumption of each of the one or more access network devices and the total amount of data transmitted by each access network device to the sixth network element.

[0231] Step 430: Determine the first power consumption according to the total power consumption of the first network element, the first data volume, and the second data volume.

[0232] In this embodiment of the present application, the sixth network element may determine the first power consumption based on the total power consumption of the first network element, the first data volume, and the second data volume. The first power consumption may be the power consumption of the first network element used to transmit the first data. Alternatively, it may be understood as the power consumption of a network including the first network element used to transmit the first data.

[0233] In a possible implementation, the sixth network element may determine a ratio of the first data volume to the second data volume, and determine the first power consumption of the first network element according to the ratio and the total power consumption of the first network element.

[0234] In the above technical solution, based on the amount of data of the target area or target application transmitted by the first network element, the total amount of data transmitted by the first network element and the total power consumption of the first network element, the power consumption corresponding to the target area or target application can be determined, thereby achieving the purpose of collecting power consumption information of the first network element at the granularity of area or application.

[0235] Figure 4 is a schematic flow chart of another communication method provided in an embodiment of the present application. The method can be executed by a second network element, or by a module and / or device (e.g., a chip or integrated circuit, etc.) with corresponding functions installed in the second network element, and the present application is not limited thereto. For ease of description, the following description is based on the second network element as the execution entity. Exemplarily, the second network element can be an SMF network element.

[0236] As shown in FIG4 , the method may include steps 510 - 520 , and steps 510 - 520 are described in detail below.

[0237] Step 510: Receive a first request message.

[0238] As an example, the second network element may receive a first request message, where the first request message is used to indicate information about a target area or a target application, and the first request message is used to request a data volume of first data transmitted by the first network element. For specific information about the target area or target application, please refer to the description in FIG3 and will not be repeated here.

[0239] In a possible implementation, the second network element may receive the first request message sent by the sixth network element.

[0240] In another possible implementation, the second network element may receive the first request message sent by the policy control network element.

[0241] Step 520: Send the data volume of the first network element.

[0242] As an example, the second network element may obtain the data volume of the first network element according to the first request message, and send the data volume of the first network element to the NWDAF network element or the EECF network element.

[0243] In one possible implementation, if the session served by the user-side network element is managed by only a second network element, the second network element obtains the data volume of the first network element based on the first request message, that is, the first data volume of the first network element, and the second network element can send the first data volume to the sixth network element.

[0244] In another possible implementation, if a session served by a user-plane network element is managed by multiple second network elements, each second network element may send the data volume of the first network element obtained by each second network element based on the first request message, that is, the fourth data volume of the first network element, to a sixth network element. After the sixth network element receives the fourth data volume of the first network element sent by each second network element, it may combine the fourth data volumes of the first network element sent by the multiple second network elements to obtain the first data volume of the first network element. For example, the sixth network element may determine the sum of the fourth data volumes of the first network element sent by the multiple second network elements as the first data volume of the first network element.

[0245] It should be understood that for the description of the first data volume, please refer to the description in FIG3 , which will not be repeated here.

[0246] Optionally, in some embodiments, taking the example that the first network element includes one or more user plane network elements, the second network element can also obtain identification information of the one or more user plane network elements and send the identification information of the one or more user plane network elements to the sixth network element.

[0247] In a possible implementation, the second network element may obtain identification information of one or more user plane network elements according to stored context information.

[0248] In another possible implementation, the second network element may also send a sixth request message to the billing network element, wherein the sixth request message includes information of the target area or target application. The billing network element obtains the identification information of the one or more user plane network elements based on the information of the target area or target application, and sends a sixth response message to the SMF network element in response to the sixth request message, wherein the sixth response message includes the identification information of the one or more user plane network elements.

[0249] In another possible implementation, after receiving the sixth request message sent by the second network element, the billing network element may obtain the identifiers of one or more sessions based on the target area or target application information included in the sixth request message, and send a sixth response message in response to the sixth request message, where the sixth response message includes the identifiers of the one or more sessions. After receiving the identifiers of the one or more sessions, the SMF network element may determine the identification information of the one or more user plane network elements based on the identifiers of the one or more sessions.

[0250] There are many ways to implement the above-mentioned second network element obtaining the data volume of the first network element based on the first request message. The embodiment of the present application does not make specific limitations on this. Below, taking the second network element obtaining the first data volume of the first network element as an example, several possible implementation methods are listed.

[0251] In a possible implementation, the second network element may obtain the first data volume of the first network element according to the stored context information.

[0252] In another possible implementation, after receiving the sixth request message sent by the second network element, the billing network element may obtain a third data volume based on the target area or target application information included in the sixth request message, where the third data volume includes the data volume of the first data of each of the one or more sessions, and send a sixth response message in response to the sixth request message, where the sixth response message includes the third data volume. After receiving the third data volume, the second network element may determine, based on the third data volume, the data volume of the first data transmitted by each of the one or more user plane network elements, where the one or more user plane network elements are used to transmit data of at least one of the one or more sessions.

[0253] In another possible implementation, the second network element receives the fourth data volume from one or more user-plane network elements. For example, after receiving the first request message, the second network element sends a tenth request message to the one or more user-plane network elements. After receiving the tenth request message, the one or more user-plane network elements respectively send a tenth response message in response to the tenth request message to the second network element. The tenth response message includes the fifth data volume, and the second network element determines the first data volume based on the fifth data volume.

[0254] Below, in combination with Figures 5-7 and 11, taking the sixth network element as the NWDAF network element / EECF network element and the second network element as the SMF network element, and taking the determination of the power consumption of the target area as an example, a specific method of the communication method provided in the embodiment of the present application is described in detail. It should be understood that the examples of Figures 5-7 and 11 are only to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the application embodiments to the specific numerical values ​​or specific scenarios illustrated in Figures 5-7 and 11. Those skilled in the art can obviously make various equivalent modifications or changes based on the following examples given in Figures 5-7 and 11, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0255] FIG5 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG5 , the method may include S610 - S685 , and S610 - S685 are described in detail below.

[0256] It should be understood that the following S610-S650 is to obtain the data and power consumption of the UPF network element, and S655-S685 is to obtain the data and power consumption of the access network device. The order of these two parts is not limited in this application.

[0257] It should also be understood that the UPF network element below corresponds to the user plane network element mentioned above.

[0258] S610: The AF network element sends message 1 to the NWDAF network element / EECF network element.

[0259] The message 1 is used to request relevant information for determining the power consumption of the target area.

[0260] For example, the AF network element may send a message 1 to the NWDAF network element / EECF network element, where the message 1 is used to request information about power consumption of a target area.

[0261] As an example, the message 1 may be a Nnwdaf_EventExposure_Subscribe Request message.

[0262] For example, the message 1 may include but is not limited to: information for indicating the target area, which may include but is not limited to: a list of cell IDs of the target area, and a list of TACs of the target area.

[0263] Optionally, the message 1 may further include at least one of the following information:

[0264] 1) Request granularity: based on the power consumption of the region;

[0265] 2) Time information: Indicates that the power consumption of the target area is the energy consumption generated by the network element serving the target area during the time period indicated by the time information. In one example, the time information includes the start time and end time of the time period. In another example, the time information includes the start time and duration of the time period. In another example, the time information includes the duration of the time period, and the start time of the time period is the current system time. In another example, the time information includes the end time of the time period, and the start time of the time period is the current system time.

[0266] It should be understood that the above current system time may be the time when the AF network element sends the message 1, or the time when the NWDAF network element / EECF network element receives the message 1.

[0267] S615: The NWDAF network element / EECF network element sends message 2 to the NRF network element.

[0268] Among them, the message 2 is used to request the identifier of the SMF network element corresponding to the above-mentioned target area.

[0269] For example, after receiving message 1 sent by the AF network element, the NWDAF network element / EECF network element can send message 2 to the NRF network element, where message 2 is used to request the identifier of the SMF network element corresponding to the above-mentioned target area.

[0270] It should be understood that message 2 may correspond to the fourth request message mentioned above.

[0271] For example, the above message 2 may be a Nnrf_NFDiscovery_Request message.

[0272] For example, the message 2 may include but is not limited to: information for indicating the target area, including but not limited to: a list of cell IDs corresponding to the target area, and a list of TACs corresponding to the target area.

[0273] Optionally, message 2 may further include at least one of the following information:

[0274] 1) Request granularity: based on the power consumption of the region;

[0275] 2) Time information.

[0276] It should be understood that the time information contained in message 2 is similar to the time information contained in message 1. For details, please refer to the description of the time information in the above message 1, which will not be repeated here.

[0277] S620: The NRF network element sends message 3 to the NWDAF network element / EECF network element.

[0278] The message 3 includes identification information of the SMF corresponding to the target area.

[0279] For example, after receiving message 2 sent by the NWDAF network element / EECF network element, the NRF network element obtains the identification information of the SMF corresponding to the target area contained in message 2, and can send message 3 to the NWDAF network element / EECF network element, which includes the identification information of the SMF corresponding to the above target area.

[0280] For example, the above message 3 may be a Nnrf_NFDiscovery_Request Response message.

[0281] For example, message 3 may include: identification information of the SMF network element (such as SMFID, which may be an IP address or a fully qualified domain name (FQDN)).

[0282] Optionally, message 3 may also include: area information corresponding to the SMF network element, such as the TAC list (list of TAC) corresponding to the SMF network element, or the service area of ​​the SMF network element.

[0283] It should be noted that the identification information of the SMF network element returned in the above message 3 may be the identification information of a single SMF network element, or it may be a list containing identification information of multiple SMF network elements.

[0284] Optionally, the list containing identification information of multiple SMF network elements may also include area information corresponding to the multiple SMF network elements.

[0285] S625: The NWDAF network element / EECF network element sends message 4 to the corresponding SMF network element according to the identification information of the SMF network element in message 3.

[0286] The message 4 is used to request: information related to determining power consumption of the target area.

[0287] The relevant information used to determine the power consumption of the target area may include: identification information of the UPF network element corresponding to the target area and the amount of data transmitted by the UPF network element for the target area. The UPF network elements corresponding to the target area refer to those whose service areas include the target area, that is, the sessions served by these UPF network elements include sessions of terminal devices located in the target area.

[0288] For example, after the NWDAF network element / EECF network element receives message 3 sent by the NRF network element, it can send message 4 to the SMF network element indicated by the identification information of the SMF network element.

[0289] It should be understood that message 4 may correspond to the first request message mentioned above.

[0290] For example, the above message 4 may be an Nsmf_EnergyEfficiency_EnergyConsumption request message.

[0291] For example, the message 4 sent by the above-mentioned NWDAF network element / EECF network element to the SMF network element may include but is not limited to: area information, which may indicate the target area included in the message 1 received by the NWDAF network element / EECF network element in S610, or may also indicate a partial area, for example, the partial area is the area where the target area overlaps with the service area of ​​a certain SMF network element that receives the message 4.

[0292] Optionally, message 4 may also include: time information.

[0293] It should be understood that the time information contained in message 4 is similar to the time information contained in message 1. For details, please refer to the description of the time information in the above message 1, which will not be repeated here.

[0294] S630: The SMF network element sends message 5 to the billing network element.

[0295] Message 5 is used to request relevant information for determining the power consumption of the target area.

[0296] For example, after the SMF network element receives message 4 sent by the NWDAF network element / EECF network element, it can send message 5 to the billing network element. Message 5 includes the area information in message 4, and the message 5 is used to request: relevant information for determining the power consumption of the area corresponding to the area information.

[0297] For example, the message 5 may be an Nchf_ConvergedCharging_DataRequest Request message.

[0298] Optionally, message 5 may also include, but is not limited to, one or more of the following information:

[0299] 1) Identification information of the UPF network element corresponding to the area information in message 4;

[0300] For example, the SMF network element obtains the identification information of the corresponding UPF network element (such as UPFID, which may be an IP address or FQDN) according to the area information in message 4;

[0301] Exemplarily, the SMF network element can obtain the identification information of the UPF network element by querying the NRF network element; or obtain the identification information of the UPF network element whose service area overlaps with the area indicated by the information of the area included in message 4 based on the service areas of multiple UPF network elements obtained when the SMF network element and the UPF network element perform N4 interaction; or assuming that the service area of ​​the SMF network element belongs to the area indicated by the information of the area included in message 4, the SMF network element can obtain the identification information of the UPF network element by querying the context information of the session it manages stored locally. For example, the SMF network element obtains the identification information of the one or more UPF network elements based on the identification information of the user plane network element contained in the context information of each session it manages.

[0302] 2) Identification information of the UPF network element session corresponding to the area information in message 4;

[0303] For example, the SMF network element obtains the identifier of the session including the UPF (eg, SessionID) based on the obtained identification information of the UPF.

[0304] For another example, when the SMF network element determines the session identifier (eg, SessionID) by querying the context information of the session it manages stored locally.

[0305] 3) Time information, which can be the same as the time information in message 4.

[0306] S635: The charging network element sends a message 6 to the SMF network element. The message 6 includes relevant information for determining the power consumption of the target area.

[0307] For example, after receiving message 5 sent by the SMF network element, the billing network element can query the locally stored information, obtain relevant information that can be used to calculate power consumption, and send relevant information for determining the power consumption of the target area to the SMF through message 6.

[0308] As an example, the billing network element obtains relevant information for calculating the power consumption of the target area based on message 5 sent by the SMF network element in combination with the stored information (such as the CDR information in Table 2). The specific acquisition process is illustrated below.

[0309] For example, if message 5 includes regional information, the charging network element will filter out the corresponding entry from the stored information based on the cell global identifier (CGI), tracking area identity (TAI), and other information contained in the provided regional information. For example, the corresponding entry is found based on the terminal device location information (UE Location Info) in Table 1.

[0310] For another example, if message 5 includes identification information of the UPF network element (e.g., UPFID), the billing network element may first find an entry in the stored information that is identical to the UPFID in message 5 based on the UPFID included in message 5 before filtering the stored information based on the area information included in message 5. This can avoid the excessive burden caused by the billing network element filtering the stored information based solely on the area information in message 5.

[0311] For another example, if message 5 includes a session identifier (e.g., Session ID), the charging network element may first find the entry in the stored information that has the same Session ID according to the Session ID included in message 5 before filtering the stored information based on the regional information included in message 5. This avoids the excessive burden on the CHF caused by filtering the stored information based solely on the "regional information" in message 5.

[0312] For another example, further, when the billing network element is checking, if message 5 includes time information, the billing network element can further filter based on the time information. The timing of filtering may not be limited. For example, the filtering result may be obtained based on the information of the area included in message 5, or the UPFID included in message 5, or the SessionID included in message 5, and then the result may be further filtered based on the time information; or the filtering may be performed based on the time information included in message 5 to obtain the filtering result, and then the filtering result may be further filtered based on the information of the area provided in message 5, or the UPFID included in message 5, or the SessionID included in message 5; or the filtering may be performed based on the information of the area, UPFID, SessionID and time information included in message 5 to obtain the filtering result. This embodiment of the present application does not limit this.

[0313] For example, the message 6 may be an Nchf_ConvergedCharging_DataRequest Response message.

[0314] For example, the message 6 may include the amount of data transmitted by the UPF in the target area in Table 1. Optionally, the message 6 may also include other information in Table 1, such as the identifier of the UPF.

[0315] Table 1

[0316] Table 2

[0317] S640: The SMF network element sends message 7 to the NWDAF network element / EECF network element.

[0318] The message 7 includes information for determining the power consumption of the target area.

[0319] For example, the above message 7 may be an Nsmf_EnergyEfficiency_EnergyConsumption response message.

[0320] For example, the above message 7 may include one or more information in Table 1.

[0321] S645: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0322] The message 8 includes the identifier of the UPF network element, and is used to request the total amount of data transmitted by these UPF network elements and the power consumption value (total power consumption).

[0323] Optionally, before the NWDAF network element / EECF network element sends message 8 to the OAM system, it may first obtain a first data amount based on the information obtained in S640. For example, at S640, the NWDAF network element / EECF network element obtains the data amount transmitted by each PDU session managed by each SMF network element. The NWDAF network element / EECF network element may sum the data amount involving a certain UPF to obtain the first data amount.

[0324] For example, after receiving message 7 sent by the SMF network element, the NWDAF network element / EECF network element may send message 8 to the OAM system.

[0325] It should be understood that message 8 may correspond to the second request message mentioned above.

[0326] It should be noted that the OAM system mentioned above is not limited to a specific network element, but refers to the network element belonging to the OAM system. When this network element receives message 8, it may process it internally or send a request to other network elements, which is not limited here.

[0327] For example, the above message 8 may be a UPFInformationRequest message.

[0328] S650: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0329] The message 9 includes the total amount of data transmitted by a given UPF and the total power consumption.

[0330] For example, after the OAM system receives message 8 sent by the NWDAF network element / EECF network element, it queries the total amount of data transmitted and the total power consumption of the given UPF, and sends the total amount of data transmitted and the total power consumption of the given UPF to the NWDAF network element / EECF network element through message 9.

[0331] For example, message 9 may include the following information: the identifier of the UPF, and the total amount of data transmitted by each UPF and the total power consumption.

[0332] At this point, the NWDAF network element / EECF network element obtains the following information:

[0333] 1) UPF network element identification list;

[0334] 2) The total amount of data transmitted by the UPF network element;

[0335] 3) Data transmission volume of the UPF network element in the target area (see total volume in Table 1);

[0336] 4) UPF network element power consumption value (EnergyConsumption).

[0337] S655: The NWDAF network element / EECF network element sends message 10 to the NRF network element.

[0338] For example, the NWDAF network element / EECF network element can send message 10 to the NRF network element, where message 10 is used to request the identifier of the AMF network element corresponding to the above-mentioned target area.

[0339] For example, the message 10 may be an Nnrf_NFDiscovery_Request message.

[0340] For example, the message 10 includes but is not limited to: target area information (Area information).

[0341] Optionally, the message 10 may also include: time information.

[0342] It should be understood that the time information contained in message 10 is similar to the time information contained in message 1. For details, please refer to the description of the time information in the above message 1, which will not be repeated here.

[0343] S660: The NRF network element sends message 11 to the NWDAF network element / EECF network element.

[0344] Among them, the message 11 includes the identification information of the AMF corresponding to the above-mentioned target area.

[0345] For example, after receiving message 10 sent by the NWDAF network element / EECF network element, the NRF network element obtains the identification information of the AMF corresponding to the target area contained in message 10, and can send message 11 to the NWDAF network element / EECF network element, which includes the identification information of the AMF corresponding to the above-mentioned target area.

[0346] For example, the above message 11 may be a Nnrf_NFDiscovery_Request Response message.

[0347] For example, the message 11 sent by the above-mentioned NRF network element to the NWDAF network element / EECF network element may include: identification information of the AMF network element (for example, AMFID, which can be an IP address or a fully qualified domain name (FQDN)).

[0348] Optionally, message 11 may also include: area information corresponding to the AMF network element (for example, a list of TACs corresponding to the AMF network element), or the service area of ​​the AMF network element.

[0349] It should be noted that the identification information of the AMF network element returned in the above message 11 may be the identification information of a single AMF network element, or it may be a list containing the identification information of multiple AMF network elements.

[0350] Optionally, this list containing identification information of multiple AMF network elements will also include area information corresponding to the multiple AMF network elements.

[0351] It should be noted that S615-S620 and S655-S660 can be executed together (for example, using the same message) or separately, and this application is not limited here.

[0352] S665: The NWDAF network element / EECF network element sends message 12 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 11.

[0353] The message 12 is used to request identification information of an access network device corresponding to a target area.

[0354] For example, after the NWDAF network element / EECF network element receives message 11 sent by the NRF network element, it can send message 12 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 11. The message 12 is used to request the identification information of the access network device corresponding to the target area.

[0355] It should be understood that message 12 may correspond to the third request message mentioned above.

[0356] For example, the message 12 may be a Namf_EnergyEffciency Request message.

[0357] For example, the message 12 sent by the above-mentioned NWDAF network element / EECF network element to the AMF network element may include: area information, which may be the information of the target area included in the message 1 received by the NWDAF network element / EECF network element in S610, or it may be information of a partial area. For example, the information of the partial area refers to the information of the area where the target area in the message 1 overlaps with the service area of ​​the AMF network element that receives the message 12.

[0358] Optionally, the above message 12 also includes time information corresponding to the request information, which may be the same as the time information corresponding to the request message 1.

[0359] S670: The AMF network element sends message 13 to the NWDAF network element / EECF network element.

[0360] The message 13 includes identification information of the access network device corresponding to the area.

[0361] For example, the above message 13 may be a Namf_EnergyEffciency response message.

[0362] For example, the message 13 may include identification information of the access network device. For example, the message 13 may include: identification information of the access network device, for example, the identification information of the access network device is a Global RANID (global base station identification information), such as a Global gNB ID, a Global ng-eNB ID, etc., which may be a string of 22 to 32 bits; or the identification information of the access network device is a RANID (base station identification information), such as a gNB ID, an ng-eNB ID.

[0363] Optionally, the message 13 may further include information on the coverage area corresponding to the access network device, such as CellID, CGI, TAI, etc.

[0364] S675: The NWDAF network element / EECF network element sends message 14 to the OAM system.

[0365] The message 14 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0366] For example, after the NWDAF network element / EECF network element receives message 13 sent by the AMF network element, it can send message 14 to the OAM system, where message 14 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0367] It should be understood that message 14 may correspond to the fifth request message mentioned above.

[0368] It should be noted that the OAM system mentioned here is not limited to a specific network element, but refers to the network element belonging to the OAM system. When this network element receives message 8, it may process it internally or send a request to other network elements, which is not limited here.

[0369] For example, the message 14 may be a RANInformationRequest message.

[0370] S680: The OAM system sends message 15 to the NWDAF network element / EECF network element.

[0371] The message 15 includes the total amount of data transmitted by a given access network device and a power consumption value (total power consumption).

[0372] For example, after the OAM system receives message 14 sent by the NWDAF network element / EECF network element, it queries the total amount of data transmitted by a given access network device and the power consumption value (total power consumption), and sends the total amount of data transmitted by the given access network device and the power consumption value (total power consumption) to the NWDAF network element / EECF network element through message 15.

[0373] For example, the message 15 may include but is not limited to the following information: an identification of the access network device, a total amount of data transmitted by each access network device, and a power consumption value (EnergyConsumption).

[0374] At this point, the NWDAF network element / EECF network element obtains the following information:

[0375] 1) List of identifications of access network devices;

[0376] 2) The total amount of data transmitted by access network equipment;

[0377] 3) the data transmission volume of the access network equipment in the target area (e.g., through the total volume in Table 1);

[0378] 4) Power consumption of access network equipment (EnergyConsumption).

[0379] Optionally, the data transmission volume of the access network device in the target area can be obtained in the following ways: 1) the access network device returns the information of the coverage area corresponding to the access network device in S670; 2) the NWDAF network element / EECF network element obtains the transmission data volume corresponding to a certain UElocationinfo through message 7 of S640; 3) the NWDAF network element / EECF network element can associate the information obtained in 1) and 2) to obtain the data transmission volume of the access network device within the target area.

[0380] Optionally, in some embodiments, assuming that the OAM system stores (or can calculate) content similar to Table 3, the above S655-S680 may also only execute S675-S680.

[0381] Table 3

[0382] S685: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target area according to the information obtained.

[0383] For example, the NWDAF network element / EECF network element may calculate the power consumption corresponding to the target area based on the following information obtained.

[0384] 1) UPF network element identification list;

[0385] 2) The total amount of data transmitted by the UPF network element;

[0386] 3) Data transmission volume of the UPF network element within the target area (see total volume in Table 1);

[0387] 4) UPF network element power consumption value (EnergyConsumption);

[0388] 5) List of identifications of access network devices;

[0389] 6) The total amount of data transmitted by access network equipment;

[0390] 7) Data transmission volume of the access network device within the target area (see S680);

[0391] 8) Power consumption of access network equipment (EnergyConsumption).

[0392] In the above technical solution, NWDAF / EECF can obtain information such as energy consumption and data volume of network elements related to the target area of ​​the request through the interaction between NWDAF / EECF network elements and SMF network elements, AMF network elements and OAM, thereby supporting the network to "count the total power consumption in a certain area". This will only cause minor changes to the existing process and does not require additional recording of other content.

[0393] FIG6 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG6 , the method may include S710 - S799 , and S710 - S799 are described in detail below.

[0394] It should be understood that the following S710-S770 is to obtain the data and power consumption of the UPF network element, and S770-S799 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0395] S710: The AF network element sends message 1 to the NWDAF network element / EECF network element.

[0396] The message 1 is used to request to obtain relevant information for determining the power consumption of the target area.

[0397] Similar to S610, please refer to the description in S610 for details, which will not be repeated here.

[0398] S715: The NWDAF network element / EECF network element sends message 2 to the NRF network element.

[0399] Among them, the message 2 is used to request the identifier of the SMF network element corresponding to the above-mentioned target area.

[0400] Similar to S615, please refer to the description in S615 for details, which will not be repeated here.

[0401] S720: The NRF network element sends message 3 to the NWDAF network element / EECF network element.

[0402] The message 3 includes identification information of the SMF corresponding to the target area.

[0403] Similar to S620, please refer to the description in S620 for details, which will not be repeated here.

[0404] S725: The NWDAF network element / EECF network element sends message 4 to the corresponding SMF network element according to the identification information of the SMF network element indicated in message 3.

[0405] The message 4 is used to request to obtain relevant information for determining the power consumption of the target area.

[0406] Similar to S625, please refer to the description in S625 for details, which will not be repeated here.

[0407] S730: The SMF network element sends message 16 to the AMF network element.

[0408] Message 16 is used to request the location information of the UE, or the relationship between the UE and the area received in S725.

[0409] For example, the message 16 may be a Namf_EventExposure_Subscribe Request message.

[0410] For example, the above message 16 can be a message sent by the SMF network element to the AMF network element for each PDU session it manages.

[0411] For example, the message 16 may include one or more of the following information:

[0412] 1) The area information received in S725;

[0413] 2) Indication information of UE location.

[0414] S735: The AMF network element sends message 17 to the access network device.

[0415] Message 17 includes area information or information indicating the location of the UE.

[0416] For example, if message 16 in S730 contains area information, then message 17 sent by the AMF network element to the access network device where the UE currently resides may be a Locationreportcontrol message, which contains the area information received in S730.

[0417] For example, if message 16 in S730 contains information indicating the UE location, then message 17 sent by the AMF network element to the access network device where the UE currently resides may be a Location report control message, which contains information indicating the UE's current location.

[0418] S740: The access network device sends message 18 to the AMF network element.

[0419] Message 18 includes the current location of the UE, or the correspondence between the UE and the target area.

[0420] For example, when the access network device receives a request message 17 from the AMF network element, if the message 17 received in S735 contains area information, the access network device will detect the relationship between the UE's current location and the area information. If the current UE enters this area or leaves this area, the access network device sends a message 18 to the AMF network element. Message 18 includes the UE's current location, or the correspondence between the UE and the current area.

[0421] For example, message 18 may be a Location report message.

[0422] For example, when the access network device receives message 17, it may immediately send a Locationreport message.

[0423] For example, message 18 may include one or more of the following information:

[0424] 1) The correspondence between the UE and the current area, for example, "UE is in the area", "UE is not in the area";

[0425] 2) The current location of the UE.

[0426] S745: The AMF network element sends message 19 to the SMF network element.

[0427] Message 19 includes the current location of the UE, or the correspondence between the UE and the current area.

[0428] For example, message 19 may be a Namf_EventExposure_Subscribe notify message.

[0429] For example, message 19 may include one or more of the following information:

[0430] 1) The correspondence between the UE and the current area, for example, "UE is in the area", "UE is not in the area";

[0431] 2) The current location of the UE.

[0432] S750: The SMF network element determines whether the UE is in the target area.

[0433] In the embodiment of the present application, after the SMF network element receives the message 19 from the AMF network element, it determines whether the UE is in the target area (the area corresponding to S725) based on the current information. When the UE is in the target area, S755-758 are executed; or another implementation method is that the SMF network element obtains the amount of transmitted data from the UPF network element based on S755-758 on a regular basis or based on an event trigger, and records it when the SMF network element determines that the UE is in the target area.

[0434] S755: The SMF network element sends message 20 to the UPF network element.

[0435] Among them, message 20 is used to request the UPF network element to send the amount of data it transmits for the target area.

[0436] For example, the message 20 may be an N4 modification request message.

[0437] For example, the message 20 may include information indicating the amount of data to be sent.

[0438] Optionally, message 20 may also include a sending period for the amount of data to be sent.

[0439] It should be understood that if the UPF network element continuously sends the transmitted data volume without the need for the SMF network element to actively subscribe, then S755 is optional.

[0440] S758: The UPF network element sends message 21 to the SMF network element.

[0441] Among them, message 21 includes the amount of data transmitted by the UPF network element for the target area.

[0442] For example, the message 21 may be an N4 notification message.

[0443] For example, message 21 may include: the amount of data transmitted by the UPF network element.

[0444] Optionally, message 21 may also include: time information corresponding to the amount of data transmitted by the UPF network element, such as time length information, start time and end time information, etc.

[0445] S760: The SMF network element summarizes and updates the local record information based on the information sent by the UPF network element.

[0446] In an embodiment of the present application, the SMF network element can summarize the total amount of data transmission of the UPF network element. For example, the SMF network element adds up the transmission data of all PDU sessions of a given UPF network element at a given location.

[0447] It should be understood that if the SMF network element can be sent directly to the NWDAF network element, and the NWDAF network element performs the summary calculation, then S760 is optional.

[0448] S765: The SMF network element sends message 22 to the NWDAF network element / EECF network element.

[0449] For example, the message 22 may be an Nsmf_EnergyEfficiency_EnergyConsumption response message.

[0450] For example, message 22 may include one or more of the following information:

[0451] 1) PDU session identification information;

[0452] 2) Terminal location information, such as CellID, CGI, TAC, TAI, etc.;

[0453] 3) Information on the amount of data transmitted, such as the amount of data transmitted at a certain location in a PDU session, such as bit, byte (B), kb, kB, Mb, MB, etc.;

[0454] 4) Identification information of the UPF involved, such as FQDN, IP address, etc.

[0455] For example, the message 22 may include at least one of the information in Tables 4-6 below.

[0456] Table 4

[0457] Table 5

[0458] Table 6

[0459] S768: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0460] The message 8 is used to request the total amount of data transmitted by a given UPF network element and the power consumption value (total power consumption).

[0461] Similar to S645, please refer to the description in S645 for details, which will not be repeated here.

[0462] S770: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0463] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0464] Similar to S650, please refer to the description in S650 for details, which will not be repeated here.

[0465] S775: The NWDAF network element / EECF network element sends message 10 to the NRF network element.

[0466] Among them, message 10 is used to request the identification of the AMF network element corresponding to the above-mentioned target area.

[0467] Similar to S655, please refer to the description in S655 for details, which will not be repeated here.

[0468] S780: The NRF network element sends message 11 to the NWDAF network element / EECF network element.

[0469] Among them, the message 11 includes the identification information of the AMF corresponding to the above-mentioned target area.

[0470] Similar to S660, please refer to the description in S660 for details, which will not be repeated here.

[0471] S785: The NWDAF network element / EECF network element sends message 12 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 11.

[0472] The message 12 is used to request identification information of an access network device corresponding to a target area.

[0473] Similar to S665, please refer to the description in S665 for details, which will not be repeated here.

[0474] S790: The AMF network element sends message 13 to the NWDAF network element / EECF network element.

[0475] The message 13 includes identification information of the access network device corresponding to the area.

[0476] Similar to S670, please refer to the description in S670 for details, which will not be repeated here.

[0477] S795: The NWDAF network element / EECF network element sends message 14 to the OAM system.

[0478] The message 14 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0479] Similar to S675, please refer to the description in S675 for details, which will not be repeated here.

[0480] S798: The OAM system sends message 15 to the NWDAF network element / EECF network element.

[0481] The message 15 includes the total amount of data transmitted by a given access network device and a power consumption value (total power consumption).

[0482] Similar to S680, please refer to the description in S680 for details, which will not be repeated here.

[0483] S799: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target area according to the information obtained.

[0484] Similar to S685, please refer to the description in S685 for details, which will not be repeated here.

[0485] In the above technical solution, the NWDAF network element / EECF network element can obtain the network element's energy consumption, data volume and other information based on the requested area through the interaction between the NWDAF network element / EECF network element and the SMF network element, AMF network element and OAM. Without relying on billing information, it supports the network to "count the total power consumption in a certain area". This will cause little change to the existing process and does not require additional recording of other content.

[0486] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG7 , the method may include S810 - S885 , and S810 - S885 are described in detail below.

[0487] It should be understood that the following S810-S850 is to obtain the data and power consumption of the UPF network element, and S855-S885 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0488] S810: The AF network element sends message 1 to the NWDAF network element / EECF network element.

[0489] The message 1 is used to request information for determining the power consumption of the target area.

[0490] Similar to S610, please refer to the description in S610 for details, which will not be repeated here.

[0491] S815: The NWDAF network element / EECF network element sends message 23 to the charging network element.

[0492] Message 23 requests to obtain power consumption related information for determining the target area.

[0493] For example, the message 23 may be an Nchf_ConvergedCharging_DataRequest Request message.

[0494] For example, the message 23 sent by the SMF network element to the billing network element may include: information about the area received in message 1.

[0495] Optionally, message 23 may also include: time information.

[0496] S820: The charging network element sends message 24 to the NWDAF network element / EECF network element.

[0497] The message 24 includes relevant information for determining the power consumption of the target area.

[0498] After receiving message 23 sent by the NWDAF network element / EECF network element, the billing network element queries the locally stored information to obtain relevant information that can be used to calculate power consumption, and returns the relevant information to the NWDAF network element / EECF network element. Specifically:

[0499] For example, if the message 23 includes the area information, the charging network element filters out the corresponding entry in the stored information based on the CGI, cellID, TAC, TAI and other information contained in the provided area information. For example, the corresponding entry is found based on the terminal device location information (UE Location Info) in Table 2;

[0500] For example, if message 23 includes time information, the billing network element can further filter based on the time information. The timing of filtering is not limited. For example, the filtering result can be obtained based on the regional information provided in message 23 first, and then the filtering result can be filtered again based on the time information; or the filtering result can be obtained based on the time information first, and then the filtering result can be filtered based on the regional information provided in message 23; or the filtering result can be obtained based on both the regional information and the time information provided in message 23. This solution does not limit this.

[0501] For example, the message 24 may be an Nchf_ConvergedCharging_DataRequest Response message.

[0502] For example, the message 24 may include one or more pieces of information in Table 1.

[0503] S825: The NWDAF network element / EECF network element sends message 2 to the NRF network element.

[0504] Among them, the message 2 is used to request the identifier of the SMF network element corresponding to the above-mentioned target area.

[0505] Similar to S615, please refer to the description in S615 for details, which will not be repeated here.

[0506] S830: The NRF network element sends message 3 to the NWDAF network element / EECF network element.

[0507] The message 3 includes identification information of the SMF corresponding to the target area.

[0508] Similar to S620, please refer to the description in S620 for details, which will not be repeated here.

[0509] S835: The NWDAF network element / EECF network element sends message 4 to the corresponding SMF network element according to the identification information of the SMF network element indicated in message 3.

[0510] The message 4 is used to request information for determining the power consumption of the target area.

[0511] Similar to S625, please refer to the description in S625 for details, which will not be repeated here.

[0512] In another possible implementation, the NWDAF network element / EECF network element includes in message 4 the information of all PDU sessions, or information of part of the PDU sessions, in the PDU session information (PDU Session Information) obtained from message 24. The information of part of the PDU sessions may refer to the information of the PDU sessions managed by the corresponding SMF.

[0513] S840: The SMF network element sends message 7 to the NWDAF network element / EECF network element.

[0514] The message 7 includes information for determining the power consumption of the target area.

[0515] Similar to S640, please refer to the description in S640 for details, which will not be repeated here.

[0516] In another possible implementation, the SMF network element obtains the UPF information corresponding to the PDU session based on the PDU session information contained in message 24, for example, it may include the identification information of the anchor UPF, the identification information of the intermediate UPF (intermediateUPF, I-UPF), etc.

[0517] It should be understood that S825-S840 are optional and are only used when the NWDAF network element / EECF network element cannot obtain the UPFID from the billing network element. This is because the CDR stored in the billing network element may not contain all UPF network elements (for example, I-UPF network elements, which are other UPF network elements in the PDU session that do not belong to the anchor UPF network element). Therefore, this information can only be obtained from the SMF network element).

[0518] S845: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0519] The message 8 is used to request the total amount of data transmitted by a given UPF network element and the power consumption value (total power consumption).

[0520] Similar to S645, please refer to the description in S645 for details, which will not be repeated here.

[0521] S850: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0522] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0523] Similar to S650, please refer to the description in S650 for details, which will not be repeated here.

[0524] S855: The NWDAF network element / EECF network element sends message 10 to the NRF network element.

[0525] Among them, message 10 is used to request the identification of the AMF network element corresponding to the above-mentioned target area.

[0526] Similar to S655, please refer to the description in S655 for details, which will not be repeated here.

[0527] S860: The NRF network element sends message 11 to the NWDAF network element / EECF network element.

[0528] Among them, the message 11 includes the identification information of the AMF corresponding to the above-mentioned target area.

[0529] Similar to S660, please refer to the description in S660 for details, which will not be repeated here.

[0530] S865: The NWDAF network element / EECF network element sends message 12 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 11.

[0531] The message 12 is used to request identification information of an access network device corresponding to a target area.

[0532] Similar to S665, please refer to the description in S665 for details, which will not be repeated here.

[0533] S870: The AMF network element sends message 13 to the NWDAF network element / EECF network element.

[0534] The message 13 includes identification information of the access network device corresponding to the area.

[0535] Similar to S670, please refer to the description in S670 for details, which will not be repeated here.

[0536] S875: The NWDAF network element / EECF network element sends message 14 to the OAM system.

[0537] The message 14 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0538] Similar to S675, please refer to the description in S675 for details, which will not be repeated here.

[0539] S880: The OAM system sends message 15 to the NWDAF network element / EECF network element.

[0540] The message 15 includes the total amount of data transmitted by a given access network device and a power consumption value (total power consumption).

[0541] Similar to S680, please refer to the description in S680 for details, which will not be repeated here.

[0542] S885: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target area based on the information obtained.

[0543] Similar to S685, please refer to the description in S685 for details, which will not be repeated here.

[0544] Below, in conjunction with Figures 8 to 10, taking the sixth network element as the NWDAF network element / EECF network element and the second network element as the SMF network element, and taking the determination of the power consumption of the target application as an example, a specific method of the communication method provided in the embodiment of the present application is described in detail. It should be understood that the examples of Figures 8 to 10 are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the application embodiments to the specific numerical values ​​or specific scenarios illustrated in Figures 8 to 10. Those skilled in the art can obviously make various equivalent modifications or changes based on the following examples given in Figures 8 to 10, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0545] FIG8 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG8 , the method may include S910 - S990 , and S910 - S990 are described in detail below.

[0546] It should be understood that the following S910-S955 is to obtain the data and power consumption of the UPF network element, and S960-S990 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0547] S910: The AF network element sends message 25 to the NWDAF network element / EECF network element.

[0548] The message 25 is used to request to obtain relevant information for determining the power consumption of the target application.

[0549] For example, the AF network element may send a message 25 to the NWDAF network element / EECF network element, where the message 25 is used to request information for determining the power consumption of the target application.

[0550] As an example, the message 25 may be a Nnwdaf_EventExposure_Subscribe Request message.

[0551] For example, the message 25 sent by the AF network element to the NWDAF network element / EECF network element may include: specific information for indicating the target application, which may include but is not limited to: address information corresponding to the target application, such as IP address, service data flow description, etc.

[0552] Optionally, the message 25 may further include at least one of the following information:

[0553] 1) Request granularity: based on the application's power consumption;

[0554] 2) AF Application Identifier, which can be a string or a string of numbers;

[0555] 3) Time information, such as time points and time spans. A time point can be, for example, two Coordinated Universal Time (UTC) values. A time span can have a start time of a time point and a corresponding duration. A time span can also include only the duration (meaning the start time is the current system time). Alternatively, a time span can include only a time point (meaning the start time is the current system time).

[0556] It should be understood that the above-mentioned time information is the time for determining the power consumption of the target application, for example, the start time and end time of determining the power consumption of the target application.

[0557] S915: The NWDAF network element / EECF network element sends message 26 to the BSF network element.

[0558] The message 26 is used to request the identifier of the PCF network element corresponding to the target application.

[0559] For example, the message 26 may be an Nbsf_Management_Discovery_Request message.

[0560] For example, the message 26 may include specific information indicating the target application.

[0561] Optionally, the message 26 may further include at least one of the following information:

[0562] 1) Request granularity: based on the application's power consumption;

[0563] 2) Time information.

[0564] It should be understood that the time information contained in message 26 is similar to the time information contained in message 25. For details, please refer to the description of the time information in the above message 25, which will not be repeated here.

[0565] S920: The BSF network element sends message 27 to the NWDAF network element / EECF network element.

[0566] The message 27 includes the identification information of the PCF corresponding to the target application.

[0567] For example, after receiving message 26 sent by the NWDAF network element / EECF network element, the BSF network element obtains the identification information of the PCF network element corresponding to the target application contained in message 26, and can send message 27 to the NWDAF network element / EECF network element, which includes the identification information of the PCF network element corresponding to the above-mentioned target area.

[0568] For example, the message 27 may be an Nbsf_Management_Discovery_Request Response message.

[0569] For example, the message 3 sent by the NRF network element to the NWDAF network element / EECF network element may include: identification information of the PCF network element (for example, PCFID, which may be an IP address or a fully qualified domain name (FQDN));

[0570] It should be noted that the identification information of the PCF network element returned in the above message 27 may be the identification information of one PCF network element, or may be a list of identification information of multiple PCF network elements.

[0571] S925: The NWDAF network element / EECF network element sends message 28 to the corresponding PCF network element.

[0572] The message 28 is used to request to obtain relevant information for determining the power consumption of the target application.

[0573] For example, after receiving message 27 sent by the BSF network element, the NWDAF network element / EECF network element may send message 28 to the corresponding PCF network element according to the identification information of the PCF network element indicated in message 27. The message 28 is used to request information for determining the power consumption of the target application.

[0574] For example, the message 28 may be an Npcf_EnergyEfficiency_PolicyAuthorization Request message.

[0575] For example, the message 28 sent by the above-mentioned NWDAF network element / EECF network element to the PCF network element may include but is not limited to the following information: application information, and the information of the area may be the information of the target area included in the message 25 received by the NWDAF network element / EECF network element in S910.

[0576] Optionally, message 28 may also include: time information.

[0577] It should be understood that the time information contained in message 28 is similar to the time information contained in message 25. For details, please refer to the description of the time information in the above message 25, which will not be repeated here.

[0578] S930: The PCF network element sends a message 29 to the corresponding SMF network element. The message 29 is used to request to obtain relevant information for determining the power consumption of the target application.

[0579] For example, after receiving message 28 sent by the NWDAF network element / EECF network element, the PCF network element can send message 29 to the corresponding SMF network element according to the identification information of the SMF network element indicated in message 28.

[0580] The message 29 is used to request to obtain relevant information for determining the power consumption of the target application.

[0581] For example, the message 29 may be an Nsmf_EnergyEfficiency_EnergyConsumption request message.

[0582] For example, the message 29 sent by the above-mentioned PCF network element to the SMF network element may include but is not limited to the following information: application information.

[0583] Optionally, message 29 may also include time information.

[0584] S935: The SMF network element sends message 30 to the billing network element.

[0585] The message 30 is used to request to obtain relevant information for determining the power consumption of the target application.

[0586] For example, after receiving the message 29 sent by the PCF network element, the SMF network element may send a message 30 to the charging network element, where the message 30 is used to request relevant information for calculating the power consumption of the target application.

[0587] For example, the message 30 may be an Nchf_ConvergedCharging_DataRequest Request message.

[0588] For example, the message 30 sent by the SMF network element to the billing network element may include: application information.

[0589] Optionally, the message 30 may further include, but is not limited to, one or more of the following information:

[0590] 1) The SMF network element obtains the identification information of the corresponding UPF network element (such as UPFID, which can be an IP address or FQDN) according to the received application information;

[0591] Exemplarily, the SMF network element can obtain the identification information of the UPF network element by querying the NRF network element, or obtain the identification information of the UPF network element corresponding to the service area of ​​the UPF network element whose service area overlaps with the target area among the service areas of multiple UPF network elements obtained when the SMF network element performs N4 interaction with the UPF network element, or the SMF network element can obtain the identification information of the UPF network element by querying the context information of the locally stored session. For example, the SMF network element obtains the identification information of the one or more user plane network elements based on the identification information of the user plane network element contained in the context information of each session it manages.

[0592] 2) The SMF obtains the session identifier (e.g., PDUSessionID) containing the UPF identification information based on the obtained UPF identification information;

[0593] 3) Time information.

[0594] S940: The billing network element sends message 31 to the SMF network element.

[0595] The message 31 includes relevant information for determining the power consumption of the target area.

[0596] In an embodiment of the present application, after receiving message 30 sent by the SMF network element, the billing network element can query the locally stored information, obtain relevant information for determining the power consumption of the target area, and send the relevant information for determining the power consumption of the target area to the SMF via message 31.

[0597] As an example, the billing network element obtains relevant information for determining the power consumption of the target area based on the message 30 sent by the SMF network element in combination with the stored information (such as the CDR information in Table 2). The specific acquisition process is illustrated below.

[0598] For example, if message 30 includes application information, the charging network element will filter out corresponding entries from the stored information based on the provided application information, for example, based on the UE Service Identifier or PDUAddress information in Table 2 to find the corresponding entry.

[0599] For another example, if message 30 includes a UPFID, the billing network element may first find an entry in the stored information that has the same UPFID based on the UPFID included in message 30 before filtering the stored information based on the application information included in message 30. This can avoid the excessive burden on the billing network element caused by filtering the stored information based solely on the application information in message 30.

[0600] For another example, if message 30 includes a PDU Session ID, the billing network element may first find an entry in the stored information that has the same PDU Session ID based on the PDU Session ID included in message 30 before filtering the stored information based on the application information included in message 30. This avoids the excessive burden caused by filtering the stored information based solely on the application information in message 30.

[0601] For another example, when the billing network element is checking, if the message 30 includes time information, the billing network element can further filter based on the time information. The timing of filtering can be unlimited. For example, the filtering result can be obtained based on the domain information provided in the message 30, or the UPFID provided in the message 30, or the SessionID provided in the message 30, and then the result is further filtered based on the time information; or the filtering is first performed based on the time information provided in the message 30 to obtain the filtering result, and then the filtering result is further filtered based on the area information provided in the message 30, or the UPFID provided in the message 30, or the SessionID provided in the message 30; or the filtering is performed based on the area information provided in the message 30, the UPFID, the SessionID and the time information to obtain the filtering result. This solution does not limit this.

[0602] For example, the message 31 may be an Nchf_ConvergedCharging_DataRequest Response message.

[0603] For example, the message 31 may include, but is not limited to, one or more of the information in Table 7:

[0604] Table 7

[0605] S945: The SMF network element sends message 32 to the NWDAF network element / EECF network element through the PCF network element.

[0606] The message 32 includes information for determining the power consumption of the target application.

[0607] For example, the message 32 may be an Nsmf_EnergyEfficiency_EnergyConsumption response message and an Npcf_EnergyEffciency_PolicyAuthorization response message.

[0608] For example, the message 32 may include one or more pieces of information in Table 7.

[0609] S950: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0610] The message 8 is used to request the total amount of data transmitted by a given UPF network element and the power consumption value (total power consumption).

[0611] Similar to S645, please refer to the description in S645 for details, which will not be repeated here.

[0612] S955: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0613] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0614] Similar to S650, please refer to the description in S650 for details, which will not be repeated here.

[0615] At this point, the NWDAF network element / EECF network element obtains the following information:

[0616] 1) UPF network element identification list;

[0617] 2) The total amount of data transmitted by the UPF network element;

[0618] 3) The data volume transmitted by the UPF network element for the target application (see total volume in Table 7);

[0619] 4) UPF network element power consumption value (EnergyConsumption).

[0620] S960: The NWDAF network element / EECF network element sends message 33 to the NRF network element.

[0621] Among them, message 33 is used to request the identifier of the AMF network element corresponding to the above-mentioned target application.

[0622] For example, the NWDAF network element / EECF network element generates area information (e.g., list of cell IDs, list of TAIs, etc.) based on the UE location information (e.g., UE Location Information) obtained in S945, and sends message 33 to the NRF network element, requesting the identifier of the AMF network element corresponding to the area information corresponding to the "UE location information". For example, the NWDAF network element / EECF network element combines the UE location information to obtain the area information.

[0623] For example, the above-mentioned message 33 may be a Nnrf_NFDiscovery_Request message, which includes but is not limited to: UE location information.

[0624] S965: The NRF network element sends message 34 to the NWDAF network element / EECF network element, where the message 34 includes the identification information of the AMF corresponding to the above-mentioned area information (determined according to the UE's location information).

[0625] For example, after receiving message 33 sent by the NWDAF network element / EECF network element, the NRF network element obtains the area information contained in message 33 (determined according to the UE's location information), and can send message 34 to the NWDAF network element / EECF network element. The message 34 includes the identification information of the AMF corresponding to the above-mentioned area information (determined according to the UE's location information).

[0626] For example, the message 33 may be an Nnrf_NFDiscovery_Request Response message.

[0627] For example, the message 33 sent by the above-mentioned NRF network element to the NWDAF network element / EECF network element may include: identification information of the AMF network element (for example, AMFID, which can be an IP address or a fully qualified domain name (FQDN)).

[0628] Optionally, message 33 may also include: area information corresponding to the AMF network element (for example, a list of TACs corresponding to the AMF network element), or the service area of ​​the AMF network element.

[0629] It is worth noting that the AMF identifier returned in message 33 may be one or a list containing identification information of multiple AMF network elements.

[0630] Optionally, this list containing identification information of multiple AMF network elements will also include area information corresponding to the multiple AMF network elements.

[0631] S970: The NWDAF network element / EECF network element sends message 34-1 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 33.

[0632] The message 34 - 1 is used to request identification information of an access network device corresponding to an area.

[0633] For example, after the NWDAF network element / EECF network element receives message 33 sent by the NRF network element, it can select the corresponding AMF network element according to the area corresponding to the UE's location information and the area covered by the service area corresponding to the AMF, and send message 34-1 to the corresponding AMF network element. The message 34-1 is used to request the identification information of the access network device corresponding to the area.

[0634] For example, the message 34 - 1 may be a Namf_EnergyEffciency Request message.

[0635] For example, the message 34-1 sent by the above-mentioned NWDAF network element / EECF network element to the AMF network element may include but is not limited to the following information: area information, which may be information about the entire area corresponding to the UE's location information; or, information about a partial area, for example, the information about the partial area refers to information about the area in the UE's location information that overlaps with the area information corresponding to the AMF network element.

[0636] S975: The AMF network element sends message 35 to the NWDAF network element / EECF network element.

[0637] The message 35 includes identification information of the access network device corresponding to the area.

[0638] For example, the message 35 may be a Namf_EnergyEffciency response message.

[0639] For example, the message 35 may include identification information of the access network device. For example, the message 35 may include: identification information of the access network device, for example, the identification information of the access network device is a Global RANID (global base station identification information), such as a Global gNB ID, a Global ng-eNB ID, etc., which may be a string of 22 to 32 bits; or the identification information of the access network device is a RANID (base station identification information), such as a gNB ID, an ng-eNB ID.

[0640] Optionally, the message 35 may also include information about the coverage area corresponding to the access network device, such as CellID, CGI, TAI, etc.

[0641] S980: The NWDAF network element / EECF network element sends message 36 to the OAM system.

[0642] The message 36 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0643] For example, the message 36 may be a RANInformationRequest message.

[0644] S985: The OAM system sends message 37 to the NWDAF network element / EECF network element.

[0645] The message 37 includes the total amount of data transmitted by the given access network device and the power consumption value (total power consumption).

[0646] For example, the message 37 may include but is not limited to the following information: an identification of the access network device, a total amount of data transmitted by each access network device, and a power consumption value (EnergyConsumption).

[0647] At this point, the NWDAF network element / EECF network element obtains the following information:

[0648] 1) List of identifications of access network devices;

[0649] 2) The total amount of data transmitted by access network equipment;

[0650] 3) The amount of data transmitted by the access network equipment for the target application (see Tables 8 and 9);

[0651] 4) Power consumption of access network equipment (EnergyConsumption).

[0652] Optionally, in some embodiments, assuming that the OAM system stores (or is capable of calculating) content similar to Table 3, only S980 to S985 may be executed in the above S960 to S985.

[0653] S990: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target application based on the information obtained.

[0654] It should be noted that, unlike the data volume corresponding to the calculation target area, it may not be possible to directly determine the data transmitted by a certain application on the access network device at the application granularity. As an example, one calculation method can be shown in the following Table 8-9.

[0655] Table 8

[0656] Table 9

[0657] For example, the NWDAF / EECF network element can correlate the data based on the information in the UElocationinfo returned by the SMF network element and the coveragearea returned by the AMF or OAM, thereby obtaining the actual data volume transmitted by a certain access network device for a certain target application.

[0658] In the above technical solution, NWDAF / EECF can obtain the energy consumption, data volume and other information of the network elements related to the target application according to the requested target application through the interaction between NWDAF / EECF network elements and SMF network elements, AMF network elements and OAM, and support the network to "count the total power consumption of a certain application". This will only cause minor changes to the existing process and does not require additional recording of other content.

[0659] FIG9 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG9 , the method may include S1010 - S1090 , and S1010 - S1090 are described in detail below.

[0660] It should be understood that the following S1010-S1055 is to obtain the data and power consumption of the UPF network element, and S1060-S1090 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0661] S1010: The AF network element sends message 25 to the NWDAF network element / EECF network element.

[0662] The message 25 is used to request to obtain relevant information for determining the power consumption of the target application.

[0663] Similar to S910, please refer to the description in S910 for details, which will not be repeated here.

[0664] S1015: The NWDAF network element / EECF network element sends a message 38 to a unified data repository (UDR).

[0665] The message 38 is used to request the UDR to store relevant information for determining the power consumption of the target application.

[0666] For example, the message 38 may include specific information of the target application. Optionally, the message 38 may also include the start time and end time of the request information.

[0667] S1020: The UDR sends message 39 to the PCF network element.

[0668] Message 39 is used to request to obtain relevant information for determining the power consumption of the target application.

[0669] In an embodiment of the present application, after the UDR receives message 38 sent by the NWDAF network element / EECF network element, it can send message 39 to the corresponding PCF network element based on the specific information of the target application indicated in message 38. The message 39 is used to request information for determining the energy consumption corresponding to the target application.

[0670] For example, the message 39 may be a Nudr_DM_Notify message.

[0671] For example, the message 39 may include: specific information for indicating an application.

[0672] Optionally, the message 39 may further include: the start time and end time of the requested information.

[0673] S1025: The PCF network element sends message 40 to the corresponding SMF network element.

[0674] The message 40 is used to request to obtain relevant information for determining the power consumption of the target application.

[0675] In an embodiment of the present application, the above-mentioned SMF is used to manage the PDU session corresponding to the application.

[0676] For example, the message 40 may be an Npcf_SMPolicyControl_Control_Update Notify message.

[0677] For example, the message 40 may include: specific information for indicating an application.

[0678] Optionally, the message 40 may further include: time information corresponding to the request information.

[0679] S1030: The SMF network element sends message 41 to the UPF network element.

[0680] Among them, message 41 is used to request the UPF network element to transmit the amount of data for the target application.

[0681] For example, the message 41 may be an N4 modification request message.

[0682] For example, the message 41 may include: specific information for indicating an application.

[0683] Optionally, the message 41 may further include one or more of the following:

[0684] 1) Indication of the amount of data sent;

[0685] 3) The sending cycle of the amount of data sent.

[0686] It should be understood that if the UPF network element continuously sends the transmitted data volume without the need for the SMF network element to actively subscribe, then S1030 is optional.

[0687] S1035: The UPF network element sends message 42 to the SMF network element.

[0688] Among them, message 42 includes the amount of data transmitted by the UPF network element for the target application.

[0689] For example, the message 42 may be an N4 notification message.

[0690] For example, message 42 may include: the amount of data transmitted by the UPF network element.

[0691] Optionally, the message 42 may also include time information.

[0692] S1040: The SMF network element summarizes and updates the local record information based on the information sent by the UPF network element.

[0693] Similar to S760, please refer to the description in S760 for details, which will not be repeated here.

[0694] S1045: The SMF network element sends message 43 to the NWDAF network element / EECF network element.

[0695] For example, the message 43 may be an Nsmf_EnergyEfficiency_EnergyConsumption response message.

[0696] For example, the message 43 may include at least one of the information in the following Tables 4-6.

[0697] S1050: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0698] The message 8 is used to request the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0699] Similar to S950, please refer to the description in S950 for details, which will not be repeated here.

[0700] S1055: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0701] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0702] Similar to S955, please refer to the description in S955 for details, which will not be repeated here.

[0703] At this point, the NWDAF network element / EECF network element obtains the following information:

[0704] 1) UPF network element identification list;

[0705] 2) The total amount of data transmitted by the UPF network element;

[0706] 3) The data volume transmitted by the UPF network element for the target application (see total volume in Table 7);

[0707] 4) UPF network element power consumption value (EnergyConsumption).

[0708] S1060: The NWDAF network element / EECF network element sends message 33 to the NRF network element.

[0709] Among them, message 33 is used to request the identifier of the AMF network element corresponding to the above-mentioned target application.

[0710] Similar to S960, please refer to the description in S960 for details, which will not be repeated here.

[0711] S1065: The NRF network element sends message 34 to the NWDAF network element / EECF network element.

[0712] Among them, the message 34 includes the identification information of the AMF corresponding to the above-mentioned area information (determined according to the UE's location information).

[0713] Similar to S965, please refer to the description in S965 for details, which will not be repeated here.

[0714] S1070: The NWDAF network element / EECF network element sends message 34-1 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 33.

[0715] The message 34 - 1 is used to request identification information of an access network device corresponding to an area.

[0716] Similar to S970, please refer to the description in S970 for details, which will not be repeated here.

[0717] S1075: The AMF network element sends message 35 to the NWDAF network element / EECF network element.

[0718] The message 35 includes identification information of the access network device corresponding to the area.

[0719] Similar to S975, please refer to the description in S975 for details, which will not be repeated here.

[0720] S1080: The NWDAF network element / EECF network element sends message 36 to the OAM system.

[0721] The message 36 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0722] Similar to S980, please refer to the description in S980 for details, which will not be repeated here.

[0723] S1085: The OAM system sends message 37 to the NWDAF network element / EECF network element.

[0724] The message 37 includes the total amount of data transmitted by the given access network device and the power consumption value (total power consumption).

[0725] Similar to S985, please refer to the description in S985 for details, which will not be repeated here.

[0726] At this point, the NWDAF network element / EECF network element obtains the following information:

[0727] 1) List of identifications of access network devices;

[0728] 2) The total amount of data transmitted by access network equipment;

[0729] 3) The amount of data transmitted by the access network equipment for the target application (see Tables 8 and 9);

[0730] 4) Power consumption of access network equipment (EnergyConsumption).

[0731] S1090: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target application based on the information obtained.

[0732] Similar to S990, please refer to the description of S990 for details, which will not be repeated here.

[0733] In the above technical solution, NWDAF / EECF can obtain information such as energy consumption and data volume of network elements related to the target application based on the requested target application through the interaction between NWDAF / EECF network elements and SMF, AMF and OAM. Without relying on billing information, it supports the network to "count the total power consumption within a certain application". This will only cause minor changes to the existing process and does not require additional recording of other content.

[0734] FIG10 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG10 , the method may include S1110 - 1195 , and S1110 - 1195 are described in detail below.

[0735] It should be understood that the following S1110-1160 is to obtain the data and power consumption of the UPF network element, and S1165-1195 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0736] S1110: The AF network element sends message 25 to the NWDAF network element / EECF network element.

[0737] The message 25 is used to request to obtain relevant information for determining the power consumption of the target application.

[0738] Corresponding to S910, please refer to the description of S910 for details, which will not be repeated here.

[0739] S1115: The NWDAF network element / EECF network element sends message 44 to the charging network element.

[0740] Message 44 requests to obtain relevant information for determining the power consumption of the target application.

[0741] For example, after receiving the message 25 sent by the AF network element, the NWDAF network element / EECF network element may send a message 44 to the charging network element.

[0742] The message 44 is used to request to obtain relevant information for calculating the power consumption of the target application.

[0743] For example, the message 44 may be an Nchf_ConvergedCharging_DataRequest Request message.

[0744] For example, the message 44 sent by the NWDAF network element / EECF network element to the charging network element may include but is not limited to application information.

[0745] Optionally, the message 44 may further include: time information corresponding to the request information.

[0746] S1120: The charging network element sends message 45 to the NWDAF network element / EECF network element.

[0747] The message 45 includes relevant information for determining the power consumption of the target application.

[0748] As an example, after receiving the message 44 sent by the NWDAF network element / EECF network element, the billing network element queries the locally stored information, obtains relevant information that can be used to determine the power consumption of the target application, and returns the relevant information to the NWDAF network element / EECF network element. Specifically:

[0749] For example, if message 44 includes application information, the charging network element filters out corresponding entries from the stored information based on the provided application information, for example, based on the UE Service Identifier or PDUAddress information in Table 2 to find the corresponding entry.

[0750] For example, if message 44 includes time information, the billing network element can further filter based on the time information. The timing of filtering is not limited. For example, the stored information can be filtered based on the application information included in message 44 to obtain the filtering result, and then the filtering result is filtered again based on the time information; or the stored information can be filtered based on the time information included in message 44 to obtain the filtering result, and then the filtering result is filtered again based on the application information included in message 44; or the stored information can be filtered based on both the time information and the application information included in message 44 to obtain the filtering result. This solution does not impose any restrictions.

[0751] For example, the message 45 may be an Nchf_ConvergedCharging_DataRequest Response message.

[0752] For example, the message 45 may include but is not limited to one or more items of information in Table 7.

[0753] S1125: The NWDAF network element / EECF network element sends message 26 to the BSF network element.

[0754] The message 26 is used to request the identifier of the PCF network element corresponding to the target application.

[0755] Similar to S915, please refer to the description in S915 for details, which will not be repeated here.

[0756] S1130: The BSF network element sends message 27 to the NWDAF network element / EECF network element.

[0757] The message 27 includes the identification information of the PCF corresponding to the target application.

[0758] Similar to S920, please refer to the description in S920 for details, which will not be repeated here.

[0759] S1135: The NWDAF network element / EECF network element sends message 28 to the corresponding PCF network element.

[0760] The message 28 is used to request to obtain relevant information for determining the power consumption of the target application.

[0761] Similar to S925, please refer to the description in S925 for details, which will not be repeated here.

[0762] It is worth noting that S1125 to 1135 can be replaced by S1137 to 1139.

[0763] S1137: The NWDAF network element / EECF network element sends message 38 to the UDR network element.

[0764] The message 38 is used to request to determine relevant information for calculating the power consumption of the target application based on information stored in the UDR.

[0765] For example, the message 38 may include specific information indicating the target application.

[0766] Optionally, the message 38 may further include a start time and an end time of the requested information.

[0767] S1137 is similar to S1015. For details, please refer to the description in S1015 and will not be repeated here.

[0768] S1139: The UDR network element sends message 39 to the PCF network element.

[0769] Message 39 is used to request to obtain relevant information for determining the power consumption of the target application.

[0770] For example, the message 39 may include specific information indicating the target application and, optionally, may also include the start time and end time of the request information.

[0771] S1139 is similar to S1020. For details, please refer to the description in S1020, which will not be repeated here.

[0772] S1140: The PCF network element sends message 29 to the corresponding SMF network element.

[0773] The message 29 is used to request to obtain relevant information for determining the power consumption of the target application.

[0774] Similar to S930, please refer to the description in S930 for details, which will not be repeated here.

[0775] S1145: The SMF network element sends message 30 to the billing network element.

[0776] The message 30 is used to request to obtain relevant information for determining the power consumption of the target application.

[0777] Similar to S935, please refer to the description in S935 for details, which will not be repeated here.

[0778] S1150: The billing network element sends message 31 to the SMF network element.

[0779] The message 31 includes relevant information for determining the power consumption of the target application.

[0780] Similar to S940, please refer to the description in S940 for details, which will not be repeated here.

[0781] S1155: The SMF network element sends message 32 to the NWDAF network element / EECF network element through the PCF network element.

[0782] The message 32 includes relevant information for determining the power consumption of the target application.

[0783] Similar to S945, please refer to the description in S945 for details, which will not be repeated here.

[0784] S1158: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0785] The message 8 is used to request the total amount of data transmitted by a given UPF network element and the power consumption value (total power consumption).

[0786] Similar to S1150, please refer to the description of S950 for details, which will not be repeated here.

[0787] S1160: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0788] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0789] Similar to S955, please refer to the description in S955 for details, which will not be repeated here.

[0790] S1165: The NWDAF network element / EECF network element sends message 33 to the NRF network element.

[0791] Among them, message 33 is used to request the identifier of the AMF network element corresponding to the above-mentioned target application.

[0792] Similar to S960, please refer to the description in S960 for details, which will not be repeated here.

[0793] S1170: The NRF network element sends message 34 to the NWDAF network element / EECF network element.

[0794] Among them, the message 34 includes the identification information of the AMF corresponding to the above-mentioned area information (determined according to the UE's location information).

[0795] Similar to S965, please refer to the description in S965 for details, which will not be repeated here.

[0796] S1175: The NWDAF network element / EECF network element sends message 34-1 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 33.

[0797] The message 34 - 1 is used to request identification information of an access network device corresponding to an area.

[0798] Similar to S970, please refer to the description in S970 for details, which will not be repeated here.

[0799] S1180: The AMF network element sends message 35 to the NWDAF network element / EECF network element.

[0800] The message 35 includes identification information of the access network device corresponding to the area.

[0801] Similar to the S9750, please refer to the description of the S975 for details.

[0802] S1185: The NWDAF network element / EECF network element sends message 36 to the OAM system.

[0803] The message 36 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0804] Similar to S980, please refer to the description in S980 for details, which will not be repeated here.

[0805] S1190: The OAM system sends message 37 to the NWDAF network element / EECF network element.

[0806] The message 37 includes the total amount of data transmitted by the given access network device and the power consumption value (total power consumption).

[0807] Similar to S985, please refer to the description in S985 for details, which will not be repeated here.

[0808] S1195: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target application based on the information obtained.

[0809] Similar to S990, please refer to the description of S990 for details, which will not be repeated here.

[0810] In the above technical solution, NWDAF / EECF can directly obtain information such as data volume from the billing network element according to the target application of the request, so that the network can "count the total power consumption of a certain application", making the implementation simpler.

[0811] FIG11 is a schematic flowchart of another communication method provided in an embodiment of the present application. As shown in FIG11 , the method may include S1210 - S1299 , and S1210 - S1299 are described in detail below.

[0812] It should be understood that the following S1210-S1270 is to obtain the data and power consumption of the UPF network element, and S1270-S1299 is to obtain the data and power consumption of the access network device (access network device). The order of these two parts is not limited in this application.

[0813] S1210: The AF network element sends message 1 to the NWDAF network element / EECF network element.

[0814] The message 1 is used to request information for determining the power consumption of the target area.

[0815] Similar to S610, please refer to the description in S610 for details, which will not be repeated here.

[0816] S1215: The NWDAF network element / EECF network element sends message 2 to the NRF network element.

[0817] Among them, message 2 is used to request the identification of the AMF network element corresponding to the above-mentioned target area.

[0818] For example, the message 2 may be a Nnrf_NFDiscovery_Request message, which includes area information.

[0819] S1220: The NRF network element sends message 3 to the NWDAF network element / EECF network element.

[0820] Among them, the message 3 includes the identification information of the AMF corresponding to the above-mentioned target area.

[0821] For example, the above message 3 may be a Nnrf_NFDiscovery_Request Response message.

[0822] For example, the message 3 sent by the above-mentioned NRF network element to the NWDAF network element / EECF network element may include: identification information of the AMF network element (for example, AMFID, which can be an IP address or a fully qualified domain name (FQDN)).

[0823] Optionally, message 3 may also include: area information corresponding to the SMF network element, such as the TAC list (list of TAC) corresponding to the SMF network element, or the service area of ​​the SMF network element.

[0824] It should be noted that the identification information of the AMF network element returned in the above message 3 may be the identification information of a single AMF network element, or it may be a list containing the identification information of multiple AMF network elements.

[0825] Optionally, the list containing identification information of multiple AMF network elements may also include area information corresponding to the multiple AMF network elements.

[0826] S1225: The NWDAF network element / EECF network element sends message 46 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 3.

[0827] The message 46 is used to request identification information of a terminal device (eg, UE) corresponding to the target area.

[0828] It should be understood that message 46 may correspond to the seventh request message above.

[0829] For example, the message 46 may be a Namf_EnergyEfficiency_EnergyConsumption request message.

[0830] For example, the message 46 sent by the above-mentioned NWDAF network element / EECF network element to the AMF network element may include: area information, which may be the information of the target area included in the message 1 received by the NWDAF network element / EECF network element in S1210, or it may be information of a partial area. For example, the information of the partial area refers to the area where the target area in the message 1 overlaps with the service area of ​​the SMF network element that receives the message 46.

[0831] Optionally, the message 46 may further include: time information corresponding to the request information.

[0832] S1230: The AMF network element sends message 17 to the access network device according to S1225.

[0833] Among them, message 17 is used to request the location information of the terminal device (for example, UE), or the relationship between the terminal device and the area received in message 46.

[0834] For example, the message 17 may be a Location report control message.

[0835] For example, the above message 17 can be a message sent by the AMF network element to the access network devices corresponding to each terminal device it manages.

[0836] For example, the message 17 may include one or more of the following information:

[0837] 1) The area information received in S1225;

[0838] 2) Indication information of UE location.

[0839] For example, if message 17 sent in S1230 contains area information, then the message 17 sent by the AMF network element to the access network device where the UE currently resides can be a Locationreportcontrol message, which contains the area information received in S1230.

[0840] For example, if the message 17 sent in S1230 contains the indication information of the UE location, then the message 17 sent by the AMF network element to the access network device where the UE currently resides can be a Location report control message, which contains the indication information of the UE's current location.

[0841] S1240: The access network device sends message 18 to the AMF network element.

[0842] Message 18 includes the current location of the UE, or the correspondence between the UE and the current area.

[0843] In an embodiment of the present application, when the access network device receives a request message 17 from the AMF network element, if the message 17 sent in S1230 contains area information, the access network device will detect the relationship between the UE's current location and the area information. If the current UE enters this area or leaves this area, the access network device sends a message 18 to the AMF network element. Message 18 includes the UE's current location, or the correspondence between the UE and the current area.

[0844] For example, message 18 may be a Location report message.

[0845] For example, when the RAN receives message 17, it may immediately send a Location report message.

[0846] For example, message 18 may include one or more of the following information:

[0847] 1) The correspondence between the UE and the current area, for example, "UE is in the area", "UE is not in the area";

[0848] 2) The current location of the UE.

[0849] S1245: The AMF network element sends message 47 to the NWDAF network element / EECF network element based on message 18.

[0850] Message 47 includes identification information of the terminal device (eg, UE) corresponding to the target area.

[0851] It should be understood that message 18 may correspond to the seventh response message above.

[0852] For example, AMF obtains the identification information of the terminal corresponding to the target area, and can determine whether the UE is in the target area (the corresponding area in S1225) based on the current information after the AMF network element receives message 18 from the access network device. For example, when message 18 contains the correspondence between the UE and the current area, AMF can record the identification of the terminal devices (i.e., UEID) returned by the access network device to the UE in the area. When message 18 contains the current location of the UE, AMF can record the identification of the terminal devices (i.e., UEID) whose current locations belong to the target area based on the current location of the UE and its relationship with the target area.

[0853] For example, the message 47 may be a Namf_EnergyEfficiency_EnergyConsumption Response message.

[0854] For example, message 47 may include one or more of the following information:

[0855] 1) Identification information of the terminal device, such as SUPI, GPSI, GUTI, etc.; it is worth noting that the identification information of the terminal device here can correspond to one terminal device or multiple terminal devices (such as UEIDlist);

[0856] 2) AMF identification information, such as FQDN, IP address, etc.

[0857] 3) Location information of the terminal device, for example, the “correspondence between the UE and the current area” contained in message X3, for example, “UE is in the area”, “UE is not in the area”, or the current location of the UE.

[0858] S1255: The NWDAF network element / EECF network element sends message 48 to the UDM network element.

[0859] Among them, message 48 is used to request information of SMF network elements.

[0860] It should be understood that message 48 may correspond to the eighth request message above.

[0861] For example, the NWDAF network element / EECF network element can send message 48 to each terminal device corresponding to the message 47, such as UEID, and the message 48 is used to request the information of the corresponding SMF network element.

[0862] For example, the NWDAF network element / EECF network element can include multiple terminal devices corresponding to message 47 (such as UEIDlist) in message 48, and message 48 is used to request information of the corresponding SMF network element (such as SMFlist).

[0863] For example, the message 48 may be a Nudm_UECM_Get message.

[0864] For example, the message 48 may include identification information of the terminal device, such as SUPI, GPSI, GUTI, etc.

[0865] It is worth noting that the identification information of the terminal device here can be the identification information of one terminal device or the identification information of multiple terminal devices, for example, a terminal device identification list (UEIDlist).

[0866] S1258: The UDM network element sends message 49 to the NWDAF network element / EECF network element.

[0867] Among them, message 49 includes the identification information of the SMF network element.

[0868] It should be understood that message 49 may correspond to the eighth response message above.

[0869] For example, the message 49 may be a Nudm_UECM_Get Response message.

[0870] For example, message 49 may include identification information of the SMF network element (such as FQDN, IP address, etc.), and the identification information of the SMF network element may be one or more.

[0871] S1260: The NWDAF network element / EECF network element sends a message 50 to the corresponding SMF network element according to the message 49 sent by the UDM network element.

[0872] For example, the NWDAF network element / EECF network element sends message 50 to the corresponding SMF network element based on the identification information of the SMF network element contained in message 49.

[0873] For example, the message 50 may be an Nsmf_EventExposure Subscription message.

[0874] For example, the message 50 may include one or more of the following information:

[0875] 1) Address information for receiving notification messages, such as IP address information, FQDN, etc.;

[0876] 2) Indication of the amount of open data transmission.

[0877] For example, after receiving message 50, the SMF network element can send a response message to the NWDAF network element / EECF network element, and the response message includes the current location information of the UE obtained by the SMF network element.

[0878] S1265: After receiving message 50, the SMF network element sends message 51 to the UPF network element.

[0879] For example, the SMF may send message 51 to each UPF network element in the PDU session based on the context information of the session stored locally.

[0880] For example, the message 51 may be a Nupf_event exposure subscribe request message.

[0881] For example, message 51 may include one or more of the following information:

[0882] 1) Address information for receiving notification messages, such as IP address information, FQDN, etc.;

[0883] 2) Indication of the amount of open data transmission.

[0884] S1266: After receiving message 51, the UPF network element sends message 52 to the NWDAF network element / EECF network element.

[0885] For example, the message 52 may be a Nupf_EventExposure_Notify message.

[0886] For example, the target address to which message 52 is sent may be the address information for receiving the notification message contained in message 51 .

[0887] For example, the message 52 may include one or more of the following information:

[0888] 1) PDU session identification information, such as PDUSessionID, PFCP (Packet Forwarding Control Protocol) SessionID;

[0889] 2) Data transmission volume, such as Byte, bit, KB, Kb, Mb, MB, etc.;

[0890] 3) Identification information of SMF network elements, such as SMFID, IP address information, FQDN, etc.;

[0891] 4) Identification information of the UPF network element, such as UPFID, IP address information, FQDN, etc.

[0892] It is worth noting that after S1266, the NWDAF network element / EECF network element can obtain the data volume information of the UPF network element contained in each PDU session of the terminal device located in the target area. Based on this, the NWDAF network element / EECF network element can obtain the data transmission volume of the UPF network element within the target area.

[0893] S1268: The NWDAF network element / EECF network element sends message 8 to the OAM system.

[0894] The message 8 is used to request the total amount of data transmitted by a given UPF network element and the power consumption value (total power consumption).

[0895] Similar to S645, please refer to the description in S645 for details, which will not be repeated here.

[0896] S1270: The OAM system sends message 9 to the NWDAF network element / EECF network element.

[0897] The message 9 includes the total amount of data transmitted by a given UPF and the power consumption value (total power consumption).

[0898] Similar to S650, please refer to the description in S650 for details, which will not be repeated here.

[0899] S1275: The NWDAF network element / EECF network element sends message 10 to the NRF network element.

[0900] Among them, message 10 is used to request the identification of the AMF network element corresponding to the above-mentioned target area.

[0901] Similar to S655, please refer to the description in S655 for details, which will not be repeated here.

[0902] S1280: The NRF network element sends message 11 to the NWDAF network element / EECF network element.

[0903] Among them, the message 11 includes the identification information of the AMF corresponding to the above-mentioned target area.

[0904] Similar to S660, please refer to the description in S660 for details, which will not be repeated here.

[0905] S1285: The NWDAF network element / EECF network element sends message 12 to the corresponding AMF network element according to the identification information of the AMF network element indicated in message 11.

[0906] The message 12 is used to request identification information of an access network device corresponding to a target area.

[0907] Similar to S665, please refer to the description in S665 for details, which will not be repeated here.

[0908] S1290: The AMF network element sends message 13 to the NWDAF network element / EECF network element.

[0909] The message 13 includes identification information of the access network device corresponding to the area.

[0910] Similar to S670, please refer to the description in S670 for details, which will not be repeated here.

[0911] S1295: The NWDAF network element / EECF network element sends message 14 to the OAM system.

[0912] The message 14 is used to request the total amount of data transmitted by a given access network device and the power consumption value (total power consumption).

[0913] Similar to S675, please refer to the description in S675 for details, which will not be repeated here.

[0914] S1298: The OAM system sends message 15 to the NWDAF network element / EECF network element.

[0915] The message 15 includes the total amount of data transmitted by a given access network device and a power consumption value (total power consumption).

[0916] Similar to S680, please refer to the description in S680 for details, which will not be repeated here.

[0917] S1299: The NWDAF network element / EECF network element calculates the power consumption corresponding to the target area based on the information obtained.

[0918] Similar to S685, please refer to the description in S685 for details, which will not be repeated here.

[0919] In the above technical solution, NWDAF / EECF can obtain information such as energy consumption and data volume of network elements related to the target area of ​​the request through the interaction between NWDAF / EECF network elements and SMF network elements, AMF network elements and OAM. Without relying on billing information, it supports the network to "count the total power consumption in a certain area". This will only cause minor changes to the existing process and does not require additional recording of other content.

[0920] It should be noted that all message names in Figures 3 to 11 are only examples, and the embodiments of the present application do not specifically limit the names of the messages.

[0921] Taking the sixth network element as an NWDAF network element or an EECF network element as an example, in the above method, the NWDAF network element / EECF network element can discover the network elements in the target area and obtain the corresponding transmitted data volume (first data volume) according to the following process.

[0922] As an example, the following lists different implementation methods of how to discover SMF network elements and obtain the amount of data sent to the target area (the fourth data amount).

[0923] The first implementation method:

[0924] 1. The NWDAF network element / EECF network element receives target area information and, optionally, time information from the AF network element.

[0925] This corresponds to S610 above. Please refer to the description in S610 for details, which will not be repeated here.

[0926] 2. The NWDAF network element / EECF network element obtains the SMF network element serving the target area from the AF network element.

[0927] For example, the SMF network element serving the target area is obtained through the network element function description information (network element function profile, NFprofile) of the SMF network element stored in the NRF network element. This corresponds to S615-S620 above. For details, please refer to the description in S615-S620, which will not be repeated here.

[0928] Afterwards, the NWDAF network element / EECF network element sends the corresponding area information and optional time information to the selected SMF network element. This corresponds to S625 above. Please refer to the description of S625 for details, which will not be repeated here.

[0929] 3. For each PDU session managed by the SMF network element, when the UE (requesting to establish a PDU session) is located in the target area, the SMF network element collects the uplink / downlink data volume (the fourth data volume) of the PDU session.

[0930] Implementation method 1: When the SMF network element knows that the UE is located in the target area, for example, the SMF network element obtains the UE's location information from the AMF network element, or the SMF network element obtains the correspondence between the UE and the target area from the AMF network element, the SMF network element requests the UPF network element to provide the data volume transmitted by the PDU session.

[0931] The above implementation method 1 corresponds to S730-S745 above. For details, please refer to the description in S730-S745, which will not be repeated here.

[0932] Implementation method 2: The UPF network element reports the data volume to the SMF.

[0933] The above implementation method 2 corresponds to S758 above. Please refer to the description in S758 for details, which will not be repeated here.

[0934] In implementation method 3, the SMF network element will update the data volume of the UE's PDU session and the location information related to the UE in its storage. At the same time, the SMF network element will also record the identification information of the UPF network element related to the PDU session.

[0935] The above implementation method 3 corresponds to S760 above. Please refer to the description in S760 for details, which will not be repeated here.

[0936] 4. The SMF network element provides its stored information to the NWDAF network element / EECF network element. Optionally, the SMF network element can provide its stored information to the NWDAF network element / EECF network element after the time expires. This corresponds to S640 above. Please refer to the description in S640 for details and will not be repeated here.

[0937] The second implementation method:

[0938] The NWDAF network element / EECF network element can call the service provided by the CHF network element to query the CDR information to obtain the same information. To this end, the NWDAF network element / EECF network element provides the target area information and time information to the CHF network element. In response, the CHF network element provides the (required) data volume, the identifier of the UPF network element, and the UE location information to the NWDAF network element / EECF network element. This corresponds to S815-S820 above. Please refer to the description in S815-S820 for details and will not be repeated here.

[0939] As another example, the following lists implementation methods for discovering RAN network elements located in a target area.

[0940] 1. The NWDAF network element / EECF network element searches for an AMF network element that can serve the target area. For example, it searches for an AMF network element that can serve the target area through the NFProfile of the AMF network element stored at the NRF network element. Afterwards, the NWDAF network element / EECF network element sends the corresponding area information to the selected AMF network element. This corresponds to S655-S665 above. For details, please refer to the description in S655-S665, which will not be repeated here.

[0941] 2. In response, the AMF network element returns the identification information of the RAN network element that can serve the target area. For example, the identification information of the RAN network element that can serve the target area is obtained by using the TAI list obtained when the NG connection is established and the TAI list associated with the RAN network element. This corresponds to S670 above. Please refer to the description of S670 for details and will not be repeated here.

[0942] As an example, regarding how the NWDAF network element / EECF network element discovers the network element serving a certain application and the corresponding transmitted data volume (first data volume), there is the following process:

[0943] As an example, the following lists how to discover the SMF network element and how to obtain the amount of data sent to a certain application (the fourth data amount).

[0944] 1. The NWDAF network element / EECF network element receives application information (in other words, filter information—such as IP address information, FQDN, etc., or application ID) and, optionally, time information from the AF network element. This corresponds to S910 above. Please refer to the description of S910 for details and will not be repeated here.

[0945] 2. The NWDAF / EECF notifies the involved PCF elements (these PCF elements control the policy for the PDU session that transmits application data) through the BSF or UDR elements. The notification information includes application information and possible timing information. This corresponds to S915-S925 or S1015-S1020 above. For details, please refer to the description in S915-S925 or S1015-S1020. It will not be repeated here.

[0946] 3. The PCF network element notifies the SMF network element. This corresponds to S930 or S1025 above. For details, please refer to the description in S930 or S1025, which will not be repeated here.

[0947] 4. The SMF network element includes application information in the N4 message and requests the UPF network element to provide the data volume corresponding to the transmitted application data. This corresponds to S1030 above. Please refer to the description of S1030 for details and will not be repeated here.

[0948] For example, the UPF reports the amount of data transmitted for the application to the SMF, which corresponds to S1035 above. For details, please refer to the description in S1035, which will not be repeated here.

[0949] For another example, the SMF network element will update the data volume of the UE's PDU session and the location information related to the UE in its storage. At the same time, the SMF network element will also record the identification information of the UPF network element related to the PDU session. This corresponds to S1040 above. Please refer to the description in S1040 for details, which will not be repeated here.

[0950] 5. The SMF network element provides its stored information to the NWDAF / EECF network element directly or through the PCF network element. Optionally, the SMF can provide its stored information to the NWDAF / EECF network element after the time expires. This corresponds to S1045 or S945 above. Please refer to the description of S1045 or S945 for details and will not be repeated here.

[0951] As another example, the following lists implementation methods for discovering RAN network elements serving a certain application.

[0952] 1. The NWDAF network element / EECF network element will search for the AMF network element that can serve the area based on the TAI area in the user location information returned from the SMF network element. For example, the NFProfile of the AMF network element is used to find the AMF network element that can serve the target area. After that, the NWDAF network element / EECF network element sends the corresponding application information to the selected AMF network element. This corresponds to S960-S970 above. For details, please refer to the description in S960-S970, which will not be repeated here.

[0953] 2. In response, the AMF network element returns the identification information of the RAN network element that can serve the area provided by the NWDAF network element / EECF network element. For example, the identification information is obtained by the TAI list obtained when the NG connection is established and provided by the RAN network element (returned). This corresponds to S975 above. Please refer to the description in S975 for details and will not be repeated here.

[0954] The above describes in detail the method provided by the embodiment of the present application in conjunction with Figures 1 to 11. The following describes in detail the embodiment of the device of the present application in conjunction with Figures 12 to 14. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0955] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that each network element, such as a transmitting end device or a receiving end device, includes a hardware structure and / or software module corresponding to the execution of each function in order to implement the above functions. Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0956] In the embodiment of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0957] FIG12 is a schematic structural diagram of a communication device 1300 provided in an embodiment of the present application.

[0958] The communication device 1300 includes a transceiver module 1310 and a processing module 1320 , wherein the transceiver module 1310 can be used to implement corresponding communication functions, and the processing module 1320 can be used to perform data processing.

[0959] Optionally, the processing module 1320 may be a processor (may include one or more), a processing circuit with processor functions, etc., and may be used to execute other steps except sending and receiving in the above method embodiment.

[0960] Optionally, the apparatus 1300 further includes a storage unit, which may be a memory, an internal storage unit (e.g., a register, a cache, etc.), an external storage unit (e.g., a read-only memory, a random access memory, etc.), etc. The storage unit is used to store instructions, and the processing module 1320 executes the instructions stored in the storage unit to cause the communication apparatus to perform the above method.

[0961] In one example, the processing module 1320 is used to obtain the first data volume of the first network element, for example, obtaining the first data volume of the first network element through the transceiver module 1310, the first data volume being the data volume of the first data transmitted by the first network element, the first data being the data of the target area or the data of the target application; the processing module 1320 is also used to obtain the total power consumption and the second data volume of the first network element, for example, obtaining the total power consumption and the second data volume of the first network element through the transceiver module 1310, the second data volume being the total amount of data transmitted by the first network element; the processing module 1320 is also used to determine the first power consumption based on the total power consumption of the first network element, the first data volume and the second data volume, the first power consumption being the power consumption of the first network element for transmitting the first data.

[0962] Optionally, the data of the target area includes: data of terminal devices located in the target area.

[0963] Optionally, the data of the target area includes: data of a cell corresponding to the target area.

[0964] Optionally, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0965] Optionally, the transceiver module 1310 is further used to send a first request message to the second network element, where the first request message includes information indicating the target area or the target application; the transceiver module 1310 is further used to receive the first data volume from the second network element.

[0966] Optionally, the first data is data of the target area, the second network element is a session management network element, and the service area of ​​the second network element includes the target area; or, the first data is data of the target application, the second network element is a policy control network element, and the second network element provides policy control for the session used to transmit the data of the target application.

[0967] Optionally, the transceiver module 1310 is further configured to receive identification information of the one or more user plane network elements from the second network element.

[0968] Optionally, the transceiver module 1310 is also used to receive identification information of one or more sessions from the second network element, and the data of the one or more sessions includes the first data; the processing module 1320 is also used to obtain identification information of the one or more user-plane network elements based on the identification information of the one or more sessions, and the one or more user-plane network elements are used to transmit data of at least one of the one or more sessions.

[0969] Optionally, the transceiver module 1310 is also used to: send a second request message, the second request message including identification information of the one or more user plane network elements; the transceiver module 1310 also receives the total power consumption of each user plane network element in the one or more user plane network elements and the total amount of data transmitted by each user plane network element.

[0970] Optionally, the first network element includes one or more access network devices, and the transceiver module 1310 is also used to send a third request message to the access and mobility management network element, where the third request message is used to request that the service area include identification information of the access network device of the first area, wherein the first area is the target area, or the first area is the area where the terminal device using the target application is located; the transceiver module 1310 is also used to receive identification information of the one or more access network devices from the access and mobility management network element.

[0971] Optionally, the transceiver module 1310 is further configured to receive area information covered by the one or more access network devices from the access and mobility management network element.

[0972] In another example, the transceiver module 1310 is used to receive a first request message, which includes information for indicating a target area or a target application; the processing module 1320 is used to obtain a first data volume of a first network element, and the transceiver module 1310 is used to send a first data volume of the first network element, which is a data volume of first data transmitted by the first network element, and the first data is data of the target area or data of the target application.

[0973] Optionally, the transceiver module 1310 is further configured to send identification information of the first network element.

[0974] Optionally, the first network element includes one or more user plane network elements, and the first data volume includes the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

[0975] Optionally, the transceiver module 1310 is also used to receive a third data volume, which includes the data volume of the first data of each session in one or more sessions; the processing module 1320 is also used to determine the data volume of the first data transmitted by each user plane network element in the one or more user plane network elements based on the third data volume, and the one or more user plane network elements are used to transmit data of at least one session in the one or more sessions.

[0976] Optionally, the transceiver module 1310 is further used to receive identification information of the one or more sessions; the processing module 1320 is further used to determine identification information of the one or more user plane network elements based on the identification information of the one or more sessions.

[0977] Optionally, the first data is data of the target application, and the transceiver module 1310 is further used to send information indicating a first area, where the first area is an area where a terminal device using the target application is located.

[0978] 13 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application. The communication device 1500 includes a processor 1510 and a communication interface 1520 , which may be interconnected via a bus 1530 .

[0979] Optionally, the communication device 500 may further include a memory 1540. The processor 1510 is coupled to the memory 1540 and configured to execute instructions stored in the memory 1540 to control the communication interface 1520 to send and / or receive signals.

[0980] It should be understood that the processor 1510 and memory 1540 may be combined into a processing device, and the processor 1510 is used to execute the program code stored in the memory 1540 to implement the above functions. In specific implementations, the memory 1540 may also be integrated into the processor 1510 or independent of the processor 1510.

[0981] The memory 540 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used for related instructions and data.

[0982] The processor 510 may be one or more central processing units (CPUs). In the case where the processor 510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0983] The above description is merely an example description. For details, please refer to the contents shown in the above method embodiment.

[0984] FIG14 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application.

[0985] Communication device 1600 includes an input / output interface 1620 and a processor 1610. Input / output interface 1620 may be an input / output circuit. Processor 1610 may be a signal processor, a chip, or other integrated circuit capable of implementing the method of the present application. Input / output interface 1620 is used for inputting or outputting signals or data.

[0986] In one possible implementation, the processor 1610 implements the functions implemented by the network device or the terminal device by executing instructions stored in the memory.

[0987] Optionally, the communication device 1600 further includes a memory.

[0988] Optionally, the processor and memory are integrated together.

[0989] Optionally, the memory is outside the communication device 1600 .

[0990] In one possible implementation, the processor 1610 may be a logic circuit, which inputs / outputs messages or signals through the input / output interface 1620. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.

[0991] The above description of the communication device 1600 is only an exemplary description. The communication device 1600 can be used to execute the method described in the above embodiment. For specific content, please refer to the description of the above method embodiment, which will not be repeated here.

[0992] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0993] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0994] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving a network device or a terminal device in any of the above embodiments.

[0995] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0996] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.

[0997] In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0998] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0999] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[1000] In the several embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[1001] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[1002] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[1003] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[1004] The above is only a specific implementation of the embodiment of the present application, but the scope of protection of the embodiment of the present application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the embodiment of the present application, and they should be included in the scope of protection of the embodiment of the present application. Therefore, the scope of protection of the embodiment of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method comprises: Acquire a first data volume of a first network element, where the first data volume is a data volume of first data transmitted by the first network element, and the first data is data of a target area or data of a target application; Obtaining total power consumption and a second data volume of the first network element, where the second data volume is a total amount of data transmitted by the first network element; A first power consumption is determined according to the total power consumption of the first network element, the first data volume, and the second data volume, where the first power consumption is the power consumption of the first network element used to transmit the first data.

2. The method according to claim 1, characterized in that The data of the target area includes: data of terminal devices located in the target area.

3. The method according to claim 1, characterized in that The data of the target area includes: data of a cell corresponding to the target area.

4. The method according to any one of claims 1 to 3, characterized in that The first network element includes one or more user plane network elements, and the first data volume includes a data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

5. The method according to claim 4, characterized in that The method further comprises: Sending a first request message to the second network element, where the first request message includes information indicating the target area or the target application; The obtaining of the first data volume of the first network element includes: Receive the first data volume from the second network element.

6. The method according to claim 5, characterized in that The first data is data of the target area, the second network element is a session management network element, and a service area of ​​the second network element includes the target area; or, The first data is data of the target application, and the second network element is a policy control network element, which provides policy control for a session used to transmit the data of the target application.

7. The method according to claim 5 or 6, characterized in that The method further comprises: Receive identification information of the one or more user plane network elements from the second network element.

8. The method according to claim 5 or 6, characterized in that The method further comprises: receiving identification information of one or more sessions from the second network element, where data of the one or more sessions includes the first data; The identification information of the one or more user plane network elements is obtained according to the identification information of the one or more sessions, and the one or more user plane network elements are used to transmit data of at least one session of the one or more sessions.

9. The method according to claim 7 or 8, characterized in that The obtaining the total power consumption and the second data volume of the first network element includes: Sending a second request message, where the second request message includes identification information of the one or more user plane network elements; The total power consumption of each user plane network element among the one or more user plane network elements and the total amount of data transmitted by each user plane network element are received.

10. The method according to any one of claims 1 to 9, characterized in that The first network element includes one or more access network devices, and the method further includes: Sending a third request message to the access and mobility management network element, where the third request message is used to request identification information of an access network device whose service area includes a first area, where the first area is the target area, or the first area is an area where a terminal device using the target application is located; Receive identification information of the one or more access network devices from the access and mobility management network element.

11. The method according to claim 10, characterized in that The method further comprises: Receive area information covered by the one or more access network devices from the access and mobility management network element.

12. A communication method, characterized in that: The method comprises: receiving a first request message, where the first request message includes information indicating a target area or a target application; A first data volume of a first network element is sent, where the first data volume is a data volume of first data transmitted by the first network element, and the first data is data of the target area or data of the target application.

13. The method according to claim 12, characterized in that The method further comprises: Send identification information of the first network element.

14. The method according to claim 12 or 13, characterized in that The first network element includes one or more user plane network elements, and the first data volume includes a data volume of the first data transmitted by each user plane network element in the one or more user plane network elements.

15. The method according to claim 14, characterized in that The method further comprises: receiving a third data amount, the third data amount including a data amount of the first data for each of one or more sessions; The data volume of the first data transmitted by each user plane network element of the one or more user plane network elements is determined based on the third data volume, and the one or more user plane network elements are used to transmit data of at least one session of the one or more sessions.

16. The method according to claim 15, characterized in that The method further comprises: receiving identification information of the one or more sessions; The identification information of the one or more user plane network elements is determined according to the identification information of the one or more sessions.

17. The method according to any one of claims 12 to 16, characterized in that The first data is data of the target application, and the method further includes: Information indicating a first area is sent, where the first area is an area where a terminal device using the target application is located.

18. A communication device, characterized in that: The method comprises modules or units for executing the method according to any one of claims 1 to 11.

19. A communication device, characterized in that: The method comprises modules or units for executing the method according to any one of claims 12 to 17.

20. A communication device, characterized in that: The apparatus includes a processor coupled to a memory, wherein the memory stores instructions. When the instructions are executed by the processor, the processor performs the method according to any one of claims 1 to 11 or the method according to any one of claims 12 to 17.

21. A computer-readable storage medium, characterized in that A computer program or instruction is stored, wherein the computer program or instruction is used to implement the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 17.

22. A chip, characterized in that: include: A processor and an interface, configured to call from a memory and run a computer program stored in the memory to perform the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 17.

23. A computer program product, characterized in that The invention comprises instructions which, when executed on a computer, cause the method according to any one of claims 1 to 11 or the method according to any one of claims 12 to 17 to be performed.

Images