Method, apparatus, communication device and readable storage medium for allocating identity

Abstract

The application discloses a method and device for allocating an identifier, a communication device and a readable storage medium, and belongs to the technical field of communication. The scheme of the embodiment of the application comprises: a DHCPv6 client receives a first message from a DHCPv6 server; wherein the first message comprises a first field, and the first field is used for indicating a Locator segment allocated for the DHCPv6 client; and the Locator segment is a network node identifier segment in an SRv6 protocol system. Thus, the DHCPv6 can be extended, the Locator segment is allocated for the DHCPv6 client by the DHCPv6 server, so that the SRv6 message can be normally transmitted and received between the DHCPv6 server and the client, and the operation of the SRv6 protocol system is ensured.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a method and device for allocating an identifier, a communication device and a readable storage medium. BACKGROUND

[0002] At present, SRv6 is a segment routing (SR) solution based on an Internet Protocol Version 6 (IPv6) extension. In the IPv6 protocol system, a client device such as an optical network unit (ONU), a router, a switch, etc. can cooperate with an edge device of an operator network such as a broadband remote access server (BRAS), a service router (SR), etc. to automatically obtain an IPv6 address from the Bras / SR through a DHCPv6 protocol. However, an IPv6 address and a network node identifier Locator in the SRv6 protocol system are completely different resources, and there is currently no related method for allocating a Locator for a client device. SUMMARY

[0003] The purpose of the embodiments of the present application is to provide a method and device for allocating an identifier, a communication device and a readable storage medium, so as to solve the problem that a Locator cannot be allocated for a client device at present.

[0004] In order to solve the above technical problems, the present application is implemented as follows:

[0005] In a first aspect, a method for allocating an identifier is provided, and is applied to a DHCPv6 client, and includes the following steps.

[0006] receiving a first message from a DHCPv6 server; wherein the first message includes a first field, and the first field is used to indicate a Locator segment allocated for the DHCPv6 client; and the Locator segment is a network node identifier segment in an SRv6 protocol system.

[0007] In a second aspect, a method for allocating an identifier is provided, and is applied to a DHCPv6 server, and includes the following steps.

[0008] sending a first message to a DHCPv6 client; wherein the first message includes a first field, and the first field is used to indicate a Locator segment allocated for the DHCPv6 client; and the Locator segment is a network node identifier segment in an SRv6 protocol system.

[0009] In a third aspect, a device for allocating an identifier is provided, and is applied to a DHCPv6 client, and includes:

[0010] A first receiving module is configured to receive a first packet from a DHCPv6 server, wherein the first packet includes a first field, and the first field is used to indicate a Locator segment allocated to the DHCPv6 client, and the Locator segment is a network node identifier segment in an SRv6 protocol system.

[0011] In a fourth aspect, a device for allocating an identifier is provided, and is applied to a DHCPv6 server, and includes:

[0012] A third sending module is configured to send a first packet to a DHCPv6 client, wherein the first packet includes a first field, and the first field is used to indicate a Locator segment allocated to the DHCPv6 client, and the Locator segment is a network node identifier segment in an SRv6 protocol system.

[0013] In a fifth aspect, an embodiment of the present application provides a communication device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and when the program or instruction is executed by the processor, the steps of the method according to the first aspect are implemented, or the steps of the method according to the second aspect are implemented.

[0014] In a sixth aspect, an embodiment of the present application provides a readable storage medium, and the readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented, or the steps of the method according to the second aspect are implemented.

[0015] In an embodiment of the present application, a first packet can be received by a DHCPv6 client from a DHCPv6 server, and the first packet includes a first field, and the first field is used to indicate a Locator segment allocated to the DHCPv6 client, and the Locator segment is a network node identifier segment in an SRv6 protocol system. Thus, the DHCPv6 can be extended, and the Locator segment can be allocated to the DHCPv6 client by the DHCPv6 server, so that the SRv6 packet can be normally transmitted and received between the DHCPv6 server and the client, and the SRv6 protocol system can be ensured to operate. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 is a schematic diagram of an SRH in an embodiment of the present application;

