WO2014163280A1 - 무선 통신 시스템에서 서버의 단말의 리소스 요청 또는 단말의 리소스 제공을 위한 방법 및 이를 위한 장치 - Google Patents
무선 통신 시스템에서 서버의 단말의 리소스 요청 또는 단말의 리소스 제공을 위한 방법 및 이를 위한 장치 Download PDFInfo
- Publication number
- WO2014163280A1 WO2014163280A1 PCT/KR2013/011947 KR2013011947W WO2014163280A1 WO 2014163280 A1 WO2014163280 A1 WO 2014163280A1 KR 2013011947 W KR2013011947 W KR 2013011947W WO 2014163280 A1 WO2014163280 A1 WO 2014163280A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- instance
- node
- server
- data
- cache
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
Definitions
- the present invention relates to a method for providing a resource of a terminal or a resource of a terminal of a server in a wireless communication system and an apparatus therefor, and more particularly, to a resource request or providing method using a cache verifier.
- DM Device Management
- the device management technology is being developed as an international standard based on SynchML Data Synchronization, which is written by the SyncML Initiative (Synchronization Markup Language) Forum at 0pen Mobile Alliance (0MA), and is already being developed for other standardization organizations and operators worldwide. It is accepted as the standard of management skills.
- the 0MA device management technology is a standard that supports the most diverse functions compared to other device management technologies.
- the device management protocol standard the standard for the device management document presentation method, the standard for binding with the transport protocol, the device management tree And a standard for a device management node, a standard for a device description framework (DDF), a standard for notification, and the like.
- DDF device description framework
- This device management is a device management server (DMS) sends a command to the device for a Management Object (MO) existing inside the device, the device management client (DMC) of the device is the command This can be done by The DMC is mounted on the device and corresponds to an entity that receives and executes the command from the DMS.
- the M0 is logically connected to a management tree (or tree) existing within the device or a node of the tree. Therefore, the device management server may control the M0 or the tree or node associated with the M0 that is the target of the command through the command for M0.
- the M0 is generally present in the database of the device, and the device management server can direct the management command by accessing the M0 through the URI of the tree or node.
- the present invention proposes a resource request method of a terminal of a server, a resource providing method of the terminal, and an apparatus therefor in a wireless communication system.
- a method for processing a request for M0 data using a cache validator (CV) assigned to an MCKManagement Object) instance according to an embodiment of the present invention, wherein the method is performed by a terminal.
- the instance consists of a tree structure consisting of one or more nodes, wherein the M0 data includes the name of the node included in the M0 instance, the value of the node and the structure of the node, wherein the method comprises the M0 instance from a server.
- the method includes verifying the first CV. If the first CV is verified to be valid, a result indicating that the first CV is valid is returned. Transmitting to the server, if the first CV is found to be invalid, transmitting the requested specific M0 data to the server. And if the URI information indicates a root node of the M0 instance, transmitting the second CV for the M0 instance.
- the method may include updating a second CV for the M0 instance.
- the M0 instance may be cacheable.
- the first CV may be provided by a specific field included in the URI.
- the first CV may be determined to be valid.
- a method for requesting M0 data using a cache validator (CV) assigned to an MCKManagement Object) instance wherein the method is performed by a server and is performed by the server.
- the instance is composed of a tree structure consisting of one or more nodes, wherein the M0 data includes the name of the node included in the M0 instance, the value of the node and the structure of the node, wherein the method includes a specific M0 of the M0 instance.
- URI Uniform Resource Identifier
- the first CV is not included in the URI information. If the first CV is not included in RI information, receiving the requested specific M0 data from the terminal; And if the URI information indicates a root node of the M0 instance, receiving the second CV for the M0 instance.
- the first CV when the first CV is included in the URI information, the first CV is verified by the terminal, and when the first CV is validated, a result indicating that the first CV is valid is returned.
- Receiving from the terminal if the first CV is verified to be invalid, receiving the requested specific M0 data from the terminal; And if the URI information indicates a root node of the M0 instance, receiving a second CV for the M0 instance from the terminal.
- the second CV for the M0 instance may be updated.
- the M0 instance may be cacheable.
- the first CV may be provided by a specific field included in the URI.
- the first CV may be determined to be valid if no change occurs in the M0 instance.
- a terminal for processing a M0 data request using a cache validator (CV) f allocated to a M0 (Management Object) instance according to another embodiment of the present invention.
- the M0 instance is composed of a tree structure consisting of one or more nodes, and the M0 data includes a name of a node included in the M0 instance, a value of a node, and a structure of a node.
- radio frequency (RF) unit RF
- a processor configured to control the RF unit, wherein the processor includes Uniform Resource Identifier (URI) information identifying the specific M0 data for requesting specific M0 data of the M0 instance from a server.
- URI Uniform Resource Identifier
- the processor transmits the specific M0 data to the server, the URI If the information indicates a root node of the M0 instance, it may be configured to send a second CV for the M0 instance.
- a server for requesting M0 data using a cache validator (CV) assigned to an MCKManagement Object) instance wherein the M0 instance includes one or more nodes.
- the M0 data comprises a tree structure, the name of the node included in the M0 instance, the value of the node and the structure of the node, wherein the server comprises: a radio frequency (RF) unit; And a processor configured to control the RF unit, wherein the processor makes a request including Uniform Resource Identifier (URI) information identifying the specific M0 data for requesting specific M0 data of the M0 instance.
- RF radio frequency
- URI Uniform Resource Identifier
- the first CV for the M0 instance is configured to include the first CV in the URI information, and if the first CV is not included in the URI information, the processor requests the request.
- the processor When receiving specific M0 data from the terminal, and the URI information indicates the root node of the M0 instance, it may be configured to receive a second CV for the M0 instance.
- Figure 1 shows an HTTP web cache.
- M0 Management Object
- DM Device Management
- Figure 3 shows an example of allocation of the M0 instance-specific cache verifier in accordance with an embodiment of the present invention.
- FIG. 4 illustrates a resource request method according to an embodiment of the present invention.
- FIG. 5 illustrates a resource providing method according to an embodiment of the present invention.
- FIG. 6 shows a method that can be contrasted with an embodiment of the present invention.
- Figure 7 shows a block diagram of an apparatus for implementing embodiment (s) of the present invention.
- the device may be fixed or mobile, and various devices that transmit and receive user data and / or various control information by communicating with a server or a gateway belong to the device.
- the device is a terminal equipment (Terminal Equipment), MS (Mobile Station), MT (Mobile) Terminal), UKUser Terminal), SSCSubscribe Station), wireless device (wireless device), PDA (Personal Digital Assistant), wireless modem (wireless modem), handheld device (handheld device) and the like.
- a server and a gateway generally refer to a fixed station that communicates with a device, a gateway, and / or another server, and communicates with the device, gateway, and / or another server to provide various data and control information. Exchange it.
- the server or the gateway may be referred to as a server device or a gateway device, respectively.
- the device management refers to the management of other managed objects of the apparatus configuration and apparatus in view of the various regulatory authorities (Management authorities).
- Device management includes sequential updates of constantly persistent information in devices, retrieval of management information from devices, and processing of events and alarms generated by devices, but for setting initial configuration information in devices.
- Device Management includes, but is not restricted to setting initial conf igurat ion information in Devices, subsequent updates of persistent information in Devices, retrieval of management information from Devices and processing events and alarms generated by Devices.
- a management tree is an interface for a management server to interact with a DM client, for example by storing values in or retrieving values from the management tree and by manipulating the attributes of the management tree, for example as an attribute of the management tree.
- ACL access control list
- the interface by which the management server interacts with the client :, eg by storing and retrieving values from it and by manipulating the properties of it, for exam le the access control lists. May be referred to interchangeably with the DM tree.
- a management object is a subtree of a management tree that is intended to be a set of nodes (or even one node alone) that are related to each other in some way.
- a ./Devlnfo node and its child nodes may form a managed object.
- a Management Object is a subtree of the Management Tree which is intended to be a (possibly singleton) collection of Nodes which are related in some way.For example, the ./Devlnfo Nodes form a Management Object .A simple Management Object may consist of one single Node.)
- a DM server or DMS may be a conceptual software component in a device management infrastructure that follows the 0MA Device Management Enabler static conformance requirements specified for the DM server or the DMS. have.
- the DM server or the DMS may serve as an end-point of a DM client-server protocol and a DM server-server interface.
- An abstract software component in a de loyed Device Management infrastructure that conforms to the OMA Device Management Enabler static conformance requirements specified for DM Servers .It serves as an end-point of the DM Client—Server Protocols and DM Server-Server Interface).
- the DM server or the DMS may be provided mounted in an apparatus, a device, a computer, etc. having communication modules, processor modules, and the like, and thus may be implemented as one device.
- a DM client or DMC is a conceptual component in device implementation that follows the 0MA Device Management Enabler static conformance requirements specified for the DM Client or the DMC. It may be a software component.
- the DM client or the DMC may serve as an end point of a DM client and server protocol. (An abstract software component in a Device im lement at ion that conforms to the OMA Device Management Enabler stat ic conformance requirements specified for DM Clients. It serves as an end-point of the DM CI ient-Server Protocols.).
- the DM client or the DMC may be provided as mounted in a device that is the target of the DM including a communication module, processor modules, and the like, and thus may be implemented as one device.
- An ACL refers to a list of DM server identifiers and access rights associated with each DM server identifier for a particular node in the management tree (A list of identifiers and access rights associated with each identifier).
- a node is a single element in the management tree. There can be two types of nodes in the management tree: interior nodes and leaf nodes.
- the format attribute of a node provides information as to whether the node is a leaf node or an interior node.
- the Format property of a Node provides information about whether a Node is a leaf or an Interior Node.).
- An interior node may have child nodes, while an interior node may not have a value assigned to the node, that is, a node value.
- the Format property of an Interior Node is node.
- a leaf node may not have child nodes but may have node values instead.
- the Format property of a Leaf Node is not node.
- a persistent node is a node whose DDF attribute scope is set to permanent. If the node is not a permanent node, it is a dynamic node. A Node is permanent if the DDF property Scope is set to Permanent .If a Node is not permanent, it is dynamic .A permanent Node can never be deleted by the server.) [58] Dynamic Node
- a dynamic node is a node in which a DDF property scope is set to dynamic, or in which the DDF property scope is not specified (A Node is dynamic if the DDF property Scope is set to Dynamic, or if the Scope property is unspecified).
- the server identifier refers to the OMA DM internal name for the DM server.
- a DM Server is associated with an existing Server Identifier in a device through OMA DM account.
- All terminals managed by the DM (device management) 1.3 protocol have one DM tree starting with a root node, and the DM protocol is managed by the terminals by manipulating each node of the DM tree. Perform the command. For example, in order to install the downloaded software on the terminal, the user can install the software by executing a node called install that matches the software.
- Each node can represent simple information such as numbers, or it can represent complex data such as picture data or log data.
- a node can also represent a single command, such as run or download.
- Each node has a property that provides meta information about the node, one of which is the runtime attribute, which is used until the node is created and destroyed in the DM tree. Possible attributes. These runtime attributes include ACL, Format, Name, Size, Title, TSt am, Type, and VerNo.
- Access Control List is an essential function that both the terminal and the server must implement in the DM 1.3 protocol.
- ACL specifies DM commands that a specific DM server can execute on a specific node. Unless specified, DM commands cannot be executed. In other words, an ACL means a specific DM server is granted to a specific node.
- ACLs are assigned to the server identifier of the DM server, not URIs, IP addresses, or DM server certificates (cert if icate). This server identifier is used as an identifier to authenticate the DM server in the DM protocol.
- such an ACL may be provided as an ACL property and an ACL value assigned to the ACL property.
- the ACL value is ACL information (ACL). information) or information about an ACL may be referred to interchangeably.
- ACL ACL information
- information information about an ACL
- all nodes are defined to have ACL attributes, and all nodes with ACL attributes are defined to have either empty or non-empty ACL values.
- ACL has unique properties that differ from other run-time properties, and this unique representative property is ACL inheritance.
- ACL inheritance is the concept that when a node in the DM tree does not have an ACL value, the ACL value for that node is taken from the ACL value of the parent node. If the parent node also does not have an ACL value, the ACL is taken from the parent node's parent node. Since the DM protocol specifies that the root node, which is the top node of the DM tree, must have an ACL value, the ACL value is necessarily inherited. This ACL inheritance is not done for each DM command, but because it is performed for the entire ACL value, the ACL value must be empty, so that ACL inheritance occurs from the parent node. In other words, if the ACL value of a node specifies only the Add permission, the Get permission that is not specified is not inherited.
- Replace permission means permission to replace ACL values of all child nodes.
- the parent node of that node has the R ⁇ lace privilege, the ACL value for that node You have the right to replace it. To get the ACL of the node, the parent node must have Get permission. Likewise, if the node has Replace permission, it means that the value of that node can be replaced. To replace the ACL, the parent node must have Replace permission.
- the authority to replace the ACL value of the node may be controlled by the ACL value of the parent node. If you have Replace permission on an interior node, this means that you can replace the ACL values of all the child nodes, as well as the interior node. Thus, if the root node has Replace permission, it means that any node in the DM tree can have any permission. However, having the Replace permission on a parent node does not imply a specific permission such as Get on the child node, and the right such as Get must be specified directly on the child node.
- the ACL value must be modified before the command is executed, and the ACL value of all the nodes on the way to the node to be modified must be modified to finally modify the ACL value of the child node. This is inconvenient.
- the ACL allows the node to modify its ACL value without modifying the ACL value of the intermediate node.
- the created node When the DM server creates a new node through the Add command, the created node generally does not have an ACL value, so all permissions are inherited from the parent. However, if the created node is an interior node and the parent node does not have the R ⁇ lace privilege, it is necessary to have sufficient authority to manage the node by setting the ACL value at the same time.
- DMS1 and DMS2 are the server identifiers of the DM Server, and Get, Replace, Delete are the DM commands. Therefore, DMS1 can execute Get and Replace commands for the node, and DMS2 can execute Delete commands.
- an ACL value is a set of individual ACL entries, and each node's ACL value may include at least one ACL entry.
- DDF Device Description Framework
- DM 1.3 authentication is performed based on the ACL. DM authentication is done separately for each DM command. If the DM server sends multiple DM commands, the DM client (DMC) performs authentication before executing the individual commands, and only the authorized DM commands are executed.
- DMC DM client
- the DM tree refers to the set of M0 instances exposed by the DM client, which acts as an interface by the management server interacting with the client, for example the management server stores and retrieves specific values from the DM tree. It can retrieve the attributes of the DM tree.
- M0 data corresponds to information about the DM tree.
- the information may be for the entire DM tree or may be part of the DM tree (eg, a subtree in the M0 instance).
- the DM server requests M0 data using the ClientURI, and the M0 data consists of node name, node value and node structure.
- Caching is a general term for a technique for reducing unnecessary transfer of resources between a server and a client.
- the client stores previous voice answers from the server and reuses the stored when requesting the same resource.
- the cache verifier is a component used to verify the cache.
- Cache validation is the process of determining whether a resource cached at a resource requestor is up to date or not.
- freshness means that the resource has not changed since it was delivered to the resource requester.
- cache validators are the ETag and Last-Modified fields used in the web cache.
- M0 instances [86] The MO instance is the presence of a Management Object (M0) published by a DM Client. Instances of M0 share the same node definitions and behaviors, and can be represented as a collection of related nodes published by the DM client. Multiple instances of one M0 may exist in the DM tree.
- M0 Management Object
- the ClientURI identifies a specific node of the DM tree existing in the terminal.
- ClientURI may point to an interior node or a leaf node. Accordingly, ClientURI may be represented by an indicator or information indicating a specific node.
- HTTP is a widely used protocol for sending and receiving resources on the Web.
- resources are manipulated using HTTP commands such as GET, DELETE, PUT, and POST for the resource called URI.
- HTTP client must know the URI that refers to a picture file in order to obtain a picture file that exists on the Web, and if that URI is "http: //w.server, com / a.jpg" '' Will send the HTTP GET command to the URI, and the HTTP server will send the picture file to the HTTP client in response to the HTP GET command.
- Cache Validation is a process of checking whether a cache is valid or expired.
- a cache validator is called a cache validator.
- HTTP typically uses ETag and Last—Modi fied as cache validators.
- ETag is a type of identifier that an HTTP server gives to a particular version of a resource.
- an HTTP server sends a response to a resource request, it sends the resource indicated by the URI together with the ETag value assigned to the resource.
- the HTTP server changes the ETag value when the resource changes (when the version of the resource changes), and compares the ETag value sent by the HTTP client with the ETag value sent by the HTTP client during the cache verification process, so that the local copy of the HTTP client has the latest. It will determine if it is a version.
- the left table of FIG. 1 shows a web cache using ETag and the right table shows a web cache using Last-Modified.
- an HTTP client requests an image file resource of "a.jpg” through a URI of "http://www.server.com/a.jpg” (S101-a). .
- the HTTP server transmits an HTTP header called ETag together with the image file which is the requested resource (S102-a).
- This ETag header indicates the ETag value assigned to the current version of the image file resource.
- the HTTP client receives a response and stores the image file resource locally (local copy) and also stores the ETag value.
- the HTTP client When an HTTP client sends a request for the same URI, the HTTP client includes a stored ETag, and for this purpose, an HTTP header called If-None—Match is used (S103-a).
- the HTTP server receives this request and compares it to the ETag value for the current version of the resource represented by the UI. If the two values are the same, the ⁇ client informs the client that the resource has not been modified using a "304 Not Modified" response code ( S104-a).
- the HTTP client receives this response from the HTTP server, it confirms that the resource it is storing is the latest version, and uses the latest version resource without sending it back from the server.
- Last—Modified In addition to ETags, the most commonly used HTTP cache validator is Last—Modified.
- the basic behavior of Last-Modified is almost identical to ETag, as shown in the table on the right in FIG.
- Last-Modifier means the time when the resource was last changed. That is, when the HTTP server transmits a resource to the HTTP client, the HTTP server transmits the last changed time in the HTTP Last-Modified header (S102-b).
- HTTP clients store resources and Last-Modified values locally and then send requests to the same URI.
- the If-Modified-Since header includes the last modified time of the received resource (S103-b).
- the HTTP server will update the resource change time whenever the resource changes, and if the request for the same URI contains an If— Modified-Since header, then the time contained in the If-Modified-Since header and stored by itself It compares the last resource change time that it has, and if it thinks the resource has changed, it sends back the requested resource. If the resource has not been changed, transmit a "304 Not Modified" voice answer code (S104-b).
- the DM server may request the DM client to transmit the information stored in the terminal.
- this information is configured in the form of a DM tree and stored in the terminal and is commonly referred to as management object data (M0 Data).
- M0 Data may be the entire DM tree information or may be a value stored in one node.
- 2 illustrates a DM tree stored in a terminal in 0MA DM 2.0.
- 0MA DM 2.0 does not restrict the M0 instances in the terminal (that is, the set of M0 related nodes created in the terminal) to be organized in a hierarchical tree structure, where ClientURI, which refers to the node of the DM tree, is based on the M0 instance This is because it specifies the address of.
- a request for a DM server to obtain M0 data is generally implemented through a GET command.
- the DM server delivers the ClientURI as a parameter of the GET command in the process of delivering the GET command to the DM Client, and ClientURI refers to a specific node of the DM tree.
- Package # 2 is used by the DM server to deliver a command to a DM client, and Package # 2 may include a plurality of DM commands. The following is an example of Package # 2 containing two GET commands.
- the first GET command requests the Devlnfo Management Object stored in the terminal, and the second GET command requests the IDs of all the software components installed in the terminal. do.
- CMD CMD
- ⁇ In the above example, it can be seen that two GET commands are included.
- the element following the GET command is ClientURI. That is, the first GET command requests MO data for the entire Devlnfo Management Object called "oma: mo: oma ⁇ dm ⁇ devinfo: 1.0 //", and the second GET command is "ur n: oma: mo: oma-s como: 1.0 // 1 nvent ory / Dep 1 oyed / * / 1 D "]-Request transmission of all installed software component identifiers (IDs).
- DM Client When this request is received, it sends the requested M0 Data to the DM server through the following vocal reply message.
- the response code for each command is transmitted using Package # 3.
- the DM client transmits the following HTTP message.
- OMADM-DevID IMEI: 493005100592800
- the DM client's response is made using HTTP multipart
- the first encapsulation contains Package # 3
- the second encapsulation is the answer to the first GET command
- three The first encapsulation is the answer to the second GET command.
- the DM server requests MOData to the DM client in this way, and the DM client sends the requested M0 Data to the DM server.
- inefficiency may occur. That is, the time required for the transmission of the M0 Data is long, the answer time is high, and network resources may be wasted due to unnecessary data transmission.
- the HTTP web cache described above may be applied to OMA DM 2.0 as it is.
- the DM client can assign and manage cache verifiers in all nodes of the DM tree, just as the cache verifiers are allocated and managed for each resource.
- the DM server requests the DM client a resource called ClientURI with a DM GET command, and if there is a cache verifier, additionally delivers it and receives a status code indicating that the resource has not changed unless the requested resource has changed.
- ClientURI resource
- the following shows a GET command for requesting the FwV node (storing device firmware version information) of Devlnfo M0.
- the first GET command to request an FwV node (resource).
- the DM server will not have a local cache for this as well as a cache verifier for it, so the GET command is sent as follows without the cache verifier.
- the DM server sends the requested resource as shown below.
- a DM client sends a resource, it can send a cache verifier for the resource, which is passed through the "CV" key below.
- ETag as the cache validator.
- the DM server may store the firmware version of the terminal "android4.0.4" and the cache verifier "686897696a7c876b7e" for this resource.
- the DM server requests the same resource later, the resource can be requested using the following GET command.
- the cache validator is "686897696a7c876b7e" which is entered as the second parameter of the GET instruction.
- the DM client When the DM client receives the Package # 2, the DM client performs a Cache Validation, and if the cache is valid, the DM client transmits a status code 304 indicating "Not Modified" to the DM server. In this case, the DM server knows that the local cache is still valid and can use "android4.0.4" stored in the local cache. Below is Package # 3 which says "304 Not Modified”.
- OMADM-DevID IMEI: 493005100592800
- OMADM-DevID IMEI: 493005100592800
- the DM client In the case of applying the HTTP web cache directly to OMA DM 2.0, the DM client must assign a cache validator to all resources, resulting in heavy management of multiple cache validators and a heavy protocol.
- a cache validator when a cache validator is assigned to an interior node, there is a problem of the range of resources to be validated by the corresponding cache verifier. That is, in the case of a cache validator assigned to an interior node, whether or not the cache validator should be updated when its child node or descendant node is updated is a problem.
- ClientURI (urn: oma: mo: oma-scomo: 1.0 // Invent ory), which refers to multiple nodes, is an example of" DM 2.0-based resource acquisition ". Problems occur when / Dep 1 oyed / * / ID ”) is used in the GET command. That is, because ClientURI refers to multiple nodes, it is impossible to select which cache validator to send in the GET command. Moreover, the DM server cannot know how many nodes are designated as ClientURI and thus cannot select the cache validator.
- FIG 3 shows an example of a cache verifier allocation according to an embodiment of the present invention.
- a cache validator is an entity that can give validity information about a local cache held by a server.
- the cache verifier provides freshness information for the local cache.
- Representative examples of cache validators include last-modified or ETag.
- the cache verifier is assigned to only the M0 instance as shown in FIG. However, not all M0 instances in the DM tree are assigned a cache validator, and a cache validator can be assigned only to a required M0 instance by selecting the M0 instance.
- 3 is a diagram illustrating the allocation of a cache validator to two M0 instances (FUM0 instance, SC0M0 instance) among three M0 instances existing in the DM tree of the UE.
- the M0 instance to which the cache verifier is allocated is called a cacheable MO instance.
- a cacheable M0 instance In order to use the cache, a cacheable M0 instance must first be selected by a terminal (or DM client) or a DM server, and a cache verifier must be assigned and managed for the selected M0 instance. For each cacheable M0 instance, the DM client must assign a cache verifier and assign it whenever the data in the M0 instance changes (node value changes, new node additions and deletions, node name changes, etc.). The updated cache validator.
- the cache verifier is assigned only to the M0 instance, the resource request / provision method using the cache can be efficiently performed.
- the cache validation process is a process of checking whether a cache or cache copy is valid or invalid. Because a cache validator is assigned to a cacheable M0 instance, cache validation returns success (“success” or “true") if no data in the cacheable M0 instance has changed. If it does change, it should return failure ("false”). For example, when the cache verifier is an ETag, the cache verifier may be performed by comparing the ETag value transmitted by the DM server with the ETag value of the corresponding M0 instance managed by the terminal. The terminal returns "success” if the ETag value transmitted from the DM server and the ETag 3 ⁇ 4): that it manages are the same, and "failure” if the value is different.
- the cache verifier is assigned to the M0 instance, the cache verifier can be used to send GET commands to all nodes in the M0 instance.
- the DM server may deliver a cache verifier for the M0 instance.
- the DM client verifies that the M0 instance has not been changed through the cache validator, and if the M0 instance has not been changed, the specific leaf node would not have been changed, and therefore, transmits a "304 Not Modified" code to the DM server.
- the DM server receiving "304 Not Modified” may refer to locally cached data.
- the method of delivering the cache verifier to the DM client may vary.
- the cv field may be included in the ClientURI.
- Using the cv field simplifies resource requests because the cache validator can be integrated into ClientURI and not passed as a separate parameter.
- ClientURI points to a specific node, so the cv field will pass the cache validator for the M0 instance that contains that particular node.
- This ClientURI refers to the "FwV" node of Devlnfo M0. Since the node is included in the Devlnfo M0 instance, the value cache verifier "686897696a7c876b7e '' passed in as the cv field becomes the cache verifier for this Devlnfo M0 instance.
- FIG. 4 illustrates an example of a resource request using a cache verifier allocated to an M0 instance according to an embodiment of the present invention.
- the DM server may determine to request MO Data (resource) referred to as ClientURI (S401).
- MO Data resource
- S401 ClientURI
- a GET command can be used for this request.
- the DM server may send a DM command by including the cv field in the ClientURI (S403).
- the cv field carries a cache verifier for the corresponding M0 instance. Since the cache verifier can use the command to obtain the resource, it can use the DM GET / HPUT / HPOST command.
- the DM server may transmit a resource request command to the DM client without the cv field (S403).
- the DM client (terminal) performs processing according to the method illustrated in FIG.
- Figure 5 shows an example of the response or processing of the resource request using the cache verifier assigned to the M0 instance in accordance with an embodiment of the present invention.
- the DM client may receive a DM command for acquiring a resource (MO data) from the DM server (S501).
- the DM command requesting the resource is one of GET / HPUT / HPOST, and the DM command carries a parameter called ClientURI.
- This resource acquisition command may be interpreted as a command for requesting MO data for the node indicated by the ClientURI.
- the DM client may determine whether the ClientURI of the DM command includes a cv field (S502). If the ClientURI of the DM command includes a cv field, the DM client performs a cache verification procedure (S503). In the cache verification procedure, if the MO data corresponding to the CV provided by the cv field is not changed in the terminal, it should return "success", and if any part of the MOData has changed, it should return "failure". Taking ETag as an example, the cache verification procedure is such that the DM client has a CV (hereinafter referred to as “first CV”) provided by the cv field stored or present in the DM client.
- first CV hereinafter referred to as “first CV”
- This cache verification procedure may vary depending on the type of cache verifier.
- first CV is a CV stored in the DM server
- second CV is a CV stored in the DM client (ie, a terminal).
- the first CV is derived from the second CV (because, the CV for a specific M0 instance, that is, a set of M0 related nodes is allocated by the DM terminal, and as described below, a DM server that does not have a CV may request cv when requesting a specific resource).
- the first CV is received from the DM terminal by not including the field in the ClientURI for the request), and the CVs stored by each of the DM server and the DM terminal are respectively referred to as 1CV and 2CV for convenience of description. It can be referred to.
- the cache validation process is when returns "success” (for Etag cache verifying party, when the same claim 1CV and the second 2CV “success”:)
- the DM client "304 Not Modified” is transmitted to the DM server, and the requested MOData is not transmitted to the DM server.
- the DM server receiving this answer uses or references a local cache.
- the DM client may transmit the M0 data referred to by the ClientURI to the DM server (S505).
- the cache verification procedure is "Failed", that is, cv (first CV) of the corresponding MOData that the DM server has, the cv (second CV) of the corresponding M0 data managed by the DM client.
- the DM client may transmit the M0 Data referred to by the ClientURI to the DM server (S505).
- the DM client sends the resource (ie, MOData) to the DM server.
- the resource ie, MOData
- the cv stored by the DM server and the cv managed by the DM client are different, the cv managed by the DM client together with the corresponding resource is transferred to the DM server. send,
- the DM client may determine whether the DM command, more specifically, ClientURI refers to the root node of the cacheable M0 instance (S506). That is, the DM client may determine whether the M0 instance including the node indicated by the ClientURI is a cacheable M0 instance and whether the node referred to as ClientURI is the root node of the cacheable M0 instance.
- the DM client may additionally transmit a cache verifier for the M0 instance to the DM server (S507). ).
- the DM client's answering process ends here.
- the DM server stores the cache verifier and can be used when requesting MO data later.
- the DM client does not additionally transmit the cache verifier to the DM server (S508). ).
- the DM client may transmit a cache verifier to the DM server in S507.
- the cache verifier is delivered with MOData, and forwards to the DM server if ClientURI refers to the root node of the cacheable M0 instance. If the ClientURI does not refer to the root node of the cacheable M0 instance, then the cache verifier shall not be passed.
- the cache validator gives the validity information for the entire M0 instance. When only a part of the M0 instance is received by the DM server, a problem occurs in the validation of the DM client later.
- the DM client may request the requested resource.
- the changed resource when sending to the DM server If the changed resource is not the resource requested by the DM server, it is not transmitted to the DM server.), If the second CV is reflected to the DM server, the DM server is changed in the terminal but cannot be obtained.
- the acquisition opportunities for other resource (s) other than resources are lost, which means a loss of functionality of the CV.
- FIG. 6 illustrates a case in which the DM server includes both a request for a root node of a cacheable M0 instance and a request for a resource other than the root node to the DM client.
- the DM server requests a M0 instance from the DM client having ClientURI "moid: 1.1" as the MO ID (S601).
- ClientURI "moid: 1.1 //" refers to the root node of the corresponding M0 instance.
- the M0 instance owned by the terminal is represented together in the upper right of FIG. 6.
- the DM client transmits the entire data of the M0 instance requested by the DM server, and transfers the cache verifier "CV1" allocated to the M0 instance to the DM server (S602).
- the DM client updates the c node such as renaming the c node.
- the cache validator is updated to "CV2" because the information of the M0 instance (that is, the information about the c node) is changed (S603).
- the DM client may perform a cache verification procedure based on the received CV1 (S605). That is, the DM client can determine whether the "CV1" is valid. In S603, the DM client has updated the information of the M0 instance and accordingly updated the cache verifier to CV2. Accordingly, the DM client determines that the cache validation fails because the "CV1" received from the DM server in S604 and the cache verifier "CV2" which it has have differed. ETag).
- the DM client may transmit the requested information (node b and its subnodes d and e) and the cache verifier "CV2" which it has in S604 to the DM server (S606).
- the DM client uses the cache verifier to the DM server even though the request from the DM server is not a request for the root node of the M0 instance. send.
- the DM server may store the cache verifier "CV2" (that is, update from the existing "CV1” to "CV2").
- the DM client may perform a cache verification procedure for verifying a cache verifier from the DM server (S608). Since the cache verifier of the DM client is also "CV2", the DM client determines that the cache verifier "CV2" from the DM server is valid and determines the cache verification procedure as "success”. Since the cache verification procedure is successful, the DM client transmits a male answer code of "304 Not Modified" to the DM server (S609).
- the DM server receives a "304 Not Modified" response in S609 even though the DM server does not have the latest information of the updated c-node. Misunderstanding that you have a. This is because the DM client delivers the cache verifier "CV2" to the DM server in S606 even though the request from the DM server does not target the M0 instance root node. Since the delivered "CV2" is eventually used when the DM server requests information about the node c in S607, the DM client incorrectly determines that the DM server has the latest information about the node c. Does not transmit to the DM server. To prevent this problem in advance, the request of S607 may include a cache validator for one node. But in the end, this is similar to the HTTP web caching method, where there is a cache validator for each subtree, which complicates the mechanism for managing cache validators and requesting / replying resources.
- the processing load due to the allocation of the cache verifier may be reduced, and the cache using the cache verifier may be used.
- the verification procedure can be performed simply and efficiently. That is, an embodiment of the present invention allocates the cache verifier only to the M0 instance itself, unlike in the prior art which allocates the cache verifier (CV) for each of all resources, and to which node to assign the CV. Solve complex problems.
- the CV (first CV) from the DM server is always checked to the DM terminal even if it is verified to be invalid.
- the UE checks which resource is the requested resource, and the DM terminal may transmit the second CV to the DM server only when the resource is previously specified. .
- the DM server sends the requested resource as shown below.
- the DM client can send a cache verifier for the resource when sending the resource, which carries the cache verifier through the "CV" key below.
- ETag as the cache validator.
- OMADM-DevID IMEI: 93005100592800
- the DM server may store the firmware version ⁇ android4.0.4 '' of the terminal and the cache verifier "686897696a7c876b7e" for the resource.
- the cache verifier is "686897696a7c876b7e" passed in the cv field of the ClientURI.
- the DM server After performing the validation), if the cache is valid, the DM server sends a status code 304 indicating "Not Modified". In this case, the DM server knows that the local cache is still valid and can use "android4.0.4" stored in the local cache. Below is Package # 3, which knows "304 Not Modified”.
- OMADM-DevID IMEI: 4930.05100592800
- FIG. 7 shows a block diagram of an apparatus configured to perform embodiment (s) of the present invention.
- the transmitter 10 and the receiver 20 are R radio frequency units 13 and 23 capable of transmitting or receiving radio signals carrying information and / or data, signals, messages, and the like, in a wireless communication system.
- Memory (12, 22) for storing various kinds of information related to communication.
- Memo operatively connected to components such as the RF unit 13, 23 and the memory 12, 22, and controls the components so that the device performs at least one of the embodiments of the invention described above.
- Processor 12, 22 and / or processor 11, 21 configured to control RF units 13, 23, respectively.
- the memory 12 and 22 may store a program for processing and controlling the processors 11 and 21 and may temporarily store input / output information.
- Memory 12, 22 can be utilized as a buffer.
- the processor (11, 21) typically controls the overall operation of the various models in the transmitter or receiver.
- the processors 11 and 21 may perform various control functions for carrying out the present invention.
- the processors 11 and 21 may also be blurred by a controller, a microcontroller, a microprocessor, a microcomputer, or the like.
- the processors 11 and 21 may be implemented by hardware or firmware, software, or a combination thereof. Hardware In the case of implementing the present invention using a language, it is configured to carry out the present invention.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gate devices
- pipware or software may be configured to include modules, procedures, or functions for performing the functions or operations of the present invention, and the present invention may be performed.
- Firmware or software configured to be capable of doing so may be provided in the processors 11 and 21 or stored in the memories 12 and 22 to be driven by the processors 11 and 21.
- the terminal, the DM client, the DM server, etc. may operate as the transmitting device 10 or the receiving device 20, respectively.
- the matters described in the various embodiments of the present invention described above with reference to the drawings may be independently applied or two.
- the above embodiments may be implemented to be applied at the same time.
- the present invention can be used in a wireless communication device such as a terminal, a base station, a server, and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/774,608 US10084748B2 (en) | 2013-04-04 | 2013-12-20 | Method and apparatus for requesting or providing resource by terminal of server in wireless communication system |
CN201380075406.XA CN105103505B (zh) | 2013-04-04 | 2013-12-20 | 在无线通信系统中由服务器的终端请求或提供资源的方法和装置 |
JP2016506220A JP6276380B2 (ja) | 2013-04-04 | 2013-12-20 | 無線通信システムにおけるサーバーの端末のリソース要請又は端末のリソース提供のための方法及びこのための装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361808586P | 2013-04-04 | 2013-04-04 | |
US61/808,586 | 2013-04-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014163280A1 true WO2014163280A1 (ko) | 2014-10-09 |
Family
ID=51658534
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2013/011947 WO2014163280A1 (ko) | 2013-04-04 | 2013-12-20 | 무선 통신 시스템에서 서버의 단말의 리소스 요청 또는 단말의 리소스 제공을 위한 방법 및 이를 위한 장치 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10084748B2 (ko) |
JP (1) | JP6276380B2 (ko) |
CN (1) | CN105103505B (ko) |
WO (1) | WO2014163280A1 (ko) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230031114A1 (en) * | 2021-07-27 | 2023-02-02 | Synchrony Bank | Unique device identification system |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111090514B (zh) * | 2018-10-24 | 2023-06-20 | 阿里巴巴集团控股有限公司 | 一种分配计算能力的方法及系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050010552A1 (en) * | 2003-07-11 | 2005-01-13 | Nokia Corporation | Specifying nodes in device management system |
US20060015626A1 (en) * | 2004-07-01 | 2006-01-19 | Mika Hallamaa | Device management system |
WO2012124999A2 (ko) * | 2011-03-17 | 2012-09-20 | 엘지전자 주식회사 | 단말의 리소스 제공 방법 및 서버의 리소스 획득 방법 |
US20130031262A1 (en) * | 2011-07-27 | 2013-01-31 | Htc Corporation | Methods for handling multiple device management (dm) server addresses in a dm account management object (mo) |
US20130078984A1 (en) * | 2007-11-15 | 2013-03-28 | Huawei Technologies Co., Ltd. | Method and device for creating management object instance in management tree of terminal device |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8701010B2 (en) * | 2007-03-12 | 2014-04-15 | Citrix Systems, Inc. | Systems and methods of using the refresh button to determine freshness policy |
EP2393238A1 (en) * | 2010-06-01 | 2011-12-07 | HTC Corporation | Communication apparatus and method thereof |
-
2013
- 2013-12-20 CN CN201380075406.XA patent/CN105103505B/zh not_active Expired - Fee Related
- 2013-12-20 US US14/774,608 patent/US10084748B2/en active Active
- 2013-12-20 JP JP2016506220A patent/JP6276380B2/ja active Active
- 2013-12-20 WO PCT/KR2013/011947 patent/WO2014163280A1/ko active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050010552A1 (en) * | 2003-07-11 | 2005-01-13 | Nokia Corporation | Specifying nodes in device management system |
US20060015626A1 (en) * | 2004-07-01 | 2006-01-19 | Mika Hallamaa | Device management system |
US20130078984A1 (en) * | 2007-11-15 | 2013-03-28 | Huawei Technologies Co., Ltd. | Method and device for creating management object instance in management tree of terminal device |
WO2012124999A2 (ko) * | 2011-03-17 | 2012-09-20 | 엘지전자 주식회사 | 단말의 리소스 제공 방법 및 서버의 리소스 획득 방법 |
US20130031262A1 (en) * | 2011-07-27 | 2013-01-31 | Htc Corporation | Methods for handling multiple device management (dm) server addresses in a dm account management object (mo) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230031114A1 (en) * | 2021-07-27 | 2023-02-02 | Synchrony Bank | Unique device identification system |
Also Published As
Publication number | Publication date |
---|---|
CN105103505A (zh) | 2015-11-25 |
CN105103505B (zh) | 2018-02-27 |
US10084748B2 (en) | 2018-09-25 |
US20160036776A1 (en) | 2016-02-04 |
JP2016525728A (ja) | 2016-08-25 |
JP6276380B2 (ja) | 2018-02-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9615346B2 (en) | Method and apparatus for notifying information change in wireless communication system | |
US10506432B2 (en) | Method and apparatus for authenticating access authority for specific resource in wireless communication system | |
US9769801B2 (en) | Method and apparatus for updating information regarding specific resource in wireless communication system | |
US9900727B2 (en) | Method and apparatus for controlling access in wireless communication system | |
GB2559835A (en) | Systems and methods for providing access to a data file stored at a data storage system | |
US20150195338A1 (en) | File fetch from a remote client device | |
CN108289098B (zh) | 分布式文件系统的权限管理方法和装置、服务器、介质 | |
CN110673881B (zh) | 微服务集群的配置管理方法、装置和计算机设备 | |
US8117293B1 (en) | Method of receiving, storing, and providing device management parameters and firmware updates to application programs within a mobile device | |
US9438603B2 (en) | Method for managing access right of terminal to resource by server in wireless communication system, and device for same | |
CN112688983A (zh) | 代理权限管理装置、终端设备及存储介质 | |
US20140040973A1 (en) | Method for controlling initial access rights to open mobile alliance device management servers | |
WO2014163280A1 (ko) | 무선 통신 시스템에서 서버의 단말의 리소스 요청 또는 단말의 리소스 제공을 위한 방법 및 이를 위한 장치 | |
EP2874069A1 (en) | Method and apparatus for managing personal information in communication system | |
JP2015118459A (ja) | 画像形成装置、情報端末、サーバ装置、データ処理システム、画像形成装置の通信方法、情報端末の通信方法、サーバ装置の通信方法、及びプログラム | |
US20230291577A1 (en) | Apparatus and method for managing data certificates in an icn network | |
JP5658516B2 (ja) | アクセス権管理システムおよび方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201380075406.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13881331 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14774608 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2016506220 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13881331 Country of ref document: EP Kind code of ref document: A1 |