WO2021139394A1 - 通信方法、装置、计算机可读介质及电子设备 - Google Patents

通信方法、装置、计算机可读介质及电子设备 Download PDF

Info

Publication number
WO2021139394A1
WO2021139394A1 PCT/CN2020/128173 CN2020128173W WO2021139394A1 WO 2021139394 A1 WO2021139394 A1 WO 2021139394A1 CN 2020128173 W CN2020128173 W CN 2020128173W WO 2021139394 A1 WO2021139394 A1 WO 2021139394A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
subscription request
request
information
edge computing
Prior art date
Application number
PCT/CN2020/128173
Other languages
English (en)
French (fr)
Inventor
张卓筠
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP20911335.6A priority Critical patent/EP3993485A4/en
Publication of WO2021139394A1 publication Critical patent/WO2021139394A1/zh
Priority to US17/585,400 priority patent/US20220150678A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • This application relates to the field of computer and communication technology, and in particular, to a communication method, device, computer-readable medium, and electronic equipment.
  • AF Application Function
  • MEC Multi-access Edge Computing
  • the embodiments of the present application provide a communication method, device, computer readable medium, and electronic equipment, which can reduce the time delay of network information opening, and meet the time delay requirements of application function entities in the edge computing platform for network information.
  • the embodiment of the application provides a communication method applied to an edge computing scenario, in which an edge computing platform is deployed, the edge computing platform is deployed with application function entities, the edge computing platform and a lightweight network
  • the open function entity is connected
  • the lightweight network open function entity is connected to the core network open function entity deployed in the core network
  • the communication method is executed by the lightweight network open function entity, and the communication method includes:
  • the capability invocation request is used to request to obtain wireless network information, sending a subscription request for wireless network information to the access network side based on the capability invocation request;
  • the embodiment of the application provides a communication method applied to an edge computing scenario, in which an edge computing platform is deployed, the edge computing platform is deployed with application function entities, the edge computing platform and a lightweight network
  • the open function entity is connected
  • the lightweight network open function entity is connected to the core network open function entity deployed in the core network
  • the communication method is performed by the base station deployed in the area where the edge computing platform is located or the operation and maintenance of the base station
  • the management system executes, and the communication method includes:
  • the wireless network information is sent to the light-weight network open function entity, so that the light-weight network open function entity sends the wireless network information to the wireless network.
  • the network information is fed back to the application function entity.
  • An embodiment of the application provides a communication device applied to an edge computing scenario, in which an edge computing platform is deployed, the edge computing platform is deployed with application function entities, the edge computing platform and a lightweight network
  • the open function entity is connected
  • the lightweight network open function entity is connected to the core network open function entity deployed in the core network
  • the communication device is arranged in the lightweight network open function entity, and the communication device includes:
  • the first receiving unit is configured to receive a capability invocation request sent by the application function entity
  • the first sending unit is configured to send a wireless network information subscription request to the access network side based on the capability invocation request when the capability invocation request is used to request to obtain wireless network information;
  • the second receiving unit is configured to receive wireless network information fed back by the access network side for the subscription request;
  • the second sending unit is configured to notify the application function entity of the wireless network information.
  • the embodiment of the application provides a communication device applied to an edge computing scenario, in which an edge computing platform is deployed, the edge computing platform is deployed with application function entities, and the edge computing platform is open to a lightweight network
  • the functional entity is connected
  • the lightweight network open function entity is connected to the core network open function entity deployed in the core network
  • the communication device is set in a base station deployed in the area where the edge computing platform is located or is set in the base station
  • the communication device includes:
  • the obtaining unit is configured to obtain a subscription request for wireless network information sent by the lightweight network open function entity, where the subscription request is sent by the lightweight network open function entity according to the capability call request sent by the application function entity of;
  • a monitoring unit configured to monitor wireless network information according to the subscription request
  • the sending unit is configured to send the wireless network information to the lightweight network open function entity when the wireless network information conforming to the subscription request is monitored, so that the lightweight network open function entity Feed back the wireless network information to the application function entity.
  • the embodiments of the present application provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a processor, it implements a communication method applied to an edge computing scenario on the side of a lightweight network open function entity, or implements A communication method applied to an edge computing scenario on the side of the base station or the operation and maintenance management system of the base station.
  • An embodiment of the present application provides an electronic device, including: one or more processors; a storage device, used to store one or more programs, when the one or more programs are executed by the one or more processors At the same time, the one or more processors are allowed to implement the communication method applied to the edge computing scenario on the side of the lightweight network open function entity, or implement the communication method applied to the edge computing scenario on the base station or the operation and maintenance management system side of the base station. Communication method.
  • the lightweight network open function entity is connected to the edge computing platform and the core network open function entity, so that the lightweight network open function entity can be used in application functions.
  • the entity and the access network side implement wireless network information subscription processing, that is, receive the capability call request sent by the application function entity, send a wireless network information subscription request to the access network side based on the capability call request, and connect the access network The wireless network information fed back from the side is notified to the application function entity.
  • the time delay for the application function entity to obtain the subscribed wireless network information can be reduced, that is, The time delay of network information opening is reduced, so that the time delay requirement of the application function entity in the edge computing platform for the network information can be met.
  • Figure 1 shows a schematic diagram of a network capability opening architecture in related technologies
  • FIG. 2 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;
  • FIG. 3 shows a schematic diagram of another exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;
  • Fig. 4 shows a flowchart of a communication method applied to an edge computing scenario according to an embodiment of the present application
  • Fig. 5 shows a flowchart of a communication method applied to an edge computing scenario according to an embodiment of the present application
  • FIG. 6 shows a flow chart of interaction between devices under the system architecture shown in FIG. 2;
  • FIG. 7 shows a flow chart of interaction between devices under the system architecture shown in FIG. 3;
  • Fig. 8 shows a block diagram of a communication device applied to an edge computing scenario according to an embodiment of the present application
  • Fig. 9 shows a block diagram of a communication device applied to an edge computing scenario according to an embodiment of the present application.
  • FIG. 10 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • FIG. 1 shows a schematic diagram of a network capability opening architecture in related technologies.
  • the application program interfaces of the Network Exposure Function (NEF) namely API1, API2, API3, ... APIn
  • NEF Network Exposure Function
  • AF application function
  • FIG. 1 shows a schematic diagram of a network capability opening architecture in related technologies.
  • the application program interfaces of the Network Exposure Function (NEF) namely API1, API2, API3, ... APIn
  • AF application function
  • AF application function
  • AF application function
  • NEF Network information is opened to AF through NEF
  • AF is deployed on the Multi-access Edge Computing (MEC) platform
  • MEC platforms are generally deployed near the core base station NEF is usually located in the core computer room of the operator, that is, NEF is located farther from the MEC platform, which will cause the delay of network information to be longer.
  • the embodiments of the present application provide a communication method, device, computer-readable storage medium, and electronic equipment, which can reduce the time delay when network information is opened.
  • Fig. 2 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied.
  • the system architecture may include user equipment (user equipment 1 and user equipment 2 as shown in FIG. 2), where the user equipment (User Equipment, UE for short) may be a smart phone, a tablet computer, a portable computer, Desktop computers, smart watches, etc.), base stations (base station 1 and base station 2 as shown in Figure 2), user plane function entities (User Plane Function, referred to as UPF), edge computing platform (MEC), application function entities (AF) ), Lightweight Network Exposure Function-lite (NEF-lite), Core Network Exposure Function-central (NEF-central), and Operation Administration and Maintenance (Operation Administration and Maintenance, for short) OAM) system.
  • UPF User Plane Function
  • MEC edge computing platform
  • AF application function entities
  • NEF-lite Lightweight Network Exposure Function-lite
  • NEF-central Core Network Exposure Function-central
  • OAM Operation Administration and Maintenance
  • base stations (base station 1 and base station 2 as shown in Figure 2) are connected to UPF through N3 interface, UPF and edge computing platform are connected through N6 interface, AF is deployed on MEC platform, NEF-lite and OAM The system, AF and NEF-lite are connected, and NEF-lite and NEF-central are connected.
  • the UPF shown in FIG. 2 may be an I-UPF (Intermediate UPF, source intermediate UPF) with uplink classifier (Uplink Classifier, ULCL) function, or an anchor point UPF.
  • NEF-lite can be deployed near the location of the MEC, or in the same computer room as the MEC. NEF-lite is used to open the capabilities of the MEC platform. The main open scenario is the opening of the wireless information of the base station serving the MEC platform. .
  • NEF-lite does not have a direct interface with the base station, but obtains wireless information on the base station side by connecting with the OAM system of the base station. This method can reduce the need for base station functions and the existing network architecture. Impact.
  • the connection between NEF-lite and NEF-central can realize the opening of the capabilities of the core network control plane to the MEC platform, that is, after NEF-lite receives the capability call request sent by the AF on the MEC platform, it will respond according to the request.
  • the included event identifier determines whether it is related to the capabilities of the wireless side (for example, whether it is used to request wireless network information). If it is not related to the capabilities of the wireless side, the request is forwarded to NEF-central, and NEF-central paired The request is authenticated and authorized.
  • NEF-lite can have no direct interface with other NF (Network Function) entities on the core network control plane, and is only connected to NEF-central, and NEF-lite can also invoke the capabilities of NEF-central , To realize the authentication and authorization of AF request.
  • NF Network Function
  • each device shown in FIG. 2 is merely illustrative. According to implementation needs, there can be any number of user equipments, base stations, UPFs, AFs, etc.
  • the AF may send a capability invocation request to NEF-lite.
  • the capability invocation request may include an event identifier (such as wireless network information that needs to be acquired), event filtering information (such as signal threshold), Event reporting information (such as maximum reporting times, minimum reporting interval, etc.), target information (such as target UE ID, target UE group ID, PDU (Protocol Data Unit) session information, target cell information, target location area, etc.) Target time period, etc.), AF information (such as AF address information, etc.), etc.
  • NEF-lite After NEF-lite receives the capability invocation request, it can perform authorization verification on the AF based on the capability invocation request.
  • NEF-lite cannot realize the authorization and verification of AF, for example, NEF-lite does not have the ability to authorize and verify AF, or the contract information of AF is not imported into NEF-lite, then NEF-lite cannot complete the application.
  • the capability call request can be sent to NEF-central, and NEF-central will implement the authorization verification of AF, and return the result to NEF-lite.
  • NEF-lite can send a subscription request to OAM according to the capability call request. After receiving the subscription request, OAM can determine whether to accept the subscription request. In the case of not accepting the subscription request, it can feed back the response message of refusing the subscription and the reason for the refusing to AF; when OAM accepts the subscription request Then, you can feedback the response message agreeing to subscribe. After NEF-lite receives the response information, it can forward it to AF.
  • the OAM has a connection with the base station, and will receive the wireless side information reported by the base station.
  • the wireless side information may be information reported periodically or reported information triggered by a special event. After the corresponding wireless network information is monitored according to the subscription request, the monitored wireless network information can be sent to NEF-lite, and then forwarded by NEF-lite to AF.
  • the OAM may also send the subscription request to the target base station.
  • the target base station may determine whether to accept the subscription request In the case that the subscription request is not accepted, the response message of the subscription rejection and the reason for the subscription rejection can be fed back; in the case that the target base station accepts the subscription request, the response message that the subscription is approved can be fed back.
  • OAM receives the response information, it can forward it to NEF-lite, and then NEF-lite to AF.
  • the wireless network information mentioned in the context may be a wireless network congestion indication, a Quality of Service (QoS) congestion indication, a QoS measurement report, and the like.
  • QoS Quality of Service
  • Fig. 3 shows a schematic diagram of another exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied.
  • the system architecture includes user equipment (user equipment 1 and user equipment 2 as shown in Figure 3), base stations (base station 1 and base station 2 as shown in Figure 3), and user plane function entities (UPF). ), edge computing platform (MEC), application function entity (AF), lightweight network open function entity (NEF-lite) and core network open function entity (NEF-central).
  • the base stations (base station 1 and base station 2 shown in Figure 3) are connected to the UPF through the N3 interface
  • the UPF and the MEC platform are connected through the N6 interface
  • the AF is deployed on the MEC platform
  • the AF is connected to the NEF-lite.
  • NEF-lite is connected to NEF-central.
  • NEF-lite is directly connected to the base station without going through the operation and maintenance management system, that is, the OAM system, so the delay of information transmission can be further reduced.
  • NEF-lite after NEF-lite receives the capability invocation request sent by the AF, it may perform authorization verification on the AF based on the capability invocation request.
  • NEF-lite cannot realize the authorization and verification of AF, for example, NEF-lite does not have the ability to perform authorization and verification of AF, or the contract information of AF is not imported into NEF-lite, then NEF-lite cannot complete AF.
  • the capability call request can be sent to NEF-central, and NEF-central will implement the authorization verification of AF.
  • NEF-lite can send a subscription request to the base station according to the capability invocation request. After receiving the subscription request, the base station can determine whether to accept the subscription request. In the case of not accepting the subscription request, it can feed back the response message of the rejection of subscription and the reason for the rejection to NEF-lite; the base station accepts the subscription request In the case of, you can feed back the response message agreeing to subscribe to NEF-lite. After NEF-lite receives the response information, it can forward it to AF.
  • the base station after the base station monitors the corresponding wireless network information according to the subscription request, it can send the monitored wireless network information to NEF-lite, which then forwards it to AF.
  • NEF-lite is deployed closer to the MEC platform, it can reduce the time delay for AF to obtain subscribed wireless network information, which also reduces the time when network information is opened. In turn, it can meet the delay requirements of the AF on the network information in the MEC platform.
  • FIG. 4 shows a flowchart of a communication method applied to an edge computing scene according to an embodiment of the present application, and the edge computing scene may be the edge computing scene shown in FIG. 2 or FIG. 3.
  • the communication method applied to the edge computing scenario can be executed by NEF-lite shown in FIG. 2 or FIG. 3, that is, a lightweight network open function entity.
  • the communication method applied to edge computing scenarios includes at least step S410 to step S440, which are described in detail as follows:
  • step S410 the lightweight network opening function entity receives the capability invocation request sent by the application function entity.
  • the application function entity may generate a capability invocation request, and send the generated capability invocation request to the lightweight open function entity through the network.
  • the capability invocation request can include event identification (such as wireless network information that needs to be acquired, etc.), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting interval, etc.), target information (such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.), AF information (such as AF address information, etc.).
  • event identification such as wireless network information that needs to be acquired, etc.
  • event filtering information such as signal threshold
  • event reporting information such as maximum reporting times, minimum reporting interval, etc.
  • target information such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.
  • AF information such as AF address information, etc.
  • step S420 in the case that the capability invocation request is used to request to obtain wireless network information, the lightweight network opening function entity sends a wireless network information subscription request to the access network side based on the capability invocation request.
  • the lightweight network open function entity can determine whether the capability invocation request is for request acquisition according to the event identifier contained in the capability invocation request Wireless network information. For example, when the event identifier is a first value, it is determined that it is used to request wireless network information; when the event identifier is a second value, it is determined that it is not used to request wireless network information. Both the first value and the second value can be set according to actual conditions.
  • the lightweight network open function entity may forward the capability invocation request to NEF-central, that is, to the core
  • the network open function entity the core network open function entity authenticates and authorizes the request.
  • the core network open function entity accepts the subscription request, it will apply the existing capability opening process according to the subscription request to obtain the corresponding capability Information, and send a corresponding notification message to the lightweight network open function entity, and the lightweight network open function entity forwards it to the application function entity.
  • the lightweight network open function entity may authorize and verify the identity of the application function entity according to the capability invocation request, and if the identity authorization verification of the application function entity is passed, then according to the capability The call request sends a subscription request to the access network side.
  • the lightweight network open function entity may obtain the digital certificate of the application function entity in advance, and then the lightweight network open function entity may authorize and verify its identity based on the digital certificate of the application function entity.
  • the capability call request may be sent to the core network open function entity to make the core network open
  • the functional entity authorizes and verifies the identity of the application functional entity, and then the lightweight network open functional entity can determine whether the application functional entity’s identity authorization verification is passed according to the authentication result of the core network open functional entity’s identity authorization to the application functional entity.
  • a subscription request can be sent to the access network side according to the capability invocation request.
  • the N lightweight network open function entity does not have the ability to perform authorization verification processing on the functional entity, but instead places the authorization verification function on the core network open function entity side for processing, then it can be determined that the lightweight The network open function entity cannot complete the authentication of the application function entity; or if the contract information of the application function entity is not imported into the lightweight network open function entity, then the lightweight network open function entity cannot complete the application function entity.
  • Authorization verification if the N lightweight network open function entity does not have the ability to perform authorization verification processing on the functional entity, but instead places the authorization verification function on the core network open function entity side for processing, then it can be determined that the lightweight The network open function entity cannot complete the authentication of the application function entity; or if the contract information of the application function entity is not imported into the lightweight network open function entity, then the lightweight network open function entity cannot complete the application function entity.
  • Authorization verification if the N lightweight network open function entity does not have the ability to perform authorization verification processing on the functional entity, but instead places the authorization verification function on the core network open function entity side for processing, then it
  • the process of the lightweight network open function entity sending a subscription request to the access network side according to the capability invocation request may specifically be as follows: according to the address indication information contained in the capability invocation request, determining the connection with the subscription Request the corresponding information of at least one target base station, and then send a subscription request to the at least one target base station or the operation and maintenance management system of the at least one target base station based on the information of the at least one target base station. That is, the lightweight network open entity function first parses out the information of one or more target base stations based on the address indication information in the capability call request, and determines one or more target base stations based on the information of one or more target base stations. The target base station then sends the subscription request to the operation and maintenance management system of the one or more target base stations.
  • the address indication information includes at least one of the following: address information of the application function entity, information of the target cell, and target location area information.
  • the location of the edge computing platform can be determined according to the address information of the application function entity, and then the base station near the location of the edge computing platform can be used as the target base station corresponding to the subscription request; or the target base station can be formed according to the information of the target cell.
  • the base station of the target cell serves as the target base station corresponding to the subscription request; or, according to the target location area information, the base station whose signal coverage includes the target location area may be used as the target base station corresponding to the subscription request.
  • the candidate base stations can be determined separately based on the at least two pieces of information, and then The target base station is determined from the candidate base stations, for example, all the candidate base stations can be used as the target base station, or a target base station with better performance can be selected from the candidate base stations.
  • the access network side includes a base station and an operation and maintenance management system connected to the base station, and the operation and maintenance of the lightweight network open function entity and the base station
  • the lightweight network open function entity can send a subscription request to the operation and maintenance management system based on the capability call request, and then the operation and maintenance management system determines whether to accept the subscription request; of course, the operation and maintenance management system After receiving the subscription request, the subscription request may also be forwarded to the base station, and then the base station determines whether to accept the subscription request.
  • the access network side includes the base station, and the lightweight network open function entity is connected to the base station, then the lightweight network open function entity can directly send the base station based on the capability call request. Send a subscription request.
  • the lightweight network open function entity before the lightweight network open function entity receives the wireless network information fed back by the access network side for the subscription request, after the lightweight network open function entity sends the subscription request to the access network side, The subscription response fed back by the access network side may be received, and the subscription response is used to indicate whether the access network side accepts the subscription request. Then, the lightweight network open function entity feeds back the subscription response to the application function entity.
  • the lightweight network opening function entity may feed back the rejection reason information to the application function entity according to the subscription response; the subscription response indicates the access
  • the lightweight network opening function entity can detect whether the wireless network information fed back by the access network side for the subscription request is received.
  • the target base station responds to the subscription request, when all target base stations sent to the subscription request refuse to accept the subscription request, it can be determined that the access network side rejects the subscription request; In the case that at least one target base station accepts the subscription request, it can be determined that the access network side accepts the subscription request. If the operation and maintenance management system responds to the subscription request, the operation and maintenance management system can determine whether the subscription request needs to be accepted according to the prior configuration file.
  • the lightweight network opening function entity receives the wireless network information fed back by the access network side for the subscription request.
  • the access network side after receiving the subscription request feedback, the access network side will generate corresponding wireless network information, and then send the wireless network information to the lightweight network open function entity through the network.
  • the lightweight network open function entity in the case of the system architecture shown in FIG. 2, that is, the lightweight network open function entity is connected to the operation and maintenance management system of the base station, then the lightweight network open function entity can receive operation and maintenance
  • the wireless network information sent by the management system may be the wireless network information monitored by the base station in accordance with the subscription request forwarded by the operation and maintenance management system and transmitted to the operation and maintenance management system; or it may be The operation and maintenance management system monitors the wireless network information that meets the subscription request according to the information reported by the base station.
  • the lightweight network open function entity In the case of the system architecture shown in FIG. 3, that is, the lightweight network open function entity is directly connected to the base station, then the lightweight network open function entity can directly receive the wireless network information fed back by the base station in response to the subscription request.
  • step S440 the lightweight network opening function entity notifies the application function entity of the wireless network information.
  • the lightweight network open function entity will send wireless network information to the application function entity through the network, and the application function entity will receive the wireless network information.
  • the application function entity may perform application layer processing based on the wireless network information.
  • the lightweight network open function entity may also count the wireless network information requested by the application function entity, such as the number of calls, to obtain the statistical result, and then report the statistical result to the core network open function entity.
  • FIG. 4 The technical solution of the embodiment shown in FIG. 4 is to explain the implementation details of the communication method of the embodiment of the present application from the perspective of a lightweight network open function entity.
  • the following describes the present application from the perspective of the base station or the operation and maintenance management system of the base station with reference to FIG. 5
  • the implementation details of the communication method of the embodiment are described in detail:
  • FIG. 5 shows a flowchart of a communication method applied to an edge computing scenario according to an embodiment of the present application
  • the edge computing scenario may be the edge computing scenario shown in FIG. 2 or FIG. 3.
  • the communication method applied to the edge computing scenario may be executed by any base station (such as base station 1 or base station 2) shown in FIG. 2 or FIG. 3, or may be executed by the operation and maintenance management system shown in FIG.
  • the communication method applied to the edge computing scenario at least includes steps S510 to S530, which are described in detail as follows:
  • step S510 the base station or the operation and maintenance management system of the base station obtains a subscription request for wireless network information sent by the lightweight network open function entity.
  • the subscription request is a capability call request sent by the lightweight network open function entity according to the application function entity. Sent.
  • the lightweight network open function entity in the case of the system architecture shown in FIG. 2, that is, the lightweight network open function entity is connected to the operation and maintenance management system of the base station, then the communication method shown in FIG.
  • the operation and maintenance management system can receive subscription requests from the lightweight network open function entity; in the case that the communication method shown in Figure 5 is executed by the base station, the base station can receive the operation and maintenance The subscription request from the lightweight network open function entity forwarded by the management system.
  • the system architecture shown in FIG. 3 that is, the lightweight network open function entity is directly connected to the base station, then the base station can directly receive the subscription request sent by the lightweight network open function entity.
  • step S520 the base station or the operation and maintenance management system of the base station monitors wireless network information according to the subscription request.
  • the base station or the operation and maintenance management system of the base station may first determine whether to accept the subscription request according to the information contained in the subscription request, and then determine whether to accept the subscription request.
  • the wireless network information is monitored according to the subscription request, and an acceptance notification message is returned to the lightweight network opening function entity; when it is determined that the subscription request needs to be rejected, the function can be opened to the lightweight network
  • the entity sends a rejection notification message.
  • the rejection notification message may include a corresponding rejection reason.
  • the base station or the operation and maintenance management system of the base station may reject the subscription request if it is determined that the terminal is not connected to the base station according to the identification of the terminal included in the subscription request; the base station or The operation and maintenance management system of the base station may accept the subscription request when it is determined that the terminal has accessed the base station according to the terminal identifier included in the subscription request.
  • step S530 when the base station or the operation and maintenance management system of the base station monitors the wireless network information that meets the subscription request, the wireless network information is sent to the lightweight network open function entity to enable the lightweight network open function The entity feeds back the wireless network information to the application function entity.
  • the communication method shown in FIG. 5 is controlled by the operation and maintenance
  • the operation and maintenance management system will send wireless network information that meets the subscription request to the lightweight network open function entity based on the wireless side information reported by the base station and the subscription request; the communication method shown in Figure 5 is determined by the base station
  • the base station can send the wireless network information that meets the subscription request to the operation and maintenance management system according to the subscription request and the detected wireless side information, and then the operation and maintenance management system forwards it to the lightweight network open function entity.
  • the system architecture shown in FIG. 3 that is, the lightweight network open function entity is directly connected to the base station, then the base station can directly send wireless network information to the lightweight network open function entity.
  • Figures 4 and 5 illustrate the technical solutions of the embodiments of the present application from the perspectives of lightweight network open function entities and base stations, respectively.
  • the following is a combination of the system architectures shown in Figures 2 and 3 to describe the embodiments of the present application.
  • FIG. 2 in the system architecture shown in FIG. 2, that is, the application scenario in which the lightweight network open function entity is connected to the operation and maintenance management system of the base station, the interaction process between the devices is shown in FIG. Show, including the following steps:
  • the application function entity sends a capability invocation request to the lightweight network open function entity (NEF-lite).
  • the capability invocation request may include event identification (such as wireless network information that needs to be acquired, etc.), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting Time interval, etc.), target information (such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.), AF information (such as AF address information, etc.).
  • event identification such as wireless network information that needs to be acquired, etc.
  • event filtering information such as signal threshold
  • event reporting information such as maximum reporting times, minimum reporting Time interval, etc.
  • target information such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.
  • AF information such as AF address information, etc.
  • step S602a after the NEF-lite receives the capability invocation request, it processes the capability invocation request.
  • the lightweight network open function entity may perform authorization verification on the request, and if the authorization verification is passed, the lightweight network open function entity will perform further processing, such as adding the capability call request included
  • the external ID of the user equipment (UE) is converted into an internal ID
  • the external group identification of the user equipment (UE) is converted into an internal group identification, and the corresponding information is determined according to the location information of the edge computing platform (MEC) where the application function entity (AF) is located
  • MEC edge computing platform
  • AF application function entity
  • step S602b may be executed, that is, the lightweight network opening function entity sends the capability call request to the core network open
  • the functional entity NEF-central
  • NEF-central then completes the authentication and authorization of the capability call request by NEF-central, and returns the result to NEF-lite to indicate to NEF-lite whether to accept the capability call request.
  • NEF-lite or NEF-central performs authorization verification, if it is determined that the capability call request needs to be rejected, the corresponding reason value can be returned to AF.
  • the capability invocation response is directly fed back to the AF, and the capability invocation response includes the rejection information and the corresponding rejection reason.
  • the lightweight network opening function entity sends a wireless information subscription request to the operation maintenance management (OAM) system according to the capability invocation request sent by the application function entity (AF).
  • the subscription request can include event identification (such as wireless network information that needs to be obtained), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting interval, etc.), target information (such as Target UE identity, target UE group identity, PDU session information, target cell information, target base station, target time period, etc.) and so on.
  • Step S604 After receiving the subscription request sent by NEF-lite, the OAM system sends a wireless information subscription request to the target base station.
  • the subscription request includes event identification (such as wireless network information that needs to be obtained, etc.), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting interval, etc.), target information (such as target UE identity, target UE group identity, PDU session information, target cell information, target time period, etc.).
  • event identification such as wireless network information that needs to be obtained, etc.
  • event filtering information such as signal threshold
  • event reporting information such as maximum reporting times, minimum reporting interval, etc.
  • target information such as target UE identity, target UE group identity, PDU session information, target cell information, target time period, etc.
  • Step S605 The target base station returns a subscription response message to the OAM system, indicating whether the subscription request is accepted.
  • the target base station detects that the target UE is not connected to the base station, it will reject the subscription request.
  • the reason for the rejection may be fed back in the subscription response message.
  • steps S604 and S605 are optional steps.
  • the OAM system can determine whether to accept the subscription request, the OAM system can directly determine whether to accept the subscription request, and set the wireless The information subscription response is sent to NEF-lite.
  • Step S606 After the OAM system receives and responds to the subscription request (applicable to the scenario where OAM determines whether to accept the subscription request), or after receiving the subscription response message returned by the target base station in step S605 (applicable to the base station determining whether to accept the subscription request) The scenario of subscription request), a subscription response message is returned to NEF-lite to indicate whether the subscription request is accepted. In some embodiments, in the case that the OAM rejects the subscription request, the corresponding reason may be returned.
  • Step S607 After receiving the subscription response message, NEF-lite returns a subscription response message to the AF to indicate whether to accept the subscription request. In some embodiments, in the case that NEF-lite rejects the subscription request, the corresponding reason may be returned to AF.
  • step S608 needs to be executed. If steps S604 and S605 have not been executed before, step S608 is not executed, and step S609 is executed directly.
  • step S608 when the target base station detects that the event reporting condition is met, it sends an event notification message to the OAM system.
  • step S609 the OAM system detects whether the wireless information meets the requirements in the event subscription request, and if it does, sends an event notification message to NEF-lite.
  • step S610 NEF-lite sends an event notification message to the AF.
  • NEF-lite may report the statistical information of event invocation to NEF-central. This step is optional, and it is not necessary to upload statistical information of event calls.
  • the interaction process between the devices is shown in FIG. 7, including the following step:
  • Step S701 The application function entity (AF) sends a capability invocation request to the lightweight network open function entity (NEF-lite).
  • the capability invocation request may include event identification (such as wireless network information that needs to be acquired, etc.), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting Time interval, etc.), target information (such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.), AF information (such as AF address information, etc.).
  • event identification such as wireless network information that needs to be acquired, etc.
  • event filtering information such as signal threshold
  • event reporting information such as maximum reporting times, minimum reporting Time interval, etc.
  • target information such as target UE identity, target UE group identity, PDU session information, target cell information, target location area, target time period, etc.
  • AF information such as AF address information, etc.
  • NEF-lite processes the capability invocation request.
  • NEF-lite can perform authorization verification on the request. If the authorization verification is passed, further processing will be performed, such as converting the external ID of the user equipment (UE) contained in the capability call request into an internal ID , Convert the external group identifier of the UE into the internal group identifier, determine the corresponding information of one or more base stations according to the location information of the MEC where the AF is located, and use these information as the target base station.
  • UE user equipment
  • step S702b in the case that NEF-lite cannot complete the authorization of the capability call request, step S702b may be performed, that is, the capability call request is sent to the core network open function entity (NEF-central), NEF-central then completes the authentication and authorization of the capability call request, and returns the result to NEF-lite to indicate to NEF-lite whether to accept the capability call request.
  • NEF-central core network open function entity
  • step S705 is directly executed, that is, the capability invocation response is fed back to the AF, and the capability invocation response includes the rejection information and the corresponding rejection reason.
  • Step S703 NEF-lite sends a wireless information subscription request to the target base station according to the capability invocation request sent by the AF.
  • the subscription request can include event identification (such as wireless network information that needs to be obtained), event filtering information (such as signal threshold), event reporting information (such as maximum reporting times, minimum reporting interval, etc.), target information (such as Target UE identity, target UE group identity, PDU session information, target cell information, target time period, etc.)
  • Step S704 The target base station returns a subscription response message to NEF-lite, indicating whether the subscription request is accepted.
  • the target base station detects that the target UE is not connected to the base station, it will reject the subscription request.
  • the reason for the rejection may be fed back in the subscription response message.
  • Step S705 After receiving the subscription response message, NEF-lite returns a response message to the AF to indicate whether to accept the subscription request.
  • a response message of rejecting the subscription request may be returned and include a corresponding reason to the AF, such as a specific reason value.
  • at least one target base station accepts the subscription request, it returns a response message of accepting the subscription request to the AF.
  • Step 706 When the target base station detects that the event reporting condition is met, it sends an event notification message to NEF-lite.
  • step S707 NEF-lite checks whether the notification message meets the requirements in the event reporting information, and if it does, it sends the event notification message to the AF.
  • NEF-lite may report the statistical information of event invocation to NEF-central. This step is optional, and it is not necessary to upload statistical information of event calls.
  • the technical solution of the embodiment shown in FIG. 7 can further shorten the delay of capability opening because the lightweight network opening function entity, that is, NEF-lite, directly interacts with the base station.
  • the technical solution of the above-mentioned embodiment of the present application introduces a lightweight network open function entity and deploys it at a position closer to the edge computing platform, so that the time delay for the application function entity to obtain subscribed wireless network information can be reduced, that is, The time delay of network information opening is reduced, so that the time delay requirement of the application function entity in the edge computing platform for the network information can be met.
  • FIG. 8 shows a block diagram of a communication device applied to an edge computing scenario according to some embodiments of the present application.
  • the edge computing scenario may be the edge computing scenario shown in FIG. 2 or FIG. 3, and the communication device is set in a lightweight Within the network open functional entity.
  • a communication device 800 applied to an edge computing scenario includes: a first receiving unit 802, a first sending unit 804, a second receiving unit 806, and a second sending unit 808.
  • the first receiving unit 802 is configured to receive a capability call request sent by the application function entity; the first sending unit 804 is configured to call based on the capability when the capability call request is used to request wireless network information Request to send a subscription request for wireless network information to the access network side; the second receiving unit 806 is configured to receive the wireless network information fed back by the access network side for the subscription request; the second sending unit 808 is configured to send the wireless network information The network information is notified to the application function entity.
  • the first sending unit 804 is configured to: perform authorization verification on the identity of the application function entity according to the capability invocation request; If the verification is passed, the subscription request is sent to the access network side according to the capability invocation request.
  • the first sending unit 804 is further configured to: when the lightweight network open function entity cannot complete the authentication of the application function entity's identity, The capability invocation request is sent to the core network open function entity, so that the core network open function entity can authorize and verify the identity of the application function entity; receive the core network open function entity to the application function entity If the core network open function entity authenticates the application function entity’s identity authorization verification, the subscription request is sent to the access network side according to the capability invocation request.
  • the first sending unit 804 is configured to: determine information of at least one target base station corresponding to the subscription request according to the address indication information included in the capability invocation request,
  • the address indication information includes at least one of the following: the address information of the application function entity, the information of the target cell, the target location area information; based on the information of the at least one target base station, to the at least one target base station or the The operation and maintenance management system of at least one target base station sends the subscription request.
  • the second receiving unit 806 is further configured to: before receiving the wireless network information fed back by the access network side for the subscription request, receive the feedback from the access network side.
  • the subscription response is used to indicate whether the access network side accepts the subscription request; the second sending unit 808 is further configured to feed back the subscription response to the application function entity.
  • the second sending unit 808 is further configured to: in the case that the subscription response indicates that the access network side rejects the subscription request, send a notification to the user according to the subscription response
  • the application function entity feeds back rejection reason information
  • the communication device 800 applied to the edge computing scenario further includes: a detection unit configured to, when the subscription response indicates that the access network side accepts the subscription request, Detecting whether the wireless network information fed back by the access network side for the subscription request is received.
  • the access network side includes a base station and an operation and maintenance management system connected to the base station, and the lightweight network open function entity is connected to the operation and maintenance management system
  • the first sending unit 804 is configured to send the subscription request to the operation and maintenance management system based on the capability call request; the second receiving unit 806 is configured to receive the wireless network information sent by the operation and maintenance management system.
  • the access network side includes a base station, and the lightweight network open function entity is connected to the base station; the first sending unit 804 is configured to be based on the capability invocation request The subscription request is sent to the base station; the second receiving unit 806 is configured to receive wireless network information fed back by the base station in response to the subscription request.
  • the communication device 800 applied to the edge computing scenario further includes: a statistics unit configured to count the wireless network information requested by the application function entity to obtain a statistical result;
  • the second sending unit 808 is further configured to report the statistical result to the core network open function entity.
  • the first receiving unit 802 is further configured to, after receiving the capability invocation request sent by the application function entity, determine the event identifier contained in the capability invocation request. Whether the capability invocation request is used to request to obtain wireless network information; the first sending unit 804 is further configured to forward the capability invocation request to the The core network open function entity.
  • FIG. 9 shows a block diagram of a communication device applied to an edge computing scenario according to some embodiments of the present application.
  • the edge computing scenario may be the edge computing scenario shown in FIG. 2 or FIG. 3, and the communication device is set in a base station or Set in the operation and maintenance management system of the base station.
  • a communication device 900 applied to an edge computing scenario includes: an acquiring unit 902, a monitoring unit 904, and a sending unit 906.
  • the obtaining unit 902 is configured to obtain a subscription request for wireless network information sent by the lightweight network open function entity, where the subscription request is a capability call sent by the lightweight network open function entity according to the application function entity
  • the monitoring unit 904 is configured to monitor wireless network information according to the subscription request;
  • the sending unit 906 is configured to send the wireless network information to the A lightweight network open function entity, so that the lightweight network open function entity feeds back the wireless network information to the application function entity.
  • the communication device 900 applied to the edge computing scenario further includes: a determining unit configured to determine whether to accept the subscription request according to the information contained in the subscription request
  • the monitoring unit 904 is further configured to: in the case that the determining unit determines to accept the subscription request, monitor wireless network information according to the subscription request, and send an acceptance notification message to the lightweight network open function entity;
  • the unit 906 is further configured to send a rejection notification message to the lightweight network opening function entity when the determining unit determines that the subscription request needs to be rejected.
  • the determining unit is configured to: in a case where it is determined that the terminal does not access the base station according to the identification of the terminal included in the subscription request, then It is determined that the subscription request needs to be rejected; if it is determined that the terminal has accessed the base station according to the terminal identifier included in the subscription request, it is determined to accept the subscription request.
  • the acquiring unit 902 when the base station is connected to the lightweight network open function entity, the acquiring unit 902 is configured to: receive the light-weight network open function entity sent The subscription request.
  • the obtaining unit 902 is configured to receive the subscription request from the lightweight network open function entity forwarded by the operation and maintenance management system.
  • the operation and maintenance management system of the base station is connected to the lightweight network open function entity, and the communication device 900 is set in the operation and maintenance management system of the base station
  • the acquiring unit 902 is configured to receive the subscription request sent by the lightweight network open function entity.
  • FIG. 10 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • the computer system includes a central processing unit (Central Processing Unit, CPU) 1001, which can be loaded into a random system according to a program stored in a read-only memory (Read-Only Memory, ROM) 1002 or from a storage part 1008. Access to the program in the memory (Random Access Memory, RAM) 1003 to execute various appropriate actions and processing, for example, execute the method described in the foregoing embodiment. In RAM 1003, various programs and data required for system operation are also stored.
  • the CPU 1001, the ROM 1002, and the RAM 1003 are connected to each other through a bus 1004.
  • An input/output (Input/Output, I/O) interface 1005 is also connected to the bus 1004.
  • the following components are connected to the I/O interface 1005: input part 1006 including keyboard, mouse, etc.; output part 1007 including cathode ray tube (Cathode Ray Tube, CRT), liquid crystal display (LCD), etc., and speakers, etc.
  • the communication section 1009 performs communication processing via a network such as the Internet.
  • the driver 1010 is also connected to the I/O interface 1005 as needed.
  • a removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that the computer program read therefrom is installed into the storage portion 1008 as needed.
  • the process described above with reference to the flowchart can be implemented as a computer software program.
  • the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication part 1009, and/or installed from the removable medium 1011.
  • CPU central processing unit
  • the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above.
  • Computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any suitable of the above The combination.
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable computer program is carried therein.
  • This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .
  • the computer program contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code includes one or more executables for realizing the specified logic function. instruction.
  • the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved.
  • each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by It is realized by a combination of dedicated hardware and computer instructions.
  • the units described in the embodiments of the present application may be implemented in software or hardware, and the described units may also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.
  • this application also provides a computer-readable medium.
  • the computer-readable medium may be included in the electronic device described in the above-mentioned embodiment; or it may exist alone without being assembled into the electronic device. in.
  • the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by an electronic device, the electronic device realizes the method described in the above-mentioned embodiment.
  • modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory.
  • the features and functions of two or more modules or units described above may be embodied in one module or unit.
  • the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.
  • the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) execute the method according to the embodiment of the present application.
  • a non-volatile storage medium which can be a CD-ROM, U disk, mobile hard disk, etc.
  • Including several instructions to make a computing device which can be a personal computer, a server, a touch terminal, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供了一种通信方法、装置、计算机可读介质及电子设备。该边缘计算场景中部署有边缘计算平台，边缘计算平台部署有应用功能实体，边缘计算平台与轻量级网络开放功能实体相连，轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，该通信方法由所述轻量级网络开放功能实体执行，包括：接收应用功能实体发送的能力调用请求；在该能力调用请求用于请求获取无线网络信息的情况下，则基于该能力调用请求向接入网侧发送无线网络信息的订阅请求；接收接入网侧针对该订阅请求反馈的无线网络信息；将该无线网络信息通知给所述应用功能实体。

