WO2016090933A1 - 应用通告资源的创建方法及装置 - Google Patents

应用通告资源的创建方法及装置 Download PDF

Info

Publication number
WO2016090933A1
WO2016090933A1 PCT/CN2015/086051 CN2015086051W WO2016090933A1 WO 2016090933 A1 WO2016090933 A1 WO 2016090933A1 CN 2015086051 W CN2015086051 W CN 2015086051W WO 2016090933 A1 WO2016090933 A1 WO 2016090933A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
cse
registration
created
remote
Prior art date
Application number
PCT/CN2015/086051
Other languages
English (en)
French (fr)
Inventor
吴昊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US15/534,650 priority Critical patent/US20180270190A1/en
Priority to EP15868485.2A priority patent/EP3232693B1/en
Priority to KR1020177018391A priority patent/KR20170092646A/ko
Publication of WO2016090933A1 publication Critical patent/WO2016090933A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4541—Directories for service discovery
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/803—Application aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and an apparatus for creating an application advertisement resource.
  • the machine-to-machine (M2M) communication network consists of various M2M nodes and bearer networks.
  • the M2M nodes can communicate with each other through the bearer network.
  • One M2M node includes at least one application entity (AE) or one public service entity (CSE).
  • An application entity is a logical unit that performs an actual M2M application
  • a public service entity is a logical unit that manages and services an application.
  • FIG. 1 is a schematic diagram of an M2M system architecture according to the related art.
  • the application node is the end execution node, such as: smart meter, temperature measurement and control sensor, fire alarm, smart home appliance;
  • the intermediate node is the middleware connecting the end execution node to the network side server.
  • gateway the base node is the server on the network side.
  • the application entity needs to register with the public service entity on the intermediate node to join the M2M network, thereby serving as an application node of the M2M system.
  • the CSE on the intermediate node is called the registration CSE or the local CSE of the AE
  • the CSE on the base node is called the remote CSE of the AE.
  • the application entity related resources on the application node need to be registered to the public service entity on the application node, and do not need to be registered to the public service entity of the intermediate node and the public service entity of the base node.
  • the intermediate node forwards the query request to each application node, which not only consumes a large amount of Network resources also take a long time.
  • the resource advertisement is specifically used, and the advertisement resource corresponding to the original resource on the application node is created on the intermediate node, and the notification resource has the same as the original resource.
  • the tag is searched and has a link to the original resource, so that the application on the intermediate node can easily search for the required resource and access the original resource according to the link.
  • the original resource will create an attribute "advertised to" to save the address information of the successfully created announcement resource.
  • the advertised resources still maintain the same structure as the original resources, for example
  • resource ⁇ ae> has a sub-resource ⁇ container>
  • the resource ⁇ containerAnnc> on the remote CSE (this is the advertised resource corresponding to the original resource ⁇ container>) should be stored in the resource.
  • ⁇ aeAnnc> This is an implementation in an ideal state, in other words, the premise is that ⁇ ae> is considered to be first notified.
  • an application entity is likely to only advertise the ⁇ container> resource whose data is generated, and does not want to advertise its own information. This will cause ⁇ container> to not find the original definition on the remote CSE.
  • the parent resource eventually causes the notification to fail.
  • each CSE has a total root directory ⁇ CSEBase>, and all resources managed by the CSE are created in this root directory.
  • CSEBase> the total root directory
  • all resources managed by the CSE are created in this root directory.
  • CSE1 creates resource ⁇ ae1> for AE1 in the root directory ⁇ CSE1Base>;
  • CSE1 is registered on CSE2, and after registration is successful, CSE2 creates a resource ⁇ remoteCSE1> for CSE1;
  • CSE2 is registered on CSE3, and after registration is successful, CSE3 creates a resource ⁇ remoteCSE2> for CSE2;
  • CSE3 can create an advertisement resource ⁇ remoteCSE1Annc> for CSE1.
  • the advertisement resource can exist in the following two ways:
  • Method 1 Create directly under the root directory ⁇ CSE3Base> of CSE3;
  • AE1 can also request CSE1 to advertise it to CSE3, and AE1's announcement resource is created under ⁇ remoteCSE1Annc>.
  • the resource advertisement in the related art needs to be limited by whether the parent resource is advertised, and lacks flexibility.
  • the embodiments of the present invention provide a method and an apparatus for creating an application advertisement resource, so as to at least solve the problem that the resource advertisement in the related art needs to be restricted by the parent resource, and the flexibility is lacking.
  • a method for creating an application advertisement resource is provided.
  • the method for creating an application advertisement resource includes: the registration CSE receives the request message from the sender, where the request message carries the resource to be advertised and the advertisement target, and the notification target is the resource to be advertised indicated by the sender.
  • the identity of the remote CSE advertised; the registration CSE indicates to the remote CSE the location of the resource to be created according to the request message.
  • the registration CSE indicates the location of the to-be-created resource to the remote CSE according to the request message, and the registration CSE determines the location of the resource to be created, wherein the determination condition for determining the location of the resource to be created includes one of the following: registering the CSE and the remote CSE.
  • the registration CSE carries the determined location of the to-be-created resource in the create resource request message, and sends the create resource request message to the remote CSE.
  • the registration CSE determines the location of the resource to be created, including: the registration CSE determines that there is a registration relationship between itself and the remote CSE; and the registration CSE sets the location of the resource to be created to the address information of the resource created when registering on the remote CSE.
  • the registration CSE determines the location of the resource to be created, including: the registration CSE determines that there is no registration relationship between the self and the remote CSE, and does not include the advertisement to the attribute in the root directory of the resource; the registration CSE sets the location of the resource to be created to the remote location.
  • the address information of the root directory resource on the CSE is not limited
  • the registration CSE determines the location of the resource to be created, including: the registration CSE determines that there is no registration relationship between the self and the remote CSE, and the advertised to attribute in the root directory of the self resource does not include the address information corresponding to the remote CSE.
  • the registration CSE sets the location of the resource to be created to the address information of the root directory resource on the remote CSE.
  • the registration CSE determines the location of the resource to be created, including: the registration CSE determines that there is no registration relationship between the self and the remote CSE, and includes an advertisement to the attribute in the root directory of the resource, and the notification includes the address information corresponding to the remote CSE in the attribute; The registration CSE sets the location of the resource to be created to the address information of the advertisement resource created when it is advertised to the remote CSE.
  • the method further includes: the registration CSE also carries the original resource address information in the create resource request message, and sends the create resource request message to the remote CSE, where the original resource address information is used to indicate the original resource to be advertised.
  • the remote CSE checks whether there is a resource with the same value of the original resource link and the original resource address information carried in the resource request message; if so, the remote CSE The registration CSE sends a create resource response message, wherein the create resource response message is used to indicate that the resource to be created already exists; if not, the remote CSE creates a resource according to the location of the resource to be created indicated in the create resource request message.
  • an apparatus for creating an advertisement resource is provided.
  • the device for creating an application advertisement resource includes: a receiving module, configured to receive a request message from a sender, where the request message carries a resource to be advertised and an advertisement target, and the notification target is to be notified by the sender.
  • the resource needs to be advertised to the identity of the remote CSE; the indication module is configured to indicate to the remote CSE the location of the resource to be created according to the request message.
  • the indication module comprises: a determining unit, configured to determine a location of the resource to be created, wherein the determining condition for determining the location of the resource to be created comprises one of: registering whether there is a registration relationship between the CSE and the remote CSE, registering the CSE with Whether there is a registration relationship between the remote CSEs and whether the resource root directory of the registered CSE contains an advertisement to the attribute, whether there is a registration relationship between the registered CSE and the remote CSE, whether the attribute root directory of the registered CSE contains the advertisement to the attribute, and the advertisement to the attribute.
  • the sending unit is configured to carry the determined location of the to-be-created resource in the create resource request message, and send the create resource request message to the remote CSE.
  • the determining unit comprises: a first determining subunit, configured to determine that there is a registration relationship between itself and the remote CSE; the first setting subunit is set to set the location of the resource to be created to be created when registering on the remote CSE The address information of the resource.
  • the determining unit comprises: a second determining subunit, configured to determine that there is no registration relationship between itself and the remote CSE, and does not include an advertisement to the attribute in the root directory of the resource; the second setting subunit is set to be to be created The location of the resource is set to the address information of the root directory resource on the remote CSE.
  • the determining unit comprises: a third determining subunit, configured to determine that there is no registration relationship between the self and the remote CSE, the advertised to attribute in the root directory of the resource, and the advertised to the attribute does not include the address information corresponding to the remote CSE
  • the third setting subunit is set to set the location of the resource to be created as the address information of the root directory resource on the remote CSE.
  • the determining unit comprises: a fourth determining subunit, configured to determine that there is no registration relationship between the self and the remote CSE, the affiliation to the attribute in the root directory of the self resource, and the advertised address information including the address information corresponding to the remote CSE;
  • the fourth setting subunit is configured to set the location of the to-be-created resource to the address information of the advertisement resource created when the advertisement is advertised to the remote CSE.
  • the registration CSE is used to receive the request message from the sending end, where the request message carries the resource to be advertised and the advertised target, and the advertised target is the identifier of the remote CSE to which the advertised resource indicated by the sending end needs to be advertised.
  • the registration CSE indicates the location of the resource to be created to the remote CSE according to the request message, and solves the problem that the resource advertisement in the related art needs to be notified by the parent resource, and lacks flexibility, thereby ensuring the flexibility of the notification.
  • FIG. 1 is a schematic diagram of an architecture of an M2M system according to the related art
  • FIG. 2 is a schematic diagram of a resource notification process according to the related art
  • FIG. 3 is a flowchart of a method for creating an application advertisement resource according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of an apparatus for creating an advertisement resource according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of an apparatus for creating an advertisement resource according to a preferred embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for creating an application advertisement resource according to an embodiment of the present invention. As shown in FIG. 3, the method may include the following processing steps:
  • Step S302 The registration CSE receives the request message from the sending end, where the request message carries the resource to be advertised and the advertised target, and the advertised target is the identifier of the remote CSE to which the resource to be advertised indicated by the sending end needs to be advertised;
  • Step S304 The registration CSE indicates the location of the resource to be created to the remote CSE according to the request message.
  • the resource advertisement in the related art needs to be limited by whether the parent resource is advertised, and lacks flexibility.
  • the method shown in FIG. 3 is used to receive the request message from the sending end by the registration CSE, and according to the identifier of the remote CSE to be advertised, the resource to be advertised, which is indicated by the sending end of the request message, indicates to the remote CSE that the request is to be created.
  • the location of the resource thereby solving the problem that the resource notification in the related technology needs to be notified by the parent resource, and the lack of flexibility, thereby ensuring the flexibility of the notification.
  • the registration CSE indicates to the remote CSE that the location of the resource to be created according to the request message may include the following operations:
  • Step S1 The registration CSE determines the location of the resource to be created, wherein the determination condition for determining the location of the resource to be created may include one of the following:
  • Condition 1 Whether there is a registration relationship between the registered CSE and the remote CSE;
  • Condition 2 Whether there is a registration relationship between the registered CSE and the remote CSE;
  • Condition 3 Whether the CSE resource root directory contains the advertisement to the attribute, whether there is a registration relationship between the registered CSE and the remote CSE, whether the CSE resource root directory contains the advertisement to the attribute, and whether the advertisement to the attribute contains the remote CSE. Corresponding address information;
  • Step S2 The registration CSE carries the determined location of the to-be-created resource in the create resource request message, and sends a create resource request message to the remote CSE.
  • the registration CSE determines the location of the resource to be created may include the following steps:
  • Step S11 The registration CSE determines that there is a registration relationship between itself and the remote CSE;
  • Step S12 The registration CSE sets the location of the resource to be created to the address information of the resource created when registering on the remote CSE.
  • the AE1 sends an update resource request message or a resource request message to the CSE1, where the parameters carried in the update resource request message or the create resource request message may include, but are not limited to, an advertisement target, which indicates that the AE1 indicates the identity of the CSE to be advertised.
  • the parameters carried in the update resource request message or the create resource request message may include, but are not limited to, an advertisement target, which indicates that the AE1 indicates the identity of the CSE to be advertised.
  • CSE1 After receiving the update resource request message or the resource request message from AE1, CSE1 checks whether there is a resource of type ⁇ remoteCSE> created for CSE3 locally, thereby judging whether there is a registration relationship between CSE1 and CSE3.
  • a request for creating a resource may be sent to CSE3, where the parameter "to" in the resource request is used for receiving
  • the location of the CSE indicating the newly created resource is set to "CSE3Base/remoteCSE1", that is, the address information of the resource created when CSE1 is registered on CSE3.
  • the registration CSE determines the location of the resource to be created may include the following operations:
  • Step S13 The registration CSE determines that there is no registration relationship between itself and the remote CSE, and does not include an advertisement to the attribute in the root directory of the resource;
  • Step S14 The registration CSE sets the location of the resource to be created as the address information of the root directory resource on the remote CSE.
  • CSE1 after receiving the update resource request message or the resource request message from AE1, CSE1 checks whether there is a resource of type ⁇ remoteCSE> created for CSE3 locally, thereby determining whether there is a relationship between CSE1 and CSE3. There is a registration relationship. If there is no resource of type ⁇ remoteCSE> created for CSE3 (that is, there is no registration relationship between CSE1 and CSE3), you need to continue checking whether ⁇ CSE1Base> is included. Contains the "announce to" attribute.
  • the create resource request may be sent to the CSE3, where the parameter "to" in the create resource request is set to "CSE3Base", that is, the address information of the resource of the root directory of the CSE3.
  • the registration CSE determines the location of the resource to be created may include the following steps:
  • Step S15 The registration CSE determines that there is no registration relationship between the self and the remote CSE, and the advertised to attribute in the root directory of the resource does not include the address information corresponding to the remote CSE.
  • Step S16 The registration CSE sets the location of the resource to be created as the address information of the root directory resource on the remote CSE.
  • CSE1 after receiving the update resource request message or the resource request message from AE1, CSE1 checks whether there is a resource of type ⁇ remoteCSE> created for CSE3 locally, thereby determining whether there is a relationship between CSE1 and CSE3. There is a registration relationship. If there is no resource of type ⁇ remoteCSE> created for CSE3 (that is, there is no registration relationship between CSE1 and CSE3), you need to continue to check if ⁇ CSE1Base> contains the "advertised to" attribute.
  • CSE3Base is CSE3-ID.chinamobile.com.
  • the request to create a resource may be sent to the CSE3, where the parameter "to" in the created resource request is set to "CSE3Base", that is, the address of the root resource of the CSE3. .
  • the registration CSE determines the location of the resource to be created may include the following operations:
  • Step S17 The registration CSE determines that there is no registration relationship between the self and the remote CSE, and includes an advertisement to the attribute in the root directory of the resource, and the notification includes the address information corresponding to the remote CSE in the attribute;
  • Step S18 The registration CSE sets the location of the resource to be created to the address information of the advertisement resource created when the advertisement is advertised to the remote CSE.
  • CSE1 after receiving the update resource request message or the resource request message from AE1, CSE1 checks whether there is a resource of type ⁇ remoteCSE> created for CSE3 locally, thereby determining whether there is a relationship between CSE1 and CSE3. There is a registration relationship. If there is no resource of type ⁇ remoteCSE> created for CSE3 (that is, there is no registration relationship between CSE1 and CSE3), you need to continue to check if ⁇ CSE1Base> contains the "advertised to" attribute.
  • CSE3Base contains the identifier or address of CSE3, you can check whether this part contains the address associated with CSE3.
  • CSE3Base is CSE3-ID.
  • the above method may further comprise the following processing steps:
  • Step S3 The registration CSE also carries the original resource address information in the create resource request message, and sends the create resource request message to the remote CSE, where the original resource address information is used to indicate the address of the original resource to be advertised;
  • Step S4 After receiving the resource creation request message, the remote CSE checks whether there is a resource having the same value of the original resource link and the original resource address information carried in the resource request message.
  • Step S5 If yes, the remote CSE sends a create resource response message to the registration CSE, where the create resource response message is used to indicate that the to-be-created resource already exists;
  • Step S6 If not, the remote CSE creates a resource according to the location of the resource to be created indicated in the Create Resource Request message.
  • the request for creating a resource sent by the CSE1 may also carry the parameter “original resource address” for indicating the address of the original resource ⁇ ae1>.
  • the CSE3 may create a resource in the specified location according to the setting of the parameter "to”; or, after receiving the request message, the CSE3 reads the value of the parameter "original resource address” and checks the local resource. Whether the value of the attribute "original resource address" of the resource exists is the same; if there is, the create resource response message may be sent to CSE1, the response message indicates that the creation fails, and the response status code is set to "already exist”; if not, The resource is created under the specified location according to the setting of the parameter "to".
  • FIG. 4 is a structural block diagram of an apparatus for creating an advertisement resource according to an embodiment of the present invention.
  • the apparatus may be applied to the registration CSE.
  • the apparatus for creating an advertisement of the application may include: the receiving module 10, configured to receive a request message from the sending end, where the request message carries the resource to be advertised and
  • the notification target is an identifier of the remote CSE to which the to-be-advertised resource indicated by the sender needs to be advertised;
  • the indication module 20 is configured to indicate to the remote CSE the location of the resource to be created according to the request message.
  • the device shown in FIG. 4 solves the problem that the resource notification in the related art needs to be notified by the parent resource, and the problem of lack of flexibility ensures the flexibility of the notification.
  • the indication module 20 may include: a determining unit 200 configured to determine to treat The location of the resource is determined, wherein the determining condition for determining the location of the resource to be created includes one of the following: whether there is a registration relationship between the registered CSE and the remote CSE, whether there is a registration relationship between the registered CSE and the remote CSE, and a resource root of the registered CSE Whether the advertised to attribute is included in the directory, whether there is a registration relationship between the registered CSE and the remote CSE, whether the resource root directory of the registered CSE includes the advertisement to the attribute, and whether the advertised to the attribute includes the address information corresponding to the remote CSE; the sending unit 202 And setting to carry the determined location of the to-be-created resource in the create resource request message, and send the create resource request message to the remote CSE.
  • the determining condition for determining the location of the resource to be created includes one of the following: whether there is a registration relationship between the registered CSE and the remote CSE, whether there is a registration relationship between the registered C
  • the determining unit 200 may include: a first determining subunit (not shown in the figure), configured to determine that there is a registration relationship between itself and the remote CSE; the first setting subunit (not shown) is set to The location of the resource to be created is set to the address information of the resource created when it is registered on the remote CSE.
  • the determining unit 200 may include: a second determining subunit (not shown in the figure), configured to determine that there is no registration relationship between itself and the remote CSE, and does not include an advertisement to the attribute in the root directory of the resource;
  • the setting subunit (not shown in the figure) is set to set the location of the resource to be created as the address information of the root directory resource on the remote CSE.
  • the determining unit 200 may include: a third determining subunit (not shown in the figure), configured to determine that there is no registration relationship between the self and the remote CSE, and the advertised attribute is included in the root directory of the own resource and is advertised to the attribute.
  • the address information corresponding to the remote CSE is not included; the third setting subunit (not shown) is set to set the location of the resource to be created as the address information of the root directory resource on the remote CSE.
  • the determining unit 200 may include: a fourth determining subunit (not shown in the figure), configured to determine that there is no registration relationship between the self and the remote CSE, and the root resource includes an advertisement to the attribute and is advertised to the attribute.
  • the address information corresponding to the remote CSE is included; the fourth setting subunit (not shown in the figure) is set to set the location of the resource to be created to the address information of the advertisement resource created when the advertisement is advertised to the remote CSE.
  • the foregoing embodiment achieves the following technical effects (it is required that the effects are achievable by some preferred embodiments): by using the technical solution provided by the embodiment of the present invention, registration is adopted.
  • the CSE receives the request message from the sender, and indicates the location of the to-be-created resource to the remote CSE according to the identifier of the remote CSE to be advertised by the to-be-advertised resource indicated by the sender that is carried in the request message, thereby solving the related art.
  • the resource notification needs to be limited by whether the parent resource is advertised, and the lack of flexibility ensures the flexibility of the notification.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the method and apparatus for creating an application advertisement resource provided by the embodiment of the present invention have the following beneficial effects: the restriction of the resource advertisement needs to be notified by the parent resource, thereby ensuring the flexibility of the advertisement.

