Method for allocating resource identifier, terminal, first device, storage medium and product

Abstract

The application discloses a resource identifier allocation method, a terminal, a first device, a computer readable storage medium and a computer program product. The method comprises the following steps: a terminal multicasts a first message to multiple devices; wherein the first message is used for requesting allocation of a resource identifier and / or configuration parameters corresponding to the resource identifier; an option field of the first message is used for carrying the resource identifier and / or the configuration parameters corresponding to the resource identifier; a first device receives the first message sent by the terminal; wherein the multiple devices comprise the first device; the first device sends a second message to the terminal; wherein the second message is used for confirming that a first resource identifier and / or first configuration parameters corresponding to the first resource identifier are allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameters are carried in an option field of the second message; and the terminal receives the second message sent by the first device.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of communications, and particularly to a method for allocating resource identifiers, a terminal, a first device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] The customer-side optical network unit (ONU) / customer-side router or switch works in conjunction with the operator's network edge devices, the broadband remote access server (BRAS) / service router (SR), to automatically obtain an IPv6 address from the BRAS / SR via the IPv6 dynamic host configuration protocol (DHCPv6).

[0003] As user services gradually shift from traditional voice and web access to multi-dimensional, interactive, and dedicated line services, Service Level Agreement (SLA) requirements vary, posing greater challenges to network devices (such as BRAS) in order to improve user experience. Currently, some network devices (such as BRAS) cannot identify different services and cannot perform differentiated SLA scheduling and guarantees for different services. Therefore, to address the aforementioned issues in some network devices, a unified adaptive routing notification (ARN) identifier (ID) scheme has been proposed for the entire network.

[0004] However, the IPv4 Dynamic Host Configuration Protocol (DHCPv4) / DHCPv6 protocol in related technologies can only automatically allocate IPv4 / IPv6 address information and cannot allocate ARN ID information. Currently, there are no schemes or protocols for client-side devices to request ARN ID allocation from upstream network devices (BRAS / SR), and client-side devices are usually connected with dynamic or arbitrary addresses, so ARN IDs cannot be pre-configured. Summary of the Invention

[0005] This application provides a method for allocating resource identifiers, a terminal, a first device, a computer-readable storage medium, and a computer program product to solve the problem in related technologies that it is impossible to allocate or pre-allocate resource identifiers.

[0006] The technical solution of this application embodiment is implemented as follows:

[0007] Firstly, embodiments of this application provide a method for allocating resource identifiers, applied to a terminal, the method comprising:

[0008] A first message is multicast to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier;

[0009] The system receives a second message sent by a first device; wherein the second message is used to confirm that a first resource identifier and / or a first configuration parameter corresponding to the first resource identifier is allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in an option field of the second message; the plurality of devices includes the first device.

[0010] Secondly, embodiments of this application provide a method for allocating resource identifiers, applied to a first device, the method comprising:

[0011] The receiving terminal sends a first message; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the first device is a device in the network accessed by the terminal;

[0012] Send a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in the option field of the second message.

[0013] Thirdly, embodiments of this application provide a terminal, the terminal comprising:

[0014] The first sending module is used to multicast a first message to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier.

[0015] A first receiving module is configured to receive a second message sent by a first device; wherein the second message is used to confirm that a first resource identifier and / or a first configuration parameter corresponding to the first resource identifier is allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in an option field of the second message; the plurality of devices includes the first device.

[0016] Fourthly, embodiments of this application provide a first device, the first device comprising:

[0017] The second receiving module is used to receive a first message sent by the terminal; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the first device is a device in the network accessed by the terminal;

[0018] The second sending module is used to send a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in the option field of the second message.

[0019] Fifthly, embodiments of this application provide a terminal, the terminal comprising:

[0020] The first memory is used to store executable instructions;

[0021] The first processor, when executing executable instructions stored in the first memory, performs the steps of the resource identifier allocation method described above.

[0022] Sixthly, embodiments of this application provide a first device, the first device comprising:

[0023] The second memory is used to store executable instructions;

[0024] The second processor, when executing executable instructions stored in the second memory, performs the steps of the resource identifier allocation method described above.

[0025] Seventhly, embodiments of this application provide a computer-readable storage medium storing one or more computer programs thereon, the one or more programs being executable by one or more processors to implement the steps of the resource identifier allocation method described above.

