WO2022262441A1 - 网元配置方法、业务配置方法、网元、存储介质 - Google Patents

网元配置方法、业务配置方法、网元、存储介质 Download PDF

Info

Publication number
WO2022262441A1
WO2022262441A1 PCT/CN2022/090045 CN2022090045W WO2022262441A1 WO 2022262441 A1 WO2022262441 A1 WO 2022262441A1 CN 2022090045 W CN2022090045 W CN 2022090045W WO 2022262441 A1 WO2022262441 A1 WO 2022262441A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
network element
service
object identifier
business
Prior art date
Application number
PCT/CN2022/090045
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 中兴通讯股份有限公司
Publication of WO2022262441A1 publication Critical patent/WO2022262441A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the embodiments of the present application relate to but are not limited to the communication field, and in particular relate to a network element configuration method, a service configuration method, a network element, and a storage medium.
  • 5GC Fifth Generation Communication
  • DNN Data Network Name
  • TAC Tracking Area Code
  • slices slices or DNNs may be managed by multiple enterprises. Sharing, it is difficult to manage and control for each enterprise.
  • DNN combined with integrated services digital network (Integrated Services Digital Network, ISDN) number segments can also be distinguished for enterprises, but the setting and mapping relationship maintenance need to be completed one by one through operation and maintenance, which increases the complexity of operation and maintenance, and low efficiency.
  • ISDN Integrated Services Digital Network
  • Embodiments of the present application provide a network element configuration method, a service configuration method, a network element, and a storage medium.
  • the embodiment of the present application provides a network element configuration method, which is applied to the Access and Mobility Management Function (Access and Mobility Management Function, AMF).
  • the network element configuration method includes: acquiring trigger information, according to the triggering information to initiate a business process; obtaining an object identifier, wherein the object identifier belongs to a business object of the business process; passing the object identifier to a target network element through information interaction for the business process, wherein the The target network element is located downstream of the AMF in the service process.
  • the embodiment of the present application provides a service configuration method, which is applied to a network element, and the network element is configured with an object identifier by applying the network element configuration method described in the first aspect, and the service configuration method includes: acquiring a service Create a request, where the service creation request includes a target object identifier and a target service; determine a target service object according to the target object identifier, and configure the target service for the target service object.
  • an embodiment of the present application provides a network element, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, when the processor executes the computer program, implements the following: The network element configuration method according to one aspect, or, when the processor executes the computer program, implements the service configuration method according to the second aspect.
  • FIG. 1 is a flowchart of a network element configuration method provided by an embodiment of the present application
  • FIG. 2 is a structural diagram of a network element management system provided by another embodiment of the present application.
  • Fig. 3 is a flow chart of acquiring subscription data provided by another embodiment of the present application.
  • Fig. 4 is a flow chart of obtaining a service policy provided by another embodiment of the present application.
  • Fig. 5 is a flow chart of transferring object identifiers provided by another embodiment of the present application.
  • FIG. 6 is a flow chart of transferring object identifiers one by one according to another embodiment of the present application.
  • FIG. 7 is a flow chart of retransmitting object identifiers provided by another embodiment of the present application.
  • Fig. 8 is a flow chart of Example 1 of the present application.
  • Fig. 9 is a flowchart of Example 2 of the present application.
  • Fig. 10 is a flow chart of Example 3 of the present application.
  • Fig. 11 is a flowchart of a service configuration method provided by another embodiment of the present application.
  • FIG. 12 is a structural diagram of a network element management system provided by another embodiment of the present application.
  • Fig. 13 is a flow chart of establishing an association relationship provided by another embodiment of the present application.
  • FIG. 14 is a flow chart of configuring target policies provided by another embodiment of the present application.
  • Fig. 15 is a flow chart of Example 4 of the present application.
  • Fig. 16 is a structural diagram of a network element provided by another embodiment of the present application.
  • the present application provides a network element configuration method, a service configuration method, a network element, and a storage medium.
  • the network element configuration method includes: acquiring trigger information, initiating a service process according to the trigger information; acquiring an object identifier, wherein the object identifying a service object belonging to the service process; passing the object identifier to a target network element through information interaction for the service process, wherein the target network element is located downstream of the AMF in the service process .
  • FIG. 1 is a network element configuration method provided by an embodiment of the present application, which is applied to AMF.
  • the network element configuration method includes but is not limited to step S110 , step S120 and step S130 .
  • Step S110 acquiring trigger information, and initiating a business process according to the trigger information.
  • the trigger information can be any request information that enables the AMF to initiate a business process, for example, a registration request sent by a terminal (User Equipment, UE) or a protocol data unit (Protocol Data Unit, PDU) session creation request, which can enable It is sufficient for the AMF to initiate the corresponding service process, and this embodiment does not involve the improvement of the way of initiating the service process, so details are not repeated here.
  • a terminal User Equipment, UE
  • PDU Protocol Data Unit
  • Step S120 obtaining an object ID, wherein the object ID belongs to a business object of a business process.
  • the trigger information can carry the object identifier, and the object identifier can also be obtained through the AMF according to the trigger information.
  • the trigger information is a registration request, and the UE only needs to send the device information, so that the AMF can use the unified data management function ( Unified Data Management (UDM) or Policy Control Function (Policy Control Functionality, PCF) contract data to match the corresponding object identifier;
  • UDM Unified Data Management
  • Policy Control Functionality, PCF Policy Control Functionality
  • AMF passes The registration process has obtained the object identifier, so the object identifier corresponding to the UE can be directly determined and subsequent operations can be performed; for another example, when the trigger information is a request to change the object identifier, the trigger information carries the object identifier, and AMF can obtain the object identifier from the trigger information. Obtain the object ID, so as to perform the subsequent de-registration process according to the object ID.
  • the object identification can be of any granularity.
  • the object identification can be for each enterprise.
  • the object identification can also use a coarser granularity for several companies with the same specific business characteristics. Enterprises and those skilled in the art have the motivation to adjust the granularity corresponding to the object identifier according to actual needs, so I won't go into details here.
  • object identifier may be in any form, for example, a numerical value or letter specified according to a certain standard, and the specific form of the object identifier is not limited too much in this embodiment.
  • step S130 the object identifier is transmitted to the target network element through information interaction for the service process, wherein the target network element is located downstream of the AMF in the service process.
  • AMF is the control plane entity of the core network and is used for user mobility management. Therefore, for most business processes, AMF is located upstream of the business process and can initiate various business processes. Therefore, the object identifier obtained through AMF , and the object identifier is added to the information interaction for the business process, so that the object identifier can be transmitted to each network element.
  • the type of the network element downstream of the AMF in the business process can be determined according to the specific business process.
  • the downstream network element of the AMF is the session management function (Session Management Function, SMF), Those skilled in the art are familiar with the network elements involved in various service processes, so details are not repeated here.
  • BOSS Business&Operation Support System
  • UDM User Plane Function
  • SMF User Plane Function
  • Charging Function CHF
  • BOSS sends it to UDM and PCF after obtaining the contract data
  • AMF obtains the object identifier from UDM through the registration process
  • AMF passes the object identifier to SMF through the creation of PDU session process
  • SMF further passes it to CHF and UPF according to the process , so as to realize the automatic transfer of object identifiers and reduce the complexity of operation and maintenance.
  • step S120 in the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S310 determining the object targeted by the registration request as a business object
  • Step S320 initiate the registration process, and obtain the object identifier corresponding to the business object from the contract data stored in the UDM, wherein the contract data is delivered to the UDM by the BOSS, and the contract data carries the object identifier.
  • the deployment of object identifiers in UDM can be realized by sending the contract data to UDM through BOSS, which is the pre-order step of transferring object identifiers, so that UDM has a data foundation, so that AMF can obtain object identifiers from UDM , and pass it to other relevant network elements through the subsequent PDU session creation process, so as to pass the object identifier to as many network elements as possible, thereby realizing the automatic configuration of the object identifier.
  • BOSS is the pre-order step of transferring object identifiers
  • the object identifier can be added by adding parameters in the contract information.
  • two parameters are added to the contract information through BOSS, which are "enterprise identifier" and "enterprise group identifier".
  • the enterprise identifier It is used to identify a specific enterprise.
  • the enterprise group identifier is used to represent the enterprise group to which the enterprise belongs. Enterprises in this enterprise group have similar business characteristics. Those skilled in the art know how to add parameters in the BOSS contract information, and according to The actual need to adjust the number of parameters, this embodiment will not go into details, it only needs to realize that the subscription data carries at least one object identifier.
  • step S120 in the embodiment shown in FIG. 1 is executed, it also includes but is not limited to the following steps:
  • Step S410 sending policy request information to the PCF, where the policy request information carries an object identifier
  • Step S420 acquiring and applying the service policy fed back by the PCF according to the object identifier.
  • the AMF in addition to sending the BOSS contract data to the UDM, it can also be sent to the PCF.
  • the AMF After the AMF obtains the object identifier from the UDM, it can add the object identifier to the policy request information requesting the service policy from the PCF, so that The PCF can not only verify the object identifier of the service object, but also enable the PCF to specify and issue access and mobility policies according to the object identifier.
  • step S130 in the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S510 determine the target service interface according to the business process, and the target service interface is used for information interaction with the network element of the next process node;
  • Step S520 adding an identification information element on the target service interface according to the object identification
  • Step S530 passing the object identifier to the network element of the next process node through the identifier information element.
  • the service interfaces used between two adjacent network elements may be different.
  • the target service interface involved in the current business process can be determined first. , and add an interface information element to the target service interface, so that the downstream network element can obtain the identification information element, thereby obtaining the object identification.
  • the SMF is the downstream network element of the AMF, and the AMF can add an identification information element to the service interface sending the session creation request, so that the SMF can obtain the object identifier through the session creation request information.
  • step S130 in the embodiment shown in FIG. 1 also includes but is not limited to the following steps:
  • Step S610 through information interaction for the business process, the object ID is transmitted one by one to all target network elements corresponding to the business process, so that all target network elements acquire and store the object ID.
  • the object identification can be placed on all network elements of the service process through the operation shown in the embodiment in Figure 5 In the middle, the upstream network element in the adjacent position is transmitted to the downstream network element, and so on, until it is transmitted to the network element corresponding to the last process node of the business process, thereby realizing the automatic configuration of the object identifier.
  • step S130 in the embodiment shown in FIG. 1 is executed, it also includes but is not limited to the following steps:
  • Step S710 when the ID change request corresponding to the object ID is obtained, initiate the de-registration process, and transfer the object ID to the target network element through information interaction for the de-registration process, so that the target network element deletes the previously obtained object ID ;
  • Step S720 obtain a new object identifier from the identifier change request, and re-initiate the registration process for the business object;
  • step S730 the new object identifier is transferred to the target network element through the information interaction of the re-initiated registration process.
  • the object ID does not remain unchanged. Therefore, when the object ID changes, the object ID of the business object needs to be modified.
  • the de-registration process can delete the information of business objects in all network elements, so you can initiate the de-registration process
  • the deregistration reason value can be added in the trigger information of the deregistration process, and the object identifier can be added to the deregistration reason value, so that each downstream network element can obtain the deregistration reason value Delete the object ID from the local.
  • the registration process includes but is not limited to the following steps:
  • Step S810 the enterprise user activates the network, and the BOSS sends the signing data to the PCF and UDM, and adds two parameters of "enterprise identification” and "enterprise group identification” in the signing information;
  • Step S820 the AMF obtains the registration request, and initiates the registration process
  • Step S830 adding an enterprise identification information element to the AccessAndMobilitySubscriptionData type in the Nudm_SDM_Get service interface, so that the AMF will obtain the subscription data from the UDM through the Nudm_SDM_Get service interface;
  • Step S840 in the Npcf_SMPolicyControl service interface of PCF, the PolicyAssociationRequest type adds an enterprise identification cell, and the AMF sends an Npcf_AMPolicyControl_Create Request message to the PCF to establish an access management (Access Management, AM) policy control association.
  • the PCF can base the enterprise identification or enterprise group ID to formulate and deliver access and mobility policies.
  • Step S910 the UE sends a non-access stratum (Non-Access-Stratum, NAS) message to the AMF, and initiates a session creation process;
  • NAS Non-Access-Stratum
  • Step S920 after receiving the request, the AMF selects the SMF for the establishment of the PDU session according to information such as single network slice selection assistance information (S-NSSAI), DNN, etc., and then requests the SMF to create an SMContext through the Nsmf_PDUSession_CreateSMContext Request message. context;
  • S-NSSAI single network slice selection assistance information
  • DNN DNN
  • Step S930 the SMF obtains the enterprise identity again through the signing process with the UDM and checks it with the identity carried by the front end;
  • Step S940 the SMF sends a Npcf_SMPolicyControl_Create Request message, and requests the PCF for strategy model (Strategy Model, SM) policy association. After receiving the request, the PCF can formulate and issue a control strategy based on the enterprise identification or enterprise group identification;
  • strategy model Strategy Model, SM
  • Step S950 SMF sends Nchf_ConvergedCharging_Create Requestet to create a charging session request to CHF;
  • step S960 the SMF starts to establish a connection with the UPF, provides data monitoring, reporting rules, and CN tunnel information for the PDU session, and the SMF sends a PFCP Session EstablishmentRequest message to the UPF, thereby finally passing the identifier to the UPF.
  • Step S1010 when the registered user's contracted enterprise ID changes, UDM will notify the AMF user to de-register through the Nudm_UECM_Deregistration Notification message, and the newly added de-registration reason value is "UE_Enterprise_IDENTITY_CHANGE". After receiving the notification, AMF will trigger the user's Go to the registration process. If the session exists, the session release process will be initiated.
  • a service configuration method is also provided, which is applied to a network element.
  • the network element is configured with an object identifier using the network element configuration method described in the above embodiment.
  • the service configuration method includes but not It is limited to step S1110 and step S1120.
  • step S1110 a service creation request is acquired, and the service creation request includes a target object identifier and a target service.
  • the service creation request can be obtained through the Network Exposure Function (NEF), and delivered to the corresponding target network element.
  • the target business can be statistics, collection and reporting of key performance indicators (Key Performance Indicator, KPI), monitoring and alarming, policy and billing control for different enterprises or different enterprise groups, and the specific target business can be selected according to actual needs.
  • KPI Key Performance Indicator
  • Step S1120 determine the target business object according to the target object identifier, and configure the target business for the target business object.
  • the same type of identifier can be added to the service creation request, so that the NEF can determine the corresponding service object.
  • an NEF is added on the basis of the system structure shown in FIG. 2 , wherein the NEF communicates with each network element, so that after the NEF obtains a service creation request, it can be delivered to the corresponding service network element.
  • the NEF communicates with each network element, so that after the NEF obtains a service creation request, it can be delivered to the corresponding service network element.
  • NEF and object identification Through the setting of NEF and object identification, it can provide users with a capability opening interface, so as to realize independent operation and maintenance and operation.
  • step S1120 in the embodiment shown in FIG. 11 also includes but is not limited to the following steps:
  • Step S1310 establishing an association relationship between the target service and the target object identifier.
  • step S1120 in the embodiment shown in FIG. 11 also includes but is not limited to the following steps:
  • Step S1412 establishing an association relationship between the target strategy and the target object identifier
  • Step S1420 determine the target service network element corresponding to the target policy, and send the target policy and the association relationship to the target service network element, so that the target service network element determines the target object identifier according to the association relationship, and determines the target service according to the target object identifier object to apply the target policy against the target business object.
  • the target object identifier is added in the service creation request, so that the PCF can issue a specific QoS policy to the SMF for the enterprise user.
  • this example includes but is not limited to the following steps:
  • Step S1510 the enterprise user sends a subscription request to the NEF through the operation system, and subscribes to monitor the state of the user terminal of the enterprise, wherein the subscription request carries the enterprise identification of the enterprise user;
  • Step S1520 the UE initiates registration with the 5GC, and notifies the enterprise operation system that the terminal status is reachable through the NEF;
  • Step S1530 the enterprise operation system records and updates the current real-time terminal status list.
  • an embodiment of the present application also provides a network element, which includes: a memory 1610 , a processor 1620 , and a computer program stored in the memory 1610 and operable on the processor 1620 .
  • the processor 1620 and the memory 1610 may be connected through a bus or in other ways.
  • the non-transitory software programs and instructions required to implement the network element configuration method or service configuration method of the above embodiments are stored in the memory 1610, and when executed by the processor 1620, the network element configuration applied to the AMF in the above embodiments is executed Method, for example, execute method step S110 to step S130 in Fig. 1 described above, method step S310 to step S320 in Fig. 3, method step S410 to step S420 in Fig. 4, method step S510 to step in Fig. 5 S530, method step S610 in FIG. 6 , method step S710 to step S730 in FIG. 7 , method step S810 to step S840 in FIG. 8 , method step S910 to step S960 in FIG. 9 , method step S1010 in FIG.
  • the embodiment of the present application includes: acquiring trigger information, and initiating a business process according to the trigger information; acquiring an object identifier, wherein the object identifier is a business object belonging to the business process; The object identifier is transmitted to a target network element, wherein the target network element is located downstream of the AMF in the service process.
  • the object identifier can be transferred to each target network element through the information interaction of the business process, and the automatic configuration of the object identifier is realized, which effectively reduces the complexity of operation and maintenance degree, improve work efficiency.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the above-mentioned Execution by a processor in the network element embodiment can cause the above-mentioned processor to execute the network element configuration method applied to AMF in the above-mentioned embodiment, for example, execute steps S110 to S130 of the method in FIG. 1 described above, and FIG. 3 Method step S310 to step S320 in, method step S410 to step S420 in Fig. 4, method step S510 to step S530 in Fig. 5, method step S610 in Fig. 6, method step S710 to step S730 in Fig.
  • the method steps S1110 to S1120 in FIG. 11 , the method steps S1310 in FIG. 13 , the method steps S1410 to S1420 in FIG. 14 , and the method steps S1510 to S1530 in FIG. 15 are described above. Those skilled in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware and an appropriate combination thereof.
  • Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit .
  • a processor such as a central processing unit, digital signal processor, or microprocessor
  • Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种网元配置方法、业务配置方法、网元、存储介质，该网元配置方法包括：获取触发信息，根据所述触发信息发起业务流程(S110)；获取对象标识，其中，所述对象标识归属于所述业务流程的业务对象(S120)；通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，其中，所述目标网元在所述业务流程中位于所述AMF的下游(S130)。

Description

网元配置方法、业务配置方法、网元、存储介质
相关申请的交叉引用
本申请基于申请号为202110677353.5、申请日为2021年06月18日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信领域，尤其涉及一种网元配置方法、业务配置方法、网元、存储介质。
背景技术
随着通信技术和互联网技术的发展，第五代通信(5th Generation Communication，5GC)在各行各业的应用越来越广泛，为了满足不同企业的网络定制需求，需要针对运维数据和运营策略进行差异化管控。对于传统的核心网模式，差异化管控通常基于数据网络名称(Data Network Name，DNN)、跟踪区域码(Tracking Area Code，TAC)和切片等较粗的粒度，而切片或者DNN可能由多个企业共享，很难针对每个企业进行管控。
虽然DNN结合综合业务数字网(Integrated Services Digital Network，ISDN)号段也能针对企业进行区分，但是设置和映射关系维护都需要通过运维在逐个网元完成，增加了运维的复杂性，而且效率低下。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种网元配置方法、业务配置方法、网元、存储介质。
第一方面，本申请实施例提供了一种网元配置方法，应用于接入和移动管理功能(Access and Mobility Management Function，AMF)，所述网元配置方法包括：获取触发信息，根据所述触发信息发起业务流程；获取对象标识，其中，所述对象标识归属于所述业务流程的业务对象；通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，其中，所述目标网元在所述业务流程中位于所述AMF的下游。
第二方面，本申请实施例提供了一种业务配置方法，应用于网元，所述网元应用第一方面所述的网元配置方法配置有对象标识，所述业务配置方法包括：获取业务创建请求，所述业务创建请求包括目标对象标识和目标业务；根据所述目标对象标识确定目标业务对象，针对所述目标业务对象配置所述目标业务。
第三方面，本申请实施例提供了一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如第一方面所述的网元配置方法，或者，所述处理器执行所述计算机程序时实现如第二方面所述的业务配置方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的网元配置方法的流程图；
图2是本申请另一个实施例提供的网元管理系统的结构图；
图3是本申请另一个实施例提供的获取签约数据的流程图；
图4是本申请另一个实施例提供的获取业务策略的流程图；
图5是本申请另一个实施例提供的传递对象标识的流程图；
图6是本申请另一个实施例提供的逐个网元传递对象标识的流程图；
图7是本申请另一个实施例提供的重新传递对象标识的流程图；
图8是本申请示例一的流程图；
图9是本申请示例二的流程图；
图10是本申请示例三的流程图；
图11是本申请另一个实施例提供的业务配置方法的流程图；
图12是本申请另一个实施例提供的网元管理系统的结构图；
图13是本申请另一个实施例提供的建立关联关系的流程图；
图14是本申请另一个实施例提供的配置目标策略的流程图；
图15是本申请示例四的流程图；
图16是本申请另一个实施例提供的网元的结构图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请提供了一种网元配置方法、业务配置方法、网元、存储介质，该网元配置方法包括：获取触发信息，根据所述触发信息发起业务流程；获取对象标识，其中，所述对象标识归属于所述业务流程的业务对象；通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，其中，所述目标网元在所述业务流程中位于所述AMF的下游。根据本申请实施例提供的方案，只需要进行一次部署下发，即可以通过业务流程的信息交互将对象标识传递至各个目标网元，实现了对象标识的自动配置，有效减少了运维的复杂度，提高工作效率。
下面结合附图，对本申请实施例进行阐述。
如图1所示，图1是本申请一个实施例提供的网元配置方法，应用于AMF，网元配置方法包括但不限于有步骤S110、步骤S120和步骤S130。
步骤S110，获取触发信息，根据触发信息发起业务流程。
需要说明的是，触发信息可以是任意能够使得AMF发起业务流程的请求信息，例如，终端(User Equipment，UE)发送的注册请求或者协议数据单元(Protocol Data Unit，PDU) 会话创建请求，能够使得AMF发起对应的业务流程即可，本实施例并不涉及业务流程的发起方式的改进，在此不多作赘述。
步骤S120，获取对象标识，其中，对象标识归属于业务流程的业务对象。
需要说明的是，触发信息可以携带有对象标识，也可以通过AMF根据触发信息获取对象标识，例如触发信息为注册请求，UE只需要发送设备信息，能够使得AMF根据设备信息从统一数据管理功能(Unified Data Management，UDM)或者策略控制功能(Policy Control Functionality，PCF)的签约数据中匹配出对应的对象标识即可；又如，当触发信息为PDU会话创建请求，由于UE已经完成注册，AMF通过注册流程获取到了对象标识，因此可以直接确定与UE对应的对象标识，进行后续操作；又如，当触发信息为变更对象标识的请求，则触发信息中携带有对象标识，AMF可以从触发信息中获取对象标识，从而根据对象标识进行后续的去注册流程。
值得注意的是，对象标识可以是任意粒度，例如对于不同企业进行的配置，对象标识可以是针对每一个企业，当然，对象标识也可以采用较粗的粒度，针对若干个具有相同特定业务特征的企业，本领域技术人员有动机根据实际需求调整对象标识所对应的粒度，在此不多作赘述。
需要说明的是，对象标识可以是任意形式，例如采用根据某一标准指定的数值、字母等，本实施例对对象标识的具体形式不作过多限定。
步骤S130，通过针对业务流程的信息交互将对象标识传递至目标网元，其中，目标网元在业务流程中位于AMF的下游。
需要说明的是，AMF为核心网的控制面实体，用于用户的移动性管理，因此对于大多数业务流程，AMF位于业务流程的上游，能够发起各种业务流程，因此，通过AMF获取对象标识，并且将对象标识加入至针对业务流程的信息交互，能够使得对象标识传递至每个网元。
需要说明的是，在业务流程中位于AMF下游的网元的类型根据具体的业务流程确定即可，例如对于PDU会话创建流程，AMF的下游网元为会话管理功能(Session Management Function，SMF)，本领域技术人员熟知各种业务流程所涉及的网元，在此不多作赘述。
例如，参考图2所示的系统结构，包括业务运营支撑系统(Business&Operation Support System，BOSS)，UDM、PCF、AMF、SMF、用户面功能(User Plane Function，UPF)、计费功能(Charging Function，CHF)，BOSS在获取到签约数据后下发至UDM和PCF，AMF通过注册流程从UDM获取对象标识，AMF通过创建PDU会话流程，将对象标识传递至SMF，SMF根据流程进一步传递至CHF和UPF，从而实现对象标识的自动传递，减少了运维的复杂度。
另外，AMF与UDM通信连接，参照图3，触发信息为注册请求，在一实施例中，图1所示实施例中的步骤S120还包括但不限于有以下步骤：
步骤S310，将注册请求针对的对象确定为业务对象；
步骤S320，发起注册流程，从UDM保存的签约数据中获取与业务对象相对应的对象标识，其中，签约数据由BOSS下发至UDM，签约数据携带有对象标识。
需要说明的是，通过BOSS将签约数据下发至UDM，能够实现对象标识在UDM的部署，属于传递对象标识的前序步骤，使得UDM中具备数据基础，从而AMF能够从UDM中获取到对象标识，并通过后续的PDU会话创建流程传递至其他相关网元，从而将对象标识传递至尽可能多的网元中，从而实现对象标识的自动配置。
值得注意的是，可以通过在签约信息中增加参数的方式实现对象标识的添加，例如通过BOSS在签约信息中增加两个参数，分别为“企业标识”和“企业组标识”，其中，企业标识用于标识具体的企业，企业组标识用于表征该企业所归属的企业组，在该企业组的企业具有相似的业务特征，本领域技术人员熟知如何在BOSS的签约信息中增加参数，以及根据实际需求调整参数的数量，本实施例对此不多作赘述，能够实现签约数据携带有至少一种对象标识即可。
另外，AMF与PCF通信连接，参照图4，在一实施例中，在执行完图1所示实施例中的步骤S120之后，还包括但不限于有以下步骤：
步骤S410，向PCF发送策略请求信息，策略请求信息携带有对象标识；
步骤S420，获取并应用PCF根据对象标识反馈的业务策略。
需要说明的是，BOSS的签约数据除了下发至UDM，还可以下发至PCF中，在AMF从UDM获取到对象标识后，可以在向PCF请求业务策略的策略请求信息中添加对象标识，使得PCF既可以对业务对象的对象标识进行校验，也能够使得PCF根据对象标识指定并下发接入和移动性策略。
另外，参照图5，在一实施例中，图1所示实施例中的步骤S130还包括但不限于有以下步骤：
步骤S510，根据业务流程确定目标服务接口，目标服务接口用于与下一个流程节点的网元进行信息交互；
步骤S520，根据对象标识在目标服务接口增加标识信元；
步骤S530，通过标识信元将对象标识传递至下一个流程节点的网元。
值得注意的是，对于不同的业务流程，相邻的两个网元之间使用的服务接口可能不同，为了对象标识能够通过业务流程进行传递，可以先确定当前的业务流程所涉及的目标服务接口，并在目标服务接口增加接口信元，使得下游网元能够获取到标识信元，从而得到对象标识。例如，在创建PDU会话流程中，SMF为AMF的下游网元，AMF可以在发送会话创建请求的服务接口中增加标识信元，从而使得SMF通过会话创建请求信息得到对象标识。
另外，参照图6，在一实施例中，图1所示实施例中的步骤S130还包括但不限于有以下步骤：
步骤S610，通过针对业务流程的信息交互，使得对象标识在业务流程所对应的全部目标网元中逐个传递，从而使全部的目标网元获取并保存对象标识。
可以理解的是，由于业务流程通常涉及多个网元，因此，为了确保尽可能多的网元得到对象标识，可以通过图5实施例所示的操作，将对象标识在业务流程的全部网元中逐级传递，处于相邻位置的上游网元传递至下游网元，以此类推，直至传递至业务流程最后一个流程节点所对应的网元，从而实现了对象标识的自动配置。
另外，参照图7，在一实施例中，在执行完图1所示实施例中的步骤S130之后，还包括但不限于有以下步骤：
步骤S710，当获取到与对象标识相对应的标识变更请求，发起去注册流程，并通过针对去注册流程的信息交互向目标网元传递对象标识，以使目标网元删除在先得到的对象标识；
步骤S720，从标识变更请求中获取新的对象标识，并针对业务对象重新发起注册流程；
步骤S730，通过重新发起的注册流程的信息交互将新的对象标识传递至目标网元。
需要说明的是，在实际使用过程中，对象标识并不是保持不变的，因此，在对象标识发生变化的情况下，需要对业务对象的对象标识进行修改。
值得注意的是，为了避免错误的对象标识导致业务出错，需要确保修改全部网元中的对象标识，而去注册流程能够在全部的网元中删除业务对象的信息，因此可以通过发起去注册流程将在先的对象标识删除，例如，可以在去注册流程的触发信息中增加去注册原因值，在该去注册原因值中增加对象标识，从而使得下游的每个网元得到去注册原因值后从本地删除对象标识。
可以理解的是，在通过去注册流程删除在先的对象标识之后，需要重新配置新的对象标识，可以通过新的对象标识重新发起注册流程，具体的方式可以参考图1至图6所示实施例的描述，为了叙述简便在此不重复赘述。
另外，为了更好地对图1至图7所示实施例的技术方案进行解释，以下结合图2所示的系统结构，提出三个示例。
示例一：注册流程
参考图8，在该注册流程中，包括但不限于有以下步骤：
步骤S810，企业用户开通入网，BOSS向PCF和UDM下发签约数据，在签约信息中新增“企业标识”和“企业组标识”两个参数；
步骤S820，AMF获取注册请求，发起注册流程；
步骤S830，在Nudm_SDM_Get服务接口中的AccessAndMobilitySubscriptionData类型增加企业标识信元，使得AMF将通过Nudm_SDM_Get服务接口向UDM获取签约数据；
步骤S840，在PCF的Npcf_SMPolicyControl服务接口中PolicyAssociationRequest类型新增企业标识信元，AMF向PCF发送Npcf_AMPolicyControl_Create Request消息，建立接入管理(Access Management，AM)策略控制关联，PCF收到请求后可基于企业标识或企业组标识制定并下发接入和移动性策略。
需要说明的是，上述示例仅对做出改进的步骤进行阐述说明，在相邻的两个步骤之间还可能存在相关协议规定的流程，本领域技术人员熟知该流程，在此不多作赘述。
示例二：会话创建流程
步骤S910，UE向AMF发送非接入层(Non-Access-Stratum，NAS)消息，发起会话创建流程；
步骤S920，AMF收到请求后，根据基于单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、DNN等信息为PDU会话建立选择SMF，然后通过Nsmf_PDUSession_CreateSMContext Request消息向SMF请求创建SM上下文；
步骤S930，SMF通过与UDM间的获取签约流程再次获取企业标识并与前端携带的标识进行校验；
步骤S940，SMF发送Npcf_SMPolicyControl_Create Request消息，向PCF请求策略模式(Strategy Model，SM)策略关联，PCF收到请求后可基于企业标识或企业组标识制定并下发控制策略；
步骤S950，SMF发送Nchf_ConvergedCharging_Create Requset，向CHF创建计费会话请求；
步骤S960，SMF开始建立与UPF的连接，提供用于该PDU会话的数据监测、报告规则、 CN隧道信息，SMF向UPF发送PFCP Session EstablishmentRequest消息，从而将该标识最终传递至UPF。
需要说明的是，上述示例仅对做出改进的步骤进行阐述说明，在相邻的两个步骤之间还可能存在相关协议规定的流程，本领域技术人员熟知该流程，在此不多作赘述。
示例三：企业标识变更
步骤S1010，当已注册的用户所签约的企业标识发生变更时，UDM将通过Nudm_UECM_Deregistration Notification消息通知AMF用户去注册，新增去注册原因值为"UE_Enterprise_IDENTITY_CHANGE"，AMF收到通知后，将触发用户的去注册流程，如果会话存在，将发起会话释放流程。
需要说明的是，用户去注册后会重新注册并进行新的会话创建，可以参考示例一和示例二的流程，在此不重复赘述。
需要说明的是，上述示例仅对做出改进的步骤进行阐述说明，在相邻的两个步骤之间还可能存在相关协议规定的流程，本领域技术人员熟知该流程，在此不多作赘述。
另外，参照图11，在一实施例中，还提供了一种业务配置方法，应用于网元，网元应用如上实施例所述的网元配置方法配置有对象标识，业务配置方法包括但不限于有步骤S1110和步骤S1120。
步骤S1110，获取业务创建请求，业务创建请求包括目标对象标识和目标业务。
需要说明的是，业务创建请求可以通过网络能力开放功能(Network Exposure Function，NEF)获取，并且下发给相对应的目标网元。目标业务可以是针对不同企业或者不同企业组的统计、收集、上报关键绩效指标(Key Performance Indicator，KPI)、监控告警及策略和计费控制，根据实际需求选取具体的目标业务即可。
步骤S1120，根据目标对象标识确定目标业务对象，针对目标业务对象配置目标业务。
需要说明的是，由于网元中已经配置有对象标识，因此可以在业务创建请求中添加相同类型的标识，从而使得NEF能够确定对应的业务对象。
值得注意的是，由于不同的业务所对应的网元不同，因此在确定目标业务对象之后，还需要确定对应的网元，针对该网元进行目标业务的配置。
例如，参考图12，在图2所示的系统结构的基础上增加NEF，其中NEF与各网元通信连接，从而使得NEF在获取到业务创建请求之后，能够传递至对应的业务网元。通过NEF和对象标识的设置，能够为用户提供能力开放接口，从而实现自主运维和运营。
另外，参照图13，在一实施例中，图11所示实施例中的步骤S1120还包括但不限于有以下步骤：
步骤S1310，建立所述目标业务与所述目标对象标识的关联关系。
需要说明的是，在获取到目标对象标识和目标业务之后，可以通过建立关联关系，使得目标业务能够针对特定的目标对象标识，从而使得目标业务的运行是针对目标对象标识所对应的业务对象，从而提高运维的便利性。
另外，在一实施例中，网元为PCF，目标业务为目标策略，参照图14，图11所示实施例中的步骤S1120还包括但不限于有以下步骤：
步骤S1412，建立目标策略与目标对象标识的关联关系；
步骤S1420，确定目标策略所对应的目标业务网元，将目标策略和关联关系下发至目标 业务网元，以使目标业务网元根据关联关系确定目标对象标识，并根据目标对象标识确定目标业务对象，从而针对目标业务对象应用目标策略。
需要说明的是，通过NEF的设置，使得企业用户能够根据自身需求制定运维和运营策略，例如，根据企业对服务质量(Quality of Service，QoS)的需求，创建针对自身的QoS策略，可以通过业务创建请求，在业务创建请求中添加目标对象标识，从而使得PCF能够针对该企业用户向SMF下发特定的QoS策略。
为了更好地说明业务配置方法的技术方案，以下提出一个示例。
示例四：状态监控订阅
参考图15，该示例包括但不限于有以下步骤：
步骤S1510，企业用户通过运营系统向NEF发送订阅请求，订阅对本企业用户终端状态监控,其中，订阅请求携带有企业用户的企业标识；
步骤S1520，UE向5GC发起注册，通过NEF通知企业运营系统该终端状态可达；
步骤S1530，企业运营系统记录并更新当前实时的终端状态列表。
另外，参照图16，本申请的一个实施例还提供了一种网元，该网元包括：存储器1610、处理器1620及存储在存储器1610上并可在处理器1620上运行的计算机程序。
处理器1620和存储器1610可以通过总线或者其他方式连接。
实现上述实施例的网元配置方法或者业务配置方法所需的非暂态软件程序以及指令存储在存储器1610中，当被处理器1620执行时，执行上述实施例中的应用于AMF的网元配置方法，例如，执行以上描述的图1中的方法步骤S110至步骤S130、图3中的方法步骤S310至步骤S320、图4中的方法步骤S410至步骤S420、图5中的方法步骤S510至步骤S530、图6中的方法步骤S610、图7中的方法步骤S710至步骤S730、图8中的方法步骤S810至步骤S840、图9中的方法步骤S910至步骤S960、图10中的方法步骤S1010；或者，执行上述实施例中的应用于网元的业务配置方法，例如，执行以上描述的图11中的方法步骤S1110至步骤S1120、图13中的方法步骤S1310、图14中的方法步骤S1410至步骤S1420、图15中的方法步骤S1510至步骤S1530。
本申请实施例包括：获取触发信息，根据所述触发信息发起业务流程；获取对象标识，其中，所述对象标识归属于所述业务流程的业务对象；通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，其中，所述目标网元在所述业务流程中位于所述AMF的下游。根据本申请实施例提供的方案，只需要进行一次部署下发，即可以通过业务流程的信息交互将对象标识传递至各个目标网元，实现了对象标识的自动配置，有效减少了运维的复杂度，提高工作效率。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述网元实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的应用于AMF的网元配置方法，例如，执行以上描述的图1中的方法步骤S110至步骤S130、图3中的方法步骤S310至步骤S320、图4中的方法步骤S410至步骤S420、图5中的方法步骤S510至步骤S530、 图6中的方法步骤S610、图7中的方法步骤S710至步骤S730、图8中的方法步骤S810至步骤S840、图9中的方法步骤S910至步骤S960、图10中的方法步骤S1010；或者，执行上述实施例中的应用于网元的业务配置方法，例如，执行以上描述的图11中的方法步骤S1110至步骤S1120、图13中的方法步骤S1310、图14中的方法步骤S1410至步骤S1420、图15中的方法步骤S1510至步骤S1530。本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的实施例进行了说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (11)

  1. 一种网元配置方法，应用于接入和移动管理功能AMF，所述网元配置方法包括：
    获取触发信息，根据所述触发信息发起业务流程；
    获取对象标识，其中，所述对象标识归属于所述业务流程的业务对象；以及
    通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，其中，所述目标网元在所述业务流程中位于所述AMF的下游。
  2. 根据权利要求1所述的方法，其中，所述AMF与统一数据管理功能UDM通信连接，所述触发信息为注册请求，所述获取对象标识，包括：
    将所述注册请求针对的对象确定为所述业务对象；
    发起注册流程，从所述UDM保存的签约数据中获取与所述业务对象相对应的所述对象标识，其中，所述签约数据由业务运营支撑系统BOSS下发至所述UDM，所述签约数据携带有所述对象标识。
  3. 根据权利要求2所述的方法，其中，所述AMF与策略控制功能PCF通信连接，在所述获取对象标识之后，所述方法还包括：
    向所述PCF发送策略请求信息，所述策略请求信息携带有所述对象标识；
    获取并应用所述PCF根据所述对象标识反馈的业务策略。
  4. 根据权利要求1所述的方法，其中，所述针对所述业务流程的信息交互，包括：
    根据所述业务流程确定目标服务接口，所述目标服务接口用于与下一个流程节点的网元进行信息交互；
    根据所述对象标识在所述目标服务接口增加标识信元；以及
    通过所述标识信元将所述对象标识传递至所述下一个流程节点的网元。
  5. 根据权利要求4所述的方法，其中，所述通过针对所述业务流程的信息交互将所述对象标识传递至目标网元，包括：
    通过所述针对所述业务流程的信息交互，使得所述对象标识在所述业务流程所对应的全部目标网元中逐个传递，从而使全部的所述目标网元获取并保存所述对象标识。
  6. 根据权利要求1所述的方法，其中，在所述通过针对所述业务流程的信息交互将所述对象标识传递至目标网元之后，所述方法还包括：
    当获取到与所述对象标识相对应的标识变更请求，发起去注册流程，并通过针对所述去注册流程的信息交互向目标网元传递所述对象标识，以使所述目标网元删除在先得到的所述对象标识；
    从所述标识变更请求中获取新的对象标识，并针对所述业务对象重新发起注册流程；以及
    通过重新发起的注册流程的信息交互将所述新的对象标识传递至所述目标网元。
  7. 一种业务配置方法，应用于网元，所述网元应用权利要求1至6任意一项所述的网元配置方法配置有对象标识，所述业务配置方法包括：
    获取业务创建请求，所述业务创建请求包括目标对象标识和目标业务；
    根据所述目标对象标识确定目标业务对象，针对所述目标业务对象配置所述目标业务。
  8. 根据权利要求7所述的方法，其中，所述针对所述目标业务对象配置所述目标业务， 包括：
    建立所述目标业务与所述目标对象标识的关联关系。
  9. 根据权利要求7所述的方法，其中，所述网元为PCF，所述目标业务为目标策略，所述针对所述目标业务对象配置所述目标业务，包括：
    建立所述目标策略与所述目标对象标识的关联关系；
    确定所述目标策略所对应的目标业务网元，将所述目标策略和所述关联关系下发至所述目标业务网元，以使所述目标业务网元根据所述关联关系确定目标对象标识，并根据所述目标对象标识确定所述目标业务对象，从而针对所述目标业务对象应用所述目标策略。
  10. 一种网元，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至6中任意一项所述的网元配置方法，或者，所述处理器执行所述计算机程序时实现如权利要求7至9中任意一项所述的业务配置方法。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如权利要求1至6中任意一项所述的网元配置方法，或者，所述计算机可执行指令用于执行如权利要求7至9中任意一项所述的业务配置方法。
PCT/CN2022/090045 2021-06-18 2022-04-28 网元配置方法、业务配置方法、网元、存储介质 WO2022262441A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110677353.5 2021-06-18
CN202110677353.5A CN115499807A (zh) 2021-06-18 2021-06-18 网元配置方法、业务配置方法、网元、存储介质

Publications (1)

Publication Number Publication Date
WO2022262441A1 true WO2022262441A1 (zh) 2022-12-22

Family

ID=84465467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/090045 WO2022262441A1 (zh) 2021-06-18 2022-04-28 网元配置方法、业务配置方法、网元、存储介质

Country Status (2)

Country Link
CN (1) CN115499807A (zh)
WO (1) WO2022262441A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859165A (zh) * 2005-10-22 2006-11-08 华为技术有限公司 一种业务跟踪的方法和系统
CN109548008A (zh) * 2017-08-15 2019-03-29 华为技术有限公司 网络侧对远端用户设备的识别和控制方法以及设备
CN111436160A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 一种局域网通信方法、装置及系统
CN112566149A (zh) * 2019-09-26 2021-03-26 华为技术有限公司 配置业务的方法、通信装置和通信系统
WO2021056448A1 (zh) * 2019-09-27 2021-04-01 华为技术有限公司 通信处理方法和通信处理装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859165A (zh) * 2005-10-22 2006-11-08 华为技术有限公司 一种业务跟踪的方法和系统
CN109548008A (zh) * 2017-08-15 2019-03-29 华为技术有限公司 网络侧对远端用户设备的识别和控制方法以及设备
CN111436160A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 一种局域网通信方法、装置及系统
CN112566149A (zh) * 2019-09-26 2021-03-26 华为技术有限公司 配置业务的方法、通信装置和通信系统
WO2021056448A1 (zh) * 2019-09-27 2021-04-01 华为技术有限公司 通信处理方法和通信处理装置

Also Published As

Publication number Publication date
CN115499807A (zh) 2022-12-20

Similar Documents

Publication Publication Date Title
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
WO2020147760A1 (zh) 一种局域网通信方法、装置及系统
US11425225B2 (en) Method, apparatus, and equipment for exposing edge network capability, and storage medium
CN105745867B (zh) 用于在无线通信系统中管理特定资源的方法和设备
US20180352050A1 (en) Method and system for supporting edge computing
US9172822B2 (en) Methods, systems, and computer readable media for providing a user record deletion notification
WO2018157439A1 (zh) 业务处理的方法和设备
BR112021013594A2 (pt) Método e sistema de armazenamento compartilhável para análise de dados de rede
US20220191665A1 (en) Event notification method, apparatus and storage medium
CN109792598A (zh) 支持网络分片的漫游环境中用于终端附接和创建归属路由pdu会话的方法和设备
WO2021017999A1 (zh) 策略控制功能网元的选择方法、装置、系统及存储介质
CN111211912B (zh) 计费的方法和装置
JP2010213335A (ja) １対多ポイント（ｐｏｉｎｔ−ｔｏ−ｍｕｌｔｉｐｏｉｎｔ，ＰＴＭ）サービスに対する接続と会計処理のための方法とシステム
WO2022148254A1 (zh) 一种用户信息分析结果反馈方法及其装置
CN112073919A (zh) 多播广播业务的通信方法及装置、电子设备、存储介质
US20220124015A1 (en) Historical data support enhancement for network entities
WO2021197489A1 (zh) 通信系统、方法及装置
CN112134730B (zh) 网络数据采集方法及装置
KR20150031225A (ko) 무선 통신 시스템에서 서버를 활성화 또는 비활성화하기 위한 방법 및 장치
WO2021109134A1 (zh) Mbms信息的获取、发送方法、终端设备及网元设备
US11533597B2 (en) Method for processing message in M2M system and device therefor
US10268532B2 (en) Application message processing system, method, and application device
WO2022262441A1 (zh) 网元配置方法、业务配置方法、网元、存储介质
WO2010124571A1 (zh) 节点信息获取方法、客户端、服务器
WO2012167657A1 (zh) 一种实现事件转发的方法及通用信息模型cim服务器

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: 22823924

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE