










技术领域technical field
本发明涉及执行调度设备管理(scheduled device management)。 The present invention relates to performing scheduled device management. the
背景技术Background technique
总体而言,设备管理(DM:Device Management)技术涉及向设备管理(DM)服务器(或其他网络实体)显示(或指示)出位于设备管理(DM)树(或用于设备管理的其他类型的层级结构或逻辑格式)上的作为管理对象的设备管理(DM)客户端(即终端或其他用户设备)的资源,允许对该资源进行访问,并允许DM服务器轻松地对终端进行管理。 In general, Device Management (DM: Device Management) technology involves displaying (or indicating) to a Device Management (DM) server (or other network entity) the Hierarchical structure or logical format) as the resource of the device management (DM) client (terminal or other user equipment) as the management object, allowing access to the resource, and allowing the DM server to easily manage the terminal. the
在这类DM技术中,DM服务器可以指示终端处理设备管理命令,而被管理的终端在立即执行相应的命令之后可以向DM服务器报告执行的结果。并且,DM服务器可以请求终端改变、更新、删除或以其他方式处理设备管理的具体功能。 In this type of DM technology, the DM server can instruct the terminal to process the device management command, and the managed terminal can report the execution result to the DM server after executing the corresponding command immediately. And, the DM server may request the terminal to change, update, delete or otherwise handle specific functions of device management. the
本发明的一个方面是由发明人对某些DM技术中的以下缺陷的认识。即,在一些DM技术中,只有当终端中存在错误或异常时,终端才向DM服务器请求DM命令。由此,终端的诊断过程使得开销很大,并且由于在这些问题发生之前不能预期或发现,因此该诊断过程无法有效地解决诊断问题。 One aspect of the present invention is the recognition by the inventors of the following deficiencies in certain DM techniques. That is, in some DM technologies, the terminal requests a DM command from the DM server only when there is an error or abnormality in the terminal. Thus, the diagnostic process of the terminal is very expensive and cannot effectively solve the diagnostic problems since these problems cannot be anticipated or discovered before they occur. the
发明内容Contents of the invention
由此,为了解决上述问题,本发明提供一种终端,该终端能够在潜在的问题发生前从服务器接收设备管理命令以及执行所述命令的条件,监视是否满足该条件,并且如果条件满足则执行设备管理命令。 Therefore, in order to solve the above-mentioned problems, the present invention provides a terminal capable of receiving a device management command from a server and a condition for executing the command before a potential problem occurs, monitors whether the condition is satisfied, and executes the command if the condition is satisfied. Device management commands. the
附图说明Description of drawings
附图中示出了根据本发明的示范性实施方式的各个特征,其中: Various features according to exemplary embodiments of the present invention are shown in the accompanying drawings, in which:
图1示出了设备管理(DM)终端和设备管理(DM)服务器。 FIG. 1 shows a device management (DM) terminal and a device management (DM) server. the
图2是终端诊断方法的一个示例的流程图。 FIG. 2 is a flowchart of an example of a terminal diagnosis method. the
图3是执行调度设备管理的方法的一个示例的流程图。 3 is a flowchart of one example of a method of performing scheduled device management. the
图4是以一个示范性树结构示出根据本发明第一实施方式的调度环境的图。 FIG. 4 is a diagram showing an exemplary tree structure of a scheduling environment according to the first embodiment of the present invention. the
图5是以一个示范性树结构示出根据本发明第一实施方式的诊断管理对象的图。 FIG. 5 is a diagram showing an exemplary tree structure of diagnosis management objects according to the first embodiment of the present invention. the
图6是以一个示范性树结构示出根据本发明第二实施方式的调度管理对象的图。 Fig. 6 is a diagram showing an exemplary tree structure of a scheduling management object according to a second embodiment of the present invention. the
图7是以一个示范性树结构示出连接到图6所示的调度管理对象的诊断管理对象的图。 FIG. 7 is a diagram showing an exemplary tree structure of diagnostic management objects connected to the schedule management object shown in FIG. 6 . the
图8是以一个示范性树结构示出根据本发明第三示范性实施方式的诊断管理对象的图。 FIG. 8 is a diagram showing a diagnosis management object according to a third exemplary embodiment of the present invention in an exemplary tree structure. the
图9是以一个示范性树结构示出连接到图8所示的诊断管理对象的调度环境的图。 FIG. 9 is a diagram showing an exemplary tree structure of a scheduling environment connected to the diagnosis management object shown in FIG. 8 . the
图10是以一个示范性树结构示出根据本发明第四实施方式的调度环境和诊断管理对象的图。 Fig. 10 is a diagram showing an exemplary tree structure of scheduling environment and diagnosis management objects according to the fourth embodiment of the present invention. the
图11是以一个示范性树结构示出根据本发明第五实施方式的调度环境和诊断管理对象的图。 FIG. 11 is a diagram showing an exemplary tree structure of a scheduling environment and diagnosis management objects according to a fifth embodiment of the present invention. the
具体实施方式Detailed ways
如图1所示,根据本发明示范性实施方式的DM系统包括DM服务器100和终端200。可以想到,还可以实施其他类型的服务器、网络实体等。终端可以是用户装置、用户设备(UE)、移动终端、客户装置等。 As shown in FIG. 1 , a DM system according to an exemplary embodiment of the present invention includes a
DM服务器100可以包括DM调度使能服务器110(包括硬件、软件、或其任意组合)以及DM使能服务器120(包括硬件、软件、或其任意组合)。可以理解DM服务器100内可以存在附加和/或另选的实体和要素。 The
DM调度使能服务器110可以包括调度环境(scheduling context)管理模块111(包括硬件、软件、或其任意组合)和状态报告处理模块112(包括硬件、软件、或其任意组合)。可以理解DM调度使能服务器110内可以存在附加和/或另选的实体和要素。 The DM scheduling enabling
调度环境管理模块111可以生成调度环境(即在执行设备管理调度时使用的概要、基础、框架等)并请求终端200安装该调度环境。调度环境管理模块111可以与终端200建立DM会话,并通过建立的DM会话请求终端200安装所生成的调度环境。 The scheduling
调度环境可以包括以下中的至少一项:规定包括至少一条设备管理命令(或指令)的消息的任务元素(例如第一元素),以及规定条件(要素、环境等)的条件元素(例如第二元素)。所述条件可以是以下中的至少一项:基于定时器的条件、基于陷阱的条件、以及基于阈值的条件。这里,本领域技术人员可以将术语“陷阱(trap)”(如陷阱项、陷阱机制等中使用的)理解为是指某种类型的基于条件的方案(即,特定事件的发生使硬件、软件(即操作系统)或它们的组合以特定方式工作)。此外,如图4所示,调度环境还可以包括附加信息,下面将对此进行详细描述。 The scheduling environment may include at least one of the following: a task element (such as a first element) specifying a message including at least one device management command (or instruction), and a condition element (such as a second element) specifying a condition (element, environment, etc.) element). The condition may be at least one of: a timer-based condition, a trap-based condition, and a threshold-based condition. Here, those skilled in the art may understand the term "trap" (as used in trap item, trap mechanism, etc.) (i.e. the operating system) or a combination of them work in a particular way). In addition, as shown in Figure 4, the scheduling environment may also include additional information, which will be described in detail below. the
状态报告处理模块112可以从终端200接收状态报告(例如,从执行命令得到的结果,或从诊断和监视终端200得到的结果),并对该状态报告进行处理。 The status
DM使能服务器120可以与终端200建立会话,并接着请求终端200进行设备管理,但不通过调度环境。具体地说,DM使能服务器120可以生成管理对象并接着发送该管理对象,或请求终端200生成管理对象。接着,DM使能服务器120可以通过该管理对象访问终端200,并对终端200进行管理。 The DM-enabled
诊断监视服务器130可以生成适当的诊断和监视包,并向终端200发送所述包。该包例如可以是图5所示的诊断监视管理对象。并且,诊断监视使能服务器120可以接收以下中的至少一项:诊断和监视的结果,以及终端200发生的事件。 The
终端200
如图所示,终端200可以包括DM调度使能客户端210、DM使能客户端220、以及诊断监视使能客户端230。可以理解的是,终端200内可以存在附加和/或另选的实体或要素。 As shown in the figure, the terminal 200 may include a DM
DM调度使能客户端210可以包括在从服务器100接收到调度环境时安装该调度环境的第一实体210a,以及执行设备管理命令的第二实体210b。可以理解的是,DM调度使能客户端210中可以存在附加和/或另选的实体和要素。 The DM
第一实体210a可以包括调度环境安装模块211。调度环境安装模块211处理来自DM服务器100的调度环境安装请求。即,调度环境安装模块211可以按DM树的形式(或其他用于设备管理的层级结构或逻辑格式)安装调度环境。 The first entity 210a may include a scheduling
这里,调度环境安装模块211可以执行补充过程以处理该调度环境安装请求。例如,调度环境安装模块211请求诊断监视使能客户端230在发生了特定事件时进行通报。 Here, the scheduling
调度环境安装模块211可以在安装调度环境之前选择性地验证该调度环境的有效性。 The scheduling
第二实体210b可以包括条件匹配模块212、任务执行模块213、以及状态报告模块214。可以理解的是第二实体210b中可以存在附加和/或另选的实体和要素。 The second entity 210b may include a
条件匹配模块212可以监视条件是否匹配,并且如果匹配,则该条件匹配模块212可以请求任务执行模块213执行与该条件对应的命令。如果该条件对应于基于陷阱的条件,则条件匹配模块212在诊断监视使能客户端230通报了特定事件的发生的情况下判定条件匹配。 The
当执行命令的条件被判定为匹配时,任务执行模块213可以与DM使能客户端220协作以使得可以执行命令。 When the condition of executing the command is determined to be matched, the
状态报告模块214可以向DM服务器100报告终端200中的调度环境的一个或多个形态以及命令执行结果中的一项或更多项。状态报告模块214利用结果和调度环境状态中的一项或更多项来创建报告消息(或其他类型的报告指示),并接着向DM服务器100发送该报告消息。 The
DM使能客户端220可以通过与命令执行模块213协作来执行设备管理命令。详细地说,DM使能客户端220可以从命令执行模块213接收命令,执行该命令,并接着向命令执行模块213返回执行命令的结果。 The DM-enabled
并且,DM使能客户端220与DM服务器100建立会话以使得DM调度使能客户端210与DM服务器100通信。此外,DM使能客户端220接收诊断管理对象232,并将该诊断管理对象递送给诊断监视使能客户端230。 And, the DM-enabled
同时,诊断监视使能客户端230包括诊断监视代理231以及诊断管理对象232。 Meanwhile, the diagnosis
诊断监视代理231可以根据诊断管理对象232来诊断并监视终端200。并且,诊断监视代理231可以向DM服务器100发送对终端200的诊断和监视的结果。 The
诊断管理对象232包括诊断监视代理231诊断或监视终端200所需的信息。换句话说,终端管理对象232可以控制诊断监视代理231的工作。这里,诊断管理对象232可以与图5中所示的相同。 The
如上所述,DM服务器100可以包括DM调度使能服务器110和DM使能服务器120,并且终端200可以包括DM调度使能客户端210、DM使能客户端220、诊断监视使能客户端230。然而,可以通过对处理器(未示出)、网络接口(未示出)、以及存储装置(未示出)进行彼此组合来构造服务器100或终端200。这里,可以理解的是还可以使用其他类似的硬件、软件、或其任意组合。 As described above, the
操作 operate
现在将参考图2到图3描述根据示范性实施方式的终端和DM服务器的操作。尽管图2到图3未详细地示出所有要素,但是可以理解各操作均由DM服务器100和终端200的各个对应要素执行。 Operations of a terminal and a DM server according to an exemplary embodiment will now be described with reference to FIGS. 2 to 3 . Although not all elements are shown in detail in FIGS. 2 to 3 , it can be understood that each operation is performed by respective corresponding elements of the
图2是终端诊断方法的一个示例的流程图。 FIG. 2 is a flowchart of an example of a terminal diagnosis method. the
如图所示,DM服务器100向终端200提供要在终端200内执行的设备管理命令以及执行命令的条件。接着,如果确定条件匹配,则终端 200执行命令。因此,终端200认识到:只要终端200要求命令,DM服务器100就会立即提供设备管理命令。 As shown, the
1)DM服务器100(具体地说,诊断监视服务器130)创建诊断管理对象。 1) The DM server 100 (specifically, the diagnosis monitoring server 130) creates a diagnosis management object. the
2)DM服务器100与终端200建立DM会话,并向终端200发送所创建的诊断管理对象。 2) The
3)接着,终端200(具体地说,DM使能客户端220)接收诊断管理对象并向诊断监视代理231递送该诊断管理对象。 3) Next, the terminal 200 (specifically, the DM-enabled client 220 ) receives the diagnosis management object and delivers the diagnosis management object to the
4)诊断监视代理231在终端200内配置诊断管理对象。 4) The
5)此后,DM服务器110向终端200发送激活诊断管理对象的命令。 5) Thereafter, the
6)接着,终端200(具体地说,DM使能客户端220)接收命令。并且,DM使能客户端220执行该命令。 6) Next, the terminal 200 (specifically, the DM-enabled client 220) receives the command. And, the DM-enabled
7)作为对执行命令的响应,激活诊断管理对象。 7) In response to the execute command, activate the diagnostic management object. the
8)诊断监视代理231开始对终端200进行诊断或监视。这里,采集与硬件、内存转储(memory dump)、错误、造成错误的代码、应用程序相关的一条或更多条信息。 8) The
9)诊断监视代理231向DM使能客户端220递送对终端200的诊断或监视的结果。 9) The
10)接着,DM使能客户端220向DM服务器100发送结果。 10) Next, the DM-enabled
图3是进行调度设备管理的方法的一个示例的流程图。 FIG. 3 is a flowchart of an example of a method for scheduling device management. the
如图3所示,DM服务器100根据对终端200的诊断和监视的结果创建调度环境,并发送安装调度环境的请求。 As shown in FIG. 3, the
处理过程的各步骤如下。 The steps of the processing are as follows. the
步骤1)~10)与图2所示的步骤类似,因此为避免无谓地混淆本发明而省略了对相同步骤的描述。 Steps 1) to 10) are similar to the steps shown in FIG. 2 , so the description of the same steps is omitted to avoid unnecessarily confusing the present invention. the
11)DM服务器100(具体地说,调度环境管理模块111)根据对终端200的诊断或监视的结果创建调度环境。即,DM服务器100(具体地说,调度环境管理模块111)创建调度环境以根据对终端200的诊断或监视的结果发现将在未来遇到的问题,并解决此类问题。 11) The DM server 100 (specifically, the scheduling environment management module 111 ) creates a scheduling environment according to the results of diagnosis or monitoring of the terminal 200 . That is, the DM server 100 (specifically, the scheduling environment management module 111) creates a scheduling environment to find problems that will be encountered in the future according to the results of diagnosis or monitoring of the terminal 200, and to solve such problems. the
12)DM服务器100利用DM协议请求终端200安装所生成的DM调度环境。 12) The
13)接着,终端200的DM使能客户端220向DM调度使能客户端210递送该调度环境。 13) Next, the DM-enabled
14)DM调度使能客户端210(具体地说,调度环境安装模块211)处理安装请求。 14) The DM scheduling enabling client 210 (specifically, the scheduling environment installation module 211 ) processes the installation request. the
15)随后,DM调度使能客户端210(具体地说,调度环境安装模块211)请求诊断监视代理231在发生特定事件时进行通报。在这种情况下,可以通过登记消息来发送该请求。 15) Subsequently, the DM scheduling enabling client 210 (specifically, the scheduling environment installation module 211) requests the
16)响应于该请求,诊断监视代理231登记该诊断管理对象232。 16) In response to the request, the
17)诊断监视代理231向DM调度使能客户端210通报登记完成。可以通过向DM调度使能客户端210发出确认(ACK)消息来实现该通报。 17) The
18)在接收到ACK消息后,DM调度使能客户端210向DM服务器100通报调度环境安装完成。可以通过向DM服务器100发出ACK消息来实现该通报。 18) After receiving the ACK message, the DM
19)~20),此后,如果捕捉到特定事件的发生,则诊断监视代理231向DM调度使能客户端210通报该发生。 19) to 20), after that, if the occurrence of a specific event is caught, the
21)接着,DM调度使能客户端210(具体地说,条件匹配模块212)判定发生的特定事件是否能够满足条件。如果满足条件,则条件匹配模块212请求任务执行模块213执行调度环境中的设备管理命令。 21) Next, the DM scheduling enabling client 210 (specifically, the condition matching module 212) determines whether the specific event that occurs can satisfy the condition. If the condition is satisfied, the
22)如果完成执行,则DM调度使能客户端210的状态报告模块214向DM服务器100报告执行命令的结果。 22) If the execution is completed, the
23)接着,DM服务器100(具体地说,DM调度使能服务器110的状态报告处理模块112)接收报告,并对该报告进行解析。 23) Next, the DM server 100 (specifically, the status
以上描述了示范性方法。可以理解的是所述方法可以通过软件、硬件或其组合来实现。例如,所述方法可以存储于存储介质(即移动终端的内部存储器、闪存、硬盘等)中,或可以实现为可由处理器(例如移动终端的内部微处理器)执行的软件程序中的代码或命令语言。 Exemplary methods are described above. It can be understood that the method can be implemented by software, hardware or a combination thereof. For example, the method may be stored in a storage medium (i.e., internal memory, flash memory, hard disk, etc. of the mobile terminal), or may be implemented as codes or command language. the
调度环境 Scheduling environment
图4是以一个示范性树结构(层级结构中的节点或其他类型的点、占位符等)示出调度环境的图。 FIG. 4 is a diagram showing a scheduling environment in an exemplary tree structure (nodes or other types of points in a hierarchy, placeholders, etc.). the
如图4所示,调度环境可以包括总体信息部分和调度部分。 As shown in Figure 4, the scheduling environment may include a general information section and a scheduling section. the
总体信息部分可以包括表示调度环境的标识符的ID节点、表示调度环境的名称的Name(名称)节点、规定调度环境的有效期的Valid(有效)节点、表示调度环境拥有者的Server(服务器)节点、表示调度环境状态的State(状态)节点、以及控制调度环境状态的state operation(状态操作)节点(或StateOP节点)。很明显,也可以有其他类型的附加或另选的节点。 The overall information part may include an ID node representing the identifier of the scheduling environment, a Name (name) node representing the name of the scheduling environment, a Valid (effective) node specifying the validity period of the scheduling environment, and a Server (server) node representing the owner of the scheduling environment , the State (state) node representing the state of the scheduling environment, and the state operation (state operation) node (or StateOP node) controlling the state of the scheduling environment. Obviously, there can be other types of additional or alternative nodes as well. the
该调度部分可以包括以下中一项或更多项:规定包括至少一个设备管理命令的消息的Task(任务)节点(即第一节点)、规定执行命令的条件的Cond(条件)节点(即第二节点)、以及规定是否应该向服务器报告执行命令的结果和调度环境的状态的Reporting(报告)节点(即第三节点)。 The scheduling part may include one or more of the following: a Task (task) node (i.e. the first node) specifying a message including at least one device management command, a Cond (condition) node (i.e. the first node) specifying a condition for executing the command two nodes), and a Reporting (reporting) node (that is, a third node) specifying whether to report the result of executing the command and the state of the scheduling environment to the server. the
Cond节点可以包括以下中的至少一项:规定基于定时器的条件的Timer(定时器)节点、规定基于陷阱的条件(即,是否发生特定事件)的Trap(陷阱)节点、以及规定基于阈值的条件(即终端中的特定管理对象的值是否达到阈值)的Th(阈值)节点。 Cond nodes may include at least one of the following: Timer (timer) nodes that specify timer-based conditions, Trap (trap) nodes that specify trap-based conditions (i.e., whether a specific event occurs), and threshold-based Th (threshold) node of the condition (that is, whether the value of a specific managed object in the terminal reaches the threshold). the
首先,该Timer节点可以规定时间、持续时间、周期、间隔的一个给定点。该Timer节点可以包括规定以完整表达形式表达的时间点的Base(基础)节点,以及规定了条件是否循环的循环规则(RRule)节点。因此,如果在RRule规则节点中未规定循环,则可以在命令执行一次之后禁用基于定时器的条件。 First, the Timer node can specify a given point of time, duration, period, and interval. The Timer node may include a Base (basic) node specifying a time point expressed in a complete expression form, and a RRule node specifying whether a condition is cyclic. Therefore, if no loop is specified in the RRule rule node, the timer-based condition can be disabled after the command has been executed once. the
并且,Trap节点可以包括规定特定事件的标识符的陷阱参考节点(TrapRef节点或标识符)。 And, the Trap node may include a trap reference node (TrapRef node or identifier) specifying an identifier of a specific event. the
如图4所示的Th节点包括以下中的至少一项:规定管理对象的地址的Address(地址)节点、规定监视管理对象的值的间隔的Interval(间隔)节点、规定阈值的Threshold(阈值)节点、规定阈值的格式是布尔(bool)、字符型、整型、浮点型、日期、或时间的ThFormat节点、规定节点的类型是绝对值或变量值的ThType节点、规定阈值是上升、下降或静态的Direction(方向)节点、以及规定阈值的容限的滞后(Hyst)节点。 The Th node as shown in Figure 4 includes at least one of the following: Address (address) node specifying the address of the management object, Interval (interval) node specifying the interval of monitoring the value of the management object, Threshold (threshold value) specifying the threshold Node, the format of the specified threshold value is bool (bool), character type, integer type, floating point type, date, or ThFormat node of time, the type of specified node is an absolute value or a ThType node of variable value, and the specified threshold value is rising or falling Or a static Direction node, and a hysteresis (Hyst) node that specifies a tolerance for a threshold. the
并且,Address节点包括以下中的至少一项:规定管理对象的统一资源标识符(URI)的URI节点、规定管理对象标识符(MOI)的MOI节点、以及由于在使用MOI节点的情况下具有相同MOI的管理对象共存而规定用于对指定管理对象与其他管理对象进行区分的附加信息的MOIfilter(MOI过滤器)节点。 And, the Address node includes at least one of the following: a URI node specifying a Uniform Resource Identifier (URI) of a management object, an MOI node specifying a Management Object Identifier (MOI), and since the MOI node has the same A MOI filter (MOI filter) node that defines additional information for distinguishing a designated managed object from other managed objects coexists with the managed objects of the MOI. the
如果不存在MOI节点,则URI节点可以规定完整地址。然而,如果存在MOI节点,那么URI节点可以规定相对于管理对象的根的相对地址。 If no MOI node exists, the URI node may specify the full address. However, if there is an MOI node, the URI node may specify a relative address with respect to the root of the managed object. the
具体地说,MOIfilter节点包括以下中的至少一项:URI节点、Value(值)节点以及Format(格式)节点。 Specifically, the MOIfilter node includes at least one of the following: a URI node, a Value (value) node, and a Format (format) node. the
包括在MOIfilter节点中的URI节点规定了指定管理对象相对于管理对象的根的统一资源标识符(URI)。 The URI node included in the MOIfilter node specifies a Uniform Resource Identifier (URI) specifying the managed object with respect to the root of the managed object. the
包括在MOIfilter节点中的Value节点规定了与由MOIfilter节点的URI节点指示的指定管理对象的值相比较的值,以在存在不止一个具有相同管理对象标识符(MOI)的管理对象的情况下对指定管理对象与其他管理对象进行区分。如果存在包含于MOIfilter节点中的URI节点,则Value节点中的值可以与URI的值进行比较。然而,如果不存在包含于MOIfilter节点中的URI节点,那么Value节点中的值可以与管理对象的根名称进行比较。 The Value node included in the MOIfilter node specifies the value to be compared with the value of the specified management object indicated by the URI node of the MOIfilter node, to compare the Specifies the managed object to distinguish from other managed objects. If there is a URI node included in the MOIfilter node, the value in the Value node can be compared with the value of the URI. However, if there is no URI node contained in the MOIfilter node, the value in the Value node can be compared with the root name of the managed object. the
包含于MOIfilter节点中的Format节点规定Value节点中的值的格式。可能的格式是‘b64’、‘bin’、‘bool’、‘int’、‘xml’、‘日期’、‘时间’、或‘浮点’。如果不存在Format节点,那么可以认为Value节点的格式是字符型。 The Format node contained in the MOIfilter node specifies the format of the value in the Value node. Possible formats are 'b64', 'bin', 'bool', 'int', 'xml', 'date', 'time', or 'float'. If there is no Format node, it can be considered that the format of the Value node is a character type. the
同时,Threshold节点规定阈值,并且Threshold节点的值是表示各种格式的阈值的数字文本串。阈值的实际格式由ThFormat节点决定。所选的管理对象的采样统计将与Threshold节点的值进行比较。但是,如果 当前采样值是第一个采样值(例如在电源重启后调度操作刚启动),并且如果没有先前的采样,则不考虑前一采样。 Meanwhile, the Threshold node specifies a threshold, and the value of the Threshold node is a numeric text string representing the threshold in various formats. The actual format of the threshold is determined by the ThFormat node. The sampling statistics of the selected management object will be compared with the value of the Threshold node. However, if the current sampled value is the first sampled value (e.g. the scheduled operation has just started after a power cycle), and if there is no previous sample, the previous sample is not considered. the
ThFormat节点规定阈值和滞后的实际格式。ThFormat节点的可能值是‘bool’、‘chr’、‘int’、‘日期’、‘时间’或‘浮点’。 The ThFormat node specifies the actual format of the threshold and hysteresis. Possible values for the ThFormat node are 'bool', 'chr', 'int', 'date', 'time' or 'float'. the
ThType节点规定阈值类型。ThType节点的可能值是‘绝对值’或‘变化(delta)值’。如果所述值为‘绝对值’,则管理对象的采样值将直接与阈值进行比较。如果所述值为‘变化值’,将从当前采样值中减去前一采样的采样值,并将该差值与所述阈值进行比较。 The ThType node specifies the threshold type. Possible values for a ThType node are 'absolute value' or 'delta value'. If the value is an 'absolute value', the sampled value of the managed object will be compared directly to the threshold. If the value is 'variation', the sample value of the previous sample is subtracted from the current sample value and the difference is compared to the threshold. the
Direction节点规定发生阈交(threshold crossing)事件时的值变化的行为。可能的值是‘上升’、‘下降’、或‘静态’。静态阈值是指当采样值等于阈值时发生条件匹配,而不考虑阈交的方向。当该阈值是上升阈值时,如果当前采样值大于或等于该阈值,并且如果前一采样小于该阈值时发生单一条件匹配。当该阈值是下降阈值时,如果当前采样值小于该阈值,并且如果前一采样大于该阈值时,则发生条件匹配。当该阈值设定为静态阈值时,当在不考虑阈交的情况下当前采样值等于该阈值,并且如果前一采样不等于该阈值时,发生单一条件匹配。但是只要采样值等于该阈值,条件的逻辑状态就为‘真’。 The Direction node specifies the behavior of value changes when a threshold crossing event occurs. Possible values are 'rising', 'falling', or 'static'. A static threshold means that a conditional match occurs when the sampled value is equal to the threshold, regardless of the direction of the threshold crossing. When this threshold is a rising threshold, a single condition match occurs if the current sampled value is greater than or equal to this threshold, and if the previous sample was less than this threshold. When the threshold is a falling threshold, a condition match occurs if the current sampled value is less than the threshold, and if the previous sample was greater than the threshold. When this threshold is set to a static threshold, a single condition match occurs when the current sampled value is equal to the threshold regardless of threshold crossing, and if the previous sample was not equal to the threshold. But as long as the sampled value is equal to the threshold, the logical state of the condition is 'true'. the
Hysteresis节点规定滞后值。Hysteresis节点的值是表示各种格式的滞后值的文本串。滞后值的实际格式由ThFormat节点决定。如果规定了滞后,在生成阈交事件之后,直至采样值降低至低于或升高至高于由该滞后规定的该阈值容限才会生成另一个阈交事件。如果由于噪声引起采样值在阈值周围波动,利用滞后可以防止生成过多的阈交事件。例如,在上升阈值的情况下,命令执行一次,将不会再次执行,除非采样值变为小于由该节点规定的阈值容限。 The Hysteresis node specifies the hysteresis value. The value of the Hysteresis node is a text string representing the hysteresis value in various formats. The actual format of the hysteresis values is determined by the ThFormat node. If a hysteresis is specified, after a threshold crossing event is generated, another threshold crossing event is not generated until the sampled value falls below or rises above the threshold tolerance specified by the hysteresis. Hysteresis is used to prevent excessive threshold crossing events from being generated if the sampled values fluctuate around the threshold due to noise. For example, in the case of a rising threshold, the command is executed once and will not be executed again unless the sampled value becomes less than the threshold tolerance specified by the node. the
同时,Task(任务)节点可以包括XML节点和Binary节点,XML节点规定消息是否包括具有基于XML(可扩展标记语言)数据的命令,而Binary节点规定消息是否包括基于二进制的数据的命令。 Meanwhile, the Task (task) node may include an XML node specifying whether the message includes a command with XML (Extensible Markup Language)-based data, and a Binary node specifying whether the message includes a command based on binary data. the
Reporting(报告)节点包括以下中的至少一项:规定是否应该向DM服务器100报告执行命令的结果的Gating(选通)节点,以及规定是否应该向DM服务器100报告调度环境的状态的Event(事件)节点。 The Reporting (report) node includes at least one of the following: a Gating (gate) node that stipulates whether the result of the execution command should be reported to the
图5是以一个示范性树结构(具有层级结构的节点或其他类型的点、占位符等)示出根据本发明第一实施方式的诊断管理对象的图。 FIG. 5 is a diagram showing a diagnosis management object according to the first embodiment of the present invention in an exemplary tree structure (nodes with hierarchical structure or other types of points, placeholders, etc.). the
参考图5,将以一个示范性树结构描述诊断管理对象。 Referring to FIG. 5, diagnosis management objects will be described in an exemplary tree structure. the
如上所述,诊断管理对象包括对终端200进行诊断或监视所需的信息。换句话说,终端管理对象包括DFID节点、ServerID(服务器ID)节点、诊断监视配置节点、诊断监视数据节点、Operation(操作)节点、以及State(状态)节点。 As described above, the diagnosis management object includes information required to diagnose or monitor the terminal 200 . In other words, the terminal management object includes a DFID node, a ServerID (server ID) node, a diagnostic monitoring configuration node, a diagnostic monitoring data node, an Operation (operation) node, and a State (status) node. the
DFID节点规定诊断功能的名称。并且,ServerID节点规定要报告的DM服务器200的标识符。 The DFID node specifies the name of the diagnostic function. And, the ServerID node specifies the identifier of the
DFID节点指示诊断功能的名称。ServerID节点报告在进行诊断功能时诊断操作的状态,或指令(指示)要将执行结果报告给的设备管理服务器的标识(ID)。诊断监视配置节点是指存储特定诊断功能所需的设定值的文件夹节点或内部节点。诊断监视数据节点是指存储诊断结果的节点或文件夹节点。 The DFID node indicates the name of the diagnostic function. The ServerID node reports the status of the diagnostic operation when performing the diagnostic function, or instructs (indicates) the identification (ID) of the device management server to which the execution result is to be reported. A diagnostic monitoring configuration node is a folder node or an internal node that stores setting values required for a specific diagnostic function. A diagnostic monitoring data node refers to a node or a folder node that stores diagnostic results. the
Operation节点中的Start(开始)节点是用于允许DM服务器(100)以远程方式执行诊断功能的节点。此外,Operation节点中的Stop(结束)节点是用于允许DM服务器(100)停止正在进行的诊断功能的节点。Operation节点中的Report(报告)节点是用于允许DM服务器(100)接收诊断结果报告的节点。State节点是用于通报诊断功能的状态的节点。 A Start node among Operation nodes is a node for allowing the DM server (100) to perform a diagnosis function in a remote manner. In addition, the Stop (end) node in the Operation node is a node for allowing the DM server (100) to stop the ongoing diagnosis function. The Report (report) node in the Operation node is a node for allowing the DM server (100) to receive a diagnosis result report. The State node is a node for notifying the status of the diagnostic function. the
图6是以一个示范性树结构示出根据本发明第二实施方式的调度管理对象的图。并且图7是以一个示范性树结构示出连接到图6所示的调度管理对象的诊断管理对象的图。 Fig. 6 is a diagram showing an exemplary tree structure of a scheduling management object according to a second embodiment of the present invention. And FIG. 7 is a diagram showing a diagnosis management object connected to the schedule management object shown in FIG. 6 in an exemplary tree structure. the
根据第二示范性实施方式,诊断监视使能客户端(230)可以监视条件是否匹配。 According to the second exemplary embodiment, the diagnostic monitoring enabling client (230) may monitor whether the conditions are matched. the
为此,从图6和图7中可知,条件(即Timer节点、Trap节点、Threshold节点)可以与调度环境分离,由此构成单独(独立)的管理对象。 For this reason, it can be known from Fig. 6 and Fig. 7 that the conditions (ie Timer node, Trap node, and Threshold node) can be separated from the scheduling environment, thereby forming a separate (independent) management object. the
并且,为此,诊断管理对象的诊断监视配置节点可以包括规定(指示)调度DM对象的地址(或ID或URI)的调度参考节点。因此,调度 DM对象可以连接到该诊断管理对象,并且诊断监视使能客户端(230)可以监视条件是否匹配。如果确定条件匹配,则诊断监视使能客户端(230)生成向条件匹配模块(212)递送(转发)的事件。这里,条件匹配模块(212)根据所述事件确定条件匹配,并请求任务执行模块(213)执行命令。 And, for this, the diagnosis monitoring configuration node of the diagnosis management object may include a dispatch reference node specifying (indicating) the address (or ID or URI) of the dispatch DM object. Therefore, the scheduling DM object can be connected to the diagnostic management object, and the diagnostic monitoring enabling client (230) can monitor whether the condition is matched. If the conditions are determined to match, the diagnostic monitoring enabling client (230) generates an event that is delivered (forwarded) to the condition matching module (212). Here, the condition matching module (212) determines that the condition matches according to the event, and requests the task execution module (213) to execute the command. the
图8是以一个示范性树结构示出根据本发明第三实施方式的调度管理对象的图。并且图9是以一个示范性树结构示出连接到图8所示的调度管理对象的调度环境的图。 Fig. 8 is a diagram showing an exemplary tree structure of a scheduling management object according to a third embodiment of the present invention. And FIG. 9 is a diagram showing a scheduling environment connected to the scheduling management object shown in FIG. 8 in an exemplary tree structure. the
根据第三实施方式,与第二实施方式类似地,诊断监视使能客户端(230)可以监视条件是否满足。 According to the third embodiment, similarly to the second embodiment, the diagnostic monitoring enabling client ( 230 ) can monitor whether a condition is satisfied. the
为此,如图8所示,在调度环境中分离出条件(即Timer节点、Trap节点、Threshold节点),并可以将该条件包括在诊断管理对象中。而且,如图9所示,诊断管理对象和调度环境的条件节点可以通过地址或ID(或URI)连接。 To this end, as shown in FIG. 8 , conditions (ie, Timer nodes, Trap nodes, and Threshold nodes) are separated in the scheduling environment, and the conditions can be included in the diagnosis management object. Moreover, as shown in FIG. 9, the diagnosis management object and the condition node of the scheduling environment can be connected by address or ID (or URI). the
因此,如果诊断监视使能客户端(230)确定条件匹配,则生成事件并将该事件递送(转发)给条件匹配模块(212)。这里,条件匹配模块(212)根据所述事件确定条件已经匹配,并可以请求任务执行模块(213)执行命令。 Accordingly, if the diagnostic monitoring enabled client (230) determines that the condition matches, an event is generated and delivered (forwarded) to the condition matching module (212). Here, the condition matching module (212) determines that the condition has been matched according to the event, and may request the task execution module (213) to execute the command. the
图10是以一个示范性树结构示出根据本发明第四实施方式的调度环境和诊断管理对象的图。 Fig. 10 is a diagram showing an exemplary tree structure of scheduling environment and diagnosis management objects according to the fourth embodiment of the present invention. the
如参照图10可知地,根据第四实施方式,诊断监视使能客户端(230)可以监视基于阈值的条件(即存储于阈值节点中的条件)是否匹配,并且条件匹配模块(212)可以监视基于定时器的条件(即存储于Timer节点中的条件)和基于事件的条件(即存储于Trap节点中的条件)是否匹配。 As can be seen with reference to FIG. 10, according to the fourth embodiment, the diagnostic monitoring enabling client (230) can monitor whether the threshold-based condition (ie, the condition stored in the threshold node) matches, and the condition matching module (212) can monitor Whether the condition based on the timer (that is, the condition stored in the Timer node) and the condition based on the event (that is, the condition stored in the Trap node) match. the
如图10(a)所示,调度环境的Cond(条件)节点可以包括Timer节点和Trap节点。并且Cond节点还可以包括指示终端200中的特定管理对象的管理节点(或MO节点)。该MO节点可以包括URI节点和Value(值)节点中的至少一项,URI节点指示具体管理对象的统一资源标识符,而Value节点规定用于附加地确定由URI节点指示的具体管理对象是否是预期的值。然而,显然这些节点(或附加和/或另选的节点)的其他实施方式也是可以的。 As shown in FIG. 10(a), the Cond (condition) node of the scheduling environment may include a Timer node and a Trap node. And the Cond node may also include a management node (or MO node) indicating a specific management object in the
如图10(b)所示,分离后的管理对象可以包括诊断监视配置节点(或DiagMonConfig节点)。诊断监视配置节点可以包括上述的Th(阈值)节点。 As shown in FIG. 10( b ), the separated management objects may include a diagnosis monitoring configuration node (or a DiagMonConfig node). The diagnostic monitoring configuration node may include the above-mentioned Th (threshold) node. the
下面将通过一些示例来进一步描述上述调度环境和分离后的管理对象。如果任意管理对象的值与由诊断监视配置节点的Th(阈值)节点指示的阈值交叉,则发生事件。接着,检查发生事件的任意管理对象是否与由调度环境中的管理对象节点的URI节点指示的特定管理对象相对应。如果该任意管理对象与之对应,则进一步检查发生的事件是否与由调度环境的Trap节点指示的事件相对应。如果发生的事件与之对应,则条件匹配模块212确定条件满足,并接着任务执行模块213执行命令。 Below, some examples will be used to further describe the above scheduling environment and separated management objects. An event occurs if the value of any managed object crosses the threshold indicated by the Th (Threshold) node of the Diagnostic Monitoring Configuration node. Next, it is checked whether any managed object in which an event occurred corresponds to the specific managed object indicated by the URI node of the managed object node in the scheduling environment. If the arbitrary management object corresponds to it, it is further checked whether the occurred event corresponds to the event indicated by the Trap node of the scheduling environment. If the event occurs corresponding thereto, the
图11是以一个示范性树结构示出根据本发明第五实施方式的调度环境和诊断管理对象的图。 FIG. 11 is a diagram showing an exemplary tree structure of a scheduling environment and diagnosis management objects according to a fifth embodiment of the present invention. the
根据第五实施方式,终端(200)可以采用不同的模块来监视基于阈值的条件(即存储于Threshold节点中的条件),并且如果确定条件匹配,则生成事件。并且,根据第五实施方式,终端(200)可以采用另一不同的模块来监视基于定时器的条件(即存储于Timer节点的条件),并且如果确定条件匹配,则可以生成事件。如果这样,则条件匹配模块(212)接收所生成的事件,并可以请求任务执行模块(213)执行命令。 According to the fifth embodiment, the terminal (200) may employ different modules to monitor threshold-based conditions (ie conditions stored in the Threshold node) and generate an event if the conditions are determined to match. Also, according to the fifth embodiment, the terminal (200) can employ another different module to monitor timer-based conditions (ie, conditions stored in the Timer node), and if it is determined that the conditions match, an event can be generated. If so, the condition matching module (212) receives the generated event and may request the task execution module (213) to execute the command. the
如图11(a)所示,调度环境的Cond(条件)节点仅包括管理对象。MO(管理对象)节点可以包括URI节点和Value节点中的至少一项,该URI节点指示特定管理对象的统一资源标识符,而该Value节点规定用于附加地确定由URI节点指示的特定管理对象是否是预期的值。 As shown in FIG. 11( a ), the Cond (condition) node of the scheduling environment includes only management objects. The MO (Management Object) node may include at least one of a URI node indicating a Uniform Resource Identifier of a specific management object and a Value node specified for additionally determining the specific management object indicated by the URI node Is the expected value. the
如图11(b)所示,包括(与调度环境分离的)Timer节点的定时器调度管理对象可以包括以下中的至少一项:规定执行设备管理命令的特定时间点的Base(基础)节点、规定是否应循环使用特定点的循环规则节点(或RRule节点)、以及Trap节点。该Trap节点可以包括以下中的 至少一项:规定当Trap节点到达特定点时将发生的特定事件的标识符的标识符节点(或ID节点)、Report(报告)节点、以及Schedule(调度)节点。这里,该Report节点包括服务器标识符节点(或ServerID节点)和用户交互节点(UI节点)中的至少一项,该ServerID节点规定如果发生特定事件则将该特定事件报告给的服务器的标识符,而该UI节点规定是否就特定事件的发生与用户交互。调度节点包括UI节点和参考节点(或ToRef节点、或标识符)中的至少一项,该UI节点规定是否与用户交互,而ToRef节点规定调度环境的标识符。 As shown in Figure 11(b), the timer scheduling management object including (separated from the scheduling environment) Timer node may include at least one of the following: a Base (basic) node specifying a specific time point for executing a device management command, A cycle rule node (or RRule node) that specifies whether a specific point should be cycled, and a Trap node. The Trap node may include at least one of the following: an identifier node (or ID node), a Report (report) node, and a Schedule (scheduling) node specifying an identifier of a specific event that will occur when the Trap node reaches a specific point . Here, the Report node includes at least one of a server identifier node (or ServerID node) and a user interaction node (UI node), and the ServerID node specifies an identifier of a server to which a specific event is reported if a specific event occurs, The UI node specifies whether to interact with the user on the occurrence of a specific event. The scheduling node includes at least one of a UI node and a reference node (or a ToRef node, or an identifier), the UI node specifies whether to interact with the user, and the ToRef node specifies the identifier of the scheduling environment. the
如图11(c)所示,包括(与调度环境分离的)Threshold节点的阈值监视管理对象可以包括以下中的至少一项:规定要监视的特定管理对象的标识符的统一资源标识符节点(或URI节点)、规定要监视的特定管理对象的阈值的Threshold节点、以及Trap节点。 As shown in Figure 11(c), the threshold monitoring management object including the Threshold node (separated from the scheduling environment) may include at least one of the following: a uniform resource identifier node specifying the identifier of the specific management object to be monitored ( or URI node), a Threshold node specifying a threshold for a specific managed object to be monitored, and a Trap node. the
下面将通过一些示例进一步描述上述调度环境和时间调度管理对象。如果发现已到达基础节点中指示的时间点,则事件发生。接着,检查发生的事件的标识符是否与Trap节点的Identifier节点中规定的标识符相对应。如果发生的事件的标识符与Trap节点的Identifier节点中规定的标识符相对应,则终端200根据Report节点的服务器标识符节点向服务器报告该情况。并将发生的事件递送给由ToRef节点规定的调度环境,终端200执行调度环境的Task节点规定的设备管理命令。 The above-mentioned scheduling environment and time scheduling management objects will be further described below through some examples. The event occurs if the point in time indicated in the base node is found to have been reached. Next, it is checked whether the identifier of the occurred event corresponds to the identifier specified in the Identifier node of the Trap node. If the identifier of the occurred event corresponds to the identifier specified in the Identifier node of the Trap node, the terminal 200 reports the situation to the server according to the server identifier node of the Report node. And deliver the occurred events to the scheduling environment specified by the ToRef node, and the terminal 200 executes the device management command specified by the Task node of the scheduling environment. the
此外,通过一些示例描述上述调度环境和阈值监视管理对象。如果由URI节点规定的特定管理对象的值与由Threshold节点规定的阈值相交,则事件发生。并且,检查所发生的事件的标识符是否与Trap节点的ID节点规定的标识符相对应。如果发生的事件的标识符与Trap节点的ID节点规定的标识符相对应,则终端200根据Report节点的服务器标识符节点向服务器报告该情况。并向由ToRef节点规定的调度环境递送所发生的事件。接着,终端200执行调度环境的Task节点中规定的设备管理命令。 In addition, the above-mentioned scheduling environment and threshold monitoring management objects are described with some examples. An event occurs if the value of a particular managed object specified by the URI node crosses the threshold specified by the Threshold node. And, it is checked whether the identifier of the occurred event corresponds to the identifier specified by the ID node of the Trap node. If the identifier of the event that occurs corresponds to the identifier specified by the ID node of the Trap node, the terminal 200 reports the situation to the server according to the server identifier node of the Report node. And deliver the occurring events to the scheduling environment specified by the ToRef node. Next, the terminal 200 executes the device management command specified in the Task node of the scheduling environment. the
如上所述,所述终端、服务器和方法可以具有以下特征。 As described above, the terminal, server and method may have the following features. the
即,本发明通过允许终端在潜在的问题发生前从服务器接收设备管 理命令和执行该命令的条件,并由此如果条件满足则执行该设备管理命令,来允许在适当的时间自动进行期望的设备管理。 That is, the present invention allows the terminal to receive a device management command and a condition for executing the command from a server before a potential problem occurs, and thereby execute the device management command if the condition is satisfied, allowing the desired operation to be performed automatically at the appropriate time. device management. the
本发明提供了一种终端,该终端包括:第一实体,其适于通过第一管理对象的地址或标识符识别第一管理对象,并监视是否符合所识别的第一管理对象中包含的调度;其中在第二管理对象中规定所述地址或所述标识符;以及第二实体,其适于在所述第一实体确定符合所述调度的情况下执行包括于调度环境中的设备管理命令。 The present invention provides a terminal comprising: a first entity adapted to identify a first management object by its address or identifier and to monitor compliance with the schedule contained in the identified first management object ; wherein said address or said identifier is specified in a second management object; and a second entity adapted to execute a device management command included in a scheduled environment if said first entity determines that said schedule is met . the
此外,本发明提供了一种终端,该终端包括:第一实体,其适于监视是否符合诊断管理对象中包括的调度;以及第二实体,其适于在所述第一实体确定符合所述调度的情况下执行包括于调度环境中的设备管理命令。 Furthermore, the present invention provides a terminal comprising: a first entity adapted to monitor compliance with a schedule included in a diagnostic management object; and a second entity adapted to, when said first entity determines compliance with said In the case of scheduling, the device management commands included in the scheduling environment are executed. the
此外,本发明提供了一种终端,该终端包括:第一实体,其适于根据包括基于阈值的条件的第一调度管理对象来监视是否满足基于阈值的条件;第二实体,其适于根据包括基于定时器的条件的第二调度管理对象来监视是否满足基于定时器的条件;以及第三实体,其适于在满足所述基于阈值的条件和所述基于定时器的条件的至少其中之一的情况下执行包括于调度环境中的设备管理命令。 Furthermore, the present invention provides a terminal comprising: a first entity adapted to monitor whether a threshold-based condition is satisfied according to a first scheduling management object comprising the threshold-based condition; a second entity adapted to monitor whether a threshold-based condition is satisfied according to a second scheduling management object comprising a timer-based condition to monitor whether the timer-based condition is met; and a third entity adapted to satisfy at least one of said threshold-based condition and said timer-based condition In the case of one, the device management commands included in the scheduling environment are executed. the
应注意的是,这里描述的特征和概念涉及针对由特定相应标准组织管理的设备管理(DM)的各种标准。因此,这里规定的各种对应的标准和/或概念也是本公开的一部分。 It should be noted that the features and concepts described herein relate to various standards for Device Management (DM) managed by particular corresponding standards organizations. Accordingly, various corresponding standards and/or concepts specified herein are also part of this disclosure. the
例如,这里描述的某些方面涉及具体标准(例如OMA、GSM、3GPP、3GPP2、IEEE等)。因此,这里描述的至少一些特征适用于这些已经开发的或正在演进的标准。 For example, certain aspects described herein relate to specific standards (eg, OMA, GSM, 3GPP, 3GPP2, IEEE, etc.). Accordingly, at least some of the features described herein are applicable to such developed or evolving standards. the
尽管本发明规定了与设备管理(DM)相关的命令、节点、子节点等的各种名称,但是可以清楚理解的是,此类名称和标签仅是示范性的。本发明的特征决不由此受到限制,因为可以使用其他等效的名称或标签,只要其指代相同或等效的功能和/或特征。 Although the present invention specifies various names for Device Management (DM) related commands, nodes, sub-nodes, etc., it is clearly understood that such names and labels are merely exemplary. The features of the present invention are in no way limited thereby, since other equivalent names or labels may be used as long as they refer to the same or equivalent function and/or feature. the
在说明书中对“一种实施方式”,“一个实施方式”,“示例性实施方式”等的引用是指结合该实施方式描述的具体特征、结构、或特性是包 括在本发明的至少一种实施方式中。本说明书中各个位置出现的此类词语并不一定指同一实施方式。此外,当结合任何实施方式描述具体特征、结构或特性时,认为本领域技术人员能够结合其他实施方式实现这些特征、结构或特性。 References in the specification to "one embodiment", "an embodiment", "exemplary embodiment" and the like mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one aspect of the present invention. in one embodiment. The appearances of such words in various places in this specification are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure or characteristic is described in connection with any embodiment, it is believed that one skilled in the art can implement that feature, structure or characteristic in combination with other embodiments. the
尽管结合示例性实施方式对各个实施方式进行了描述,但是应理解,本领域技术人员可以设计出落入本发明原理范围内的多个其他修改例和实施方式。更具体地说,在本公开、附图和所附的权利要求的范围内组成部分和/或对象构造的组合排列可以存在各种修改例和变形例。除了组成部分和/或构造的修改例和变形例之外,另外的应用对于本领域技术人员而言也是显而易见的。 Although embodiments have been described in conjunction with illustrative embodiments thereof, it should be understood that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the scope of the principles of this invention. More specifically, various modifications and variations are possible in combination arrangements of constituent parts and/or object configurations within the scope of the disclosure, drawings, and appended claims. In addition to modifications and variations of components and/or constructions, further applications will be apparent to those skilled in the art. the
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US76094306P | 2006-01-23 | 2006-01-23 | |
| US76094206P | 2006-01-23 | 2006-01-23 | |
| US60/760,943 | 2006-01-23 | ||
| US60/760,942 | 2006-01-23 | ||
| US76251706P | 2006-01-27 | 2006-01-27 | |
| US60/762,517 | 2006-01-27 | ||
| KR10-2006-0124992 | 2006-12-08 | ||
| KR1020060124992AKR20070108432A (en) | 2006-01-23 | 2006-12-08 | Device Management Scheduling Method |
| KR1020060124992 | 2006-12-08 | ||
| KR1020070005812 | 2007-01-18 | ||
| KR1020070005812AKR101474413B1 (en) | 2006-01-23 | 2007-01-18 | Terminal and method for performing scheduled device management |
| KR10-2007-0005812 | 2007-01-18 | ||
| PCT/KR2007/000378WO2007083972A1 (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
| Publication Number | Publication Date |
|---|---|
| CN101371243A CN101371243A (en) | 2009-02-18 |
| CN101371243Btrue CN101371243B (en) | 2011-04-27 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800029582AExpired - Fee RelatedCN101371243B (en) | 2006-01-23 | 2007-01-22 | Execute scheduling device management |
| CN2007800028043AExpired - Fee RelatedCN101371235B (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
| CN2007800028823AExpired - Fee RelatedCN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management based on threshold value scheduling |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028043AExpired - Fee RelatedCN101371235B (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
| CN2007800028823AExpired - Fee RelatedCN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management based on threshold value scheduling |
| Country | Link |
|---|---|
| CN (3) | CN101371243B (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101888119B (en)* | 2010-05-28 | 2012-07-18 | 北京中恒博瑞数字电力科技有限公司 | Generation method of scheduling operating command ticket |
| CN104301179B (en)* | 2014-10-15 | 2017-12-22 | 东华大学 | Sensor data transmission system failure monitoring method based on Ethernet |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512382A (en)* | 2002-12-27 | 2004-07-14 | ������������ʽ���� | Equipment monitoring system, monitoring program, monitoring method and device |
| KR20050046932A (en)* | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3834452B2 (en)* | 1999-04-01 | 2006-10-18 | セイコーエプソン株式会社 | Device management system, management server, and computer-readable recording medium |
| FI116426B (en)* | 2003-05-02 | 2005-11-15 | Nokia Corp | Initiate device management between the management server and the client |
| CN1309211C (en)* | 2003-05-13 | 2007-04-04 | 中兴通讯股份有限公司 | Distributed central management method for special shaped network equipment in distributing network environment |
| CN1547120A (en)* | 2003-12-10 | 2004-11-17 | 沈阳东软软件股份有限公司 | Network monitoring management system |
| CN100370739C (en)* | 2003-12-26 | 2008-02-20 | 华为技术有限公司 | Application of distributed network management system and method |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512382A (en)* | 2002-12-27 | 2004-07-14 | ������������ʽ���� | Equipment monitoring system, monitoring program, monitoring method and device |
| KR20050046932A (en)* | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
| Title |
|---|
| JP特开2002-216279A 2002.08.02 |
| Publication number | Publication date |
|---|---|
| CN101371235B (en) | 2010-09-15 |
| CN101371236B (en) | 2012-05-23 |
| CN101371243A (en) | 2009-02-18 |
| CN101371236A (en) | 2009-02-18 |
| CN101371235A (en) | 2009-02-18 |
| Publication | Publication Date | Title |
|---|---|---|
| CN101375266B (en) | Device Management Scheduling Based on Trap Mechanism | |
| US20070192158A1 (en) | Performing scheduled device management | |
| CN111416736B (en) | Configuration management method and device of network equipment, computing equipment and storage medium | |
| US11894995B2 (en) | Data processing method and apparatus | |
| EP2001160A9 (en) | The method of device capability information negotiation, the method, system and device of synchronization | |
| CN101161013A (en) | Method for managing terminal equipment | |
| US20120102177A1 (en) | Terminal and method for performing device management scheduled based on threshold | |
| EP4027588A1 (en) | Yang model management method, apparatus and system, device, and storage medium | |
| KR20070077449A (en) | Device management method based on the terminal and the threshold-value in the terminal | |
| CN101540698B (en) | Event processing system and method | |
| CN101371243B (en) | Execute scheduling device management | |
| CN113170346B (en) | Methods and apparatus for control performance measurements | |
| US8001415B2 (en) | Program control method for network devices and network system | |
| CN100514915C (en) | Device management system and device management command scheduling method | |
| US7571429B2 (en) | System and method for error reporting | |
| KR101702583B1 (en) | A system for monitoring a network performance using xmpp and method thereof | |
| CN100550767C (en) | The kinetic controlling equation method of the management information bank of internet network TV service | |
| CN117093480A (en) | Method and device for optimizing extraction flow, computer equipment and readable storage medium | |
| Lee et al. | A design of dynamic network management system | |
| HK1106357B (en) | Device management system and device management command scheduling method thereof | |
| Ryu et al. | Web based management system of a remote mobile device using Device Management Protocol | |
| CN101371242A (en) | Methods of interacting with users and their terminals | |
| Shin et al. | Active network management system with automatic generation of network management program using triggers | |
| HK1106357A1 (en) | Device management system and device management command scheduling method thereof | |
| MX2008009282A (en) | Terminal and method for performing device management scheduled based on threshold |
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | Granted publication date:20110427 Termination date:20170122 | |
| CF01 | Termination of patent right due to non-payment of annual fee |