WO2015062421A1

WO2015062421A1 - Gateway replacement method, gateway, and server

Info

Publication number: WO2015062421A1
Application number: PCT/CN2014/088798
Authority: WO
Inventors: 李娜
Original assignee: 华为终端有限公司
Priority date: 2013-10-30
Filing date: 2014-10-17
Publication date: 2015-05-07
Also published as: CN104601456B; CN104601456A

Abstract

A gateway replacement method comprises: receiving a gateway replacement notification sent by a second gateway, the gateway replacement notification carrying a replacement instruction, and the replacement instruction being for indicating that the second gateway will be replaced with a first gateway; generating a gateway replacement identifier, the gateway replacement identifier being for identifying gateway replacement; sending the gateway replacement identifier to the second gateway; receiving a create resource request sent by the first gateway, the create resource request carrying a service capability layer identifier of the second gateway and the gateway replacement identifier; updating a service capability layer resource according to a first service capability layer identifier and a second service capability layer identifier, the first service capability layer identifier being obtained by the server according to the gateway replacement notification or the create resource request; and sending a first message to the first gateway, the first message carrying the information about that the server has successfully created the service capability layer resource.

Description

Gateway replacement method, gateway and server

Technical field

The present invention relates to the field of communications, and in particular, to a gateway replacement method, a gateway, and a server.

Background technique

M2M (English name: Machine-to-Machine, full name in Chinese: machine-to-machine) Communication is a general term for a series of technical and technical combinations of data communication and interaction between machines and machines. The M2M service capability layer (English name: M2M Service Capability Layer) includes the network side service capability layer, the gateway service capability layer, and the MSM terminal service capability layer, and the interface for communication between the layers. The service capability layer of the network side, the gateway, and the M2M terminal provides a service function, which may also be called a common service layer (English name Common Service Layer). This layer contains the general service entity (English name Common Service Entity), and the general business entity is the instantiation of the common business function (English name: Common Service Function). The general business function is the business function provided by the business capability layer. The service capability layer identifier may also be referred to as a general service layer identifier or a general service entity identifier.

In the prior art, when the device that does not have the service capability layer needs to be replaced, the notification of the device replacement by the old device is given to the service capability layer (Hosting SCL) of the device, and the Hosting SCL determines the authority of the device. Hosting SCL marks the resources corresponding to this device and replies to notify the old device that it can go offline. Hosting SCL waits for new devices to join to replace the old devices that are offline. The new device initiates the creation of the request to the Hosting SCL, and carries the replacement indication and the identification information of the replaced old device. After receiving the request, the Hosting SCL associates the related information and updates the differentiated information of the corresponding resource, that is, the replacement process is completed. .

The replaceable device in the prior art only has application capability and no business capability, so it only needs to store information related to its own application, and does not need to store and manage information of other devices. A gateway or device with SCL provides service capabilities and needs to store and manage resources of gateways or devices without service capabilities. Therefore, the prior art cannot solve the replacement problem of a gateway with business capability.

Summary of the invention

It is an object of the present invention to provide a gateway replacement method for implementing replacement of a service capable gateway.

The first aspect provides a gateway replacement method, the method comprising:

The server receives a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries Instructing, the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

The server generates a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement;

Sending, by the server, the gateway replacement identifier to the second gateway;

The server receives a request for creating a resource that is sent by the first gateway, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, where the second service capability layer identifier And the gateway replacement identifier is sent by the second gateway or the server to the first gateway;

The server updates the service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is requested by the server according to the gateway replacement notification or the resource creation request. obtain;

The server sends a first message to the first gateway, where the first message carries information that the server has successfully created the service capability layer resource.

Based on the first aspect, in a first possible implementation manner, the gateway replacement notification further includes the first service capability layer identifier of the first gateway.

Based on the first aspect, or the first possible implementation manner of the first aspect, in a second possible implementation manner, the first service capability layer identifier and the replacement indication are sent by the first gateway to Said second gateway.

Based on the first aspect, or the first possible implementation manner of the first aspect, in a third possible implementation manner, the receiving, by the second gateway, the gateway replacement notification, before:

Receiving, by the server, the first service capability layer identifier and the replacement indication sent by the first gateway;

The server sends the first service capability layer identifier and the replacement indication to the second gateway.

Based on the first possible implementation manner or the second possible implementation manner of the first aspect, in the fourth possible implementation manner, before the server generates the gateway replacement identifier, the method further includes:

The server detects whether the first service capability layer identifier is valid;

The server generates the gateway replacement identifier when the first service capability layer identifier is valid.

Based on the first aspect, in a fifth possible implementation manner, after the server receives the gateway replacement notification sent by the second gateway, the method further includes:

The server checks whether the second gateway can be replaced;

The server generates the gateway replacement identifier when the second gateway can be replaced.

Based on the first aspect, or the first possible implementation manner of the first aspect, in a sixth possible implementation, the server sends the gateway replacement identifier to the second gateway, and further to the second The gateway sends a wait indication, where the wait indication is used to indicate that the second gateway needs to wait for a downline indication.

Based on the first aspect, in a seventh possible implementation, after the server sends the first message to the first gateway, the method further includes:

The server sends a notification to the second gateway, where the notification carries a first indication and a uniform resource locator of the first gateway service capability layer, where the first indication is used to indicate that the gateway replacement is completed.

In a second aspect, a gateway replacement method is provided, the method comprising:

The first gateway receives the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway;

The first gateway sends a request for creating a resource to the server, where the request for creating a resource carries the identifier of the second service capability layer and the gateway replacement identifier, where the request for creating a resource triggers the server according to the first gateway. The first service capability layer identifier and the second service capability layer identifier are updated, and the first service capability layer identifier is included in the creation resource request or the gateway replacement notification sent by the second gateway. ;

Receiving, by the first gateway, the first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

The first gateway receives the second message sent by the second gateway, where the second information includes resource information corresponding to the device registered by the second gateway and registered to the second gateway;

The first gateway updates the gateway information to the device registered to the second gateway according to the received second information.

Based on the second aspect, in a first possible implementation manner, before the receiving, by the first gateway, the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway, the first gateway further includes:

The first gateway sends the first service capability layer identifier and the replacement indication of the first gateway to the second gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway. The second gateway is configured to send the gateway replacement notification to the server, where the gateway replacement notification carries the replacement indication and the first service capability layer identifier.

Based on the second aspect, in a second possible implementation, the first gateway receives the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway.

Sending, by the first gateway, the first service capability layer identifier and the replacement indication to the server, so that the server sends the first service capability layer identifier and the replacement indication to the Second gateway.

Based on the second aspect or the second possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, in a third possible implementation manner, the gateway information includes the first gateway A uniform resource locator of the service capability layer and a uniform resource locator of the service capability layer of the second gateway.

Based on the second aspect, in a fourth possible implementation manner, the first gateway, according to the received second message, updates the gateway information to the device that is registered to the second gateway, and specifically includes:

Transmitting, by the first gateway, a third message to the device corresponding to the application resource that is included in the first gateway, where the third message includes a uniform resource locator of the service capability layer of the first gateway, and the second gateway The uniform resource locator of the service capability layer; the application resource refers to the corresponding resource of the device registered to the second gateway.

According to a fourth possible implementation manner of the second aspect, in a fifth possible implementation, the first gateway sends a third message to the device corresponding to the application resource of the first gateway, and then includes

The first gateway receives a fourth message sent by the online device, where the fourth message carries information that the online device receives the update message.

According to a fifth possible implementation manner of the second aspect, in a sixth possible implementation, the fourth message further carries, by the online device, a uniform resource locator of the service capability layer of the second gateway Information of a uniform resource locator of the service capability layer of the second gateway.

Based on the fifth possible implementation manner of the second aspect, in a seventh possible implementation manner, the receiving the confirmation message of the online device, and then the following:

The first gateway marks the online device corresponding to the fourth message received by the first gateway.

According to a fifth possible implementation manner of the second aspect, in an eighth possible implementation manner, the first gateway updates the device that is registered to the second gateway according to the received second information Gateway information, further including:

The first gateway checks whether the resource corresponding to the device that is not updated expires, and if it expires, deletes the resource corresponding to the device that is not updated.

In a third aspect, a gateway replacement method is provided, where the method includes:

The second gateway sends a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication and a first service capability layer identifier of the first gateway, where the replacement indication is used to indicate that the second gateway Replaced by the first gateway;

Receiving, by the second gateway, a gateway replacement identifier sent by the server, where the gateway replacement identifier is used to identify a gateway replacement;

Sending, by the second gateway, the second service capability layer identifier of the second gateway and the gateway replacement identifier to the first gateway;

Receiving, by the second gateway, the first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource;

The second gateway sends a second message to the first gateway, where the second message includes resource information corresponding to the device registered by the second gateway and registered to the second gateway.

Based on the third aspect, in a first possible implementation manner, before the second gateway sends a gateway replacement notification to the server, the method further includes:

The second gateway receives the first service capability layer identifier and the replacement indication of the first gateway that are sent by the first gateway, and the gateway replacement identifier further includes the first service capability layer identifier.

Based on the third aspect, in a second possible implementation manner, the second gateway sends a network replacement notification to the server, where the gateway replacement notification carries a replacement indication, and then includes:

The second gateway receives the gateway replacement identifier and the waiting indication sent by the server.

Based on the third aspect, in a third possible implementation, the sending, by the first gateway, the second service capability layer identifier and the gateway replacement identifier of the second gateway;

The second gateway receives a uniform resource locator of the service capability layer of the first gateway and the replacement indication sent by the server.

According to the third aspect, in a fourth possible implementation, the second gateway sends a second message to the first gateway, where the second message includes a registration that is stored by the second gateway to the first The resource information corresponding to the device of the second gateway, and then includes:

After receiving the acknowledgement message sent by the first gateway, the second gateway goes offline, and the acknowledgement message is used to confirm that the first gateway receives the second message.

In a fourth aspect, a server is provided, the server comprising:

a first receiving unit, configured to receive, by the server, a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

a generating unit, configured to generate a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement;

a first sending unit, configured to send the gateway replacement identifier to the second gateway;

a second receiving unit, configured to receive a request for creating a resource that is sent by the first gateway, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, where the second The service capability layer identifier and the gateway replacement identifier are sent by the second gateway or the server to the first gateway;

An update unit, configured to update a service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is replaced by the server according to the gateway replacement notification or the creation Resource request is obtained;

The second sending unit is configured to send a first message to the first gateway, where the first message carries information that the server has successfully created the service capability layer resource.

According to the fourth aspect, in a first possible implementation, the gateway replacement notification further includes the first service capability layer identifier of the first gateway;

According to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the first service capability layer identifier and the replacement indication are sent by the first gateway to the Second gateway.

According to the fourth aspect, in a third possible implementation manner, the gateway replacement notification further includes a first service capability layer identifier of the first gateway, where the server further includes:

a third receiving unit, configured to receive a first service capability layer identifier and a replacement indication sent by the first gateway;

And a third sending unit, configured to send the first service capability layer identifier and the replacement indication to the second gateway.

Based on the fourth aspect or the first possible implementation manner of the fourth aspect, or the second possible implementation manner of the fourth aspect, in a fourth possible implementation manner, the server further includes:

The detecting unit is configured to detect whether the first service capability layer identifier is valid.

The generating unit is configured to generate the gateway replacement identifier when the first service capability layer identifier is valid.

According to the fourth aspect, in a fifth possible implementation, the second sending unit is further configured to send, by the second gateway, a waiting indication, to notify the The second gateway needs to wait for the offline indication.

Based on the fourth aspect, in a sixth possible implementation, the server further includes:

a fourth sending unit, configured to send a notification to the second gateway, where the notification carries the first indication and a uniform resource locator of the first gateway service capability layer, where the first indication is used to indicate a gateway Replacement is complete.

In a fifth aspect, a gateway is provided, where the gateway includes:

a first receiving unit, configured to receive a gateway replacement identifier sent by the second gateway and a second service capability layer identifier of the second gateway;

a first sending unit, configured to send a request for creating a resource to the server, where the request for creating a resource carries the identifier of the second service capability layer and the gateway replacement identifier, where the request for creating a resource triggers the server according to the Updating the first service capability layer identifier and the second service capability layer identifier of the first gateway, and updating the service capability layer resource, where the first service capability layer identifier is included in the creation resource request or the second gateway The gateway is sent in the replacement notification;

a second receiving unit, configured to receive a first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

a third receiving unit, configured to receive a second message sent by the second gateway, where the second message includes resource information corresponding to a device that is stored by the second gateway and registered to the second gateway;

And an updating unit, configured to update the gateway information to the device registered to the second gateway according to the second message received by the third receiving unit.

Based on the fifth aspect, in a first possible implementation manner, the gateway further includes:

a second sending unit, configured to send, to the second gateway, a first service capability layer identifier and a replacement indication of the first gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the second gateway The second gateway sends a network replacement notification to the server, where the gateway replacement notification carries the replacement indication and the first service capability layer identifier.

Based on the fifth aspect, in a second possible implementation manner, the gateway further includes:

a third sending unit, configured to send the first service capability layer identifier and the replacement indication to the server, so that the server sends the first service capability layer identifier and the replacement indication to the Second gateway.

Based on the fifth aspect or the first possible implementation manner of the fifth aspect, or the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the first gateway, according to the received a second message, the gateway information is updated to the device registered to the second gateway, where the gateway information includes a uniform resource locator of the service capability layer of the first gateway and a service capability layer of the second gateway. Resource locator.

Based on the fifth aspect, in a fourth possible implementation, the updating unit is specifically configured to:

Transmitting, by the first gateway, a third message to the device corresponding to the application resource that is included in the first gateway, where the third message includes a uniform resource locator of the service capability layer of the first gateway, and the second a uniform resource locator of the service capability layer of the gateway; the application resource refers to a corresponding resource of the device registered to the second gateway.