Description

通信方法、装置、计算机可读介质及电子设备
相关申请的交叉引用
本申请基于申请号为202010014254.4、申请日为2020年01月07日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及计算机及通信技术领域，具体而言，涉及一种通信方法、装置、计算机可读介质及电子设备。
背景技术
在移动通信场景中可能需要将某些网络信息开放给应用功能(Application Function，简称AF)实体，以便于AF根据这些信息进行相应的应用层处理。但是如果AF调用这些信息的时延过长，会导致信息无效，影响后续应用层的处理，尤其是在边缘计算场景中，由于多接入边缘计算(Multi-access Edge Computing，简称MEC)平台通常部署在更加靠近终端用户的位置，即远离运营商核心机房的位置，从而导致网络信息开放的时延较大。
发明内容
本申请的实施例提供了一种通信方法、装置、计算机可读介质及电子设备，能够降低网络信息开放的时延，满足边缘计算平台中的应用功能实体对网络信息的时延要求。
本申请的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本申请的实践而习得。
本申请实施例提供了一种应用于边缘计算场景的通信方法，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信方法由所述轻量级网络开放功能实体执行，所述通信方法包括：
接收所述应用功能实体发送的能力调用请求；
在所述能力调用请求用于请求获取无线网络信息的情况下，则基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求；
接收所述接入网侧针对所述订阅请求反馈的无线网络信息；
将所述无线网络信息通知给所述应用功能实体。
本申请实施例提供了一种应用于边缘计算场景的通信方法，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信方法由所述边缘计算平台所在区域内部署的基站或所述基站的操作维护管理系统执行，所述通信方法包括：
获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，所述订阅请求是所述轻量级网络开放功能实体根据所述应用功能实体发送的能力调用请求发送的；
根据所述订阅请求监测无线网络信息；
在监测到符合所述订阅请求的无线网络信息的情况下，则将所述无线网络信息发送给所述轻量级网络开放功能实体，以使所述轻量级网络开放功能实体将所述无线网络信息反馈给所述应用功能实体。
本申请实施例提供了一种应用于边缘计算场景的通信装置，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信装置设置于所述轻量级网络开放功能实体内，所述通信装置包括：
第一接收单元，配置为接收所述应用功能实体发送的能力调用请求；
第一发送单元，配置为在所述能力调用请求用于请求获取无线网络信息的情况下，基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求；
第二接收单元，配置为接收所述接入网侧针对所述订阅请求反馈的无线网络信息；
第二发送单元，配置为将所述无线网络信息通知给所述应用功能实体。
本申请实施例了一种应用于边缘计算场景的通信装置，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信装置设置于所述边缘计算平台所在区域内部署的基站内或设置于所述基站的操作维护管理系统内，所述通信装置包括：
获取单元，配置为获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，所述订阅请求是所述轻量级网络开放功能实体根据所述应用功能实体发送的能力调用请求发送的；
监测单元，配置为根据所述订阅请求监测无线网络信息；
发送单元，配置为在监测到符合所述订阅请求的无线网络信息的情况下，将所述无线网络信息发送给所述轻量级网络开放功能实体，以使所述 轻量级网络开放功能实体将所述无线网络信息反馈给所述应用功能实体。
本申请实施例提供了一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现轻量级网络开放功能实体侧的应用于边缘计算场景的通信方法，或者实现基站或所述基站的操作维护管理系统侧的应用于边缘计算场景的通信方法。
本申请实施例提供了一种电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现轻量级网络开放功能实体侧的应用于边缘计算场景的通信方法，或者实现基站或所述基站的操作维护管理系统侧的应用于边缘计算场景的通信方法。
在本申请的实施例中，通过部署轻量级网络开放功能实体，该轻量级网络开放功能实体与边缘计算平台及核心网络开放功能实体相连，使得轻量级网络开放功能实体能够在应用功能实体与接入网侧之间实现无线网络信息的订阅处理，即接收应用功能实体发送的能力调用请求，基于该能力调用请求向接入网侧发送无线网络信息的订阅请求，并将接入网侧反馈的无线网络信息通知给应用功能实体，由于轻量级网络开放功能实体可以部署在距离边缘计算平台较近的位置，因此可以降低应用功能实体获取订阅的无线网络信息的时延，也即降低了网络信息开放的时延，进而可以满足边缘计算平台中的应用功能实体对网络信息的时延要求。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1示出了相关技术中的网络能力开放架构的示意图；
图2示出了可以应用本申请实施例的技术方案的示例性系统架构的示意图；
图3示出了可以应用本申请实施例的技术方案的另一种示例性系统架构的示意图；
图4示出了根据本申请的一个实施例的应用于边缘计算场景的通信方法的流程图；
图5示出了根据本申请的一个实施例的应用于边缘计算场景的通信方法的流程图；
图6示出了在图2所示的系统架构下各设备之间的交互流程图；
图7示出了在图3所示的系统架构下各设备之间的交互流程图；
图8示出了根据本申请的一个实施例的应用于边缘计算场景的通信装置的框图；
图9示出了根据本申请的一个实施例的应用于边缘计算场景的通信装置的框图；
图10示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本申请将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，提供许多具体细节从而给出对本申请的实施例的充分理解。然而，本领域技术人员将意识到，可以实践本申请的技术方案而没有特定细节中的一个或更多，或者可以采用其它的方法、装置、步骤等。在其它情况下，不详细示出或描述公知方法、装置、实现或者操作以避免模糊本申请的各方面。
附图中所示的方框图仅仅是功能实体，不一定必须与物理上独立的实体相对应。即，可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
附图中所示的流程图仅是示例性说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解，而有的操作/步骤可以合并或部分合并，因此实际执行的顺序有可能根据实际情况改变。
在移动应用场景中，为了保证应用功能的使用体验，对于某些网络信息，例如，网络拥塞条件，实时的用户面时延等，需要实时的开放给应用功能(Application Function，简称AF)，以使得AF能够根据这些网络信息进行相应的应用层处理，例如，调整视频的分辨率、改变自动驾驶的等级等。
示例性的，图1示出了相关技术中的网络能力开放架构的示意图。如图1所示，在信任域中，网络开放功能实体(Network Exposure Function，简称NEF)的应用程序接口，即API1、API2、API3、……APIn，通过接口N33与应用功能(AF)交互，获取AF的能力调用请求，并按照能力调用 请求将相应的网络信息开发给AF。NEF通过服务化接口与核心网控制面的各个其他网络功能(Network Function，NF)，即NF1、NF2、……、NFn来进行交互，从而获取AF所需要的特定的网络信息。然而，在该架构中，虽然通过NEF将网络信息开放给AF，但是，AF部署在多接入边缘计算(Multi-access Edge Computing，简称MEC)平台上，而MEC平台一般都部署在靠近核心基站的位置，而NEF的部署位置通常位于运行商的核心机房，即NEF的位置与MEC平台较远，从而会使得网络信息的时延较长。
然而，网络信息调度的时延较长，会使得该网络信息无效，从而会影响后续应用层的处理、优化方案，例如，影响视频分辨率的调整、自动驾驶的等级变更等。由此可见，MEC部署在与更加靠近终端的位置，即远离运营商核心机房的位置，会使得网络信息开发的时延增大，进而影响后续应用层的处理，如何能够保证网络信息开发的时延是亟待解决的技术问题。
综上，本领域技术人员未对网络信息开放的实现过程进行分析，且上述技术问题对于本领域技术来说并不是公知常识，因此，本领域技术人员难以发现并提出上述技术问题。而本申请实施例，针对网络信息开发的过程进行了分析，从而发现上述技术问题。
本申请实施例提供了一种通信方法、装置、计算机可读存储介质及电子设备，能够降低网络信息开放时的时延。
图2示出了可以应用本申请实施例的技术方案的示例性系统架构的示意图。
如图2所示，系统架构可以包括用户设备(如图2中所示的用户设备1和用户设备2，其中，用户设备(User Equipment，简称UE)可以是智能手机、平板电脑、便携式计算机、台式计算机、智能手表等等)、基站(如图2中所示的基站1和基站2)、用户面功能实体(User Plane Function，简称UPF)、边缘计算平台(MEC)、应用功能实体(AF)、轻量级网络开放功能实体(Network Exposure Function-lite，简称NEF-lite)、核心网络开放功能实体(Network Exposure Function-central，简称NEF-central)和操作维护管理(Operation Administration and Maintenance，简称OAM)系统。其中，基站(如图2中所示的基站1和基站2)与UPF之间通过N3接口相连，UPF与边缘计算平台之间通过N6接口相连，AF部署在MEC平台上，NEF-lite与OAM系统、AF和NEF-lite相连，NEF-lite和NEF-central相连。
在本申请的一个实施例中，图2中所示的UPF可以是具备上行链路分类器(Uplink Classifier，简称ULCL)功能的I-UPF(Intermediate UPF，源中间UPF)，也可以是锚点的UPF。NEF-lite可以部署在MEC的位置附近，或者与MEC部署在同一个机房内，NEF-lite用于实现对MEC平台的能力开放，主要开放的场景是为MEC平台服务的基站的无线信息的开放。在图2所示的系统架构中，NEF-lite与基站没有直接的接口，而是通过与基站的OAM系统连接来获取基站侧的无线信息，这种方式可以减少对基站功 能以及现有网络架构的影响。NEF-lite与NEF-central之间的相连可以实现从核心网控制面的能力对MEC平台的开放，即：NEF-lite在接收到MEC平台上的AF发送的能力调用请求后，会根据请求中包含的事件标识判断是否和无线侧的能力有关(比如是否是用于请求获取无线网络信息的)，在与无线侧能力无关的情况下，则将该请求转发给NEF-central，NEF-central对该请求进行鉴权和授权，在接受该订阅请求的情况下，则会根据订阅请求，应用现有的能力开放流程获取对应的能力信息，并发送相应的通知消息给NEF-lite，并由NEF-lite转发给AF；另外NEF-lite可以与核心网控制面的其他NF(Network Function，网络功能)实体没有直接接口，只与NEF-central相连，并且NEF-lite也可以调用NEF-central的能力，实现对AF请求的鉴权和授权。
应该理解，图2中所示的各个设备的数目仅仅是示意性的。根据实现需要，可以具有任意数目的用户设备、基站、UPF、AF等。
在本申请的一些实施例中，AF可以向NEF-lite发送能力调用请求，该能力调用请求可以包括事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU(Protocol Data Unit，协议数据单元)会话信息、目标小区信息、目标位置区域、目标时间段等)、AF信息(如AF的地址信息等)等。NEF-lite在接收到该能力调用请求之后，可以基于该能力调用请求对AF进行授权验证。在NEF-lite不能实现对AF的授权验证的情况下，比如NEF-lite不具备对AF进行授权验证的能力，或者AF的签约信息没有导入到NEF-lite，那么NEF-lite也无法完成对应用功能实体的身份授权验证，则可以将该能力调用请求发送至NEF-central，由NEF-central实现对AF的授权验证，并返回结果给NEF-lite。
在对AF的授权验证通过之后，NEF-lite可以根据该能力调用请求向OAM发送订阅请求。OAM在接收到该订阅请求之后，可以确定是否接受该订阅请求，在不接受该订阅请求的情况下，可以反馈拒绝订阅的响应消息及拒绝订阅的原因给AF；在OAM接受该订阅请求的情况下，则可以反馈同意订阅的响应信息。NEF-lite在接收到该响应信息之后，可以转发给AF。
在本申请的一些实施例中，OAM与基站具有连接，会接收基站上报的无线侧信息，该无线侧信息可以是周期性上报的信息，也可以是特殊事件触发的上报信息。在根据订阅请求监测到相应的无线网络信息之后，可以将监测到的无线网络信息发送给NEF-lite，进而由NEF-lite转发给AF。
在本申请的一些实施例中，OAM在接收到NEF-lite发送的订阅请求之后，也可以将该订阅请求发送给目标基站，目标基站在接收到该订阅请求之后，可以确定是否接受该订阅请求，在不接受该订阅请求的情况下，可以反馈拒绝订阅的响应消息及拒绝订阅的原因；在目标基站接受该订阅请 求的情况下，则可以反馈同意订阅的响应信息。OAM在接收到该响应信息之后，可以转发给NEF-lite，然后由NEF-lite转发给AF。
在本申请的一些实施例中，上下文中所述的无线网络信息可以是无线网络拥塞指示、服务质量(Quality of Service，QoS)拥塞指示、QoS测量报告等。
图3示出了可以应用本申请实施例的技术方案的另一种示例性系统架构的示意图。如图3所示，系统架构中包括用户设备(如图3所示的用户设备1和用户设备2)、基站(如图3中所示的基站1和基站2)、用户面功能实体(UPF)、边缘计算平台(MEC)、应用功能实体(AF)、轻量级网络开放功能实体(NEF-lite)和核心网络开放功能实体(NEF-central)。其中，基站(如图3所示的基站1和基站2)与UPF之间通过N3接口相连，UPF与MEC平台之间通过N6接口相连，AF部署在MEC平台上，AF与NEF-lite相连，NEF-lite与NEF-central相连。在图3所示的系统架构中，NEF-lite直接与基站相连，无需经过操作维护管理系统，即OAM系统，因此可以进一步降低信息传输的时延。在本申请的一些实施例中，NEF-lite在接收到AF发送的能力调用请求之后，可以基于该能力调用请求对AF进行授权验证。在NEF-lite不能实现对AF的授权验证的情况下，比如NEF-lite不具备对AF进行授权验证的能力，或者AF的签约信息没有导入到NEF-lite，那么NEF-lite也无法完成对AF的身份授权验证，则可以将该能力调用请求发送至NEF-central，由NEF-central实现对AF的授权验证。
在对AF的授权验证通过之后，NEF-lite可以根据该能力调用请求向基站发送订阅请求。基站在接收到该订阅请求之后，可以确定是否接受该订阅请求，在不接受该订阅请求的情况下，可以向NEF-lite反馈拒绝订阅的响应消息及拒绝订阅的原因；在基站接受该订阅请求的情况下，则可以向NEF-lite反馈同意订阅的响应信息。NEF-lite在接收到该响应信息之后，可以转发给AF。
在本申请的一些实施例中，基站在根据订阅请求监测到相应的无线网络信息之后，可以将监测到的无线网络信息发送给NEF-lite，进而由NEF-lite转发给AF。
在图2和图3所示的系统架构中，由于NEF-lite部署在距离MEC平台较近的位置，因此可以降低AF获取订阅的无线网络信息的时延，也即降低了网络信息开放的时延，进而可以满足MEC平台中的AF对网络信息的时延要求。
以下对本申请实施例的技术方案的实现细节进行详细阐述：
图4示出了根据本申请实施例的应用于边缘计算场景的通信方法的流程图，该边缘计算场景可以是图2或图3所示的边缘计算场景。该应用于边缘计算场景的通信方法可以由图2或图3中所示的NEF-lite，即轻量级网络开放功能实体来执行。参照图4所示，该应用于边缘计算场景的通信方 法至少包括步骤S410至步骤S440，详细介绍如下：
在步骤S410中，轻量级网络开放功能实体接收应用功能实体发送的能力调用请求。
在本申请的实施例中，应用功能实体可以生成能力调用请求，并通过网络向轻量级开放功能实体发送生成的能力调用请求。能力调用请求可以包括事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息、目标小区信息、目标位置区域、目标时间段等)、AF信息(如AF的地址信息等)等。
在步骤S420中，在该能力调用请求用于请求获取无线网络信息的情况下，则轻量级网络开放功能实体基于该能力调用请求向接入网侧发送无线网络信息的订阅请求。
在本申请的实施例中，在接收到应用功能实体发送的能力调用请求之后，轻量级网络开放功能实体可以根据能力调用请求中包含的事件标识，确定该能力调用请求是否是用于请求获取无线网络信息的。比如，在该事件标识为第一值的情况下，则确定是用于请求获取无线网络信息的；在该事件标识为第二值的情况下，则确定不是用于请求获取无线网络信息的。第一值和第二值都可以根据实际情况进行设置。在本申请的一些实施例中，在该能力调用请求不是用于请求获取无线网络信息的情况下，则轻量级网络开放功能实体可以将该能力调用请求转发给NEF-central，即转发给核心网络开放功能实体，由核心网络开放功能实体对该请求进行鉴权和授权，核心网络开放功能实体在接受该订阅请求的情况下，则会根据订阅请求应用现有的能力开放流程获取对应的能力信息，并发送相应的通知消息给轻量级网络开放功能实体，并由轻量级网络开放功能实体转发给应用功能实体。
在本申请的一个实施例中，轻量级网络开放功能实体可以根据能力调用请求，对应用功能实体的身份进行授权验证，在对应用功能实体的身份授权验证通过的情况下，再根据该能力调用请求向接入网侧发送订阅请求。在本申请的一些实施例中，轻量级网络开放功能实体可以事先获取应用功能实体的数字证书，进而轻量级网络开放功能实体可以基于应用功能实体的数字证书来对其身份进行授权验证。
在本申请的一些实施例中，在轻量级网络开放功能实体无法完成对应用功能实体的身份授权验证的情况下，则可以将能力调用请求发送给核心网络开放功能实体，以使核心网络开放功能实体对应用功能实体的身份进行授权验证，进而轻量级网络开放功能实体可以根据核心网络开放功能实体对应用功能实体的身份授权验证结果来确定是否对应用功能实体的身份授权验证通过。在对应用功能实体的身份授权验证通过的情况下，则可以根据该能力调用请求向接入网侧发送订阅请求。在一些实施例中，如果N 轻量级网络开放功能实体不具备对功能实体进行授权验证处理的能力，而是将授权验证的功能放在核心网络开放功能实体侧进行处理，那么可以确定轻量级网络开放功能实体无法完成对应用功能实体的身份授权验证；或者如果应用功能实体的签约信息没有导入到轻量级网络开放功能实体，那么轻量级网络开放功能实体也无法完成对应用功能实体的身份授权验证。
在本申请的一些实施例中，轻量级网络开放功能实体根据能力调用请求向接入网侧发送订阅请求的过程具体可以是：根据该能力调用请求中包含的地址指示信息，确定与该订阅请求相对应的至少一个目标基站的信息，然后基于至少一个目标基站的信息，向该至少一个目标基站或该至少一个目标基站的操作维护管理系统发送订阅请求。也即，轻量级网络开放实体功能先是依据能力调用请求中的地址指示信息中，解析出一个或多个目标基站的信息，并依据一个或多个目标基站的信息，确定出一个或多个目标基站，然后将订阅请求发送给这一个或多个目标基站的操作维护管理系统。
在本申请的一些实施例中，该地址指示信息包括以下至少之一：应用功能实体的地址信息、目标小区的信息、目标位置区域信息。比如可以根据应用功能实体的地址信息确定边缘计算平台的位置，然后将处于该边缘计算平台所在位置附近的基站作为与该订阅请求相对应的目标基站；或者可以根据目标小区的信息，将形成该目标小区的基站作为与该订阅请求相对应的目标基站；或者可以根据目标位置区域信息，将信号覆盖范围包含该目标位置区域的基站作为与该订阅请求相对应的目标基站。
需要说明的是，如果该地址指示信息包括应用功能实体的地址信息、目标小区的信息、目标位置区域信息中的至少两个，那么可以先根据这至少两个信息分别确定出候选基站，然后再从候选基站中确定目标基站，比如可以将所有的候选基站作为目标基站，或者是从候选基站中选择出性能较好的目标基站。
在本申请的一些实施例中，在图2所示的系统架构的情况下，即接入网侧包括基站及与基站相连的操作维护管理系统，轻量级网络开放功能实体与基站的操作维护管理系统相连的情况下，那么轻量级网络开放功能实体可以基于能力调用请求向该操作维护管理系统发送订阅请求，然后由操作维护管理系统来确定是否接受该订阅请求；当然，操作维护管理系统在接收到该订阅请求之后，也可以将该订阅请求转发给基站，然后由基站来确定是否接受该订阅请求。在图3所示的系统架构的情况下，即接入网侧包括基站，轻量级网络开放功能实体连接至基站的情况下，那么轻量级网络开放功能实体可以基于能力调用请求直接向基站发送订阅请求。
在本申请的一些实施例中，在轻量级网络开放功能实体接收接入网侧针对订阅请求反馈的无线网络信息之前，轻量级网络开放功能实体在向接入网侧发送订阅请求之后，可以接收接入网侧反馈的订阅响应，该订阅响应用于指示接入网侧是否接受订阅请求。然后，轻量级网络开放功能实体 将该订阅响应反馈给应用功能实体。在一些实施例中，在该订阅响应指示接入网侧拒绝订阅请求的情况下，则轻量级网络开放功能实体可以根据订阅响应向应用功能实体反馈拒绝原因信息；在该订阅响应指示接入网侧接受订阅请求的情况下，则轻量级网络开放功能实体可以检测是否接收到接入网侧针对订阅请求反馈的无线网络信息。
需要说明的是：在是由目标基站来响应订阅请求的情况下，那么当订阅请求发送到的所有目标基站都拒绝接受该订阅请求时，则可以确定接入网侧拒绝该订阅请求；而在有至少一个目标基站接受该订阅请求的情况下，那么可以确定接入网侧接受该订阅请求。在是由操作维护管理系统来响应该订阅请求，那么操作维护管理系统可以根据事先的配置文件确定是否需要接受该订阅请求。
继续参照图4所示，在步骤S430中，轻量级网络开放功能实体接收接入网侧针对订阅请求反馈的无线网络信息。
在此情况下，接入网侧在接收到订阅请求反馈之后，就会生成与其对应的无线网络信息，然后通过网络将无线网络信息发送给轻量级网络开放功能实体。
在本申请的一些实施例中，在图2所示的系统架构的情况下，即轻量级网络开放功能实体与基站的操作维护管理系统相连，那么轻量级网络开放功能实体可以接收操作维护管理系统发送的无线网络信息，该无线网络信息可以是由基站根据操作维护管理系统转发的订阅请求监测到的符合该订阅请求、并传输给操作维护管理系统的无线网络信息；或者也可以是由操作维护管理系统根据基站上报的信息监测到的符合该订阅请求的无线网络信息。在图3所示的系统架构的情况下，即轻量级网络开放功能实体与基站直接相连，那么轻量级网络开放功能实体可以直接接收基站针对订阅请求反馈的无线网络信息。
在步骤S440中，轻量级网络开放功能实体将无线网络信息通知给应用功能实体。
在此情况下，轻量级网络开放功能实体会通过网络，将无线网络信息发送给应用功能实体，应用功能实体接收无线网络信息。
在本申请的一些实施例中，轻量级网络开放功能实体将无线网络信息通知给应用功能实体之后，应用功能实体可以基于该无线网络信息进行应用层的处理。
在本申请的一些实施例中，轻量级网络开放功能实体也可以统计应用功能实体请求获取的无线网络信息，如调用次数等，得到统计结果，然后将统计结果上报至核心网络开放功能实体。
图4所示实施例的技术方案是从轻量级网络开放功能实体的角度来阐述本申请实施例的通信方法的实现细节，以下结合图5从基站或基站的操作维护管理系统的角度对本申请实施例的通信方法的实现细节进行详细说 明：
图5示出了根据本申请的一个实施例的应用于边缘计算场景的通信方法的流程图，该边缘计算场景可以是图2或图3所示的边缘计算场景。该应用于边缘计算场景的通信方法可以由图2或图3中所示的任一基站(如基站1或基站2)来执行，或者可以由图2中所示的操作维护管理系统来执行。参照图5所示，该应用于边缘计算场景的通信方法至少包括步骤S510至步骤S530，详细介绍如下：
在步骤S510中，基站或基站的操作维护管理系统获取轻量级网络开放功能实体发送的无线网络信息的订阅请求，该订阅请求是轻量级网络开放功能实体根据应用功能实体发送的能力调用请求所发送的。
在本申请的一些实施例中，在图2所示的系统架构的情况下，即轻量级网络开放功能实体与基站的操作维护管理系统相连，那么在图5所示的通信方法由基站的操作维护管理系统来执行的情况下，操作维护管理系统可以接收来自于轻量级网络开放功能实体的订阅请求；在图5所示的通信方法由基站来执行的情况下，基站可以接收操作维护管理系统转发的来自于轻量级网络开放功能实体的订阅请求。在图3所示的系统架构的情况下，即轻量级网络开放功能实体与基站直接相连，那么基站可以直接接收轻量级网络开放功能实体发送的订阅请求。
在步骤S520中，基站或基站的操作维护管理系统根据订阅请求监测无线网络信息。
在本申请的一些实施例中，基站或基站的操作维护管理系统在根据该订阅请求监测无线网络信息之前，可以先根据该订阅请求中所包含的信息确定是否接受该订阅请求，在确定接受该订阅请求的情况下，再根据该订阅请求监测无线网络信息，并向轻量级网络开放功能实体返回接受通知消息；在确定需要拒绝该订阅请求的情况下，则可以向轻量级网络开放功能实体发送拒绝通知消息。在本申请的一些实施例中，该拒绝通知消息中可以包含有相应的拒绝原因。
在本申请的一些实施例中，基站或基站的操作维护管理系统在根据订阅请求中所包含的终端的标识，确定该终端并未接入基站的情况下，则可以拒绝该订阅请求；基站或基站的操作维护管理系统在根据订阅请求中所包含的终端的标识确定终端已接入基站的情况下，则可以接受该订阅请求。
在步骤S530中，在基站或基站的操作维护管理系统监测到符合订阅请求的无线网络信息的情况下，则将无线网络信息发送给轻量级网络开放功能实体，以使轻量级网络开放功能实体将无线网络信息反馈给应用功能实体。
在本申请的一些实施例中，在图2所示的系统架构的情况下，即轻量级网络开放功能实体与基站的操作维护管理系统相连，那么在图5所示的通信方法由操作维护管理执行的情况下，操作维护管理系统会根据基站上 报的无线侧信息以及订阅请求，将符合订阅请求的无线网络信息发送给轻量级网络开放功能实体；在图5所示的通信方法由基站执行的情况下，基站可以根据订阅请求及检测到的无线侧信息，将符合订阅请求的无线网络信息发送给操作维护管理系统，然后由操作维护管理系统转发给轻量级网络开放功能实体。在图3所示的系统架构的情况下，即轻量级网络开放功能实体与基站直接相连，那么基站可以直接将无线网络信息发送给轻量级网络开放功能实体。
图4和图5分别是从轻量级网络开放功能实体和基站的角度对本申请实施例的技术方案进行了阐述，以下结合图2和图3所示的系统架构，对本申请实施例中涉及到的各个设备之间的交互过程进行详细说明：
在本申请的一些实施例中，在图2所示的系统架构，即轻量级网络开放功能实体与基站的操作维护管理系统相连的应用场景中，各设备之间的交互过程如图6所示，包括如下步骤：
步骤S601，应用功能实体(AF)向轻量级网络开放功能实体(NEF-lite)发送能力调用请求。在本申请的一些实施例中，该能力调用请求可以包括事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息、目标小区信息、目标位置区域、目标时间段等)、AF信息(如AF的地址信息等)等。
步骤S602a，轻量级网络开放功能实体(NEF-lite)接收到该能力调用请求之后，对能力调用请求进行处理。在一些实施例中，轻量级网络开放功能实体可以对该请求进行授权验证，在授权验证通过的情况下，轻量级网络开放功能实体则会进行进一步处理，比如将能力调用请求中包含的用户设备(UE)的外部ID转化为内部ID，将用户设备(UE)的外部组标识转化为内部组标识，根据应用功能实体(AF)位于的边缘计算平台(MEC)的位置信息确定为对应的1个或多个基站的信息，将这些信息作为目标基站。
在本申请的一些实施例中，在NEF-lite不能完成对该能力调用请求的授权的情况下，则可以执行步骤S602b，即轻量级网络开放功能实体将该能力调用请求发送给核心网络开放功能实体(NEF-central)，然后由NEF-central完成对该能力调用请求的鉴权和授权，并返回结果给NEF-lite，以向NEF-lite指示是否接受该能力调用请求。
需要说明的是，不管是由NEF-lite进行授权验证，还是由NEF-central进行授权验证，在确定需要拒绝该能力调用请求的情况下，则都可以向AF返回相应的原因值。同时，在AF的能力调用请求被拒绝的情况下，则直接向AF反馈能力调用响应，该能力调用响应包含了拒绝信息及相应的拒绝原因。
步骤S603，轻量级网络开放功能实体(NEF-lite)根据应用功能实体(A F)发送的能力调用请求，向操作维护管理(OAM)系统发送无线信息的订阅请求。该订阅请求中可以包含事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息、目标小区信息、目标基站、目标时间段等)等。
步骤S604，OAM系统接收到NEF-lite发送的订阅请求之后，向目标基站发送无线信息的订阅请求。该订阅请求中包含事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息，目标小区信息、目标时间段等)等。
步骤S605，目标基站向OAM系统返回订阅响应消息，指示该订阅请求是否被接受。在目标基站检测到目标UE没有接入到该基站上的情况下，则会拒绝该订阅请求。在一些实施例中，在基站拒绝该订阅请求的情况下，则可以在订阅响应消息中反馈拒绝的原因。
需要说明的是，步骤S604和S605为可选步骤，在一些实施例中，在OAM系统可以确定是否接受该订阅请求的情况下，那么OAM系统可以直接确定是否要接受该订阅请求，并将无线信息订阅响应发送给NEF-lite。
步骤S606，OAM系统接收到订阅请求并响应之后(适用于OAM确定是否接受该订阅请求的场景)，或者在接收到步骤S605中目标基站返回的订阅响应消息之后(适用于由基站确定是否接受该订阅请求的场景)，向NEF-lite返回订阅响应消息，以指示该订阅请求是否被接受。在一些实施例中，在OAM拒绝该订阅请求的情况下，则可以返回相应的原因。
步骤S607，NEF-lite在接收到该订阅响应消息之后，返回订阅响应消息给AF，以指示是否接受该订阅请求。在一些实施例中，在NEF-lite拒绝该订阅请求的情况下，则可以向AF返回相应的原因。
在之前执行了步骤S604和S605的情况下，则需执行步骤S608，在之前没有执行步骤S604和S605的情况下，则不执行步骤S608，直接执行步骤S609。
步骤S608，目标基站检测到满足事件上报条件时，会发送事件通知消息给OAM系统。
步骤S609，OAM系统检测无线信息是否符合事件订阅请求中的要求，在符合的情况下，则发送事件通知消息给NEF-lite。
步骤S610，NEF-lite发送事件通知消息给AF。
步骤S611，NEF-lite可以将事件调用的统计信息上报给NEF-central。该步骤为可选步骤，并非一定要上传事件调用的统计信息。
在本申请的一些实施例中，在图3所示的系统架构，即轻量级网络开放功能实体与基站直接相连的应用场景中，各设备之间的交互过程如图7所示，包括如下步骤：
步骤S701，应用功能实体(AF)向轻量级网络开放功能实体(NEF-lite)发送能力调用请求。在本申请的一些实施例中，该能力调用请求可以包括事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息、目标小区信息、目标位置区域、目标时间段等)、AF信息(如AF的地址信息等)等。
步骤S702a，NEF-lite接收到该能力调用请求之后，对能力调用请求进行处理。在本申请中，NEF-lite可以对该请求进行授权验证，在授权验证通过的情况下，则会进行进一步处理，比如将能力调用请求中包含的用户设备(UE)的外部ID转化为内部ID，将UE的外部组标识转化为内部组标识，根据AF位于的MEC的位置信息确定为对应的1个或多个基站的信息，将这些信息作为目标基站。
在本申请的一些实施例中，在NEF-lite不能完成对该能力调用请求的授权的情况下，则可以执行步骤S702b，即将该能力调用请求发送给核心网络开放功能实体(NEF-central)，然后由NEF-central完成对该能力调用请求的鉴权和授权，并返回结果给NEF-lite，以向NEF-lite指示是否接受该能力调用请求。
需要说明的是，不管是由NEF-lite进行授权验证，还是由NEF-central进行授权验证，在确定需要拒绝该能力调用请求的情况下，则都可以向AF返回相应的原因值。同时，在AF的能力调用请求被拒绝的情况下，则直接执行步骤S705，即向AF反馈能力调用响应，该能力调用响应包含了拒绝信息及相应的拒绝原因。
步骤S703，NEF-lite根据AF发送的能力调用请求，向目标基站发送无线信息的订阅请求。该订阅请求中可以包含事件标识(比如需要获取的无线网络信息等)、事件过滤信息(比如信号门限值)、事件上报信息(比如最大上报次数、最小上报时间间隔等)、目标信息(如目标UE标识、目标UE组标识、PDU会话信息、目标小区信息、目标时间段等)
步骤S704，目标基站向NEF-lite返回订阅响应消息，指示该订阅请求是否被接受。在目标基站检测到目标UE没有接入到该基站上的情况下，则会拒绝该订阅请求。在一些实施例中，在目标基站拒绝该订阅请求的情况下，则可以在订阅响应消息中反馈拒绝的原因。
步骤S705，NEF-lite在接收到该订阅响应消息之后，返回响应消息给AF，以指示是否接受该订阅请求。在本申请的一些实施例中，在所有目标基站都拒绝该订阅请求的情况下，则可以返回拒绝订阅请求的响应消息并包含相应的原因给AF，比如特定的原因值。在至少有一个目标基站接受了该订阅请求，则返回接受订阅请求的响应消息给AF。
步骤706，目标基站检测到满足事件上报条件时，会发送事件通知消息给NEF-lite。
步骤S707，NEF-lite查看该通知消息是否符合事件上报信息中的要求，在符合的情况下，则发送事件通知消息给AF。
步骤S708，NEF-lite可以将事件调用的统计信息上报给NEF-central。该步骤为可选步骤，并非一定要上传事件调用的统计信息。
图7所示实施例的技术方案由于轻量级网络开放功能实体，即NEF-lite是与基站直接交互，因此可以进一步缩短能力开放的时延。
本申请上述实施例的技术方案通过引入轻量级网络开放功能实体，并将其部署在距离边缘计算平台较近的位置，因此可以降低应用功能实体获取订阅的无线网络信息的时延，也即降低了网络信息开放的时延，进而可以满足边缘计算平台中的应用功能实体对网络信息的时延要求。
以下介绍本申请的装置实施例，可以用于执行本申请上述实施例中的应用于边缘计算场景的通信方法。对于本申请装置实施例中未披露的细节，请参照本申请上述的应用于边缘计算场景的通信方法的实施例。
图8示出了根据本申请的一些实施例的应用于边缘计算场景的通信装置的框图，该边缘计算场景可以是图2或图3所示的边缘计算场景，该通信装置设置于轻量级网络开放功能实体内。
参照图8所示，根据本申请的一个实施例的应用于边缘计算场景的通信装置800，包括：第一接收单元802、第一发送单元804、第二接收单元806和第二发送单元808。
其中，第一接收单元802配置为接收所述应用功能实体发送的能力调用请求；第一发送单元804配置为在所述能力调用请求用于请求获取无线网络信息的情况下，基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求；第二接收单元806配置为接收所述接入网侧针对所述订阅请求反馈的无线网络信息；第二发送单元808配置为将所述无线网络信息通知给所述应用功能实体。
在本申请的一些实施例中，基于前述方案，第一发送单元804配置为：根据所述能力调用请求，对所述应用功能实体的身份进行授权验证；在对所述应用功能实体的身份授权验证通过的情况下，则根据所述能力调用请求向接入网侧发送所述订阅请求。
在本申请的一些实施例中，基于前述方案，第一发送单元804还配置为：在所述轻量级网络开放功能实体无法完成对所述应用功能实体的身份授权验证的情况下，则将所述能力调用请求发送给所述核心网络开放功能实体，以使所述核心网络开放功能实体对所述应用功能实体的身份进行授权验证；接收所述核心网络开放功能实体对所述应用功能实体的身份授权验证结果；在所述核心网络开放功能实体对所述应用功能实体的身份授权验证通过的情况下，则根据所述能力调用请求向接入网侧发送所述订阅请求。
在本申请的一些实施例中，基于前述方案，第一发送单元804配置为： 根据所述能力调用请求中包含的地址指示信息，确定与所述订阅请求相对应的至少一个目标基站的信息，所述地址指示信息包括以下至少之一：所述应用功能实体的地址信息、目标小区的信息、目标位置区域信息；基于所述至少一个目标基站的信息，向所述至少一个目标基站或所述至少一个目标基站的操作维护管理系统发送所述订阅请求。
在本申请的一些实施例中，基于前述方案，第二接收单元806还配置为：在接收所述接入网侧针对所述订阅请求反馈的无线网络信息之前，接收所述接入网侧反馈的订阅响应，所述订阅响应用于指示所述接入网侧是否接受所述订阅请求；第二发送单元808还配置为：将所述订阅响应反馈给所述应用功能实体。
在本申请的一些实施例中，基于前述方案，第二发送单元808还配置为：在所述订阅响应指示所述接入网侧拒绝所述订阅请求的情况下，则根据所述订阅响应向所述应用功能实体反馈拒绝原因信息；所述应用于边缘计算场景的通信装置800还包括：检测单元，配置为在所述订阅响应指示所述接入网侧接受所述订阅请求的情况下，检测是否接收到所述接入网侧针对所述订阅请求反馈的无线网络信息。
在本申请的一些实施例中，基于前述方案，所述接入网侧包括基站及与所述基站相连的操作维护管理系统，所述轻量级网络开放功能实体连接至所述操作维护管理系统；第一发送单元804配置为基于所述能力调用请求向所述操作维护管理系统发送所述订阅请求；第二接收单元806配置为接收所述操作维护管理系统发送的无线网络信息。
在本申请的一些实施例中，基于前述方案，所述接入网侧包括基站，所述轻量级网络开放功能实体连接至所述基站；第一发送单元804配置为基于所述能力调用请求向所述基站发送所述订阅请求；第二接收单元806配置为接收所述基站针对所述订阅请求反馈的无线网络信息。
在本申请的一些实施例中，基于前述方案，所述的应用于边缘计算场景的通信装置800还包括：统计单元，配置为统计所述应用功能实体请求获取的无线网络信息，得到统计结果；第二发送单元808还配置为将所述统计结果上报至所述核心网络开放功能实体。
在本申请的一些实施例中，基于前述方案，第一接收单元802还配置为在接收到所述应用功能实体发送的能力调用请求之后，根据所述能力调用请求中包含的事件标识，确定所述能力调用请求是否是用于请求获取无线网络信息；第一发送单元804还配置为在所述能力调用请求不是用于请求获取无线网络信息的情况下，将所述能力调用请求转发至所述核心网络开放功能实体。
图9示出了根据本申请的一些实施例的应用于边缘计算场景的通信装置的框图，该边缘计算场景可以是图2或图3所示的边缘计算场景，该通信装置设置于基站内或设置于基站的操作维护管理系统内。
参照图9所示，根据本申请的一些实施例的应用于边缘计算场景的通信装置900，包括：获取单元902、监测单元904和发送单元906。
其中，获取单元902配置为获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，所述订阅请求是所述轻量级网络开放功能实体根据所述应用功能实体发送的能力调用请求发送的；监测单元904配置为根据所述订阅请求监测无线网络信息；发送单元906配置为在监测到符合所述订阅请求的无线网络信息的情况下，将所述无线网络信息发送给所述轻量级网络开放功能实体，以使所述轻量级网络开放功能实体将所述无线网络信息反馈给所述应用功能实体。
在本申请的一些实施例中，基于前述方案，所述的应用于边缘计算场景的通信装置900还包括：确定单元，配置为根据所述订阅请求中所包含的信息确定是否接受所述订阅请求；监测单元904还配置为：在所述确定单元确定接受所述订阅请求的情况下，根据所述订阅请求监测无线网络信息，并向所述轻量级网络开放功能实体发送接受通知消息；发送单元906还配置为：在所述确定单元确定需要拒绝所述订阅请求的情况下，向所述轻量级网络开放功能实体发送拒绝通知消息。
在本申请的一些实施例中，基于前述方案，所述确定单元配置为：在根据所述订阅请求中所包含的终端的标识，确定所述终端并未接入所述基站的情况下，则确定需要拒绝所述订阅请求；在根据所述订阅请求中所包含的终端的标识，确定所述终端已接入所述基站的情况下，则确定接受所述订阅请求。
在本申请的一些实施例中，基于前述方案，在所述基站与所述轻量级网络开放功能实体相连的情况下，获取单元902配置为：接收所述轻量级网络开放功能实体发送的所述订阅请求。
在本申请的一些实施例中，基于前述方案，在所述基站的操作维护管理系统与所述轻量级网络开放功能实体相连、且所述通信装置900设置于所述基站内的情况下，获取单元902配置为：接收所述操作维护管理系统转发的来自于所述轻量级网络开放功能实体的所述订阅请求。
在本申请的一些实施例中，基于前述方案，在所述基站的操作维护管理系统与所述轻量级网络开放功能实体相连、且所述通信装置900设置于所述基站的操作维护管理系统内的情况下，获取单元902配置为：接收所述轻量级网络开放功能实体发送的所述订阅请求。
图10示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
需要说明的是，图10示出的电子设备的计算机系统仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图10所示，计算机系统包括中央处理单元(Central Processing Unit，CPU)1001，其可以根据存储在只读存储器(Read-Only Memory，RO M)1002中的程序或者从存储部分1008加载到随机访问存储器(Random Access Memory，RAM)1003中的程序而执行各种适当的动作和处理，例如执行上述实施例中所述的方法。在RAM 1003中，还存储有系统操作所需的各种程序和数据。CPU 1001、ROM 1002以及RAM 1003通过总线1004彼此相连。输入/输出(Input/Output，I/O)接口1005也连接至总线1004。
以下部件连接至I/O接口1005：包括键盘、鼠标等的输入部分1006；包括诸如阴极射线管(Cathode Ray Tube，CRT)、液晶显示器(Liquid Crystal Display，LCD)等以及扬声器等的输出部分1007；包括硬盘等的存储部分908；以及包括诸如LAN(Local Area Network，局域网)卡、调制解调器等的网络接口卡的通信部分1009。通信部分1009经由诸如因特网的网络执行通信处理。驱动器1010也根据需要连接至I/O接口1005。可拆卸介质1011，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器1010上，以便于从其上读出的计算机程序根据需要被安装入存储部分1008。
特别地，根据本申请的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的计算机程序。在这样的实施例中，该计算机程序可以通过通信部分1009从网络上被下载和安装，和/或从可拆卸介质1011被安装。在该计算机程序被中央处理单元(CPU)1001执行时，执行本申请的系统中限定的各种功能。
需要说明的是，本申请实施例所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的计算机程序。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者 传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的计算机程序可以用任何适当的介质传输，包括但不限于：无线、有线等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。其中，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现，所描述的单元也可以设置在处理器中。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现上述实施例中所述的方法。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本申请实施方式的方法。
本领域技术人员在考虑说明书及实践这里公开的实施方式后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精 确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (18)

  1. 一种应用于边缘计算场景的通信方法，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信方法由所述轻量级网络开放功能实体执行，所述通信方法包括：
    接收所述应用功能实体发送的能力调用请求；
    在所述能力调用请求用于请求获取无线网络信息的情况下，则基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求；
    接收所述接入网侧针对所述订阅请求反馈的无线网络信息；
    将所述无线网络信息通知给所述应用功能实体。
  2. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，所述基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求，包括：
    根据所述能力调用请求，对所述应用功能实体的身份进行授权验证；
    在对所述应用功能实体的身份授权验证通过的情况下，则根据所述能力调用请求向接入网侧发送所述订阅请求。
  3. 根据权利要求2所述的应用于边缘计算场景的通信方法，其中，还包括：
    在无法完成对所述应用功能实体的身份授权验证的情况下，则将所述能力调用请求发送给所述核心网络开放功能实体，以使所述核心网络开放功能实体对所述应用功能实体的身份进行授权验证；
    接收所述核心网络开放功能实体对所述应用功能实体的身份授权验证结果；
    在所述核心网络开放功能实体对所述应用功能实体的身份授权验证通过的情况下，则根据所述能力调用请求向接入网侧发送所述订阅请求。
  4. 根据权利要求2或3所述的应用于边缘计算场景的通信方法，其中，所述根据所述能力调用请求向接入网侧发送所述订阅请求，包括：
    根据所述能力调用请求中包含的地址指示信息，确定与所述订阅请求相对应的至少一个目标基站的信息，所述地址指示信息包括以下至少之一：所述应用功能实体的地址信息、目标小区的信息、目标位置区域信息；
    基于所述至少一个目标基站的信息，向所述至少一个目标基站或所述至少一个目标基站的操作维护管理系统发送所述订阅请求。
  5. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，在所述接收所述接入网侧针对所述订阅请求反馈的无线网络信息之前，所述通信方法还包括：
    在向所述接入网侧发送所述订阅请求之后，接收所述接入网侧反馈的订阅响应，所述订阅响应用于指示所述接入网侧是否接受所述订阅请求；
    将所述订阅响应反馈给所述应用功能实体。
  6. 根据权利要求5所述的应用于边缘计算场景的通信方法，其中，还包括：
    在所述订阅响应指示所述接入网侧拒绝所述订阅请求的情况下，则根据所述订阅响应向所述应用功能实体反馈拒绝原因信息；
    在所述订阅响应指示所述接入网侧接受所述订阅请求的情况下，则检测是否接收到所述接入网侧针对所述订阅请求反馈的无线网络信息。
  7. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，所述接入网侧包括基站及与所述基站相连的操作维护管理系统，所述轻量级网络开放功能实体连接至所述操作维护管理系统；
    所述基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求，包括：基于所述能力调用请求向所述操作维护管理系统发送所述订阅请求；
    所述接收所述接入网侧针对所述订阅请求反馈的无线网络信息，包括：接收所述操作维护管理系统发送的无线网络信息。
  8. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，所述接入网侧包括基站，所述轻量级网络开放功能实体连接至所述基站；
    所述基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求，包括：基于所述能力调用请求向所述基站发送所述订阅请求；
    所述接收所述接入网侧针对所述订阅请求反馈的无线网络信息，包括：接收所述基站针对所述订阅请求反馈的无线网络信息。
  9. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，还包括：
    统计所述应用功能实体请求获取的无线网络信息，得到统计结果；
    将所述统计结果上报至所述核心网络开放功能实体。
  10. 根据权利要求1所述的应用于边缘计算场景的通信方法，其中，还包括：
    在接收到所述应用功能实体发送的能力调用请求之后，根据所述能力调用请求中包含的事件标识，确定所述能力调用请求是否是用于请求获取无线网络信息；
    在所述能力调用请求不是用于请求获取无线网络信息的情况下，则将所述能力调用请求转发至所述核心网络开放功能实体。
  11. 一种应用于边缘计算场景的通信方法，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信方法由所述边缘计算平台所在区域内部署的基站或所述基站的操作维护管理系统执行，所述通信方法包括：
    获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，所述订阅请求是所述轻量级网络开放功能实体根据所述应用功能实体发送的能力调用请求发送的；
    根据所述订阅请求监测无线网络信息；
    在监测到符合所述订阅请求的无线网络信息的情况下，则将所述无线网络信息发送给所述轻量级网络开放功能实体，以使所述轻量级网络开放功能实体将所述无线网络信息反馈给所述应用功能实体。
  12. 根据权利要求11所述的应用于边缘计算场景的通信方法，其中，在所述根据所述订阅请求监测无线网络信息之前，所述通信方法还包括：
    根据所述订阅请求中所包含的信息确定是否接受所述订阅请求；
    在确定接受所述订阅请求的情况下，则根据所述订阅请求监测无线网络信息，并向所述轻量级网络开放功能实体发送接受通知消息；
    在确定需要拒绝所述订阅请求的情况下，则向所述轻量级网络开放功能实体发送拒绝通知消息。
  13. 根据权利要求12所述的应用于边缘计算场景的通信方法，其中，所述根据所述订阅请求中所包含的信息确定是否接受所述订阅请求，包括：
    在根据所述订阅请求中所包含的终端的标识，确定所述终端并未接入所述基站的情况下，则确定需要拒绝所述订阅请求；
    在根据所述订阅请求中所包含的终端的标识，确定所述终端已接入所述基站的情况下，则确定接受所述订阅请求。
  14. 根据权利要求11至13中任一项所述的应用于边缘计算场景的通信方法，其中，
    在所述基站与所述轻量级网络开放功能实体相连的情况下，所述获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，包括：接收所述轻量级网络开放功能实体发送的所述订阅请求；
    在所述基站的操作维护管理系统与所述轻量级网络开放功能实体相连、且所述通信方法由基站执行的情况下，所述获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，包括：接收所述操作维护管理系统转发的来自于所述轻量级网络开放功能实体的所述订阅请求；
    在所述基站的操作维护管理系统与所述轻量级网络开放功能实体相连、且所述通信方法由基站的操作维护管理系统执行的情况下，所述获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，包括：接收所述轻量级网络开放功能实体发送的所述订阅请求。
  15. 一种应用于边缘计算场景的通信装置，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信装置设置于所述轻量级网络开放功能实体内，所述通信装置包括：
    第一接收单元，配置为接收所述应用功能实体发送的能力调用请求，所述能力调用请求用于请求获取无线网络信息；
    第一发送单元，配置为基于所述能力调用请求向接入网侧发送无线网络信息的订阅请求；
    第二接收单元，配置为接收所述接入网侧针对所述订阅请求反馈的无线网络信息；
    第二发送单元，配置为将所述无线网络信息通知给所述应用功能实体。
  16. 一种应用于边缘计算场景的通信装置，所述边缘计算场景中部署有边缘计算平台，所述边缘计算平台部署有应用功能实体，所述边缘计算平台与轻量级网络开放功能实体相连，所述轻量级网络开放功能实体与部署于核心网的核心网络开放功能实体相连，所述通信装置设置于所述边缘计算平台所在区域内部署的基站内或设置于所述基站的操作维护管理系统内，所述通信装置包括：
    获取单元，配置为获取所述轻量级网络开放功能实体发送的无线网络信息的订阅请求，所述订阅请求是所述轻量级网络开放功能实体根据所述应用功能实体发送的能力调用请求发送的；
    监测单元，配置为根据所述订阅请求监测无线网络信息；
    发送单元，配置为在监测到符合所述订阅请求的无线网络信息的情况下，将所述无线网络信息发送给所述轻量级网络开放功能实体，以使所述轻量级网络开放功能实体将所述无线网络信息反馈给所述应用功能实体。
  17. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的应用于边缘计算场景的通信方法，或实现如权利要求11至14中任一项所述的应用于边缘计算场景的通信方法。
  18. 一种电子设备，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1至10中任一项所述的应用于边缘计算场景的通信方法，或实现如权利要求11至14中任一项所述的应用于边缘计算场景的通信方法。
