WO2020015634A1 - 一种mec信息获取方法及装置 - Google Patents

一种mec信息获取方法及装置 Download PDF

Info

Publication number
WO2020015634A1
WO2020015634A1 PCT/CN2019/096154 CN2019096154W WO2020015634A1 WO 2020015634 A1 WO2020015634 A1 WO 2020015634A1 CN 2019096154 W CN2019096154 W CN 2019096154W WO 2020015634 A1 WO2020015634 A1 WO 2020015634A1
Authority
WO
WIPO (PCT)
Prior art keywords
mec
information
network element
ccf
domain
Prior art date
Application number
PCT/CN2019/096154
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 EP19838743.3A priority Critical patent/EP3809766A4/en
Publication of WO2020015634A1 publication Critical patent/WO2020015634A1/zh
Priority to US17/148,045 priority patent/US11540244B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/562—Brokering proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/04—Recording calls, or communications in printed, perforated or other permanent form
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for acquiring mobile edge computing (mobile edge computing) information.
  • MEC effectively integrates wireless network and Internet technologies, adds computing, storage, and processing functions on the wireless network side, builds an open platform to implant applications, and implements wireless through application programming interface (API)
  • API application programming interface
  • the information exchange between the network and the business server, and the wireless network and business are integrated.
  • MEC can provide customized and differentiated services to the industry, thereby improving network utilization efficiency and value-added value.
  • the MEC is usually deployed on a radio access network (RAN) or a location closer to the RAN to reduce the data transmission delay. Therefore, the range of services and users of a MEC can be limited by the range of services and users of the access network, and cannot meet the needs of third-party applications.
  • RAN radio access network
  • This application provides a MEC information acquisition method and device, which are used to implement the MEC discovery process.
  • this application provides a method for obtaining MEC information, which method includes:
  • the first network element receives the target reference information from the second network element; the first network element sends the MEC information corresponding to the target reference information to the second network element.
  • the above method realizes the discovery process of the MEC, and enables the second network element to communicate with the MEC according to the obtained MEC information, thereby using the capabilities of the MEC to realize service requirements that it cannot meet.
  • the MEC information obtained by the second network element may also belong to a different domain from the second network element, such as belonging to different operators, and implements a solution for calling MECs across operators, which satisfies that third-party applications can Operators' needs to provide services.
  • the target reference information includes at least one of target position information and target capability information.
  • the method before the first network element sends the MEC information to the second network element, the method further includes: the first network element receives the first registration information of the MEC;
  • the first registration information includes addressing information of the MEC, and the first registration information further includes attribute description information of the MEC.
  • the attribute description information includes one or more of the following information: application programming interface API information provided by the MEC, location information of the MEC, and service area information of the MEC , The capability description information of the MEC, and the domain identifier of the MEC.
  • the first network element is a public API architecture core function CCF
  • the second network element is a mobile edge computing MEC
  • the first network element is a CCF
  • the second network element is a CCF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs;
  • the first network element is a MEC proxy function entity, and the second network element is a MEC;
  • the first network element is a MEC proxy function entity
  • the second network element is a MEC proxy function entity
  • the domain to which the first network element belongs is different from the domain to which the second network element belongs;
  • the first network element is a network open function network element NEF, and the second network element is a MEC; or
  • the first network element is an NEF
  • the second network element is an NEF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs.
  • the method further includes: The first network element sends the second registration information of the MEC to the third network element, where the second registration information is used to register the information of the MEC in the third network element, and the third network element belongs to The domain of is different from the domain to which the first network element belongs, and the second registration information includes addressing information of the MEC and part or all of the attribute description information of the MEC.
  • the method further includes: the first network element determining that the location information of the MEC is the MEC When the location information in the domain to which the first network element belongs is, the first network element converts the location information of the MEC into general location information and sends the general location information to the third network element; and / or,
  • the attribute description information of the MEC includes service area information of the MEC
  • the method further includes: the first network element determining that the service area information of the MEC is in a domain to which the first network element belongs The location information of the mobile station, the first network element converts the service area information of the MEC into general service area information, and sends the general service area information to the third network element.
  • the first network element is a CCF
  • the third network element is a CCF
  • a domain to which the first network element belongs is different from a domain to which the third network element belongs.
  • the information of the MEC includes information of a CCF corresponding to the MEC.
  • the information of the MEC includes addressing information of the MEC and attribute description information of the MEC.
  • an embodiment of the present application provides a method for acquiring MEC information of mobile edge computing, including:
  • the second network element sends the target reference information to the first network element
  • the second network element receives information from the first network element of the MEC corresponding to the target reference information.
  • the target reference information includes at least one of target position information and target capability information.
  • the information of the MEC includes information of a CCF corresponding to the MEC.
  • the information of the MEC includes addressing information of the MEC and attribute description information of the MEC.
  • the attribute description information of the MEC includes one or more of the following information: service area information of the MEC, capability description information of the MEC, and application programming provided by the MEC Interface API information, location information of the MEC, and domain identifier of the MEC.
  • the first network element is a public API architecture core function CCF
  • the second network element is a mobile edge computing MEC
  • the first network element is a CCF
  • the second network element is a CCF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs;
  • the first network element is a MEC proxy function entity, and the second network element is a MEC;
  • the first network element is a MEC proxy function entity
  • the second network element is a MEC proxy function entity
  • the domain to which the first network element belongs is different from the domain to which the second network element belongs;
  • the first network element is a network open function network element NEF, and the second network element is a MEC; or
  • the first network element is an NEF
  • the second network element is an NEF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs.
  • the second network element is a MEC; when the attribute description information of the MEC includes API information provided by the MEC, the method further includes: the second network element according to the The API information sends an API call request to the MEC corresponding to the target reference information; the second network element receives an API call response sent by the MEC corresponding to the target reference information.
  • the second network element is a MEC; when the attribute description information of the MEC does not include API information provided by the MEC, the method further includes: The MEC or a CCF corresponding to the MEC sends an API discovery request; the second network element receives an API discovery response, and the API discovery response includes API information provided by the MEC.
  • the method further includes: the second network element sends registration information of the MEC to the first network element, and the registration information of the MEC includes addressing information of the MEC and the MEC MEC attribute description information.
  • an embodiment of the present application provides a method for obtaining MEC information, including:
  • the first network element receives first registration information from the MEC, where the first registration information includes addressing information of the MEC and attribute description information of the MEC;
  • the first network element sends second registration information to the second network element according to the first registration information, and the domain to which the first network element belongs is different from the domain to which the second network element belongs.
  • the attribute description information of the MEC includes one or more of the following information: service area information of the MEC, capability description information of the MEC, and application programming provided by the MEC Interface API information, location information of the MEC, and domain identifier of the MEC.
  • the method further includes: the first network element determining that the location information of the MEC is the MEC When the location information in the domain to which the first network element belongs is, the first network element converts the location information of the MEC into general location information and sends the general location information to the third network element; and / or,
  • the attribute description information of the MEC includes service area information of the MEC
  • the method further includes: the first network element determining that the service area information of the MEC is in a domain to which the first network element belongs The location information of the mobile station, the first network element converts the service area information of the MEC into general service area information, and sends the general service area information to the third network element.
  • an embodiment of the present application provides a MEC information acquisition device.
  • the device includes a receiving unit and a sending unit. Further, the device may further include a processing unit.
  • the receiving unit, the sending unit, and the processing unit are configured to execute the method according to any one of the first aspects.
  • an embodiment of the present application provides a MEC information acquisition device.
  • the device includes a sending unit and a receiving unit. Further, the device may further include a processing unit.
  • the receiving unit, the sending unit, and the processing unit are configured to execute the method according to any one of the second aspects.
  • an embodiment of the present application provides a MEC information acquisition device.
  • the device includes a receiving unit and a sending unit. Further, the device may further include a processing unit.
  • the receiving unit, the sending unit, and the processing unit are configured to execute the method according to any one of the third aspects.
  • an embodiment of the present application provides a storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the method according to any one of the first aspect to the third aspect is implemented.
  • FIG. 1 (a) and FIG. 1 (b) are a network architecture provided by the present application and applicable to the embodiment of the present application;
  • FIG. 2 is a schematic diagram of a MEC architecture provided by this application.
  • FIG. 3 is another network architecture applicable to the embodiment of the present application provided by the present application.
  • FIG. 4 is a schematic flowchart of a MEC information acquisition method provided by this application.
  • FIG. 9 is a schematic flowchart of another MEC information acquisition method according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another MEC information acquisition method according to an embodiment of the present application.
  • FIG. 12 is one of the schematic structural diagrams of the MEC information acquisition device according to the embodiment of the present application.
  • FIG. 13 is a second schematic structural diagram of a MEC information acquisition device according to an embodiment of the present application.
  • FIG. 14 is a third schematic structural diagram of a MEC information acquisition device according to an embodiment of the present application.
  • FIG. 15 is a fourth schematic structural diagram of a MEC information acquisition device according to an embodiment of the present application.
  • FIG. 16 is a fifth schematic structural diagram of a MEC information acquisition device according to an embodiment of the present application.
  • MEC Mobility Management Entities
  • the service area and service users of MEC are also limited. For example, if a MEC is deployed on a base station in area A, the MEC can provide services for third-party applications in area A, but its service scope may not cover area B and cannot meet the requirements of third-party applications to provide services for users in area B. demand. As another example, if the MEC is deployed on the base station of the operator A, the MEC may not be able to provide services for users of the local operator B.
  • a MEC may not be able to meet the business needs of third-party applications, and multiple MECs may need to be coordinated to complete it.
  • there is no method for obtaining other MEC information so multiple MECs cannot be coordinated to complete third-party application service requirements.
  • an embodiment of the present application provides a method for acquiring MEC information.
  • FIG. 1 (a) and FIG. 1 (b) are schematic diagrams of a network architecture that can be applied to a method for acquiring MEC information provided by an embodiment of the present application.
  • the 3GPP Common API Architecture Core Function CCF
  • the PLMN operator also acts as An API provider (service provider) registers an API with the CCF, and a third-party API provider can share and publish its own API to another API provider.
  • CCF can be deployed on both API providers, that is, CCF logic units are deployed in the MEC.
  • One of the API providers can publish the capability information of the API provided by itself to the other API provider through the CCF to implement API sharing.
  • API calling entity also known as API caller
  • API caller is generally a third-party application that has signed a service agreement with a PLMN operator, such as a machine-to-machine (M2M) application , Internet of Things (IoT) applications, Internet of Things (V2X) applications, etc., these applications can run in terminal devices or network devices.
  • the API calling entity can be a device in a PLMN network, such as a mobility management entity (MME), RAN, policy and charging control function (PCRF), etc. in a 4G communication system, or it can be Access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function in 5G communication system , PCF), application functions (AF), etc.
  • MME mobility management entity
  • PCRF policy and charging control function
  • the API calling entity and the PLMN operator are in the same trust domain.
  • the API calling entity supports the following capabilities: Supports authentication of the API calling entity, authenticates the identity and other information of the API calling entity; supports mutual authentication with CAPIF; obtains authorization before accessing the API; discovers the API; calls the API, etc.
  • CCF has the following functions: authenticates the API calling entity based on the identity of the API calling entity and other information; supports mutual authentication with the API calling entity; provides authorization to the API calling entity before the API calling entity accesses the API; releases, stores and supports Discovery of APIs; Responsible for API access control based on policies of PLMN operators; Store logs of API calls and provide them to authorized entities; Detect API calls; Registration of API calling entities; Store configuration policies, etc.
  • API exposing function (AEF): The entry point of the API calling entity to call the API, with the following functions: authenticate the API calling entity based on the identity of the API calling entity and other information provided by the CCF; confirm the authorization provided by the CCF; Synchronize API logs to CCF.
  • API publishing function Provides API publishing functions so that API calling entities can discover the API.
  • API management function provides management of the API, including the following functions: auditing the API call logs provided by the CCF; monitoring the events reported by the CCF; configuring the API provider's policies to the API; detecting the API's Status; registered API calling entity.
  • the functional entities (API open function, API release function, and API management function) in the CCF and API provider domain can be regarded as It is MEC, or CCF and API open function and API release function are regarded as MEC, or CCF and AEF are regarded as MEC, or AEF may be regarded as MEC.
  • FIG. 2 exemplarily illustrates another network architecture that can be applied to the MEC information acquisition method provided by the embodiment of the present application.
  • the network capability open function network element can develop the network capability of the mobile communication network to the internal network elements (such as SMF, AMF) of the mobile communication network or external third-party applications, such as V2X applications, IoT applications, etc.
  • Network function warehouse network element used to maintain network element information of the mobile communication network (including network element type, network element identification, network element slice, services provided by the network element, etc.), and also supports service discovery Function, that is, to provide the requester of the discovery network element or service with the network element or service information that meets its business requirements.
  • FIG. 3 is a schematic diagram of a MEC architecture provided by an embodiment of the present application. As shown in the figure, the MEC architecture may include:
  • Mobile edge platform A set of functions required to run various mobile edge applications on a specific mobile edge host virtual infrastructure. It can provide and consume various mobile edge services, and can provide multiple mobile edge services for itself. Such as support for service registration, service discovery, transmission rule control, DNS resolution and other functions.
  • Mobile edge application An application that can be instantiated on a mobile edge host (mobile edge host) in a mobile edge system. It has the potential to potentially provide or consume mobile edge services.
  • Mobile edge service Services provided by the mobile edge platform itself or a mobile edge application can generally be provided to the mobile edge application in an API manner.
  • registering the information of the network element A with the network element B can also be understood as publishing the information of the network element A to the network element B. Further, the network element B saves the information of network element A.
  • N1, N2, N4, Nnef, etc. indicate interfaces, and other network elements involved are: User Equipment (UE), Access Network (AN), and User Plane.
  • Functional entity User Plane Function (UPF)
  • data network DN
  • authentication server function AUSF
  • access and mobility management function entity Access and Mobility Management Function
  • AMF Access and Mobility Management Function
  • SMF session function Management entity
  • NRF network exposure entity
  • NRF Network Repository Function
  • Policy Control Function Policy Control Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • AF Application Function
  • the method may include the following steps:
  • Step 401 The first network element receives target reference information from the second network element.
  • the target reference information may be used by the first network element to find information of the MEC corresponding to the target reference information.
  • the target reference information may include at least one of target position information and target capability information.
  • the target reference information may be carried in a message sent by the second network element to the first network element.
  • the message may be a MEC discovery request (MEC discovery request), a service discovery request (service discovery request), or an API discovery request (API discovery request) message.
  • MEC discovery request MEC discovery request
  • service discovery request service discovery request
  • API discovery request API discovery request
  • the target reference information is carried in the MEC discovery request as an example. Instructions.
  • the second network element may send a MEC discovery request, where the request carries the above target reference information, so that the first network element can send the information of the MEC corresponding to the target reference information to the second network element.
  • the target reference information may include target position information and / or target capability information.
  • a third-party application is deployed on MEC1, and the service area corresponding to MEC1 is area A.
  • MEC1 can provide services for third-party applications in area A (for example, broadcast V2X messages to vehicles that support V2X in area A); however, the first The third-party application also has some users located in area B.
  • MEC1 can send a MEC discovery request, which includes target location information: indication information of area B to indicate MEC1 Request for information on one or more MECs capable of serving area B.
  • MEC1 can provide V2X type services, and third-party applications need to provide V2X type services.
  • MEC1 can send a MEC discovery request, which includes target capability information: an indication of the broadcast service.
  • Information used to indicate that MEC1 requests information about MECs that can provide broadcast services.
  • MEC1 can send a MEC discovery request,
  • the request includes target location information: indication information of area A, and domain identification information of China Unicom, which is used to indicate the request for obtaining MEC information that can provide services to users of China Unicom in area A.
  • the indication information of the area A may be the identifier of the area A, the latitude and longitude information of the area A, or other information that can correspond to the area A.
  • the MEC discovery request also contains target location information and target capability information. For example, MEC1 needs to obtain information about MECs that can provide broadcast services for area A.
  • the target reference information sent by MEC1 may include area A's instruction information and Instructions for broadcasting services.
  • the above target location information indicates that the second network element needs to obtain information of an MEC capable of providing services to the target location, but it does not mean that the MEC requesting acquisition should be deployed at the target location.
  • MEC1 is deployed on area A, but the service area of MEC includes area A, area B, and area C.
  • MEC2 requests to obtain an MEC that can serve the target area B, although MEC1 is not located in area B, MEC1 Can provide services for area B, so MEC1 still meets the requirements of MEC2.
  • Step 402 The first network element sends the MEC information corresponding to the target reference information to the second network element.
  • the MEC corresponding to the target reference information may refer to the MEC in the target area corresponding to the target position information; or, when the target reference information is target capability information, the target reference information is related to the target reference information.
  • the corresponding MEC may refer to a MEC having a target capability corresponding to the target capability information; or, when the target reference information and the target capability information, the MEC corresponding to the target reference information may refer to a target region corresponding to the target position information
  • the MEC with the target capability corresponding to the target capability information is not limited.
  • the first network element may determine the MEC that meets the target reference information according to the target reference information and the MEC information obtained by the first network element, and send the determined MEC information to the second network element.
  • the information of the one or more MECs obtained in the first network element may be stored in the first network element in a pre-configured manner when the first network element is enabled, or manually entered into the first network element. It may also be that other network elements send the obtained MEC information to the first network element.
  • the MEC when a new MEC is deployed, or when API information provided by the MEC changes, or when other triggering events occur, the MEC actively sends its own information to the first network element to implement The MEC information is registered in the first network element (that is, the first network element obtains the MEC information).
  • the MEC can also send its registration information to other network elements, and then the other network elements send the first network element to complete the registration of the MEC information in the first network element.
  • MEC1 can send its registration information to CCF1 located on MEC1 (the location of the deployment hierarchy is lower), and then CCF1 sends the registration information of MEC1 to the deployment hierarchy in the network.
  • High CCF2 to register MEC1 information into CCF2.
  • the MEC may send a MEC registration request to the first network element, where the registration request includes addressing information of the MEC and attribute description information of the MEC.
  • the addressing information of the MEC may be an identifier of the MEC, or an identifier of a CCF deployed on the MEC.
  • the MEC attribute description information may include one or more of the following information:
  • MEC can provide "services" for third-party applications.
  • the "services” can be understood as network resources or programs that implement a specific function, such as functions, function libraries, packets, etc., and third-party applications. You can call the API to implement the corresponding service.
  • the API information may include an identifier of the API, whether the API can be shared, an API type, and service area information of the API.
  • MEC domain ID indicates the domain to which the MEC belongs. Taking the MEC's addressing information as the MEC identifier as an example, in some scenarios, the MEC identifier can uniquely identify a MEC; in other scenarios, the MEC identifier can uniquely identify a MEC in the domain to which it belongs. If a MEC needs to be uniquely identified globally, it is implemented by "MEC identification + domain identification".
  • the domain to which the MEC belongs can refer to the CAPIF provider domain and the CAPIF system domain.
  • the MEC can be a collection of CCF, AEF, APF, and AMF in the CAPIF architecture, and the CAPIF provider domain and system domain can be the domain to which the MEC belongs;
  • the domain to which the MEC belongs can also refer to the PLMN trust domain and the PLMN network domain.
  • the trust domain and network domain of the PLMN can be used as the domain to which the MEC belongs; or
  • the domain to which the MEC belongs can also refer to the API service provider domain, and so on.
  • the domain identifier may be a CAPIF ID, a PLMN ID, an API provider ID, or a PLMN network domain name (such as @ cmcc.com), an API service provider domain name, and so on.
  • the location information of MEC can also reflect the service area information of MEC to a certain extent.
  • the location information of the MEC can be the general location information of the MEC, that is, information that can be identified by network elements in different domains, such as the latitude and longitude of the MEC, the administrative area where the MEC is located, and the roadside unit (RSU). ) Service area, identification of RSU (RSU can be provided by a third party, and the location area where RSU is located can be determined by the identification of RSU), etc.
  • the location information of the MEC may also be location information in a domain to which the MEC belongs, for example, a cell identifier where the MEC is located.
  • MEC service area information indicates the service area of the MEC.
  • the MEC service area information can be general area information, such as the latitude and longitude range of the service area, administrative area, etc .; it can also be area information in the domain to which the MEC belongs, such as the MEC service area, tracking area, registration area, etc. , It can be expressed by the cell identity list, tracking area identity list, registered area identity list, etc.
  • MEC capability description information indicates the type of service provided by the MEC.
  • the APIs provided in MEC1 include: API_1 that provides broadcast services and API_2 that provides traffic accounting services.
  • the attribute description information of the MEC may include capability description information such as broadcasting services and traffic accounting services.
  • the capability description information may be a text label, such as Broadcast Service / Broadcast, Charging / Charging, or a predefined enumeration value, such as 001 for Broadcast Service / Broadcast, and 002 for Charging / Charging (when information When the receiver is a network element outside the domain where the MEC is located, it also needs to provide a complete mapping of enumeration values and capability descriptions) to facilitate other network element calls.
  • the first network element may store the MEC information, so that after receiving the MEC discovery request subsequently, the first network element searches for the presence of the MEC information matching the target reference information from the stored MEC information.
  • the first network element may also send the MEC registration information to other network elements, so as to register the MEC information in other network elements, so as to improve the other network elements receiving the MEC.
  • the response speed after a request is found.
  • MEC1 belonging to PLMN_1 sends a first registration to CCF1 (first network element) in PLMN_1.
  • the first registration information includes addressing information of MEC1 and attribute description information of MEC, so as to register the information of MEC1 in CCF1.
  • CCF1 sends second registration information to CCF2 in PLMN_2, and the second registration information includes addressing information of MEC1 and attribute description information of MEC.
  • the attribute description information contained in the second registration information may be less than the attribute description information contained in the first registration information.
  • the attribute description information in the first registration information includes detailed information of the API provided by MEC1 and the capabilities of MEC1.
  • the description information, the location information of MEC1, the service area information of MEC1, and the domain identifier of MEC1, and the attribute description information in the second registration information may include only the capability description information of MEC1 and the service area information of MEC1.
  • the MEC1 sends the location information (and / or service area information) of the MEC1 to the CCF1, it may be general location information or location information in PLMN_1. However, if it is the location information (such as the cell identity) in PLMN_1, the location information may not be recognized by CCF2 belonging to PLMN_2. Therefore, before sending the second MEC registration information to CCF2, CCF1 can determine whether the location information (and / or service area information) of MEC1 is the location information in PLMN_1. If so, CCF1 can convert the location information to a general location. Information, such as administrative area, etc., then the converted general location information is carried in the second registration information and sent to CCF2.
  • the first network element may further The other network elements send the target reference information described above, so as to obtain the MEC information that meets the target reference information from other network elements.
  • the MEC information is not pre-stored in the first network element, and the MEC information is registered in the network function storage function (NF, Repository Function, NRF); then the first network element is found when receiving the MEC carrying the target reference information After the request, an MEC discovery request carrying the above target reference information may be sent to the NRF, so as to obtain the MEC information from the NRF that meets the above target reference information.
  • NF Network Function Storage Function
  • NRF Network Function Storage Function
  • MEC1 second network element located in area A and belonging to PLMN_1 sends a MEC discovery request to CCF1 (first network element) in PLMN_1, requesting to obtain a service belonging to PLMN_2 that can provide services to users in area A MEC.
  • CCF1 second network element located in area A and belonging to PLMN_1 sends a MEC discovery request to CCF1 (first network element) in PLMN_1, requesting to obtain a service belonging to PLMN_2 that can provide services to users in area A MEC.
  • the CEF1 does not store the MEC information that matches the target reference information.
  • CCF1 can send information to the PLMN_2.
  • CCF2 sends a MEC discovery request to obtain CCF information from CCF2 that meets the target reference request, and sends MEC information obtained from CCF2 to MEC1.
  • the information of the MEC sent by the first network element in the foregoing step 402 may include addressing information of the MEC (for example, an identifier of the MEC) and attribute description information of the MEC.
  • the MEC attribute description information sent by the first network element may be part or all of the MEC attribute description information stored by the first network element or acquired by the first network element.
  • the attribute description information stored by the first network element or obtained by the first network element from other network elements includes detailed information of the API provided by the MEC, capability description information of the MEC1, location information of the MEC1, service area information of the MEC1,
  • the domain identifier of MEC1, and the attribute description information sent by the first network element to the second network element may include only the capability description information of MEC1 and the service area information of MEC1.
  • CCF_1 is a logical unit set in MEC_1
  • the attribute description information of CCF_1 still describes the information of MEC_1.
  • the MEC discovery response sent by CCF_2 can carry the information of CCF_1, so that the requester can The information further obtains the information of MEC_1, and specifically, the information of the API provided by the MEC_1 can be obtained.
  • the second network element may call the API of the MEC according to the obtained MEC information, so as to implement the MEC to provide a third-party application with a service that meets its service requirements. Specifically, if the MEC information obtained by the second network element includes the API information provided by the MEC, the second network element may call the corresponding API according to the required service type and service area, that is, send to the MEC API call request, the request includes the API identification. If the MEC information obtained by the second network element does not include the API information provided by the MEC, the second network element may send an API discovery request to the MEC (or the CCF corresponding to the MEC), and has requested to obtain the MEC provided by the MEC. API information; after obtaining the API information, send an API call request to the MEC.
  • the second network element achieves the MEC information through interaction with the first network element, that is, the MEC discovery process is implemented, and the second network element can make the second network element according to the obtained MEC
  • the information communicates with the MEC, so as to use the capabilities of the MEC to provide third-party applications to meet their service needs.
  • the MEC information obtained by the second network element may also belong to a different domain from the second network element, such as belonging to different operators, and implements a scheme for calling MECs across operators, which satisfies that third-party applications can be different Operators' needs to provide services.
  • FIG. 5 (a) is a network deployment scenario to which the above embodiments of the present application can be applied.
  • MEC_1 the first network element
  • CCF_2, the second network element the highest-level CCF
  • a logical unit CCF_1 with CCF function is set in MEC_1;
  • MEC_2 and the highest level CCF are deployed in PLMN_2;
  • a logical unit CCF_3 with CCF function is set in MEC_2.
  • Step 501 MEC_2 sends MEC registration information to CCF_3.
  • the registration information may include the MEC_3 identifier, the service area information of MEC_3, the API information provided by MEC_3, and the identifier of PLMN_2.
  • the registration information includes API information. Therefore, the registration information can be carried in an API publishing request (API request) and sent. Alternatively, it can also be sent in a MEC publishing request (MEC Publish request). At this time, MEC_2 can be an instance of AEF in CAPIF.
  • Step 502 CCF_3 sends a MEC registration response to MEC_2.
  • the MEC registration response is used to respond to the registration information sent by MEC_2, and the response may further include indication information of registration success or registration failure.
  • Step 503 CCF_3 sends a MEC registration request to CCF_4.
  • step 504 Since PLMN_1 and PLMN_2 already have a commercial contract relationship, the MEC information is allowed to register with each other, and step 504 is performed.
  • Step 504 CCF_4 sends MEC registration information to CCF_2.
  • the registration information may include the CCF_3 information carried in step 503 described above.
  • the information of CCF_3 sent in step 504 may be less than the information sent in step 503.
  • Step 505 CCF_2 sends a MEC registration response to CCF_4.
  • the MEC registration response is used to respond to the registration information sent by CCF_4, and the response may include indication information of successful registration or registration failure.
  • Step 506 CCF_4 sends a MEC registration response to CCF_3.
  • the MEC registration response is used to respond to the registration information sent by CCF_3, and the response may include indication information of successful registration or registration failure.
  • step 506 may also be executed after step 503.
  • MEC_1 can also complete the registration process on CCF_1, CCF_2, and CCF_4 according to the above process, which will not be repeated here.
  • Step 507 MEC_1 sends an API discovery request to CCF_1.
  • MEC_1 determines to call the API in PLMN_2 capable of providing service to service area A as the third-party application service, and then execute step 507.
  • the step of determining to call the API capable of providing service area A in PLMN_2 as a third-party application service may also be performed by CCF_1 or CCF_2.
  • the request may include target reference information.
  • the target reference information is the information of service area A and the identification of PLMN_2 is taken as an example for description.
  • the request message is used to indicate that MEC_1 requests to call the API in PLMN_2 that can provide service to area A.
  • MEC_1 can be regarded as an instance of the API requester in CAPIF.
  • the above API discovery request may also carry the identifier of MEC_1 as the identifier of the API requester.
  • step 508 is performed.
  • Step 508 CCF_1 sends a MEC discovery request to CCF_2.
  • the MEC discovery request is used to request information about a MEC capable of providing an API capable of serving Area A.
  • Step 509 CCF_2 sends a MEC discovery response to CCF1.
  • CCF_2 determines that the MEC corresponding to CCF_3 meets the requirements according to the received request message and the obtained MEC information, so the information of CCF_3 is carried in the MEC discovery response and sent to CCF_1.
  • the information obtained by CCF_2 for CCF_3 may or may not include API information provided by MEC_2 corresponding to CCF_3, so the discovery response sent by CCF_2 may not include API information provided by MEC_2 corresponding to CCF_3. If the MEC finds that the API information provided by MEC_2 is not included in the response, step 510 is performed; otherwise, step 512 is performed.
  • Step 510 CCF_1 sends an API discovery request (API discovery request) to CCF_3.
  • API discovery request API discovery request
  • Step 511 CCF_3 sends an API discovery response (API discovery response) to CCF_1.
  • the response includes the API information that CCF_1 can provide (that is, the API information that MEC_2 can provide), or if the API discovery request sent in step 510 also includes API condition information: the information of service area A and the identifier of PLMN_2, indicating Request to obtain the API in PLMN_2 that can serve area A, then the API discovery response sent by CCF_3 may also include only the information of the API corresponding to the target reference information.
  • Step 512 CCF_1 sends an API discovery response to MEC_1.
  • Step 513 MEC_1 sends an API call request (API discovery request) to MEC_3.
  • the request includes an API identifier of the request.
  • Step 514 MEC_3 sends an API call response (API discovery response) to MEC_1.
  • CCF_3 may also directly register the information of MEC_2 to CCF_2.
  • Steps 521 to 524 are the same as the foregoing steps 501 to 504.
  • Steps 525 to 528 Register the information of MEC_3 on CCF_5 and CCF4, which is similar to steps 501 to 504, and is not repeated here.
  • Step 529 CCF_4 sends registration information to CCF_2.
  • the registration information may include an identifier of CCF_4 and attribute description information of CCF_4.
  • the content of the CCF attribute description information is similar to the MEC attribute description information, and may include service area information, capability description information, and domain identifier.
  • the attribute description information of CCF_4 may be used to describe comprehensive attributes including MEC_2 and MEC_3.
  • the service area of MEC_2 is area A, and the capacity description information includes broadcast services
  • the service area of MEC_3 is area B, and the capacity description information is V2X service
  • the service area information of CCF_4 may include area A + area B
  • the capacity description information may include Broadcast service + V2X service.
  • Step 530 CCF_2 sends a registration response to CCF_4.
  • Step 531 MEC_1 sends an API discovery request to CCF_1.
  • MEC_1 requests to obtain information of an API capable of serving area A in PLMN_2 according to a demand of a third-party application to provide services to users of PLMN_2 in area A, and the above request may include API condition information:
  • the information and the identifier of PLMN_2 are used to indicate the request to obtain the API in PLMN_2 that can provide service to area A.
  • step 532 is performed.
  • Step 532 CCF_1 sends a MEC discovery request to CCF_2.
  • the MEC discovery request is used to request information about a MEC that can provide an API that meets the above conditions.
  • CCF_2 determines from the received CCF_4 information that CCF_4 has an MEC that provides an API corresponding to the above API condition information, but does not know which MEC is provided, or CCF_2 determines that there is also a CCF_4 corresponding to the PLMN_2 identifier.
  • the MEC of the API condition information performs step 534.
  • Step 534 CCF_2 sends a MEC discovery request to CCF_4.
  • the request includes information of the service area A.
  • step 535 is performed.
  • Step 535 CCF_4 sends a MEC discovery response to CCF_2.
  • the response includes information of CCF_3.
  • FIG. 6 (a) is a network deployment scenario applicable to the foregoing embodiment of the present application.
  • MEC_4 the first network element
  • CCF_6 the second network element
  • PLMN_1 the first network element
  • PLMN_2 the second network element
  • FIG. 6 (b) the schematic flowchart of the MEC information acquisition method can be shown in FIG. 6 (b).
  • description is made by taking the MEC capability as a broadcast service capability as an example:
  • Step 601 MEC_5 sends MEC registration information to CCF_7.
  • the registration information may include the MEC_5 identifier, the service area information of MEC_5, the API information provided by MEC_5, and the identifier of PLMN_2.
  • MEC_4 can be regarded as an instance of AEF and APF in CAPIF.
  • Step 602 CCF_7 sends a MEC registration response to MEC_5.
  • the MEC information can be registered with each other, and step 603 is performed.
  • Step 603 CCF_7 sends registration information of MEC_5 to CCF_6.
  • Step 604 CCF_6 sends a MEC registration response to CCF_7.
  • MEC_4 can also complete the registration process on CCF_6 and CCF_7 according to the above process, which will not be repeated here.
  • a CCF logic unit can also be set in MEC_4 to form a similar architecture to Figure 5 (a). During the registration and discovery process, the interaction between the two can be seen in Figure 5 (b) and Figure 5 (c). The embodiment shown.
  • Step 605 MEC_4 sends a MEC discovery request to CCF_6.
  • MEC_4 determines that it is necessary to obtain the MEC capable of providing broadcasting services in PLMN_2 according to the requirements of the third-party application to provide broadcasting services for users in PLMN_2.
  • the target reference information included in the request may include the indication information of the broadcasting service and the information of PLMN_2. logo.
  • Step 606 CCF_6 sends a MEC discovery response to MEC_4.
  • the MEC discovery response carries information of MEC_5 corresponding to the target reference information.
  • CCF_6 determines that the identifier of the domain to which MEC_5 belongs is PLMN_2 according to the MEC information obtained by itself, and MEC_5 is capable of providing a broadcast service, and step 606 is performed.
  • Step 607 MEC_4 sends an API call request to MEC_5.
  • the above API call request includes an identifier of an API called by the MEC_4 request.
  • Step 608 MEC_5 sends an API call response to MEC_4.
  • the process of registering the information of MEC_5 to CCF_6 is performed by CCF_7.
  • MEC_5 may also directly register its own information on CCF_6.
  • Step 611 MEC_5 sends MEC registration information to CCF_7.
  • Step 612 CCF_7 sends a MEC registration response to MEC_5.
  • Step 613 CCF_7 sends registration information to CCF_6.
  • the registration information includes the identifier of CCF_7 and the attribute description information of CCF_7.
  • the attribute description information of CCF_7 is similar to the aforementioned attribute description information of CCF_4.
  • CCF_7 sends registration information to CCF_6.
  • Step 614 CCF_6 sends a MEC registration response to CCF_7.
  • Step 615 MEC_4 sends a MEC discovery request to CCF_6.
  • the request includes broadcast service instruction information and the identification of PLMN_2.
  • MEC_4 determines that it needs to cooperate with the MEC capable of providing broadcast services in PLMN_2 to provide services to third-party applications according to the service requirements for sending broadcast messages for users in PLMN_2 provided by the third application, and then MEC_4 sends a MEC discovery request to CCF_6.
  • Step 616 CCF_6 sends a MEC discovery request to CCF_7.
  • the request includes broadcast service instruction information.
  • CCF_6 determines that there is a MEC capable of providing a broadcast service in CCF_7, and may further send a MEC discovery request to CCF_7, and has obtained the information of the MEC providing the service.
  • Step 617 CCF_7 sends a MEC discovery response to CCF_6.
  • CCF_7 determines that MEC_5 can provide a broadcast service
  • the above MEC discovery response may include an identifier of MEC_5 and information of an API providing the broadcast service.
  • Step 618 CCF_6 sends a MEC discovery response to MEC_4.
  • the discovery response includes the identifier of MEC_5 and the information of the API providing the broadcast service.
  • Step 619 MEC_4 sends an API call request to MEC_5.
  • Step 620 MEC_5 sends an API call response to MEC_4.
  • FIG. 7 (a) is a network deployment scenario to which the above embodiments of the present application can be applied.
  • MEC_6 first network element
  • MEC proxy network element MEC proxy_1 second network element
  • MEC_7 and MEC proxy network element are deployed in PLMN_2.
  • a MEC proxy network element is deployed in each PLMN, and MEC information is registered in the MEC proxy network element.
  • MEC discovery process is initiated to the MEC proxy network element.
  • the MEC proxy network element may also be replaced with a MEC gateway (MEC gateway) or a MEC repository function (NEC) or NEF.
  • MEC gateway MEC gateway
  • NEC MEC repository function
  • Step 701 MEC_7 sends MEC registration information to MEC proxy_2.
  • the registration information may include the MEC_7 identifier, the service area information of the MEC_7, the API information provided by the MEC_7, and the identifier of the PLMN_2.
  • Step 702 MEC proxy_2 sends a MEC registration response to MEC_7.
  • MEC information can be registered with each other.
  • the MEC information may be shown in steps 703a and 704a when performing cross-PLMN registration, and may also be shown in steps 703b and 704b.
  • Step 703a MEC proxy_2 sends registration information of MEC_6 to MEC proxy_1.
  • Step 704a MEC proxy_1 sends a MEC registration response to MEC proxy_2.
  • Step 703b MEC_7 sends MEC registration information to MEC proxy_1.
  • Step 704b MEC proxy_1 sends a MEC registration response to MEC_7.
  • MEC_6 can also complete the registration process on MEC proxy_1 and MEC proxy_2 according to the above process, which will not be repeated here.
  • Step 705 MEC_6 sends a MEC discovery request to MEC proxy_1.
  • the request includes the traffic accounting service indication information and the identification of PLMN_2, which indicates that the MEC_6 requests to obtain information of the MEC in PLMN_2 that can provide the traffic accounting service.
  • Step 706 MEC proxy_1 sends a MEC discovery response to MEC_6.
  • the MEC discovery response carries information of MEC_7 capable of providing traffic accounting services.
  • MEC_proxy_1 determines that MEC_7 meets the requirements according to the received MEC discovery request and the obtained MEC information, so the MEC_7 information is carried in the MEC discovery response and sent to MEC_6.
  • Step 707 MEC_6 sends an API call request to MEC_7.
  • the call request may include an API identifier of the request call.
  • Step 708 MEC_7 sends an API call response to MEC_6.
  • the schematic flow chart of the MEC information acquisition method can also be shown in Figure 7 (c): where the registration process of the MEC information can be consistent with the registration process shown in 7 (b) Or, the registration across PLMN may not be performed, that is, the information of MEC_7 may not be registered on MEC proxy_1, or the information of MEC_6 may not be registered on MEC proxy_2, which is not limited in this embodiment of the present application.
  • Steps 711 to 720 are similar to steps 611 to 620, except that the CCF is replaced with MEC proxy, which will not be repeated one by one here.
  • FIG. 8 (a) is a network deployment scenario to which the above embodiments of the present application can be applied.
  • MEC_8 (the first network element) is deployed in PLMN_1; MEC_9, NEF_1 (or MEC gateway_3) are deployed in PLMN_2. , Or MEC proxy network element as the second network element) and NRF_1.
  • MEC_8 may also be provided with a CCF logic unit.
  • CCF logic unit For the interaction between the two during the registration and discovery process, refer to the embodiment shown in FIG. 5.
  • FIG. 8 a schematic flowchart of the MEC information acquisition method is shown in FIG. 8 (b).
  • Step 801 MEC_9 sends MEC registration information to NRF_1.
  • the registration information may include the MEC_9 identifier, the service area information of the MEC_9, the API information provided by the MEC_9, and the identifier of the PLMN_2.
  • Step 802 NRF_1 sends a MEC registration response to MEC_9.
  • Step 803 MEC_8 sends a MEC discovery request to NEF_1.
  • MEC_8 determines that it needs to find the MEC capable of providing the V2X service in PLMN_2 according to the business requirements of the third-party application, and MEC_8 sends a MEC discovery request to NEF_1, which includes V2X service instruction information.
  • MEC_8 can be regarded as an embodiment of the API requester in the CAPIF. This embodiment is described by taking the capability of the MEC as a V2X service as an example.
  • Step 804 NEF_1 sends a NF discovery request to NRF_1.
  • the request may include indication information that the target network element is MEC, which is used to instruct finding a network element of MEC type, and also includes V2X service instruction information, which further instructs to find a MEC type network element that provides V2X service.
  • Step 805 NRF_1 sends a NF discovery response to NEF_1.
  • the NF discovery response carries information of MEC_9 that complies with the NEF_1 request.
  • NRF_1 determines that MEC_9 complies with NEF_1's request according to the received NEF discovery request and the obtained MEC information, so the MEC_9 information is carried in the NF discovery response and sent to NEF_1.
  • Step 806 NEF_1 sends a MEC discovery response to MEC_8.
  • the response carries information of MEC_9.
  • Step 807 MEC_8 sends an API call request to MEC_9.
  • MEC_8 can send an API call request to MEC_9, the call request contains the ID of the API to be called, and the API corresponding to the API ID is requested.
  • Step 808 MEC_9 sends an API call response to MEC_8.
  • PLMN_1 may also include NEF_2 (or MEC gateway_4, or MEC proxy network element), as shown in Figure 8 (c).
  • NEF_2 or MEC gateway_4, or MEC proxy network element
  • FIG. 8 (d) A schematic flowchart of the MEC information acquisition method can be shown in FIG. 8 (d).
  • Step 811 MEC_9 sends MEC registration information to NRF_1.
  • Step 812 NRF_1 sends a MEC registration response to MEC_9.
  • Step 813 MEC_8 sends a MEC discovery request to NEF_2.
  • the request includes V2X service instruction information and the identification of PLMN_2, which indicates that the request for obtaining information of the MEC capable of providing the V2X service in PLMN_2 is requested.
  • MEC_8 determines that it is necessary to find the MEC in PLMN_2 that can provide the V2X service, and then execute step 813 described above.
  • Step 814 NEF_2 sends a MEC discovery request to NEF_1.
  • the request includes V2X service indication information.
  • NEF_2 may send a MEC discovery request to NEF_1 according to the identity of PLMN_2 in the discovery request.
  • Step 815 NEF_1 sends a NF discovery request to NRF_1.
  • the request may include indication information that the target network element is MEC, and also includes V2X service indication information.
  • Step 816 NRF_1 sends a NF discovery response to NEF_1.
  • the NF discovery response carries information of MEC_9 capable of providing V2X services.
  • NRF_1 determines that MEC_9 meets the requirements according to the received NF discovery request and the obtained MEC information, so the MEC_9 information is carried in the NF discovery response and sent to NEF_1.
  • Step 817 NEF_1 sends a MEC discovery response to NEF_2.
  • the response carries information of MEC_9.
  • Step 818 NEF_2 sends a MEC discovery response to MEC_8.
  • the response carries information of MEC_9.
  • Step 819 MEC_8 sends an API call request to MEC_9.
  • the information of the MEC_9 includes API information provided by the MEC_9, which includes an API identifier, and the MEC_8 sends an API call request to the MEC_9, and the call request includes the API identifier, indicating that the API corresponding to the API identifier is called.
  • Step 820 MEC_9 sends an API call response to MEC_8.
  • the embodiment of the present application further provides a MEC information registration method, which is used to implement registration of MEC information on network elements in other domains.
  • a schematic flowchart of the method can be shown in FIG. 9 and includes the following steps:
  • Step 901 The third network element receives the first registration information from the MEC.
  • the third network element described herein is used to implement the MEC information registration method, and may be the same network element or a different network element as the first network element in the foregoing embodiment of the method for obtaining MEC information.
  • the third network element may receive the first registration information sent by the MEC, such as CCF_5 and CCF_6 in FIG. 6 (a), MEC proxy_1 / MECgateway_1, MEC proxy_2 / MECgateway_2, and so on in FIG. 7 (a).
  • the first registration information of the MEC received by the third network element may also be forwarded by other network elements.
  • the registration information of MEC_2 received by CCF_4 in Figure 5 (a) is CCF_3 is sent.
  • the first registration information of the MEC may include addressing information of the MEC and attribute description information of the MEC.
  • the attribute description information in this embodiment is similar to the attribute description information in the foregoing embodiment, and will not be described again.
  • Step 902 The third network element sends the second registration information to the fourth network element according to the first registration information, and the domain to which the fourth network element belongs is different from the domain to which the third network element belongs.
  • the domain to which the network element belongs is similar to the concept of "domain” in the foregoing embodiment, and is not repeated here.
  • the second registration information includes addressing information of the MEC and attribute description information of the MEC.
  • all the attribute description information received by the third network element may be sent to the fourth network element, and the attribute description information received by the third network element may also be sent. Part of the attribute description information is sent to the fourth network element.
  • the addressing information of the MEC may refer to an identifier of the MEC, etc., or an identifier of a CCF corresponding to the MEC, and the like.
  • a CCF_3 logic unit is set on MEC_2, then when CCF_4 registers MEC_2 information to CCF_2, the MEC registration information sent by CCF_4 to CCF_2 may include the MEC_2 identification And the attribute description information of MEC_2; or, it may not include the MEC granularity information, but include the CCF_3 identifier and the attribute description information of CCF_3 (because CCF_3 is deployed in MEC_2, the attribute description information of MEC_2 can be used as the attribute description information of CCF_3 ).
  • the third network element may first determine whether to send the location information or the service area information when sending the location information or the service area information. Whether the information can be sent directly or needs to be converted and then sent. For example, if the information of the MEC is the cell identity in the PLMN network, the cell identity cannot be identified by the network elements in other PLMNs, so the third network element can convert it when it is sent to a different domain. The location information commonly used between them can be converted into longitude and latitude information or administrative area information, so that the fourth network element can also identify.
  • the information of the MEC in one domain is registered with the network element in another domain, so that the network element can obtain the information of the MEC in the other domain.
  • the MEC discovery process can be implemented only in the first domain, and it is not necessary to report to the first domain.
  • the network elements in the second domain send discovery requests, which improves the response speed of MEC discovery.
  • PLMN_2 may include multiple MECs, and each MEC registers its information on CCF_4.
  • the MEC registration information sent by CCF_4 to CCF_2 may include the identity of CCF_4 and the capability set of the multiple MECs.
  • the service area of MEC_2 is area A, which can be used to provide V2X services; while the service area of MEC_3 is area B, which can be used to provide billing services, then the MEC registration information sent by CCF_4 to CCF_2 can include the identity of CCF_4, CCF_4 Service area: area A and area B, CCF_4 capability description information: V2X service and charging service, CCF_4 domain identity: PLMN_2 identity and so on.
  • this embodiment of the present application also provides an information registration method for registering MEC information with network elements in other domains.
  • registration Due to cross-domain registration, for security and other aspects, registration It does not carry the MEC logo.
  • a schematic flowchart of the method can be shown in FIG. 10 and includes the following steps:
  • Step 1001 The fifth network element receives registration information from the MEC.
  • the fifth network element in this embodiment may be a CCF, a MEC proxy, or a MEC gateway.
  • CCF_A receives the registration information from MEC1, then the registration information may include the identification of MEC1 and the attribute description information of MEC1, or may include the CCF1 identification and the attribute description information of CCF1 (because CCF1 is deployed in MEC1) , The attribute description information of MEC1 can be used as the attribute description information of CCF1). In addition, CCF_A can also receive registration information from MEC2.
  • the attribute description information in this embodiment is similar to the attribute description information in the foregoing embodiment, and will not be described again.
  • Step 1002 The fifth network element sends a registration request to the sixth network element.
  • the domain to which the sixth network element belongs is different from the domain to which the fifth network element belongs.
  • the registration request includes the identity of the fifth network element and the fifth network element.
  • the attribute description information of the network element, and the attribute description information of the fifth network element is used to comprehensively describe the attribute description information of one or more MECs registered on the fifth network element.
  • the fifth network element and the sixth network element belong to different domains, such as different PLMNs, for security reasons, the fifth network element may not send MEC granularity information when sending a registration request to the sixth network element. Only the description of the fifth network element and the attribute description information of the fifth network element are sent.
  • CCF_A in PLMN_A may send registration information to CCF_B in PLMN_B, and the registration information may include an identifier of CCF_A. If the identification of CCF_A can only uniquely identify CCF_A in PLMN_A, the registration information may also include the identification of PLMN_A, and uniquely identify CCF_A by means of ⁇ identification of CCF_A + identification of PLMN_A>.
  • the registration information also includes the attribute description information of CCF_A, that is, the attribute description information of the MEC registered on CCF_A.
  • the attribute description information may not specifically refer to the attribute description information of a certain MEC, but may be expressed as the total capability of multiple MECs registered on CCF_A. For example, if MEC1 registered on CCF_A has the capability of broadcasting and traffic accounting MEC2 has the ability to provide V2X services, so in the registration information sent by CCF_A to CCF_B, the capability description information may include broadcast, traffic accounting, and V2X service instruction information.
  • the registration information may also include service area information of the MEC registered on CCF_A.
  • the service area information may not specifically refer to capability information of a certain MEC, but may be expressed as a total service area of a plurality of MECs registered on CCF_A. For example, if the service area of MEC1 registered on CCF_A is area A and area B, and the service area of MEC2 is area C and area D, then the registration information sent by CCF_A to CCF_B may include area A, area B , Area C, area D.
  • CCF_B receives a MEC discovery request, the MEC request contains the target reference information, and the target reference information is used to request the MEC that can serve area A. Then CCF_B can determine the CCF_A and If the target reference information corresponds, a MEC discovery request is sent to CCF_A to obtain the corresponding MEC information from CCF_A. Alternatively, CCF_B may also send the identifier of CCF_A (or the identifier of CCF_A + the identifier of PLMN_A) to the requester, and the requester may request CCF_A to obtain information about the MEC that can provide the corresponding service.
  • the above step 1002 may be performed after receiving the registration information of the MEC, or the above step 1002 may be performed periodically.
  • Step 1003 The sixth network element updates the received registration information to the local, so that after subsequent MEC discovery requests are received, the MEC corresponding to the target reference information or the CCF corresponding to the MEC is selected according to the registration information saved locally.
  • Step 1004 The sixth network element sends a registration response to the fifth network element.
  • an embodiment of the present application further provides a MEC information acquisition device, which is configured to execute a function performed by the first network element in the MEC information acquisition method.
  • FIG. 12 exemplarily shows a schematic structural diagram of the device. As shown in the figure, the device may include a receiving unit 1201 and a sending unit 1202. Further, the device may further include a processing unit 1203.
  • the sending unit 1202 is configured to send information of the MEC corresponding to the target reference information to the second network element.
  • the target reference information includes at least one of target position information and target capability information.
  • the receiving unit 1201 is further configured to: receive the MEC First registration information; wherein the first registration information includes addressing information of the MEC and attribute description information of the MEC.
  • the attribute description information includes one or more of the following information: application programming interface API information provided by the MEC, location information of the MEC, and service area information of the MEC , The capability description information of the MEC, and the domain identifier of the MEC.
  • the first network element is a public API architecture core function CCF, and the second network element is a mobile edge computing MEC; or the first network element is a CCF, and the second The network element is a CCF, and the domain to which the first network element belongs is different from the domain to which the second network element belongs; or, the first network element is a MEC proxy function entity, and the second network element is a MEC; or The first network element is a MEC proxy function entity, the second network element is a MEC proxy function entity, and the domain to which the first network element belongs is different from the domain to which the second network element belongs; or The first network element is a network open function network element NEF, and the second network element is MEC; or, the first network element is NEF, the second network element is NEF, and the domain to which the first network element belongs Different from the domain to which the second network element belongs.
  • the sending unit 1202 further And configured to send the second registration information of the MEC to a third network element, where the second registration information is used to register the information of the MEC in the third network element, and the third network element belongs to The domain is different from the domain to which the first network element belongs, and the second registration information includes part or all of the MEC's addressing information and the MEC's attribute description information.
  • the first network element further includes a processing unit, configured to: the MEC attribute description information includes location information of the MEC, and when determining the MEC according to the location information of the MEC When the MEC is located in a domain to which the first network element belongs, converting the location information of the MEC into general location information; the location information sent by the sending unit 1202 to the third network element is the general location information; And / or, the attribute description information of the MEC includes service area information of the MEC, and when it is determined that the service area of the MEC is located in a domain to which the first network element belongs according to the service area information of the MEC, Converting the service area information of the MEC into general service area information; the service area information sent by the sending unit 1202 to the third network element is the general service area information.
  • the MEC attribute description information includes location information of the MEC, and when determining the MEC according to the location information of the MEC When the MEC is located in a domain to which the first network element belongs, converting the location information of the M
  • the first network element is a CCF
  • the third network element is a CCF
  • a domain to which the first network element belongs is different from a domain to which the third network element belongs.
  • the information of the MEC includes information of a CCF corresponding to the MEC.
  • the information of the MEC includes addressing information of the MEC and attribute description information of the MEC.
  • an embodiment of the present application further provides a MEC information acquisition device, which is configured to execute a function performed by the first network element in the MEC information acquisition method.
  • FIG. 13 exemplarily shows a structural schematic diagram of the device. As shown in the figure, the device may include a receiving unit 1301 and a sending unit 1302.
  • the receiving unit 1301 is configured to receive information of an MEC corresponding to the target reference information from the first network element.
  • the target reference information includes at least one of target position information and target capability information.
  • the information of the MEC includes information of a CCF corresponding to the MEC.
  • the information of the MEC includes addressing information of the MEC and attribute description information of the MEC.
  • the attribute description information of the MEC includes one or more of the following information: service area information of the MEC, capability description information of the MEC, and application programming provided by the MEC Interface API information, location information of the MEC, and domain identifier of the MEC.
  • the first network element is a public API architecture core function CCF
  • the second network element is a mobile edge computing MEC
  • the first network element is a CCF
  • the second network element is a CCF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs;
  • the first network element is a MEC proxy function entity, and the second network element is a MEC;
  • the first network element is a MEC proxy function entity
  • the second network element is a MEC proxy function entity
  • the domain to which the first network element belongs is different from the domain to which the second network element belongs;
  • the first network element is a network open function network element NEF, and the second network element is a MEC; or
  • the first network element is an NEF
  • the second network element is an NEF
  • a domain to which the first network element belongs is different from a domain to which the second network element belongs.
  • the attribute description information of the MEC includes API information provided by the MEC;
  • the sending network element is further configured to send an API call request to the MEC corresponding to the target reference information according to the API information;
  • the receiving network element is further configured to receive an API call response sent by the MEC corresponding to the target reference information.
  • the second network element is a MEC
  • the sending network element is further configured to: send an API discovery request to the MEC corresponding to the target reference information, or send the API discovery request to the MEC corresponding to the target reference information;
  • the CCF corresponding to the MEC corresponding to the reference information sends an API discovery request;
  • the receiving network element is further configured to receive an API discovery response, where the API discovery response includes API information provided by the MEC.
  • the sending unit 1302 is further configured to:
  • the registration information of the MEC includes addressing information of the MEC and attribute description information of the MEC.
  • an embodiment of the present application further provides a MEC information acquisition device, which is configured to execute a function performed by the first network element in the MEC information acquisition method.
  • FIG. 14 exemplarily shows a schematic structural diagram of the device. As shown in the figure, the device may include a receiving unit 1401 and a sending unit 1402. Further, the device may further include a processing unit 1403.
  • the receiving unit 1401 is configured to receive first registration information from the MEC, where the first registration information includes addressing information of the MEC and attribute description information of the MEC;
  • the sending unit 1402 is configured to send second registration information to a second network element according to the first registration information, and a domain to which the first network element belongs is different from a domain to which the second network element belongs.
  • the attribute description information of the MEC includes one or more of the following information: service area information of the MEC, capability description information of the MEC, and application programming provided by the MEC Interface API information, location information of the MEC, and domain identifier of the MEC.
  • the first network element further includes a processing unit 1403, configured to:
  • the attribute description information of the MEC includes the location information of the MEC.
  • the location information of the MEC is converted into General location information; the location information sent by the sending unit to the third network element is the general location information; and / or
  • the attribute description information of the MEC includes service area information of the MEC.
  • the first network element When it is determined that the MEC is located in a domain to which the first network element belongs according to the service area information of the MEC, the first network element will The service area information of the MEC is converted into general service area information; and the sending unit sends the service area information to the third network element as the general service area information.
  • the embodiment of the present application provides a MEC information acquisition device 1500, which is used to implement the function performed by the first network element in the foregoing method embodiment.
  • the hardware structure of the network device 1500 includes at least one processor 1501, a communication bus 1502, a memory 1503, and at least one communication interface 1504.
  • the processor 1501 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program of the solution of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 1502 may include a path for transmitting information between the aforementioned components.
  • the communication interface 1504 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 1503 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.
  • the memory 1503 is configured to store application program code for executing the solution of the present application, and the processor 1501 controls execution.
  • the processor 1501 is configured to execute application program code stored in the memory 1503, thereby implementing the MEC information acquisition method provided by the foregoing embodiment of the present application.
  • the processor 1501 may perform related functions in the MEC information acquisition method provided by the foregoing embodiments of the present application.
  • the communication interface 1504 is responsible for communicating with other devices or communication networks. Examples do not specifically limit this.
  • the processor 1501 may include one or more CPUs.
  • the network device may include multiple processors.
  • Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • an embodiment of the present application provides a MEC information acquisition device 1600, which is used to implement the function performed by the second network element in the foregoing method embodiment.
  • the hardware structure of the network device 1600 may be as shown in FIG. 16 and includes at least one processor 1601, a communication bus 1602, a memory 1603, and at least one communication interface 1604.
  • the processor 1601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program of the solution of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 1602 may include a path for transmitting information between the aforementioned components.
  • the communication interface 1604 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 1603 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.
  • the memory 1603 is configured to store application program code for executing the solution of the present application, and the processor 1601 controls execution.
  • the processor 1601 is configured to execute application program code stored in the memory 1603, so as to implement the MEC information acquisition method provided by the foregoing embodiment of the present application.
  • the processor 1601 may perform related functions in the MEC information acquisition method provided by the foregoing embodiments of the present application, and the communication interface 1604 is responsible for communicating with other devices or communication networks. Examples do not specifically limit this.
  • the processor 1601 may include one or more CPUs.
  • the network device may include multiple processors.
  • Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • An embodiment of the present application further provides a storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the method according to any one of the first aspect to the third aspect is implemented.
  • this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开了一种MEC信息获取方法及装置，包括：第一网元接收来自第二网元的目标参考信息；所述第一网元向所述第二网元发送所述目标参考信息对应的MEC的信息。上述方法实现了MEC的发现过程，能够使得第二网元根据获取的MEC的信息与该MEC进行通信，从而利用该MEC的能力实现其自身无法满足的服务需求。进一步地，第二网元获取到的MEC的信息也可以与第二网元属于不同的域，例如属于不同的运营商，实现了跨运营商调用MEC的方案，满足了第三方应用能够为不同运营商的用户提供服务的需求。

