CN116418741A

CN116418741A - Method, device, communication equipment and readable storage medium for allocating identification

Info

Publication number: CN116418741A
Application number: CN202111648821.2A
Authority: CN
Inventors: 韩瑞波; 刘毅松; 李晗; 程伟强; 林洁; 宋开胜; 赵玉印; 刘少华; 姜文颖
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2023-07-11

Abstract

The application discloses a method and a device for distributing identifiers, communication equipment and a readable storage medium, and belongs to the technical field of communication. The scheme of the embodiment of the application comprises the following steps: the first equipment sends a first message which comprises a first field, wherein the first field is used for requesting the second equipment to allocate a first path and/or SID of a first service for the first equipment and receiving the allocated target SID from the target second equipment; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; alternatively, the first device is a DHCPv6 server and the second device is a DHCPv6 client. Therefore, the DHCPv6 can be expanded, and the SID is dynamically announced between the DHCPv6 server and the client, so that SRv messages can be normally received and transmitted between the DHCPv6 server and the client, and SRv protocol system operation is ensured.

Description

Method, device, communication equipment and readable storage medium for allocating identification

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method and a device for distributing an identifier, communication equipment and a readable storage medium.

Background

Currently SRv is a Segment Routing (SR) solution based on internet protocol version 6 (Internet Protocol Version, ipv 6) extensions. For the SRv solution, a Segment ID (SID) of an edge device of a dynamic host configuration protocol sixth edition (Dynamic Host Configuration Protocol Version, DHCPv 6) server, such as an operator network, is generated for calculation, and is dynamically updated along with the network status, while the SID of the DHCPv6 client is dynamically calculated based on the self-positioning Locator identifier. In this case, due to the management authority and security reasons, the DHCPv6 server and the client cannot interact with each other, so that SRv messages cannot be normally received and transmitted between the DHCPv6 server and the client, and the operation of the SRv protocol system is affected.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method, an apparatus, a communication device, and a readable storage medium for allocating an identifier, so as to solve the problem that an SID cannot be interacted between a DHCPv6 server and a client at present.

In order to solve the technical problems, the application is realized as follows:

in a first aspect, a method for allocating an identifier is provided, which is applied to a first device, and includes:

sending a first message; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a segment identification SID of a first service for the first device;

receiving a target SID from a target second device; wherein the target SID is a SID assigned by the target second device to the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

In a second aspect, there is provided a method of allocating an identifier, applied to a second device, including:

receiving a first message from a first device; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a SID of a first service to the first device;

transmitting the SID assigned thereto to the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

In a third aspect, an apparatus for allocating an identifier is provided, which is applied to a first device, and includes:

the first sending module is used for sending a first message; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a SID of a first service to the first device;

a first receiving module for receiving a target SID from a target second device; wherein the target SID is a SID assigned by the target second device to the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

In a fourth aspect, an apparatus for allocating an identifier is provided, where the apparatus is applied to a second device, and the apparatus includes:

the third receiving module is used for receiving the first message from the first equipment; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a SID of a first service to the first device;

a third transmitting module, configured to transmit the SID allocated thereto to the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

In a fifth aspect, embodiments of the present application provide a communications device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the method as described in the first aspect or implementing the steps of the method as described in the second aspect.

In a sixth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect.

In the embodiment of the application, a first message may be sent by a first device, where the first message includes a first field, where the first field is used to request a second device to allocate a first path and/or a SID of a first service to the first device, and receive a target SID allocated by the second device from a target second device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; alternatively, the first device is a DHCPv6 server and the second device is a DHCPv6 client. Therefore, the DHCPv6 can be expanded, and the SID is dynamically announced between the DHCPv6 server and the client, so that SRv messages can be normally received and transmitted between the DHCPv6 server and the client, and SRv protocol system operation is ensured.

Drawings

FIG. 1 is a schematic diagram of an SRH in an embodiment of the present application;

FIG. 2 is a schematic diagram of a SID format in an embodiment of the present application;

