WO2022233244A1 - 一种数据获取方法、系统及其装置 - Google Patents

一种数据获取方法、系统及其装置 Download PDF

Info

Publication number
WO2022233244A1
WO2022233244A1 PCT/CN2022/088689 CN2022088689W WO2022233244A1 WO 2022233244 A1 WO2022233244 A1 WO 2022233244A1 CN 2022088689 W CN2022088689 W CN 2022088689W WO 2022233244 A1 WO2022233244 A1 WO 2022233244A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network element
identifier
data source
data
Prior art date
Application number
PCT/CN2022/088689
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 JP2023568156A priority Critical patent/JP2024519311A/ja
Priority to EP22798585.0A priority patent/EP4325925A1/en
Publication of WO2022233244A1 publication Critical patent/WO2022233244A1/zh
Priority to US18/500,491 priority patent/US20240064069A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a data acquisition method, system, and device thereof.
  • Operation, administration, and maintenance (OAM) systems can be used to analyze, predict, plan, configure, test, and manage faults on networks and services.
  • the OAM system performs the above-mentioned management operations and maintenance operations on the network and services, and can generate a large amount of data about the network and services.
  • the NWDAF wants to obtain the data of the managed objects in the OAM system
  • the NWDAF needs to have the entire managed object database of the OAM system. Therefore, the process for the NWDAF to obtain the data of the managed objects from the OAM system is complicated.
  • Embodiments of the present application provide a data acquisition method, system, and device, which are used to simplify the process of NWDAF acquiring data of a managed object from an OAM system.
  • an embodiment of the present application provides a data acquisition method, and the execution body of the method may be a network data analysis network element, or may be a chip applied to the network data analysis network element.
  • the method includes: a network data analysis network element determines a data source to which data to be acquired belongs; acquires first information, where the first information is used to determine an object identifier of the data source in the OAM system; and determines the data source according to the first information The object identifier of the data source in the operation management and maintenance OAM system; sending a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to obtain the to-be-obtained data.
  • the first information may be associated with the identifier of the data source and the object identifier of the data source in the OAM system, or may associate the domain name of the data source with the object identifier of the data source in the OAM system.
  • the first information may also be referred to as association information.
  • the network data analysis network element can determine the object identifier of the data source in the OAM system according to the first information. In this way, the network data analysis network element does not need to acquire the entire managed object database of the OAM system, thereby It is beneficial to simplify the process of network data analysis network element acquiring data from the OAM system.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the object identifier of the data source in the OAM system can be obtained by querying the corresponding relationship, thereby facilitating the simplification of the process of acquiring data from the OAM system by the network data analysis network element.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following: a relationship between an identifier of the network slice and an object identifier of the network slice in the OAM system Correspondence; the correspondence between the identifier of the network slice and the object identifier of the network slice subnet in the network slice in the OAM system; the identifier of the network slice subnet in the network slice and the network slice in the OAM system The corresponding relationship between the object identifiers of the network slice; or, the corresponding relationship between the identifier of the network slice subnet in the network slice and the object identifier of the network slice subnet in the OAM system.
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes the generation rule of the object identifier of the data source in the OAM system; the aforementioned network data analysis network element determines the specific implementation of the object identifier of the data source in the OAM system according to the first information
  • the method may be as follows: the network data analysis network element generates the object identifier of the data source in the OAM system according to the generation rule and the identifier of the data source.
  • the data source is a network slice or a network slice subnet
  • a (newly added) network slice or network slice can be generated according to the historically acquired generation rules.
  • the aforementioned object identifiers include a first identifier and a second identifier; the generation rule includes a first generation rule and a second generation rule; the network data analysis network element generates the
  • the specific implementation of the object identification of the data source in the OAM system may be: the network data analysis network element generates the first identification according to the first generation rule and the domain name of the network data analysis network element; and according to the second generation rule and the identifier of the data source to generate the second identifier.
  • the identifier of the data source includes network slice selection assistance information and/or the network slice subnet identifier; the object identifier of the data source in the OAM system includes the network slice managed object identifier and/or the network slice subnet identifier Managed object ID.
  • the method further includes: the network data analysis network element receives a second request, where the second request is used to request data analysis; the network data analysis network element receives the aforementioned data to be acquired from the OAM system; Perform data analysis on the data to be acquired, and obtain an analysis result; the specific implementation manner of the aforementioned network data analysis network element determining the data source to which the data to be acquired belongs may be: the network data analysis network element determines the data source to which the data to be acquired belongs according to the second request. data source.
  • the second request includes an identification of the data source.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system; the method further includes: a network data analysis network element obtains the domain name of the data source
  • the specific implementation of the aforementioned network data analysis network element to determine the object identifier of the data source in the OAM system according to the first information may be: the network data analysis network element obtains the data from the domain name mapping of the data source according to the mapping rule The object identifier of the source in the OAM system.
  • the object identifier includes a third identifier and a fourth identifier;
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the the second mapping rule between the fourth identifiers;
  • the method further includes: the network data analysis network element obtains the host name of the data source; the network data analysis network element maps the data source from the domain name of the data source according to the mapping rule.
  • the specific implementation of the object identifier of the data source in the OAM system may be as follows: the network data analysis network element obtains the third identifier from the domain name of the data source according to the first mapping rule; and according to the second mapping rule, The fourth identifier is obtained from the hostname mapping of the data source.
  • the specific implementation manner of the foregoing network data analysis network element acquiring the domain name of the data source may be: the network data analysis network element sends a third request to the network warehouse function NRF network element, where the third request is used to request to acquire The domain name of the data source; the network data analysis network element receives the domain name of the data source from the NRF network element.
  • the network data analysis network element obtains the first information, including any one of the following: the network data analysis network element obtains the first information from the OAM system or the NRF network element; the network data analysis network element obtains the first information from the OAM system or the NRF network element; The NRF network element obtains a network element configuration file, the network element configuration file includes first information; the network data analysis network element obtains the first information from the memory of the network data analysis network element.
  • the network element configuration file selects a configuration file of a network element for the network data analysis network element or network slice.
  • the data source includes one or more of the following: a network element, an interface of the network element, or configuration data of the network element.
  • the embodiments of the present application provide another data acquisition method, which is applied to an operation management and maintenance OAM system, where the system includes a management device.
  • the execution body of the method may be a management device, or may be a chip applied in the management device.
  • the method includes: a management device generates first information, and sends the first information to a first network element; wherein the first information is used to determine the object identifier in the OAM system of the data source to which the data to be acquired belongs.
  • the first information is sent to a first network element
  • the first network element may be a network data analysis network element, or the network data analysis network element may acquire the first information from the first network element, so that The network data analysis network element can determine the object identifier of the data source in the OAM system according to the first information.
  • the network data analysis network element does not need to obtain the entire managed object database of the OAM system, thereby facilitating network data analysis. The process by which a network element obtains data from the OAM system.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following: a relationship between an identifier of the network slice and an object identifier of the network slice in the OAM system Correspondence; the correspondence between the identifier of the network slice and the object identifier of the network slice subnet in the network slice in the OAM system; the identifier of the network slice subnet in the network slice and the network slice in the OAM system The corresponding relationship between the object identifiers of the network slice; or, the corresponding relationship between the identifier of the network slice subnet in the network slice and the object identifier of the network slice subnet in the OAM system.
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes a rule for generating object identifiers of the data source in the OAM system.
  • the object identifier includes a first identifier and a second identifier
  • the generation rule includes a first generation rule and a second generation rule, wherein the first generation rule includes analyzing the domain name of the network element according to the network data.
  • a rule for the first identification, the second generation rule includes a rule for generating the second identification according to the identification of the data source.
  • the identifier of the data source includes network slice selection assistance information and/or a network slice subnet identifier;
  • the object identifier of the data source in the OAM system includes a network slice managed object identifier and/or a network slice sub-network identifier Web managed object identifier.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • the object identifier includes a third identifier and a fourth identifier;
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the A second mapping rule between the fourth identifiers.
  • the specific implementation manner of the foregoing management device sending the first information to the first network element may be: the management device sends a configuration command to the first network element, where the configuration command includes the first information; or, the management The device sends a network element configuration file to the first network element, where the network element configuration file includes the first information.
  • the network element configuration file selects a configuration file of a network element for a network data analysis network element or a network slice.
  • the data source includes one or more of the following: a network element, an interface of the network element, or configuration data of the network element.
  • the first network element includes one or more of the following: a network slice selection network element, a network warehouse function NRF network element, or a network data analysis network element.
  • an embodiment of the present application provides a communication device, and the communication device has some or all of the functions of the network data analysis network element in the method example described in the first aspect above.
  • the function of the communication device may have the function of the present application.
  • Some or all of the functions in the embodiments may also have the functions of independently implementing any one of the embodiments in this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication apparatus may include a processing unit and a communication unit, and the processing unit is configured to support the communication apparatus to perform the corresponding functions in the above method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the communication device may also include a storage unit for coupling with the processing unit and the sending unit, which stores computer programs and data necessary for the communication device.
  • the communication device includes: a processing unit, configured to determine the data source to which the data to be acquired belongs; acquire first information, and determine, according to the first information, that the data source is in the operation management and maintenance of the OAM system The object identifier in ; the communication unit is used to send a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device includes: a processor for determining a data source to which the data to be acquired belongs; acquiring first information, and determining, according to the first information, that the data source is operating the management and maintenance OAM system The object identifier in ; the transceiver is used to send a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • an embodiment of the present application provides another communication device, the communication device having to implement part or all of the functions of the management device in the method example described in the second aspect above, for example, the function of the communication device may have the functions of the Some or all of the functions in the embodiments may also have the functions of independently implementing any one of the embodiments in this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication apparatus may include a processing unit and a communication unit, and the processing unit is configured to support the communication apparatus to perform the corresponding functions in the above method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the communication device may also include a storage unit for coupling with the processing unit and the sending unit, which stores computer programs and data necessary for the communication device.
  • the communication device includes: a processing unit configured to generate first information, where the first information is used to determine an object identifier in the OAM system of a data source to which the data to be acquired belongs; a communication unit configured to use for sending the first information to the first network element.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device includes: a processor configured to generate first information, where the first information is used to determine an object identifier in the OAM system of a data source to which the data to be acquired belongs; a transceiver, configured with for sending the first information to the first network element.
  • an embodiment of the present application provides a data acquisition system, where the system includes one or more communication devices as in the third to fourth aspects.
  • an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions that, when executed by a communication device, cause the communication device to The method of the first aspect above is performed.
  • an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program includes program instructions that, when executed by a communication device, cause the communication device to The method of the second aspect above is performed.
  • the present application further provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present application also provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect above.
  • the present application provides a chip system
  • the chip system includes at least one processor and an interface, and is used to support a network data analysis network element to implement the functions involved in the first aspect, for example, determining or processing the above methods. At least one of the data and information involved.
  • the chip system further includes a memory, and the memory is used for storing computer programs and data necessary for analyzing the network element of the network data.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a chip system
  • the chip system includes at least one processor and an interface for supporting a management device in the OAM system to implement the functions involved in the second aspect, for example, determining or processing the above method At least one of the data and information referred to in .
  • the chip system further includes a memory for storing necessary computer programs and data for managing the device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Figure 1a is a schematic diagram of a network architecture for a 5G system
  • Fig. 1b is a schematic diagram of a tree structure provided by an embodiment of the present application.
  • Fig. 1c is a schematic diagram of another tree structure provided by an embodiment of the present application.
  • 1d is a schematic diagram of a system architecture applying an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a data acquisition method provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • FIG. 4a is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • 4b is a schematic diagram of the composition of an object identifier of a data source in an OAM system provided by an embodiment of the present application;
  • FIG. 5 is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • FIG. 1a is a schematic diagram of a network architecture of a 5G system, which may include an access network (AN) and a core network.
  • AN access network
  • core network a network architecture of a 5G system, which may include an access network (AN) and a core network.
  • AN is used to realize access-related functions, which can provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data according to user levels and service requirements.
  • the AN forwards control signals and user data between the terminal equipment and the core network.
  • the AN may include an AN device, and the AN device may be a device that provides access for terminal devices, and may include a radio access network (radio access network, RAN) device and an AN device.
  • the (R)AN device is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • (R)AN devices may include various forms of base stations, such as macro base stations, micro base stations (which may also be referred to as small cells), relay stations, access points, balloon stations, and the like.
  • the possible deployment forms of (R)AN equipment include: separation scenarios of centralized unit (centralized unit, CU) and distributed unit (distributed unit, DU) and single-site scenarios.
  • the CU can support radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP) and other protocols;
  • DU can support radio link control layer (radio link control, RLC), medium access control layer (media access control, MAC) and physical layer protocols.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • DU can support radio link control layer (radio link control, RLC), medium access control layer (media access control, MAC) and physical layer protocols.
  • RLC radio link control layer
  • MAC medium access control layer
  • the names of devices with base station functions may be different, for example, in 5G systems, called (R)AN or next-generation Node basestation (gNB) ); in a long term evolution (long term evolution, LTE) system, it is called an evolved NodeB (evolved NodeB, eNB or eNodeB).
  • the core network is responsible for maintaining the subscription data of the mobile network, and provides functions such as session management, mobility management, policy management, and security authentication for user equipment (UE).
  • the core network may include the following network elements: network data analysis, network slice selection, network function repository function (NF repository function, NRF), unified data management (unified data management, UDM), access and mobility management function (access and mobility management function) management function, AMF), user plane function (UPF), session management function (session management function, SMF), policy control function (policy control function, PCF), application function (application function, AF) and network opening Function (network exposure function, NEF).
  • the network data analysis network element can be used to collect data from network function (network function, NF) network elements, operation, administration, and maintenance (OAM) systems, and perform data analysis according to the acquired data. and/or forecast.
  • network function network function
  • OAM operation, administration, and maintenance
  • the network data analysis network element may be a network data analysis function (NWDAF) network element.
  • the network slice selection network element is used to select an appropriate network slice for terminal services.
  • the network slice selection network element may be a network slice selection function (NSSF) network element.
  • NSSF network slice selection function
  • the NRF network element mainly provides service registration, discovery and authorization, and maintains available network function (NF) instance information, which can realize on-demand configuration of network functions and services and interconnection between NFs.
  • the service registration refers to that the NF network element needs to be registered in the NRF network element before it can provide the service.
  • Service discovery means that when an NF network element needs other NF network elements to provide services for it, it needs to first perform service discovery through the NRF network element to discover the expected NF network element that provides services for it. For example, when the NF network element 1 needs the NF network element 2 to provide services for it, it needs to perform service discovery through the NRF network element first to discover the NF network element 2.
  • the UDM network element is used to manage user data, such as subscription data, authentication/authorization data, and so on.
  • the AMF network element is mainly responsible for the mobility management in the mobile network, such as user location update, user registration network, user handover, etc.
  • the UPF network element is mainly responsible for the forwarding and receiving of user data. It can receive user data from the data network and transmit it to the UE through the access network device; it can also receive user data from the UE through the access network device and forward it to the data network.
  • the SMF network element is mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions are, for example, allocating Internet Protocol (IP) addresses to users, and selecting a UPF that provides a packet forwarding function.
  • IP Internet Protocol
  • the PCF network element mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for acquiring user subscription information related to policy decisions.
  • the PCF network element may provide policies to the AMF network element and the SMF network element, such as a quality of service (quality of service, QoS) policy, a slice selection policy, and the like.
  • quality of service quality of service, QoS
  • PCF network elements can be divided into multiple entities, such as global PCF and PCF in slices, or session management PCF (Session Management PCF, SM-PCF) and access management PCF (Access Management PCF, AM). -PCF).
  • the AF network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.
  • the NEF network element can be used to perform protocol conversion for external and internal interaction, for example, to perform protocol conversion for the interaction between a 3GPP external network element and a 3GPP internal network element (eg, an SMF network element).
  • a 3GPP network can refer to a network defined by the 3GPP protocol, such as a mobile communication network, a public land mobile network (PLMN), a non-public network (NPN), and other networks that include an access network and a core network. It may be a fifth-generation communication (5th generation, 5G) network or a future evolved mobile communication network.
  • 5G fifth-generation communication
  • a data network can be used to provide data transmission services for terminals.
  • the UE can access the data network through an established protocol data unit (protocol data unit, PDU) session.
  • the data network can be a public data network (PDN) network, such as the Internet, or a local access data network (LADN), such as mobile edge computing (MEC). ) network of nodes, etc.
  • PDN public data network
  • LADN local access data network
  • MEC mobile edge computing
  • the network elements in the dotted box are service-oriented NF network elements
  • the interfaces between the NF network elements are service-oriented interfaces
  • the exchanged messages are service-oriented messages.
  • the data source may include one or more of the following: a network slice, a network slice subnet, a network element, a subnet composed of network elements, an interface of a network element, or configuration data of a network element.
  • the management data of the data source may specifically be network slice, network slice subnet, performance statistics data of network elements, or alarm information data.
  • the management data is the specific value of the network element configuration item, or the specific value of the network element interface configuration item.
  • the network slice is obtained from the abstract division of the physical network, an end-to-end logical network.
  • a physical network can be abstractly divided into multiple network slices. Each network slice is isolated and does not affect each other.
  • a network slice can be identified by a single network slice selection assistance information (S-NSSAI).
  • S-NSSAI network slice selection assistance information
  • the network can select a network slice for the service according to the S-NSSAI carried in the terminal service request, and establish a packet data unit session (packet date unit, PDU) session in the selected network slice to transmit service data.
  • PDU packet date unit
  • a network slice subnet refers to the wireless subnet part or core network part that constitutes a network slice.
  • the wireless subnet part that constitutes a network slice is called a network slice access network subnet
  • the core network part that constitutes a network slice is called a network slice.
  • Core network subnet The network slice access network subnet can be understood as an instance of the access network part in the network slice
  • the network slice core network subnet can be understood as an instance of the core network part in the network slice.
  • a network slice may include one or more network slice core network subnets.
  • a network slice core network subnet can be identified by a network slice instance identifier (Network Slice Instance Identifier, NSI ID).
  • NSI ID Network Slice Instance Identifier
  • the interface of the above network element is an N4 interface between a certain SMF and a certain UPF.
  • QI quality of service identifier
  • the above-mentioned network elements may be network elements in network slices or network slice subnets, or may not be network elements in network slices or network slice subnets.
  • the ID of the data source which is used to identify the data source.
  • the identification of the data source may select auxiliary information (such as S-NSSAI) for the network slice to identify the network slice.
  • the identifier of the data source can be the network slice subnet identifier, which is used to identify the network slice subnet.
  • the identifier of the data source may be S-NSSAI.
  • the identifier of the data source can be S-NSSAI+NSI ID.
  • the identifier of the data source may be the identifier of the network element. For example, when the data source is AMF, the identification of the data source is the AMF ID.
  • the network slice subnet identifier may also be referred to as a network slice instance identifier.
  • the S-NSSAI may be configured for the network slice by the OAM system after the network slice is created.
  • the NSI ID can be configured for the network slice core network subnet after the OAM system creates the network slice core network subnet.
  • a network slicing core network subnet may also be referred to as a core network slicing subnet
  • a network slicing access network subnet may also be referred to as an access network slicing subnet.
  • the object identifier of the data source in the OAM system which can be used to identify the data source in the OAM system.
  • the data source can be managed as a managed object instance (MOI) in the OAM system.
  • MOI managed object instance
  • the object identifier of the data source in the OAM system can be used to identify the MOI of the data source in the OAM system in the OAM system.
  • a wireless network in the southern area of the city is managed as a sub-network, and the wireless network may be referred to as the southern sub-network for short.
  • the wireless network includes three wireless devices (a, b, and c), where wireless device a is a base station device that can provide both 4G (eNB) and 5G (gNB) functions, and the area covered by the base station device can be divided into multiple Cell. It is assumed that the wireless device a provides 4G functions through eNB1 and 5G functions through gNB1, and the area covered by the gNB1 is divided into two cells (cell 1 and cell 2).
  • the MOIs of the above-mentioned data sources in the southern subnet (southern subnet, three wireless devices, eNB1, gNB1, cell 1, and cell 2) in the OAM system can form a tree structure, and the schematic diagram of the tree structure can be as follows shown in Figure 1b. Among them, each node in the tree structure is an MOI.
  • the MOI in the OAM system can also have different attributes, for example, the network slice has the S-NSSAI attribute, the core network subnet slice has the NSI ID attribute, different access network slice subnets can have different coverage areas, and each gNB can To configure one or more cells, SMF and UPF can configure their own service areas, and AMF can configure a tracking area (TA) list as its own service area.
  • TA tracking area
  • a network slice includes an access network slice subnet 1 and an access network slice subnet 2.
  • the access network slice subnet 1 includes gNB1 and gNB2, gNB1 is configured with cell 1 and cell 2, and the access network slice subnet 2 includes gNB3 and gNB4.
  • the network slice also includes core network slice subnet 1 and core network slice subnet 2, wherein core network slice subnet 1 includes SMF1, UPF1 and AMF, and core network slice subnet 2 includes the AMF, SMF2, UPF2 .
  • the MOIs of the above data sources in the network slice (network slice, access network slice subnet 1, access network slice subnet 2, core network slice subnet 1, core network slice subnet 2) in the OAM system can be composed of MOIs
  • a tree-like structure, a schematic diagram of the tree-like structure can be shown in Figure 1c.
  • the white filled box represents an MOI
  • the gray filled box represents the properties of the MOI.
  • the OAM system after the OAM system creates a new network slice or network slice subnet, it can create a tree structure of the network slice or network slice subnet in the OAM system, where the tree structure includes the network slice or network slice sub-network The MOI of the net in the OAM system.
  • the MOI may be identified by a distinguished name (DN), that is, the object identifier of the data source in the OAM system refers to the DN of the MOI of the data source in the OAM system. It should be noted that the DN mentioned later refers to the distinguished name.
  • DN distinguished name
  • the object identifier of the data source in the OAM system may be simply referred to as the object identifier of the data source.
  • the DN of the MOI of the network slice in the OAM system may be referred to as the DN of the network slice
  • the DN of the MOI of the network slice subnet in the OAM system may be referred to as the DN of the network slice subnet
  • the MOI of the network element in the OAM system can be referred to as the DN of the network element.
  • the DN of the network slice may be the object identifier generated for the network slice by the OAM system when the network slice is created; the DN of the network slice subnet may be the network slice subnet created by the OAM system when the network slice is created. Net-generated object identifiers.
  • a DN may include one or more relative distinguished names (RDNs).
  • RDNs relative distinguished names
  • a plurality of RDNs included in the DN may form an RDN list.
  • each RDN may be separated by a comma (“,”) in the RDN list.
  • the DN may include two types of RDNs, the first type of RDN is located at the leftmost of the RDN list that constitutes the DN, and this type of RDN may be called a domain component (Domain Component, DC).
  • the value of the DC can be a domain name, and the DN with the DC is globally unique.
  • the DN may include a DC.
  • the second type of RDN is the RDN other than the DC in the DN.
  • the DN may include one or more RDNs of the second type.
  • the value of the second type of RDN is related to the MOI identified by the DN.
  • the DN of the MOI corresponding to the cell 1 is as follows:
  • the value of DC is the domain name operatorA.com.
  • the DN indicates that the cell 1 is a cell that is divided and identified as 1 in the area covered by the gNB1 provided by the wireless device a in the southern subnet.
  • the OAM system may include one or more of the following network elements: Network Function Management Function (NFMF), Network Slice Management Function (NSMF), and Network Slice Subnet Management Function (Network Slice Subnet Management Function, NSSMF).
  • NFMF Network Function Management Function
  • NSMF Network Slice Management Function
  • NSSMF Network Slice Subnet Management Function
  • NFMF is used to manage network elements in the OAM system.
  • the management data of the network element can be obtained by calling a service or interface of the NFMF in the OAM system.
  • the NWDAF needs to obtain the configuration information of the NSSF, when invoking the configuration management service or interface of the OAM system to obtain the configuration information, specifically, the configuration management service or interface provided by the NFMF may be invoked.
  • the NWDAF needs to obtain the overload alarm information of the SMF, when invoking the alarm management service or interface of the OAM system to obtain the overload alarm information, specifically, the alarm management service or interface provided by the NFMF may be invoked.
  • NSMF is used to manage network slices in OAM systems.
  • the management data of the network slice can be obtained by calling a service or interface of the NSMF in the OAM system.
  • NWDAF key performance indicator
  • the call can be provided by NSMF. performance management service or interface.
  • NSSMF is used to manage network slice subnets in OAM systems.
  • a service or interface of the OAM system needs to be called to obtain management data of a network slice subnet
  • the OAM system can call a service or interface of the NSSMF to obtain the data of the network slice subnet.
  • NWDAF needs to obtain the KPI information of a certain network slice subnet
  • the performance management service or interface provided by NSSMF can be called.
  • the network slice can be created by NSMF, and the same is true.
  • the network slice subnet can be specifically created by NSSMF.
  • the DN of the MOI of the data source in the OAM system needs to be provided, that is, the object identifier of the data source in the OAM system.
  • the NWDAF needs to obtain the configuration information of the NSSF
  • the NWDAF needs to provide the DN of the MOI of the NSSF in the OAM system before invoking the configuration management service or interface of the OAM system to obtain the configuration information.
  • the NWDAF needs to obtain the KPI information of a network slice or a network slice subnet
  • the NWDAF needs to provide the DN of the MOI of the network slice or the network slice subnet in the OAM system before calling the performance management service or interface of the OAM system. to obtain the KPI information.
  • the data of the data source acquired from the OAM system may also be referred to as management data of the data source.
  • the NWDAF wants to obtain the management data of the managed objects in the OAM system
  • the NWDAF needs to have the entire managed object database of the OAM system, starting from the root node of the tree structure composed of the entire managed objects as shown in Figure 1c,
  • the managed object corresponding to the data source in the OAM system is found layer by layer, and then the data of the managed object is obtained. Therefore, the process for NWDAF to obtain the data of the managed object from the OAM system is complicated.
  • the present application provides a data acquisition method, system and device, which are used to simplify the process of NWDAF acquiring data of managed objects from the OAM system.
  • FIG. 1d is a schematic diagram of a system architecture to which an embodiment of the present application is applied.
  • the system architecture may include a network data analysis network element 101 and an OAM system 102 .
  • the network data analysis network element 101 may be the NWDAF network element in FIG. 1a.
  • the network data analysis network element 101 may be used to determine the data source to which the data to be acquired belongs; acquire the first information, and determine the object identifier of the data source in the OAM system according to the first information.
  • the object identifier of the data source in the OAM system may be the DN of the MOI of the data source in the OAM system.
  • the network data analysis network element 101 is further configured to send a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • the OAM system 102 is configured to, after receiving the first request from the network data analysis network element 101, obtain the data to be obtained according to the object identifier in the first request; and may also send the obtained data to the network data analysis network element 101. Data to be obtained.
  • the first information may include the following information:
  • the first information may include a correspondence between an identifier of a data source and an object identifier of the data source in the OAM system.
  • the identifier of a data source may include a correspondence between an identifier of a data source and an object identifier of the data source in the OAM system.
  • the first information may include a generation rule for generating the object identifier of the data source in the OAM system according to the identifier of the data source.
  • a generation rule for generating the object identifier of the data source in the OAM system according to the identifier of the data source.
  • the first information may include a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • mapping rule For the specific description of the mapping rule, refer to the description in the corresponding embodiment of FIG. 5 .
  • the network data analysis network element 101 can determine the object identifier of the data source in the OAM system according to the first information. In this way, the network data analysis network element 101 does not need to obtain the entire managed object database of the OAM system, which is beneficial to simplify the network Data analysis is the process in which the network element obtains the data of the managed object from the OAM system.
  • the first information can be associated with the identifier of the data source and the object identifier of the data source in the OAM system, or can associate the domain name of the data source with the object identifier of the data source in the OAM system .
  • the first information may also be referred to as association information.
  • the technologies described in the embodiments of this application can be used in various communication systems, such as a fourth-generation (4th generation, 4G) communication system, a 4.5G communication system, a 5G communication system, a system that integrates multiple communication systems, or a communication system that evolves in the future , such as 6G communication systems.
  • 4G fourth-generation
  • 5G fifth generation
  • 6G 6th generation
  • the network element names, message names, etc. mentioned in the embodiments of the present application are used as examples, and when applied to different communication systems, the network element and message names may be different, which are not limited in the embodiments of the present application.
  • the network data analysis network element is described by taking the NWDAF network element as an example, and the network slice selection network element as an NSSF network element as an example.
  • NWDAF Network Data Analysis network element
  • NSSF Network Slice Selection network element
  • the figures corresponding to the embodiments do not show the word "network element”, and the specific description of the embodiment does not indicate the word "network element”, but this does not affect the understanding of the embodiments of the present application.
  • the names of messages between network elements or the names of parameters in the messages in the following embodiments of the present application are just an example, and other names may also be used in specific implementations, which are not made in the embodiments of the present application. Specific restrictions.
  • FIG. 2 is a schematic flowchart of a data acquisition method provided by an embodiment of the present application. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step S201 The NWDAF network element determines the data source to which the data to be acquired belongs.
  • the data to be acquired may be network element configuration data, performance statistics data, KPIs of network slices, or KPIs of network slice subnets.
  • the NWDAF network element determines the data source to which the to-be-obtained data belongs when it is determined that the to-be-obtained data needs to be acquired from the OAM system.
  • the NWDAF network element may receive a second request, where the second request is used to request data analysis; and determine the data source to which the data to be acquired belongs according to the second request.
  • the second request includes the identifier of the data source, that is, the data source indicated by the identifier carried in the second request is the data source to which the data to be acquired belongs.
  • the data source may include a network slice and/or a network slice subnet
  • the identifier of the data source carried in the second request may include network slice selection assistance information (S-NSSAI) and/or network slice sub-network.
  • S-NSSAI network slice selection assistance information
  • NSI ID Network Identification
  • the NWDAF network element may analyze the second request to determine the data source to which the data to be acquired belongs. In this way, the second request does not carry the identity of the data source.
  • the NWDAF network element analyzes the second request, and can determine that the data source to which the data to be acquired belongs is the configuration data of the SMF network element, and the configuration data of the SMF network element includes the 5QI set preconfigured by the SMF network element.
  • the sender of the second request may be a certain network element or a terminal device, which is not limited in this embodiment of the present application.
  • Step S202 the NWDAF network element acquires the first information.
  • the first information is used to determine the object identifier in the OAM system of the data source to which the data to be acquired belongs.
  • the NWDAF network element may acquire the first information in any of the following manners:
  • the NWDAF network element acquires the first information from the OAM system or the NRF network element.
  • the OAM system or the NRF network element may actively send the first information to the NWDAF network element.
  • the NWDAF network element may send request 1 to the OAM system or the NRF network element to request to obtain the first information; after receiving the request 1, the OAM system or the NRF network element sends the first information to the NWDAF network element.
  • the NRF network element may acquire the first information from the OAM system or the NSSF network element, and then send the first information to the NWDAF network element.
  • the NSSF network element may acquire the first information from the OAM system, and then send the first information to the NRF network element.
  • the first information may actually come from the OAM system.
  • the OAM system may generate first information and send the first information to a first network element, where the first network element may be an NWDAF network element, an NSSF network element or an NRF network element.
  • the OAM system can directly send the first information to the NWDAF network element, or send the first information to the NWDAF network element through one or more network elements (ie, the NRF network element, or the NSSF network element and the NRF network element).
  • the OAM system may send a configuration command to the first network element, where the configuration command includes the first information.
  • the NWDAF network element obtains a network element configuration file (NF profile) from the OAM system or the NRF network element, and the network element configuration file includes the first information.
  • NF profile network element configuration file
  • the OAM system or the NRF network element may actively send the network element configuration file to the NWDAF network element.
  • the NWDAF network element may send request 2 to the OAM system or the NRF network element to request to obtain the network element configuration file; after receiving the request 2, the OAM system or the NRF network element sends the network element configuration file to the NWDAF network element .
  • the NRF network element may obtain the network element configuration file from the OAM system or the NSSF network element, and then send the network element configuration file to the NWDAF network element.
  • the NSSF network element can obtain the network element configuration file from the OAM system, and then send the network element configuration file to the NRF network element.
  • the network element configuration file may actually be derived from the OAM system.
  • the OAM system may generate the network element configuration file, and send the network element configuration file to the first network element, where the first network element may be an NWDAF network element, an NSSF network element, or an NRF network element.
  • the OAM system can directly send the network element configuration file to the NWDAF network element, or send the network element configuration file to the NWDAF network element through one or more network elements (ie, the NRF network element, or the NSSF network element and the NRF network element).
  • the network element configuration file may be a configuration file of an NWDAF network element or a configuration file of an NSSF network element.
  • the NWDAF network element acquires the first information from the memory of the NWDAF network element.
  • the NWDAF network element can obtain the first information locally.
  • the first information may be built in the NWDAF network element, or pre-configured in the NWDAF network element.
  • Step S203 The NWDAF network element determines the object identifier of the data source in the OAM system according to the first information.
  • the NWDAF network element may determine the object identifier of the data source in the OAM system according to the first information. For example, when the first information includes the correspondence between the identifier of the data source and the object identifier of the data source in the OAM system, the NWDAF network element may determine that the data source is in the OAM system according to the identifier of the data source and the correspondence Object identification in OAM systems.
  • Step S204 The NWDAF network element sends a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • the OAM system receives the first request.
  • the NWDAF network element may send a first request to the OAM system to request to acquire the to-be-obtained data.
  • the NWDAF network element calls the createMeasurementJob or subscribe service interface of the OAM system with the object ID as a parameter to obtain the performance statistics or alarm information data of the data source.
  • the NWDAF network element calls the getMOIAttribute service interface of the OAM system with the object ID as the parameter To obtain the specific value of the configuration item of the data source in the OAM system.
  • Step S205 The OAM system acquires the to-be-obtained data according to the object identifier.
  • the OAM system can obtain the data to be obtained according to the object identifier in the first request.
  • the OAM system includes a management device, and in each embodiment of the present application, the steps performed by the OAM system may be specifically performed by the management device.
  • the management device may be the aforementioned NFMF.
  • the NWDAF network element may specifically call the getMOIAttribute service interface of NFMF with the object identifier as a parameter.
  • the management device may be the aforementioned NSMF.
  • the NWDAF network element can specifically call the createMeasurementJob or subscribe service interface of the NSMF with the object identifier as a parameter.
  • the management device may be the aforementioned NSSMF.
  • the NWDAF network element can specifically call the createMeasurementJob or subscribe service interface of NSSMF with the object ID as a parameter.
  • Step S206 The OAM system sends the to-be-obtained data to the NWDAF network element.
  • the OAM system may send the to-be-obtained data to the NWDAF network element.
  • the NWDAF network element may perform data analysis according to the to-be-obtained data to obtain an analysis result.
  • the NWDAF network element may send the analysis result to the sender of the second request.
  • the NSMF in the OAM system may acquire the data to be acquired, and send the data to be acquired to the NWDAF network element.
  • the data source to which the data to be acquired belongs is a network slice subnet
  • the NSSMF in the OAM system may acquire the to-be-obtained data, and send the to-be-obtained data to the NWDAF network element.
  • the data source to which the data to be acquired belongs is the network element (or the interface of the network element or the configuration data of the network element)
  • the to-be-obtained data can be acquired by the NFMF in the OAM system, and the to-be-obtained data can be sent to the NWDAF network element data.
  • the NWDAF network element can determine the object identifier of the data source in the OAM system according to the first information. In this way, the NWDAF network element does not need to acquire the entire managed object database of the OAM system, which is conducive to simplifying The process by which NWDAF network elements obtain data from the OAM system. Secondly, the NWDAF network element does not acquire the entire managed object database of the OAM system, so that the NWDAF network element does not have the authority to view all network management data, thereby helping to ensure network element security.
  • FIG. 3 is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • the data source is a network slice or a network slice subnet.
  • the method describes in detail how the NWDAF network element
  • the correspondence between the identifier of the data source and the object identifier of the data source in the OAM system determines the object identifier of the data source in the OAM system.
  • the method may include but is not limited to the following steps:
  • Step S301 The NWDAF network element determines the data source to which the data to be acquired belongs.
  • step S301 for the execution process of step S301, reference may be made to the specific description of step S201 in FIG. 2, which will not be repeated here.
  • Step S302 The NWDAF network element acquires first information, where the first information includes the correspondence between the identifier of the data source and the object identifier of the data source in the OAM system.
  • step S202 in FIG. 2 For the manner in which the NWDAF network element obtains the first information, reference may be made to the specific description in step S202 in FIG. 2 , which will not be repeated here.
  • the identification of the data source in the first information may be used to identify a network slice or a network slice subnet.
  • the identifier of the data source may include network slice selection assistance information and/or a network slice subnet identifier
  • the object identifier of the data source in the OAM system may include a network slice managed object identifier and/or a network slice subnet managed object identifier.
  • the identifier of the network slice is S-NSSAI
  • the object identifier is DN as an example
  • the NWDAF network element can determine the object identifier of the data source in the OAM system by querying Table 1.
  • the NWDAF network element may obtain the identifier of the data source from the foregoing second request. For details, refer to the description in step S201 in FIG. 2 , which will not be repeated here.
  • the OAM system can create the network slice or network slice subnet after creating the network slice or network slice subnet. Do not configure the correspondence between the identifier of the network slice and the object identifier of the network slice in the OAM system, or the OAM system may not configure the identifier of the network slice subnet and the object identifier of the network slice subnet in the OAM system Correspondence between.
  • the NWDAF network element cannot obtain the object identifier of the network slice or network slice subnet from the first information, and further cannot obtain the slice subnet included in the network slice and the DN of each network element (or cannot obtain the newly created network element).
  • the DN of each network element included in the network slice subnet cannot be called by the management service interface provided by the OAM system to obtain the data of the network slice or network slice subnet, which achieves the purpose of network security and authority control.
  • the first information may be included in a network element configuration file
  • the network element configuration file may include, but is not limited to, one or more of the following: the identification of the network slice and the identification of the network slice in the OAM system
  • the correspondence between object identifiers for example, called correspondence 1
  • the correspondence between the network slice identifier and the object identifier of the network slice subnet in the network slice in the OAM system for example, called correspondence 2
  • the correspondence between the identifier of the network slice subnet in the network slice and the object identifier of the network slice in the OAM system (as referred to as correspondence 3); or, the identifier of the network slice subnet in the network slice and this network slice
  • correspondence between the object identifiers of the network slice subnets in the OAM system for example, called correspondence 4).
  • the corresponding relationship 3 may specifically be the corresponding relationship between the identifier of the core network slice subnet in the network slice and the object identifier of the network slice in the OAM system.
  • the corresponding relationship 4 may specifically be a corresponding relationship between the identifier of the core network slice subnet in the network slice and the object identifier of the core network slice subnet in the OAM system.
  • the specific form of the corresponding relationship included in the network element configuration file may be: S-NSSAI: ⁇ DN of the network slice ⁇ .
  • the identifier of a network slice may be the same as the object identifier in the OAM system of one or more network slice subnets (such as access network slice subnets and/or core network slice subnets) in the network slice Corresponding. That is, after acquiring the corresponding relationship 2 and the identifier of the network slice, the NWDAF network element can know the object identifier of the network slice subnet in the network slice in the OAM system. Taking the identifier of the network slice as S-NSSAI and the identifier of the object as DN as an example, one S-NSSAI may correspond to the DN of one or more network slice subnets in the OAM system.
  • the specific form of the corresponding relationship included in the network element configuration file may be: S-NSSAI: ⁇ DN of the network slice, one or more ANs DN of slice subnet, DN of one or more CN slice subnets ⁇ .
  • the corresponding relationship included in the network element configuration file is: S-NSSAI#1: ⁇ DN of network slice, DN of AN slice subnet 1 and AN slice child DN of network 2, DN of CN slice subnet 1 and DN of CN slice subnet 2 ⁇ .
  • S-NSSAI#1 ⁇ DN of network slice, DN list of AN slice subnet: ⁇ DN of AN slice subnet 1, DN of AN slice subnet 2 ⁇ , DN list of CN slice subnet: ⁇ CN The DN of the slice subnet 1, the DN of the CN slice subnet 2 ⁇ .
  • the specific form of the corresponding relationship included in the network element configuration file may be: S-NSSAI+NSI ID: ⁇ DN of the network slice ⁇ .
  • the specific form of the corresponding relationship included in the network element configuration file may be: S-NSSAI+NSI ID: ⁇ DN of the CN slice subnet ⁇ .
  • the corresponding relationship included in the network element configuration file is: ⁇ S-NSSAI#1+NSI ID#1: DN of CN slice subnet 1; S-NSSAI #1+NSI ID#2: DN of CN slice subnet 2 ⁇ .
  • the network element configuration file includes a corresponding relationship 1, a corresponding relationship 2 and a corresponding relationship 4, and the corresponding relationship 4 is specifically the identification of the core network slice subnet in the network slice and the core network slice subnet in the OAM system
  • the corresponding relationship between the object identifiers then the specific form of the corresponding relationship included in the network element configuration file may be: S-NSSAI: ⁇ DN of network slice, ⁇ NSI ID: DN of CN slice subnet ⁇ .
  • the corresponding relationship included in the network element configuration file is: S-NSSAI#1: ⁇ DN of network slice, DN list of AN slice subnet (optional) , DN list of CN slice subnets: ⁇ NSI ID#1: DN of CN slice subnet 1; NSI ID#2: DN of CN slice subnet 2 ⁇ .
  • the NWDAF network element can select the required corresponding relationship according to the determined data source. , and then proceed to the next steps.
  • Step S303 The NWDAF network element determines the object identifier of the data source in the OAM system according to the identifier of the data source and the corresponding relationship.
  • the NWDAF network element After acquiring the identifier of the data source to which the data to be acquired belongs, the NWDAF network element can query Table 1 to determine the object identifier of the data source in the OAM system.
  • the network element configuration file may include one or more correspondences among the correspondence 1, the correspondence 2, the correspondence 3, and the correspondence 4. If the data source to which the data to be acquired belongs is a network slice subnet, the NWDAF network element can determine the object identifier of the data source in the OAM system according to the identifier of the data source and the corresponding relationship 4 in the network element configuration file.
  • Step S304 The NWDAF network element sends a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • Step S305 The OAM system acquires the to-be-obtained data according to the object identifier.
  • Step S306 The OAM system sends the to-be-obtained data to the NWDAF network element.
  • the NWDAF network element can determine the object identifier of the data source in the OAM system according to the correspondence between the identifier of the data source and the object identifier of the data source in the OAM system. In this way, The NWDAF network element does not need to acquire the entire managed object database of the OAM system, which is beneficial to simplify the process of the NWDAF network element acquiring data from the OAM system. Secondly, the NWDAF network element does not acquire the entire managed object database of the OAM system, so that the NWDAF network element does not have the authority to view all network management data, thereby helping to ensure network element security.
  • FIG. 4a is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • the data source is a network slice or a network slice subnet.
  • the method describes in detail how the NWDAF network element
  • the identification of the data source and the generation rule of the object identification of the data source in the OAM system are used to generate the object identification of the data source in the OAM system.
  • the method may include but is not limited to the following steps:
  • Step S401 The NWDAF network element determines the data source to which the data to be acquired belongs.
  • step S401 for the execution process of step S401, reference may be made to the specific description of step S201 in FIG. 2, which will not be repeated here.
  • Step S402 The NWDAF network element acquires first information, where the first information includes a rule for generating object identifiers of the data source in the OAM system.
  • step S202 in FIG. 2 For the manner in which the NWDAF network element obtains the first information, reference may be made to the specific description in step S202 in FIG. 2 , which will not be repeated here.
  • the first information specifically includes a generation rule for generating the object identifier of the data source in the OAM system according to the identifier of the data source.
  • the NWDAF network element may obtain the identifier of the data source from the foregoing second request, and for details, refer to the description in step S201 in FIG. 2 , which will not be repeated here.
  • the generation rule included in the first information can be To: take the value of the identifier of the data source as the value of the RDN name.
  • the generation rule may be to use the value of the identifier of the network slice (that is, the value of S-NSSAI) as the value of the RDN name.
  • the generation rule may be to use the value of the identifier of the core network slice subnet (that is, the value of S-NSSAI and the value of NSI ID) as the value of the RDN name. Specifically, the generation rule may be to use the value of the S-NSSAI identifier of the core network slice subnet as the value of one RDN name, and use the value of the NSI ID of the core network slice subnet as the value of another RDN name .
  • S-NSSAI xxx and NSI ID yy indicate that the value of the S-NSSAI identifier of the core network slice subnet is xxx, the value of the NSI ID identifier of the core network slice subnet is yy, and the DN of the core network slice subnet
  • the generation rule may be the value of the identifier of the network slice to which the access network slice subnet belongs (that is, the value of S-NSSAI) as the value of the RDN name.
  • the generation rule may be that the value of the S-NSSAI identifier of the access network slice subnet is taken as the value of one RDN name, and the value of the S-NSSAI identifier of the access network slice subnet is taken as another value. The value of the RDN name.
  • S-NSSAI xxx indicates that the value of the S-NSSAI identifier of the access network slice subnet is xxx, and the value of the identifier of the access network slice subnet is also xxx, and the DN in the DN of the access network slice subnet
  • Step S403 The NWDAF network element generates the object identifier of the data source in the OAM system according to the generation rule and the identifier of the data source.
  • the NWDAF network element can generate the object identifier of the data source in the OAM system according to the generation rule and the identifier of the data source.
  • the object identifier of the data source in the OAM system includes a first identifier and a second identifier;
  • the aforementioned generation rule includes a first generation rule and a second generation rule; wherein the first generation rule may include The domain name of the meta generates a rule for the first identification, and the second generation rule may include a rule for generating the second identification according to the identification of the data source.
  • the NWDAF network element can generate the first identifier according to the first generation rule and the domain name of the NWDAF network element; and generate the second identifier according to the second generation rule and the identifier of the data source.
  • the object identifier of the data source in the OAM system may include a DC+RDN set, and the RDN set includes one or more RDNs.
  • the first identifier may include the former one or more adjacent RDNs in the DC and RDN set
  • the second identifier may include the latter one or more adjacent RDNs in the RDN set
  • the first identifier and the second identifier form a DC+RDN gather. That is to say, the position of the first identifier in the DN is higher than that of the second identifier in the DN.
  • the first generation rule generate the first identifier according to the top n-level domain name of the NWDAF network element.
  • n is an integer greater than or equal to 2.
  • the first generation rule is: take the first two-level domain names of the NWDAF network element as DCs, and take the third-level domain names to the first n-level domain names of the NWDAF network element as the respective RDNs in the first identifier
  • the value of the name may be determined by the OAM system, or may be stipulated in an agreement, which is not limited in this embodiment of the present application.
  • the NWDAF network element will be generated according to the second generation rule and the first example in the previous example. Once a rule is generated, it is possible to generate:
  • the aforementioned first identification may specifically include a first identification 1 and a first identification 2; the aforementioned first generation rule includes a first generation rule 1 and a first generation rule 2; wherein, the first generation rule 1 may include the first generation rule 1 according to NWDAF.
  • the rules for generating the first identifier 1 from the domain name of the network element please refer to the foregoing descriptions about the first generation rule and the first identifier for details.
  • the first generation rule 2 may include a rule for generating the first identifier 2 according to the hostname of the NWDAF network element.
  • the NWDAF network element can generate the first identification 1 according to the first generation rule 1 and the domain name of the NWDAF network element; and generate the first identification 1 according to the first generation rule 2 and the host name of the NWDAF network element.
  • the first identifier 2; and the second identifier is generated according to the second generation rule and the identifier of the data source.
  • the first identifier 1 may include the DC and the previous one or more adjacent RDNs in the RDN set
  • the first identifier 2 may include one or more RDNs in the RDN set adjacent to the RDN in the first identifier 1
  • the aforementioned second identifier may be one or more RDNs adjacent to the first identifier 2 in the RDN set.
  • FIG. 4b A schematic diagram of the composition of the object identification of the data source in the OAM system can be seen in Figure 4b. In FIG. 4b, it is taken as an example that the first identifier 1 includes one RDN, the first identifier 2 includes three RDNs, and the second identifier includes two RDNs.
  • the hostname consists of one or more characters separated by ".”
  • the first generation rule 2 may be: the letter part in each string part separated by ".” in the host name of the NWDAF network element is used as the RDN name, and the number part in each string is used as the RDN name. value.
  • the host name of the NWDAF network element is "nwdaf1.managedElement1"
  • the managedElement may be a physical device for managing the NWDAF network element. In other implementations, the managedElement may not be present. Optionally, whether there is a physical device managedElement for managing the NWDAF network element may depend on the operator's deployment. It should be noted that the above host name includes a specific network element (such as an NWDAF network element) for an example. In other feasible implementation manners, the host name may also include the interface or configuration data of the network element.
  • the domain name of the aforementioned NWDAF network element may be a fully qualified domain name (FQDN).
  • FQDN has both the host name and the domain name, and the name is connected by the symbol ".”.
  • the hostname is bigserver and the domain name is mycompany.com, then the FQDN is bigserver.mycompany.com.
  • Step S404 The NWDAF network element sends a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • Step S405 The OAM system acquires the to-be-obtained data according to the object identifier.
  • Step S406 The OAM system sends the data to be acquired to the NWDAF network element.
  • steps S504 to S506 reference may be made to the specific descriptions of steps S204 to S206 in FIG. 2 , which will not be repeated here.
  • the NWDAF network element can generate the object identifier of the data source in the OAM system according to the identifier of the data source and the generation rule of the object identifier of the data source in the OAM system. In this way, the NWDAF network element There is no need to acquire the entire managed object database of the OAM system, which is beneficial to simplify the process of acquiring data from the OAM system by the NWDAF network element. Secondly, the NWDAF network element does not acquire the entire managed object database of the OAM system, so that the NWDAF network element does not have the authority to view all network management data, thereby helping to ensure network element security.
  • a (new) network slice or network slice subnet can be generated according to the historically acquired generation rules Object identification in an OAM system.
  • FIG. 5 is a schematic flowchart of another data acquisition method provided by an embodiment of the present application.
  • the data source is a network element, an interface of a network element, or configuration data of a network element, and the method is described in detail.
  • NWDAF network element can obtain the object identifier of the data source in the OAM system from the domain name of the data source according to the mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • the method may include but is not limited to the following steps:
  • Step S501 The NWDAF network element determines the data source to which the data to be acquired belongs.
  • step S501 for the execution process of step S501 , reference may be made to the specific description of step S201 in FIG. 2 , which will not be repeated here.
  • Step S502a the NWDAF network element obtains the domain name of the data source.
  • the NWDAF network element can obtain the domain name of the data source in the following manner:
  • the NWDAF network element sends a third request to the NRF network element, where the third request is used to request to obtain the domain name of the data source; the NWDAF network element receives the domain name of the data source from the NRF network element. Or, if the data source is an NWDAF network element, the NWDAF network element may acquire the domain name of the NWDAF network element from the memory of the NWDAF network element.
  • the OAM system can only provide the IP address and not the domain name when configuring the network element.
  • the information registered by the network element in the NRF network element will not include its domain name, and the NWDAF network element cannot obtain the domain name of the network element from the NRF network element, and further, it is impossible to obtain the network element in the OAM system.
  • the object identifier of the NE cannot be obtained by calling the management service interface provided by the OAM system, so as to achieve the purpose of network security and authority control.
  • Step S502b The NWDAF network element acquires first information, where the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • step S202 in FIG. 2 For the manner in which the NWDAF network element obtains the first information, reference may be made to the specific description in step S202 in FIG. 2 , which will not be repeated here.
  • the mapping rule may be: mapping the top m-level domain name of the data source to the object identifier of the data source in the OAM system.
  • the object identifier of the data source in the OAM system may include a DC+RDN set, and the RDN set includes one or more RDNs.
  • the mapping rule may be: mapping the first two-level domain names of the data source to obtain the DC, and mapping from the third-level domain name of the data source to the first-m-level domain names of all levels to obtain the data source in the OAM system.
  • the value of m may be determined by the OAM system, or may be stipulated in an agreement, which is not limited in this embodiment of the present application.
  • the data source is an SMF network element
  • subNetwork is the name of the RDN.
  • step S502a and step S502b does not limit the execution order of step S502a and step S502b, and step S502a or step S502b may be executed first, or step S502a and step S502b may be executed simultaneously.
  • Step S503 The NWDAF network element obtains the object identifier of the data source in the OAM system from the domain name of the data source according to the mapping rule.
  • the object identifier of the data source in the OAM system may include a third identifier and a fourth identifier; the aforementioned first information may specifically include a first mapping rule between the domain name of the data source and the third identifier , and a second mapping rule between the hostname of the data source and the fourth identifier.
  • the first mapping rule refer to the description of the mapping rule in the foregoing.
  • the NWDAF network element can obtain the host name of the data source; map the third identifier from the domain name of the data source according to the first mapping rule; and obtain the third identifier from the host name of the data source according to the second mapping rule.
  • the fourth identifier is obtained by mapping.
  • the object identifier of the data source in the OAM system may include a DC+RDN set, and the RDN set includes one or more RDNs.
  • the third identifier may include the DC and the previous one or more adjacent RDNs in the RDN set, the fourth identifier may include the last one or more adjacent RDNs in the RDN set, and the third identifier and the fourth identifier form DC+RDN gather. That is to say, the position of the third identifier in the DN is higher than that of the fourth identifier in the DN.
  • the hostname consists of one or more characters separated by ".”
  • the first generation rule 2 may be: the letter part in each string part separated by ".” in the host name of the data source is used as the RDN name, and the number part in each string is used as the RDN. value.
  • the domain name of the aforementioned data source may be a fully qualified domain name (FQDN). FQDN has both hostname and domain name.
  • the managedElement may be a physical device for managing the SMF network element. In other implementations, the managedElement may not be present.
  • the host name includes a specific network element (such as an SMF network element) for an example.
  • the host name may also include the interface or configuration data of the network element.
  • the hostname includes N4 interface 1 (N4Inf1.smf1.managedElement1) between SMF1 and a UPF.
  • Step S504 The NWDAF network element sends a first request to the OAM system, where the first request includes the object identifier, and the first request is used for requesting to acquire the to-be-obtained data.
  • Step S505 The OAM system acquires the to-be-obtained data according to the object identifier.
  • Step S506 The OAM system sends the to-be-obtained data to the NWDAF network element.
  • steps S504 to S506 reference may be made to the specific descriptions of steps S204 to S206 in FIG. 2 , which will not be repeated here.
  • the NWDAF network element can further acquire the performance statistical indicators corresponding to the 5QI from the OAM system, such as each The number of QoS flows of 5QI, etc.
  • the NWDAF network element can obtain the configuration data of each NF including the access network network element from the OAM system, such as the cell list configured by the gNB, the service area configured by the SMF, the S-NSSAI list and NSI ID list configured by the NSSF, and the UPF capacity, deployment location, and other information.
  • the NWDAF network element can use the data obtained from the OAM system as the input data for data analysis.
  • the NWDAF network element obtains the DN of the MOI of the data source in the OAM system, it means that the NWDAF network element has obtained all the sub-MOIs whose vertices are the MOI in the tree structure to which the MOI belongs in the OAM system. DN.
  • the NWDAF network element obtains the DN of the wireless device a (one MOI) in the OAM, it means that the NWDAF network element obtains the MOIs of the wireless device a, eNB1, gNB1, cell 1 and cell 2 in the OAM. DN in OAM.
  • the NWDAF network element can map the domain name of the data source to obtain the data source in the OAM system according to the mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system. Object identification.
  • the NWDAF network element does not need to acquire the entire managed object database of the OAM system, which is beneficial to simplify the process of the NWDAF network element acquiring data from the OAM system.
  • the NWDAF network element does not acquire the entire managed object database of the OAM system, so that the NWDAF network element does not have the authority to view all network management data, thereby helping to ensure network element security.
  • the embodiments of the present application further provide corresponding apparatuses, including corresponding modules for executing the foregoing embodiments.
  • the modules may be software, hardware, or a combination of software and hardware.
  • FIG. 6 is a schematic structural diagram of a communication device provided by the present application.
  • the communication apparatus 600 shown in FIG. 6 includes a processing unit 601 and a communication unit 602 .
  • the apparatus 600 is a network data analysis network element:
  • the processing unit 601 is used to determine the data source to which the data to be acquired belongs; acquire the first information, and determine the object identifier of the data source in the operation management and maintenance OAM system according to the first information; the communication unit 602 , which is used to send a first request to the OAM system, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following: a relationship between an identifier of the network slice and an object identifier of the network slice in the OAM system Correspondence; the correspondence between the identifier of the network slice and the object identifier of the network slice subnet in the network slice in the OAM system; the identifier of the network slice subnet in the network slice and the network slice in the OAM system The corresponding relationship between the object identifiers of the network slice; or, the corresponding relationship between the identifier of the network slice subnet in the network slice and the object identifier of the network slice subnet in the OAM system.
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes the generation rule of the object identifier of the data source in the OAM system; the processing unit 601 is configured to determine the object identifier of the data source in the OAM system according to the first information, specifically using To: generate the object identifier of the data source in the OAM system according to the generation rule and the identifier of the data source.
  • the aforementioned object identifier includes a first identifier and a second identifier
  • the generation rule includes a first generation rule and a second generation rule
  • the processing unit 601 is configured to generate the data source according to the generation rule and the identifier of the data source.
  • the object identification of the data source in the OAM system it is specifically used to: generate the first identification according to the first generation rule and the domain name of the network data analysis network element; and according to the second generation rule and the identification of the data source , and generate the second identifier.
  • the identifier of the data source includes network slice selection assistance information and/or the network slice subnet identifier; the object identifier of the data source in the OAM system includes the network slice managed object identifier and/or the network slice subnet identifier Managed object ID.
  • the communication unit 602 is further configured to receive a second request, where the second request is used to request data analysis; the communication unit 602 is further configured to receive the aforementioned data to be acquired from the OAM system; the processing unit 601, It is also used to perform data analysis according to the data to be acquired to obtain an analysis result; when the processing unit 601 is used to determine the data source to which the data to be acquired belongs, it is specifically used to: determine the data source to which the data to be acquired belongs according to the second request .
  • the second request includes an identification of the data source.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system; the processing unit 601 is further configured to acquire the domain name of the data source; the processing unit 601 is used for determining the object identifier of the data source in the OAM system according to the first information, and is specifically used for: mapping the domain name of the data source to obtain the object identifier of the data source in the OAM system according to the mapping rule.
  • the object identifier includes a third identifier and a fourth identifier
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the The second mapping rule between the fourth identifiers
  • the processing unit 601 is further configured to acquire the host name of the data source
  • the processing unit 601 is configured to map from the domain name of the data source to obtain the data source in the data source according to the mapping rule
  • the object identification in the OAM system it is specifically used for: mapping the domain name of the data source to obtain the third identification according to the first mapping rule; and mapping the host name of the data source to obtain the third identification according to the second mapping rule Fourth logo.
  • the processing unit 601 when configured to obtain the domain name of the data source, it is specifically configured to: call the communication unit 602 to send a third request to the network warehouse function NRF network element, where the third request is used to request to obtain the data source and call the communication unit 602 to receive the domain name of the data source from the NRF network element.
  • the processing unit 601 when configured to acquire the first information, it is specifically used for any one of the following: acquiring the first information from the OAM system or the NRF network element; acquiring the network element configuration from the OAM system or the NRF network element file, the network element configuration file includes first information; the first information is acquired from the memory of the communication device 600 .
  • the network element configuration file is the configuration file of the communication apparatus 600 or the configuration file of the network slice selection network element.
  • the apparatus 600 When the apparatus 600 is a network data analysis network element, it is configured to implement the functions of the network data analysis network element in the embodiments shown in FIG. 2 to FIG. 5 .
  • the apparatus 600 is a management device in the OAM system: exemplarily, the processing unit 601 is configured to generate first information, where the first information is used to determine that the data source to which the data to be acquired belongs is in the OAM system
  • the communication unit 602 is configured to send the first information to the first network element.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following:
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes a rule for generating object identifiers of the data source in the OAM system.
  • the object identifier includes a first identifier and a second identifier
  • the generation rule includes a first generation rule and a second generation rule, wherein the first generation rule includes analyzing the domain name of the network element according to the network data.
  • a rule for the first identification, the second generation rule includes a rule for generating the second identification according to the identification of the data source.
  • the identifier of the data source includes network slice selection assistance information and/or a network slice subnet identifier;
  • the object identifier of the data source in the OAM system includes a network slice managed object identifier and/or a network slice sub-network identifier Web managed object identifier.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • the object identifier includes a third identifier and a fourth identifier;
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the A second mapping rule between the fourth identifiers.
  • the communication unit 602 when configured to send the first information to the first network element, it is specifically configured to: send a configuration command to the first network element, where the configuration command includes the first information; or, to the first network element The first network element sends a network element configuration file, where the network element configuration file includes the first information.
  • the network element configuration file selects a configuration file of a network element for a network data analysis network element or a network slice.
  • the first network element includes one or more of the following: a network slice selection network element, a network warehouse function NRF network element, or a network data analysis network element.
  • the apparatus 600 When the apparatus 600 is a management device in the OAM system, it is used to implement the functions of the management device in the embodiments shown in FIG. 2 to FIG. 5 .
  • FIG. 7 is a schematic structural diagram of another communication device provided by the present application.
  • the communication apparatus 700 shown in FIG. 7 includes at least one processor 701 , a memory 702 , and a transceiver 703 .
  • the memory 702 can be volatile memory, such as random access memory; the memory can also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD) or solid-state drive (solid-state drive, SSD), or memory 702 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. Memory 702 may be a combination of the above-described memories.
  • connection medium between the processor 701 , the memory 702 , and the transceiver 703 is not limited in the embodiments of the present application.
  • the transceiver 703, the memory 702, and the processor 701 are connected through a bus 704 in the figure.
  • the bus 704 is represented by a thick line in the figure.
  • the connection mode between other components is only for schematic illustration. It is not limited.
  • the bus 704 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the processor 701 may have a data sending and receiving function and be able to communicate with other devices.
  • an independent data communication unit such as a transceiver 703, may also be set to send and receive data; the processor 701 is communicating with other devices. During communication, data transmission can be performed through the transceiver 703 .
  • the dashed box in FIG. 7 indicates that the transceiver 703 can be set independently from the processor 701, or the transceiver 703 can also be integrated in the processor 701; the memory 702 can be set independently from the processor 701, or the memory 702 It can also be integrated in the processor 701 .
  • the processor in FIG. 7 can execute the instruction by calling the computer stored in the memory 702, so that the network data analysis network element executes any of the above method implementation.
  • the network data in the example analyzes the method performed by the network element.
  • the processor in FIG. 7 may execute the instructions by calling the computer stored in the memory 702, so that the management device executes any of the above method embodiments. Methods for managing device execution.
  • the functions/implementation processes of the processing unit and the communication unit in FIG. 6 can be implemented by calling the computer execution instructions stored in the memory 702 by the processor 701 in FIG. 7 .
  • the function/implementation process of the processing unit in FIG. 6 may be implemented by the processor 701 in FIG. 7 calling the computer-executed instructions stored in the memory 702, and the function/implementation process of the communication unit in FIG. device 703 to implement.
  • the communication apparatus 700 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors described in this application can be implemented in the following ways: integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuit boards (printed circuit boards) circuit board, PCB), electronic equipment, etc.
  • the processor can also be fabricated using the following IC process technologies: for example, complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • N-type metal oxide semiconductor nMetal-oxide-semiconductor
  • PMOS positive channel metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication apparatus described in the above embodiments may be a network data analysis network element or a management device in an OAM system.
  • the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited by FIG. 7 .
  • the communication apparatus may be a stand-alone device or may be part of a larger device.
  • the communication means may be:
  • the IC set can also include a storage component for storing data and computer programs;
  • ASIC such as modem (Modem);
  • the communication device may be a chip or a chip system
  • the chip shown in FIG. 8 includes an interface 801 and a processor 802 .
  • the number of interfaces 801 may be one or more, and the number of processors 802 may be multiple.
  • the processor 802 is used to determine the data source to which the data to be acquired belongs; acquire the first information, and determine the object identifier of the data source in the operation management and maintenance OAM system according to the first information; the interface 801 is used to report to the OAM The system sends a first request, where the first request includes the object identifier, and the first request is used to request to acquire the to-be-obtained data.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following: a relationship between an identifier of the network slice and an object identifier of the network slice in the OAM system Correspondence; the correspondence between the identifier of the network slice and the object identifier of the network slice subnet in the network slice in the OAM system; the identifier of the network slice subnet in the network slice and the network slice in the OAM system The corresponding relationship between the object identifiers of the network slice; or, the corresponding relationship between the identifier of the network slice subnet in the network slice and the object identifier of the network slice subnet in the OAM system.
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes the generation rule of the object identifier of the data source in the OAM system; the processor 802 is configured to determine the object identifier of the data source in the OAM system according to the first information, specifically using To: generate the object identifier of the data source in the OAM system according to the generation rule and the identifier of the data source.
  • the aforementioned object identifier includes a first identifier and a second identifier
  • the generation rule includes a first generation rule and a second generation rule
  • the processor 802 is configured to generate the data source according to the generation rule and the identifier of the data source.
  • the object identification of the data source in the OAM system it is specifically used to: generate the first identification according to the first generation rule and the domain name of the network data analysis network element; and according to the second generation rule and the identification of the data source , and generate the second identifier.
  • the identifier of the data source includes network slice selection assistance information and/or the network slice subnet identifier; the object identifier of the data source in the OAM system includes the network slice managed object identifier and/or the network slice subnet identifier Managed object ID.
  • the interface 801 is further configured to receive a second request, where the second request is used to request data analysis; the interface 801 is further configured to receive the aforementioned data to be acquired from the OAM system; the processor 802 is further configured to use Perform data analysis according to the data to be acquired to obtain an analysis result; when the processor 802 is configured to determine the data source to which the data to be acquired belongs, it is specifically configured to: determine the data source to which the data to be acquired belongs according to the second request.
  • the second request includes an identification of the data source.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system; the processor 802 is further configured to acquire the domain name of the data source; the processor 802 is used for determining the object identifier of the data source in the OAM system according to the first information, and is specifically used for: mapping the domain name of the data source to obtain the object identifier of the data source in the OAM system according to the mapping rule.
  • the object identifier includes a third identifier and a fourth identifier
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the The second mapping rule between the fourth identifiers
  • the processor 802 is further configured to obtain the host name of the data source
  • the processor 802 is configured to map the data source from the domain name of the data source according to the mapping rule to obtain the data source in
  • it is specifically used for: mapping the domain name of the data source to obtain the third identification according to the first mapping rule; and mapping the host name of the data source to obtain the third identification according to the second mapping rule Fourth logo.
  • the processor 802 when used to obtain the domain name of the data source, it is specifically configured to: call the interface 801 to send a third request to the network warehouse function NRF network element, where the third request is used to request to obtain the data source of the data source. domain name; and call interface 801 to receive the domain name of the data source from the NRF network element.
  • the processor 802 when configured to acquire the first information, it is specifically used for any one of the following: acquiring the first information from the OAM system or the NRF network element; acquiring the network element configuration from the OAM system or the NRF network element file, the network element configuration file includes first information; the first information is obtained from the memory of the aforementioned communication device.
  • the network element configuration file is a configuration file of the communication device or a network slice selection network element configuration file.
  • the operations performed by the interface 801 and the processor 802 may refer to the introduction about the network data analysis network element in the above-mentioned embodiments corresponding to FIG. 2 to FIG. 5 .
  • the processor 802 is configured to generate first information, where the first information is used to determine the object identifier in the OAM system of the data source to which the data to be acquired belongs; the interface 801 is configured to send the first information to the first network element.
  • the first information includes a correspondence between an identifier of the data source and an object identifier of the data source in the OAM system.
  • the data source includes a network slice or a subnet of network slices.
  • the first information is included in a network element configuration file
  • the network element configuration file includes one or more of the following: a relationship between an identifier of the network slice and an object identifier of the network slice in the OAM system Correspondence; the correspondence between the identifier of the network slice and the object identifier of the network slice subnet in the network slice in the OAM system; the identifier of the network slice subnet in the network slice and the network slice in the OAM system The corresponding relationship between the object identifiers of the network slice; or, the corresponding relationship between the identifier of the network slice subnet in the network slice and the object identifier of the network slice subnet in the OAM system.
  • the aforementioned data to be acquired is the key performance indicator KPI of the network slice, or the KPI of the network slice subnet.
  • the first information includes a rule for generating object identifiers of the data source in the OAM system.
  • the object identifier includes a first identifier and a second identifier
  • the generation rule includes a first generation rule and a second generation rule, wherein the first generation rule includes analyzing the domain name of the network element according to the network data.
  • a rule for the first identification, the second generation rule includes a rule for generating the second identification according to the identification of the data source.
  • the identifier of the data source includes network slice selection assistance information and/or a network slice subnet identifier;
  • the object identifier of the data source in the OAM system includes a network slice managed object identifier and/or a network slice sub-network identifier Web managed object identifier.
  • the first information includes a mapping rule between the domain name of the data source and the object identifier of the data source in the OAM system.
  • the object identifier includes a third identifier and a fourth identifier;
  • the first information specifically includes a first mapping rule between the domain name of the data source and the third identifier, and the host name of the data source and the A second mapping rule between the fourth identifiers.
  • the interface 801 when configured to send the first information to the first network element, it is specifically configured to: send a configuration command to the first network element, where the configuration command includes the first information; or, send the first information to the first network element.
  • a network element sends a network element configuration file, where the network element configuration file includes the first information.
  • the network element configuration file selects a configuration file of a network element for a network data analysis network element or a network slice.
  • the first network element includes one or more of the following: a network slice selection network element, a network warehouse function NRF network element, or a network data analysis network element.
  • the chip further includes a memory 803 for storing necessary computer programs and data.
  • the memory 803 can be set independently, or can be integrated with the processor 802, as shown by the dotted box in FIG. 8 .
  • An embodiment of the present application further provides a data acquisition system, and the system may include one or more of the network data analysis network elements in the embodiments corresponding to FIG. 2 to FIG. 5 and the management device in the OAM system. Optionally, it also includes the network slice selection network element and/or the network warehouse function NRF network element in the embodiments corresponding to FIG. 2 to FIG. 5 .
  • the present application also provides a computer-readable storage medium on which a computer program is stored, where the computer program includes program instructions, and when the program instructions are executed by a computer, the functions of any of the foregoing method embodiments are implemented.
  • the above-mentioned computer-readable storage medium includes, but is not limited to, flash memory, hard disk, and solid-state disk.
  • the present application also provides a computer program product, which implements the functions of any of the above method embodiments when the computer program product is executed by a computer.
  • a processing unit for performing these techniques at a communication device may be implemented on one or more general-purpose processors, digital signal processors ( digital signal processor (DSP), digital signal processing device, application specific integrated circuit (ASIC), programmable logic device, field programmable gate array (FPGA), or other programmable logic devices, Discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor, or alternatively, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration. accomplish.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state drives, SSD)) etc.
  • system and “network” are often used interchangeably herein.
  • the term “and/or” in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently The three cases of B, where A can be singular or plural, and B can be singular or plural.
  • Predefined in this application may be understood as defining, predefining, storing, pre-storing, pre-negotiating, pre-configuring, curing, or pre-firing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Bioethics (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种数据获取方法、系统及其装置，该方法包括：网络数据分析网元确定待获取数据所归属的数据源；并根据第一信息，确定该数据源在运行管理和维护OAM系统中的对象标识；向该OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。通过这种方式，可以简化网络数据分析网元从OAM系统获取被管理对象的数据的过程。

Description

一种数据获取方法、系统及其装置
本申请要求于2021年5月6日提交中国专利局、申请号为202110494318.X、申请名称为“一种数据获取方法、系统及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据获取方法、系统及其装置。
背景技术
运行管理和维护(operation,administration,and maintenance，OAM)系统可用于对网络和业务进行分析、预测、规划、配置、测试和故障管理等。OAM系统对网络和业务进行上述管理操作、维护操作，可生成关于网络和业务的大量数据。
目前，若NWDAF要获取OAM系统中被管理对象的数据，NWDAF需具备OAM系统的整个被管理对象数据库，因此，NWDAF从OAM系统获取被管理对象的数据的过程复杂。
发明内容
本申请实施例提供一种数据获取方法、系统及其装置，用于简化NWDAF从OAM系统获取被管理对象的数据的过程。
第一方面，本申请实施例提供一种数据获取方法，该方法的执行主体可以是网络数据分析网元，也可以是应用于网络数据分析网元中的芯片。该方法包括：网络数据分析网元确定待获取数据所归属的数据源；获取第一信息，该第一信息用于确定该数据源在OAM系统中的对象标识；并根据该第一信息确定该数据源在运行管理和维护OAM系统中的对象标识；向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。需要说明的是，该第一信息可以关联数据源的标识与该数据源在OAM系统中的对象标识，或者，可以关联数据源的域名与该数据源在OAM系统中的对象标识。该第一信息还可以称为关联信息。
在该技术方案中，网络数据分析网元根据第一信息可确定数据源在OAM系统中的对象标识，在这种方式下，网络数据分析网元无需获取OAM系统的整个被管理对象数据库，从而有利于简化网络数据分析网元从OAM系统获取数据的过程。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在该技术方案中，通过查询该对应关系即可得到数据源在OAM系统中的对象标识，从而有利于简化网络数据分析网元从OAM系统获取数据的过程。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该 网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括该数据源在OAM系统中的对象标识的生成规则；前述网络数据分析网元根据第一信息，确定该数据源在OAM系统中的对象标识的具体实施方式可以为：网络数据分析网元根据该生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识。
在该技术方案中，在数据源为网络切片或网络切片子网的情况下，即使新增了网络切片或网络切片子网，根据历史获取的生成规则也可以生成(新增的)网络切片或网络切片子网在OAM系统中的对象标识。
在一种实现方式中，前述对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则；网络数据分析网元根据生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识的具体实施方式可以为：网络数据分析网元根据该第一生成规则以及该网络数据分析网元的域名，生成该第一标识；并根据该第二生成规则以及该数据源的标识，生成该第二标识。
在一种实现方式中，数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
在一种实现方式中，该方法还包括：网络数据分析网元接收第二请求，该第二请求用于请求进行数据分析；网络数据分析网元从OAM系统接收前述待获取数据；并根据该待获取数据进行数据分析，得到分析结果；前述网络数据分析网元确定待获取数据所归属的数据源的具体实施方式可以为：网络数据分析网元根据该第二请求确定待获取数据所归属的数据源。
在一种实现方式中，该第二请求包括该数据源的标识。
在一种实现方式中，第一信息包括该数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则；该方法还包括：网络数据分析网元获取该数据源的该域名；前述网络数据分析网元根据第一信息，确定该数据源在OAM系统中的对象标识的具体实施方式可以为：网络数据分析网元根据该映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则；该方法还包括：网络数据分析网元获取该数据源的所述主机名；前述网络数据分析网元根据映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识的具体实施方式可以为：网络数据分析网元根据该第一映射规则，从该数据源的域名映射得到该第三标识；并根据该第二映射规则，从该数据源的主机名映射得到该第四标识。
在一种实现方式中，前述网络数据分析网元获取数据源的域名的具体实施方式可以为：网络数据分析网元向网络仓库功能NRF网元发送第三请求，该第三请求用于请求获取该数据源的域名；该网络数据分析网元从该NRF网元接收该数据源的域名。
在一种实现方式中，网络数据分析网元获取第一信息，包括以下任一项：网络数据分析网元从OAM系统或者NRF网元获取该第一信息；网络数据分析网元从OAM系统或NRF网 元获取网元配置文件，该网元配置文件包括第一信息；网络数据分析网元从该网络数据分析网元的存储器中获取该第一信息。
在一种实现方式中，该网元配置文件为该网络数据分析网元或网络切片选择网元的配置文件。
在一种实现方式中，数据源包括以下一项或多项：网元、网元的接口或网元的配置数据。
第二方面，本申请实施例提供另一种数据获取方法，应用于运行管理和维护OAM系统，该系统包括管理设备。该方法的执行主体可以是管理设备，也可以是应用于管理设备中的芯片。该方法包括：管理设备产生第一信息，并向第一网元发送该第一信息；其中，该第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识。
在该技术方案中，向第一网元发送第一信息，该第一网元可以为网络数据分析网元，或者网络数据分析网元可以从该第一网元中获取该第一信息，使得网络数据分析网元可以根据第一信息确定数据源在OAM系统中的对象标识，在这种方式下，网络数据分析网元无需获取OAM系统的整个被管理对象数据库，从而有利于简化网络数据分析网元从OAM系统获取数据的过程。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括数据源在OAM系统中的对象标识的生成规则。
在一种实现方式中，该对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则，其中，第一生成规则包括根据网络数据分析网元的域名生成该第一标识的规则，该第二生成规则包括根据该数据源的标识生成该第二标识的规则。
在一种实现方式中，该数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
在一种实现方式中，第一信息包括数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则。
在一种实现方式中，前述管理设备向第一网元发送第一信息的具体实施方式可以为：管理设备向第一网元发送配置命令，该配置命令中包括该第一信息；或者，管理设备向该第一网元发送网元配置文件，该网元配置文件包括该第一信息。
在一种实现方式中，网元配置文件为网络数据分析网元或网络切片选择网元的配置文件。
在一种实现方式中，数据源包括以下一项或多项：网元、网元的接口或网元的配置数据。
在一种实现方式中，该第一网元包括以下一项或多项：网络切片选择网元、网络仓库功能NRF网元或网络数据分析网元。
第三方面，本申请实施例提供了一种通信装置，该通信装置具有实现上述第一方面所述的方法示例中网络数据分析网元的部分或全部功能，比如通信装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括处理单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储单元，所述存储单元用于与处理单元和发送单元耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：处理单元，用于确定待获取数据所归属的数据源；获取第一信息，并根据该第一信息确定该数据源在运行管理和维护OAM系统中的对象标识；通信单元，用于向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，所述通信装置包括：处理器，用于确定待获取数据所归属的数据源；获取第一信息，并根据该第一信息确定该数据源在运行管理和维护OAM系统中的对象标识；收发器，用于向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
第四方面，本申请实施例提供了另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中管理设备的部分或全部功能，比如通信装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括处理单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储单元，所述存储单元用于与处理单元和发送单元耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：处理单元，用于产生第一信息，该第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识；通信单元，用于向第一网元发送该第一信息。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，所述通信装置包括：处理器，用于产生第一信息，该第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识；收发器，用于向第一网元发送该第一信息。
第五方面，本申请实施例提供一种数据获取系统，该系统包括如第三方面至第四方面中的一个或多个通信装置。
第六方面，本发明实施例提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令被通信装置执行时使该通信装置执行上述第一方面的方法。
第七方面，本发明实施例提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令被通信装置执行时使该通信装置执行上述第二方面的方法。
第八方面，本申请还提供了一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第九方面，本申请还提供了一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络数据分析网元实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存网络数据分析网元必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十一方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持OAM系统中的管理设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存管理设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1a是为5G系统的网络架构的示意图；
图1b是本申请实施例提供的一种树状结构的示意图；
图1c是本申请实施例提供的另一种树状结构的示意图；
图1d是应用本申请实施例的系统架构示意图；
图2是本申请实施例提供的一种数据获取方法的流程示意图；
图3是本申请实施例提供的另一种数据获取方法的流程示意图；
图4a是本申请实施例提供的又一种数据获取方法的流程示意图；
图4b是本申请实施例提供的一种数据源在OAM系统中的对象标识的构成示意图；
图5是本申请实施例提供的又一种数据获取方法的流程示意图；
图6是本申请实施例提供的一种通信装置的结构示意图；
图7是本申请实施例提供的另一种通信装置的结构示意图；
图8是本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于理解，首先介绍本申请涉及的术语。
1、第五代通信(5 th generation，5G)系统的网络架构
请参见图1a，为5G系统的网络架构的示意图，该架构可包括接入网(access network，AN)和核心网。
其中，AN用于实现接入有关的功能，可以为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输隧道以传输用户数据。AN在终端设备与核心网之间转发控制信号和用户数据。
AN可以包括AN设备，AN设备可以是为终端设备提供接入的设备，可以包括无线接入网(radio access network，RAN)设备和AN设备。(R)AN设备，主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。(R)AN设备可以包括各种形式的基站，例如宏基站，微基站(也可称为小站)，中继站，接入点，气球站等。(R)AN设备可能的部署形态包括：集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)的分离场景以及单站点场景。其中，在分离场景中，CU可支持无线资源控制(radio resource control，RRC)、分组数据汇聚协议(packet data convergence protocol，PDCP)、业务数据适配协议(service data adaptation protocol，SDAP)等协议；DU可支持无线链路控制层(radio link control，RLC)、媒体接入控制层(media access control，MAC)和物理层协议。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为(R)AN或者下一代基站(next-generation Node basestation，gNB)；在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或eNodeB)。
核心网负责维护移动网络的签约数据，为用户设备(user equipment，UE)提供会话管理、移动性管理、策略管理以及安全认证等功能。核心网可以包括如下网元：网络数据分析、网络切片选择、网络功能仓储功能(NF repository function，NRF)、统一数据管理(unified data management，UDM)、接入和移动性管理功能(access and mobility management function，AMF)、用户面功能(user plane function，UPF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)、应用功能(application function，AF)和网络开放功能(network exposure function，NEF)。
其中，网络数据分析网元，可以用于从网络功能(network function，NF)网元、运行管理和维护(operation,administration,and maintenance，OAM)系统收集数据，并根据所获取的数据进行数据分析和/或预测。在5G通信系统中，网络数据分析网元可以是网络数据分析功能(network data analytics function，NWDAF)网元。
网络切片选择网元，用于为终端的业务选择合适的网络切片。在5G通信系统中，网络切片选择网元可以是网络切片选择功能(network slice selection function，NSSF)网元。
NRF网元，主要提供服务注册、发现和授权，并维护可用的网络功能(network function，NF)实例信息，可以实现网络功能和服务的按需配置以及NF之间的互连。其中，服务注册是指，NF网元需要在NRF网元进行注册登记后才能提供服务。服务发现是指，NF网元需要其他NF网元为其提供服务时，需先通过NRF网元执行服务发现，以发现所期望的为其提供服务的NF网元。例如，NF网元1需要NF网元2为其提供服务时，需先通过NRF网元进行服务发现，以发现NF网元2。
UDM网元，用于负责管理用户数据，例如签约数据、鉴权/授权数据等。
AMF网元，主要负责移动网络中的移动性管理，例如用户位置更新、用户注册网络、用户切换等。
UPF网元，主要负责用户数据的转发和接收，可以从数据网络接收用户数据，通过接入网络设备传输给UE；还可以通过接入网络设备从UE接收用户数据，转发至数据网络。
SMF网元，主要负责移动网络中的会话管理，例如会话建立、修改、释放。具体功能例如为用户分配互联网协议(internet protocol，IP)地址，选择提供报文转发功能的UPF等。
PCF网元，主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。PCF网元可以向AMF网元、SMF网元提供策略，例如服务质量(quality of service，QoS)策略、切片选择策略等。按照层次或功能，PCF网元可以分为多个实体，例如分为全局PCF和切片内的PCF，或者会话管理PCF(Session Management PCF，SM-PCF)和接入管理PCF(Access Management PCF，AM-PCF)。
AF网元，主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
NEF网元，可以用于对外部与内部的交互进行协议转化，例如，对3GPP外部网元与3GPP内部网元(如SMF网元)的交互进行协议转化。3GPP网络可以指3GPP协议定义的网络，如移动通信网络、公共陆地移动网(public land mobile network，PLMN)、非公共网络(non-public network，NPN)等包含接入网和核心网的网络，可以是第五代通信(5th generation，5G)网络或者未来演进的移动通信网络。
其中，数据网络(data network，DN)可用于为终端提供数据传输服务。UE可通过建立的协议数据单元(protocol data unit，PDU)会话，来访问数据网络。数据网络可以是公用数据网(public data network，PDN)网络，如因特网(internet)等，也可以是本地接入数据网络(local access data network，LADN)，如移动边缘计算(mobile edge computing，MEC)节点的网络等。
在图1a所示的架构中，虚线方框中的网元是服务化的NF网元，NF网元之间的接口为服务化接口，交互的消息为服务化的消息。
2、数据源
对于每个数据源，在OAM系统中可生成关于该数据源的管理数据。在本申请实施例中，数据源可以包括以下一项或多项：网络切片、网络切片子网、网元、网元组成的子网、网元的接口或网元的配置数据。数据源的管理数据具体的可以是网络切片、网络切片子网、网元的性能统计数据，或者告警信息数据。当数据源是网元的接口或网元的配置数据时，管理数据是网元配置项的具体数值，或者网元接口配置项的具体数值。
其中，网络切片是从物理网络抽象划分得到的，一个端到端的逻辑网络。一张物理网络可以被抽象划分成多个网络切片，各个网络切片之间是隔离的，互不影响。网络切片可通过单个网络切片选择辅助信息(Single-Network slice selection assistance information，S-NSSAI)来标识。网络可根据终端业务请求中携带的S-NSSAI为业务选择网络切片，并在所选择的网络切片内建立分组数据单元会话(packet date unit，PDU)会话来传输业务数据。
网络切片子网是指组成网络切片的无线子网部分或核心网部分，其中，组成网络切片的无线子网部分称为网络切片接入网子网，组成网络切片的核心网部分称为网络切片核心网子网。网络切片接入网子网可以理解为网络切片内接入网部分的实例，网络切片核心网子网可以理解为网络切片内核心网部分的实例。一个网络切片下可包括一个或多个网络切片核心网子网。在网络内可通过网络切片实例标识(Network Slice Instance Identifier，NSI ID)来标识网络切片核心网子网。
示例性的，上述网元的接口为某SMF与某UPF之间的N4接口。上述网元的配置数据为某SMF上预先配置的5G服务质量标示符(quality of service identifier，QI)集合，该5QI集合包括两个预先配置的5QI，分别为5QI＝1、5QI＝5。
上述网元可以是网络切片或网络切片子网中的网元，也可以不是网络切片或网络切片子网中的网元。
3、数据源的标识
数据源的标识，用于标识该数据源。数据源为网络切片时，该数据源的标识可以为网络切片选择辅助信息(如S-NSSAI)，用于标识网络切片。数据源为网络切片子网时，该数据源的标识可以为网络切片子网标识，用于标识网络切片子网。具体的，数据源为网络切片接入网子网时，该数据源的标识可以为S-NSSAI。数据源为网络切片核心网子网时，该数据源的标识可以为S-NSSAI+NSI ID。数据源为网元时，该数据源的标识可以为网元的标识。例如，数据源为AMF时，数据源的标识为AMF ID。
其中，网络切片子网标识还可以称为网络切片实例标识。S-NSSAI可以是OAM系统在创建网络切片后为该网络切片配置的。NSI ID可以是OAM系统在创建网络切片核心网子网后为该网络切片核心网子网配置的。在本申请中，网络切片核心网子网还可以称为核心网切片子网，同理，网络切片接入网子网还可以称为接入网切片子网。
4、数据源在OAM系统中的对象标识
数据源在OAM系统中的对象标识，可用于在OAM系统中标识该数据源。数据源在OAM系统内部可作为被管理对象实例(managed object instance，MOI)进行管理，数据源在OAM系统中的对象标识，具体可用于在OAM系统中标识该数据源在OAM系统中的MOI。
示例性的，城市南部区域内的一个无线网络，该无线网络被作为一个子网管理，该无线网络可简称为南部子网。该无线网络包括三个无线设备(a、b和c)，其中，无线设备a是可同时提供4G(eNB)和5G(gNB)功能的基站设备，基站设备覆盖的区域内可划分出多个小区(cell)。假设无线设备a通过eNB1提供4G功能，通过gNB1提供5G功能，且该gNB1覆盖的区域内划分2个小区(小区1和小区2)。该南部子网中的上述数据源(南部子网、三个无线设备、eNB1、gNB1、小区1、小区2)在OAM系统中的MOI可组成一树状结构，该树状结构的示意图可以如图1b所示。其中，树状结构中每个节点为一个MOI。
OAM系统中的MOI还可以具有不同的属性，例如网络切片具有S-NSSAI属性，核心网子网切片具有NSI ID属性，不同的接入网切片子网可以具有不同的覆盖区域，每个gNB可以配置一到多个小区，SMF和UPF可以配置各自的服务区，AMF可以配置跟踪区(tracking area，TA)列表作为自己的服务区。
示例性的，一网络切片中包括接入网切片子网1和接入网切片子网2。其中，接入网切片子网1内包括gNB1和gNB2，gNB1配置了小区1和小区2，接入网切片子网2内包括gNB3和gNB4。该网络切片中还包括核心网切片子网1和核心网切片子网2，其中，核心网切片子网1内包括SMF1、UPF1和AMF，核心网切片子网2内包括该AMF以及SMF2、UPF2。该网络切片中的上述数据源(网络切片、接入网切片子网1、接入网切片子网2、核心网切片子网1、核心网切片子网2)在OAM系统中的MOI可组成一树状结构，该树状结构的示意图可以如图1c所示。图1c中，白色填充方框表示一个MOI，灰色填充方框表示MOI的属性。在本申请中，OAM系统创建新的网络切片或网络切片子网后，可创建该网络切片或网络切片子网在OAM系统中的树状结构，该树状结构包括该网络切片或网络切片子网在OAM系统中的MOI。
在本申请实施例中，可通过可分辨名称(distinguished name，DN)来标识MOI，即数据源在OAM系统中的对象标识指该数据源在OAM系统中的MOI的DN。需要说明的是，后文提及的DN均指可分辨名称。
需要说明的是，为了方便描述，在本申请实施例中，数据源在OAM系统中的对象标识可以简称为数据源的对象标识。例如，网络切片在OAM系统中的MOI的DN可以简称为网络切片的DN，网络切片子网在OAM系统中的MOI的DN可简称为网络切片子网的DN，网元在OAM 系统中的MOI的DN可简称为网元的DN。网络切片的DN可以是由OAM系统在创建该网络切片时，为该网络切片生成的对象标识；网络切片子网的DN可以是由OAM系统在创建该网络切片子网时，为该网络切片子网生成的对象标识。
DN可包括一个或多个相对可分辨名称(relative distinguished name，RDN)。在一种实现方式中，DN包括的多个RDN可以组成一个RDN列表，示例性的，该RDN列表中可通过逗号(“，”)来分隔各个RDN。
可选的，DN可包括两类RDN，第一类RDN位于组成该DN的RDN列表的最左侧，该类RDN可以称为域组件(Domain Component，DC)。DC的取值可以为域名(domain name)，具有DC的DN是全局唯一的。可选的，DN可包括一个DC。第二类RDN为DN中除DC以外的RDN。DN可包括一个或多个第二类RDN。第二类RDN的取值与DN所标识的MOI相关。
示例性的，以图1b中的小区1为例，该小区1对应的MOI的DN如下：
DN＝“DC＝operatorA.com,subNetwork＝south,managedElement＝a,gNBFunction＝1,cell＝1”。
其中，DC的取值为域名operatorA.com。“subNetwork＝south”表示：小区1为南部子网中的小区。“managedElement＝a”表示：小区1为无线设备a提供的基站功能所划分出的小区。“gNBFunction＝1”表示：小区1为gNB1覆盖的区域内划分出的小区。“cell＝1”表示该小区1的标识为1。综上，该DN表示：小区1为南部子网中的无线设备a所提供的gNB1覆盖的区域内划分出的且标识为1的小区。
5、OAM系统
OAM系统中可包括如下网元中的一个或多个：网络功能管理功能(Network Function Management Function，NFMF)、网络切片管理功能(Network Slice Management Function，NSMF)和网络切片子网管理功能(Network Slice Subnet Management Function，NSSMF)。
其中，NFMF用于在OAM系统中管理网元。当需要调用OAM系统的某服务或接口以获取某网元的管理数据时，具体的，在OAM系统中可通过调用该NFMF的某服务或接口以获取该网元的管理数据。例如，若NWDAF需要获取NSSF的配置信息，那么在调用OAM系统的配置管理服务或接口以获取该配置信息时，具体的，调用的可以是NFMF提供的配置管理服务或接口。若NWDAF需要获取SMF的过载告警信息，那么在调用OAM系统的告警管理服务或接口以获取该过载告警信息时，具体的，调用的可以是NFMF提供的告警管理服务或接口。
NSMF用于在OAM系统中管理网络切片。当需要调用OAM系统的某服务或接口以获取某网络切片的数据时，具体的，在OAM系统中可通过调用该NSMF的某服务或接口以获取该网络切片的管理数据。例如，若NWDAF需要获取某个网络切片的关键性能指标(key performance indicator，KPI)信息，那么在调用OAM系统的性能管理服务或接口以获取该KPI信息时，具体的，调用的可以是NSMF提供的性能管理服务或接口。
NSSMF用于在OAM系统中管理网络切片子网。当需要调用OAM系统的某服务或接口以获取某网络切片子网的管理数据时，具体的，在OAM系统中可通过调用该NSSMF的某服务或接口以获取该网络切片子网的数据。例如，若NWDAF需要获取某个网络切片子网的KPI信息，那么在调用OAM系统的性能管理服务或接口以获取该KPI信息时，具体的，调用的可以是NSSMF提供的性能管理服务或接口。需要说明的是，网络切片具体可以是由NSMF创建的，同理。网络切片子网具体可以是由NSSMF创建的。
需要说明的是，若需要调用OAM系统提供的服务或接口以获取数据源的管理数据，需提供该数据源在OAM系统中的MOI的DN，即该数据源在OAM系统中的对象标识。例如，若NWDAF需要获取NSSF的配置信息，那么NWDAF需提供该NSSF在OAM系统的MOI的DN， 才能调用OAM系统的配置管理服务或接口以获取该配置信息。若NWDAF需要获得某个网络切片或某个网络切片子网的KPI信息，那么NWDAF需提供该网络切片或该网络切片子网在OAM系统的MOI的DN，才能调用OAM系统的性能管理服务或接口以获取该KPI信息。还需要说明的是，在本申请中，从OAM系统中获取的数据源的数据还可以称为该数据源的管理数据。
目前，若NWDAF要获取OAM系统中被管理对象的管理数据，NWDAF需具备OAM系统的整个被管理对象数据库，并从类似图1c所示的整个被管理对象组成的树状结构的根节点开始，逐层查找到数据源在OAM系统中对应的被管理对象，然后获取被管理对象的数据，因此，NWDAF从OAM系统获取被管理对象的数据的过程复杂。
鉴于此，本申请提供一种数据获取方法、系统及其装置，用于简化NWDAF从OAM系统获取被管理对象的数据的过程。
请参见图1d，为应用本申请实施例的系统架构示意图，该系统架构可包括网络数据分析网元101和OAM系统102。其中，网络数据分析网元101可以是图1a中的NWDAF网元。
其中，网络数据分析网元101可以用于确定待获取数据所归属的数据源；获取第一信息，并根据第一信息确定该数据源在OAM系统中的对象标识。其中，该数据源在OAM系统中的对象标识可以为该数据源在OAM系统中的MOI的DN。网络数据分析网元101在确定该对象标识后，还用于向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
OAM系统102用于在接收到来自网络数据分析网元101的第一请求后，根据该第一请求中的对象标识，获取该待获取数据；还可以向网络数据分析网元101发送所获取的待获取数据。
其中，第一信息可以包括如下信息：
在第一种实现方式中，第一信息可包括数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。关于该对应关系的具体描述可以详见图3对应实施例中的描述。
在第二种实现方式中，第一信息可包括根据数据源的标识生成该数据源在OAM系统中的对象标识的生成规则。关于该生成规则的具体描述可以详见图4a对应实施例中的描述。
在第三种实现方式中，第一信息可包括数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则。关于该映射规则的具体描述可以详见图5对应实施例中的描述。
网络数据分析网元101根据第一信息可确定数据源在OAM系统中的对象标识，在这种方式下，网络数据分析网元101无需获取OAM系统的整个被管理对象数据库，从而有利于简化网络数据分析网元从OAM系统获取被管理对象的数据的过程。
需要说明的是，由上述可知，该第一信息可以关联数据源的标识与该数据源在OAM系统中的对象标识，或者，可以关联数据源的域名与该数据源在OAM系统中的对象标识。该第一信息还可以称为关联信息。
本申请实施例描述的技术可用于各种通信系统，例如第四代(4th generation，4G)通信系统，4.5G通信系统，5G通信系统，多种通信系统融合的系统，或者未来演进的通信系统，如6G通信系统。需要说明的是，本申请实施例中提及的网元名称、消息名称等用于举例，应用于不同通信系统中，网元和消息名称可以不同，本申请实施例对此不做限定。
可以理解的是，本申请实施例描述的通信系统是为了更加清楚的说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域技术人员可知，随着系统架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本申请提供的数据获取方法、系统及其装置进行详细地介绍。需要说明的是，在数据获取方法的介绍中，网络数据分析网元以NWDAF网元为例，网络切片选择网元为NSSF网元为例进行介绍。为了简便描述，实施例对应的图未示出“网元”两个字，实施例的具体描述中未指出“网元”两个字，但是这样并不影响对本申请实施例的理解。还需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
请参见图2，图2是本申请实施例提供的一种数据获取方法的流程示意图。如图2所示，该方法可以包括但不限于如下步骤：
步骤S201：NWDAF网元确定待获取数据所归属的数据源。
其中，待获取数据可以为网元的配置数据、性能统计数据，网络切片的KPI，或者网络切片子网的KPI。
在本申请实施例中，NWDAF网元在确定需要从OAM系统获取待获取数据的情况下，确定该待获取数据所归属的数据源。在一种实现方式中，NWDAF网元可以接收第二请求，该第二请求用于请求进行数据分析；并根据该第二请求确定待获取数据所归属的数据源。
在一种可能的实现方式中，该第二请求包括该数据源的标识，即第二请求中携带的标识所指示的数据源即为待获取数据所归属的数据源。可选的，此时，该数据源可以包括网络切片和/或网络切片子网，第二请求中携带的数据源的标识可以包括网络切片选择辅助信息(S-NSSAI)和/或网络切片子网标识(NSI ID)。
在另一种可能的实现方式中，NWDAF网元可以对该第二请求进行分析，以确定该待获取数据所归属的数据源。在这种方式中，第二请求并未携带数据源的标识。示例性的，若第二请求用于请求统计某个5G服务质量标示符(5G quality of service identifier，5QI)的服务质量(quality of service identifier，QoS)流的数量，且5QI由SMF网元预先配置，则NWDAF网元对第二请求进行分析，可确定待获取数据所归属的数据源为SMF网元的配置数据，该SMF网元的配置数据包括该SMF网元预先配置的5QI集合。
其中，该第二请求的发送方可以为某网元或终端设备，本申请实施例对此不做限定。
步骤S202：NWDAF网元获取第一信息。
其中，第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识。在本申请实施例中，NWDAF网元可通过以下任一项方式以获取第一信息：
方式1、NWDAF网元从OAM系统或者NRF网元获取该第一信息。
在方式1中，OAM系统或者NRF网元可以主动向NWDAF网元发送该第一信息。或者，NWDAF网元可以向OAM系统或者NRF网元发送请求1，以请求获取该第一信息；OAM系统或者NRF网元在接收到该请求1后，向NWDAF网元发送该第一信息。
其中，NRF网元可以从OAM系统或者NSSF网元获取该第一信息，进而向NWDAF网元发送该第一信息。NSSF网元可以从OAM系统获取该第一信息，进而向NRF网元发送该第一信息。换言之，在方式1中，该第一信息实际可以来源于OAM系统。OAM系统可以产生第一信息，并向第一网元发送该第一信息，其中，该第一网元可以为NWDAF网元、NSSF网元或NRF网元。即OAM系统可以直接向NWDAF网元发送该第一信息，或者，通过一个或多个网元(即NRF网元，或NSSF网元和NRF网元)向NWDAF网元发送该第一信息。可选的，OAM系统可以向第一网元发送配置命令，该配置命令中包括该第一信息。
方式2、NWDAF网元从OAM系统或NRF网元获取网元配置文件(NF profile)，该网元 配置文件包括该第一信息。
在方式2中，OAM系统或者NRF网元可以主动向NWDAF网元发送该网元配置文件。或者，NWDAF网元可以向OAM系统或者NRF网元发送请求2，以请求获取该网元配置文件；OAM系统或者NRF网元在接收到该请求2后，向NWDAF网元发送该网元配置文件。
NRF网元可以从OAM系统或者NSSF网元获取该网元配置文件，进而向NWDAF网元发送该网元配置文件。NSSF网元可以从OAM系统获取该网元配置文件，进而向NRF网元发送该网元配置文件。换言之，在方式2中，该网元配置文件实际可以来源于OAM系统。OAM系统可以生成该网元配置文件，并向第一网元发送该网元配置文件，其中，该第一网元可以为NWDAF网元、NSSF网元或NRF网元。即OAM系统可以直接向NWDAF网元发送该网元配置文件，或者，通过一个或多个网元(即NRF网元，或NSSF网元和NRF网元)向NWDAF网元发送该网元配置文件。其中，该网元配置文件可以为NWDAF网元的配置文件或NSSF网元的配置文件。
方式3、NWDAF网元从NWDAF网元的存储器中获取该第一信息。换言之，NWDAF网元可以从本地获取该第一信息。可选的，该第一信息可以是内置于该NWDAF网元中，或者，预先配置于该NWDAF网元中。
步骤S203：NWDAF网元根据该第一信息，确定该数据源在OAM系统中的对象标识。
NWDAF网元在获取第一信息后，可以根据该第一信息，确定该数据源在OAM系统中的对象标识。例如，第一信息包括数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系的情况下，NWDAF网元可以根据该数据源的标识以及该对应关系，确定该数据源在OAM系统中的对象标识。
步骤S204：NWDAF网元向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。OAM系统接收该第一请求。
NWDAF网元在确定该数据源在OAM系统中的对象标识后，可以向OAM系统发送第一请求，以请求获取该待获取数据。例如NWDAF网元以该对象标识为参数调用OAM系统的createMeasurementJob或subscribe服务接口以获取数据源的性能统计数据或告警信息数据，再例如NWDAF网元以该对象标识为参数调用OAM系统的getMOIAttribute服务接口以获取数据源在OAM系统中的配置项的具体数值。
步骤S205：OAM系统根据该对象标识，获取该待获取数据。
OAM系统接收到第一请求后，可以根据该第一请求中的对象标识获取该待获取数据。
需要说明的是，OAM系统包括管理设备，在本申请各实施例中，由OAM系统执行的步骤具体可以是由该管理设备执行的。在数据源为网元、网元的接口或网元的配置数据的情况下，该管理设备可以为前述NFMF。此时，NWDAF网元以该对象标识为参数具体调用的可以是NFMF的getMOIAttribute服务接口。同理，在数据源为网络切片的情况下，该管理设备可以为前述NSMF。此时，NWDAF网元以该对象标识为参数具体调用的可以是NSMF的createMeasurementJob或subscribe服务接口。在数据源为网络切片子网的情况下，该管理设备可以为前述NSSMF。此时，NWDAF网元以该对象标识为参数具体调用的可以是NSSMF的createMeasurementJob或subscribe服务接口。
步骤S206：OAM系统向NWDAF网元发送该待获取数据。
OAM系统在获取该待获取数据后，可以向NWDAF网元发送该待获取数据。相应的，NWDAF网元在接收到该待获取数据后，可以根据该待获取数据进行数据分析，得到分析结果。可选的，NWDAF网元可以向前述第二请求的发送方发送该分析结果。
具体的，若该待获取数据所归属的数据源为网络切片，则可以由OAM系统中的NSMF获取该待获取数据，并向NWDAF网元发送该待获取数据。若该待获取数据所归属的数据源为网络切片子网，则可以由OAM系统中的NSSMF获取该待获取数据，并向NWDAF网元发送该待获取数据。若该待获取数据所归属的数据源为网元(或网元的接口或网元的配置数据)，则可以由OAM系统中的NFMF获取该待获取数据，并向NWDAF网元发送该待获取数据。
在本申请实施例中，NWDAF网元根据第一信息可确定数据源在OAM系统中的对象标识，在这种方式下，NWDAF网元无需获取OAM系统的整个被管理对象数据库，从而有利于简化NWDAF网元从OAM系统获取数据的过程。其次，NWDAF网元不获取OAM系统的整个被管理对象数据库，使得NWDAF网元不具有查看所有网络管理数据的权限，从而有利于确保网元安全。
请参见图3，图3是本申请实施例提供的另一种数据获取方法的流程示意图，在该实施例中数据源为网络切片或网络切片子网，该方法详细描述了NWDAF网元如何根据数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系，确定该数据源在OAM系统中的对象标识。该方法可以包括但不限于如下步骤：
步骤S301：NWDAF网元确定待获取数据所归属的数据源。
需要说明的是，步骤S301的执行过程可参见图2中步骤S201的具体描述，此处不再赘述。
步骤S302：NWDAF网元获取第一信息，该第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
NWDAF网元获取第一信息的方式可参见图2中步骤S202中的具体描述，此处不再赘述。
第一信息中的数据源的标识可以用于标识网络切片或网络切片子网。数据源的标识可以包括网络切片选择辅助信息和/或网络切片子网标识，该数据源在OAM系统中的对象标识可以包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
以第一信息中的数据源的标识用于标识网络切片，网络切片的标识为S-NSSAI，且对象标识为DN为例，该对应关系可以如表1所示：
表1对应关系
数据源的标识 该数据源在OAM系统中的对象标识
S-NSSAI 1 DN 1
S-NSSAI 2 DN 2
由表1可知，NWDAF网元在获取待获取数据所归属的数据源的标识后，通过查询表1，即可确定该数据源在OAM系统中的对象标识。可选的，NWDAF网元可以从前述第二请求中获取该数据源的标识，具体参见图2中步骤S201中的描述，此处不再赘述。
参见图2中步骤S202中的描述可知，该第一信息实际来源于OAM系统。需要说明的是，如果根据网络管理的权限控制和安全需求，不希望NWDAF网元获得某个网络切片或网络切片子网的数据时，OAM系统在创建该网络切片或网络切片子网后，可以不配置该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系，或者OAM系统可以不配置该网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。这样，NWDAF网元将无法从第一信息中获得该网络切片或网络切片子网的对象标识，进一步也无法获取该网络切片包括的切片子网和各个网元的DN(或无法获取该新创建的网络切片子网 包括的各个网元的DN)，也就无法调用OAM系统提供的管理服务接口获得该网络切片或网络切片子网的数据，达到了网络安全和权限控制的目的。
在一种实现方式中，该第一信息可以包括于网元配置文件中，该网元配置文件可以包括但不限于以下一项或多项：网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系(如称为对应关系1)；网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系(如称为对应关系2)；网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系(如称为对应关系3)；或者，网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系(如称为对应关系4)。可选的，对应关系3具体可以为网络切片中的核心网切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系。对应关系4具体可以为网络切片中的核心网切片子网的标识与该核心网切片子网在OAM系统中的对象标识之间的对应关系。
示例性的，若网元配置文件包括对应关系1，那么该网元配置文件中包括的对应关系的具体形式可以为：S-NSSAI:{网络切片的DN}。
在对应关系2中，一个网络切片的标识可以与该网络切片中的一个或多个网络切片子网(如接入网切片子网和/或核心网切片子网)在OAM系统中的对象标识相对应。即NWDAF网元获取对应关系2和网络切片的标识后，可获知该网络切片中的网络切片子网在OAM系统中的对象标识。以网络切片的标识为S-NSSAI，且对象标识为DN为例，一个S-NSSAI可以对应一个或多个网络切片子网在OAM系统中的DN。
示例性的，若网元配置文件包括对应关系1和对应关系2，那么该网元配置文件中包括的对应关系的具体形式可以为：S-NSSAI:{网络切片的DN，一个或多个AN切片子网的DN，一个或多个CN切片子网的DN}。将该具体形式应用于图1c所示的树状结构中，网元配置文件中包括的对应关系为：S-NSSAI#1:{网络切片的DN，AN切片子网1的DN和AN切片子网2的DN，CN切片子网1的DN和CN切片子网2的DN}。或者，S-NSSAI#1：{网络切片的DN，AN切片子网的DN列表：{AN切片子网1的DN，AN切片子网2的DN}，CN切片子网的DN列表：{CN切片子网1的DN，CN切片子网2的DN}}。
示例性的，若网元配置文件包括对应关系3，网络切片子网的标识为S-NSSAI+NSI ID，那么该网元配置文件中包括的对应关系的具体形式可以为：S-NSSAI+NSI ID:{网络切片的DN}。
示例性的，若网元配置文件包括对应关系4，且对应关系4具体为网络切片中的核心网切片子网的标识与该核心网切片子网在OAM系统中的对象标识之间的对应关系，那么该网元配置文件中包括的对应关系的具体形式可以为：S-NSSAI+NSI ID:{CN切片子网的DN}。将该具体形式应用于图1c所示的树状结构中，网元配置文件中包括的对应关系为：{S-NSSAI#1+NSI ID#1：CN切片子网1的DN；S-NSSAI#1+NSI ID#2：CN切片子网2的DN}。
示例性的，若网元配置文件包括对应关系1、对应关系2和对应关系4，且对应关系4具体为网络切片中的核心网切片子网的标识与该核心网切片子网在OAM系统中的对象标识之间的对应关系，那么该网元配置文件中包括的对应关系的具体形式可以为：S-NSSAI:{网络切片的DN,{NSI ID：CN切片子网的DN}}。将该具体形式应用于图1c所示的树状结构中，网元配置文件中包括的对应关系为：S-NSSAI#1：{网络切片的DN，AN切片子网的DN列表(可选)，CN切片子网的DN列表：{NSI ID#1：CN切片子网1的DN；NSI ID#2：CN切片子网2的DN}}。
如果网元配置文件同时包括上述对应关系1、对应关系2、对应关系3和对应关系4中的一种或多种对应关系，NWDAF网元可以根据确定的数据源，从中选择所需的对应关系，然后再执行后续步骤。
步骤S303：NWDAF网元根据该数据源的标识以及该对应关系，确定该数据源在OAM系统中的对象标识。
NWDAF网元在获取待获取数据所归属的数据源的标识后，可通过查询表1以确定该数据源在OAM系统中的对象标识。
由上述可知，网元配置文件中可包括对应关系1、对应关系2、对应关系3和对应关系4中的一种或多种对应关系。若待获取数据所归属的数据源为网络切片子网，则NWDAF网元可以根据该数据源的标识以及网元配置文件中的对应关系4，确定该数据源在OAM系统中的对象标识。
步骤S304：NWDAF网元向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
步骤S305：OAM系统根据该对象标识，获取该待获取数据。
步骤S306：OAM系统向NWDAF网元发送该待获取数据。
需要说明的是，步骤S304～步骤S306的执行过程可参见图2中步骤S204～步骤S206的具体描述，此处不再赘述。
在本申请实施例中，NWDAF网元根据数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系即可确定数据源在OAM系统中的对象标识，在这种方式下，NWDAF网元无需获取OAM系统的整个被管理对象数据库，从而有利于简化NWDAF网元从OAM系统获取数据的过程。其次，NWDAF网元不获取OAM系统的整个被管理对象数据库，使得NWDAF网元不具有查看所有网络管理数据的权限，从而有利于确保网元安全。
请参见图4a，图4a是本申请实施例提供的又一种数据获取方法的流程示意图，在该实施例中数据源为网络切片或网络切片子网，该方法详细描述了NWDAF网元如何根据数据源的标识以及数据源在OAM系统中的对象标识的生成规则，生成该数据源在OAM系统中的对象标识。该方法可以包括但不限于如下步骤：
步骤S401：NWDAF网元确定待获取数据所归属的数据源。
需要说明的是，步骤S401的执行过程可参见图2中步骤S201的具体描述，此处不再赘述。
步骤S402：NWDAF网元获取第一信息，第一信息包括该数据源在OAM系统中的对象标识的生成规则。
NWDAF网元获取第一信息的方式可参见图2中步骤S202中的具体描述，此处不再赘述。
其中，该第一信息具体包括根据该数据源的标识生成该数据源在OAM系统中的对象标识的生成规则。NWDAF网元可从前述第二请求中获取该数据源的标识，具体参见图2中步骤S201中的描述，此处不再赘述。
以该对象标识为DN，该DN包括一个或多个RDN，RDN包括RDN名称及其取值，且数据源的标识包括该数据源的标识的取值为例，第一信息包括的生成规则可以为：将数据源的标识的取值作为RDN名称的取值。具体的，若该数据源为网络切片，那么生成规则可以为将网络切片的标识的取值(即S-NSSAI的取值)作为RDN名称的取值。例如，S-NSSAI xxx表示网络切片的标识(S-NSSAI)的取值为“xxx”，网络切片的DN中的RDN名称包括 “networkslice”，那么根据该生成规则生成的RDN为“networkslice＝xxx”。
若该数据源为核心网切片子网，那么生成规则可以为将核心网切片子网的标识的取值(即S-NSSAI的取值和NSI ID的取值)作为RDN名称的取值。具体的，生成规则可以为将核心网切片子网的S-NSSAI标识的取值作为一个RDN名称的取值，并将核心网切片子网的NSI ID的取值作为另一RDN名称的取值。例如，S-NSSAI xxx和NSI ID yy表示核心网切片子网的S-NSSAI标识的取值为xxx，且核心网切片子网的NSI ID标识的取值为yy，核心网切片子网的DN中的RDN名称包括“networkslice”和“networkslicesubnet”，那么根据该生成规则生成的一个RDN为“networkslice＝xxx”，另一RDN为“networkslicesubnet＝yy”或者“networkslicesubnet＝CN-yy”。
若该数据源为接入网切片子网，那么生成规则可以为将该接入网切片子网所属的网络切片的标识的取值(即S-NSSAI的取值)作为RDN名称的取值。具体的，生成规则可以为将接入网切片子网的S-NSSAI标识的取值作为一个RDN名称的取值，并根据该接入网切片子网的S-NSSAI标识的取值作为另一RDN名称的取值。例如，S-NSSAI xxx表示接入网切片子网的S-NSSAI标识的取值为xxx，且接入网切片子网的标识的取值也为xxx，接入网切片子网的DN中的RDN名称包括“networkslice”和“networkslicesubnet”，那么根据该生成规则生成的一个RDN为“networkslice＝xxx”，另一RDN为“networkslicesubnet＝xxx”或者“networkslicesubnet＝RAN-xxx”或“networkslicesubnet＝AN-xxx”。
需要说明的是，上述用大写字母表示网络切片的标识，且用小写字母表示RDN的名称，是为了便于区分两者，仅用于举例，在具体实现中两者可以相同。
步骤S403：NWDAF网元根据该生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识。
具体的，NWDAF网元在获取该生成规则以及该数据源的标识后，可根据该生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识。
在一种实现方式中，数据源在OAM系统中的对象标识包括第一标识和第二标识；前述生成规则包括第一生成规则和第二生成规则；其中，第一生成规则可包括根据NWDAF网元的域名生成该第一标识的规则，第二生成规则可包括根据该数据源的标识生成该第二标识的规则。可以理解的是，NWDAF网元可以根据该第一生成规则以及该NWDAF网元的域名，生成该第一标识；并根据该第二生成规则以及该数据源的标识，生成该第二标识。
其中，数据源在OAM系统中的对象标识可包括DC+RDN集合，RDN集合包括一个或多个RDN。第一标识可以包括DC和RDN集合中的前一个或多个相邻RDN，第二标识可以包括RDN集合中的后一个或多个相邻RDN，第一标识和第二标识组成了DC+RDN集合。也就是说，第一标识在DN中的位置相较于第二标识在DN中的位置更靠前。关于第二生成规则的内容可参见步骤S402中的具体描述，此处不再赘述。
第一生成规则：根据NWDAF网元的前n级域名生成第一标识。n为大于或等于2的整数。具体的，第一生成规则为：将NWDAF网元的前两级域名作为DC，并将NWDAF网元的第三级域名至前n级域名中的各级域名分别作为第一标识中的各个RDN名称的取值。其中，n的取值可以由OAM系统确定，或者可以由协议约定，本申请实施例对此不做限定。
示例性的，若NWDAF网元的域名为“nwdaf.5gc.mnc001.mcc460.3gppnetwork.org”，且n＝4。则将NWDAF网元的前两级域名“3gppnetwork.org”作为DC，得到“DC＝3gppnetwork.org”；将NWDAF网元的第三级域名(即“mcc460”)至前4级域名(即“mnc001”)中的各级域名分别作为第一标识中的各个RDN名称的取值，得到“MCC＝460，MNC＝001”。因此，根据第一 生成规则生成的第一标识为“DC＝3gppnetwork.org，MCC＝460，MNC＝001”。
示例性的，若OAM系统创建网络切片和网络切片子网后，OAM系统向NWDAF网元配置了S-NSSAI 567，NSI ID abc，那么NWDAF网元根据第二生成规则和前一示例中的第一生成规则，可以生成：
网络切片的DN：“DC＝3gppnetwork.org，MCC＝460，MNC＝001，networkslice＝567”。
接入网切片子网的DN：“DC＝3gppnetwork.org，MCC＝460，MNC＝001，networkslice＝567，networkslicesubnet＝RAN-567”。
核心网切片子网的DN：“DC＝3gppnetwork.org，MCC＝460，MNC＝001，networkslice＝567，networkslicesubnet＝CN-abc”。
可选的，前述第一标识具体可以包括第一标识1和第一标识2；前述第一生成规则包括第一生成规则1和第一生成规则2；其中，第一生成规则1可包括根据NWDAF网元的域名生成该第一标识1的规则，具体参见前文中关于第一生成规则和第一标识的描述。第一生成规则2可包括根据NWDAF网元的主机名生成该第一标识2的规则。可以理解的是，NWDAF网元可以根据该第一生成规则1以及该NWDAF网元的域名，生成该第一标识1；并根据该第一生成规则2以及该NWDAF网元的主机名，生成该第一标识2；并根据该第二生成规则以及该数据源的标识，生成该第二标识。
其中，第一标识1可以包括DC和RDN集合中的前一个或多个相邻RDN，第一标识2可以包括RDN集合中与该第一标识1中的RDN相邻的一个或多个RDN，前述第二标识可以为RDN集合中与该第一标识2相邻的一个或多个RDN。数据源在OAM系统中的对象标识的构成示意图可参见图4b所示。图4b中，以第一标识1包括1个RDN，第一标识2包括3个RDN，且第二标识包括2个RDN为例。
主机名包括用“.”分开的一段或多段字符。可选的，第一生成规则2可以为：将NWDAF网元的主机名中用“.”分开的每一段字符串部分中的字母部分作为RDN名称，每一段字符串中的数字部分作为RDN的取值。
示例性的，若NWDAF网元的主机名为“nwdaf1.managedElement1”，则根据该主机名生成的第一标识2可以为“managedElement＝1,NWDAFID＝1”。其中，managedElement可以为用于管理该NWDAF网元的物理设备。在其他实现方式中，可以不存在该managedElement。可选的，是否存在用于管理该NWDAF网元的物理设备managedElement可以取决于运营商的部署。需要说明的是，上述主机名包括具体的网元(如NWDAF网元)是用于举例。在其他可行的实现方式中，主机名还可以包括网元的接口或配置数据。
前述NWDAF网元的域名可以为全限定域名(fully qualified domain name，FQDN)。FQDN同时带有主机名和域名，且通过符号“.”连接的名称。例如：主机名是bigserver，域名是mycompany.com，那么FQDN就是bigserver.mycompany.com。
步骤S404：NWDAF网元向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
步骤S405：OAM系统根据该对象标识，获取该待获取数据。
步骤S406：OAM系统向NWDAF网元发送该待获取数据。
需要说明的是，步骤S504～步骤S506的执行过程可参见图2中步骤S204～步骤S206的具体描述，此处不再赘述。
在本申请实施例中，NWDAF网元根据数据源的标识以及数据源在OAM系统中的对象标识的生成规则即可生成数据源在OAM系统中的对象标识，在这种方式下，NWDAF网元 无需获取OAM系统的整个被管理对象数据库，从而有利于简化NWDAF网元从OAM系统获取数据的过程。其次，NWDAF网元不获取OAM系统的整个被管理对象数据库，使得NWDAF网元不具有查看所有网络管理数据的权限，从而有利于确保网元安全。另外，在数据源为网络切片或网络切片子网的情况下，即使新增了网络切片或网络切片子网，根据历史获取的生成规则也可以生成(新增的)网络切片或网络切片子网在OAM系统中的对象标识。
请参见图5，图5是本申请实施例提供的又一种数据获取方法的流程示意图，在该实施例中数据源为网元、网元的接口或网元的配置数据，该方法详细描述了NWDAF网元如何根据数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识。该方法可以包括但不限于如下步骤：
步骤S501：NWDAF网元确定待获取数据所归属的数据源。
需要说明的是，步骤S501的执行过程可参见图2中步骤S201的具体描述，此处不再赘述。
步骤S502a：NWDAF网元获取该数据源的域名。
在一种实现方式中，NWDAF网元可通过如下方式获取数据源的域名：
NWDAF网元向NRF网元发送第三请求，该第三请求用于请求获取该数据源的域名；NWDAF网元从该NRF网元接收该数据源的域名。或者，若该数据源为NWDAF网元，那么该NWDAF网元可以从该NWDAF网元的存储器中获取该NWDAF网元的域名。
需要说明的是，如果根据网络管理的权限控制和安全需求，不希望NWDAF网元获得某个网元的数据时，OAM系统在配置该网元时，可以只提供IP地址，不提供域名。这样，该网元注册到NRF网元中的信息将不包括其域名，NWDAF网元也就无法从NRF网元获得该网元的域名，进一步的，也就无法获取该网元在OAM系统中的对象标识，无法调用OAM系统提供的管理服务接口获得该网元的数据，从而达到网络安全和权限控制的目的。
步骤S502b：NWDAF网元获取第一信息，第一信息包括该数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则。
NWDAF网元获取第一信息的方式可参见图2中步骤S202中的具体描述，此处不再赘述。
映射规则可以为：将数据源的前m级域名映射为该数据源在OAM系统中的对象标识。其中，数据源在OAM系统中的对象标识可包括DC+RDN集合，RDN集合包括一个或多个RDN。具体的，映射规则可以为：从数据源的前两级域名映射得到DC，并从该数据源的第三级域名至前m级域名中的各级域名分别映射得到该数据源在OAM系统中的对象标识中的各个RDN名称的取值。其中，m的取值可以由OAM系统确定，或者可以由协议约定，本申请实施例对此不做限定。
示例性的，若该数据源为SMF网元，且该SMF网元的域名为“smf.5gc.mnc001.mcc460.3gppnetwork.org”，且m＝4。则从SMF网元的前两级域名“3gppnetwork.org”可映射得到“DC＝3gppnetwork.org”；从SMF网元的第三级域名(即“mcc460”)映射得到“MCC＝460”，从SMF网元的第4级域名(即“mnc001”)映射得到“MNC＝001”。因此，根据该映射规则映射得到的对象标识为“DC＝3gppnetwork.org，MCC＝460，MNC＝001”。
或者，映射规则具体可以为：将域名“south.subNetwork.operatorA.com”映射为DC＝operatorA.com,subNetwork＝south。其中，subNetwork为RDN的名称。
需要说明的是，本申请实施例对步骤S502a和步骤S502b的执行顺序不做限定，可以先 执行步骤S502a或者步骤S502b，或者，可以同时执行步骤S502a和步骤S502b。
步骤S503：NWDAF网元根据该映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识。
在一种实现方式中，数据源在OAM系统中的对象标识可包括第三标识和第四标识；前述第一信息具体可包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则。第一映射规则具体参见前文中关于映射规则的描述。可以理解的是，NWDAF网元可以获取数据源的主机名；根据该第一映射规则从该数据源的域名映射得到该第三标识；并根据该第二映射规则，从该数据源的主机名映射得到该第四标识。
其中，数据源在OAM系统中的对象标识可包括DC+RDN集合，RDN集合包括一个或多个RDN。第三标识可以包括DC和RDN集合中的前一个或多个相邻RDN，第四标识可以包括RDN集合中的后一个或多个相邻RDN，第三标识和第四标识组成了DC+RDN集合。也就是说，第三标识在DN中的位置相较于第四标识在DN中的位置更靠前。
主机名包括用“.”分开的一段或多段字符。可选的，第一生成规则2可以为：将数据源的主机名中用“.”分开的每一段字符串部分中的字母部分作为RDN名称，每一段字符串中的数字部分作为RDN的取值。前述数据源的域名可以为全限定域名(fully qualified domain name，FQDN)。FQDN同时带有主机名和域名。
示例性的，若数据源为SMF网元，该SMF网元的FQDN为“smf1.managedElement1.south.subNetwork.operatorA.com”，且m＝4。则根据第一映射规则映射得到的该SMF网元在OAM系统中的第三标识可以为“DC＝operatorA.com,subNetwork＝south”。根据第二映射规则映射得到的该SMF网元在OAM系统中的第四标识可以为“managedElement＝1,SMF＝1”。其中，managedElement可以为用于管理该SMF网元的物理设备。在其他实现方式中，可以不存在该managedElement。可选的，是否存在用于管理该SMF网元的物理设备managedElement可以取决于运营商的部署。需要说明的是，上述主机名包括具体的网元(如SMF网元)是用于举例。在其他可行的实现方式中，主机名还可以包括网元的接口或配置数据。例如，主机名包括SMF1与某UPF之间的N4接口1(N4Inf1.smf1.managedElement1)。或者，主机名包括SMF1上预先配置的5QI集合1(5QIset1.smf1.managedElement1)，其中5QI集合1包括两个预先配置的5QI，其中一个5QI＝1，另一个5QI＝5。
步骤S504：NWDAF网元向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
步骤S505：OAM系统根据该对象标识，获取该待获取数据。
步骤S506：OAM系统向NWDAF网元发送该待获取数据。
需要说明的是，步骤S504～步骤S506的执行过程可参见图2中步骤S204～步骤S206的具体描述，此处不再赘述。
在一种实现方式中，若待获取数据为SMF网元配置的5QI集合，NWDAF网元在获取该5QI集合后，进一步的，还可以从OAM系统中获取5QI对应的性能统计指标，比如每个5QI的QoS流的数量等。
NWDAF网元可以从OAM系统中获取包括接入网网元在内的各个NF的配置数据，比如gNB配置的小区列表，SMF配置的服务区，NSSF配置的S-NSSAI列表和NSI ID列表，UPF的容量、部署位置等信息。NWDAF网元可以将从OAM系统所获取的数据作为进行数据分析时的输入数据。
需要说明的是，若NWDAF网元获取数据源在OAM系统中的MOI的DN，可表示该NWDAF网元获取了该MOI在OAM系统中所属的树状结构中以该MOI为顶点的所有子MOI的DN。例如，在图1b中，若NWDAF网元获取了无线设备a(一MOI)在OAM中的DN，则表示该NWDAF网元获取了无线设备a、eNB1、gNB1、小区1和小区2这些MOI在OAM中的DN。
在本申请实施例中，NWDAF网元根据数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则，即可从该数据源的域名映射得到该数据源在OAM系统中的对象标识，在这种方式下，NWDAF网元无需获取OAM系统的整个被管理对象数据库，从而有利于简化NWDAF网元从OAM系统获取数据的过程。其次，NWDAF网元不获取OAM系统的整个被管理对象数据库，使得NWDAF网元不具有查看所有网络管理数据的权限，从而有利于确保网元安全。
相应于上述方法实施例给出的方法，本申请实施例还提供了相应的装置，包括用于执行上述实施例相应的模块。所述模块可以是软件，也可以是硬件，或者是软件和硬件结合。
请参见图6，为本申请提供的一种通信装置的结构示意图。图6所示的通信装置600包括处理单元601和通信单元602。
在一种设计中，装置600为网络数据分析网元：
示例性的，处理单元601，用于确定待获取数据所归属的数据源；获取第一信息，并根据该第一信息确定该数据源在运行管理和维护OAM系统中的对象标识；通信单元602，用于向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括该数据源在OAM系统中的对象标识的生成规则；处理单元601用于根据第一信息，确定该数据源在OAM系统中的对象标识时，具体用于：根据该生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识。
在一种实现方式中，前述对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则；处理单元601用于根据生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识时，具体用于：根据该第一生成规则以及该网络数据分析网元的域名，生成该第一标识；并根据该第二生成规则以及该数据源的标识，生成该第二标识。
在一种实现方式中，数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理 对象标识。
在一种实现方式中，通信单元602，还用于接收第二请求，该第二请求用于请求进行数据分析；通信单元602，还用于从OAM系统接收前述待获取数据；处理单元601，还用于根据该待获取数据进行数据分析，得到分析结果；处理单元601用于确定待获取数据所归属的数据源时，具体用于：根据该第二请求确定待获取数据所归属的数据源。
在一种实现方式中，该第二请求包括该数据源的标识。
在一种实现方式中，第一信息包括该数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则；处理单元601，还用于获取该数据源的该域名；处理单元601用于根据第一信息，确定该数据源在OAM系统中的对象标识时，具体用于：根据该映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则；处理单元601，还用于获取该数据源的所述主机名；处理单元601用于根据映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识时，具体用于：根据该第一映射规则，从该数据源的域名映射得到该第三标识；并根据该第二映射规则，从该数据源的主机名映射得到该第四标识。
在一种实现方式中，处理单元601用于获取数据源的域名时，具体用于：调用通信单元602向网络仓库功能NRF网元发送第三请求，该第三请求用于请求获取该数据源的域名；并调用通信单元602从该NRF网元接收该数据源的域名。
在一种实现方式中，处理单元601用于获取第一信息时，具体用于以下任一项：从OAM系统或者NRF网元获取该第一信息；从OAM系统或NRF网元获取网元配置文件，该网元配置文件包括第一信息；从该通信装置600的存储器中获取该第一信息。
在一种实现方式中，该网元配置文件为该通信装置600的配置文件或网络切片选择网元的配置文件。
装置600为网络数据分析网元时，用于实现图2～图5所示实施例中网络数据分析网元的功能。
在一种设计中，装置600为OAM系统中的管理设备：示例性的，处理单元601，用于产生第一信息，该第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识；通信单元602，用于向第一网元发送该第一信息。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：
该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括数据源在OAM系统中的对象标识的生成规则。
在一种实现方式中，该对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则，其中，第一生成规则包括根据网络数据分析网元的域名生成该第一标识的规则，该第二生成规则包括根据该数据源的标识生成该第二标识的规则。
在一种实现方式中，该数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
在一种实现方式中，第一信息包括数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则。
在一种实现方式中，通信单元602用于向第一网元发送第一信息时，具体用于：向第一网元发送配置命令，该配置命令中包括该第一信息；或者，向该第一网元发送网元配置文件，该网元配置文件包括该第一信息。
在一种实现方式中，网元配置文件为网络数据分析网元或网络切片选择网元的配置文件。
在一种实现方式中，该第一网元包括以下一项或多项：网络切片选择网元、网络仓库功能NRF网元或网络数据分析网元。
装置600为OAM系统中的管理设备时，用于实现图2～图5所示实施例中管理设备的功能。
请参见图7，为本申请提供的另一种通信装置的结构示意图。图7所示的通信装置700包括至少一个处理器701、存储器702、收发器703。
存储器702可以是易失性存储器，例如随机存取存储器；存储器也可以是非易失性存储器，例如只读存储器，快闪存储器，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)、或者存储器702是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器702可以是上述存储器的组合。
本申请实施例中不限定上述处理器701、存储器702以及收发器703之间的具体连接介质。本申请实施例在图中以收发器703、存储器702、处理器701之间通过总线704连接，总线704在图中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。该总线704可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器701可以具有数据收发功能，能够与其他设备进行通信，在如图7装置中，也可以设置独立的数据通信单元，例如收发器703，用于收发数据；处理器701在与其他设备进行通信时，可以通过收发器703进行数据传输。
需要说明的是，图7中虚线框表示收发器703可以与处理器701单独设置，或者，收发器703也可以集成在处理器701中；存储器702可以与处理器701单独设置，或者，存储器702也可以集成在处理器701中。
一种示例中，当网络数据分析网元采用图7所示的形式时，图7中的处理器可以通过调用存储器702中存储的计算机执行指令，使得网络数据分析网元执行上述任一方法实施例中的网络数据分析网元执行的方法。
一种示例中，当OAM中的管理设备采用图7所示的形式时，图7中的处理器可以通过调用存储器702中存储的计算机执行指令，使得管理设备执行上述任一方法实施例中的管理设备执行的方法。
具体的，图6的处理单元和通信单元的功能/实现过程均可以通过图7中的处理器701调用存储器702中存储的计算机执行指令来实现。或者，图6的处理单元的功能/实现过程可以通过图7中的处理器701调用存储器702中存储的计算机执行指令来实现，图6的通信单元的功能/实现过程可以通过图7中的收发器703来实现。
在一种实现方式中，通信装置700可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器可用如下方式实现：集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等。该处理器也可以用如下IC工艺技术来制造：例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络数据分析网元或OAM系统中的管理设备。但本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图7的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端、智能终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图8所示的芯片的结构示意图。图8所示的芯片包括接口801和处理器802。其中，接口801的数量可以是一个或多个，处理器802的数量可以是多个。
对于芯片用于实现本申请实施例中网络数据分析网元的功能的情况：
处理器802，用于确定待获取数据所归属的数据源；获取第一信息，并根据该第一信息确定该数据源在运行管理和维护OAM系统中的对象标识；接口801，用于向OAM系统发送第一请求，该第一请求包括该对象标识，该第一请求用于请求获取该待获取数据。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该 网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括该数据源在OAM系统中的对象标识的生成规则；处理器802用于根据第一信息，确定该数据源在OAM系统中的对象标识时，具体用于：根据该生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识。
在一种实现方式中，前述对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则；处理器802用于根据生成规则以及该数据源的标识，生成该数据源在OAM系统中的对象标识时，具体用于：根据该第一生成规则以及该网络数据分析网元的域名，生成该第一标识；并根据该第二生成规则以及该数据源的标识，生成该第二标识。
在一种实现方式中，数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
在一种实现方式中，接口801，还用于接收第二请求，该第二请求用于请求进行数据分析；接口801，还用于从OAM系统接收前述待获取数据；处理器802，还用于根据该待获取数据进行数据分析，得到分析结果；处理器802用于确定待获取数据所归属的数据源时，具体用于：根据该第二请求确定待获取数据所归属的数据源。
在一种实现方式中，该第二请求包括该数据源的标识。
在一种实现方式中，第一信息包括该数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则；处理器802，还用于获取该数据源的该域名；处理器802用于根据第一信息，确定该数据源在OAM系统中的对象标识时，具体用于：根据该映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则；处理器802，还用于获取该数据源的所述主机名；处理器802用于根据映射规则，从该数据源的域名映射得到该数据源在OAM系统中的对象标识时，具体用于：根据该第一映射规则，从该数据源的域名映射得到该第三标识；并根据该第二映射规则，从该数据源的主机名映射得到该第四标识。
在一种实现方式中，处理器802用于获取数据源的域名时，具体用于：调用接口801向网络仓库功能NRF网元发送第三请求，该第三请求用于请求获取该数据源的域名；并调用接口801从该NRF网元接收该数据源的域名。
在一种实现方式中，处理器802用于获取第一信息时，具体用于以下任一项：从OAM系统或者NRF网元获取该第一信息；从OAM系统或NRF网元获取网元配置文件，该网元配置文件包括第一信息；从前述通信装置的存储器中获取该第一信息。
在一种实现方式中，该网元配置文件为该通信装置的配置文件或网络切片选择网元的配置文件。
具体的，在这种情况中，接口801和处理器802所执行的操作可以参照上述图2～图5所对应的实施例中有关网络数据分析网元的介绍。
对于芯片用于实现本申请实施例中OAM系统中的管理设备的功能的情况：
处理器802，用于产生第一信息，该第一信息用于确定待获取数据所归属的数据源在OAM系统中的对象标识；接口801，用于向第一网元发送该第一信息。
在一种实现方式中，第一信息包括该数据源的标识与该数据源在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，该数据源包括网络切片或网络切片子网。
在一种实现方式中，第一信息包括于网元配置文件中，该网元配置文件包括以下一项或多项：该网络切片的标识与该网络切片在OAM系统中的对象标识之间的对应关系；该网络切片的标识与该网络切片中的网络切片子网在OAM系统中的对象标识之间的对应关系；该网络切片中的网络切片子网的标识与该网络切片在OAM系统中的对象标识之间的对应关系；或者，该网络切片中的网络切片子网的标识与该网络切片子网在OAM系统中的对象标识之间的对应关系。
在一种实现方式中，前述待获取数据为该网络切片的关键性能指标KPI，或该网络切片子网的KPI。
在一种实现方式中，第一信息包括数据源在OAM系统中的对象标识的生成规则。
在一种实现方式中，该对象标识包括第一标识和第二标识；该生成规则包括第一生成规则和第二生成规则，其中，第一生成规则包括根据网络数据分析网元的域名生成该第一标识的规则，该第二生成规则包括根据该数据源的标识生成该第二标识的规则。
在一种实现方式中，该数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；该数据源在OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
在一种实现方式中，第一信息包括数据源的域名与该数据源在OAM系统中的对象标识之间的映射规则。
在一种实现方式中，该对象标识包括第三标识和第四标识；第一信息具体包括该数据源的域名与该第三标识之间的第一映射规则，以及该数据源的主机名与该第四标识之间的第二映射规则。
在一种实现方式中，接口801用于向第一网元发送第一信息时，具体用于：向第一网元发送配置命令，该配置命令中包括该第一信息；或者，向该第一网元发送网元配置文件，该网元配置文件包括该第一信息。
在一种实现方式中，网元配置文件为网络数据分析网元或网络切片选择网元的配置文件。
在一种实现方式中，该第一网元包括以下一项或多项：网络切片选择网元、网络仓库功能NRF网元或网络数据分析网元。
具体的，在这种情况中，接口801和处理器802所执行的操作可以参照上述图2～图5所对应的实施例中有关管理设备的介绍。
可选的，芯片还包括存储器803，存储器803用于存储必要的计算机程序和数据。存储器803可以单独设置，也可以与处理器802集成在一起，如图8中虚框所示。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请实施例还提供一种数据获取系统，该系统可以包括图2～图5对应实施例中的网络 数据分析网元和OAM系统中的管理设备中的一个或多个。可选的，还包括图2～图5对应实施例中的网络切片选择网元和/或网络仓库功能NRF网元。
本申请还提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序包括程序指令，该程序指令被计算机执行时实现上述任一方法实施例的功能。
上述计算机可读存储介质包括但不限于快闪存储器、硬盘、固态硬盘。
本申请还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
可以理解的是，本申请实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，比如其当前所基于的方案，而独立实施，解决相应的技术问题，达到相应的效果，也可以在某些场景下，依据需求与其他特征进行结合。相应的，本申请实施例中给出的装置也可以相应的实现这些特征或功能，在此不予赘述。
本领域技术人员还可以理解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员对于相应的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请所描述的方案可通过各种方式来实现。例如，这些技术可以用硬件、软件或者硬件结合的方式来实现。对于硬件实现，用于在通信装置(例如，基站，终端、网络实体、核心网网元或芯片)处执行这些技术的处理单元，可以实现在一个或多个通用处理器、数字信号处理器(digital signal processor，DSP)、数字信号处理器件、专用集成电路(application specific integrated circuit，ASIC)、可编程逻辑器件、现场可编程门阵列(field programmable gate array，FPGA)、或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合中。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按 照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state drive，SSD))等。
可以理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
可以理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下装置会做出相应的处理，并非是限定时间，且也不要求装置实现时一定要有判断的动作，也不意味着存在其它限定。
本申请中对于使用单数表示的元素旨在用于表示“一个或多个”，而并非表示“一个且仅一个”，除非有特别说明。本申请中，在没有特别说明的情况下，“至少一个”旨在用于表示“一个或者多个”，“多个”旨在用于表示“两个或两个以上”。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A可以是单数或者复数，B可以是单数或者复数。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以理解，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本申请中各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中，如果没有特殊说明以及逻辑冲突，不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以上所述的本申请实施方式并不构成对本申请保护范围的限定。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。