Based on the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner, the gateway further includes:

The fourth receiving unit is configured to receive a fourth message sent by the online device, where the fourth message carries the information that the online device receives the update message.

Based on the fourth possible implementation manner of the fifth aspect, in a sixth possible implementation manner, the gateway further includes:

a marking unit, configured to mark a device corresponding to the fourth message received by the fourth receiving unit.

Based on the fourth possible implementation manner of the fifth aspect, in a seventh possible implementation, the gateway further includes:

The processing unit is configured to determine whether the resource corresponding to the device that is not updated is expired, and if it is determined that the resource corresponding to the unupdated device is expired, the resource corresponding to the unupdated device is deleted.

In a sixth aspect, a gateway is provided, where the gateway includes:

a first sending unit, configured to send a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

a first receiving unit, configured to receive a gateway replacement identifier sent by the server, where the gateway replacement identifier is used to identify a gateway replacement;

a second sending unit, configured to send, to the first gateway, a second service capability layer identifier of the second gateway and the gateway replacement identifier;

a second receiving unit, configured to receive a first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource;

And a third sending unit, configured to send a second message to the first gateway, where the second message includes resource information corresponding to the device that is stored by the second gateway and registered to the second gateway.

Based on the sixth aspect, in a first possible implementation manner, the gateway further includes:

And a third receiving unit, configured to receive the first service capability layer identifier and the replacement indication of the first gateway sent by the first gateway, where the gateway replacement identifier further includes the first service capability layer identifier.

According to the sixth aspect, or the first possible implementation manner of the sixth aspect, in a second possible implementation, the gateway, further includes: a fourth receiving unit, configured to receive a gateway replacement identifier sent by the server And waiting for instructions.

Based on the sixth aspect or the first possible implementation manner of the sixth aspect, in a third possible implementation manner, the gateway further includes:

a fifth receiving unit, configured to receive a uniform resource locator and a replacement indication of a service capability layer of the first gateway sent by the server;

The fourth possible implementation manner of the sixth aspect or the sixth aspect or the second possible implementation manner of the sixth aspect or the second possible implementation manner of the sixth aspect, in the fourth possible implementation manner The gateway further includes:

a sixth receiving unit, configured to receive an acknowledgement message sent by the first gateway;

The processing unit is configured to go offline according to the confirmation message received by the sixth receiving unit, where the confirmation message is used to confirm that the first gateway receives the second message.

The gateway replacement method provided by the embodiment of the present invention can implement the replacement of the gateway with the service capability layer. Before the replaced gateway replaces the stored information transmission fee with the gateway, it needs to replace the verification of the macro access server, at the gateway. Before the replacement is completed, the replaced gateway works normally and will not go offline before the replacement is completed. It can ensure that the device registered to the replaced gateway can work normally.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments or the description of the prior art will be briefly described below. It is obvious that the drawings in the following description are only the present invention. For some embodiments, other drawings may be obtained from those of ordinary skill in the art in light of the inventive workability.

1 is a schematic structural diagram of an embodiment of the present invention;

2 is a flowchart of an embodiment of a gateway replacement method according to an embodiment of the present invention;

3 is a flowchart of an embodiment of a gateway replacement method according to an embodiment of the present invention;

4 is a flowchart of an embodiment of a gateway replacement method according to an embodiment of the present invention;

FIG. 5 is an interaction diagram of an embodiment of a gateway replacement method according to an embodiment of the present invention;

FIG. 6 is an interaction diagram of an embodiment of a gateway replacement method according to an embodiment of the present invention;

FIG. 7 is an interaction diagram of an embodiment of a gateway replacement method according to an embodiment of the present invention;

FIG. 8 is an interaction diagram of an embodiment of a gateway replacement method according to an embodiment of the present invention;

FIG. 9 is a structural diagram of an embodiment of a server according to an embodiment of the present invention;

FIG. 10 is a structural diagram of an embodiment of a gateway according to an embodiment of the present invention;

FIG. 11 is a structural diagram of an embodiment of a gateway according to an embodiment of the present invention;

FIG. 12 is a structural diagram of an embodiment of a server according to an embodiment of the present invention;

FIG. 13 is a structural diagram of an embodiment of a gateway according to an embodiment of the present invention;

FIG. 14 is a structural diagram of an embodiment of a gateway according to an embodiment of the present invention.

detailed description

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments.

1 is an architectural diagram of a gateway replacement method according to an embodiment of the present invention. As shown in FIG. 1 , an application architecture of the method mainly includes a second gateway 20, a first gateway 10 and a server 30, and a second gateway 20 is registered. At least one device 40, wherein the device 40 may be an M2M terminal with service capability or an M2M terminal without service capability, and both the first gateway 10 and the second gateway 20 have service capabilities, and the second gateway 20 The second gateway 20 stores the information of all the devices registered to the second gateway 20, with the second gateway service capability layer identifier (English name: Gateway Service Capability Layer Identity, GSCL ID). In a specific case, the second gateway 20 needs to be replaced, and the second gateway 20 is replaced by the first gateway 10. Before the first gateway 10 joins the network for communication, a verification and security protection process is required, where authentication and security protection are performed. The process may be a process of a bootstrap process and a service connection, where the bootstrap process obtains a first service capability layer identifier (GSCL ID) for the first gateway, a service connection process generates a corresponding key, and a key and a SCL ID are provided. The network service capability layer (NSCL) of the server 30 stores the related data for authenticating the first gateway 10 in the server 30.

Based on the architecture shown in FIG. 1 , an embodiment of the present invention provides a gateway replacement method. The method is deployed in a server 30 having a service capability layer. As shown in FIG. 2, the method includes:

The server receives the gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway.

202. The server generates a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement.

203. The server sends the gateway replacement identifier to the second gateway.

204. The server receives a request for creating a resource sent by the first gateway, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, and the service capability of the second gateway The layer identifier and the gateway replacement identifier are sent by the second gateway or server to the first gateway;

205. The server updates the service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is replaced by the server according to the gateway. The notification or the creation of the resource request is obtained;

In different embodiments, the first service capability layer identifier may be obtained in different manners, for example, may be carried in a gateway replacement notification, or may be carried in a resource creation request.

206. The server sends a first message to the first gateway, where the first message carries information that the server has successfully updated the service capability layer resource.

In different embodiments, the initiator of the replacement process is different, and therefore, the information carried in different notifications is also different. For example, in an implementation manner, the replacement process may be initiated by the first gateway, where the gateway replacement notification further includes a first service capability layer identifier of the first gateway, the first service capability layer identifier and the replacement The indication is sent by the first gateway to the second gateway, a more specific embodiment, which will be described later.

In another embodiment, the gateway replacement notification further includes a first service capability layer identifier of the first gateway; and the receiving the gateway replacement notification sent by the second gateway, before:

Receiving, by the server, a first service capability layer identifier and a replacement indication sent by the first gateway;