FIG. 3 is a flow chart of a method for assigning identifications provided by an embodiment of the present application;

FIG. 4 is a flow chart of another method of assigning identifications provided by embodiments of the present application;

FIG. 5 is a flow chart of a SID advertisement process in an embodiment of the present application;

fig. 6 is a schematic structural diagram of an apparatus for allocating an identifier according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of another apparatus for allocating identifiers according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.

To facilitate an understanding of the embodiments of the present application, the following is first described.

SRv6 is simply referred to as SR-IPv6, and refers to applying Segment Routing (SR) to an IPv6 forwarding plane, i.e., encapsulating an instruction list (SID list) of SR in an IPv6 message to direct the message to be forwarded according to source route. As shown in fig. 1, the IPv6 Header (Header) and the segment routing Header (Segment Routing Header, SRH) may have a Next Header value of 43 in the IPv6 Header, which indicates that the lower layer Header is a routing extension Header (Routing Extension Header). SRv6 the data plane may be encapsulated with a segment routing header (Segment Routing Header, SRH) in which segment list (segment list) information is encapsulated, each segment being a 128bit IPv6 address. SRv6 tunnels (tunnels) are the management entities of the corresponding SID list, presenting traffic as other tunnels. SRv6 tunnel is capable of carrying all types of payloads known as two-layer, three-layer, multiprotocol label switching (Multi-Protocol Label Switching, MPLS), transmission control protocol (Transmission Control Protocol, TCP) user datagram protocol (User Datagram Protocol, UDP), etc.

SRv6 the SID can be understood as the IP address of the router and the SID list characterizes the IP address list of the entire routing path. As shown in fig. 2, the SID of SRv6 may be a 128bit programmable SID, and may include Locator, function (fusion) and Arguments (ARGS). The Locator is a network node identifier in a SRv protocol system, which is an identifier allocated to a network node in a network topology and is used for forwarding a data packet to the network node. The route corresponding to the Locator is issued to the network by the network node through an Interior Gateway Protocol (IGP) for helping other devices forward the data packet to the node network issuing the Locator. In SRv SID, the Locator length is variable for adapting to different scale networks. The Locator can be subdivided into B and N, with B identification SRv SID blocks (blocks), typically assigned by the operator to a subnet, typically denoted by Prefix, and N being the identification of the distinct nodes within the subnet. Function (FUNCT) is used to express the operation code of the forwarding action to be performed, which corresponds to the computer instruction, and in SRv network programming, the different forwarding actions (Behavior) are described by functions, such as forwarding a packet to a specified link, or table lookup forwarding in a specified table, etc. Arguments (ARGS) is an optional field that is a parameter to which the instruction corresponds when executed, which may include data flow, services, or any other relevant information.

For the IPv6 protocol architecture, client devices such as optical network units (Optical Network Unit, ONUs), routers (routers), switches, etc. may cooperate with edge devices of the operator network such as broadband remote access servers (Broadband Remote Access Server, BRAS), full-Service Routers (SR), etc. to automatically obtain IPv6 addresses from the BRAS/SR via the DHCPv6 protocol. The BRAS/SR has directly host routes/direct routes for downstream devices, with client device default routes pointing to the BRAS/SR.

Alternatively, in embodiments of the present application, the DHCPv6 client may include, but is not limited to, a 4G/5G device, a small switch, a router, and other client-side devices. The DHCPv6 server may be an edge device of the operator network, such as a BRAS, SR, etc.

Optionally, the SID in the embodiment of the present application is specifically a SID of SRv.

In order to solve the problem that the SID cannot be interacted between the DHCPv6 server and the client, the embodiment of the application expands the DHCPv6 and provides a dynamic notification SID between the DHCPv6 server and the client, so that SRv messages can be normally received and transmitted between the DHCPv6 server and the client, and SRv protocol system operation is ensured.

The method, the device, the communication equipment and the readable storage medium for allocating the identifier provided by the embodiment of the application are described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.