Claims (33)

  1. 一种数据获取方法，其特征在于，所述方法包括：
    网络数据分析网元确定待获取数据所归属的数据源；
    所述网络数据分析网元获取第一信息；
    所述网络数据分析网元根据所述第一信息，确定所述数据源在运行管理和维护OAM系统中的对象标识；
    所述网络数据分析网元向所述OAM系统发送第一请求，所述第一请求包括所述对象标识，所述第一请求用于请求获取所述待获取数据。
  2. 如权利要求1所述的方法，其特征在于，所述第一信息包括所述数据源的标识与所述数据源在所述OAM系统中的对象标识之间的对应关系。
  3. 如权利要求2所述的方法，其特征在于，所述数据源包括网络切片或网络切片子网。
  4. 如权利要求3所述的方法，其特征在于，所述第一信息包括于网元配置文件中，所述网元配置文件包括以下一项或多项：
    所述网络切片的标识与所述网络切片在所述OAM系统中的对象标识之间的对应关系；
    所述网络切片的标识与所述网络切片中的所述网络切片子网在所述OAM系统中的对象标识之间的对应关系；
    所述网络切片中的所述网络切片子网的标识与所述网络切片在所述OAM系统中的对象标识之间的对应关系；或者，
    所述网络切片中的所述网络切片子网的标识与所述网络切片子网在所述OAM系统中的对象标识之间的对应关系。
  5. 如权利要求3或4所述的方法，其特征在于，所述待获取数据为所述网络切片的关键性能指标KPI，或所述网络切片子网的KPI。
  6. 如权利要求1所述的方法，其特征在于，所述第一信息包括所述数据源在所述OAM系统中的对象标识的生成规则；所述网络数据分析网元根据所述第一信息，确定所述数据源在所述OAM系统中的对象标识，包括：
    所述网络数据分析网元根据所述生成规则以及所述数据源的标识，生成所述数据源在所述OAM系统中的对象标识。
  7. 如权利要求6所述的方法，其特征在于，所述对象标识包括第一标识和第二标识；所述生成规则包括第一生成规则和第二生成规则；
    所述网络数据分析网元根据所述生成规则以及所述数据源的标识，生成所述数据源在所述OAM系统中的对象标识，包括：
    所述网络数据分析网元根据所述第一生成规则以及所述网络数据分析网元的域名，生成所述第一标识；并根据所述第二生成规则以及所述数据源的标识，生成所述第二标识。
  8. 如权利要求1～7任一项所述的方法，其特征在于，所述数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；所述数据源在所述OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
  9. 如权利要求1～8任一项所述的方法，其特征在于，所述方法还包括：
    所述网络数据分析网元接收第二请求，所述第二请求用于请求进行数据分析；
    所述网络数据分析网元从所述OAM系统接收所述待获取数据；
    所述网络数据分析网元根据所述待获取数据进行数据分析，得到分析结果；
    所述网络数据分析网元确定待获取数据所归属的数据源，包括：
    所述网络数据分析网元根据所述第二请求确定待获取数据所归属的数据源。
  10. 如权利要求9所述的方法，其特征在于，所述第二请求包括所述数据源的标识。
  11. 如权利要求1所述的方法，其特征在于，所述第一信息包括所述数据源的域名与所述数据源在所述OAM系统中的所述对象标识之间的映射规则；
    所述方法还包括：
    所述网络数据分析网元获取所述数据源的所述域名；
    所述网络数据分析网元根据所述第一信息，确定所述数据源在所述OAM系统中的对象标识，包括：
    所述网络数据分析网元根据所述映射规则，从所述数据源的域名映射得到所述数据源在所述OAM系统中的对象标识。
  12. 如权利要求11所述的方法，其特征在于，所述对象标识包括第三标识和第四标识；所述第一信息具体包括所述数据源的域名与所述第三标识之间的第一映射规则，以及所述数据源的主机名与所述第四标识之间的第二映射规则；
    所述方法还包括：
    所述网络数据分析网元获取所述数据源的所述主机名；
    所述网络数据分析网元根据所述映射规则，从所述数据源的域名映射得到所述数据源在所述OAM系统中的对象标识，包括：
    所述网络数据分析网元根据所述第一映射规则，从所述数据源的域名映射得到所述第三标识；并根据所述第二映射规则，从所述数据源的主机名映射得到所述第四标识。
  13. 如权利要求11或12所述的方法，其特征在于，所述网络数据分析网元获取所述数据源的域名，包括：
    所述网络数据分析网元向网络仓库功能NRF网元发送第三请求，所述第三请求用于请求获取所述数据源的域名；
    所述网络数据分析网元从所述NRF网元接收所述数据源的域名。
  14. 如权利要求1～13中任一项所述的方法，其特征在于，所述网络数据分析网元获取第一信息，包括以下任一项：
    所述网络数据分析网元从所述OAM系统或者NRF网元获取所述第一信息；
    所述网络数据分析网元从所述OAM系统或NRF网元获取网元配置文件，所述网元配置文件包括所述第一信息；
    所述网络数据分析网元从所述网络数据分析网元的存储器中获取所述第一信息。
  15. 如权利要求14所述的方法，其特征在于，所述网元配置文件为所述网络数据分析网元或网络切片选择网元的配置文件。
  16. 一种数据获取方法，其特征在于，应用于运行管理和维护OAM系统，所述系统包括管理设备；所述方法包括：
    所述管理设备产生第一信息；所述第一信息用于确定待获取数据所归属的数据源在所述OAM系统中的对象标识；
    所述管理设备向第一网元发送所述第一信息。
  17. 如权利要求16所述的方法，其特征在于，所述第一信息包括所述数据源的标识与所述 数据源在所述OAM系统中的对象标识之间的对应关系。
  18. 如权利要求17所述的方法，其特征在于，所述数据源包括网络切片或网络切片子网。
  19. 如权利要求18所述的方法，所述第一信息包括于网元配置文件中，所述网元配置文件包括以下一项或多项：
    所述网络切片的标识与所述网络切片在所述OAM系统中的对象标识之间的对应关系；
    所述网络切片的标识与所述网络切片中的所述网络切片子网在所述OAM系统中的对象标识之间的对应关系；
    所述网络切片中的所述网络切片子网的标识与所述网络切片在所述OAM系统中的对象标识之间的对应关系；或者，
    所述网络切片中的所述网络切片子网的标识与所述网络切片子网在所述OAM系统中的对象标识之间的对应关系。
  20. 如权利要求18或19所述的方法，其特征在于，所述待获取数据为所述网络切片的关键性能指标KPI，或所述网络切片子网的KPI。
  21. 如权利要求16所述的方法，其特征在于，所述第一信息包括所述数据源在所述OAM系统中的对象标识的生成规则。
  22. 如权利要求21所述的方法，其特征在于，所述对象标识包括第一标识和第二标识；所述生成规则包括第一生成规则和第二生成规则，其中，所述第一生成规则包括根据网络数据分析网元的域名生成所述第一标识的规则，所述第二生成规则包括根据所述数据源的标识生成所述第二标识的规则。
  23. 如权利要求16～22中任一项所述的方法，其特征在于，所述数据源的标识包括网络切片选择辅助信息和/或网络切片子网标识；所述数据源在所述OAM系统中的对象标识包括网络切片被管理对象标识和/或网络切片子网被管理对象标识。
  24. 如权利要求16所述的方法，其特征在于，所述第一信息包括所述数据源的域名与所述数据源在所述OAM系统中的对象标识之间的映射规则。
  25. 如权利要求24所述的方法，其特征在于，所述对象标识包括第三标识和第四标识；所述第一信息具体包括所述数据源的域名与所述第三标识之间的第一映射规则，以及所述数据源的主机名与所述第四标识之间的第二映射规则。
  26. 如权利要求16～25任一项所述的方法，其特征在于，所述管理设备向第一网元发送所述第一信息，包括：
    所述管理设备向第一网元发送配置命令，所述配置命令中包括所述第一信息；或者，
    所述管理设备向所述第一网元发送网元配置文件，所述网元配置文件包括所述第一信息。
  27. 如权利要求26所述的方法，其特征在于，所述网元配置文件为网络数据分析网元或网络切片选择网元的配置文件。
  28. 如权利要求16～27任一项所述的方法，其特征在于，所述第一网元包括以下一项或多项：网络切片选择网元、网络仓库功能NRF网元或网络数据分析网元。
  29. 一种数据获取系统，其特征在于，所述系统包括如权利要求1～15任一项所述的网络数据分析网元，和如权利要求16～28任一项所述的管理设备。
  30. 一种通信装置，其特征在于，包括用于执行如权利要求1～15或16～28中任一项所述的方法的单元。
  31. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有 程序指令，所述处理器执行所述存储器中存储的程序指令，以使所述装置执行如权利要求1～15或16～28中任一项所述的方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令被通信装置执行时，使得如权利要求1～15或16～28中任一项所述的方法被执行。
  33. 一种计算机程序产品，其特征在于，所述计算机程序产品包括程序指令，所述程序指令被通信装置执行时，使得如权利要求1～15或16～28中任一项所述的方法被执行。
PCT/CN2022/088689 2021-05-06 2022-04-24 一种数据获取方法、系统及其装置 WO2022233244A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2023568156A JP2024519311A (ja) 2021-05-06 2022-04-24 データ入手方法およびシステム、ならびにその装置
EP22798585.0A EP4325925A1 (en) 2021-05-06 2022-04-24 Data acquisition method and system, and apparatus thereof
US18/500,491 US20240064069A1 (en) 2021-05-06 2023-11-02 Data obtaining method and system, and apparatus thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110494318.X 2021-05-06
CN202110494318.XA CN115396275B (zh) 2021-05-06 2021-05-06 一种数据获取方法、系统及其装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/500,491 Continuation US20240064069A1 (en) 2021-05-06 2023-11-02 Data obtaining method and system, and apparatus thereof

Publications (1)

Publication Number Publication Date
WO2022233244A1 true WO2022233244A1 (zh) 2022-11-10

Family

ID=83931989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/088689 WO2022233244A1 (zh) 2021-05-06 2022-04-24 一种数据获取方法、系统及其装置

Country Status (5)

Country Link
US (1) US20240064069A1 (zh)
EP (1) EP4325925A1 (zh)
JP (1) JP2024519311A (zh)
CN (1) CN115396275B (zh)
WO (1) WO2022233244A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117690093A (zh) * 2024-01-31 2024-03-12 华能澜沧江水电股份有限公司 大坝安全监测运行维护方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1677935A (zh) * 2004-03-31 2005-10-05 华为技术有限公司 电信管理网中配置信息模型树的转换系统及其方法
US20150227604A1 (en) * 2012-09-20 2015-08-13 Zte Corporation Data updating method, system and device
WO2020062097A1 (en) * 2018-09-28 2020-04-02 Nokia Shanghai Bell Co., Ltd. Managed object instance identification for object management
US20200145833A1 (en) * 2017-05-08 2020-05-07 Ntt Docomo, Inc. Method for associating network functions with a network slice instance of a mobile radio communication network
CN111836291A (zh) * 2019-04-18 2020-10-27 中国移动通信有限公司研究院 一种切片资源调度方法及网元
US20210105638A1 (en) * 2018-02-16 2021-04-08 NEC Laboratories Europe GmbH Network data analytics for oam

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104040539B (zh) * 2012-12-31 2017-06-06 华为技术有限公司 数据存储方法和装置、数据操作方法、系统及接入服务器
CN112350841B (zh) * 2019-08-08 2022-05-17 华为技术有限公司 一种管理数据的获取方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1677935A (zh) * 2004-03-31 2005-10-05 华为技术有限公司 电信管理网中配置信息模型树的转换系统及其方法
US20150227604A1 (en) * 2012-09-20 2015-08-13 Zte Corporation Data updating method, system and device
US20200145833A1 (en) * 2017-05-08 2020-05-07 Ntt Docomo, Inc. Method for associating network functions with a network slice instance of a mobile radio communication network
US20210105638A1 (en) * 2018-02-16 2021-04-08 NEC Laboratories Europe GmbH Network data analytics for oam
WO2020062097A1 (en) * 2018-09-28 2020-04-02 Nokia Shanghai Bell Co., Ltd. Managed object instance identification for object management
CN111836291A (zh) * 2019-04-18 2020-10-27 中国移动通信有限公司研究院 一种切片资源调度方法及网元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "TD enhance 5GC NRM to support plug and play of 5GC NF", 3GPP DRAFT; S5-213373, vol. SA WG5, 30 April 2021 (2021-04-30), pages 1 - 2, XP051999038 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117690093A (zh) * 2024-01-31 2024-03-12 华能澜沧江水电股份有限公司 大坝安全监测运行维护方法、装置、电子设备及存储介质
CN117690093B (zh) * 2024-01-31 2024-04-26 华能澜沧江水电股份有限公司 大坝安全监测运行维护方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN115396275A (zh) 2022-11-25
US20240064069A1 (en) 2024-02-22
EP4325925A1 (en) 2024-02-21
JP2024519311A (ja) 2024-05-10
CN115396275B (zh) 2023-12-29