In the foregoing two implementation manners, the gateway replacement identifier is generated when the first service capability layer identifier is valid, and before the generating gateway replaces the identifier, the method further includes:

Detecting whether the first service capability layer identifier is valid;

In an implementation manner in which the second gateway initiates the replacement process, after receiving the gateway replacement notification sent by the second gateway, the method further includes:

The server checks whether the second gateway can be replaced;

The server generates the gateway replacement identifier when the server is replaceable by the second gateway.

While the server sends the gateway replacement identifier to the second gateway, the server further sends a waiting indication to the second gateway, where the waiting indication is used to indicate that the second gateway needs to wait for an offline indication. That is to say, after waiting for the first gateway to join, the second gateway can go offline to ensure normal operation of the system.

After the server sends the first message to the first gateway, the method further includes:

The server sends a notification to the second gateway, where the notification carries the first indication and a uniform resource locator of the first gateway service capability layer, where the first indication is used to indicate that the gateway is replaced. to make.

Through the above embodiments, the replacement of the gateway with the service capability layer can be implemented. Before the replaced gateway replaces the information sent by the gateway to replace the gateway, the verification of the macro access server needs to be replaced, and before the gateway replacement is completed, The replacement gateway works normally and will not go offline before the replacement is completed. It can ensure that the device registered to the replaced gateway can work normally.

As shown in FIG. 3, based on the architecture shown in FIG. 1, the embodiment of the present invention further provides a gateway replacement method. The execution body in this embodiment is the first gateway 10 in FIG. The methods described include:

301. The first gateway receives a gateway replacement identifier sent by the second gateway and a second service capability layer identifier of the second gateway.

302. The first gateway sends a request for creating a resource to the server, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, where the creation resource request triggers Updating, by the server, the service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is included in the creation resource request or the gateway replacement sent by the second gateway In the notice;

303. The first gateway receives a first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource.

304. The first gateway receives the second message sent by the second gateway, where the second message includes resource information corresponding to the device that is stored by the second gateway and is registered to the second gateway.

305. The first gateway updates the gateway information to the device registered to the second gateway according to the received second message.

In an embodiment, before receiving the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway, the first gateway further includes:

In the second implementation, the first gateway receives the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway, where the gateway replacement identifier is sent by the server and sent to the The second gateway; before, it also includes:

Transmitting, by the first gateway, the first service capability layer identifier and the replacement finger to the server So that the server sends the first service capability layer identifier and the replacement indication to the second gateway.

According to any of the foregoing two implementation manners, the gateway information includes a uniform resource locator of a service capability layer of the first gateway and a uniform resource locator of a service capability layer of the second gateway.

After the first gateway is successfully replaced, in step 305, the first gateway updates the gateway information to the device registered on the second gateway according to the received second message, which specifically includes:

The first gateway sends a third message to the device corresponding to the application resource that is included in the first gateway, where the third message includes a uniform resource locator of the service capability layer of the first gateway and a service of the second gateway. A uniform resource locator of the capability layer, where the application resource refers to a corresponding resource of the device registered to the second gateway.

After the first gateway sends a third message to the device corresponding to the application resource of the first gateway, the first gateway receives a fourth message sent by the online device, where the fourth message is received by the online device. The information of the update message.

Further, the fourth message further carries the information that the online device updates the uniform resource locator of the service capability layer of the second gateway to the uniform resource locator of the service capability layer of the first gateway.

After the first gateway receives the fourth message of the online device, the method further includes:

The first gateway marks the online device corresponding to the fourth message received by the first gateway;

The first gateway updates the gateway information to the device registered to the second gateway according to the received second information, and further includes:

Correspondingly, as shown in FIG. 4, based on the network architecture shown in FIG. 1, the embodiment of the present invention further provides a gateway replacement method. In this embodiment, the execution entity is the second gateway 20 in FIG. The gateway to be replaced, in this embodiment, the method includes:

401. The second gateway sends a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway.

The second gateway receives the gateway replacement identifier sent by the server, where the gateway replacement identifier is generated by the server, and the gateway replacement identifier is used to identify the gateway replacement.

403. The second gateway sends, to the first gateway, a second service capability layer identifier of the second gateway and the gateway replacement identifier.

404. The second gateway receives the first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource.

405. The second gateway sends a second message to the first gateway, where the second message information includes resource information corresponding to the device registered by the second gateway and registered to the second gateway.

In the first embodiment, before step 401, the method further includes:

The second gateway receives the first service capability layer identifier and the replacement indication of the first gateway sent by the first gateway, where the gateway replacement identifier further includes the first service capability layer identifier.

In another embodiment, step 401, after that, further includes:

The second gateway receives the illustrated gateway replacement identifier and the waiting indication sent by the server.

Step 403, before, further includes:

Receiving, by the second gateway, a uniform resource locator of the service capability layer of the first gateway that is sent by the server, and the replacement indication;

Step 405, after that, further includes:

After receiving the acknowledgement message sent by the first gateway, the second gateway goes offline, and the acknowledgement message is used to confirm that the first gateway receives the storage device message.

In conjunction with the gateway replacement method provided by the foregoing three embodiments of FIG. 2 to FIG. 4, an interaction diagram of three implementation manners of the gateway replacement method provided by the embodiment of the present invention is described below, as shown in FIG. 5, in the first implementation manner. in:

Before the first gateway joins the network for communication, the process of the Bootstrap process and the service connection is required. Through the two processes, the first gateway obtains the SCL ID and generates a corresponding key, and the NSCL also obtains the first gateway. Information about rights;

501. The first gateway sends a first GSCL ID and a replacement indication of the first gateway to the second gateway.

502. The message that the second gateway receives the first gateway includes the first GSCL ID and the replacement finger. The second gateway sends a gateway replacement notification to the NSCL of the server, where the gateway replacement notification carries the replacement indication and the first GSCL ID.

503. The NSCL of the server detects whether the first GSCL ID is valid.

Specifically, the NSCL detects whether the first GSCL ID is verified by the MSBF and the MAS. If the first GSCL ID is valid, step 504 is performed, and if invalid, a reject message is sent to the second gateway.

504. The NSCL allocates a gateway replacement identifier and replies to the second gateway.

505. The second gateway sends the second GSCL ID of the second gateway and the gateway replacement identifier to the first gateway.

506. The first gateway sends a create resource request message to the NSCL, where the create resource request carries the second GSCL ID and the gateway replacement identifier.

507. The NSCL updates the SCL resource created by the server for the second gateway according to the second GSCL ID, the first GSCL ID, and the network replacement identifier.

Specifically, the NSCL detects the content in the created resource message sent by the first gateway, and if the created resource message carries the replacement identifier, it indicates that the created resource message is used for updating the resource, so the NSCL is configured according to the second gateway. The GSCL ID finds a resource registered by the second gateway on the network side, and the server compares the content included in the resource with the content in the created resource request sent by the first gateway, and updates different content, and maintains the same content. constant.

508. The NSCL sends a first message to the first gateway, where the first message carries information that the service capability layer resource has been successfully updated.