Description

一种MEC信息获取方法及装置
本申请要求在2018年7月16日提交中国专利局、申请号为201810780270.7、发明名称为“一种MEC信息获取方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种移动边缘计算(mobile edge computing，MEC)信息获取方法及装置。
背景技术
MEC将无线网络和互联网技术有效融合在一起，在无线网络侧增加计算、存储、处理等功能，构建了开放式平台以植入应用，并通过无线应用编程接口(application programming interface，API)实现无线网络与业务服务器之间的信息交互，对无线网络与业务进行融合。面向业务层面(物联网、视频、医疗、零售等)，MEC可向行业提供定制化、差异化服务，进而提升网络利用效率和增值价值。
MEC通常部署在无线接入网(radio access network，RAN)上，或者部署与RAN较近的位置，以减少数据传输时延。因此，一个MEC的能够提供服务的范围以及服务的用户，会受到接入网的能够提供服务的范围以及服务的用户的限制，而无法满足第三方应用的需求。
发明内容
本申请提供一种MEC信息获取方法及装置，用于实现MEC的发现过程。
第一方面，本申请提供了一种MEC信息获取方法，该方法包括：
第一网元接收来自第二网元的目标参考信息；所述第一网元向所述第二网元发送所述目标参考信息对应的MEC的信息。
上述方法实现了MEC的发现过程，能够使得第二网元根据获取的MEC的信息与该MEC进行通信，从而利用该MEC的能力实现其自身无法满足的服务需求。进一步地，第二网元获取到的MEC的信息也可以与第二网元属于不同的域，例如属于不同的运营商，实现了跨运营商调用MEC的方案，满足了第三方应用能够为不同运营商的用户提供服务的需求。
在一种可能的实现方式中，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
在一种可能的实现方式中，在所述第一网元向所述第二网元发送所述MEC的信息之前，还包括：所述第一网元接收所述MEC的第一注册信息；其中，所述第一注册信息包括所述MEC的寻址信息，所述第一注册信息还包括所述MEC的属性描述信息。
在一种可能的实现方式中，所述属性描述信息包括以下信息中的一种或多种：所述 MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的服务区域信息，所述MEC的能力描述信息，以及所述MEC的域标识。
在一种可能的实现方式中，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者
所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者
所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
在一种可能的实现方式中，当所述MEC所属的域与所述第一网元所属的域相同时，在所述第一网元接收所述第一注册信息之后，还包括：所述第一网元向第三网元发送所述MEC的第二注册信息，所述第二注册信息用于将所述MEC的信息注册在所述第三网元中，所述第三网元所属的域与所述第一网元所属的域不同，所述第二注册信息中包括所述MEC的寻址信息，以及所述MEC的属性描述信息的部分或全部。
在一种可能的实现方式中，当所述MEC的属性描述信息中包括所述MEC的位置信息时，所述方法还包括：所述第一网元在判断所述MEC的位置信息为所述第一网元所属域中位置信息时，所述第一网元将所述MEC的位置信息转换为通用位置信息，并将所述通用位置信息发送给所述第三网元；和/或，当所述MEC的属性描述信息中包括所述MEC的服务区域信息时，所述方法还包括：所述第一网元在判断所述MEC的服务区域信息为所述第一网元所属域中的位置信息时，所述第一网元将所述MEC的服务区域信息转换为通用服务区域信息，并将所述通用服务区域信息发送给所述第三网元。
在一种可能的实现方式中，所述第一网元为CCF，所述第三网元为CCF，且所述第一网元所属的域与所述第三网元所属的域不同。
在一种可能的实现方式中，所述MEC的信息包括所述MEC对应的CCF的信息。
在一种可能的实现方式中，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
第二方面，本申请实施例提供了一种移动边缘计算MEC信息获取方法，包括：
第二网元向第一网元发送目标参考信息；
所述第二网元接收来自所述第一网元的与所述目标参考信息对应的MEC的信息。
在一种可能的实现方式中，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
在一种可能的实现方式中，所述MEC的信息包括所述MEC对应的CCF的信息。
在一种可能的实现方式中，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
在一种可能的实现方式中，所述MEC的属性描述信息包括以下信息中的一种或多种：所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
在一种可能的实现方式中，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者
所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者
所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
在一种可能的实现方式中，所述第二网元为MEC；当所述MEC的属性描述信息包括所述MEC提供的API信息时，所述方法还包括：所述第二网元根据所述API信息向与所述目标参考信息对应的MEC发送API调用请求；所述第二网元接收与所述目标参考信息对应的MEC发送的API调用响应。
在一种可能的实现方式中，所述第二网元为MEC；当所述MEC的属性描述信息不包括所述MEC提供的API信息时，所述方法还包括：所述第二网元向所述MEC或与所述MEC对应的CCF发送API发现请求；所述第二网元接收API发现响应，所述API发现响应中包括所述MEC提供的API信息。
在一种可能的实现方式中，所述方法还包括：所述第二网元向所述第一网元发送MEC的注册信息，所述MEC的注册信息中包括MEC的寻址信息以及所述MEC的属性描述信息。
第三方面，本申请实施例提供了一种MEC信息获取方法，包括：
第一网元接收来自MEC的第一注册信息，所述第一注册信息包括所述MEC的寻址信息以及所述MEC的属性描述信息；
第一网元根据所述第一注册信息，向第二网元发送第二注册信息，所述第一网元所属域与所述第二网元所属域不同。
在一种可能的实现方式中，所述MEC的属性描述信息包括以下信息中的一种或多种：所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
在一种可能的实现方式中，当所述MEC的属性描述信息中包括所述MEC的位置信息时，所述方法还包括：所述第一网元在判断所述MEC的位置信息为所述第一网元所属域中位置信息时，所述第一网元将所述MEC的位置信息转换为通用位置信息，并将所述通用位置信息发送给所述第三网元；和/或，当所述MEC的属性描述信息中包括所述MEC的服务区域信息时，所述方法还包括：所述第一网元在判断所述MEC的服务区域信息为所述第一网元所属域中的位置信息时，所述第一网元将所述MEC的服务区域信息转换为通用服务区域信息，并将所述通用服务区域信息发送给所述第三网元。
第四方面，本申请实施例提供了一种MEC信息获取装置，该装置包括接收单元和发送单元，进一步地，还可以包括处理单元。该接收单元、发送单元以及处理单元，用于执行如第一方面中任一项所述的方法。
第五方面，本申请实施例提供了一种MEC信息获取装置，该装置包括发送单元和接 收单元，进一步地，还可以包括处理单元。该接收单元、发送单元以及处理单元，用于执行如第二方面中任一项所述的方法。
第六方面，本申请实施例提供了一种MEC信息获取装置，该装置包括接收单元和发送单元，进一步地，还可以包括处理单元。该接收单元、发送单元以及处理单元，用于执行如第三方面中任一项所述的方法。
第七方面，本申请实施例提供一种存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面至第三方面任一项所述的方法。
附图说明
图1(a)和图1(b)为本申请提供的适用本申请实施例的一种网络架构；
图2为本申请提供的MEC架构示意图；
图3为本申请提供的适用本申请实施例的另一种网络架构；
图4为本申请提供的MEC信息获取方法流程示意图；
图5(a)-图5(c)为本申请提供的具体实施例之一；
图6(a)-图6(c)为本申请提供的具体实施例之二；
图7(a)-图7(c)为本申请提供的具体实施例之三；
图8(a)-图8(d)为本申请提供的具体实施例之四；
图9为本申请实施例提供的另一种MEC信息获取方法流程示意图；
图10为本申请实施例提供的又一种MEC信息获取方法流程示意图；
图11为本申请实施例提供的具体实施例之五；
图12为本申请实施例提供的MEC信息获取装置的结构示意图之一；
图13为本申请实施例提供的MEC信息获取装置的结构示意图之二；
图14为本申请实施例提供的MEC信息获取装置的结构示意图之三；
图15为本申请实施例提供的MEC信息获取装置的结构示意图之四；
图16为本申请实施例提供的MEC信息获取装置的结构示意图之五。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
将MEC部署在RAN上或者部署与RAN较近的位置，能够减少数据传输时延，提高响应速度。然而，由于MEC的部署与RAN相关，也使得MEC的服务区域以及服务用户受到了限制。例如，若将MEC部署在区域A的基站上，该MEC可以为第三方应用在区域A中提供服务，但其服务范围可能无法覆盖区域B，无法满足第三方应用为区域B的用户提供业务的需求。又例如，若将MEC部署在运营商A的基站上，那么该MEC可能无法为本地运营商B的用户提供服务。
由于一个MEC的能够提供服务的范围以及服务的用户受限，因此一个MEC可能无法满足第三方应用的业务需求，可能需要多个MEC协调完成。然而，在传统的技术方案中，还没有获取其他MEC信息的方法，因而无法实现多个MEC协调完成第三方应用服务需求。
为了解决上述技术问题，本申请实施例提供了一种MEC信息获取方法。
图1(a)和图1(b)示例性的给出了一种能够适用本申请实施例提供的MEC信息获取方法的网络架构示意图。如图1(a)所示的场景中，可以在公共陆地移动网络(public land mobile network，PLMN)网络域内上部署3GPP通用API架构核心功能(CAPIF core function，CCF)，该PLMN运营商同时作为API提供方(service provider)，将API注册到CCF上，第三方的API提供方可以将其自身的API共享、发布给另一个API提供方。如图1(b)所示的场景中，可以在两个API提供方上均部署CCF，即，在MEC中部署CCF逻辑单元。其中一个API提供方可以通过CCF将自身提供API的能力信息发布给另一API提供方，以实现API共享。
其中，各个功能实体的描述如下：
1)API调用实体(API invoker)，也可以称为API调用者，一般为与PLMN的运营商签定了服务协议的第三方应用，如机器到机器(machine-to-machine，M2M)的应用、物联网(internet of things，IoT)应用、车联网(vehicle to everything，V2X)应用等，这些应用可以运行在终端设备中，也可以运行在网络设备中。API调用实体可以是PLMN网络中的设备，如4G通信系统中的移动管理实体(mobility management entity，MME)，RAN，略与计费控制功能(policy and charging control function，PCRF)等，也可以是5G通信系统中的接入和移动性管理功能(access and mobility management，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、策略控制功能(policy control function，PCF)、应用功能(application function，AF)等。API调用实体和PLMN运营商处于同一个信任域。API调用实体支持以下能力：支持API调用实体的认证，通过认证API调用实体的标识及其他信息；支持和CAPIF的相互鉴权；访问API之前获取授权；发现API；调用API等。
2)CCF具有以下功能：基于API调用实体的标识和其他信息认证API调用实体；支持和API调用实体的相互鉴权；在API调用实体访问API之前向API调用实体提供授权；发布、存储和支持API的发现；基于PLMN运营商的策略负责API的访问控制；存储API调用的日志，并提供给授权实体；检测API的调用；API调用实体的注册；存储配置策略等。
3)API开放功能(API exposing function，AEF)：API调用实体调用API的入口，具有以下功能：基于API调用实体的标识和CCF提供的其他信息对API调用实体进行认证；确认CCF提供的授权；将API日志同步到CCF上。
4)API发布功能(API publishing function)：提供API发布的功能，以便API调用实体可以发现API。
5)API管理功能(API management function)：提供对API的管理，具体包括以下功能：对CCF提供的API调用日志进行审计；监控CCF报告的事件；向API配置API提供方的策略；检测API的状态；注册API调用实体。
在图1(a)和图1(b)所示的网络架构中，可以将CCF与API提供域(API provider domain)中的功能实体(API开放功能，API发布功能和API管理功能)看作是MEC，或将CCF与API开放功能和API发布功能看作MEC，或将CCF与AEF看作MEC，或者，也可以将AEF看作MEC。
图2示例性的给出了又一种能够适用本申请实施例提供的MEC信息获取方法的网络架构示意图。
其中，网络能力开放功能网元(network exposure function，NEF)，可以将移动通信网络的提供网络能力开发给移动通信网络的内部网元(如SMF，AMF)或者外部第三方应用，如V2X应用，IoT应用等。
网络功能仓库网元(NF repository gunction，NRF)，用于维护移动通信网络的网元信息(包括网元类型，网元标识，网元所在切片，网元提供的服务等)，还支持服务发现功能，即，向请求发现网元或者服务的请求者提供满足其业务需求的网元或者服务信息。
其他网元的功能此处不再详述，具体可以参见相关通信标准协议。
图3为本申请实施例提供的一种MEC架构示意图，如图所示，MEC架构可以包括：
移动边缘平台(mobile edge platform)：于特定移动边缘主机虚拟基础设施上运行各类移动边缘应用所需的功能集。其可提供并消费各种移动边缘服务，并可为自身提供多种移动边缘服务。如支持服务注册、服务发现、传输规则控制、DNS解析等功能。
移动边缘应用(mobile edge application，ME app)：可在移动边缘系统里的移动边缘主机(mobile edge host)上实例化的应用。其具备潜在地提供或消费移动边缘服务的潜力。
移动边缘服务(mobile edge service，ME service)：通过移动边缘平台自身或某个移动边缘应用所提供的服务，一般可以以API的方式提供给移动边缘应用。
此外，在本申请实施例中，将网元A的信息注册(register)到网元B上，也可以理解为，将网元A的信息发布(publish)给网元B，进一步地，网元B对网元A的信息进行保存。
其中，图3所示的示意图中N1、N2、N4、Nnef等表示接口，其它涉及到的网元分别为：用户设备(User Equipment，UE)、接入网(Access Network，AN)、用户面功能实体(User Plane Function，UPF)、数据网络(Data Network，DN)、验证服务器功能(Authentication Server Function，AUSF)、接入和移动性管理功能实体(Access and Mobility Management Function，AMF)、会话功能管理实体(Session Management Function，SMF)、网络暴露实体(Network Exposure Function，NEF)、网络贮存功能实体(Network Repository Function，NRF)、策略控制功能实体(Policy Control Function，PCF)、统一数据管理(Unified Data Management，UDM)、应用功能(Application Function，AF)。
下面结合附图详细介绍本申请实施例提供的MEC信息获取方法。
参见图4，该方法可以包括以下步骤：
步骤401、第一网元接收来自第二网元的目标参考信息。
其中，目标参考信息可以用于第一网元寻找与目标参考信息对应的MEC的信息。目标参考信息可以包括目标位置信息和目标能力信息中的至少一种。
在一种可能的实现方式中，目标参考信息可以携带在第二网元向第一网元发送的消息中。例如，该消息可以是MEC发现请求(MEC discovery request)，或服务发现请求(service discovery request)或API发现请求(API discovery request)消息中，下面以目标参考信息携带于MEC发现请求中为例进行说明。
第二网元可以发送MEC发现请求，该请求中携带有上述目标参考信息，以使第一网元能够将与目标参考信息对应的MEC的信息发送给第二网元。具体地，目标参考信息可以包括目标位置信息和/或目标能力信息。例如，第三方应用部署在MEC1上，MEC1对应的服务区域为区域A，MEC1能够为第三方应用在区域A提供服务(例如向区域A中的支 持V2X的车辆广播V2X消息)；然而，该第三方应用还有部分用户位于区域B，为了满足该第三方应用在区域B实现业务覆盖的需求，那么MEC1可以发送MEC发现请求，该请求中包括目标位置信息：区域B的指示信息，以表示MEC1请求获取能够为区域B提供服务的一个或多个MEC的信息。又例如，MEC1能够提供V2X类型的服务，而第三方应用需要提供V2X类型的服务，此外，还需要提供广播服务，那么MEC1可以发送MEC发现请求，该请求中包括目标能力信息：广播服务的指示信息，用于表示MEC1请求获取能够提供广播服务的MEC的信息。再例如，第三方应用部署在中国移动的网络中的MEC1上，MEC1对应服务区域A，而该第三方应用还需要为区域A中的中国联通的用户提供服务，那么MEC1可以发送MEC发现请求，该请求中包括目标位置信息：区域A的指示信息，以及中国联通的域标识信息，用于表示请求获取能够为区域A的中国联通用户提供服务的MEC的信息。其中，区域A的指示信息可以为区域A的标识，也可以为区域A的经纬度信息，也可以是其他能够对应区域A信息。当然，MEC发现请求中也同时包含有目标位置信息和目标能力信息，例如MEC1需要获取能够为区域A提供广播服务的MEC的信息，那么MEC1发送的目标参考信息中可以包括区域A的指示信息和广播服务的指示信息。
应当理解，上述目标位置信息，表示第二网元需要获取能够为该目标位置提供服务的MEC的信息，但并不表示请求获取的MEC应被部署在该目标位置上。例如，MEC1被部署在区域A上，但MEC的服务区域包括区域A、区域B和区域C；当MEC2请求获取能够为目标区域B提供服务的MEC时，虽然MEC1没有位于区域B中，但MEC1能够为区域B提供服务，故MEC1仍符合MEC2的要求。
步骤402、第一网元向第二网元发送与目标参考信息对应的MEC的信息。
其中，当目标参考信息为目标位置信息时，与目标参考信息对应的MEC可以指的是目标位置信息对应的目标区域内的MEC；或者，当目标参考信息为目标能力信息时，与目标参考信息对应的MEC可以指的是具备目标能力信息对应的目标能力的MEC；或者，当目标参考信息和目标能力信息时，与目标参考信息对应的MEC可以指的是在目标位置信息对应的目标区域内，具备目标能力信息对应的目标能力的MEC，不予限制。
在上述步骤中，第一网元可以根据目标参考信息，以及第一网元获取的MEC的信息，确定符合该目标参考信息的MEC，并将确定出的MEC的信息发送给第二网元。
具体地，第一网元中获取的一个或者多个MEC的信息，可以是在第一网元启用时通过预配的方式保存在第一网元中的，或者由人工输入到第一网元中的，也可以是其他网元将获取到的MEC信息发送给第一网元的。
在一种可能的实现方式中，可以在部署新的MEC时，或者MEC提供的API信息发生变化时，或者其他触发事件发生时，MEC主动发送其自身的信息给第一网元，以实现将MEC的信息在第一网元中注册(即第一网元获取到MEC的信息)。当然，在层级部署的网络中，MEC也可以向将其注册信息发送给其它网元，再由其他网元发送给第一网元，以完成MEC的信息在第一网元中注册。例如，在层级部署CCF的网络架构中，MEC1可以将其注册信息发送给与位于MEC1上的CCF1(部署层级位置较低)，然后由CCF1将MEC1的注册信息发送给该网络中部署层级位置较高的CCF2，以实现将MEC1的信息注册到CCF2中。
例如，MEC可以向第一网元发送MEC注册请求，该注册请求中包括该MEC的寻址 信息，以及该MEC的属性描述信息。
其中，MEC的寻址信息可以是MEC的标识，或者是在该MEC上部署的CCF的标识等。
其中，MEC的属性描述信息可以包括以下信息中的一种或多种：
MEC提供的API信息：MEC可以为第三方应用提供“服务”，该“服务”可以理解为实现某种特定功能的网络资源或者程序，例如函数，功能库，包(packet)等，第三方应用可以调用API从而实现相应服务。其中，API信息可以包括API的标识、API是否可以共享、API类型以及API的服务区域信息等。
MEC的域标识：表示该MEC所属的域。以MEC的寻址信息为MEC的标识为例，在一些场景中，MEC的标识可以唯一标识一个MEC；而在另一些场景中，MEC的标识在其所属的域中能够唯一标识一个MEC，若需要全局唯一标识一个MEC，则通过“MEC的标识+域标识”实现。其中，MEC所属的域可以指CAPIF提供域、CAPIF系统域，例如MEC可以为CAPIF架构中的CCF、AEF、APF以及AMF的集合，可以将CAPIF的提供域、系统域作为该MEC所属的域；或者，MEC所属的域也可以指PLMN信任域、PLMN网络域，例如，通常是将MEC部署在某个PLMN中，那么可以将该PLMN的信任域、网络域作为该MEC所属的域；又或者，MEC所属的域还可以指API服务提供域，等等。相应的，域标识可以是CAPIF ID、PLMN ID、API提供商的ID，也可以是PLMN网络域名(如@cmcc.com)、API服务提供域名等等。
MEC的位置信息：通常情况下，位于区域A的MEC能够为区域A的用户提供服务，因此，MEC的位置信息也可以从一定程度上反映出MEC的服务区域信息。具体的，MEC的位置信息，可以是MEC的通用位置信息，即不同域中的网元均能够识别的信息，如MEC所处的经纬度、MEC所在的行政区域、路边单元(roadside unit，RSU)的服务区域、RSU的标识(RSU可以由第三方提供，可以通过RSU的标识确定RSU所在的位置区域)等。或者，MEC的位置信息也可以是该MEC所属的域中的位置信息，例如，MEC所在的小区标识等。
MEC的服务区域信息：表示该MEC的服务区域。同样的，MEC服务区域信息可以是通用区域信息，如服务区域的经纬度范围、行政区域等；也可以是该MEC所属的域中的区域信息，例如MEC提供服务的小区、追踪区域、注册区域等，可以用小区标识列表、追踪区域标识列表、注册区域标识列表等表示。
MEC的能力描述信息：表示该MEC提供的服务类型。例如，MEC1中提供的API包括：提供广播服务的API_1以及提供流量计费服务的API_2，那么MEC的属性描述信息中可以包括广播服务、流量计费服务等能力描述信息。具体地，该能力描述信息可以是文本标签，如广播服务/Broadcast，计费/Charging；也可以是预先定义的枚举值，如001表示广播服务/Broadcast，002表示计费/Charging(当信息接收方为该MEC所在域之外的网元时，还需要提供完整的枚举值和能力描述的映射)，以方便其他网元调用。
第一网元在接收到上述MEC注册信息后，可以将MEC的信息存储起来，以便在后续接收到MEC发现请求后，从存储的MEC的信息中查找是否存在符合目标参考信息的MEC的信息。
进一步地，第一网元在接收到MEC注册信息后，还可以将MEC的注册信息发送给其他网元，以实现将MEC的信息注册在其他网元中，以便提高其他网元在接收到MEC发现 请求后的响应速度。例如，属于PLMN_1的MEC1向PLMN_1中的CCF1(第一网元)发送第一注册，该第一注册信息中包括MEC1的寻址信息以及MEC的属性描述信息，以实现将MEC1的信息注册在CCF1中。CCF1向PLMN_2中的CCF2发送第二注册信息，该第二注册信息中包括MEC1的寻址信息以及MEC的属性描述信息。其中，第二注册信息中包含的属性描述信息，可以少于第一注册信息中包含的属性描述信息，例如，第一注册信息中的属性描述信息包括MEC1提供的API的详细信息、MEC1的能力描述信息、MEC1的位置信息、MEC1的服务区域信息、MEC1的域标识，而第二注册信息中的属性描述信息可以仅包括MEC1的能力描述信息和MEC1的服务区域信息。
此外，若MEC1向CCF1发送了MEC1的位置信息(和/或服务区域信息)，可以是通用位置信息或PLMN_1中的位置信息。然而，若为PLMN_1中的位置信息(如小区标识等)，那么该位置信息可能无法被属于PLMN_2的CCF2识别。因此，CCF1在向CCF2发送MEC第二注册信息之前，可以先判断MEC1的位置信息(和/或服务区域信息)是否为PLMN_1中的位置信息，若是，则CCF1可以将该位置信息转换为通用位置信息，如行政区域等，然后将转换后的通用位置信息携带在第二注册信息中发送给CCF2。
在另一种可能的实现方式中，若第一网元中没有存储MEC的信息，或者，第一网元中存储的MEC的信息均与目标参考信息不相符，那么第一网元还可以向其他网元发送上述目标参考信息，从而实现从其他网元处获取符合目标参考信息的MEC的信息。
例如，第一网元中没有预先存储有MEC的信息，MEC的信息均注册在网络功能存储功能(NF repository function，NRF)中；那么第一网元在接收到携带有目标参考信息的MEC发现请求后，可以向NRF发送携带上述目标参考信息的MEC发现请求，从而实现从NRF处获取符合上述目标参考信息的MEC的信息。
又例如，若位于区域A、属于PLMN_1的MEC1(第二网元)，向PLMN_1中的CCF1(第一网元)发送MEC发现请求，请求获取属于PLMN_2的、能够为区域A的用户提供服务的MEC。然而，第一网元中仅存储有PLMN_1中的MEC的信息，即，CCF1中没有存储有符合目标参考信息的MEC的信息，根据商业签约关系以及预设的策略信息，CCF1可以向PLMN_2中的CCF2发送MEC发现请求，以实现从CCF2处获取符合目标参考请求的CCF的信息，并将从CCF2处获取到的MEC的信息发送给MEC1。
在一些实施例中，上述步骤402中第一网元发送的MEC的信息，可以包括MEC的寻址信息(例如MEC的标识)以及MEC的属性描述信息。具体地，第一网元发送的MEC的属性描述信息，可以是第一网元存储的或第一网元获取到的该MEC属性描述信息中的部分或全部。例如，第一网元存储的或第一网元从其他网元处获取到的属性描述信息包括MEC提供的API的详细信息、MEC1的能力描述信息、MEC1的位置信息、MEC1的服务区域信息、MEC1的域标识，而第一网元发送给第二网元的属性描述信息可以仅包括MEC1的能力描述信息和MEC1的服务区域信息。
在另外一些实施例中，上述步骤402中第一网元发送的MEC的信息，也可以是该MEC对应的CCF的信息。例如，在如图5(a)所示的场景中，MEC_1中设置了具有CCF_1功能的逻辑单元。在MEC_1注册过程中，CCF_1从MEC_1处获取到MEC_1的标识以及MEC_1的属性描述信息，然后CCF_1向CCF_2(PLMN_1中最高级别的CCF)发送MEC_1的注册信息，其中该注册信息包括MEC_1的信息和/或CCF_1的信息。例如，CCF_1可以向CCF_2发送该CCF_1的标识以及CCF_1的属性描述信息，然而，由于CCF_1是设 置在MEC_1中的逻辑单元，因此，CCF_1的属性描述信息描述的仍是MEC_1的信息。在MEC发现过程中，若CCF_2接收到了MEC发现请求，且MEC_1的信息与该发现请求中目标参考信息相符，那么CCF_2发送的MEC发现响应中可以携带CCF_1的信息，以使请求者可以根据CCF_1的信息进一步获取MEC_1的信息，具体可以获取该MEC_1提供的API的信息。
在上述步骤402之后，第二网元可以根据获取到的MEC的信息，调用该MEC的API，从而实现该MEC的为第三方应用提供满足其服务需求的服务。具体地，若第二网元获取到的MEC的信息中包括该MEC提供的API信息，那么第二网元可以根据所需的服务类型、服务区域，调用相应的API，即，向该MEC发送API调用请求，该请求中包括API标识。若第二网元获取到的MEC的信息中不包括MEC提供的API信息，那么第二网元可以向该MEC(或与该MEC对应的CCF)发送API发现请求，已请求获取该MEC提供的API信息；在获取到API信息后向MEC发送API调用请求。
在本申请上述实施例中，第二网元通过与第一网元之间的交互，实现了获取MEC的信息，即，实现了MEC的发现过程，能够使得第二网元根据获取的MEC的信息与该MEC进行通信，从而利用该MEC的能力实现为第三方应用提供满足其服务需求。进一步地，第二网元获取到的MEC的信息也可以与第二网元属于不同的域，例如属于不同的运营商，实现了跨运营商调用MEC的方案，满足了第三方应用能够为不同运营商的用户提供服务的需求。
为了便于理解本申请上述实施例，下面结合附图进行举例说明。在以下实施例中，以域的概念为PLMN进行举例说明，当然，下述实施例中的PLMN也可以替换为其他域的概念。
图5(a)为能够适用本申请上述实施例的一种网络部署场景，如图所示，在PLMN_1中部署有MEC_1(第一网元)以及最高级别的CCF(即CCF_2，第二网元)，在MEC_1中设置了具有CCF功能的逻辑单元CCF_1；在PLMN_2中部署有MEC_2以及最高级别的CCF(即CCF_4)，此外，在MEC_2中设置了具有CCF功能的逻辑单元CCF_3。
在如图5(a)所示的场景下，MEC信息获取方法的流程示意图可以如图5(b)所示：
步骤501、MEC_2向CCF_3发送MEC注册信息。
该注册信息中可以包括MEC_3标识、MEC_3的服务区域信息、MEC_3提供的API信息以及PLMN_2的标识。该注册信息中包括API信息，因此，该注册信息可以携带在API发布请求(API publish request)中发送。或者，也可以在MEC发布请求(MEC publish request)中发送，此时MEC_2可以是CAPIF中AEF的一个实例。
步骤502、CCF_3向MEC_2发送MEC注册响应。
其中，MEC注册响应用于对MEC_2发送的注册信息进行应答，该响应中可以进一步包含注册成功或者注册失败的指示信息。
步骤503、CCF_3向CCF_4发送MEC注册请求。
其中，该请求中可以携带CCF粒度的信息，即携带CCF_3的信息(例如，标识、位置信息、服务区域信息、PLMN_2的标识等)以及上述API信息；也可以携带MEC粒度的信息，即携带MEC_2标识、MEC_2的服务区域信息、MEC_2提供的API信息以及PLMN_2的标识；当然，也可以将上述CCF_3的信息以及MEC_2信息全部发送给CCF_4。
由于PLMN_1与PLMN_2已存在商业签约关系，允许MEC的信息相互注册，执行步 骤504。
步骤504、CCF_4向CCF_2发送MEC注册信息。
具体地，该注册信息中可以包括上述步骤503中携带的CCF_3的信息。步骤504中发送的CCF_3的信息可以少于步骤503中发送的信息。
步骤505、CCF_2向CCF_4发送MEC注册响应。
其中，该MEC注册响应用于对CCF_4发送的注册信息进行应答，该响应中可以包含注册成功或者注册失败的指示信息。
步骤506、CCF_4向CCF_3发送MEC注册响应。
其中，该MEC注册响应用于对CCF_3发送的注册信息进行应答，该响应中可以包含注册成功或者注册失败的指示信息。
其中，步骤506的也可以在步骤503之后就执行。
相应地，MEC_1也可以按照上述流程完成在CCF_1、CCF_2以及CCF_4上的注册过程，此处不再赘述。
步骤507、MEC_1向CCF_1发送API发现请求。
示例性地，MEC_1根据第三方应用的业务覆盖区域需求，确定调用PLMN_2中能够为服务区域A提供服务的API为第三方应用服务，则执行步骤507。可选地，确定调用PLMN_2中能够为服务区域A提供服务的API为第三方应用服务这一步骤，也可以由CCF_1或CCF_2执行。
其中，该请求中可以包括目标参考信息。本实施例中以目标参考信息为服务区域A的信息和PLMN_2的标识为例进行说明，此时，该请求消息用于表示MEC_1请求调用PLMN_2中的能够为区域A提供服务的API。此时MEC_1可是看作CAPIF中API请求者的一个实例。
进一步的，上述API发现请求中还可以携带MEC_1的标识，作为API请求者的标识。
若CCF_1确定不足以提供与目标参考信息对应的API，例如CCF_1根据服务区域A的信息和PLMN_2的标识确定需要其他MEC协同处理，则执行步骤508。
步骤508、CCF_1向CCF_2发送MEC发现请求。
其中，该MEC发现请求用于请求获取能够提供能够为区域A服务的API的MEC的信息。
步骤509、CCF_2向CCF1发送MEC发现响应。
示例性地，CCF_2根据收到的请求消息和获取的MEC的信息，确定CCF_3对应的MEC符合需求，故将CCF_3的信息携带在MEC发现响应中发送给CCF_1。
CCF_2获取的CCF_3的信息中，可能包括与CCF_3对应的MEC_2提供的API信息，也可能不包括，因此CCF_2发送的发现响应中也可能不包括与CCF_3对应的MEC_2提供的API信息。若MEC发现响应中不包括MEC_2提供的API信息，则执行步骤510，否则，执行步骤512。
步骤510、CCF_1向CCF_3发送API发现请求(API discovery request)。
步骤511、CCF_3向CCF_1发送API发现响应(API discovery response)。
其中，该响应中包括CCF_1能够提供的API信息(即MEC_2能够提供的API信息)，或者，若步骤510中发送的API发现请求还包括API条件信息：服务区域A的信息和PLMN_2的标识，表示请求获取PLMN_2中能够为区域A提供服务的API，那么CCF_3 发送的API发现响应中也可以仅包括与目标参考信息对应的API的信息。
步骤512、CCF_1向MEC_1发送API发现响应。
步骤513、MEC_1向MEC_3发送API调用请求(API discovery request)。
其中，该请求中包括请求调用的API标识。
步骤514、MEC_3向MEC_1发送API调用响应(API discovery response)。
在上述实施例中，将MEC_2的信息注册到CCF_2的过程，是由CCF_4执行的。在另一种可能的实现方式中，CCF_3也可以直接将MEC_2的信息注册到CCF_2上。
在如图5(a)所示的场景下，MEC信息获取方法的流程示意图可以如图5(b)所示：
步骤521～步骤524与前述步骤501～步骤504相同。
步骤525～步骤528：将MEC_3的信息注册到CCF_5、CCF4上，与步骤501～步骤504类似，此处不再赘述。
步骤529、CCF_4向CCF_2发送注册信息。
其中，该注册信息可以包括CCF_4的标识，以及CCF_4的属性描述信息。
其中，CCF的属性描述信息包括的内容与MEC的属性描述信息类似，可以包括服务区域信息、能力描述信息、域标识等。具体地，CCF_4的属性描述信息可以用于描述包括MEC_2、MEC_3的综合属性。例如：MEC_2的服务区域为区域A，能力描述信息包括广播服务；MEC_3的服务区域为区域B，能力描述信息为V2X服务；那么CCF_4的服务区域信息可以包括区域A+区域B，能力描述信息可以包括广播服务+V2X服务。
步骤530、CCF_2向CCF_4发送注册响应。
步骤531、MEC_1向CCF_1发送API发现请求。
示例性地，MEC_1根据第三方应用为区域A中PLMN_2的用户提供服务的需求，请求获取PLMN_2中能够为区域A提供服务的API的信息，则上述请求中可以包括API条件信息：服务区域A的信息和PLMN_2的标识，用于表示请求获取PLMN_2中能够为区域A提供服务的API。
若CCF_1确定没有符合上述API条件信息的API，则执行步骤532。
步骤532、CCF_1向CCF_2发送MEC发现请求。
其中，MEC发现请求用于请求获取能够提供符合上述条件的API的MEC的信息。
示例性地，若CCF_2根据接收到的CCF_4的信息确定CCF_4中有提供符合上述API条件信息对应的API的MEC，但不知道具体由那个MEC提供，或者CCF_2确定还有PLMN_2标识对应的CCF_4有符合上述API条件信息的MEC则执行步骤534。
步骤534、CCF_2向CCF_4发送MEC发现请求。
其中，该请求中包括服务区域A的信息。
若CCF_4确定与CCF_3对应的MEC能够提供符合上述API条件信息的API，则执行步骤535。
步骤535、CCF_4向CCF_2发送MEC发现响应。
其中，该响应中包括CCF_3的信息。
此后，与前述步骤510～步骤514类似，不再赘述。
图6(a)为能够适用本申请上述实施例的一种网络部署场景，如图所示，在PLMN_1中部署有MEC_4(第一网元)以及CCF_6(第二网元)；在PLMN_2中部署有MEC_5以及CCF_7。
在如图6(a)所示的场景下，MEC信息获取方法的流程示意图可以如图6(b)所示。本实施例中以MEC能力为广播服务能力为例进行说明：
步骤601、MEC_5向CCF_7发送MEC注册信息。
其中，该注册信息中可以包括MEC_5标识、MEC_5的服务区域信息、MEC_5提供的API信息以及PLMN_2的标识。此时MEC_4可是视为CAPIF中的AEF和APF的实例。
步骤602、CCF_7向MEC_5发送MEC注册响应。
由于PLMN_1与PLMN_2已预先约定，MEC的信息可以相互注册，执行步骤603。
步骤603、CCF_7向CCF_6发送MEC_5的注册信息。
步骤604、CCF_6向CCF_7发送MEC注册响应。
同样地，MEC_4也可以按照上述流程完成在CCF_6、CCF_7上的注册过程，此处不再赘述。此外，也可以在MEC_4中设置有CCF逻辑单元，形成与图5(a)类似的架构，在注册、发现过程中，该两者间的交互可参见图5(b)、图5(c)所示的实施例。
步骤605、MEC_4向CCF_6发送MEC发现请求。
示例性地，MEC_4根据第三方应用为PLMN_2中用户提供广播服务的需求，确定需要获取PLMN_2中能够提供广播服务的MEC，则该请求中包括的目标参考信息可以包括广播服务的指示信息以及PLMN_2的标识。
步骤606、CCF_6向MEC_4发送MEC发现响应。
其中，MEC发现响应中携带与目标参考信息对应的MEC_5的信息。
示例性地，CCF_6根据自身获取的MEC的信息，确定MEC_5所属的域的标识为PLMN_2，且MEC_5能够提供广播服务，则执行步骤606。
步骤607、MEC_4向MEC_5发送API调用请求。
上述API调用请求中包括MEC_4请求调用的API的标识。
步骤608、MEC_5向MEC_4发送API调用响应。
在上述实施例中，将MEC_5的信息注册到CCF_6的过程，是由CCF_7执行的。在另一种可能的实现方式中，MEC_5也可以直接将其自身的信息注册到CCF_6上。
在如图6(a)所示的场景下，MEC信息获取方法的流程示意图还可以如图6(c)所示：
步骤611、MEC_5向CCF_7发送MEC注册信息。
步骤612、CCF_7向MEC_5发送MEC注册响应。
步骤613、CCF_7向CCF_6发送注册信息。
其中，该注册信息中包括CCF_7的标识以及CCF_7的属性描述信息。CCF_7的属性描述信息与前述CCF_4的属性描述信息类似。
由于PLMN_1与PLMN_2已预先约定，可以进行信息相关注册，故CCF_7向CCF_6发送注册信息。
步骤614、CCF_6向CCF_7发送MEC注册响应。
步骤615、MEC_4向CCF_6发送MEC发现请求。
其中，该请求中包括广播服务指示信息以及PLMN_2的标识。
示例性地，MEC_4根据第三应用提供的为PLMN_2中用户发送广播消息的服务需求，确定需要协同PLMN_2中能够提供广播服务的MEC为第三方应用提供服务，则MEC_4向CCF_6发送MEC发现请求。
步骤616、CCF_6向CCF_7发送MEC发现请求。
其中，该请求中包括广播服务指示信息。
示例性地，CCF_6确定CCF_7中有能够提供广播服务的MEC，可以进一步向CCF_7发送MEC发现请求，已获取提供服务的MEC的信息。
步骤617、CCF_7向CCF_6发送MEC发现响应。
示例性地，CCF_7确定MEC_5能够提供广播服务，上述MEC发现响应中可以包括MEC_5的标识以及提供广播服务的API的信息。
步骤618、CCF_6向MEC_4发送MEC发现响应。
其中，该发现响应中包括MEC_5的标识以及提供广播服务的API的信息。
步骤619、MEC_4向MEC_5发送API调用请求。
步骤620、MEC_5向MEC_4发送API调用响应。
图7(a)为能够适用本申请上述实施例的一种网络部署场景，如图所示，在PLMN_1中部署有MEC_6(第一网元)以及MEC代理网元MEC proxy_1(第二网元)；在PLMN_2中部署有MEC_7以及MEC代理网元(MEC proxy_2)。在该场景中，在每个PLMN中部署有MEC代理网元，MEC的信息注册在MEC代理网元中，在需要获取其他MEC的信息时，向MEC代理网元发起MEC发现过程。
此外，在图7(a)中，MEC代理网元也可以替换为MEC网关(MEC gateway)或者MEC仓库功能(MEC repository function)或者NEF，以下以MEC代理网元为例进行说明。
在如图7(a)所示的场景下，MEC信息获取方法的流程示意图可以如图7(b)所示：
步骤701、MEC_7向MEC proxy_2发送MEC注册信息。
其中，该注册信息中可以包括MEC_7标识、MEC_7的服务区域信息、MEC_7提供的API信息以及PLMN_2的标识。
步骤702、MEC proxy_2向MEC_7发送MEC注册响应。
由于PLMN_1与PLMN_2已预先约定，MEC的信息可以相互注册。MEC的信息在实现跨PLMN注册时，可以如步骤703a、704a所示，也可以如步骤703b、704b所示。
步骤703a、MEC proxy_2向MEC proxy_1发送MEC_6的注册信息。
步骤704a、MEC proxy_1向MEC proxy_2发送MEC注册响应。
步骤703b、MEC_7向MEC proxy_1发送MEC的注册信息。
步骤704b、MEC proxy_1向MEC_7发送MEC注册响应。
同样地，MEC_6也可以按照上述流程完成在MEC proxy_1、MEC proxy_2上的注册过程，此处不再赘述。
步骤705、MEC_6向MEC proxy_1发送MEC发现请求。
示例性地，该请求中包括流量计费服务指示信息以及PLMN_2的标识，表示MEC_6请求获取PLMN_2中能够提供流量计费服务的MEC的信息。
步骤706、MEC proxy_1向MEC_6发送MEC发现响应。
其中，该MEC发现响应携带能够提供流量计费服务的MEC_7的信息。
示例性地，MEC proxy_1根据收到的MEC发现请求和获取的MEC的信息，确定MEC_7符合需求，故将MEC_7的信息携带在MEC发现响应中发送给MEC_6。
步骤707、MEC_6向MEC_7发送API调用请求。
该调用请求中可以包括请求调用的API标识。
步骤708、MEC_7向MEC_6发送API调用响应。
在如图7(a)所示的场景下，MEC信息获取方法的流程示意图还可以如图7(c)所示：其中，MEC信息的注册过程可以与7(b)所示的注册过程一致，或者也可以不进行跨PLMN的注册，即，可以不将MEC_7的信息注册到MEC proxy_1上，也可以不将MEC_6的信息注册到MEC proxy_2上，本申请实施例对此不做限定。
步骤711～步骤720与步骤611～步骤620类似，其区别在于将CCF替换为MEC proxy，此处不再一一赘述。
图8(a)为能够适用本申请上述实施例的一种网络部署场景，如图所示，在PLMN_1中部署有MEC_8(第一网元)；在PLMN_2中部署有MEC_9，NEF_1(或MEC gateway_3，或MEC代理网元，作为第二网元)以及NRF_1。其中，MEC_8中也可以设置有CCF逻辑单元，在注册、发现过程中，该两者间的交互可参见图5所示的实施例。
在如图8所示的场景下，MEC信息获取方法的流程示意图如图8(b)所示。
步骤801、MEC_9向NRF_1发送MEC注册信息。
其中，该注册信息中可以包括MEC_9标识、MEC_9的服务区域信息、MEC_9提供的API信息以及PLMN_2的标识。
步骤802、NRF_1向MEC_9发送MEC注册响应。
步骤803、MEC_8向NEF_1发送MEC发现请求。
示例性地，MEC_8根据第三方应用的业务需求，确定需要寻找PLMN_2中能够提V2X服务的MEC，MEC_8向NEF_1发送MEC发现请求，该请求中包括V2X服务指示信息。此时，MEC_8可以看做CAPIF中的API请求者的一个实施例。本实施例以MEC的能力为V2X服务为例进行说明。
步骤804、NEF_1向NRF_1发送NF发现请求。
其中，该请求中可以包括目标网元为MEC的指示信息，用于指示寻找MEC类型的网元，还包括V2X服务指示信息，进一步指示寻找提供V2X服务的MEC类型的网元。
步骤805、NRF_1向NEF_1发送NF发现响应。
其中，NF发现响应携带有符合NEF_1请求的MEC_9的信息。
示例性地，NRF_1根据收到的NEF发现请求和获取的MEC的信息，确定MEC_9符合NEF_1的请求，故将MEC_9的信息携带在NF发现响应中发送给NEF_1。
步骤806、NEF_1向MEC_8发送MEC发现响应。
其中，该响应中携带有MEC_9的信息。
步骤807、MEC_8向MEC_9发送API调用请求。
由于MEC_9的信息中包含有MEC_9所提供的API的标识以及提供的服务信息，MEC_8可以向MEC_9发送API调用请求，调用请求中包含所要调用API的标识，请求调用API标识对应的API。
步骤808、MEC_9向MEC_8发送API调用响应。
此外，在图8(a)所示的网络部署场景中，在PLMN_1中也可以包含有NEF_2(或MEC gateway_4，或MEC代理网元)，如图8(c)所示，在该场景下，MEC信息获取方法的流程示意图可以如图8(d)所示。
步骤811、MEC_9向NRF_1发送MEC注册信息。
步骤812、NRF_1向MEC_9发送MEC注册响应。
步骤813、MEC_8向NEF_2发送MEC发现请求。
其中，该请求中包括V2X服务指示信息以及PLMN_2的标识，表示请求获取PLMN_2中能够提供V2X服务的MEC的信息。
示例性地，MEC_8根据第三方应用的业务需求，确定需要找到PLMN_2中能够提V2X服务的MEC，则执行上述步骤813。
步骤814、NEF_2向NEF_1发送MEC发现请求。
其中，该请求中包括V2X服务指示信息。
示例性地，NEF_2可以根据发现请求中的PLMN_2的标识，向NEF_1发送MEC发现请求。
步骤815、NEF_1向NRF_1发送NF发现请求。
其中，该请求中可以包括目标网元为MEC的指示信息，还包括V2X服务指示信息。
步骤816、NRF_1向NEF_1发送NF发现响应。
其中，NF发现响应携带能够提供V2X服务的MEC_9的信息。
示例性地，NRF_1根据收到的NF发现请求和获取的MEC的信息，确定MEC_9符合需求，故将MEC_9的信息携带在NF发现响应中发送给NEF_1。
步骤817、NEF_1向NEF_2发送MEC发现响应。
其中，该响应中携带有MEC_9的信息。
步骤818、NEF_2向MEC_8发送MEC发现响应。
其中，该响应中携带有MEC_9的信息。
步骤819、MEC_8向MEC_9发送API调用请求。
示例性地，MEC_9的信息中包含有MEC_9所提供的API信息，其中包含API标识，MEC_8向MEC_9发送API调用请求，调用请求中包含API标识，指示调用API标识对应的API。
步骤820、MEC_9向MEC_8发送API调用响应。
基于相同的技术构思，本申请实施例还提供了一种MEC信息注册方法，用于实现将MEC信息注册到其他域中的网元上。该方法的流程示意图可以如图9所示，包括以下步骤：
步骤901、第三网元接收来自MEC的第一注册信息。
此处所述的第三网元，用于实现MEC信息注册方法，与前述MEC信息获取方法实施例中的第一网元可以为同一网元，也可以为不同的网元。
在一些场景中，第三网元可以接收MEC发送的第一注册信息，例如图6(a)中的CCF_5、CCF_6，图7(a)中的MEC proxy_1/MECgateway_1、MEC proxy_2/MECgateway_2等等。而在另一些场景中，第三网元接收到的MEC的第一注册信息，也可以是由其他网元转发的，例如图5(a)中的CCF_4接收到的MEC_2的注册信息，是由CCF_3发送的。
具体地，MEC的第一注册信息中，可以包括所述MEC的寻址信息以及MEC的属性描述信息。该实施例中的属性描述信息与前述实施例中的属性描述信息类似，不再赘述。
步骤902、第三网元根据第一注册信息，向第四网元发送第二注册信息，该第四网元的所属的域与第三网元所属的域不同。
网元所属的域，与前述实施例中“域”的概念类似，此处不再重复介绍。
第二注册信息中包括MEC的寻址信息以及MEC的属性描述信息。当然，第三网元向第四网元发的MEC的属性描述信息时，可以将第三网元接收到的属性描述信息全部发送 给第四网元，也可以将第三网元接收到的属性描述信息中的部分发送给第四网元。
其中，MEC的寻址信息可以指MEC的标识等，也可以指与MEC对应的CCF的标识等。例如，在图5(a)所示的场景中，在MEC_2上设置有CCF_3逻辑单元，那么CCF_4在将MEC_2的信息注册到CCF_2上时，CCF_4向CCF_2发送的MEC注册信息，可以包含MEC_2的标识以及MEC_2的属性描述信息；或者，也可以不包含MEC粒度的信息，而是包含CCF_3标识以及CCF_3的属性描述信息(因为CCF_3部署在MEC_2中，可以将MEC_2的属性描述信息作为CCF_3的属性描述信息)。
进一步地，当MEC的属性描述信息中包括MEC的位置信息或MEC的服务区域信息时，第三网元在发送位置信息或服务区域信息，可以先对发送位置信息或服务区域信息进行判断，判断该信息是否可以直接发送还是需要经过转换再发送。例如，若MEC的信息为其PLMN网络中的小区标识，那么该小区标识不能够被其他PLMN中的网元识别，故第三网元在发送时，可以对其进行转换，转换为对于不同域之间通用的位置信息，例如可以转换为经纬度信息或行政区域信息，以使第四网元也能够识别。
在上述实施例中，实现了将一个域中的MEC的信息注册到另一域中的网元上，使得网元能够获取到其他域中MEC的信息。在后续MEC信息的获取的过程中，由于第一域中的网元中已注册有第二域中的MEC的信息，MEC的发现过程仅在第一域中即可实现，而不必再向第二域中的网元发送发现请求，提高了MEC发现的响应速度。
此外，PLMN_2中可能包含多个MEC，且每个MEC均将其信息注册在CCF_4上，CCF_4向CCF_2发送的MEC注册信息中，可以包括CCF_4的标识以及该多个MEC的能力集合。例如，MEC_2的服务区域为区域A，可用于提供V2X服务；而MEC_3的服务区域为区域B，可以用于提供计费服务，那么CCF_4向CCF_2发送的MEC注册信息，可以包括CCF_4的标识，CCF_4的服务区域：区域A和区域B，CCF_4的能力描述信息：V2X服务和计费服务，CCF_4的域标识：PLMN_2的标识等等。
基于相同的技术构思，本申请实施例还提供了一种信息注册方法，用于实现将MEC信息注册到其他域中的网元上，但由于跨域注册，出于安全等方面的考虑，注册时并不携带MEC的标识。该方法的流程示意图可以如图10所示，包括以下步骤：
步骤1001、第五网元接收来自MEC的注册信息。
如图11所示，该实施例中的第五网元可以为CCF、MEC proxy或MECgateway。
示例性地，CCF_A接收来自MEC1的注册信息，那么该注册信息中，可以包括MEC1的标识以及MEC1的属性描述信息，或者，也可以包括CCF1标识以及CCF1的属性描述信息(因为CCF1部署在MEC1中，可以将MEC1的属性描述信息作为CCF1的属性描述信息)。此外，CCF_A还可以接收来自MEC2的注册信息。
该实施例中的属性描述信息与前述实施例中的属性描述信息类似，不再赘述。
步骤1002、第五网元向第六网元发送注册请求，该第六网元的所属的域与第五网元所属的域不同，所述注册请求中包括第五网元的标识以及第五网元的属性描述信息，所述第五网元的属性描述信息用于综合描述在所述第五网元上注册的一个或多个MEC的属性描述信息。
由于第五网元与第六网元属于不同的域，例如属于不同的PLMN，出于安全的考虑，第五网元在向第六网元发送注册请求时，可以不发送MEC粒度的信息，而仅发送第五网 元的表述以及第五网元的属性描述信息。
结合图11进行举例说明，PLMN_A中的CCF_A可以向PLMN_B中的CCF_B发送注册信息，该注册信息中可以包括CCF_A的标识。如果CCF_A的标识仅能够在PLMN_A中唯一标识CCF_A，注册信息中还可以包括PLMN_A的标识，通过<CCF_A的标识+PLMN_A的标识>的方式唯一标识CCF_A。
此外，该注册信息中还包括CCF_A的属性描述信息，即在CCF_A上注册的MEC的属性描述信息。具体地，该属性描述信息可以不特指某个MEC的属性描述信息，而表示为在CCF_A上注册的多个MEC的总能力，例如若在CCF_A上注册的MEC1具有广播、流量计费的能力，MEC2具有提供V2X服务的能力，那么CCF_A向CCF_B发送的注册信息中，能力描述信息可以包括广播、流量计费、V2X服务的指示信息。
该注册信息中还可以包括CCF_A上注册的MEC的服务区域信息。具体地，该服务区域信息也可以不特指某个MEC的能力信息，而表示为在CCF_A上注册的多个MEC的总服务区域。例如，若在CCF_A上注册的MEC1的服务区域为区域A和区域B，MEC2的服务区域为区域C和区域D，那么CCF_A向CCF_B发送的注册信息中，服务区域信息可以包括区域A、区域B、区域C、区域D的指示信息。
在后续MEC发现过程中，CCF_B若接收到MEC发现请求，MEC请求中包含目标参考信息，目标参考信息用于请求获取能够为区域A服务的MEC，那么CCF_B可以根据CCF_A的属性描述信息确定CCF_A与目标参考信息对应，则向CCF_A发送MEC发现请求，以从CCF_A处获取相应的MEC的信息。或者，CCF_B还可以将CCF_A的标识(或CCF_A的标识+PLMN_A的标识)发送给请求者，请求者可以向CCF_A请求获取能够提供相应服务的MEC的信息。
可选地，上述步骤1002，可以是在每次接收到MEC的注册信息后就执行，也可以周期性执行上述步骤1002。
步骤1003、第六网元将接收到的注册信息更新到本地中，便于后续接收到MEC发现请求后，根据本地保存的注册信息，选择与目标参考信息对应的MEC或与MEC对应的CCF。
步骤1004、第六网元向第五网元发送注册响应。
基于相同的技术构思，本申请实施例还提供了一种MEC信息获取装置，用于执行上述MEC信息获取方法中第一网元所执行的功能。图12示例性地给出了一种该装置的结构示意图，如图所示，该装置可以包括接收单元1201和发送单元1202，进一步地，该装置还可以包括处理单元1203。
接收单元1201，用于接收来自第二网元的目标参考信息；
发送单元1202，用于向所述第二网元发送所述目标参考信息对应的MEC的信息。
在一种可能的实现方式中，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
在一种可能的实现方式中，在所述发送单元1202在向所述第二网元发送所述目标参考信息对应的MEC的信息之前，所述接收单元1201还用于：接收所述MEC的第一注册信息；其中，所述第一注册信息包括所述MEC的寻址信息和所述MEC的属性描述信息。
在一种可能的实现方式中，所述属性描述信息包括以下信息中的一种或多种：所述 MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的服务区域信息，所述MEC的能力描述信息，以及所述MEC的域标识。
在一种可能的实现方式中，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者，所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者，所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者，所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者，所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者，所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
在一种可能的实现方式中，当所述MEC所属的域与所述第一网元所属的域相同时，在所述接收单元1201接收所述第一注册信息之后，所述发送单元1202还用于：向第三网元发送所述MEC的第二注册信息，所述第二注册信息用于将所述MEC的信息注册在所述第三网元中，所述第三网元所属的域与所述第一网元所属的域不同，所述第二注册信息中包括所述MEC的寻址信息，以及所述MEC的属性描述信息的部分或全部。
在一种可能的实现方式中，所述第一网元还包括处理单元，用于：所述MEC的属性描述信息中包括所述MEC的位置信息，当根据所述MEC的位置信息确定所述MEC位于所述第一网元所属的域中时，将所述MEC的位置信息转换为通用位置信息；所述发送单元1202向所述第三网元发送的位置信息为所述通用位置信息；和/或，所述MEC的属性描述信息中包括所述MEC的服务区域信息，当根据所述MEC的服务区域信息确定所述MEC的服务区域位于所述第一网元所属的域中时，将所述MEC的服务区域信息转换为通用服务区域信息；所述发送单元1202向所述第三网元发送的服务区域信息为所述通用服务区域信息。
在一种可能的实现方式中，所述第一网元为CCF，所述第三网元为CCF，所述第一网元所属的域与所述第三网元所属的域不同。
在一种可能的实现方式中，所述MEC的信息包括所述MEC对应的CCF的信息。
在一种可能的实现方式中，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
基于相同的技术构思，本申请实施例还提供了一种MEC信息获取装置，用于执行上述MEC信息获取方法中第一网元所执行的功能。图13示例性地给出了一种该装置的结构示意图，如图所示，该装置可以包括接收单元1301和发送单元1302。
发送单元1302，用于向第一网元发送目标参考信息；
接收单元1301，用于接收来自所述第一网元的与所述目标参考信息对应的MEC的信息。
在一种可能的实现方式中，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
在一种可能的实现方式中，所述MEC的信息包括所述MEC对应的CCF的信息。
在一种可能的实现方式中，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
在一种可能的实现方式中，所述MEC的属性描述信息包括以下信息中的一种或多种： 所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
在一种可能的实现方式中，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者
所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者
所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者
所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者
所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
在一种可能的实现方式中，所述MEC的属性描述信息包括所述MEC提供的API信息；
所述发送网元还用于：根据所述API信息向与所述目标参考信息对应的MEC发送API调用请求；
所述接收网元还用于：接收与所述与目标参考信息对应的MEC发送的API调用响应。
在一种可能的实现方式中，所述第二网元为MEC；
当所述MEC的属性描述信息不包括所述MEC提供的API信息时，所述发送网元还用于：向与所述目标参考信息对应的MEC发送API发现请求，或者，向与所述目标参考信息对应的MEC对应的CCF发送API发现请求；
接收网元还用于：接收API发现响应，所述API发现响应中包括所述MEC提供的API信息。
在一种可能的实现方式中，所述发送单元1302还用于：
向所述第一网元发送MEC的注册信息，所述MEC的注册信息中包括MEC的寻址信息以及所述MEC的属性描述信息。
基于相同的技术构思，本申请实施例还提供了一种MEC信息获取装置，用于执行上述MEC信息获取方法中第一网元所执行的功能。图14示例性地给出了一种该装置的结构示意图，如图所示，该装置可以包括接收单元1401和发送单元1402，进一步地，该装置还可以包括处理单元1403。
接收单元1401，用于接收来自MEC的第一注册信息，所述第一注册信息包括所述MEC的寻址信息以及所述MEC的属性描述信息；
发送单元1402，用于根据所述第一注册信息，向第二网元发送第二注册信息，所述第一网元所属的域与所述第二网元所属的域不同。
在一种可能的实现方式中，所述MEC的属性描述信息包括以下信息中的一种或多种：所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
在一种可能的实现方式中，所述第一网元还包括处理单元1403，用于：
所述MEC的属性描述信息中包括所述MEC的位置信息，当根据所述MEC的位置信息确定所述MEC位于所述第一网元所属的域中时，将所述MEC的位置信息转换为通用位 置信息；所述发送单元向所述第三网元发送的位置信息为所述通用位置信息；和/或
所述MEC的属性描述信息中包括所述MEC的服务区域信息，当根据所述MEC的服务区域信息确定所述MEC位于所述第一网元所属的域中时，所述第一网元将所述MEC的服务区域信息转换为通用服务区域信息；所述发送单元向所述第三网元发送服务区域信息为所述通用服务区域信息。
基于相同的技术构思，本申请实施例提供了一种MEC信息获取装置1500，用于实现上述方法实施例中第一网元所执行的功能。具体地，该网络设备1500的硬件结构可以如图15所示，包括至少一个处理器1501，通信总线1502，存储器1503以及至少一个通信接口1504。
处理器1501可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线1502可包括一通路，在上述组件之间传送信息。
通信接口1504，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器1503可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1503用于存储执行本申请方案的应用程序代码，并由处理器1501来控制执行。处理器1501用于执行存储器1503中存储的应用程序代码，从而实现本申请上述实施例提供的MEC信息获取方法。
或者，可选的，本申请实施例中，也可以是处理器1501执行本申请上述实施例提供的MEC信息获取方法中的相关功能，通信接口1504负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1501可以包括一个或多个CPU。
在具体实现中，作为一种实施例，该网络设备可以包括多个处理器。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
基于相同的技术构思，本申请实施例提供了一种MEC信息获取装置1600，用于实现 上述方法实施例中第二网元所执行的功能。具体地，该网络设备1600的硬件结构可以如图16所示，包括至少一个处理器1601，通信总线1602，存储器1603以及至少一个通信接口1604。
处理器1601可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线1602可包括一通路，在上述组件之间传送信息。
通信接口1604，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器1603可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1603用于存储执行本申请方案的应用程序代码，并由处理器1601来控制执行。处理器1601用于执行存储器1603中存储的应用程序代码，从而实现本申请上述实施例提供的MEC信息获取方法。
或者，可选的，本申请实施例中，也可以是处理器1601执行本申请上述实施例提供的MEC信息获取方法中的相关功能，通信接口1604负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1601可以包括一个或多个CPU。
在具体实现中，作为一种实施例，该网络设备可以包括多个处理器。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
本申请实施例提供还一种存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面至第三方面任一项所述的方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/ 或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (24)

  1. 一种移动边缘计算MEC信息获取方法，其特征在于，包括：
    第一网元接收来自第二网元的目标参考信息；
    所述第一网元向所述第二网元发送所述目标参考信息对应的MEC的信息。
  2. 如权利要求1所述的方法，其特征在于，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
  3. 如权利要求1所述的方法，其特征在于，在所述第一网元向所述第二网元发送所述目标参考信息对应的MEC的信息之前，还包括：
    所述第一网元接收所述MEC的第一注册信息；
    其中，所述第一注册信息包括所述MEC的寻址信息和所述MEC的属性描述信息。
  4. 如权利要求3所述的方法，其特征在于，所述属性描述信息包括以下信息中的一种或多种：所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的服务区域信息，所述MEC的能力描述信息，以及所述MEC的域标识。
  5. 如权利要求1-4中任一项所述的方法，其特征在于，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者
    所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者
    所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者
    所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者
    所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者
    所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
  6. 如权利要求3或4所述的方法，其特征在于，当所述MEC所属的域与所述第一网元所属的域相同时，在所述第一网元接收所述第一注册信息之后，还包括：
    所述第一网元向第三网元发送所述MEC的第二注册信息，所述第二注册信息用于将所述MEC的信息注册在所述第三网元中，所述第三网元所属的域与所述第一网元所属的域不同，所述第二注册信息中包括所述MEC的寻址信息，以及所述MEC的属性描述信息的部分或全部。
  7. 如权利要求6所述的方法，其特征在于，
    所述MEC的属性描述信息中包括所述MEC的位置信息，所述方法还包括：当所述第一网元根据所述MEC的位置信息确定所述MEC位于所述第一网元所属的域中时，所述第一网元将所述MEC的位置信息转换为通用位置信息，并将所述通用位置信息发送给所述第三网元；和/或，
    所述MEC的属性描述信息中包括所述MEC的服务区域信息，所述方法还包括：当所述第一网元根据所述MEC的服务区域信息确定所述MEC的服务区域位于所述第一网元所属的域中时，所述第一网元将所述MEC的服务区域信息转换为服务区域信息，并将所述通用服务区域信息发送给所述第三网元。
  8. 如权利要求6或7所述的方法，其特征在于，所述第一网元为CCF，所述第三网 元为CCF，所述第一网元所属的域与所述第三网元所属的域不同。
  9. 如权利要求1-8中任一项所述的方法，其特征在于，所述MEC的信息包括所述MEC对应的CCF的信息。
  10. 如权利要求1-8中任一项所述的方法，其特征在于，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
  11. 一种移动边缘计算MEC信息获取方法，其特征在于，包括：
    第二网元向第一网元发送目标参考信息；
    所述第二网元接收来自所述第一网元的与所述目标参考信息对应的MEC的信息。
  12. 如权利要求11所述的方法，其特征在于，所述目标参考信息包括目标位置信息和目标能力信息中的至少一种。
  13. 如权利要求11或12所述的方法，其特征在于，所述MEC的信息包括所述MEC对应的CCF的信息。
  14. 如权利要求11或12所述的方法，其特征在于，所述MEC的信息包括所述MEC的寻址信息以及所述MEC的属性描述信息。
  15. 如权利要求14所述的方法，其特征在于，所述MEC的属性描述信息包括以下信息中的一种或多种：所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
  16. 如权利要求11-15中任一项所述的方法，其特征在于，所述第一网元为公共API架构核心功能CCF，所述第二网元为移动边缘计算MEC；或者
    所述第一网元为CCF，所述第二网元为CCF，所述第一网元所属的域与所述第二网元所属的域不同；或者
    所述第一网元为MEC代理功能实体，所述第二网元为MEC；或者
    所述第一网元为MEC代理功能实体，所述第二网元为MEC代理功能实体，所述第一网元所属的域与所述第二网元所属的域不同；或者
    所述第一网元为网络开放功能网元NEF，所述第二网元为MEC；或者
    所述第一网元为NEF，所述第二网元为NEF，所述第一网元所属的域与所述第二网元所属的域不同。
  17. 如权利要求15所述的方法，其特征在于，所述第二网元为MEC，所述MEC的属性描述信息包括所述MEC提供的API信息，所述方法还包括：
    所述第二网元根据所述API信息向与所述目标参考信息对应的MEC发送API调用请求；
    所述第二网元接收与所述目标参考信息对应的MEC发送的API调用响应。
  18. 如权利要求11-15中任一项所述的方法，其特征在于，所述第二网元为MEC所述MEC的属性描述信息不包括所述MEC提供的API信息，所述方法还包括：
    所述第二网元向所述MEC或与所述MEC对应的CCF发送API发现请求；
    所述第二网元接收API发现响应，所述API发现响应中包括所述MEC提供的API信息。
  19. 如权利要求11-18中任一项所述的方法，其特征在于，还包括：
    所述第二网元向所述第一网元发送MEC的注册信息，所述MEC的注册信息中包括MEC的寻址信息以及所述MEC的属性描述信息。
  20. 一种移动边缘计算MEC信息获取方法，其特征在于，包括：
    第一网元接收来自MEC的第一注册信息，所述第一注册信息包括所述MEC的寻址信息以及所述MEC的属性描述信息；
    第一网元根据所述第一注册信息，向第二网元发送第二注册信息，所述第一网元所属的域与所述第二网元所属的域不同。
  21. 如权利要求20所述的方法，其特征在于，所述MEC的属性描述信息包括以下信息中的一种或多种：所述MEC的服务区域信息，所述MEC的能力描述信息，所述MEC提供的应用编程接口API信息，所述MEC的位置信息，所述MEC的域标识。
  22. 如权利要求21所述的方法，其特征在于，
    所述MEC的属性描述信息中包括所述MEC的位置信息，所述方法还包括：当所述第一网元根据所述MEC的位置信息确定所述MEC位于所述第一网元所属的域中时，所述第一网元将所述MEC的位置信息转换为通用位置信息，并将所述通用位置信息发送给所述第三网元；和/或，
    所述MEC的属性描述信息中包括所述MEC的服务区域信息，所述方法还包括：当所述第一网元根据所述MEC的服务区域信息确定所述MEC位于所述第一网元所属的域中时，所述第一网元将所述MEC的服务区域信息转换为通用服务区域信息，并将所述通用服务区域信息发送给所述第三网元。
  23. 一种移动边缘计算MEC信息获取装置，其特征在于，所述装置用于执行权利要求1-10任一项所述的方法。
  24. 一种移动边缘计算MEC信息获取装置，其特征在于，所述装置用于执行权利要求11-19任一项所述的方法。