Landscapes

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

Abstract

本发明公开了一种应用通告资源的创建方法及装置，在上述方法中，注册CSE接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；注册CSE根据请求消息向远程CSE指示待创建资源的位置。根据本发明提供的技术方案，进而确保了通告的灵活性。

Description

应用通告资源的创建方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种应用通告资源的创建方法及装置。
背景技术
机器对机器(M2M)通信网络是由各个M2M节点和承载网络组成的。M2M节点可以通过承载网络实现互相通信，一个M2M节点至少包含一个应用实体(AE)或者一个公共业务实体(CSE)。应用实体是执行实际M2M应用的逻辑单元，而公共业务实体则是对应用进行管理和服务的逻辑单元。
M2M应用之间的通信是通过公共业务实体之间的交互来实现的。M2M应用可以通过X接口连接到CSE，而CSE之间可以通过Y接口进行通信，其通信的前提条件在于：M2M应用首先需要在本地CSE进行注册，然后才能通过CSE之间的通信实现M2M应用的交互。图1是根据相关技术的M2M系统架构示意图。如图1所示，在M2M系统架构中，应用节点是末端的执行节点，例如：智能电表、温度测控传感器、火警报警器、智能家电；中间节点是连接末端执行节点到网络侧服务器的中间件，例如：网关；基础节点是网络侧的服务器。
应用实体需要在中间节点上的公共业务实体进行注册才能够加入M2M网络，从而作为M2M系统的应用节点进行服务。此时，中间节点上的CSE称为AE的注册CSE或本地CSE，基础节点上的CSE则称为AE的远程CSE。
在实际应用过程中，应用节点上的应用实体相关资源需要注册到应用节点上的公共业务实体，而不需要注册到中间节点的公共业务实体和基础节点的公共业务实体，在现有技术中，例如：基础节点上的应用希望查找应用节点上的应用时，则需要发送请求到所有连接到该基础节点的中间节点，并由中间节点将查询请求转发到各个应用节点，其不仅消耗了大量的网络资源，同时也需要耗费较长的时间。
为了便于中间节点上的应用实体能够查找到应用节点上的资源，特别使用了资源通告的方式，在中间节点上创建与应用节点上的原始资源相应的通告资源，通告资源具备与原始资源相同的搜索标签，并具有原始资源的链接，从而使得中间节点上的应用可以方便地搜索到所需要的资源，并根据链接访问原始资源。而原始资源则会创建一个属性“通告到”，用来保存成功创建完成的通告资源的地址信息。
在现有技术所采用的机制下，被通告的资源仍然保持与原始资源等同的结构，例 如：资源<ae>有一个子资源<container>，那么在<container>被通告后，在远程CSE上的资源<containerAnnc>(这是相应于原始资源<container>的通告资源)应该存储在资源<aeAnnc>下。这是在理想状态下的实施方式，换言之，其前提条件在于：认为<ae>首先会被通告。
但是在实际应用过程中，一个应用实体很有可能仅将保存其产生数据的<container>资源通告，而不希望将本身的信息通告，这样会导致<container>在远程CSE上无法找到原来定义的父资源，最终导致通告失败。
图2是根据相关技术的资源通告过程的示意图。如图2所示，每个CSE都有一个总的根目录<CSEBase>，所有被CSE管理的资源都在这个根目录下创建。在具体创建过程中：
首先，AE1在CSE1上注册，并在注册成功后，CSE1为AE1在根目录<CSE1Base>下创建资源<ae1>；
紧接着，CSE1在CSE2上注册，并在注册成功后，CSE2为CSE1创建资源<remoteCSE1>；
然后，CSE2在CSE3上注册，并在注册成功后，CSE3为CSE2创建资源<remoteCSE2>；
另外，在CSE1与CSE3之间并不存在注册关系，但是CSE2可以将CSE1通告到CSE3，因此，CSE3可以为CSE1创建通告资源<remoteCSE1Annc>，该通告资源可以有以下两种存在方式：
方式一、直接在CSE3的根目录<CSE3Base>下创建；
方式二、在<remoteCSE2>下创建。
不仅如此，AE1还可以请求CSE1将其通告到CSE3上，AE1的通告资源在<remoteCSE1Annc>下创建。
综上所述，相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性。
发明内容
本发明实施例提供了一种应用通告资源的创建方法及装置，以至少解决相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性的问题。
根据本发明实施例的一个方面，提供了一种应用通告资源的创建方法。
根据本发明实施例的应用通告资源的创建方法包括：注册CSE接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；注册CSE根据请求消息向远程CSE指示待创建资源的位置。
优选地，注册CSE根据请求消息向远程CSE指示待创建资源的位置包括：注册CSE确定待创建资源的位置，其中，确定待创建资源的位置的判定条件包括以下之一：注册CSE与远程CSE之间是否存在注册关系，注册CSE与远程CSE之间是否存在注册关系以及注册CSE的资源根目录下是否包含通告到属性，注册CSE与远程CSE之间是否存在注册关系、注册CSE的资源根目录下是否包含通告到属性以及通告到属性中是否包含与远程CSE对应的地址信息；注册CSE将确定的待创建资源的位置携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE。
优选地，注册CSE确定待创建资源的位置包括：注册CSE确定自身与远程CSE之间存在注册关系；注册CSE将待创建资源的位置设置为自身在远程CSE上注册时创建的资源的地址信息。
优选地，注册CSE确定待创建资源的位置包括：注册CSE确定自身与远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；注册CSE将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，注册CSE确定待创建资源的位置包括：注册CSE确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中不包含与远程CSE对应的地址信息；注册CSE将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，注册CSE确定待创建资源的位置包括：注册CSE确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中包含与远程CSE对应的地址信息；注册CSE将待创建资源的位置设置为自身通告到远程CSE上时，创建的通告资源的地址信息。
优选地，上述方法还包括：注册CSE还将原始资源地址信息携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE，其中，原始资源地址信息用于指示待通告的原始资源的地址；远程CSE在接收到创建资源请求消息后，检查本地是否存在属性原始资源链接的取值与创建资源请求消息中携带的原始资源地址信息的取值相同的资源；如果存在，则远程CSE向注册CSE发送创建资源响应消息，其中，创建资源响应消息用于指示待创建资源已经存在；如果不存在，则远程CSE根据创建资源请求消息中指示的待创建资源的位置创建资源。
根据本发明实施例的另一方面，提供了一种应用通告资源的创建装置。
根据本发明实施例的应用通告资源的创建装置包括：接收模块，设置为接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；指示模块，设置为根据请求消息向远程CSE指示待创建资源的位置。
优选地，指示模块包括：确定单元，设置为确定待创建资源的位置，其中，确定待创建资源的位置的判定条件包括以下之一：注册CSE与远程CSE之间是否存在注册关系，注册CSE与远程CSE之间是否存在注册关系以及注册CSE的资源根目录下是否包含通告到属性，注册CSE与远程CSE之间是否存在注册关系、注册CSE的资源根目录下是否包含通告到属性以及通告到属性中是否包含与远程CSE对应的地址信息；发送单元，设置为将确定的待创建资源的位置携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE。
优选地，确定单元包括：第一确定子单元，设置为确定自身与远程CSE之间存在注册关系；第一设置子单元，设置为将待创建资源的位置设置为自身在远程CSE上注册时创建的资源的地址信息。
优选地，确定单元包括：第二确定子单元，设置为确定自身与远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；第二设置子单元，设置为将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，确定单元包括：第三确定子单元，设置为确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中不包含与远程CSE对应的地址信息；第三设置子单元，设置为将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，确定单元包括：第四确定子单元，设置为确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中包含与远程CSE对应的地址信息；第四设置子单元，设置为将待创建资源的位置设置为自身通告到远程CSE上时，创建的通告资源的地址信息。
通过本发明实施例，采用注册CSE接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；注册CSE根据请求消息向远程CSE指示待创建资源的位置，解决了相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性的问题，进而确保了通告的灵活性。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的M2M系统架构示意图；
图2是根据相关技术的资源通告过程的示意图；
图3是根据本发明实施例的应用通告资源的创建方法的流程图；
图4是根据本发明实施例的应用通告资源的创建装置的结构框图；
图5是根据本发明优选实施例的应用通告资源的创建装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图3是根据本发明实施例的应用通告资源的创建方法的流程图。如图3所示，该方法可以包括以下处理步骤：
步骤S302：注册CSE接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；
步骤S304：注册CSE根据请求消息向远程CSE指示待创建资源的位置。
相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性。采用如图3所示的方法，通过注册CSE接收来自于发送端的请求消息，并根据请求消息中携带的发送端指示的待通告的资源需要通告到的远程CSE的标识进而向远程CSE指示待创建资源的位置，由此解决了相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性的问题，进而确保了通告的灵活性。
需要说明的是，上述发送端与注册CSE之间存在注册关系。
优选地，在步骤S304中，注册CSE根据请求消息向远程CSE指示待创建资源的位置可以包括以下操作：
步骤S1：注册CSE确定待创建资源的位置，其中，确定待创建资源的位置的判定条件可以包括以下之一：
条件一：注册CSE与远程CSE之间是否存在注册关系；
条件二：注册CSE与远程CSE之间是否存在注册关系；
条件三：注册CSE的资源根目录下是否包含通告到属性，注册CSE与远程CSE之间是否存在注册关系、注册CSE的资源根目录下是否包含通告到属性以及通告到属性中是否包含与远程CSE对应的地址信息；
步骤S2：注册CSE将确定的待创建资源的位置携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE。
优选地，在步骤S1中，注册CSE确定待创建资源的位置可以包括以下步骤：
步骤S11：注册CSE确定自身与远程CSE之间存在注册关系；
步骤S12：注册CSE将待创建资源的位置设置为自身在远程CSE上注册时创建的资源的地址信息。
作为本发明的一个优选实施方式，将沿用上述图2中所提到的应用场景。AE1向CSE1发送更新资源请求消息或创建资源请求消息，其中，更新资源请求消息或创建资源请求消息中携带的参数可以包括但不限于：通告目标，其为AE1指示需要通告到的CSE的标识，在该优选实施例中设置为CSE3。CSE1在接收到来自于AE1的更新资源请求消息或创建资源请求消息之后，检查本地是否存在为CSE3创建的<remoteCSE>类型的资源，由此来判断CSE1和CSE3之间是否存在注册关系。如果存在为CSE3创建的<remoteCSE>类型的资源(即CSE1和CSE3之间存在注册关系)，则可以向CSE3发送创建资源请求，其中，该创建资源请求中的参数“to”(用于向接收请求消息的CSE指示新创建资源的位置)设置为“CSE3Base/remoteCSE1”，即在CSE3上为CSE1注册时所创建的资源的地址信息。
优选地，在步骤S1中，注册CSE确定待创建资源的位置可以包括以下操作：
步骤S13：注册CSE确定自身与远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；
步骤S14：注册CSE将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
在优选实施例中，CSE1在接收到来自于AE1的更新资源请求消息或创建资源请求消息之后，检查本地是否存在为CSE3创建的<remoteCSE>类型的资源，由此来判断CSE1和CSE3之间是否存在注册关系。如果不存在为CSE3创建的<remoteCSE>类型的资源(即CSE1和CSE3之间不存在注册关系)，则需要继续检查<CSE1Base>是否包 含“通告到”属性。如果不包含“通告到”属性，则可以向CSE3发送创建资源请求，其中，该创建资源请求中的参数“to”设置为“CSE3Base”，即CSE3的根目录的资源的地址信息。
优选地，在步骤S1中，注册CSE确定待创建资源的位置可以包括以下步骤：
步骤S15：注册CSE确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中不包含与远程CSE对应的地址信息；
步骤S16：注册CSE将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
在优选实施例中，CSE1在接收到来自于AE1的更新资源请求消息或创建资源请求消息之后，检查本地是否存在为CSE3创建的<remoteCSE>类型的资源，由此来判断CSE1和CSE3之间是否存在注册关系。如果不存在为CSE3创建的<remoteCSE>类型的资源(即CSE1和CSE3之间不存在注册关系)，则需要继续检查<CSE1Base>是否包含“通告到”属性。如果包含“通告到”属性，则检查“通告到”属性中是否包含有与CSE3相关的地址，该地址表示CSE1被通告到了CSE3上，CSE3创建的CSE1的通告资源的地址，例如：“CSE3Base/remoteCSE2/remoteCSE1Annc”或“CSE3Base/remoteCSE1Annc”即为与CSE3相关的地址，因为地址的第一部分(CSE3Base)中包含CSE3的标识或地址，所以可以通过检查此部分来判断是否包含与CSE3相关的地址。例如：CSE3Base为CSE3-ID.chinamobile.com。如果“通告到”属性中不包含与CSE3相关的地址，可以则向CSE3发送创建资源请求，其中，该创建资源请求中的参数“to”设置为“CSE3Base”，即CSE3的根目录资源的地址。
优选地，在步骤S1中，注册CSE确定待创建资源的位置可以包括以下操作：
步骤S17：注册CSE确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中包含与远程CSE对应的地址信息；
步骤S18：注册CSE将待创建资源的位置设置为自身通告到远程CSE上时，创建的通告资源的地址信息。
在优选实施例中，CSE1在接收到来自于AE1的更新资源请求消息或创建资源请求消息之后，检查本地是否存在为CSE3创建的<remoteCSE>类型的资源，由此来判断CSE1和CSE3之间是否存在注册关系。如果不存在为CSE3创建的<remoteCSE>类型的资源(即CSE1和CSE3之间不存在注册关系)，则需要继续检查<CSE1Base>是否包含“通告到”属性。如果包含“通告到”属性，则检查“通告到”属性中是否包含有与CSE3相关的地址，该地址表示CSE1被通告到了CSE3上，CSE3创建的CSE1的通告资源的地址，例如：“CSE3Base/remoteCSE2/remoteCSE1Annc”或“CSE3Base/ remoteCSE1Annc”即为与CSE3相关的地址，因为地址的第一部分(CSE3Base)中包含CSE3的标识或地址，所以可以通过检查此部分来判断是否包含与CSE3相关的地址。例如：CSE3Base为CSE3-ID.chinamobile.com。如果“通告到”属性中包含有与CSE3相关的地址，则可以向CSE3发送创建资源请求，其中，该创建资源请求中的参数“to”设置为<CSE1Base>的属性“通告到”中与CSE3相关的地址，例如：“CSE3Base/remoteCSE2/remoteCSE1Annc”或“CSE3Base/remoteCSE1Annc”。
优选地，上述方法还可以包括以下处理步骤：
步骤S3：注册CSE还将原始资源地址信息携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE，其中，原始资源地址信息用于指示待通告的原始资源的地址；
步骤S4：远程CSE在接收到创建资源请求消息后，检查本地是否存在属性原始资源链接的取值与创建资源请求消息中携带的原始资源地址信息的取值相同的资源；
步骤S5：如果存在，则远程CSE向注册CSE发送创建资源响应消息，其中，创建资源响应消息用于指示待创建资源已经存在；
步骤S6：如果不存在，则远程CSE根据创建资源请求消息中指示的待创建资源的位置创建资源。
作为本发明的另一个优选实施例，在CSE1发送的创建资源请求中还可以携带有参数“原始资源地址”，用于指示原始资源<ae1>的地址。CSE3在接收到上述请求消息后，可以根据参数“to”的设置，在指定位置下创建资源；或者，CSE3在接收到上述请求消息后，读取参数“原始资源地址”的值，检查本地资源中是否存在资源的属性“原始资源地址”的值与之相同；如果有，则可以向CSE1发送创建资源响应消息，响应消息中指示创建失败，响应状态码设置为“已经存在”；如果没有，则根据参数“to”的设置在指定位置下创建资源。
图4是根据本发明实施例的应用通告资源的创建装置的结构框图。该装置可以应用于注册CSE中，如图4所示，该应用通告资源的创建装置可以包括：接收模块10，设置为接收来自于发送端的请求消息，其中，请求消息中携带有待通告的资源和通告目标，通告目标为发送端指示的待通告的资源需要通告到的远程CSE的标识；指示模块20，设置为根据请求消息向远程CSE指示待创建资源的位置。
采用如图4所示的装置，解决了相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性的问题，进而确保了通告的灵活性。
优选地，如图5所示，指示模块20可以包括：确定单元200，设置为确定对待创 建资源的位置，其中，确定待创建资源的位置的判定条件包括以下之一：注册CSE与远程CSE之间是否存在注册关系，注册CSE与远程CSE之间是否存在注册关系以及注册CSE的资源根目录下是否包含通告到属性，注册CSE与远程CSE之间是否存在注册关系、注册CSE的资源根目录下是否包含通告到属性以及通告到属性中是否包含与远程CSE对应的地址信息；发送单元202，设置为将确定的待创建资源的位置携带在创建资源请求消息中，并将创建资源请求消息发送至远程CSE。
优选地，确定单元200可以包括：第一确定子单元(图中未示出)，设置为确定自身与远程CSE之间存在注册关系；第一设置子单元(图中未示出)，设置为将待创建资源的位置设置为自身在远程CSE上注册时创建的资源的地址信息。
优选地，确定单元200可以包括：第二确定子单元(图中未示出)，设置为确定自身与远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；第二设置子单元(图中未示出)，设置为将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，确定单元200可以包括：第三确定子单元(图中未示出)，设置为确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中不包含与远程CSE对应的地址信息；第三设置子单元(图中未示出)，设置为将待创建资源的位置设置为远程CSE上根目录资源的地址信息。
优选地，确定单元200可以包括：第四确定子单元(图中未示出)，设置为确定自身与远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且通告到属性中包含与远程CSE对应的地址信息；第四设置子单元(图中未示出)，设置为将待创建资源的位置设置为自身通告到远程CSE上时，创建的通告资源的地址信息。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，通过注册CSE接收来自于发送端的请求消息，并根据请求消息中携带的发送端指示的待通告的资源需要通告到的远程CSE的标识进而向远程CSE指示待创建资源的位置，由此解决了相关技术中的资源通告需要受到父资源是否通告的限制，缺乏灵活性的问题，进而确保了通告的灵活性。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种应用通告资源的创建方法及装置具有以下有益效果：解除了资源通告需要受到父资源是否通告的限制，进而确保了通告的灵活性。

Claims (13)

  1. 一种应用通告资源的创建方法，包括：
    注册公共业务实体CSE接收来自于发送端的请求消息，其中，所述请求消息中携带有待通告的资源和通告目标，所述通告目标为所述发送端指示的待通告的资源需要通告到的远程CSE的标识；
    所述注册CSE根据所述请求消息向所述远程CSE指示待创建资源的位置。
  2. 根据权利要求1所述的方法，其中，所述注册CSE根据所述请求消息向所述远程CSE指示待创建资源的位置包括：
    所述注册CSE确定待创建资源的位置，其中，确定所述待创建资源的位置的判定条件包括以下之一：所述注册CSE与所述远程CSE之间是否存在注册关系，所述注册CSE与所述远程CSE之间是否存在注册关系以及所述注册CSE的资源根目录下是否包含通告到属性，所述注册CSE与所述远程CSE之间是否存在注册关系、所述注册CSE的资源根目录下是否包含通告到属性以及所述通告到属性中是否包含与所述远程CSE对应的地址信息；
    所述注册CSE将确定的待创建资源的位置携带在创建资源请求消息中，并将所述创建资源请求消息发送至所述远程CSE。
  3. 根据权利要求2所述的方法，其中，所述注册CSE确定所述待创建资源的位置包括：
    所述注册CSE确定自身与所述远程CSE之间存在注册关系；
    所述注册CSE将所述待创建资源的位置设置为自身在所述远程CSE上注册时创建的资源的地址信息。
  4. 根据权利要求2所述的方法，其中，所述注册CSE确定所述待创建资源的位置包括：
    所述注册CSE确定自身与所述远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；
    所述注册CSE将所述待创建资源的位置设置为所述远程CSE上根目录资源的地址信息。
  5. 根据权利要求2所述的方法，其中，所述注册CSE确定所述待创建资源的位置包括：
    所述注册CSE确定自身与所述远程CSE之间不存在注册关系、自身资源根目 录下包含通告到属性且所述通告到属性中不包含与所述远程CSE对应的地址信息；
    所述注册CSE将所述待创建资源的位置设置为所述远程CSE上根目录资源的地址信息。
  6. 根据权利要求2所述的方法，其中，所述注册CSE确定所述待创建资源的位置包括：
    所述注册CSE确定自身与所述远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且所述通告到属性中包含与所述远程CSE对应的地址信息；
    所述注册CSE将所述待创建资源的位置设置为自身通告到所述远程CSE上时，创建的通告资源的地址信息。
  7. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述注册CSE还将原始资源地址信息携带在所述创建资源请求消息中，并将所述创建资源请求消息发送至所述远程CSE，其中，所述原始资源地址信息用于指示待通告的原始资源的地址；
    所述远程CSE在接收到所述创建资源请求消息后，检查本地是否存在属性原始资源链接的取值与所述创建资源请求消息中携带的所述原始资源地址信息的取值相同的资源；
    如果存在，则所述远程CSE向所述注册CSE发送创建资源响应消息，其中，所述创建资源响应消息用于指示待创建资源已经存在；
    如果不存在，则所述远程CSE根据所述创建资源请求消息中指示的待创建资源的位置创建资源。
  8. 一种应用通告资源的创建装置，包括：
    接收模块，设置为接收来自于发送端的请求消息，其中，所述请求消息中携带有待通告的资源和通告目标，所述通告目标为所述发送端指示的待通告的资源需要通告到的远程CSE的标识；
    指示模块，设置为根据所述请求消息向所述远程CSE指示待创建资源的位置。
  9. 根据权利要求8所述的装置，其中，所述指示模块包括：
    确定单元，设置为确定待创建资源的位置，其中，确定所述待创建资源的位置的判定条件包括以下之一：所述注册CSE与所述远程CSE之间是否存在注册关 系，所述注册CSE与所述远程CSE之间是否存在注册关系以及所述注册CSE的资源根目录下是否包含通告到属性，所述注册CSE与所述远程CSE之间是否存在注册关系、所述注册CSE的资源根目录下是否包含通告到属性以及所述通告到属性中是否包含与所述远程CSE对应的地址信息；
    发送单元，设置为将确定的待创建资源的位置携带在创建资源请求消息中，并将所述创建资源请求消息发送至所述远程CSE。
  10. 根据权利要求9所述的装置，其中，所述确定单元包括：
    第一确定子单元，设置为确定自身与所述远程CSE之间存在注册关系；
    第一设置子单元，设置为将所述待创建资源的位置设置为自身在所述远程CSE上注册时创建的资源的地址信息。
  11. 根据权利要求9所述的装置，其中，所述确定单元包括：
    第二确定子单元，设置为确定自身与所述远程CSE之间不存在注册关系且自身资源根目录下并不包含通告到属性；
    第二设置子单元，设置为将所述待创建资源的位置设置为所述远程CSE上根目录资源的地址信息。
  12. 根据权利要求9所述的装置，其中，所述确定单元包括：
    第三确定子单元，设置为确定自身与所述远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且所述通告到属性中不包含与所述远程CSE对应的地址信息；
    第三设置子单元，设置为将所述待创建资源的位置设置为所述远程CSE上根目录资源的地址信息。
  13. 根据权利要求9所述的装置，其中，所述确定单元包括：
    第四确定子单元，设置为确定自身与所述远程CSE之间不存在注册关系、自身资源根目录下包含通告到属性且所述通告到属性中包含与所述远程CSE对应的地址信息；
    第四设置子单元，设置为将所述待创建资源的位置设置为自身通告到所述远程CSE上时，创建的通告资源的地址信息。
PCT/CN2015/086051 2014-12-09 2015-08-04 应用通告资源的创建方法及装置 WO2016090933A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/534,650 US20180270190A1 (en) 2014-12-09 2015-08-04 Method and device for creating application announcement resource
EP15868485.2A EP3232693B1 (en) 2014-12-09 2015-08-04 Method and device for creating application notification resource
KR1020177018391A KR20170092646A (ko) 2014-12-09 2015-08-04 애플리케이션 통지 자원의 구축 방법 및 장치

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410749294.8A CN105744460A (zh) 2014-12-09 2014-12-09 应用通告资源的创建方法及装置
CN201410749294.8 2014-12-09

Publications (1)

Publication Number Publication Date
WO2016090933A1 true WO2016090933A1 (zh) 2016-06-16

Family

ID=56106597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086051 WO2016090933A1 (zh) 2014-12-09 2015-08-04 应用通告资源的创建方法及装置

Country Status (5)

Country Link
US (1) US20180270190A1 (zh)
EP (1) EP3232693B1 (zh)
KR (1) KR20170092646A (zh)
CN (1) CN105744460A (zh)
WO (1) WO2016090933A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108093380B (zh) * 2016-11-22 2022-11-08 中兴通讯股份有限公司 注册状态的确定方法、装置及系统、cse

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012069997A1 (en) * 2010-11-22 2012-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Xdms for resource management in m2m
US20130203394A1 (en) * 2012-02-03 2013-08-08 Interdigital Patent Holdings, Inc. Method and apparatus to support m2m content and context based services
CN103299601A (zh) * 2010-11-19 2013-09-11 交互数字专利控股公司 用于资源通告及去通告的机器对机器（m2m）接口过程
CN104093118A (zh) * 2014-03-05 2014-10-08 中兴通讯股份有限公司 一种资源通告的方法、机器对机器节点和系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9439026B2 (en) * 2012-09-10 2016-09-06 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for communication between machine to machine M2M service provider networks
KR101740449B1 (ko) * 2013-01-11 2017-05-26 엘지전자 주식회사 M2m(machine-to-machine)시스템에서 게이트웨이 변경 방법 및 이를 위한 장치
WO2014181941A1 (ko) * 2013-05-09 2014-11-13 전자부품연구원 개방형 ｍ２ｍ 시스템 및 그의 리소스 관리와 인터페이스 방법
JP6240312B2 (ja) * 2013-05-16 2017-11-29 エルジー エレクトロニクス インコーポレイティド Ｍ２ｍ通信システムにおいて購読及び通知のための方法及びそのための装置
KR102345346B1 (ko) * 2013-12-01 2021-12-30 엘지전자 주식회사 무선 통신 시스템에서 특정 리소스의 관리를 위한 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103299601A (zh) * 2010-11-19 2013-09-11 交互数字专利控股公司 用于资源通告及去通告的机器对机器（m2m）接口过程
WO2012069997A1 (en) * 2010-11-22 2012-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Xdms for resource management in m2m
US20130203394A1 (en) * 2012-02-03 2013-08-08 Interdigital Patent Holdings, Inc. Method and apparatus to support m2m content and context based services
CN104093118A (zh) * 2014-03-05 2014-10-08 中兴通讯股份有限公司 一种资源通告的方法、机器对机器节点和系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"European Telecommunications Standards Institute. ''ETSI TS 102 690 V2.1.1'' Machine-to-Machine communications (M2M);", FUNCTIONAL ARCHITECTURE, 31 October 2013 (2013-10-31), XP055392018 *
See also references of EP3232693A4 *