PCT/CN2020/128173 2020-01-07 2020-11-11 通信方法、装置、计算机可读介质及电子设备 WO2021139394A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20911335.6A EP3993485A4 (en) 2020-01-07 2020-11-11 COMMUNICATION METHOD AND APPARATUS, COMPUTER READABLE MEDIUM AND ELECTRONIC DEVICE
US17/585,400 US20220150678A1 (en) 2020-01-07 2022-01-26 Communication method and apparatus, computer-readable medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010014254.4 2020-01-07
CN202010014254.4A CN111182568B (zh) 2020-01-07 2020-01-07 通信方法、装置、计算机可读介质及电子设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/585,400 Continuation US20220150678A1 (en) 2020-01-07 2022-01-26 Communication method and apparatus, computer-readable medium, and electronic device

Publications (1)

Publication Number Publication Date
WO2021139394A1 true WO2021139394A1 (zh) 2021-07-15

Family

ID=70621507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/128173 WO2021139394A1 (zh) 2020-01-07 2020-11-11 通信方法、装置、计算机可读介质及电子设备

Country Status (4)

Country Link
US (1) US20220150678A1 (zh)
EP (1) EP3993485A4 (zh)
CN (2) CN113543177A (zh)
WO (1) WO2021139394A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4236430A4 (en) * 2021-08-06 2024-05-08 Tencent Tech Shenzhen Co Ltd NETWORK INFORMATION OPENING METHOD AND APPARATUS, ELECTRONIC DEVICE AND STORAGE MEDIUM

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021244740A1 (en) * 2020-06-04 2021-12-09 Nokia Technologies Oy Method, apparatus and computer program
CN114158034A (zh) * 2020-09-08 2022-03-08 中国移动通信有限公司研究院 无线接入网能力开放方法、装置及网元
CN112202844B (zh) * 2020-09-10 2022-05-06 中国联合网络通信集团有限公司 一种跨域多接入边缘计算能力开放的方法及设备
CN112437435A (zh) * 2020-12-07 2021-03-02 腾讯科技（深圳）有限公司 一种数据信息获取方法、装置、相关设备及介质
CN113783882B (zh) * 2021-09-16 2023-07-07 恒安嘉新（北京）科技股份公司 一种边缘应用的信息获取方法、装置、电子设备及介质
CN114173429A (zh) * 2021-12-08 2022-03-11 中国联合网络通信集团有限公司 5g专网下无线接入网和边缘计算平台的通信方法及系统
CN114845276B (zh) * 2022-04-19 2023-06-06 广州爱浦路网络技术有限公司 一种网络能力开放的实现方法及平台
WO2024026888A1 (zh) * 2022-08-05 2024-02-08 北京小米移动软件有限公司 一种应用功能的应用方法及装置
WO2024087073A1 (zh) * 2022-10-26 2024-05-02 北京小米移动软件有限公司 基于ai网络功能的处理方法及装置
CN117978740A (zh) * 2022-10-26 2024-05-03 腾讯科技（深圳）有限公司 网络信息开放方法及相关设备
WO2024092379A1 (zh) * 2022-10-31 2024-05-10 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
CN110166929A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种定位操作的方法、装置和系统
US20190357301A1 (en) * 2018-05-16 2019-11-21 Huawei Technologies Co., Ltd. Message and system for application function influence on traffic routing

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109996216B (zh) * 2018-01-02 2022-06-03 中国移动通信有限公司研究院 订阅请求处理方法、网络实体及能力开放平台

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
CN110166929A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种定位操作的方法、装置和系统
US20190357301A1 (en) * 2018-05-16 2019-11-21 Huawei Technologies Co., Ltd. Message and system for application function influence on traffic routing

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3993485A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4236430A4 (en) * 2021-08-06 2024-05-08 Tencent Tech Shenzhen Co Ltd NETWORK INFORMATION OPENING METHOD AND APPARATUS, ELECTRONIC DEVICE AND STORAGE MEDIUM

