Srv6-based capability information reporting method and apparatus
By carrying capability information in SRv6 messages and reporting to SRv6 controller or management function entities, the problem of difficulty in reporting capabilities of SRv6 devices is solved, accurate update and management of network node capabilities is achieved, and network resource utilization efficiency is improved.
Patent Information
- Application Number
- PCT/CN2024/079667
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-03-01
- Publication Date
- 2024-11-21
AI Technical Summary
In the prior art, SRv6 devices are difficult to effectively report capability information, resulting in network nodes being unable to accurately update and manage their own capabilities.
By carrying capability information in SRv6 messages using SID or Type Length Value (TLV) fields, the capability information of the device is reported to the SRv6 controller or management function entity, including data capabilities, computing capabilities, security capabilities, and manual capabilities to the SRv6 controller or management function entity. Intelligent AI capabilities and programmable capabilities, etc.
It realizes the reporting of capabilities information of SRv6 devices, ensuring that network nodes can accurately update and manage their capabilities, and improving network resource utilization efficiency and management accuracy.
Smart Images

Figure CN2024079667_21112024_PF_FP_ABST
Abstract
Description
SRv6-based capability information reporting method and device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This disclosure claims priority to Chinese patent application No. 202310546484.9, filed on May 15, 2023, entitled “Capability Information Reporting Method and Device Based on SRv6”, which is incorporated herein by reference in its entirety. Technical Field
[0003] The present disclosure relates to the field of communication technologies, and in particular to a method and device for reporting capability information based on SRv6. Background Art
[0004] Segment Routing IPv6 (SRv6) in Internet Protocol Version 6 (IPv6) is the application of Segment Routing (SR) technology to IPv6 networks. SRv6 explicitly specifies the forwarding path for a packet by inserting a Segment Routing Header (SRH) into an IPv6 packet and including the Segment IDentity (SID) list of all segments that the path traverses.
[0005] Related technologies add functional planes to the existing communication plane of the network architecture, such as the data plane, computing plane, intelligence plane, and security plane. The data plane collects and stores all data from mobile users and intelligent network elements, which can be subscribed to by the artificial intelligence plane for specific purposes. The computing plane mainly collects the computing power of each node in the network and provides computing power to the outside world. The intelligence plane mainly collects the intelligent capabilities of each node in the network and exposes intelligent functions to the outside world. The security plane mainly collects the security capabilities of each node in the network and exposes security functions to the outside world. Each node in the network needs to report and update its own capabilities.
[0006] How to report device capability information is an urgent problem to be solved.
[0007] Summary of the Invention
[0008] The embodiments of the present disclosure provide a method and apparatus for reporting capability information of segment routing (SRv6) based on IPv6, so as to implement capability information reporting of a device.
[0009] In a first aspect, an embodiment of the present disclosure provides a method for reporting capability information of segment routing (SRv6) based on IPv6, which is applied to a network side and includes:
[0010] Report capability information to the SRv6 controller or management function entity. The capability information is used to represent the capabilities of the SRv6 device and is carried in the SRv6 message.
[0011] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0012] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0013] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0014] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0015] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0016] Optionally, the capability type includes but is not limited to at least one of the following:
[0017] Data capabilities;
[0018] Computing ability;
[0019] security capabilities;
[0020] Artificial intelligence (AI) capabilities;
[0021] Control ability;
[0022] Programmability.
[0023] Optionally, the SRv6 device is an access network RAN device; and / or
[0024] The SRv6 device is a user plane function UPF entity.
[0025] Optionally, before reporting the capability information to the SRv6 controller or management function entity, the step further includes:
[0026] Receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
[0027] In a second aspect, an embodiment of the present disclosure further provides a method for reporting capability information of segment routing (SRv6) based on IPv6, which is applied to an SRv6 controller, including:
[0028] Receive capability information reported by SRv6 devices;
[0029] Reporting the capability information to the management function entity;
[0030] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0031] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0032] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0033] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0034] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0035] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0036] Optionally, the capability type includes but is not limited to at least one of the following:
[0037] Data capabilities;
[0038] Computing ability;
[0039] security capabilities;
[0040] Artificial intelligence (AI) capabilities;
[0041] Control ability;
[0042] Programmability.
[0043] Optionally, before reporting the capability information to the management function entity, the method further includes:
[0044] Receive a reporting request message sent by the management function entity for requesting the capability information.
[0045] Optionally, before receiving the capability information reported by the SRv6 device, the step further includes:
[0046] Send a report request message for requesting the capability information to the SRv6 device.
[0047] In a third aspect, an embodiment of the present disclosure further provides a method for reporting capability information of segment routing (SRv6) based on IPv6, which is applied to a management function entity, including:
[0048] Receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device and is carried in an SRv6 message.
[0049] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0050] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0051] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0052] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0053] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0054] Optionally, the capability type includes but is not limited to at least one of the following:
[0055] Data capabilities;
[0056] Computing ability;
[0057] security capabilities;
[0058] Artificial intelligence (AI) capabilities;
[0059] Control ability;
[0060] Programmability.
[0061] Optionally, before receiving capability information reported by the SRv6 device or the SRv6 controller, the method further includes:
[0062] Send a report request message for requesting the capability information to the SRv6 device or the SRv6 controller.
[0063] In a fourth aspect, an embodiment of the present disclosure further provides a network device, including a memory, a transceiver, and a processor, wherein:
[0064] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the capability information reporting method for segment routing SRv6 based on IPv6 as described in the first aspect above.
[0065] In a fifth aspect, an embodiment of the present disclosure further provides an SRv6 controller, including a memory, a transceiver, and a processor, wherein:
[0066] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the capability information reporting method for segment routing SRv6 based on IPv6 as described in the second aspect above.
[0067] In a sixth aspect, an embodiment of the present disclosure further provides a management function entity, including a memory, a transceiver, and a processor, wherein:
[0068] A memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the capability information reporting method for segment routing SRv6 based on IPv6 as described in the third aspect above.
[0069] In a seventh aspect, an embodiment of the present disclosure further provides an IPv6-based segment routing SRv6 capability information reporting device, which is applied to a network side and includes:
[0070] The first reporting unit is configured to report capability information to the SRv6 controller or management function entity, where the capability information is used to represent the capability of the SRv6 device and is carried by the SRv6 message.
[0071] In an eighth aspect, an embodiment of the present disclosure further provides an IPv6-based segment routing (SRv6) capability information reporting device, which is applied to an SRv6 controller and includes:
[0072] A second receiving unit is configured to receive capability information reported by an SRv6 device;
[0073] A second reporting unit, configured to report the capability information to the management function entity;
[0074] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0075] In a ninth aspect, an embodiment of the present disclosure further provides an IPv6-based segment routing SRv6 capability information reporting device, which is applied to a management function entity, including:
[0076] The third receiving unit is configured to receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device and is carried by an SRv6 message.
[0077] In the tenth aspect, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the capability information reporting method of IPv6-based segment routing SRv6 as described in the first aspect above.
[0078] In the eleventh aspect, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the capability information reporting method of IPv6-based segment routing SRv6 as described in the second aspect above.
[0079] In the twelfth aspect, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the capability information reporting method of IPv6-based segment routing SRv6 as described in the third aspect above.
[0080] The present disclosure provides a method and apparatus for reporting capability information of IPv6-based segment routing (SRv6), which reports capability information to an SRv6 controller or management function entity through SRv6 technology, thereby realizing capability reporting of SRv6 devices. BRIEF DESCRIPTION OF THE DRAWINGS
[0081] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0082] FIG1 is a flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0083] FIG2 is a second flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0084] FIG3 is a third flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0085] FIG4 is a fourth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0086] FIG5 is a fifth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0087] FIG6 is a sixth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure;
[0088] 7 is a schematic diagram of a structure of a device for reporting capability information of segment routing SRv6 based on IPv6 according to an embodiment of the present disclosure;
[0089] 8 is a second structural diagram of a capability information reporting device based on IPv6 segment routing SRv6 provided in an embodiment of the present disclosure;
[0090] 9 is a third structural diagram of a capability information reporting device based on IPv6 segment routing SRv6 provided in an embodiment of the present disclosure;
[0091] FIG10 is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure;
[0092] FIG11 is a schematic diagram of the structure of an SRv6 controller provided in an embodiment of the present disclosure;
[0093] FIG12 is a schematic diagram of the structure of a management function entity provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0094] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.
[0095] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.
[0096] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.
[0097] The technical solution provided by the embodiments of the present disclosure can be applicable to a variety of systems, especially 5G (5th Generation Mobile Communication Technology, fifth generation mobile communication technology) system. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal devices and network devices. The system may also include core network parts, such as the Evolved Packet System (EPS), 5G System (5GS), etc.
[0098] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present disclosure.
[0099] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.
[0100] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO. It can also use diversity transmission, precoding, or beamforming.
[0101] To facilitate understanding of the embodiments of the present disclosure, the following introduces terms or background related to the embodiments of the present disclosure:
[0102] Segment Routing IPv6 (SRv6) of Internet Protocol Version 6 (IPv6):
[0103] SRv6 is the application of Segment Routing (SR) technology to IPv6 networks. SRv6 explicitly specifies the forwarding path for a packet by inserting a Segment Routing Header (SRH) into an IPv6 packet and adding the Segment IDentity (SID) of all the segments that the path traverses, known as the SID List, to the SRH.
[0104] Segment Identifier SID:
[0105] SRv6 technology uses 128-bit IPv6 addresses as SIDs. In SRv6, SIDs are used to define certain network functions and represent certain network instructions. SRv6 SIDs use IPv6 address format but do not correspond to any interface address on any device. Table 1 shows the SRv6 SID format provided by this disclosure. The SID format is as follows:
[0106] Table 1. SRv6 SID format
[0107] 1. The locator is an identifier assigned to a network node and used for routing and forwarding packets. In an SRv6 SID, the locator is a variable-length field to accommodate networks of varying sizes.
[0108] 2. Function is used to express the forwarding action to be performed by the instruction, which is equivalent to the opcode of a computer instruction. In SRv6 network programming, different forwarding behaviors are expressed by different Functions. SRv6 SID Endpoint Behaviors is the Function in the SID.
[0109] 3. Arguments are the parameters required when executing a command. These parameters may include streams, services, or any other relevant information. For example, if you define a command to fragment a network message, you can include the fragment length in the Arguments field.
[0110] It should be understood that as long as Locator+Function+Arguments<=128 is ensured, the number of bits occupied by each part is not specified.
[0111] SRv6 extension header:
[0112] To implement Segment Routing based on the IPv6 forwarding plane, a new type of IPv6 routing extension header is added, called the Segment Routing Header (SRH). This extension header specifies an IPv6 explicit path and stores IPv6 path constraint information (Segment List).
[0113] SRH Type-Length-Value (TLV):
[0114] TLVs provide metadata for segment processing.
[0115] TLV includes Type, Length, and Variable-length data
[0116] Type field: An 8-bit code point from the "Segment Routing Header TLV" IANA-SRHTLV. Unrecognized types MUST be ignored upon receipt.
[0117] Length field: The length of the variable-length data field (in bytes).
[0118] Variable-length data field: type-specific data.
[0119] A Type-Length-Value (TLV) entry contains optional information that can be used by the node identified in the Destination Address (DA) of the packet.
[0120] In related technologies, SRv6 devices only report their own identification information. How to report the device's capability information is an urgent problem to be solved.
[0121] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.
[0122] FIG1 is a flow chart of a method for reporting capability information of segment routing (SRv6) based on IPv6 provided by an embodiment of the present disclosure. As shown in FIG1 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing (SRv6) based on IPv6, which is applied to a network side and includes:
[0123] Step 110: Report capability information to the SRv6 controller or management function entity. The capability information is used to represent the capability of the SRv6 device and is carried by the SRv6 message.
[0124] Specifically, embodiments of the present disclosure can be applied to network elements on the access network side or the core network side, and the network element can be an SRv6 device. Optionally, the SRv6 device is an access network RAN device and / or a user plane function (UPF) entity. When applied to the access network side, the SRv6 device can be a RAN device; when applied to the core network side, the SRv6 device can be a UPF entity. It should be understood that an SRv6 device can also perform the functions of both a RAN device and a UPF entity.
[0125] The management function entity is used to manage the capability information of the terminal. The management function entity can be an operation administration and maintenance (OAM) plane, an orchestration management center, etc.
[0126] The capabilities of an SRv6 device refer to the capabilities possessed by the SRv6 device, such as attribute capabilities and performance capabilities. For example, performance capabilities can include multiple capability types: computing capabilities, intelligence capabilities, security capabilities, etc. Each capability type can also include multiple specific capabilities. For example, computing capabilities can also include computing power routing capabilities, computing power forwarding capabilities, computing power orchestration capabilities, and computing power management capabilities.
[0127] For example, a network architecture including a resource and computing power layer, a routing and connection layer, a service-oriented function layer, and an open enabling layer is used as an example:
[0128] At the resource and computing power layer, the capability types of SRv6 devices may include resource management capabilities, which are used to manage resources such as spectrum, storage, computing power, and network.
[0129] For the routing and connection layer, the capability type of the SRv6 device's capabilities may include programmable capabilities;
[0130] For the service-oriented function layer, the capability types of SRv6 devices can include various service capabilities, such as computing power service capability, connection service capability, function service capability, data service capability, artificial intelligence (AI) service capability, and security service capability.
[0131] For the open enabling layer, the capability types of SRv6 devices may include the ability to provide services for proprietary businesses and third-party applications through extraction, encapsulation, orchestration, and combination.
[0132] It should be understood that the above examples are provided to facilitate understanding of the present disclosure and should not constitute any limitation on the present disclosure. The embodiments of the present disclosure do not limit the capabilities of SRv6 devices.
[0133] The capability information is carried by the SRv6 message. The capability information is used to characterize the capability of the SRv6 device. For example, the capability information of the SRv6 device is carried in the SID field or SRH header of the SRv6 message. The specific form of the capability information can be an identifier, a character, a code, etc. It should be understood that the above is an example for the convenience of understanding the present disclosure. The embodiments of the present disclosure do not limit the specific form of the capability information, as long as it can indicate the capability of the SRv6 device.
[0134] The embodiment of the present disclosure provides a method for reporting capability information of IPv6-based segment routing SRv6, which reports capability information to an SRv6 controller or management function entity through SRv6 technology, thereby realizing capability reporting of SRv6 devices.
[0135] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0136] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0137] Specifically, a single capability identifier means that the SRv6 device has the capability indicated by (i.e., associated with) the single capability identifier. A single capability identifier is associated with only one capability. Capability information can contain one or more single capability identifiers.
[0138] A combined capability identifier indicates that the SRv6 device has at least one capability indicated by (i.e., associated with) the combined capability identifier. A combined capability identifier can be associated with one or more capabilities. Optionally, at least one capability indicated by the combined capability identifier belongs to the same capability type. Capability information can include one or more combined capability identifiers.
[0139] For example, taking computing capability as an example, computing capability may include: computing power routing capability, computing power forwarding capability, computing power orchestration capability, and computing power management capability.
[0140] Single capability identifiers are 1, 2, 3, and 4. 1 is associated with computing power routing capability, 2 is associated with computing power forwarding capability, 3 is associated with computing power orchestration capability, and 4 is associated with computing power management capability. The capability identifier carried in the reported capability information indicates that the SRv6 device has the capability associated with that single capability identifier. If the capability information carried in the SRv6 message is 1 or 4, the SRv6 device has computing power routing capability and computing power management capability.
[0141] The combination capability identifiers are 5, 6, 7, 8, 9, and 10. 5 is associated with computing power routing capability and computing power forwarding capability, 6 with computing power routing capability and computing power orchestration capability, 7 with computing power routing capability and computing power management capability, 8 with computing power routing capability, computing power forwarding capability, and computing power orchestration capability, 9 with computing power routing capability, computing power forwarding capability, and computing power management capability, 10 with computing power forwarding capability, computing power orchestration capability, and computing power management capability, and 11 with computing power routing capability, computing power forwarding capability, computing power orchestration capability, and computing power management capability. The combination capability identifier carried in the reported capability information indicates that the SRv6 device has the capabilities associated with that combination capability identifier. For example, if the capability information carried in the SRv6 message is 8, the SRv6 device has computing power routing capability, computing power forwarding capability, and computing power orchestration capability.
[0142] It should be understood that using numbers as capability identifiers is an example for facilitating understanding of the present disclosure, and the embodiments of the present disclosure do not limit the specific form of capability identifiers. For example, English abbreviations, binary codes, etc. can also be used as capability identifiers.
[0143] The embodiments of the present disclosure indicate the capabilities of the SRv6 device through the capability identifier, thereby realizing the indication of the capabilities of the SRv6 device and thus realizing the reporting of the capabilities of the SRv6 device.
[0144] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0145] Specifically, when the capabilities of an SRv6 device involve multiple types, different capability types may be indicated in different field positions.
[0146] For example, taking a single capability identifier as an example:
[0147] (1) Capabilities associated with a single capability identifier: Single capability identifiers are 1 and 2;
[0148] When the capability type associated with the capability identifiers (1 and 2) is data capability: 1 represents data acquisition and 2 represents data preprocessing;
[0149] When the capability type associated with the capability identifiers (1 and 2) is security capability: 1 represents security encryption capability, and 2 represents security authentication capability.
[0150] (2) Capability type associated with field position:
[0151] Field position 1 (bits 1-2) associates the capability type with data capability;
[0152] Field position 2 (bits 3-4) associates the capability type as security capability.
[0153] (3) The capability information reported is: 12 (field position 1) 12 (field position 2);
[0154] Field position 1 contains single capability identifiers 1 and 2. If the capability type associated with field position 1 is data capability, then the single capability identifiers 1 and 2 in field position 1 represent data acquisition and data preprocessing, indicating that the SRv6 device has data acquisition and data preprocessing capabilities. Field position 2 contains single capability identifiers 1 and 2. If the capability type associated with field position 2 is security capability, then the single capability identifiers 1 and 2 in field position 2 represent security encryption capability and security authentication capability, indicating that the SRv6 device has security encryption capability and security authentication capability. That is, capability information 1212 can indicate that the SRv6 device has data acquisition capability, data preprocessing capability, security encryption capability, and security authentication capability.
[0155] For combined capability identifiers, refer to the above examples for single capability identifiers and will not be repeated here. It should be understood that the above examples are provided to facilitate understanding of the present disclosure, and the present disclosure does not limit the specific relationship between field positions and capability types, the field positions where capability identifiers are located, and the field lengths occupied by each field position.
[0156] The embodiments of the present disclosure distinguish capability types by field position, thereby enabling reporting of the capabilities of an SRv6 device when the capabilities of the SRv6 device involve multiple capability types.
[0157] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0158] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0159] Specifically, the capability information is indicated by the segment identifier SID in the SRv6 message:
[0160] Optionally, the capability information is indicated by the parameter Arguments field in the SID, and the Arguments field may be referred to as Arg for short.
[0161] Table 1 is a SID format for indicating capability information provided by an embodiment of the present disclosure:
[0162] Table 1. SID format used to indicate capability information
[0163] As shown in Table 1, the Arguments field can carry SRv6 device capability information. Optionally, the capability information can be a capability identifier, with different capability identifiers in the Arguments field representing different capabilities of the SRv6 device. It should be understood that capability identifiers can be numbers or other forms, and this disclosure does not limit their form.
[0164] Taking data capability as an example, the single capability identifier is: 1 represents data acquisition, 2 represents data preprocessing, 3 represents data fusion, 4 represents data security, 5 represents data storage, and 6 represents data forwarding; the combined capability identifier is: 7 represents the combination of data acquisition and data preprocessing capabilities, and 8 represents the combination of data acquisition, data preprocessing and fusion capabilities, etc.
[0165] The capability type corresponding to the capability identifier indicated by the Arguments field can be pre-defined. If the capabilities of an SRv6 device involve multiple capability types, refer to the above introduction and will not be repeated here.
[0166] Optionally, when the capability information is indicated by the segment identifier SID in the SRv6 message, the value of Locator + Function(s) + Arguments <= 128 is required. If the sum of the three lengths is less than 128 bits, the remaining bits of the SID are set to 0. The size of each part can be determined based on the network scale.
[0167] The Arg part can also carry a single capability identifier, or multiple single capability identifiers or combined capability identifiers. For example, if only identifier 1 is carried, it means that this SRv6 device has data collection capability; if different bits carry identifiers 1, 2, and 3 respectively, it means that this node has data collection, data preprocessing, and data fusion capabilities; if identifier 7 carries multiple combined capabilities, it means that this node has data collection and data preprocessing capabilities.
[0168] The Arg field indicates the capabilities of the SRv6 device. The embodiments of the present disclosure do not impose any restrictions on the form, order, and combination of capability identifiers carried by the Arg field.
[0169] The capability information is indicated by the type-length-value TLV field in the header of the SRv6 message:
[0170] Optionally, the type-length-value TLV field in the header of the SRv6 message may be an SRH TLV field. Optionally, the variable-length data field in the type-length-value TLV field indicates capability information, such as indicating the capability identifier of the SRv6 device.
[0171] Table 2 shows the TLV field format for indicating capability information provided by an embodiment of the present disclosure:
[0172] Table 2. TLV field format used to indicate capability information
[0173] It should be understood that X indicates that the length of the variable-length data is not limited and can be customized according to needs; and the order of the three identifiers in the TLV can include but is not limited to the above format.
[0174] Optionally, since unrecognizable types in the TLV field are ignored upon receipt, the Type field may be used to indicate the capability type to which the capability information indicated by the TLV field belongs, and the capability type may be indicated by the Type field. That is, the capability type associated with the capability identifier may be indicated by the Type field, and the capability identifier may be indicated by the variable-length data field.
[0175] As shown in Table 2, capability information can be defined in the optional TLV field of the SRH header. For example, if the capability type is data capability, Type: SJNL represents the capability type, Length: X represents the length, and V (variable-length data): carries the capability identifier. 1, 2, 3, etc. represent different data capabilities. For example, 0 represents no data capability information, 1 represents data acquisition, 2 represents data preprocessing, 3 represents data fusion, 4 represents data security, 5 represents data storage, 6 represents data forwarding, 7 represents a combination of data acquisition and preprocessing capabilities, and 8 represents a combination of data acquisition, preprocessing, and fusion capabilities, and so on.
[0176] Optionally, when the capability information is indicated by the type-length-value TLV field in the header of the SRv6 message, it is required that the total length of T, L, and V is aligned with the SID in the SRH header. As for the number of bits of each part, it can be determined according to the scale of the network, where the V part can also carry a single capability identifier, or multiple single capability identifiers or combined capability identifiers. For example: if only identifier 1 is carried, it means that the SRv6 device has data collection capability; different numbers of bits carry identifiers 1, 2, and 3 respectively, which means that the SRv6 device has data collection, data preprocessing, and data fusion capabilities; carrying identifier 7 of multiple combined capabilities, it means that this node has data collection and preprocessing capabilities. The V part indicates the capabilities of the SRv6 device, and there is no restriction on the form, order, and combination of the identifiers carried by the V part.
[0177] Optionally, the Flags in the SRH, or the Tag, or the Arg portion in the SID indicates that the capability information of the SRv6 device is obtained in the TLV.
[0178] The embodiments of the present disclosure indicate capability information through a segment identifier SID in an SRv6 message, or through a type-length-value TLV field in a header of an SRv6 message, thereby providing a method for indicating capability information through an SRv6 message and implementing capability reporting of an SRv6 device.
[0179] Optionally, the capability type includes but is not limited to at least one of the following:
[0180] Data capabilities;
[0181] Computing ability;
[0182] security capabilities;
[0183] Artificial intelligence (AI) capabilities;
[0184] Control ability;
[0185] Programmability.
[0186] Specifically, computing capabilities may include but are not limited to at least one of the following capabilities: computing power routing capability, computing power forwarding capability, computing power orchestration capability, computing power management capability, etc.
[0187] Security capabilities may include but are not limited to at least one of the following: security encryption capability, security authentication capability, security perception capability, security protection capability, etc.
[0188] AI capabilities may include but are not limited to at least one of the following: training capability, algorithm capability, model reasoning capability, model training capability, model generation capability, model optimization capability, model sharing capability, model management capability, model compression capability, etc.
[0189] The control capability may include but is not limited to at least one of the following capabilities: connection management capability, mobility management capability, policy definition capability, user authentication capability, etc.;
[0190] Programmable capabilities may include but are not limited to at least one of the following capabilities: forwarding capability, encapsulation capability, decapsulation capability, traffic distribution capability, etc.
[0191] Optionally, before reporting the capability information to the SRv6 controller or management function entity, the step further includes:
[0192] Receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
[0193] Specifically, the SRv6 device may send capability information to the SRv6 controller or the management function entity in response to the report request message. It should be understood that the embodiment of the present disclosure does not limit the name of the report request message, as long as the capability information request can be realized.
[0194] The embodiment of the present disclosure provides a method for reporting capability information of IPv6-based segment routing SRv6, which reports capability information to an SRv6 controller or management function entity through SRv6 technology, thereby realizing capability reporting of SRv6 devices.
[0195] FIG2 is a second flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided by an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6, which is applied to an SRv6 controller and includes:
[0196] Step 210: Receive capability information reported by the SRv6 device.
[0197] Step 220: reporting the capability information to the management function entity;
[0198] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0199] For the introduction of capability information, SRv6 device capabilities, and management function entities, refer to the above introduction and will not be repeated here.
[0200] The embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6. The SRv6 controller can receive capability information reported by the SRv6 device through the SRv6 technology, and report the capability information of the SRv6 device to the management function entity, thereby realizing capability reporting of the SRv6 device.
[0201] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0202] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0203] For how to indicate capability information, please refer to the above introduction and will not be repeated here.
[0204] The embodiments of the present disclosure indicate capability information through a segment identifier SID in an SRv6 message, or through a type-length-value TLV field in a header of an SRv6 message, thereby providing a method for indicating capability information through an SRv6 message and implementing capability reporting of an SRv6 device.
[0205] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0206] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0207] The embodiments of the present disclosure indicate the capabilities of the SRv6 device through the capability identifier, thereby realizing the indication of the capabilities of the SRv6 device and thus realizing the reporting of the capabilities of the SRv6 device.
[0208] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0209] For the introduction of capability identification, please refer to the above introduction and will not be repeated here.
[0210] The embodiments of the present disclosure distinguish capability types by field position, thereby enabling reporting of the capabilities of an SRv6 device when the capabilities of the SRv6 device involve multiple capability types.
[0211] Optionally, the capability type includes but is not limited to at least one of the following:
[0212] Data capabilities;
[0213] Computing ability;
[0214] security capabilities;
[0215] Artificial intelligence (AI) capabilities;
[0216] Control ability;
[0217] Programmability.
[0218] For the introduction of ability types, please refer to the above introduction and will not be repeated here.
[0219] Optionally, before reporting the capability information to the management function entity, the method further includes:
[0220] Receive a reporting request message sent by the management function entity for requesting the capability information.
[0221] Optionally, before receiving the capability information reported by the SRv6 device, the step further includes:
[0222] Send a report request message for requesting the capability information to the SRv6 device.
[0223] FIG3 is a flow chart of a third method for reporting capability information of segment routing SRv6 based on IPv6 provided by an embodiment of the present disclosure. As shown in FIG3 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6, which is applied to a management function entity and includes:
[0224] Step 310: Receive capability information reported by an SRv6 device or an SRv6 controller. The capability information is used to represent the capability of the SRv6 device and is carried by an SRv6 message.
[0225] For the introduction of capability information, SRv6 device capabilities, and management function entities, refer to the above introduction and will not be repeated here.
[0226] The present disclosure provides an IPv6-based segment routing SRv6 capability information reporting method. The management function entity can receive capability information reported by SRv6 devices or SRv6 controllers through SRv6 technology, thereby realizing capability reporting of SRv6 devices.
[0227] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0228] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0229] For how to indicate capability information, please refer to the above introduction and will not be repeated here.
[0230] The embodiments of the present disclosure indicate capability information through a segment identifier (SID) in an SRv6 message, or through a type-length-value (TLV) field in a header of an SRv6 message, thereby providing a method for indicating capability information through an SRv6 message and implementing capability reporting of an SRv6 device.
[0231] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0232] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0233] The embodiments of the present disclosure indicate the capabilities of the SRv6 device through the capability identifier, thereby realizing the indication of the capabilities of the SRv6 device and thus realizing the reporting of the capabilities of the SRv6 device.
[0234] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0235] The embodiments of the present disclosure distinguish capability types by field position, thereby enabling reporting of the capabilities of an SRv6 device when the capabilities of the SRv6 device involve multiple capability types.
[0236] For the introduction of capability identification, please refer to the above introduction and will not be repeated here.
[0237] Optionally, the capability type includes but is not limited to at least one of the following:
[0238] Data capabilities;
[0239] Computing ability;
[0240] security capabilities;
[0241] Artificial intelligence (AI) capabilities;
[0242] Control ability;
[0243] Programmability.
[0244] For the introduction of ability types, please refer to the above introduction and will not be repeated here.
[0245] Optionally, before receiving capability information reported by the SRv6 device or the SRv6 controller, the method further includes:
[0246] Send a report request message for requesting the capability information to the SRv6 device or the SRv6 controller.
[0247] Taking the capability type as data capability, the capability information as data capability information, and the management function entity as the data capability orchestration management center as an example, the SRv6-based capability information reporting method provided by the present disclosure is introduced in combination with multiple embodiments:
[0248] FIG4 is a fourth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided by an embodiment of the present disclosure. As shown in FIG4 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6, including:
[0249] Step 1: The SRv6 device sends a device data capability reporting request message to its SRv6 controller, reporting its own data capability information through the device data capability reporting request message. The data capability information is carried in the SID or TLV.
[0250] Step 2: After receiving the data capability information reported by the SRv6 device, the SRv6 controller sends a device data capability reporting response message to the SRv6 device to notify the SRv6 device that it has received the reported capability information.
[0251] Step 3: The SRv6 controller reports the collected SRv6 device data capability information (such as capability identifier) and / or the capability type (such as data capability) indicated by the capability information to the data capability orchestration management center through a device data capability reporting request message.
[0252] Step 4: After receiving the reported data capability information, the data orchestration management center sends a device data capability reporting response to the SRv6 controller to notify the SRv6 controller that the reported capability information has been received.
[0253] In the embodiment of the present disclosure, the SRv6 device actively reports capability information to the SRv6 controller, and the SRv6 controller actively reports capability information of the SRv6 device to the management function entity.
[0254] FIG5 is a fifth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided by an embodiment of the present disclosure. As shown in FIG5 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6, including:
[0255] Step 1: The SRv6 device sends a device data capability reporting request message to its SRv6 controller, reporting its own data capability information through the device data capability reporting request message. The data capability information is carried in the SID or TLV.
[0256] Step 2: After receiving the data capability information reported by the SRv6 device, the SRv6 controller sends a device data capability reporting response message to the SRv6 device to notify the SRv6 device that it has received the reported capability information.
[0257] Step 3: The data orchestration management center sends a device data capability reporting request message to the SRv6 controller, actively obtaining the data capability information of the SRv6 device from the SRv6 controller.
[0258] Step 4: The SRv6 controller reports the collected SRv6 device data capability information (such as capability identifier) and / or the capability type (such as data capability) indicated by the capability information to the data capability orchestration management center through a device data capability reporting response message.
[0259] In the disclosed embodiment, the SRv6 device proactively reports capability information to the SRv6 controller, and the data orchestration management center proactively obtains data capability information of the SRv6 device from the SRv6 controller.
[0260] FIG6 is a sixth flow chart of a method for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure. As shown in FIG6 , an embodiment of the present disclosure provides a method for reporting capability information of segment routing SRv6 based on IPv6, including:
[0261] Step 1: The SRv6 device sends a device data capability reporting request to the data management and orchestration center, reporting its own data capability information through the device data capability reporting request. The data capability information is carried in the SID or TLV.
[0262] Step 2: After receiving the reported data capability information, the data orchestration management center responds to the device data capability report.
[0263] In the disclosed embodiment, the SRv6 device may directly report data capability information to the data orchestration management center (also referred to as the data plane).
[0264] Optionally, the SRv6 device in each of the above embodiments may be a UPF, or a RAN or other network functions.
[0265] Optionally, the capability information in each of the above embodiments may also carry the computing capability, security capability, AI capability, etc. of the SRv6 device.
[0266] Referring to FIG. 7 , FIG. 7 is a schematic diagram of a structure of a device for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure. The embodiment of the present disclosure provides a device for reporting capability information of segment routing SRv6 based on IPv6, which is applied to the network side and includes:
[0267] The first reporting unit 710 is configured to report capability information to the SRv6 controller or management function entity, where the capability information is used to represent the capability of the SRv6 device and is carried by an SRv6 message.
[0268] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0269] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0270] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0271] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0272] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0273] Optionally, the capability type includes but is not limited to at least one of the following:
[0274] Data capabilities;
[0275] Computing ability;
[0276] security capabilities;
[0277] Artificial intelligence (AI) capabilities;
[0278] Control ability;
[0279] Programmability.
[0280] Optionally, the SRv6 device is an access network RAN device; and / or
[0281] The SRv6 device is a user plane function UPF entity.
[0282] Optionally, the device further includes: a first receiving unit;
[0283] The first receiving unit is configured to receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
[0284] The methods and devices provided in the various embodiments of the present disclosure are based on the same application concept. Since the capability information reporting method based on IPv6 segment routing SRv6 applied on the network side and the capability information reporting device based on IPv6 segment routing SRv6 applied on the network side solve problems based on similar principles and can achieve the same technical effects, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0285] 8 , which is a second structural diagram of a device for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure, provides a device for reporting capability information of segment routing SRv6 based on IPv6, applied to an SRv6 controller, including:
[0286] The second receiving unit 810 is configured to receive capability information reported by an SRv6 device;
[0287] A second reporting unit 820 is configured to report the capability information to the management function entity;
[0288] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0289] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0290] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0291] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0292] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0293] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0294] Optionally, the capability type includes but is not limited to at least one of the following:
[0295] Data capabilities;
[0296] Computing ability;
[0297] security capabilities;
[0298] Artificial intelligence (AI) capabilities;
[0299] Control ability;
[0300] Programmability.
[0301] Optionally, the second receiving unit 810 is further configured to receive a reporting request message sent by the management function entity for requesting the capability information.
[0302] Optionally, the device further includes a second sending unit;
[0303] The second sending unit is configured to send a reporting request message for requesting the capability information to the SRv6 device.
[0304] The methods and devices provided in the various embodiments of the present disclosure are based on the same application concept. Since the capability information reporting method for segment routing SRv6 based on IPv6 applied to the SRv6 controller and the capability information reporting device for segment routing SRv6 based on IPv6 applied to the SRv6 controller solve problems based on similar principles and can achieve the same technical effects, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0305] Referring to FIG. 9 , FIG. 9 is a third structural diagram of a device for reporting capability information of segment routing SRv6 based on IPv6 provided in an embodiment of the present disclosure. The embodiment of the present disclosure provides a device for reporting capability information of segment routing SRv6 based on IPv6, which is applied to a management function entity and includes:
[0306] The third receiving unit 910 is configured to receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to represent the capability of the SRv6 device and is carried by an SRv6 message.
[0307] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0308] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0309] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0310] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0311] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0312] Optionally, the capability type includes but is not limited to at least one of the following:
[0313] Data capabilities;
[0314] Computing ability;
[0315] security capabilities;
[0316] Artificial intelligence (AI) capabilities;
[0317] Control ability;
[0318] Programmability.
[0319] Optionally, the device further includes a third sending unit;
[0320] The third sending unit is configured to send a reporting request message for requesting the capability information to the SRv6 device or the SRv6 controller.
[0321] The methods and devices provided in the various embodiments of the present disclosure are based on the same application concept. Since the capability information reporting method based on IPv6 segment routing SRv6 applied to the management function entity and the capability information reporting device based on IPv6 segment routing SRv6 applied to the management function entity solve the problem based on similar principles and can achieve the same technical effects, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0322] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0323] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0324] FIG10 is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure. As shown in FIG10 , the network device includes a memory 1020, a transceiver 1000, and a processor 1010, wherein:
[0325] The memory 1020 is used to store computer programs; the transceiver 1000 is used to send and receive data under the control of the processor 1010; the processor 1010 is used to read the computer program in the memory 1020 and perform the following operations:
[0326] Report capability information to the SRv6 controller or management function entity. The capability information is used to represent the capabilities of the SRv6 device and is carried in the SRv6 message.
[0327] In FIG10 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1010 and memory represented by memory 1020. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface 1030 provides an interface. The transceiver 1000 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1010 when performing operations.
[0328] The processor 1010 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0329] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0330] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0331] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0332] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0333] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0334] Optionally, the capability type includes but is not limited to at least one of the following:
[0335] Data capabilities;
[0336] Computing ability;
[0337] security capabilities;
[0338] Artificial intelligence (AI) capabilities;
[0339] Control ability;
[0340] Programmability.
[0341] Optionally, the SRv6 device is an access network RAN device; and / or
[0342] The SRv6 device is a user plane function UPF entity.
[0343] Optionally, before reporting the capability information to the SRv6 controller or management function entity, the step further includes:
[0344] Receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
[0345] It should be noted here that the above-mentioned network device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned embodiment of the capability information reporting method based on IPv6 segment routing SRv6 applied to the network side, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.
[0346] FIG11 is a schematic diagram of the structure of an SRv6 controller provided in an embodiment of the present disclosure. As shown in FIG11 , the SRv6 controller includes a memory 1120 , a transceiver 1100 , and a processor 1110 , wherein:
[0347] The memory 1120 is used to store computer programs; the transceiver 1100 is used to send and receive data under the control of the processor 1110; the processor 1110 is used to read the computer program in the memory 1120 and perform the following operations:
[0348] Receive capability information reported by SRv6 devices;
[0349] Reporting the capability information to the management function entity;
[0350] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0351] In FIG11 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1110 and memory represented by memory 1120. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface 1130 provides an interface. The transceiver 1100 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1110 when performing operations.
[0352] The processor 1110 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0353] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0354] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0355] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0356] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0357] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0358] Optionally, the capability type includes but is not limited to at least one of the following:
[0359] Data capabilities;
[0360] Computing ability;
[0361] security capabilities;
[0362] Artificial intelligence (AI) capabilities;
[0363] Control ability;
[0364] Programmability.
[0365] Optionally, before reporting the capability information to the management function entity, the method further includes:
[0366] Receive a reporting request message sent by the management function entity for requesting the capability information.
[0367] Optionally, before receiving the capability information reported by the SRv6 device, the step further includes:
[0368] Send a report request message for requesting the capability information to the SRv6 device.
[0369] It should be noted here that the above-mentioned SRv6 controller provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned IPv6-based segment routing SRv6 capability information reporting method embodiment applied to the SRv6 controller, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.
[0370] FIG12 is a schematic diagram of the structure of a management function entity provided in an embodiment of the present disclosure. As shown in FIG12 , the management function entity includes a memory 1220, a transceiver 1200, and a processor 1210, wherein:
[0371] The memory 1220 is used to store computer programs; the transceiver 1200 is used to send and receive data under the control of the processor 1210; the processor 1210 is used to read the computer program in the memory 1220 and perform the following operations:
[0372] Receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device and is carried in an SRv6 message.
[0373] In FIG12 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1210 and memory represented by memory 1220. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface 1230 provides an interface. The transceiver 1200 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 when performing operations.
[0374] The processor 1210 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0375] Optionally, the capability information is indicated by a segment identifier SID in the SRv6 message; or
[0376] The capability information is indicated by a type-length-value (TLV) field in a header of the SRv6 message.
[0377] Optionally, the capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier;
[0378] The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
[0379] Optionally, the capability identifier is used to indicate the capabilities included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
[0380] Optionally, the capability type includes but is not limited to at least one of the following:
[0381] Data capabilities;
[0382] Computing ability;
[0383] security capabilities;
[0384] Artificial intelligence (AI) capabilities;
[0385] Control ability;
[0386] Programmability.
[0387] Optionally, before receiving capability information reported by the SRv6 device or the SRv6 controller, the method further includes:
[0388] Send a report request message for requesting the capability information to the SRv6 device or the SRv6 controller.
[0389] It should be noted here that the above-mentioned management function entity provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned IPv6-based segment routing SRv6 capability information reporting method embodiment applied to the management function entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.
[0390] On the other hand, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is configured to cause the processor to execute the methods provided in the above embodiments, including:
[0391] Report capability information to the SRv6 controller or management function entity. The capability information is used to represent the capabilities of the SRv6 device and is carried in the SRv6 message.
[0392] On the other hand, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is configured to cause the processor to execute the methods provided in the above embodiments, including:
[0393] Receive capability information reported by SRv6 devices;
[0394] Reporting the capability information to the management function entity;
[0395] The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
[0396] On the other hand, an embodiment of the present disclosure further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is configured to cause the processor to execute the methods provided in the above embodiments, including:
[0397] Receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device and is carried in an SRv6 message.
[0398] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.
[0399] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.
[0400] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0401] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0402] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0403] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.
Claims
1. A capability information reporting method for segment routing SRv6 based on IPv6, applied to the network side, include: Report capability information to the SRv6 controller or management function entity, where the capability information is used to characterize the capability of the SRv6 device and is carried by the SRv6 message.
2. The SRv6-based capability information reporting method according to claim 1, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
3. The SRv6-based capability information reporting method according to claim 1 or 2, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
4. The SRv6-based capability information reporting method according to claim 3, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
5. The SRv6-based capability information reporting method according to claim 1 or 2, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
6. The SRv6-based capability information reporting method according to claim 1 or 2, in, The SRv6 device is an access network RAN device; and / or The SRv6 device is a user plane function UPF entity.
7. The SRv6-based capability information reporting method according to claim 1 or 2, in, Before reporting the capability information to the SRv6 controller or management function entity, the method further includes: Receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
8. A method for reporting capability information of segment routing SRv6 based on IPv6, applied to SRv6 controller, include: Receive capability information reported by SRv6 devices; Reporting the capability information to the management function entity; The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
9. The SRv6-based capability information reporting method according to claim 8, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
10. The SRv6-based capability information reporting method according to claim 8 or 9, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
11. The SRv6-based capability information reporting method according to claim 10, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
12. The SRv6-based capability information reporting method according to claim 8 or 9, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
13. The SRv6-based capability information reporting method according to claim 8 or 9, in, Before reporting the capability information to the management function entity, the method further includes: A reporting request message for requesting the capability information is received, which is sent by the management function entity.
14. The SRv6-based capability information reporting method according to claim 8 or 9, in, The receiving of capability information reported by the SRv6 device also includes: Send a report request message for requesting the capability information to the SRv6 device.
15. A method for reporting capability information of segment routing SRv6 based on IPv6, applied to a management function entity, include: Receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by an SRv6 message.
16. The SRv6-based capability information reporting method according to claim 15, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
17. The SRv6-based capability information reporting method according to claim 15 or 16, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
18. The SRv6-based capability information reporting method according to claim 17, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
19. The SRv6-based capability information reporting method according to claim 15 or 16, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
20. The SRv6-based capability information reporting method according to claim 15 or 16, in, Before receiving the capability information reported by the SRv6 device or the SRv6 controller, the method further includes: Send a report request message for requesting the capability information to the SRv6 device or the SRv6 controller.
21. A network device comprising a memory, a transceiver and a processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Report capability information to the SRv6 controller or management function entity. The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
22. An SRv6 controller comprising a memory, a transceiver and a processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Receive capability information reported by SRv6 devices; Reporting the capability information to the management function entity; in, The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
23. A management function entity, comprising a memory, a transceiver and a processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Receive capability information reported by an SRv6 device or an SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by an SRv6 message.
24. A capability information reporting device based on IPv6 segment routing SRv6, applied to the network side, include: The first reporting unit is used to report capability information to the SRv6 controller or the management function entity, where the capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
25. The SRv6-based capability information reporting device according to claim 24, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
26. The SRv6-based capability information reporting device according to claim 24 or 25, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
27. The SRv6-based capability information reporting device according to claim 26, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
28. The SRv6-based capability information reporting device according to claim 24 or 25, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
29. The SRv6-based capability information reporting device according to claim 24 or 25, in, The SRv6 device is an access network RAN device; and / or The SRv6 device is a user plane function UPF entity.
30. The SRv6-based capability information reporting device according to claim 24 or 25, in, The apparatus further includes: a first receiving unit; before reporting the capability information to the SRv6 controller or the management function entity, the first receiving unit is configured to: Receive a reporting request message sent by the SRv6 controller or the management function entity to request the capability information.
31. A capability information reporting device for segment routing SRv6 based on IPv6, applied to SRv6 controller, include: A second receiving unit, configured to receive capability information reported by an SRv6 device; A second reporting unit, used to report the capability information to the management function entity; The capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
32. The SRv6-based capability information reporting device according to claim 31, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
33. The SRv6-based capability information reporting device according to claim 31 or 32, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
34. The SRv6-based capability information reporting device according to claim 33, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
35. The SRv6-based capability information reporting device according to claim 31 or 32, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
36. The SRv6-based capability information reporting device according to claim 31 or 32, in, Before reporting the capability information to the management function entity, the second receiving unit is further used to: A reporting request message for requesting the capability information is received, which is sent by the management function entity.
37. The SRv6-based capability information reporting device according to claim 31 or 32, in, The apparatus further includes a second sending unit; before receiving the capability information reported by the SRv6 device, the second sending unit is configured to: Send a report request message for requesting the capability information to the SRv6 device.
38. A capability information reporting device based on IPv6 segment routing SRv6, applied to a management function entity, include: The third receiving unit is used to receive capability information reported by the SRv6 device or the SRv6 controller, where the capability information is used to characterize the capability of the SRv6 device, and the capability information is carried by the SRv6 message.
39. The SRv6-based capability information reporting device according to claim 38, in, The capability information is indicated by a segment identifier SID in the SRv6 message; or The capability information is indicated by a type-length-value TLV field in a header of the SRv6 message.
40. The SRv6-based capability information reporting device according to claim 38 or 39, in, The capability information includes a capability identifier, and the capability identifier includes a single capability identifier and / or a combined capability identifier; The single capability identifier is used to indicate that the SRv6 device has a capability associated with the single capability identifier, and the combined capability identifier is used to indicate that the SRv6 device has at least one capability associated with the combined capability identifier.
41. The SRv6-based capability information reporting device according to claim 40, in, The capability identifier is used to indicate the capability included in the capability type associated with the capability identifier, and the capability type associated with the capability identifier is the capability type associated with the field position where the capability identifier is located.
42. The SRv6-based capability information reporting device according to claim 38 or 39, in, The capability type of the capability is not limited to at least one of the following: Data capabilities; Computational capacity; Security capabilities; Artificial intelligence (AI) capabilities; Control ability; Programmability.
43. The SRv6-based capability information reporting device according to claim 38 or 39, in, The apparatus further includes a third sending unit; before receiving the capability information reported by the SRv6 device or the SRv6 controller, the third sending unit is used to: Send a report request message for requesting the capability information to the SRv6 device or the SRv6 controller.
44. A processor-readable storage medium storing a computer program, wherein the computer program is used to enable the processor to execute the capability information reporting method for segment routing SRv6 based on IPv6 according to any one of claims 1 to 7.
45. A processor-readable storage medium storing a computer program, wherein the computer program is used to enable the processor to execute the capability information reporting method for segment routing SRv6 based on IPv6 according to any one of claims 8 to 14.
46. A processor-readable storage medium storing a computer program, wherein the computer program is used to enable the processor to execute the capability information reporting method of segment routing SRv6 based on IPv6 according to any one of claims 15 to 20.
Citation Information
Patent Citations
Method and device for realizing in-band operations, administration and maintenance IOAM
CN108737128A
Information sending and processing method, node, controller and computer readable medium
CN112511429A
Optimizing segment routing paths using segment identifiers
US20220174016A1