509. The first gateway replies to the second gateway, indicating that the NSCL resource is successfully updated.

510. The second gateway sends the second message information to the first gateway, and goes offline.

The second message includes information about the device registered by the second gateway and registered to the second gateway, for example, the time of the device registration, the attribute of the device, the content stored by the device to the gateway, and the like. The device here can also be an application.

511. The first gateway updates the gateway information of the device registered to the second gateway according to the information included in the received second message.

For example, where the gateway information is updated, including the URI of the first gateway and the URI of the second gateway.

More specifically, in step 511, the first gateway updates the addressing information to the device registered to the gateway, which can be implemented by the process shown in FIG. 6, and the second gateway has been offline.

601. The first gateway sends a third message to a device corresponding to all application resources of the first gateway.

Specifically, the first gateway may send an update message by using a multicast mode or a broadcast, where the update message includes a URI of the second gateway and a URI of the first gateway. The third message includes a uniform resource locator of the service capability layer of the second gateway and a uniform resource locator of the service capability layer of the second gateway; the application resource refers to the registration to the second gateway The corresponding resource of the device on it.

602. The online device receives the third message of the first gateway, finds a corresponding resource according to the URI of the second gateway, and then updates the URI of the second gateway to a URI of the first gateway, and then passes the fourth The message replies to the first gateway, and the fourth message indicates that the online device receives the update message.

603. The first gateway sets a flag for the application resource corresponding to the replied device, indicating that the device has been updated.

At the same time, the expiration time of the resource corresponding to the unupdated device is checked, and it is judged whether it is expired. If it expires, the resource is deleted; a timer is set to count the time when the update message is sent.

604. The sleep terminal is online.

Specifically, the online dormant terminal sends a message to the app resource second gateway, but since the second gateway is offline, the online dormant terminal does not receive any reply.

At this point, the sleeping terminal on the line starts the timer and waits for the update message; if it receives the update message, it stops the timer.

605. The timer of the first gateway sends the multicast update message again after the time expires.

606. The online dormant terminal receives the update message stop timer and replies to the first gateway updated information.

If the sleeping terminal that went online during the entire timer has not received any update message, the gateway is reselected.

7 is an interaction diagram of another embodiment of a gateway replacement method. Compared with the embodiment shown in FIG. 5, the difference is that there is no communication mechanism between the first gateway and the second gateway. Therefore, the first gateway is The first GSCL ID and the gateway replacement indication that need to be sent to the second gateway need to be transited through the NSCL of the server. Therefore, before the second gateway sends the gateway replacement notification to the server, the method further includes:

The first gateway sends a first service capability layer identifier and a replacement indication to the server;

The rest of the steps are the same as those of the embodiment shown in FIG. 5, and therefore will not be described again.

FIG. 8 is an interaction diagram of another implementation manner of a gateway replacement method. In this embodiment, a replacement flow is used. The process is initiated by the second gateway. As can be seen from FIG. 8, the method includes:

801. The second gateway sends a gateway replacement notification to the NSCL of the server, where the gateway replacement notification carries a replacement indication.

802. The NSCL checks the rights of the second gateway.

Specifically, the second gateway writes its own attribute to the created resource when registering, and the NSCL detects whether the second gateway has the replaced right, so as to prevent the criminal from randomly replacing the gateway. This permission is saved in the properties of the second gateway.

After the verification is passed, step 803 is performed, otherwise a rejection message is sent to the second gateway.

803. The NSCL generates a gateway replacement identifier and sends the identifier to the second gateway, and sends a waiting indication to the second gateway.

Specifically, the second gateway receives the waiting indication sent by the NSCL, that is, the second gateway is not available in the following line, and needs to wait for the first gateway to join, and can be offline when it can work instead. Thereafter, the second gateway waits for the first gateway to join and continues to work.

After step 803, in 804, the second gateway needs to interact with the first gateway to send the second GSCL ID of the second gateway and the gateway replacement identifier to the first gateway. Specifically, the first gateway and the second gateway may perform information interaction by using a wired manner or a wireless local area network manner.

805. The first gateway sends a resource request to the NSCL, where the second GSCL ID of the second gateway, the first GSCL ID, and the gateway replacement identifier are included.

806. The NSCL verifies the validity of the first gateway, and then the NSCL updates the SCL resource that the server created for the second gateway according to the first GSCLID, the second GSCL ID, and the replacement identifier.

The NSCL detects the content in the created resource message sent by the first gateway, and if the replacement identifier is carried, it indicates that the message is used for updating the resource, so the NSCL finds the second gateway according to the second GSCL ID of the second gateway. The resource registered on the network side, the server compares the content included in the resource to the content of the created resource request sent by the first gateway, and updates different content, and the same remains unchanged.

808. The NSCL sends a notification to the second gateway, where the notification carries the first indication and a uniform resource locator of the first gateway service capability layer.

809. The GSCL of the second gateway replies to the NSCL of the server, and notifies the user that the notification is received;

810. The GSCL of the second gateway sends the stored resource information to the GSCL of the first gateway by using a second message according to the GSCL URI of the first gateway.

811. The GSCL of the first gateway replies to the GSCL of the second gateway, and indicates that the second message sent by the second gateway is received.

Specifically, similar to the foregoing embodiment, the second message includes information stored by the second gateway and registered to the device on the second gateway, for example:

The time when the device is registered, the attributes of the device, the contents of the device stored on the gateway, and so on. The device here can also be an application.

812, the GSCL of the second gateway is offline;

813. The first gateway updates the gateway information to the device registered to the second gateway according to the received information in the second message, where the gateway information includes a new URI and an old URI.

Specifically, step 813 is similar to the embodiment shown in FIG. 6, and therefore, no further details are provided.

Correspondingly, as shown in FIG. 9, the embodiment of the present invention provides a server, and FIG. 9 is a schematic structural diagram of the embodiment. As shown in FIG. 9, the server includes:

The first receiving unit 901 is configured to receive, by the server, a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

The generating unit 902 is configured to generate a gateway replacement identifier, where the gateway replacement identifier is used to notify the network that the gateway replacement is to be performed;

The first sending unit 903 is configured to send the gateway replacement identifier to the second gateway.

The second receiving unit 904 is configured to receive a request for creating a resource that is sent by the first gateway, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, where The second service capability layer identifier and the gateway replacement identifier are sent by the second gateway or the server to the first gateway;

The updating unit 905 is configured to update the service capability layer resource according to the correspondence between the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is replaced by the server according to the gateway replacement notification Or the creation resource request is obtained;

The second sending unit 906 is configured to send a first message to the first gateway, where the first message carries information that the server has successfully updated the service capability layer resource.

In a possible implementation manner, the gateway replacement notification further includes a first service capability layer identifier of the first gateway, where the first service capability layer identifier and the replacement indication are sent by the first gateway to the Said second gateway.

The server further includes:

Optionally, the service server further includes:

The generating unit is further configured to generate the gateway replacement identifier when the first service capability layer identifier is valid.