Similar Documents

Publication Publication Date Title
CN109379206B (zh) 网络功能信息的管理方法及相关设备
US11228947B2 (en) Network slice deployment method and related device
WO2020224463A1 (zh) 一种数据分析方法及装置
EP3675549A1 (en) Network slice management method, device and system
US11924641B2 (en) Security management for service access in a communication system
US11729137B2 (en) Method and device for edge application server discovery
EP3868134A1 (en) Methods and apparatus for selecting network resources for lie sessions based on locations of multi-access edge computing (mec) resources and applications
JP6122951B2 (ja) ネットワーク選択の動的制御
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
EP4240043A2 (en) Privacy managing entity selection in communication system
CN111050318B (zh) 终端信息的传递方法及相关产品
WO2020048469A1 (zh) 一种通信的方法及装置
US11057828B2 (en) Method for establishing a communication connection of a communication terminal via a communication network
US20240064069A1 (en) Data obtaining method and system, and apparatus thereof
WO2023011217A1 (zh) 一种通信方法及装置
WO2021138822A1 (zh) 签约信息获取方法及装置
US20220210702A1 (en) Communication Method and Apparatus
EP3720193A1 (en) Mobile communication network component and method for requesting a service
US20240048986A1 (en) Communication method and apparatus
WO2022242452A1 (zh) 通信方法、通信装置和计算机可读存储介质
WO2020253343A1 (zh) 一种管理服务的发现方法及装置
CN114885382A (zh) 一种业务会话管理方法、装置及存储介质
WO2020200297A1 (zh) 选择会话管理网元的方法和装置
CN114830606A (zh) 组播通信方法及其装置
WO2023213177A1 (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: 22798585

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023568156

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2022798585

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022798585

Country of ref document: EP

Effective date: 20231114

NENP Non-entry into the national phase

Ref country code: DE