PCT/CN2019/096154 2018-07-16 2019-07-16 一种mec信息获取方法及装置 WO2020015634A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19838743.3A EP3809766A4 (en) 2018-07-16 2019-07-16 PROCESS AND DEVICE FOR ACQUIRING INFORMATION MEC
US17/148,045 US11540244B2 (en) 2018-07-16 2021-01-13 MEC information obtaining method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810780270.7A CN110730499B (zh) 2018-07-16 2018-07-16 一种mec信息获取方法及装置
CN201810780270.7 2018-07-16

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/148,045 Continuation US11540244B2 (en) 2018-07-16 2021-01-13 MEC information obtaining method and apparatus

Publications (1)

Publication Number Publication Date
WO2020015634A1 true WO2020015634A1 (zh) 2020-01-23

Family

ID=69164994

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/096154 WO2020015634A1 (zh) 2018-07-16 2019-07-16 一种mec信息获取方法及装置

Country Status (4)

Country Link
US (1) US11540244B2 (zh)
EP (1) EP3809766A4 (zh)
CN (1) CN110730499B (zh)
WO (1) WO2020015634A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4222594A4 (en) * 2020-09-30 2024-06-12 Telefonaktiebolaget LM Ericsson (publ) METHOD AND APPARATUS FOR MANAGING APPLICATION PROGRAMMING INTERFACE

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11290548B2 (en) * 2019-04-12 2022-03-29 Samsung Electronics Co., Ltd. Method and system for discovering edge-server or edge-service through domain name server (DNS) resolution
WO2021031127A1 (zh) * 2019-08-20 2021-02-25 华为技术有限公司 一种获取信息的方法及装置
CN117221385A (zh) * 2020-02-14 2023-12-12 瑞典爱立信有限公司 用于服务api发布的方法、网络实体和介质
CN114143778B (zh) * 2020-08-12 2024-09-06 中国移动通信有限公司研究院 数据共享方法、装置、边缘计算平台及可读存储介质
CN114915430B (zh) * 2021-01-28 2024-07-12 中国移动通信有限公司研究院 实现动态能力开放的方法、装置、通信设备及存储介质
US20220116755A1 (en) * 2021-06-07 2022-04-14 Miltiadis Filippou Multi-access edge computing (mec) vehicle-to-everything (v2x) interoperability support for multiple v2x message brokers
CN115987534A (zh) * 2021-10-14 2023-04-18 华为技术有限公司 一种资源访问方法及装置
US11765030B2 (en) * 2021-12-02 2023-09-19 Oracle International Corporation Methods, systems, and computer readable media for registering application functions using common application programming interface framework
US11709725B1 (en) 2022-01-19 2023-07-25 Oracle International Corporation Methods, systems, and computer readable media for health checking involving common application programming interface framework
CN115499470B (zh) * 2022-09-17 2023-08-04 浙江晨泰科技股份有限公司 一种智能电表数据的存储管理方法及装置
CN117857548A (zh) * 2022-09-30 2024-04-09 华为技术有限公司 一种通信方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076488A (zh) * 2016-11-14 2018-05-25 华为技术有限公司 用于小区切换的方法、装置和系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011115426A2 (en) * 2010-03-17 2011-09-22 Lg Electronics Inc. Method for iptv service discovery and iptv receiver using the same
CN105245595B (zh) * 2015-09-30 2018-07-31 小米科技有限责任公司 服务响应方法及装置
CN108353067B (zh) * 2015-11-30 2020-06-02 华为技术有限公司 一种能力开放的实现方法、系统及相关设备
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统
US20190380028A1 (en) * 2016-11-22 2019-12-12 Nokia Technologies Oy User equipment identity implementation in mobile edge scenarios
US10326766B2 (en) * 2017-07-13 2019-06-18 Dell Products, Lp Method and apparatus for optimizing mobile edge computing for nomadic computing capabilities as a service
CN109600721B (zh) 2017-09-30 2021-03-30 华为技术有限公司 一种通信方法及装置
CN107770815B (zh) * 2017-10-18 2020-09-11 中国联合网络通信集团有限公司 一种基于位置的mec方法及设备
US10659526B2 (en) * 2018-01-03 2020-05-19 Verizon Patent And Licensing Inc. Edge compute systems and methods
CN108282801B (zh) * 2018-01-26 2021-03-30 重庆邮电大学 一种基于移动边缘计算的切换管理方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076488A (zh) * 2016-11-14 2018-05-25 华为技术有限公司 用于小区切换的方法、装置和系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Mobile Edge Computing (MEC); Radio Network Information API", ETSI GS MEC 012, V1.1.1, 31 July 2017 (2017-07-31), XP014290907 *
"Study on Common API Framework for 3GPP Northbound APIs (Release 15)", 3GPP TR 23. 722 V0.2.0, 31 May 2017 (2017-05-31), XP051298255 *
HUAWEI: "Supporting MEC with CAPIF, S 6-181079", 3GPP TSG-SA WG6 MEETING #25, 27 July 2018 (2018-07-27), XP051471197 *
QI, YANLI ET AL.: "MEC coordinated future 5G mobile wireless networks", JOURNAL OF COMPUTER RESEARCH AND DEVELOPMENT, vol. 55, no. 3, 15 March 2018 (2018-03-15), pages 478 - 486, XP055771673 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4222594A4 (en) * 2020-09-30 2024-06-12 Telefonaktiebolaget LM Ericsson (publ) METHOD AND APPARATUS FOR MANAGING APPLICATION PROGRAMMING INTERFACE