In another possible implementation manner, the server further includes:

a verification unit, configured to verify whether the second gateway can be replaced;

The generating unit 902 is further configured to generate the gateway replacement identifier when the second gateway can be replaced.

Optionally, the second sending unit is further configured to send a waiting indication to the second gateway, to notify the second gateway that the offline indication needs to be waited for.

Optionally, the server further includes:

The server provided by the embodiment of the present invention can implement the replacement of the gateway with the service capability layer. Before the replaced gateway replaces the gateway with the information transmission fee, the gateway needs to replace the macro access server. It is verified that the replaced gateway works normally before the gateway replacement is completed, and will not go offline before the replacement is completed, so that the device registered to the replaced gateway can work normally.

Correspondingly, the embodiment of the present invention further provides a gateway, which may be, for example, the first gateway in FIG. 1 , and FIG. 10 is a structural diagram of the gateway. As shown in FIG. 10 , the gateway includes:

The first receiving unit 1001 is configured to receive a gateway replacement identifier sent by the second gateway and a second service capability layer identifier of the second gateway, where the gateway replacement identifier is generated by the server and sent to the second gateway.

The first sending unit 1002 is configured to send a request for creating a resource to the server, where the created resource carries the second service capability layer identifier and the gateway replacement identifier, and the created resource request server is configured according to the first service. The relationship between the capability layer identifier and the second service capability layer identifier is updated. a service capability layer resource, where the first service capability layer identifier is included in the creation resource request or the gateway replacement notification sent by the second gateway;

The second receiving unit 1003 is configured to receive a first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

The third receiving unit 1004 is configured to receive a second message sent by the second gateway, where the second message includes resource information corresponding to the device that is stored by the second gateway and registered to the second gateway;

The updating unit 1005 is configured to update the gateway information to the device registered on the second gateway according to the second message received by the third receiving unit.

In an embodiment, the gateway further includes:

a second sending unit, configured to send, to the second gateway, the first service capability layer identifier and the replacement indication of the first gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the second gateway The second gateway sends a network replacement notification to the server, where the gateway replacement notification carries the replacement indication and the first service capability layer identifier.

Optionally, the gateway further includes: a third sending unit, configured to send the first service capability layer identifier and the replacement indication to the server, so that the server identifies the first service capability layer and the The replacement indication is sent to the second gateway.

Optionally, the updating unit is configured to send a third message to the device corresponding to the application resource that is included in the first gateway, where the third message includes a uniform resource location of the service capability layer of the first gateway. And a uniform resource locator of the service capability layer of the second gateway; the application resource refers to a corresponding resource of the device registered to the second gateway.

Optionally, the gateway further includes:

The fourth receiving unit is configured to receive a fourth message sent by the online device, where the fourth message carries information that the online device receives the update message.

Optionally, the gateway further includes:

The gateway provided by the embodiment of the present invention can implement the replacement of the gateway with the service capability layer. Before the replaced gateway replaces the gateway with the information transmission fee, the gateway needs to replace the macro access server. Verify that the replaced gateway is working properly before the gateway replacement is completed. If the replacement is not completed before the replacement is completed, it can ensure that the device registered to the replaced gateway can work normally.

Correspondingly, the embodiment of the present invention further provides a gateway, which may be, for example, the second gateway in FIG. 1 , and FIG. 11 is a structural diagram of the gateway. As shown in FIG. 11 , the gateway includes:

a first sending unit 1101, configured to send a network replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

The first receiving unit 1102 is configured to receive a gateway replacement identifier sent by the server, where the gateway replacement identifier is generated by a server, and the gateway replacement identifier is used to identify a gateway replacement.

The second sending unit 1103 is configured to send, by the first gateway, its second service capability layer identifier and the gateway replacement identifier.

a second receiving unit 1104, configured to receive a first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource;

The third sending unit 1105 is configured to send second information to the first gateway, where the second information includes resource information corresponding to the device registered by the second gateway and registered to the second gateway.

In an embodiment, the gateway further includes:

a third receiving unit, configured to receive the first service capability layer identifier and the replacement indication sent by the first gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway, where the gateway is replaced The identifier further includes the first service capability layer identifier, where the gateway replacement notification carries a replacement indication and a first service capability layer identifier of the first gateway.

And a fourth receiving unit, configured to receive the gateway replacement identifier and the waiting indication sent by the server.

In another implementation manner, the gateway further includes:

Optionally, the gateway further includes:

The above-mentioned server and gateway can respectively perform the method of the foregoing method embodiment, and details are not described herein again.

As shown in FIG. 12, an embodiment of the present invention provides a server, where the server may be deployed to perform the method shown in FIG. 2 of the embodiment of the present invention; as shown in FIG. 12, the server includes a network interface 1201 and a processor. 1202 and memory 1203. System bus 1204 is used to connect network interface 1201, processor 1202, and memory 1203.

Network interface 1201 is used to communicate with other network nodes.

The memory 1203 is used to store programs. In particular, the program can include program code, the program code including computer operating instructions. The memory 1203 may include a high speed random access memory (RAM) memory, and may also include a non-volatile memory such as at least one disk memory. A device driver may also be included in the memory 1203.

The processor 1202 executes a program stored in the memory 1203 for performing:

Receiving a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

Generating a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement;

Sending the gateway replacement identifier to the second gateway;

And receiving, by the first gateway, a request for creating a resource, where the request for creating a resource carries a second service capability layer identifier of the second gateway, and the gateway replacement identifier, where the second service capability layer identifier is The gateway replacement identifier is sent by the second gateway or the server to the first gateway;

Updating the service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is obtained by the server according to the gateway replacement notification or the resource creation request;

Sending a first message to the first gateway, where the first message carries information that the server has successfully updated the service capability layer resource.

It should be noted that the processor 1202 may further perform other steps in the corresponding method embodiments, and details are not described herein again.

As shown in FIG. 34, the embodiment of the present invention further provides a gateway, which is used to perform the method shown in FIG. 3 in the embodiment of the present invention; as shown in FIG. 13, the gateway includes a network interface 1301 and a processor. 1302 and memory 1303. System bus 1304 is used to connect network interface 1301, processor 1302, and memory 1403.

Network interface 1301 is used to communicate with other network nodes.

The memory 1303 is used to store programs. In particular, the program can include program code, the program code including computer operating instructions. The memory 1303 may include a high speed random access memory (RAM) memory, and may also include a non-volatile memory such as at least one disk memory. A device driver may also be included in the memory 1303.

The processor 1302 executes a program stored in the memory 1303 for executing:

Receiving, by the second gateway, a gateway replacement identifier and a second service capability layer identifier of the second gateway;

Sending a request for creating a resource to the server, where the request for creating a resource carries the identifier of the second service capability layer and the gateway replacement identifier, where the request for creating a resource triggers the first service capability of the server according to the first gateway The layer identifier and the second service capability layer identifier are updated, and the first service capability layer identifier is included in the creation resource request or the gateway replacement notification sent by the second gateway;

Receiving a first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

Receiving a second message sent by the second gateway, where the second information includes resource information corresponding to a device registered by the second gateway and registered to the second gateway;

And updating the gateway information to the device registered to the second gateway according to the received second information.

It should be noted that the processor 1302 may further perform other steps in the corresponding method embodiments, and details are not described herein again.

As shown in FIG. 14, the embodiment of the present invention further provides a gateway, which is used to perform the method shown in FIG. 3 of the embodiment of the present invention; as shown in FIG. 14, the gateway includes a network interface 1301 and a processor 1402. And memory 1403. The system bus 1404 is used to connect the network interface 1401, the processor 1402, and the memory 1403.

Network interface 1401 is used to communicate with other network nodes.

The memory 1403 is used to store programs. In particular, the program can include program code, the program code including computer operating instructions. The memory 1403 may include a high speed random access memory (RAM) memory, and may also include a non-volatile memory such as at least one disk memory. The device 1403 may further include a device driver program.

The processor 1402 executes a program stored in the memory 1403 for execution:

Sending a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

Receiving a gateway replacement identifier sent by the server, where the gateway replacement identifier is used to identify a gateway replacement;

Sending, by the first gateway, a second service capability layer identifier of the second gateway and the gateway replacement identifier;

Receiving, by the first gateway, the first message, where the first message carries information that the server has successfully created the service capability layer resource;

Sending a second message to the first gateway, where the second message includes resource information corresponding to the device registered by the second gateway and registered to the second gateway.

It should be noted that the processor 1402 may further perform other steps in the corresponding method embodiments, and details are not described herein again.

A person skilled in the art should further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. All modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

A gateway replacement method, the method comprising:

Receiving, by the server, a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

The server generates a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement;

Sending, by the server, the gateway replacement identifier to the second gateway;

The server receives a request for creating a resource that is sent by the first gateway, where the request for creating a resource carries a second service capability layer identifier of the second gateway and the gateway replacement identifier, where the second service capability layer identifier And the gateway replacement identifier is sent by the second gateway or the server to the first gateway;

The server updates the service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is requested by the server according to the gateway replacement notification or the resource creation request. obtain;

The server sends a first message to the first gateway, where the first message carries information that the server has successfully created the service capability layer resource.
The method according to claim 1, wherein the gateway replacement notification further includes the first service capability layer identifier of the first gateway.
The method according to claim 1 or 2, wherein the first service capability layer identifier and the replacement indication are sent by the first gateway to the second gateway.
The method according to claim 1 or 2, wherein before the server receives the gateway replacement notification sent by the second gateway, the method further includes:

Receiving, by the server, the first service capability layer identifier and the replacement indication sent by the first gateway;

The server sends the first service capability layer identifier and the replacement indication to the second gateway.
The method according to claim 2 or 3, wherein before the server generates the gateway replacement identifier, the method further includes:

The server detects whether the first service capability layer identifier is valid;

The server generates the gateway replacement identifier when the first service capability layer identifier is valid.
The method of claim 1, wherein after the server receives the gateway replacement notification sent by the second gateway, the method further includes:

The server checks whether the second gateway can be replaced;

The server generates the gateway replacement identifier when the second gateway can be replaced.
The method according to claim 1, wherein the server sends a waiting indication to the second gateway while transmitting the gateway replacement identifier to the second gateway, where the waiting indication is used to indicate The second gateway needs to wait for the offline indication.
The method according to claim 1, wherein after the server sends the first message to the first gateway, the method further includes:

The server sends a notification to the second gateway, where the notification carries a first indication and a uniform resource locator of the first gateway service capability layer, where the first indication is used to indicate that the gateway replacement is completed.
A gateway replacement method, the method comprising:

The first gateway receives the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway;

The first gateway sends a request for creating a resource to the server, where the request for creating a resource carries the identifier of the second service capability layer and the gateway replacement identifier, where the request for creating a resource triggers the server according to the first gateway. The first service capability layer identifier and the second service capability layer identifier are updated, and the first service capability layer identifier is included in the creation resource request or the gateway replacement notification sent by the second gateway. ;

Receiving, by the first gateway, the first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

The first gateway receives the second message sent by the second gateway, where the second information includes resource information corresponding to the device registered by the second gateway and registered to the second gateway;

The first gateway updates the gateway information to the device registered to the second gateway according to the received second information.
The method according to claim 9, wherein the first gateway, before receiving the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway, further includes:

The first gateway sends the first service capability layer identifier and the replacement indication of the first gateway to the second gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway. The second gateway is configured to send the gateway replacement notification to the server, where the gateway replacement notification carries the replacement indication and the first service capability layer identifier.
The method of claim 9, wherein the first gateway receives the gateway replacement identifier sent by the second gateway and the second service capability layer identifier of the second gateway;

Sending, by the first gateway, the first service capability layer identifier and the replacement indication to the server, so that the server sends the first service capability layer identifier and the replacement indication to the second gateway .
The method according to any one of claims 9 to 11, wherein the gateway information comprises a uniform resource locator of a service capability layer of the first gateway and a uniform resource of a service capability layer of the second gateway. Locator.
The method according to claim 9, wherein the first gateway updates the gateway information to the device registered to the second gateway according to the received second message, which specifically includes:

Transmitting, by the first gateway, a third message to the device corresponding to the application resource that is included in the first gateway, where the third message includes a uniform resource locator of the service capability layer of the first gateway, and the second gateway The uniform resource locator of the service capability layer; the application resource refers to the corresponding resource of the device registered to the second gateway.
The method of claim 13, after the third gateway sends a third message to the device corresponding to the application resource of the first gateway,

The first gateway receives a fourth message sent by the online device, where the fourth message carries information that the online device receives the update message.
The method of claim 14, wherein the fourth message further carries the online device to update a uniform resource locator of the service capability layer of the second gateway as a unified service capability layer of the first gateway. Resource locator information.
The method according to claim 13, wherein after the first gateway receives the fourth message of the online device, the method further includes:

The first gateway marks the online device corresponding to the fourth message received by the first gateway.
The method of claim 13, wherein the first gateway updates the gateway information to the device registered to the second gateway according to the received second information, and further includes:

The first gateway checks whether the resource corresponding to the device that is not updated expires, and if it expires, deletes the resource corresponding to the device that is not updated.
A gateway replacement method, characterized in that the method comprises:

The second gateway sends a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

The second gateway receives a gateway replacement identifier sent by the server, where the gateway replaces the identifier Replace the identity gateway;

Sending, by the second gateway, the second service capability layer identifier of the second gateway and the gateway replacement identifier to the first gateway;

Receiving, by the second gateway, the first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource;

The second gateway sends a second message to the first gateway, where the second message includes resource information corresponding to the device registered by the second gateway and registered to the second gateway.
The method of claim 18, wherein before the second gateway sends a gateway replacement notification to the server, the method further includes:

The second gateway receives the first service capability layer identifier and the replacement indication of the first gateway sent by the first gateway, and the gateway replacement identifier further includes the first service capability layer identifier.
The method of claim 18, wherein the second gateway sends a network replacement notification to the server, where the gateway replacement notification carries a replacement indication, and thereafter, the method further includes:

The second gateway receives the gateway replacement identifier and the waiting indication sent by the server.
The method according to claim 18, wherein the second gateway sends the second service capability layer identifier and the gateway replacement identifier of the second gateway to the first gateway; :

The second gateway receives the uniform resource locator of the service capability layer of the first gateway and the replacement indication sent by the server.
The method of claim 18, wherein

The second gateway sends a second message to the first gateway, where the second message includes resource information corresponding to the device that is stored by the second gateway and is registered to the second gateway, and then includes:

After receiving the acknowledgement message sent by the first gateway, the second gateway goes offline, and the acknowledgement message is used to confirm that the first gateway receives the second message.
A server, comprising:

a first receiving unit, configured to receive, by the server, a gateway replacement notification sent by the second gateway, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

a generating unit, configured to generate a gateway replacement identifier, where the gateway replacement identifier is used to identify a gateway replacement;

a first sending unit, configured to send the gateway replacement identifier to the second gateway;

a second receiving unit, configured to receive a request for creating a resource sent by the first gateway, where the resource is created The source request carries the second service capability layer identifier of the second gateway and the gateway replacement identifier, where the second service capability layer identifier and the gateway replacement identifier are sent by the second gateway or the server The first gateway;

An update unit, configured to update a service capability layer resource according to the first service capability layer identifier and the second service capability layer identifier, where the first service capability layer identifier is replaced by the server according to the gateway replacement notification or the creation Resource request is obtained;

The second sending unit is configured to send a first message to the first gateway, where the first message carries information that the server has successfully updated the service capability layer resource.
The server according to claim 23, wherein the gateway replacement notification further includes the first service capability layer identifier of the first gateway;
The server according to claim 23 or 24, wherein the first service capability layer identifier and the replacement indication are sent by the first gateway to the second gateway.
The server according to claim 23, wherein the gateway replacement notification further includes a first service capability layer identifier of the first gateway; the server further includes:

a third receiving unit, configured to receive a first service capability layer identifier and a replacement indication sent by the first gateway;

And a third sending unit, configured to send the first service capability layer identifier and the replacement indication to the second gateway.
The server according to claim 24 or 25, wherein the server further comprises:

The detecting unit is configured to detect whether the first service capability layer identifier is valid.

The generating unit is further configured to generate the gateway replacement identifier when the first service capability layer identifier is valid.
The server according to claim 23, wherein the second sending unit is further configured to send a waiting indication to the second gateway, to notify the second gateway that it needs to wait for an offline indication.
The server of claim 23, further comprising:

a fourth sending unit, configured to send a notification to the second gateway, where the notification carries the first indication and a uniform resource locator of the first gateway service capability layer, where the first indication is used to indicate a gateway Replacement is complete.
A gateway, characterized in that

a first receiving unit, configured to receive a gateway replacement identifier sent by the second gateway and a second service capability layer identifier of the second gateway;

a first sending unit, configured to send a request for creating a resource to the server, where the request for creating a resource carries the identifier of the second service capability layer and the gateway replacement identifier, where the request for creating a resource triggers the server according to the The first service capability layer identifier and the second service capability layer identifier of the first gateway are updated, and the service capability layer resource is updated, where the first service capability layer identifier is included in the creation resource request or sent by the second gateway. Gateway replacement notification;

a second receiving unit, configured to receive a first message sent by the server, where the first message carries information that the server has successfully created the service capability layer resource;

a third receiving unit, configured to receive a second message sent by the second gateway, where the second message includes resource information corresponding to a device that is stored by the second gateway and registered to the second gateway;

And an updating unit, configured to update the gateway information to the device registered to the second gateway according to the second message received by the third receiving unit.
The gateway of claim 30, further comprising:

a second sending unit, configured to send, to the second gateway, a first service capability layer identifier and a replacement indication of the first gateway, where the replacement indication is used to indicate that the second gateway is to be replaced by the second gateway The second gateway sends a network replacement notification to the server, where the gateway replacement notification carries the replacement indication and the first service capability layer identifier.
The gateway of claim 30, further comprising:

a third sending unit, configured to send the first service capability layer identifier and the replacement indication to the server, so that the server sends the first service capability layer identifier and the replacement indication to the Second gateway.
The gateway according to any one of claims 30 to 32, wherein the gateway information comprises a uniform resource locator of the service capability layer of the first gateway and a uniform resource locator of the service capability layer of the second gateway. .
The gateway according to claim 33, wherein the updating unit is specifically configured to:

Transmitting, by the device corresponding to the application resource that is included in the first gateway, a third message, where the third message includes a uniform resource locator of the service capability layer of the first gateway and a service capability layer of the second gateway a uniform resource locator; the application resource refers to a corresponding resource of the device registered to the second gateway.
The gateway of claim 34, further comprising:

The fourth receiving unit is configured to receive a fourth message sent by the online device, where the fourth message carries information that the online device receives the update message.
The gateway of claim 34, further comprising:

a marking unit, configured to mark a device corresponding to the fourth message received by the fourth receiving unit.
The gateway of claim 34, further comprising:

The processing unit is configured to determine whether the resource corresponding to the device that is not updated is expired, and if it is determined that the resource corresponding to the unupdated device is expired, the resource corresponding to the unupdated device is deleted.
A gateway, characterized in that:

a first sending unit, configured to send a gateway replacement notification to the server, where the gateway replacement notification carries a replacement indication, where the replacement indication is used to indicate that the second gateway is to be replaced by the first gateway;

a first receiving unit, configured to receive a gateway replacement identifier sent by the server, where the gateway replacement identifier is used to identify a gateway replacement;

a second sending unit, configured to send, to the first gateway, a second service capability layer identifier of the second gateway and the gateway replacement identifier;

a second receiving unit, configured to receive a first message sent by the first gateway, where the first message carries information that the server has successfully created the service capability layer resource;

And a third sending unit, configured to send a second message to the first gateway, where the second message includes resource information corresponding to the device that is stored by the second gateway and registered to the second gateway.
The gateway of claim 38, further comprising:

And a third receiving unit, configured to receive the first service capability layer identifier and the replacement indication of the first gateway sent by the first gateway, where the gateway replacement identifier further includes the first service capability layer identifier.
The gateway according to claim 38 or 39, further comprising: a fourth receiving unit, configured to receive the gateway replacement identifier and the waiting indication sent by the server.
The gateway according to claim 38 or 39, further comprising:

The fifth receiving unit is configured to receive a uniform resource locator and a replacement indication of the service capability layer of the first gateway sent by the server.
The gateway according to any one of claims 38 to 41, further comprising:

a sixth receiving unit, configured to receive an acknowledgement message sent by the first gateway;

The processing unit is configured to go offline according to the confirmation message received by the sixth receiving unit, where the confirmation message is used to confirm that the first gateway receives the second message.