Referring to fig. 3, fig. 3 is a flowchart of a method for allocating an identifier, which is provided in an embodiment of the present application, and is applied to a first device, where the first device may be selected as a DHCPv6 client or a DHCPv6 server. As shown in fig. 3, the method comprises the steps of:

step 31: and sending the first message.

In this embodiment, the first packet may include a first field, where the first field is used to request the second device to allocate a first path and/or a SID of the first service to the first device. The first path is a specific path, for example, a service link having a certain threshold requirement for at least one of a passing point, a bandwidth, a delay, a jitter, a packet loss rate, etc., and may be based on actual requirements. The first service can be understood as a virtual private network (Virtual Private Network, VPN), and by allocating the SID of the VPN, the network through which the message is sent and received can be indicated, so as to ensure that the message is forwarded normally.

For example, the first path is a service link with a certain threshold requirement for bandwidth and time delay; or the first path is a service link with a certain threshold requirement on jitter; or the first path is a service link with certain threshold requirements on time delay, jitter and packet loss rate; or the first path is a service link with certain threshold requirements on the passing point, bandwidth, time delay, jitter and packet loss rate; etc.

In some embodiments, the first message may be selected as a solicitation message.

In some embodiments, the first field may be selected as the option field. For example, the first field is a special option field in the policy message, and may be represented as an option AA.

In some embodiments, the first device may send the first message, such as a solicitation message, to the plurality of second devices by multicast.

Optionally, the first device is a DHCPv6 client, and the second device is a DHCPv6 server; alternatively, the first device is a DHCPv6 server, while the second device is a DHCPv6 client. That is, the DHCPv6 client and the server can request and assign SIDs to each other.

Step 32: a target SID is received from a target second device.

Wherein the target SID is a SID assigned by the target second device for the first device. The target second device may be determined by negotiating between the plurality of second devices, or may be selected from the plurality of second devices by the first device, which is not limited.

The method for allocating the identifier in the embodiment of the application may send a first packet by a first device, where the first packet includes a first field, where the first field is used to request a second device to allocate a first path and/or a SID of a first service to the first device, and receive a target SID allocated by the second device from a target second device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; alternatively, the first device is a DHCPv6 server and the second device is a DHCPv6 client. Therefore, the DHCPv6 can be expanded, and the SID is dynamically announced between the DHCPv6 server and the client, so that SRv messages can be normally received and transmitted between the DHCPv6 server and the client, and SRv protocol system operation is ensured. Further, the SRv protocol architecture may also be enabled to cover not only operator devices such as core devices and edge devices, but also service side devices and client side devices.

Optionally, the receiving the target SID from the target second device may include: firstly, respectively receiving second messages from a plurality of second devices; the second message comprises a second field, wherein the second field is used for indicating the SID distributed for the first device; then, a server meeting preset conditions in the plurality of second devices is determined as a target second device, and the SID indicated by a second field in a second message sent by the target second device is determined as a target SID.

Alternatively, the server meeting the preset condition may be a server with the highest priority among the plurality of DHCPv6 servers, or may be one server meeting a certain selection rule among the plurality of DHCPv6 servers, which is not limited.

In some embodiments, the second message may be selected as an advertisement message.

In some embodiments, the second field may be selected as the option field. For example, the second field is a special option field in the advertisement message, which may be denoted as option BB.

In some embodiments, the second field may further indicate other required configuration parameters of the corresponding SID, such as a Locator length < Block length and Node length >, a function length, an ARGS length, and the like.

Optionally, after determining the target second device, the first device may send a third message to the plurality of second devices respectively; the third message includes a third field, where the third field is used to indicate an identification ID of the target second device, so that all relevant second devices acquire the target device determined by the first device.

In some embodiments, the third message may be selected as a request message.

In some embodiments, the third field may be selected as the option field. For example, the third field is a special option field in the request message, which may be denoted as an option CC.

In some embodiments, the first device may send a third message, such as a request message, to the plurality of second devices via multicast.