Also Published As

Publication number Publication date
CN113543177A (zh) 2021-10-22
EP3993485A4 (en) 2022-11-16
US20220150678A1 (en) 2022-05-12
CN111182568B (zh) 2021-08-17
CN111182568A (zh) 2020-05-19
EP3993485A1 (en) 2022-05-04

Similar Documents

Publication Publication Date Title
WO2021139394A1 (zh) 通信方法、装置、计算机可读介质及电子设备
US10944648B2 (en) Method and system for assisted automatic network service request and delivery in a network environment
WO2019196813A1 (zh) 一种订阅服务的方法及装置
US10785088B2 (en) Management method and management apparatus of internet of things and internet of things system
WO2020057163A1 (zh) Mec平台部署方法及装置
TWI737232B (zh) 通訊方法、裝置、電腦可讀介質、電子設備及電腦程式產品
EP3963866A2 (en) Multi-entity resource, security, and service management in edge computing deployments
US20220217514A1 (en) Network assistance information providing method and apparatus, electronic device, and computer-readable storage medium
US20230055967A1 (en) Communication method and apparatus of multicast and broadcast service, electronic device, and storage medium
WO2018010175A1 (zh) 一种媒体发送权申请方法、媒体发送权撤销方法及装置
US20220116400A1 (en) Authorization in communication networks
WO2016070609A1 (zh) 实现vnf实例化的方法、系统及nfvo和vnfm
WO2018133767A1 (zh) 通话控制方法、终端设备及存储介质
CN113630266B (zh) 一种实例化边缘应用服务器的方法和装置
WO2020029671A1 (zh) 一种直连通信的方法、amf、接入网功能实体及终端
WO2022121589A1 (zh) 一种数据信息获取方法、装置、相关设备及介质
US11968238B2 (en) Policy management system to provide authorization information via distributed data store
WO2023016255A1 (zh) 一种网络功能服务授权方法及装置
US11848841B2 (en) Metrics collecting method and apparatus for media streaming service, medium, and electronic device
US20220360586A1 (en) Apparatus, methods, and computer programs
US20220217539A1 (en) Authorization in cellular communication systems
WO2016165443A1 (zh) 一种保护机器类通信设备的方法、网络实体及mtc设备
WO2023124685A1 (zh) Pcc策略的控制方法、pcf、smf及通信系统
US12010159B2 (en) Triggering of edge server discovery and instantiation by a 5GMS-aware application
CN111669751B (zh) 一种数据流的建立方法、装置及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20911335

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020911335

Country of ref document: EP

Effective date: 20220126

NENP Non-entry into the national phase

Ref country code: DE