Also Published As

Publication number Publication date
CN110730499B (zh) 2021-06-15
EP3809766A4 (en) 2021-09-01
US20210136716A1 (en) 2021-05-06
EP3809766A1 (en) 2021-04-21
CN110730499A (zh) 2020-01-24
US11540244B2 (en) 2022-12-27

Similar Documents

Publication Publication Date Title
WO2020015634A1 (zh) 一种mec信息获取方法及装置
US11838858B2 (en) System and method for UE context and PDU session context management
US20230093339A1 (en) Session Management Method, Apparatus, and System
US20230370383A1 (en) Systems and methods for supporting traffic steering through a service function chain
US12015682B2 (en) Service subscription method and system for reporting service change in communication system
KR102224248B1 (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
US11172405B2 (en) Method for checking change in wireless connection type of terminal in third-party application server
US20200053636A1 (en) SMF Selection Based On Supported DNN
CN116057924B (zh) 用于提供网络功能发现服务增强的方法、系统和计算机可读介质
WO2018205150A1 (zh) 网络切片选择策略更新方法、及装置
US20200374698A1 (en) Communication method and communications apparatus
WO2021031562A1 (zh) 一种获取信息的方法及装置
WO2021027177A1 (en) Method and apparatus for network function service discovery
WO2021135663A1 (zh) 应用实例确定的方法、装置及系统
CN111901135A (zh) 一种数据分析方法及装置
CN113543165B (zh) 通信方法、装置及系统
WO2020119653A1 (zh) 识别终端的方法、装置
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2021081712A1 (zh) 一种dns查询方法及装置
WO2023082858A1 (zh) 确定移动性管理策略的方法、通信装置及通信系统
WO2023030077A1 (zh) 一种通信方法、通信装置及通信系统
WO2023056784A1 (zh) 数据收集方法、通信装置及通信系统
CN116866965A (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: 19838743

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019838743

Country of ref document: EP

Effective date: 20210118