Optionally, after sending the request third message to the plurality of second devices, the first device may receive a fourth message from the target second device; the fourth message includes a fourth field, where the fourth field is used to confirm that the target SID is allocated to the first device for use.

In some embodiments, the fourth message may be selected as a reply message.

In some embodiments, the fourth field may be selected as the option field. For example, the fourth field is a special option field in the reply message, which may be represented as an option DD.

In some embodiments, the fourth field may further identify other required configuration parameters of the corresponding SID, such as a Locator length < Block length and Node length >, a function length, an ARGS length, and the like.

It should be noted that the first field, the second field, the third field, and the fourth field may have different lengths, or may have the same length, which is not limited based on actual requirements.

Referring to fig. 4, fig. 4 is a flowchart of a method for allocating an identifier, which is provided in an embodiment of the present application, and the method is applied to a second device, where the second device may be selected as a DHCPv6 client or a DHCPv6 server. As shown in fig. 4, the method comprises the steps of:

step 41: a first message is received from a first device.

In this embodiment, the first packet may include a first field, where the first field is used to request the second device to allocate a first path and/or a SID of the first service to the first device. The first path is a specific path, for example, a service link having a certain threshold requirement for at least one of a passing point, a bandwidth, a delay, a jitter, a packet loss rate, etc., and may be based on actual requirements. The first service can be understood as a VPN, and indicates a network through which a message is sent and received by distributing the SID of the VPN, so as to ensure that the message is forwarded normally.

Step 42: the SID assigned thereto is transmitted to the first device.

The method for allocating the identifier in the embodiment of the present application may receive, by a second device, a first packet from a first device, where the first packet includes a first field, where the first field is used to request the second device to allocate a first path and/or a SID of a first service to the first device, and send the SID allocated to the first device, where the first device is a DHCPv6 client, and the second device is a DHCPv6 server; alternatively, the first device is a DHCPv6 server and the second device is a DHCPv6 client. Therefore, the DHCPv6 can be expanded, and the SID is dynamically announced between the DHCPv6 server and the client, so that SRv messages can be normally received and transmitted between the DHCPv6 server and the client, and SRv protocol system operation is ensured.

Optionally, the sending the SID allocated to the first device may include: sending a second message to the first device; the second message includes a second field, where the second field is used to indicate the SID allocated to the first device.

Optionally, after sending the second message to the first device, the second device may receive a third message from the first device; the third message includes a third field, where the third field is used to indicate an ID of the target second device. The target second device is one of a plurality of second devices determined by the first device and sending second messages to the target second device, wherein the second device meets the preset condition.

In some embodiments, the third message may be selected as a request message.

Optionally, after receiving the third message from the first device, the second device may first determine, according to the identifier of the target second device indicated by the third field in the third message, whether the second device is the target second device; then, if the second device is judged to be the target second device, a fourth message is sent to the first device; the fourth message includes a fourth field, where the fourth field is used to confirm that the target SID is allocated to the first device for use, and the target SID is the SID allocated by the target second device.

In some embodiments, the fourth message may be selected as a reply message.

Next, a SID advertisement process in the embodiment of the present application will be described with reference to fig. 5.

As shown in fig. 5, a specific SID advertisement procedure may include:

s51: the DHCPv6 client sends a solicitation message to a plurality of DHCPv6 servers in a multicast manner, wherein the solicitation message carries a first field, such as an option AA, for requesting the DHCPv6 server to allocate a SID of a specific path/service to the DHCPv6 server.

S52: the DHCPv6 server replies an advertisement message to the DHCPv6 client, where the advertisement message carries a second field, such as an option BB, for indicating the SID allocated to the DHCPv6 client and other required configuration parameters, such as a Locator length < Block length and Node length >, a function length, an ARGS length, and the like.

S53: the DHCPv6 client selects one server meeting the preset condition as a target DHCPv6 server, and sends a request message to all relevant DHCPv6 servers in a multicast mode, wherein the request message carries a third field such as an option CC for indicating the ID of the target DHCPv6 server.

S54: the target DHCPv6 server replies a reply message to the DHCPv6 client, wherein the reply message carries a fourth field, such as an option DD, for determining that the target SID and other required network configuration parameters are allocated to the DHCPv6 client for use.

Thus, by means of the DHCPv6 protocol interaction flow, SID dynamic notification of SRv can be achieved.

Referring to fig. 6, fig. 6 is a schematic structural diagram of an apparatus for allocating an identifier, which is provided in an embodiment of the present application, and the apparatus is applied to a first device, where the first device may be selected as a DHCPv6 client or a DHCPv6 server. As shown in fig. 6, the means 60 for assigning an identity may include:

a first sending module 61, configured to send a first message; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a SID of a first service to the first device;

a first receiving module 62 for receiving a target SID from a target second device; wherein the target SID is the SID allocated by the target second device for the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

Optionally, the first receiving module 62 includes:

a receiving unit, configured to receive second messages from a plurality of second devices respectively; the second message comprises a second field, and the second field is used for indicating the SID allocated to the first device;

and the determining unit is used for determining a server meeting a preset condition in the plurality of second devices as the target second device and determining the SID indicated by a second field in a second message sent by the target second device as the target SID.

Optionally, the apparatus for assigning an identifier 60 further includes:

the second sending module is used for respectively sending third messages to the plurality of second devices; the third message includes a third field, where the third field is used to indicate an identifier of the target second device.

Optionally, the apparatus for assigning an identifier 60 further includes:

the second receiving module is used for receiving a fourth message from the target second equipment; the fourth message includes a fourth field, where the fourth field is used to confirm that the target SID is allocated to the first device.

It can be appreciated that the identifier assigning device 60 in this embodiment of the present application may implement the processes of the identifier assigning method embodiment shown in fig. 3 and achieve the same technical effects, and will not be described herein again for avoiding repetition.

Referring to fig. 7, fig. 7 is a schematic structural diagram of an apparatus for allocating an identifier, which is provided in an embodiment of the present application, and the apparatus is applied to a second device, where the second device may be selected as a DHCPv6 client or a DHCPv6 server. As shown in fig. 7, the means 70 for assigning an identity may include:

a third receiving module 71, configured to receive a first message from a first device; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a SID of a first service to the first device;

a third transmitting module 72, configured to transmit the SID allocated thereto to the first device; the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

Optionally, the third sending module 72 is specifically configured to: sending a second message to the first device; the second message includes a second field, where the second field is used to indicate a SID allocated to the first device.

Optionally, the apparatus 70 for allocating an identifier further includes:

a fourth receiving module, configured to receive a third packet from the first device; the third message comprises a third field, and the third field is used for indicating the identification of the target second equipment; the target second device is one of a plurality of second devices which are determined by the first device and used for sending second messages to the target second device and meet preset conditions.

Optionally, the apparatus 70 for allocating an identifier further includes:

the judging module is used for judging whether the second equipment which the judging module belongs to is the target second equipment according to the identification of the target second equipment indicated by the third field in the third message;

a fourth sending module, configured to send a fourth message to the first device when it is determined that the second device to which the fourth sending module belongs is a target second device; the fourth message includes a fourth field, where the fourth field is used to confirm that a target SID is allocated to the first device, and the target SID is a SID allocated to the second device.

It can be appreciated that the identifier assigning device 70 in this embodiment of the present application may implement the processes of the identifier assigning method embodiment shown in fig. 4 and achieve the same technical effects, and will not be described herein again for avoiding repetition.

In addition, the embodiment of the present application further provides a communication device 80, including a processor 81, a memory 82, and a program or an instruction stored in the memory 82 and capable of running on the processor 81, where, for example, when the communication device 80 is a DHCPv6 client, the program or the instruction is executed by the processor 81 to implement the respective processes of the method embodiment for allocating identifiers shown in fig. 3, and achieve the same technical effects; alternatively, when the communication device 80 is a DHCPv6 server, the program or the instruction implements the respective processes of the method embodiment for allocating the identifier shown in fig. 4 when executed by the processor 81, and the same technical effects can be achieved, which is not repeated herein.

The embodiment of the present application further provides a readable storage medium, on which a program or an instruction is stored, where the program or the instruction can implement each process of the above-mentioned method embodiment of allocating identifiers and achieve the same technical effect when executed by a processor, and in order to avoid repetition, a detailed description is omitted here.

Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a service classification device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application and are intended to be comprehended within the scope of the present application.

Claims

1. A method of assigning an identity, for use with a first device, the method comprising:

sending a seeking first message; the first message comprises a first field, wherein the first field is used for requesting a second device to allocate a first path and/or a segment identification SID of a first service for the first device;

receiving a target SID from a target second device; wherein the target SID is a SID assigned by the target second device to the first device;

the first device is a dynamic host configuration protocol sixth edition DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

2. The method of claim 1, wherein the receiving the target SID from the target second device comprises:

receiving second messages from a plurality of second devices respectively; the second message comprises a second field, and the second field is used for indicating the SID allocated to the first device;

and determining a server meeting preset conditions in the plurality of second devices as the target second device, and determining the SID indicated by a second field in a second message sent by the target second device as the target SID.

3. The method of claim 2, wherein after determining the target second device, the method further comprises:

respectively sending third messages to the plurality of second devices; the third message includes a third field, where the third field is used to indicate an identifier of the target second device.

4. A method according to claim 3, wherein after sending the request third message to the plurality of second devices, respectively, the method further comprises:

receiving a fourth message from the target second device; the fourth message includes a fourth field, where the fourth field is used to confirm that the target SID is allocated to the first device.

5. A method of assigning an identity, characterized by being applied to a second device, comprising:

transmitting the SID assigned thereto to the first device;

the first device is a DHCPv6 client, and the second device is a DHCPv6 server; or the first device is a DHCPv6 server, and the second device is a DHCPv6 client.

6. The method of claim 5, wherein the transmitting the SID assigned thereto to the first device comprises:

sending a second message to the first device; the second message includes a second field, where the second field is used to indicate a SID allocated to the first device.

7. The method of claim 6, wherein after sending the second message to the first device, the method further comprises:

receiving a third message from the first device; the third message comprises a third field, and the third field is used for indicating the identification of the target second equipment; the target second device is one of a plurality of second devices which are determined by the first device and used for sending second messages to the target second device and meet preset conditions.

8. The method of claim 7, wherein after receiving a third message from the first device, the method further comprises:

judging whether the second device is the target second device according to the identification of the target second device indicated by the third field in the third message;

if the second device is judged to be the target second device, a fourth message is sent to the first device; the fourth message includes a fourth field, where the fourth field is used to confirm that a target SID is allocated to the first device, and the target SID is a SID allocated to the second device.

9. An apparatus for assigning an identity, for use with a first device, comprising:

a first receiving module for receiving a target SID from a target second device; wherein the target SID is a SID assigned by the target second device to the first device;

10. The apparatus of claim 9, wherein the first receiving means comprises:

11. The apparatus of claim 10, wherein the apparatus further comprises:

12. The apparatus of claim 11, wherein the apparatus further comprises:

13. An apparatus for assigning an identity, characterized by being applied to a second device, comprising:

a third transmitting module, configured to transmit the SID allocated thereto to the first device;

14. The apparatus of claim 13, wherein the device comprises a plurality of sensors,

the third sending module is specifically configured to: sending a second message to the first device; the second message includes a second field, where the second field is used to indicate a SID allocated to the first device.

15. The apparatus of claim 14, wherein the apparatus further comprises:

16. The apparatus of claim 15, wherein the apparatus further comprises:

17. A communication device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor implements the steps of the method of allocating identities according to any one of claims 1 to 4 or the steps of the method of allocating identities according to any one of claims 5 to 8.

18. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which program or instructions, when executed by a processor, implement the steps of the method of allocating identities according to any one of claims 1 to 4, or the steps of the method of allocating identities according to any one of claims 5 to 8.