[0017] Figure 2 is a schematic diagram of a SID format in an embodiment of the present application;

[0018] Figure 3is a flow chart of a method for allocating an identifier provided by an embodiment of the present application.

[0019] Figure 4 is a flow chart of another method for allocating an identifier provided by an embodiment of the present application.

[0020] Figure 5 is a flow chart of a Locator allocation process in an embodiment of the present application.

[0021] Figure 6 is a structural schematic diagram of an apparatus for allocating an identifier provided by an embodiment of the present application.

[0022] Figure 7 is a structural schematic diagram of another apparatus for allocating an identifier provided by an embodiment of the present application.

[0023] Figure 8 is a structural schematic diagram of a communication device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0024] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0025] The terms “first”, “second”, and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by “first”, “second”, etc. are generally of a kind and do not limit the number of objects, for example, the first object can be one or more. In addition, “and / or” in the specification and claims indicates at least one of the connected objects, and the character “ / ” generally indicates that the objects before and after are in an “or” relationship.

[0026] In order to facilitate understanding of the embodiments of the present application, the following content is first described.

[0027] SRv6 is the abbreviation of SR-IPv6, which means applying Segment Routing (SR) to the IPv6 forwarding plane, i.e. encapsulating the SR instruction list (SID list) in the IPv6 packet to guide the packet to be forwarded according to the source route. Among them, the IPv6 header (Header) and the Segment Routing Header (SRH) can be likeFigure 1 As shown, the Next Header in the IPv6 Header takes the value of 43, indicating that the lower layer header is a Routing Extension Header. The SRv6 data plane can adopt a Segment Routing Header (SRH) encapsulation, and the SRH encapsulates segment list information, each segment being a 128-bit IPv6 address. The SRv6 tunnel is a management entity corresponding to the SID list, and like other tunnels, it presents to the service. The SRv6 tunnel can carry all known types of payloads, such as Layer 2, Layer 3, Multi-Protocol Label Switching (MPLS), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and the like.

[0028] The SID of SRv6 can be understood as the IP address of the router, and the SID list represents the IP address list of the entire routing path. As shown in Figure 2 The SID of SRv6 can be a 128-bit programmable SID, which can include a Locator, a Function (FUNCT), and Arguments (ARGS). The Locator is the network node identifier in the SRv6 protocol system, which is an identifier assigned to a network node in the network topology, and is used to forward data packets to the network node. The Locator corresponding route will be published to the network by the network node through the Interior Gateway Protocol (IGP), which is used to help other devices forward data packets to the node network that publishes the Locator. In the SRv6 SID, the Locator length is variable, which is used to adapt to different sizes of networks. The Locator can be further divided into B and N, B identifies the SRv6 SID block (Block), which is generally assigned by an operator to a certain subnet, and is usually represented by a prefix, and N is the identifier for distinguishing nodes within the subnet. The Function (FUNCT) is used to express the forwarding action to be performed, which is equivalent to the operation code of the computer instruction. In SRv6 network programming, different forwarding behaviors (Behaviors) are described by the Function part, such as forwarding data packets to a specified link, or table lookup forwarding in a specified table, etc. The Arguments (ARGS) is an optional field, which is the corresponding parameter when the instruction is executed. These parameters can contain data streams, services, or any other related information.

[0029] Optionally, in the embodiments of the present application, the DHCPv6 client can include but is not limited to 4G / 5G devices, small switches, routers and other client-side devices. The DHCPv6 server can be an edge device of an operator network, such as a BRAS, a SR, etc.

[0030] Optionally, the SID in the embodiments of the present application is specifically a SID of SRv6, and a Locator segment in the network node identification segment of the SRv6 protocol system is mainly used to compose the SID to realize corresponding routing forwarding.

[0031] In order to solve the problem that the Locator cannot be allocated to the client device at present, the embodiments of the present application extend the DHCPv6, and propose to dynamically allocate a Locator segment to the DHCPv6 client by the DHCPv6 server, the Locator segment being a network node identification segment in the SRv6 protocol system, so that the SRv6 message can be normally transmitted and received between the DHCPv6 server and the client, and the operation of the SRv6 protocol system is ensured.

[0032] The method for allocating an identifier, the device, the communication device and the readable storage medium provided by the embodiments of the present application will be described in detail in combination with the drawings, specific embodiments and application scenarios.

[0033] Please refer to Figure 3 , Figure 3 is a flowchart of a method for allocating an identifier provided by the embodiments of the present application, and the method is applied to a DHCPv6 client. As shown in Figure 3 , the method includes the following steps:

[0034] Step 31: receiving a first message from a DHCPv6 server.

[0035] In the embodiments, the first message can include a first field, and the first field is used to indicate a Locator segment allocated to the DHCPv6 client, the Locator segment being a network node identification segment in the SRv6 protocol system and mainly used to compose a SID to realize corresponding routing forwarding. The Locator segment can be one Locator or composed of multiple Locators.

[0036] In some embodiments, the first message can be an advertise message.

[0037] In some embodiments, the first field can be an option field. For example, the first field is a special option field in the advertise message, which can be represented as option BB.

[0038] In some embodiments, the first field can also indicate other required configuration parameters of the corresponding Locator, such as Locator value / length, Block length, Node length, etc.

[0039] In the embodiments of the present application, the first message including the first field indicating the Locator segment allocated to the DHCPv6 client by the DHCPv6 server can be received by the DHCPv6 client from the DHCPv6 server. The Locator segment is the network node identification segment in the SRv6 protocol system. Thus, the DHCPv6 can be extended, and the Locator segment can be allocated to the DHCPv6 client by the DHCPv6 server, so that the SRv6 message can be normally transmitted and received between the DHCPv6 server and the client, and the SRv6 protocol system can be ensured to run. Further, the SRv6 protocol system can not only cover the operator backbone network device, but also cover the backbone network device and the edge device.

[0040] Optionally, before receiving the first message from the DHCPv6 server, the DHCPv6 client can send a second message including a second field to the DHCPv6 server to request the DHCPv6 server to allocate the Locator segment to the DHCPv6 client, so as to allocate the Locator segment to the DHCPv6 client by the DHCPv6 server based on the request.

[0041] In some embodiments, the second message can be a solicit message.

[0042] In some embodiments, the second field can be an option field. For example, the second field can be a special option field in the solicit message, which can be represented as option AA.

[0043] In some embodiments, the DHCPv6 client can send the second message such as the solicit message to multiple DHCPv6 servers in a multicast manner.

[0044] Optionally, if the DHCPv6 client receives the first message from multiple DHCPv6 servers, the DHCPv6 client can determine the server satisfying the preset condition from the multiple DHCPv6 servers as a target DHCPv6 server, and determine the Locator segment indicated by the first field in the first message sent by the target DHCPv6 server as a target Locator segment.

[0045] Optionally, the server satisfying the preset condition can be a server with the highest priority among the plurality of DHCPv6 servers, or a server satisfying certain selection rule among the plurality of DHCPv6 servers, and the selection is not limited.

[0046] Optionally, after determining the target DHCPv6 server, the DHCPv6 client can send a third message to the plurality of DHCPv6 servers respectively; wherein the third message comprises a third field, and the third field is used to indicate the identification ID of the target DHCPv6 server, so that all the related DHCPv6 servers obtain the target server determined by the DHCPv6 client.

[0047] In some embodiments, the third message can be a request message.

[0048] In some embodiments, the third field can be an option field. For example, the third field is a special option field in the request message, which can be represented as option CC.

[0049] In some embodiments, the DHCPv6 client can send the third message, such as the request message, to the plurality of DHCPv6 servers through multicast mode.

[0050] Optionally, after sending the third message to the plurality of DHCPv6 servers respectively, the DHCPv6 client can receive a fourth message from the target DHCPv6 server; wherein the fourth message comprises a fourth field, and the fourth field is used to confirm the allocation of the target Locator segment to the DHCPv6 client.

[0051] In some embodiments, the fourth message can be a reply message.

[0052] In some embodiments, the fourth field can be an option field. For example, the fourth field is a special option field in the reply message, which can be represented as option DD.

[0053] In some embodiments, the fourth field can also confirm other required configuration parameters of the corresponding Locator, such as Locator value / length, Block length, Node length, etc.

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

[0055] Please refer to Figure 4 , Figure 4is a flowchart of a method for allocating an identifier provided by an embodiment of the present application, which is applied to a DHCPv6 server. As shown in Figure 4 The method comprises the following steps:

[0056] Step 41: sending a first message to a DHCPv6 client.

[0057] In the embodiment, the first message can comprise a first field, which is used to indicate a Locator segment allocated for the DHCPv6 client. The Locator segment is a network node identifier segment in the SRv6 protocol system, and is mainly used to form a SID to realize corresponding route forwarding.

[0058] In some embodiments, the first message can be an advertise message.

[0059] In some embodiments, the first field can be an option field. For example, the first field is a special option field in the advertise message, which can be represented as option BB.

[0060] In some embodiments, the first field can also indicate other required configuration parameters of the corresponding Locator, such as Locator value / length, Block length, Node length, etc.

[0061] The method for allocating an identifier provided by the embodiment of the present application can send a first message to a DHCPv6 client by a DHCPv6 server, wherein the first message comprises a first field, which is used to indicate a Locator segment allocated for the DHCPv6 client. In this way, the DHCPv6 can be extended, and the Locator segment can be configured for the DHCPv6 client by the DHCPv6 server, so that the SRv6 message can be normally transmitted and received between the DHCPv6 server and the client, and the operation of the SRv6 protocol system is ensured.

[0062] Optionally, before the first message is sent to the DHCPv6 client, the DHCPv6 server can receive a second message from the DHCPv6 client, wherein the second message comprises a second field, which is used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

[0063] In some embodiments, the second message can be a solicit message.

[0064] In some embodiments, the second field can be an option field. For example, the second field is a special option field in the solicit message, which can be represented as option AA.

[0065] Optionally, after sending the first message to the DHCPv6 client, the DHCPv6 server can receive a third message from the DHCPv6 client; wherein the third message comprises a third field, the third field being used to indicate the ID of the target DHCPv6 server. The target DHCPv6 server is the one with the highest priority among the multiple DHCPv6 servers sending the first message to the DHCPv6 client.

[0066] In some embodiments, the third message can be a request message.

[0067] In some embodiments, the third field can be an option field. For example, the third field can be a special option field in the request message, which can be denoted as option CC.

[0068] In some embodiments, the DHCPv6 client can send the third message, such as the request message, to the multiple DHCPv6 servers through multicast.

[0069] Optionally, after receiving the third message from the DHCPv6 client, the DHCPv6 server can first determine whether it is the target DHCPv6 server according to the third field in the third message indicating the ID of the target DHCPv6 server; then, if it is determined that it is the target DHCPv6 server, it sends a fourth message to the DHCPv6 client; wherein the fourth message comprises a fourth field, the fourth field being used to confirm that the target Locator segment is allocated to the DHCPv6 client, the target Locator segment being the Locator segment allocated by the target DHCPv6 server. If it is determined that it is not the target DHCPv6 server, it does not need to return a message to the DHCPv6 client.

[0070] In some embodiments, the fourth message can be a reply message.

[0071] In some embodiments, the fourth field can be an option field. For example, the fourth field can be a special option field in the reply message, which can be denoted as option DD.

[0072] In some embodiments, the fourth field can also confirm other required configuration parameters of the corresponding Locator, such as the Locator value / length, Block length, Node length, etc.

[0073] In the following, the Locator allocation process in the embodiments of the present application will be described in detail. Figure 5 The Locator allocation process in the embodiments of the present application will be described in detail.

[0074] As shown in FIG. 1, the Locator allocation process in the embodiments of the present application can include the following steps. Figure 5As shown, the specific Locator allocation process can include:

[0075] S51: The DHCPv6 client sends a solicit message to multiple DHCPv6 servers through multicast, wherein a second field such as option AA is carried to request the DHCPv6 server to allocate a Locator segment for it.

[0076] S52: The DHCPv6 server replies to the DHCPv6 client with an advertise message, wherein a first field such as option BB is carried to indicate the Locator segment allocated for the DHCPv6 client and other required configuration parameters such as Locator value / length, Block length, Node length, etc.

[0077] S53: The DHCPv6 client selects a server with the highest priority as the target DHCPv6 server, and sends a request message to all related DHCPv6 servers through multicast, wherein a third field such as option CC is carried to indicate the ID of the target DHCPv6 server.

[0078] S54: The target DHCPv6 server replies to the DHCPv6 client with a reply message, wherein a fourth field such as option DD is carried to determine to allocate the target Locator segment and other required network configuration parameters to the DHCPv6 client for use.

[0079] In this way, the request and allocation of the Locator of SRv6 can be realized by means of the above-mentioned DHCPv6 protocol interaction process.

[0080] Please refer to Figure 6 , Figure 6 is a structural schematic diagram of an identifier allocation apparatus provided by the embodiment of the present application, which is applied to a DHCPv6 client, as shown in Figure 6 The identifier allocation apparatus 60 includes:

[0081] A first receiving module 61 is configured to receive a first message from a DHCPv6 server; wherein the first message includes a first field, and the first field is used to indicate a Locator segment allocated for the DHCPv6 client; and the Locator segment is a network node identifier segment in the SRv6 protocol system.

[0082] Optionally, the identifier allocation apparatus 60 further includes:

[0083] A first sending module is configured to send a second message.

[0084] The second message includes a second field, and the second field is used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

[0085] Optionally, the device 60 for allocating an identifier further includes:

[0086] The determining module is configured to, in a case where the first message is received from the plurality of DHCPv6 servers, determine a server with the highest priority among the plurality of DHCPv6 servers as a target DHCPv6 server, and determine a Locator segment indicated by the first field in the first message sent by the target DHCPv6 server as a target Locator segment.

[0087] Optionally, the device 60 for allocating an identifier further includes:

[0088] The second sending module is configured to send a third message to the plurality of DHCPv6 servers respectively, wherein the third message includes a third field, and the third field is used to indicate the identifier of the target DHCPv6 server.

[0089] Optionally, the device 60 for allocating an identifier further includes:

[0090] The second receiving module is configured to receive a fourth message from the target DHCPv6 server, wherein the fourth message includes a fourth field, and the fourth field is used to confirm that the target Locator segment is allocated to the DHCPv6 client.

[0091] It can be understood that the device 60 for allocating an identifier according to the embodiments of the present application can implement the above-mentioned Figure 3 processes of the method embodiments for allocating an identifier shown in the figures, and can achieve the same technical effects. To avoid repetition, details are not described here.

[0092] Please refer to Figure 7 , Figure 7 is a structural schematic diagram of a device for allocating an identifier provided by the embodiments of the present application, and the device is applied to a DHCPv6 server, as shown in Figure 7 The device 70 for allocating an identifier includes:

[0093] The third sending module 71 is configured to send a first message to a DHCPv6 client, wherein the first message includes a first field, and the first field is used to indicate a Locator segment allocated for the DHCPv6 client; and the Locator segment is a network node identifier segment in an SRv6 protocol system.

[0094] Optionally, the device 70 for allocating an identifier further includes:

[0095] The third receiving module is configured to receive a second message from the DHCPv6 client.

[0096] The second message includes a second field, and the second field is configured to request a DHCPv6 server to allocate a Locator segment to the DHCPv6 client.

[0097] Optionally, the device 70 for allocating an identifier further includes:

[0098] The fourth receiving module is configured to receive a third message from the DHCPv6 client, and the third message includes a third field, and the third field is configured to indicate an identifier of a target DHCPv6 server, wherein the target DHCPv6 server is a DHCPv6 server with the highest priority in a plurality of DHCPv6 servers determined by the DHCPv6 client to send the first message.

[0099] Optionally, the device 70 for allocating an identifier further includes:

[0100] The judging module is configured to judge whether a DHCPv6 server to which the device belongs is the target DHCPv6 server.

[0101] The fourth sending module is configured to send a fourth message to the DHCPv6 client when it is judged that the DHCPv6 server to which the device belongs is the target DHCPv6 server, and the fourth message includes a fourth field, and the fourth field is configured to confirm that a target Locator segment is allocated to the DHCPv6 client, wherein the target Locator segment is a Locator segment allocated by the target DHCPv6 server.

[0102] It can be understood that the device 70 for allocating an identifier according to the embodiments of the present application can implement the processes of the method for allocating an identifier as described above, and can achieve the same technical effects. To avoid repetition, details are not described herein. Figure 4 The method for allocating an identifier as described above, and can achieve the same technical effects. To avoid repetition, details are not described herein.

[0103] In addition, the embodiments of the present application further provide a communication device 80, which includes a processor 81, a memory 82, a program or instructions stored in the memory 82 and executable on the processor 81. For example, when the communication device 80 is a DHCPv6 client, the program or instructions are executed by the processor 81 to implement the processes of the method for allocating an identifier as described above, and can achieve the same technical effects. Figure 3 For example, when the communication device 80 is a DHCPv6 server, the program or instructions are executed by the processor 81 to implement the processes of the method for allocating an identifier as described above, and can achieve the same technical effects. To avoid repetition, details are not described herein. Figure 4 For example, when the communication device 80 is a DHCPv6 client, the program or instructions are executed by the processor 81 to implement the processes of the method for allocating an identifier as described above, and can achieve the same technical effects.

[0104] The embodiment of the present application further provides a readable storage medium, which stores programs or instructions, and when the programs or instructions are executed by a processor, each process of the method for allocating an identifier can be realized and the same technical effects can be achieved. To avoid repetition, details are not described herein.

[0105] Computer readable media includes permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device. According to the definition herein, computer readable media does not include transitory computer readable media, such as modulated data signals and carriers.

[0106] It should be noted that in this paper, the term "include", "contain" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0107] The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0108] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by software and necessary general hardware platform, of course, also can be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes a plurality of instructions for making a service classification device (which can be a mobile phone, computer, server, air conditioner or network device) execute the method described in each embodiment of the present application.

[0109] The above merely preferred embodiments of the present application, it should be noted that for those of ordinary skill in the art, without departing from the principles of the present application, can also make a number of improvements and refinements, these improvements and refinements should also be considered as the scope of protection of the present application.

Claims

1. A method for assigning identifiers, applied to a Dynamic Host Configuration Protocol version 6 (DHCPv6) client, characterized in that, include: Receive a first message from the DHCPv6 server; wherein the first message includes a first field, the first field being used to indicate the Locator segment allocated to the DHCPv6 client; The Locator segment is a network node identifier segment in the segmented routing protocol system based on Internet Protocol version 6 (RP6).

2. The method according to claim 1, characterized in that, Before receiving the first message from the DHCPv6 server, the method further includes: Send a second message; wherein the second message includes a second field, the second field being used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

3. The method according to claim 1, characterized in that, If the DHCPv6 client receives the first message from multiple DHCPv6 servers, the method further includes: The server that meets the preset conditions among the plurality of DHCPv6 servers is identified as the target DHCPv6 server, and the Locator segment indicated by the first field in the first message sent by the target DHCPv6 server is identified as the target Locator segment.

4. The method according to claim 3, characterized in that, After identifying the target DHCPv6 server, the method further includes: A third message is sent to each of the plurality of DHCPv6 servers; wherein the third message includes a third field, the third field being used to indicate the identifier of the target DHCPv6 server.

5. The method according to claim 4, characterized in that, After sending a third message to each of the plurality of DHCPv6 servers, the method further includes: A fourth message is received from the target DHCPv6 server; wherein the fourth message includes a fourth field, the fourth field being used to confirm that the target Locator segment is assigned to the DHCPv6 client.

6. A method for assigning identifiers, applied to a DHCPv6 server, characterized in that, include: Send a first message to the DHCPv6 client; wherein the first message includes a first field, the first field being used to indicate the Locator segment allocated to the DHCPv6 client; the Locator segment is a network node identifier segment based on the Internet Protocol version 6 (IP6) segmentation routing protocol suite.

7. The method according to claim 6, characterized in that, Before sending the first message to the DHCPv6 client, the method further includes: A second message is received from the DHCPv6 client; wherein the second message includes a second field, the second field being used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

8. The method according to claim 6, characterized in that, After sending the first message to the DHCPv6 client, the method further includes: A third message is received from the DHCPv6 client; wherein the third message includes a third field, the third field being used to indicate the identifier of the target DHCPv6 server; the target DHCPv6 server is one of a plurality of DHCPv6 servers determined by the DHCPv6 client that sent the second message to it and meets preset conditions.

9. The method according to claim 8, characterized in that, After receiving the third message from the DHCPv6 client, the method further includes: Based on the identifier of the target DHCPv6 server indicated by the third field in the third message, determine whether it is the target DHCPv6 server; If it determines that it is the target DHCPv6 server, it sends a fourth message to the DHCPv6 client; wherein the fourth message includes a fourth field, the fourth field being used to confirm that the target Locator segment is allocated to the DHCPv6 client, and the target Locator segment is the Locator segment allocated by the target DHCPv6 server.

10. An apparatus for assigning identifiers, applied to a DHCPv6 client, characterized in that, include: A first receiving module is configured to receive a first message from a DHCPv6 server; wherein the first message includes a first field, the first field being used to indicate a Locator segment allocated to the DHCPv6 client; the Locator segment is a network node identifier segment based on the Internet Protocol version 6 (IP6) segmented routing protocol suite.

11. The apparatus according to claim 10, characterized in that, The device further includes: The first sending module is used to send the second message; The second message includes a second field, which is used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

12. The apparatus according to claim 10, characterized in that, The device further includes: The determination module is configured to, upon receiving a first message from multiple DHCPv6 servers, determine the server among the multiple DHCPv6 servers that meets preset conditions as the target DHCPv6 server, and determine the Locator segment indicated by the first field in the first message sent by the target DHCPv6 server as the target Locator segment.

13. An apparatus for assigning identifiers, applied to a DHCPv6 server, characterized in that, include: The third sending module is used to send a first message to the DHCPv6 client; wherein the first message includes a first field, the first field being used to indicate the Locator segment allocated to the DHCPv6 client; the Locator segment is a network node identifier segment based on the Internet Protocol version 6 (IP6) segmentation routing protocol suite.

14. The apparatus according to claim 13, characterized in that, The device further includes: The third receiving module is used to receive the second message from the DHCPv6 client; The second message includes a second field, which is used to request the DHCPv6 server to allocate a Locator segment for the DHCPv6 client.

15. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for allocating identifiers as claimed in any one of claims 1 to 5, or implement the steps of the method for allocating identifiers as claimed in any one of claims 6 to 9.

16. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method for allocating identifiers as described in any one of claims 1 to 5, or the steps of the method for allocating identifiers as described in any one of claims 6 to 9.

Images