[0026] Eighthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the resource identifier allocation method described above.

[0027] The first and second messages provided in this application both carry an option field, which contains a resource identifier and / or the configuration parameters corresponding to the resource identifier. Thus, based on a terminal's request, the device can directly use the message carrying the option field to carry the resource identifier automatically assigned to the terminal. Therefore, regardless of when or where the terminal goes online, as long as a request is sent, the device can configure a resource identifier for the terminal. Furthermore, since the resource identifier and / or the configuration parameters corresponding to the resource identifier are carried in the option field, this solves the problem of not being able to assign resource identifiers in related technologies, enabling better compatibility with existing messages and reducing application costs. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application;

[0029] Figure 2 It is a network architecture diagram provided by related technologies;

[0030] Figure 3 This is a flowchart of the IPv6 address allocation process provided by related technologies;

[0031] Figure 4 This is a schematic diagram of the DHCPv6 message format provided by related technologies;

[0032] Figure 5 This is a partial architecture diagram of ARN provided by related technologies;

[0033] Figure 6 This is a schematic diagram of the IPv6 packet header format provided by related technologies;

[0034] Figure 7 A flowchart illustrating a resource identifier allocation method provided in this application embodiment. Figure 1 ;

[0035] Figure 8 A flowchart illustrating a resource identifier allocation method provided in this application embodiment. Figure 2 ;

[0036] Figure 9 A flowchart illustrating a resource identifier allocation method provided in this application embodiment. Figure 3 ;

[0037] Figure 10 This is a schematic diagram of the format of an option field provided in an embodiment of this application. Figure 1 ;

[0038] Figure 11 This is a schematic diagram of the format of an option field provided in an embodiment of this application. Figure 2 ;

[0039] Figure 12This is a schematic diagram of the format of an option field provided in an embodiment of this application. Figure 3 ;

[0040] Figure 13 A flowchart illustrating a resource identifier allocation method provided in this application embodiment. Figure 4 ;

[0041] Figure 14 A flowchart illustrating a resource identifier allocation method provided in this application embodiment. Figure 5 ;

[0042] Figure 15 A schematic block diagram of a terminal provided for an embodiment of this application;

[0043] Figure 16 A schematic block diagram of a first device provided in an embodiment of this application;

[0044] Figure 17 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] The embodiments of this application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, New Radio (NR) system, evolution system of NR system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wi-Fi), next-generation communication systems or other communication systems, etc.

[0047] Figure 1 This is a schematic diagram of a communication system according to an embodiment of this application.

[0048] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0049] exist Figure 1 In the communication system 100 shown, network device 120 can be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 located within that coverage area.

[0050] Network device 120 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB or gNodeB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or network device 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0051] Terminal equipment 110 can also be referred to as user equipment (UE), tag, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. Terminal equipment can be a station in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable device, and next-generation communication systems, such as terminal equipment in NR networks or terminal equipment in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0052] Terminal device 110 can be used for device-to-device (D2D) communication.

[0053] Figure 1 An exemplary illustration shows a base station and two UEs. Optionally, the communication system 100 may include multiple base stations, and each base station may include other numbers of UEs within its coverage area. This application embodiment does not limit this.

[0054] It should be noted that, Figure 1This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0055] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0056] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0057] Before explaining this application, the DHCPv6 protocol and ARN in the related technologies are described below:

[0058] Figure 2 It is a network architecture diagram provided by related technologies; such as Figure 2As shown, devices with DHCP clients deployed (such as Customer Premise Equipment (CPE) or optical modems) cooperate with the router DHCP server (such as BRAS) on the network side (Internet) through a local switch (LSW) to obtain IPv6 addresses from the BRAS via the DHCPv6 protocol.

[0059] Figure 3 It is based on the relevant technologies Figure 2 The flowchart for allocating IPv6 addresses corresponding to the network architecture is as follows: Figure 3 As shown:

[0060] Step 201: The DHCPv6 client sends Solicit messages to multiple DHCPv6 servers via multicast; the Solicit message is used to locate the DHCPv6 server that can provide services to the DHCPv6 client.

[0061] Step 202: Multiple DHCPv6 servers send Advertise messages to the DHCPv6 client; the Advertise message includes information about the DHCPv6 server, such as its priority.

[0062] Step 203: The DHCPv6 client receives the Advertise message, selects a server to allocate an address and configuration information for it according to the priority of the DHCPv6 server, and sends a Request message to the selected DHCPv6 server; the Request message is used to request the allocation of a DHCPv6 address.

[0063] Step 204: The selected DHCPv6 server sends a Reply message to the DHCPv6 client; the Reply message includes the allocation of a DHCPv6 address; that is, the address request and allocation process is completed through the interaction of Request / Reply messages.

[0064] Figure 4 This is a diagram illustrating the DHCPv6 message format provided by related technologies, such as... Figure 4 As shown, a DHCPv6 message includes a msg-type field indicating the message type, a transaction-id field, and a variable options field.

[0065] The msg-type field occupies 8 bits and has a value range of 1 to 13.

[0066] The transaction-id field occupies 16 bits and is the DHCPv6 interaction ID, used to identify a round-trip DHCPv6 message exchange.

[0067] Figure 5 This is a partial architecture diagram of ARN provided by related technologies, such as... Figure 5 As shown: ARN user edge devices, such as ONU optical modems, interact with BRAS devices located on the Internet (China Mobile Network, CMNET) via the access network to exchange ARNIDs; ARN user edge devices, such as CPEs, interact with BRAS devices located on CMNET to exchange ARNIDs; here, the ONU optical modem is for home users, and the CPE is for SD-WAN users.

[0068] It should be noted that the ARN user edge device identifies and labels relevant business data based on the five-tuple generated from the user service subscription information, business information, and ARN ID mapping strategy, and encapsulates the access-side ARN ID in the message before sending it. Client-side devices include various devices such as personal computers (PCs), 4G / 5G devices, small switches, and routers. These are mostly user-deployed devices, and their deployment and shutdown times are random events with unknown deployment locations.

[0069] Regarding the ARN data plane format definition in related technologies, the IPv6 data plane is extended to carry the ARN ID and related information, which is carried in the IPv6 Destination Options Header (DOH). Figure 6 This is a schematic diagram of the IPv6 packet header format provided in related technologies.

[0070] Figure 6 The IPv6 header shown includes an 8-bit Next Header field, an 8-bit Extended Header Length (Hdr Edr Len) field, an 8-bit Option Type field, an 8-bit Opt Data Len field, an 8-bit Type field, a 24-bit Reserved field, and a 32-bit ARN ID field.

[0071] If the Type field represents 1, then the ARN ID field includes the Network ARN ID; if the Type field represents 2, then the ARN ID field includes both the Network ARN ID and the Resources ARN ID; if the Type field represents 3, then the ARN ID field includes the Resources ARN ID.

[0072] Here, both the Resources ARN ID and the Network ARN ID occupy 16 bits.

[0073] Figure 7 A flowchart illustrating a method for allocating resource identifiers provided in this application embodiment is shown below. Figure 7 As shown, this method is applied to Figure 1 In the communication system 100 shown, the method includes:

[0074] Step 701: The terminal multicasts the first message to multiple devices.

[0075] The first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier.

[0076] In this embodiment of the application, the multiple devices are multiple candidate devices capable of providing services (such as allocating resource identifiers) to the terminal; the candidate devices can be deployed in the terminal's access network or in the Internet connected to the terminal's access network.

[0077] In this embodiment of the application, the resource identifier (ID) is a globally unique resource identifier assigned to the resource, including RAN ID and PUCCH resource identifier.

[0078] In this embodiment of the application, the option field is located in the header of the first message or in the data field of the first message.

[0079] In this embodiment, the media plane communication channel established by the terminal is a one-to-many multicast / broadcast communication channel. In this way, the first message is sent only once through the established multicast / broadcast communication channel, and other devices can receive it, effectively reducing the number of messages sent.

[0080] Step 702: Multiple devices receive the first message.

[0081] Among them, multiple devices include the first device.

[0082] In this embodiment of the application, multiple devices may be configured with servers that provide services to clients in the terminal. After receiving the first message, some of the multiple devices may successfully allocate a first resource identifier and / or configuration parameters corresponding to the first resource identifier to the terminal, and some devices may feed back the allocated first resource identifier and / or configuration parameters corresponding to the first resource identifier to the terminal.

[0083] Here, the first device is the device with the highest priority among the devices, or the device with the fastest data transmission rate, or the device closest to the terminal.

[0084] Step 703: The first device sends a second message to the terminal.

[0085] The second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier will be allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter are carried in the option field of the second message.

[0086] In this embodiment of the application, the option field is located in the header of the second message or in the data field of the second message.

[0087] Step 704: The terminal receives the second message.

[0088] In this embodiment of the application, both the first message and the second message are DHCPv6 messages carrying an option field; the option field carries a resource identifier and / or the configuration parameters corresponding to the resource identifier; the length of the option field is variable.

[0089] This application discloses a method for allocating resource identifiers. The method includes: a terminal multicasting a first message to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; a first device receiving the first message sent by the terminal; wherein the multiple devices include the first device; the first device sending a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameters corresponding to the first resource identifier are allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameters are carried in the option field of the second message; and the terminal receiving the second message sent by the first device. In other words, both the first and second messages provided in this application carry an option field, which contains a resource identifier and / or the configuration parameters corresponding to the resource identifier. Thus, the device can directly use the message carrying the option field to carry the resource identifier automatically assigned to the terminal based on the terminal's request. Therefore, regardless of when or where the terminal goes online, as long as a request is sent, the device can configure a resource identifier for the terminal. Furthermore, the resource identifier and / or the configuration parameters corresponding to the resource identifier are carried in the option field, which solves the problem of not being able to assign resource identifiers in related technologies, and can better be compatible with existing messages and reduce application costs.

[0090] Figure 8 A flowchart illustrating a method for allocating resource identifiers provided in this application embodiment is shown below. Figure 8 As shown, this method is applied to Figure 1 In the communication system 100 shown, the method includes:

[0091] Step 801: The terminal multicasts the first message to multiple devices.

[0092] Among them, multiple devices include a first device; the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier.

[0093] Step 802: Multiple devices receive the first message.

[0094] Here, the first message may include the Rapid Commit parameter, which represents the client on the terminal's desire for the server to quickly allocate resource identifiers to it.

[0095] Step 803: Multiple devices send a third message to the terminal.

[0096] The third message is used to notify the terminal that multiple devices allocate resource identifiers and / or configuration parameters corresponding to the resource identifiers to the terminal; the third message includes an option field.

[0097] In this embodiment of the application, if the first message does not include the fast allocation parameters, or if the first message includes the fast allocation parameters but the first device among multiple devices does not support the fast allocation of resource identifiers and / or the configuration parameters of resource identifiers, step 803 is executed.

[0098] It should be noted that the third message can be understood as a response message to the first message, used to respond to the terminal and notify the terminal that it can allocate resource identifiers and / or configuration parameters corresponding to resource identifiers.

[0099] In this embodiment of the application, the option field is in the header of the third message or in the data field of the third message.

[0100] Step 804: The terminal receives the third message and determines the first device from multiple devices.

[0101] Here, the first device is the device with the highest priority among multiple devices.

[0102] Step 805: The terminal sends the fourth message to multiple devices.

[0103] The fourth message is used to request the first device to allocate a resource identifier and / or the configuration parameters corresponding to the resource identifier to the terminal; the fourth message includes an option field and the identifier of the first device.

[0104] In this embodiment of the application, the option field is in the header of the fourth message or in the data field of the fourth message.

[0105] Step 806: Multiple devices receive the fourth message.

[0106] Step 807: The first device sends a second message to the terminal.

[0107] The second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier will be allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter are carried in the option field of the second message.

[0108] Step 808: The terminal receives the second message.

[0109] In this embodiment, the first message, the second message, the third message, and the fourth message are all DHCPv6 messages carrying an option field; the option field carries a resource identifier and / or the configuration parameters corresponding to the resource identifier; the length of the option field is variable.

[0110] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0111] Figure 9A flowchart illustrating a method for allocating resource identifiers provided in this application embodiment is shown below. Figure 9 As shown, this method is applied to Figure 1 In the communication system 100 shown, the method includes:

[0112] Step 901: The terminal multicasts a first message, including the fast decision parameters, to multiple devices.

[0113] The first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the fast decision parameter is used to indicate that the client on the terminal wants the server to quickly allocate a resource identifier for it.

[0114] Step 902: Multiple devices receive the first message.

[0115] Among them, multiple devices include the first device.

[0116] Step 903: If the first device supports rapid allocation of resource identifiers and / or configuration parameters of resource identifiers, the first device directly sends a second message back to the terminal.

[0117] The second message includes fast decision parameters; the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier will be allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter are carried in the option field of the second message.

[0118] Step 904: The terminal receives the second message.

[0119] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0120] In this embodiment of the application, the option fields in the first, second, third, and fourth messages include the resource identifier type (Option_ARN_ID) field, length (Option_len) field, first lifetime (Preferred-lifetime) field, second lifetime (Valid-lifetime) field, and first resource identifier (e.g., Resources ARN ID) field; or the option fields include the resource identifier type (Option_ARN_ID) field, length (Option_len) field, first lifetime (Preferred-lifetime) field, second lifetime (Valid-lifetime) field, first resource identifier (e.g., Resources ARN ID) field, and second resource identifier (e.g., Network ARN ID) field; or the option fields include the resource identifier type (Option_ARN_ID) field, length (Option_len) field, first lifetime (Preferred-lifetime) field, second lifetime (Valid-lifetime) field, and second resource identifier (e.g., Network ARN ID) field.

[0121] The length field contains the length of the option field;

[0122] The first lifecycle field carries the preferred lifecycle for the assigned location identifier;

[0123] The first lifecycle field carries the valid lifespan of the specified allocation prefix;

[0124] The preferred option is a lifespan greater than or equal to the effective lifespan.

[0125] The first resource identifier field carries the resource identifier used to notify the adaptive routing based on available resources;

[0126] The second resource identifier field carries a resource identifier used to notify the adaptive routing based on the current network state.

[0127] For example, Figure 10 This is a schematic diagram illustrating the format of an option field provided in an embodiment of this application; for example... Figure 10 As shown, the option field includes a 16-bit Option_ARN_ID (Option Code) field, a 16-bit Option_len field, a 32-bit Preferred-lifetime field, a 32-bit Valid-lifetime field, and a 32-bit Network ARN ID field.

[0128] Figure 11 This is a schematic diagram illustrating the format of an option field provided in an embodiment of this application; for example... Figure 11 As shown, the option field includes a 16-bit Option_ARN_ID (Option Code) field, a 16-bit Option_len field, a 32-bit Preferred-lifetime field, a 32-bit Valid-lifetime field, a 32-bit NetworkARN ID field, and a 32-bit Resources ARN ID field.

[0129] Figure 12 This is a schematic diagram illustrating the format of an option field provided in an embodiment of this application; for example... Figure 12 As shown, the option field includes a 16-bit Option_ARN_ID (Option Code) field, a 16-bit Option_len field, a 32-bit Preferred-lifetime field, a 32-bit Valid-lifetime field, and a 32-bit Resources ARN ID field.

[0130] The following will describe exemplary applications of the embodiments of this application in real-world application scenarios.

[0131] Figure 13 A flowchart illustrating a method for allocating resource identifiers provided in this application embodiment is shown below. Figure 13 As shown, the method includes:

[0132] Step 1301: The DHCPv6 client (i.e., the terminal) multicasts a Solicit message (i.e., the first message) to the DHCPv6 server (i.e., multiple devices);

[0133] The Solicit message carries the Option field (i.e. Figures 10 to 12 (The Option field shown); The Solicit message requests the DHCPv6 server to assign it an ARN ID.

[0134] Step 1302: The DHCPv6 server replies to the DHCPv6 client with an Advertise message (i.e., the third message);

[0135] The Advertise message carries an Option field (i.e., Figures 10 to 12 The Option field shown is used to inform the client of the ARN ID information that can be assigned to it and other necessary configuration parameters.

[0136] Step 1303: The DHCPv6 client selects the server with the highest priority (i.e., the first device) and sends a Request multicast message (i.e., the fourth message) to all servers.

[0137] The Request multicast message carries the selected server ID.

[0138] Step 1304: The selected DHCPv6 server (i.e., the first device) replies to the DHCPv6 client with a Reply message (i.e., the second message);

[0139] The Reply message carries an Option field (such as...) Figures 10 to 12 The Option field shown is used to confirm that ARN ID information and other configuration parameters are assigned to the client.

[0140] Figure 14 A flowchart illustrating a method for allocating resource identifiers provided in this application embodiment is shown below. Figure 14 As shown, the method includes:

[0141] Step 1401: The DHCPv6 client (i.e., the terminal) multicasts a Solicit message (i.e., the first message) carrying the RapidCommit parameter to the DHCPv6 server (i.e., multiple devices);

[0142] The Solicit message carries an Option field (such as...) Figures 10 to 12 The Option field shown above and the RapidCommit parameter / option are used to indicate that the client wants the server to quickly assign it an ARN ID;

[0143] Step 1402: After receiving the Solicit message, if the DHCPv6 server supports fast address allocation, it will directly return a Reply message (i.e., the second message) to the DHCPv6 client.

[0144] The Reply message assigns ARN ID information and other network configuration parameters to the client. The Reply message also carries the Rapid Commit option / option and the Reply message.

[0145] It should be noted that if the DHCPv6 server does not support the fast allocation process, then steps 1302 to 1304 are executed to allocate ARN ID information and other network configuration parameters to the client.

[0146] Embodiments of this application provide a terminal that can be used to implement... Figures 7 to 9A corresponding embodiment provides a method for allocating resource identifiers, referring to... Figure 15 As shown, terminal 1500 includes:

[0147] The first sending module 1501 is used to multicast a first message to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier.

[0148] The first receiving module 1502 is used to receive a second message sent by the first device; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter are carried in the option field of the second message; the multiple devices include the first device.

[0149] In other embodiments of this application, the first message includes fast decision parameters, and the first receiving module 1502 is used to receive the second message directly fed back by the first device if the first device supports fast allocation of resource identifiers and / or configuration parameters of resource identifiers; wherein, the second message includes fast decision parameters.

[0150] In other embodiments of this application, the first receiving module 1502 is configured to receive a third message sent by multiple devices if the first device does not support fast allocation of resource identifiers and / or configuration parameters of resource identifiers; wherein, the third message is used to notify the terminal that the multiple devices allocate resource identifiers and / or configuration parameters corresponding to resource identifiers to the terminal; the third message includes an option field;

[0151] The first processing module 1503 is used to determine the first device from multiple devices;

[0152] The first sending module 1501 is used to send a fourth message to multiple devices; wherein the fourth message is used to request the first device to allocate a resource identifier and / or configuration parameters corresponding to the resource identifier to the terminal; the fourth message includes an option field and an identifier of the first device;

[0153] The first receiving module 1502 is used to receive the second message sent by the first device.

[0154] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a first resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources.

[0155] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, a first resource identifier field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries the resource identifier used to notify of adaptive routing based on available resources; the second resource identifier field carries the resource identifier used to notify of adaptive routing based on the current network state.

[0156] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the second resource identifier field carries a resource identifier used to notify routing adaptation based on the current network state.

[0157] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0158] It should be noted that, in the embodiments of this application, if the above-mentioned resource identifier allocation method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0159] Embodiments of this application provide a first device that can be used to implement Figures 7 to 9 A corresponding embodiment provides a method for allocating resource identifiers, referring to... Figure 16 As shown, the first device 1600 includes:

[0160] The second receiving module 1601 is used to receive a first message sent by the terminal; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the first device is a device in the network accessed by the terminal;

[0161] The second sending module 1602 is used to send a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter are carried in the option field of the second message.

[0162] In other embodiments of this application, the first message includes fast decision parameters, and the second sending module 1602 is used to directly send a second message to the terminal if the first device supports fast allocation of resource identifiers and / or configuration parameters of resource identifiers; wherein, the second message includes fast decision parameters.

[0163] In other embodiments of this application, the second sending module 1602 is used to send a third message to the terminal if the first device does not support fast allocation of resource identifier and / or configuration parameters of resource identifier; wherein, the third message is used to notify the terminal that multiple devices allocate resource identifier and / or configuration parameters corresponding to resource identifier to the terminal; the third message includes an option field;

[0164] The second receiving module 1601 is used to receive a fourth message sent by the terminal; wherein the fourth message is used to request the first device to allocate a resource identifier and / or configuration parameters corresponding to the resource identifier to the terminal; the fourth message includes an option field and an identifier of the first device;

[0165] The second sending module 1602 is used to send a second message to the terminal.

[0166] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a first resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources.

[0167] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, a first resource identifier field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries the resource identifier used to notify of adaptive routing based on available resources; the second resource identifier field carries the resource identifier used to notify of adaptive routing based on the current network state.

[0168] In other embodiments of this application, the option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle of the assigned location identifier; the first lifecycle field carries the valid lifecycle of the assigned prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the second resource identifier field carries a resource identifier used to notify routing adaptation based on the current network state.

[0169] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0170] It should be noted that, in the embodiments of this application, if the above-mentioned resource identifier allocation method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal device to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROMs, magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0171] Figure 17 This is a schematic structural diagram of a communication device 1700 provided in an embodiment of this application. The communication device can be a terminal or a first device. Figure 17 The communication device 1700 shown includes a processor 1710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0172] Optionally, such as Figure 17As shown, the communication device 1700 may further include a memory 1720. The processor 1710 can retrieve and run computer programs from the memory 1720 to implement the methods described in this embodiment.

[0173] The memory 1720 can be a separate device independent of the processor 1710, or it can be integrated into the processor 1710.

[0174] Optionally, such as Figure 17 As shown, the communication device 1700 may also include a transceiver 1730, and the processor 1710 may control the transceiver 1730 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0175] The transceiver 1730 may include a transmitter and a receiver. The transceiver 1730 may further include an antenna, and the number of antennas may be one or more.

[0176] Optionally, the communication device 1700 may specifically be a terminal in the embodiments of this application, and the communication device 1700 may implement the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0177] Optionally, the communication device 1700 may specifically be the first device in the embodiments of this application, and the communication device 1700 may implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0178] This application also provides a computer program product, including a computer program that can be executed by the processor 1710 of the communication device 1700 to complete the steps described in any of the foregoing methods.

[0179] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0180] As one embodiment, the processor may include one or more general-purpose central processing units (CPUs). Each of these processors may be a single-core processor or a multi-core processor. Here, "processor" may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., executing instructions).

[0181] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), or flash memory. The volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0182] This application also provides a computer-readable storage medium for storing computer programs.

[0183] Optionally, the computer-readable storage medium can be applied to the terminal in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0184] Optionally, the computer-readable storage medium can be applied to the first device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0185] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0186] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0187] The resource identifier allocation method, terminal, first device, computer-readable storage medium, and computer program product provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0188] It should be understood that the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiment," "some implementations," or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0189] Unless otherwise specified, any step performed by the terminal / first device in the embodiments of this application may be executed by the processor of the terminal / first device. Unless otherwise specified, the embodiments of this application do not limit the order in which the terminal / first device performs the following steps. Furthermore, the methods used to process data in different embodiments may be the same or different methods.

[0190] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0191] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0192] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0193] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0194] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0195] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0196] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0197] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0198] The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0199] It should be noted that in the various embodiments involved in this application, all steps or some steps may be performed, as long as a complete technical solution can be formed.

[0200] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for allocating resource identifiers, characterized in that, Applied to a terminal, the method includes: A first message is multicast to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; The system receives a second message sent by a first device; wherein the second message is used to confirm that a first resource identifier and / or a first configuration parameter corresponding to the first resource identifier is allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in an option field of the second message; the plurality of devices includes the first device.

2. The method according to claim 1, characterized in that, The first message includes fast decision parameters, and the second message received from the first device includes: If the first device supports rapid allocation of resource identifiers and / or configuration parameters of resource identifiers, it receives a second message directly fed back by the first device; wherein the second message includes rapid decision parameters.

3. The method according to claim 2, characterized in that, The receipt of the second message sent by the first device includes: If the first device does not support fast allocation of resource identifiers and / or configuration parameters of resource identifiers, it receives a third message sent by the plurality of devices; wherein, the third message is used to notify the terminal that the plurality of devices allocate resource identifiers and / or configuration parameters corresponding to resource identifiers to the terminal; the third message includes the option field; A first device is determined from the plurality of devices; A fourth message is sent to the plurality of devices; wherein the fourth message is used to request the first device to allocate a resource identifier and / or configuration parameters corresponding to the resource identifier to the terminal; the fourth message includes an option field and an identifier of the first device; Receive the second message sent by the first device.

4. The method according to claims 1 to 3, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a first resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for assigning a location identifier; the first lifecycle field carries the valid lifecycle for assigning a prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources.

5. The method according to claims 1 to 3, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, a first resource identifier field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for allocating the location identifier; the first lifecycle field carries the valid lifecycle for allocating the prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources; The second resource identifier field carries a resource identifier used to notify the adaptive routing based on the current network status.

6. The method according to claims 1 to 3, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for allocating the location identifier; the first lifecycle field carries the valid lifecycle for allocating the prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the second resource identifier field carries a resource identifier used to notify routing adaptation based on the current network state.

7. A method for allocating resource identifiers, characterized in that, Applied to a first device, the method includes: The receiving terminal sends a first message; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the first device is a device in the network accessed by the terminal; Send a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in the option field of the second message.

8. The method according to claim 7, characterized in that, The first message includes fast decision parameters, and sending the second message to the terminal includes: If the first device supports rapid allocation of resource identifiers and / or configuration parameters of resource identifiers, it directly sends a second message to the terminal; wherein the second message includes rapid decision parameters.

9. The method according to claim 8, characterized in that, Sending the second message to the terminal includes: If the first device does not support fast allocation of resource identifiers and / or configuration parameters of resource identifiers, it sends a third message to the terminal; wherein, the third message is used to notify the terminal that multiple devices have allocated resource identifiers and / or configuration parameters corresponding to resource identifiers to the terminal; the third message includes the option field; The terminal sends a fourth message; wherein the fourth message is used to request the first device to allocate a resource identifier and / or configuration parameters corresponding to the resource identifier to the terminal; the fourth message includes an option field and an identifier of the first device; Send a second message to the terminal.

10. The method according to any one of claims 7 to 9, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a first resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for assigning a location identifier; the first lifecycle field carries the valid lifecycle for assigning a prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources.

11. The method according to any one of claims 7 to 9, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, a first resource identifier field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for allocating the location identifier; the first lifecycle field carries the valid lifecycle for allocating the prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the first resource identifier field carries a resource identifier used to notify of adaptive routing based on available resources; The second resource identifier field carries a resource identifier used to notify the adaptive routing based on the current network status.

12. The method according to any one of claims 7 to 9, characterized in that, The option field includes a resource identifier type field, a length field, a first lifecycle field, a second lifecycle field, and a second resource identifier field; the length field carries the length of the option field; the first lifecycle field carries the preferred lifecycle for allocating the location identifier; the first lifecycle field carries the valid lifecycle for allocating the prefix; the preferred lifecycle is greater than or equal to the valid lifecycle; the second resource identifier field carries a resource identifier used to notify routing adaptation based on the current network state.

13. A terminal, characterized in that, The terminal includes: The first sending module is used to multicast a first message to multiple devices; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier. A first receiving module is configured to receive a second message sent by a first device; wherein the second message is used to confirm that a first resource identifier and / or a first configuration parameter corresponding to the first resource identifier is allocated to a client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in an option field of the second message; the plurality of devices includes the first device.

14. A first device, characterized in that, The first device includes: The second receiving module is used to receive a first message sent by the terminal; wherein the first message is used to request the allocation of a resource identifier and / or the configuration parameters corresponding to the resource identifier; the option field of the first message is used to carry the resource identifier and / or the configuration parameters corresponding to the resource identifier; the first device is a device in the network accessed by the terminal; The second sending module is used to send a second message to the terminal; wherein the second message is used to confirm that the first resource identifier and / or the first configuration parameter corresponding to the first resource identifier is allocated to the client in the terminal for use; the first resource identifier and / or the first configuration parameter is carried in the option field of the second message.

15. A terminal, characterized in that, The terminal includes: The first memory is used to store executable instructions; The first processor, when executing executable instructions stored in the first memory, implements the resource identifier allocation method according to any one of claims 1 to 6.

16. A first device, characterized in that, The first device includes: The second memory is used to store executable instructions; The second processor, when executing executable instructions stored in the second memory, implements the resource identifier allocation method according to any one of claims 7 to 12.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the resource identifier allocation method of any one of claims 1 to 6, or the resource identifier allocation method of any one of claims 7 to 12.

18. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the resource identifier allocation method according to any one of claims 1 to 6, or the resource identifier allocation method according to any one of claims 7 to 12.

Images