Also Published As

Publication number Publication date
EP3232693B1 (en) 2020-04-22
CN105744460A (zh) 2016-07-06
EP3232693A4 (en) 2017-12-06
EP3232693A1 (en) 2017-10-18
KR20170092646A (ko) 2017-08-11
US20180270190A1 (en) 2018-09-20

Similar Documents

Publication Publication Date Title
JP6629392B2 (ja) デバイストリガ
US10085244B2 (en) Method for guaranteeing operation of control message in wireless communication system and device for same
KR102064690B1 (ko) 도메인들에 걸쳐 서비스 계층 리소스 전파
US20180063879A1 (en) Apparatus and method for interoperation between internet-of-things devices
US9867164B2 (en) Method and device for processing a specific request message in wireless communication system
CN104093118A (zh) 一种资源通告的方法、机器对机器节点和系统
US10070408B2 (en) Application registration methods and apparatuses
CN105282682B (zh) 一种实现资源属性通告的方法和公共业务实体
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
US10715628B2 (en) Attribute operating method and device
WO2015117482A1 (zh) 更新资源通告的方法、本地公共业务实体及系统
EP3128715B1 (en) Resource creation method and apparatus
CN109478153B (zh) 机器到机器服务层通信中的消息重定向
KR102423812B1 (ko) 안정적인 분산형 M2M/IoT 서비스들의 가능화
WO2016090933A1 (zh) 应用通告资源的创建方法及装置
WO2015117330A1 (zh) 一种删除通告资源的方法和公共业务实体
WO2016082492A1 (zh) 一种原始资源通告的方法及相应的节点
WO2015139364A1 (zh) 一种资源通告管理的方法及公共业务实体
WO2018010366A1 (zh) 信息同步方法及装置
CN118250320A (zh) 级联注册方法、装置、电子设备和存储介质
WO2014140613A2 (en) Communications systems and methods

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15868485

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15534650

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015868485

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20177018391

Country of ref document: KR

Kind code of ref document: A