A method, device and equipment for fine-grained identification of satellite network traffic data

Abstract

The embodiment of the specification relates to the technical field of satellite communication, and provides a method, device and equipment for fine-grained identification of satellite network traffic data, the method is applied to an on-board router, and the method comprises the following steps: receiving first to-be-identified traffic parameters issued by a bearer network controller; generating a first data identifier according to the first to-be-identified traffic parameters, and sending the first data identifier as a first IPv6 segment routing SRv6 instruction to a first device; receiving first general packet radio service tunneling protocol GTP message data fed back by the first device according to the first SRv6 instruction; encapsulating the first GTP message data to obtain first bearer data containing the first SRv6 instruction; and forwarding the first bearer data to a router node of a corresponding bearer tunnel, so that the router node performs corresponding operations according to the first SRv6 instruction. Through the embodiment of the specification, the GTP tunnel traffic data can be uniquely and finely identified.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of satellite communication technology, and in particular to a method, apparatus, and device for fine-grained identification of satellite network traffic data. Background Technology

[0002] In satellite networks, fine-grained identification of traffic data ensures efficient and accurate processing and transmission of different types of traffic, providing differentiated quality of service. However, existing traffic identification methods suffer from coarse-grained labeling in 5G satellite network service transmission scenarios. Specifically, the satellite base station first encapsulates the user data with a GPRS Tunneling Protocol (GTP) header before transmitting the data to the satellite router for forwarding. The satellite router's identification granularity only extends to the tunnel data layer, failing to provide fine-grained identification for the data encapsulated within the GTP header. Therefore, the satellite router cannot perform differentiated operations such as traffic engineering, load balancing, and path orchestration on GTP tunnel data of different service types, hindering further improvements in network transmission quality. Summary of the Invention

[0003] To address the aforementioned problems in the prior art, the purpose of the embodiments in this specification is to provide a fine-grained identification method, apparatus, and device for satellite network traffic data, thereby solving the problems of coarse-grained identification and insufficient characterization ability of satellite network data in the prior art.

[0004] To solve the above-mentioned technical problems, the specific technical solutions of the embodiments in this specification are as follows:

[0005] On one hand, embodiments of this specification provide a fine-grained identification method for satellite network traffic data, applied to a satellite-borne router, the method comprising:

[0006] Receive the first traffic parameter to be identified from the bearer network controller;

[0007] A first data identifier is generated based on the first traffic parameter to be identified, and the first data identifier is sent to the first device as a first IPv6 segment routing SRv6 instruction.

[0008] Receive the first General Packet Radio Service Tunneling Protocol (GTP) message data fed back by the first device according to the first SRv6 instruction;

[0009] The first GTP message data is encapsulated to obtain first bearer data containing the first SRv6 instruction;

[0010] The first bearer data is forwarded to the router node of the corresponding bearer tunnel so that the router node can perform corresponding operations according to the first SRv6 instruction.

[0011] Furthermore, the first traffic parameter to be identified includes the UPF IPv6 address and the GTP tunnel identifier.

[0012] Further, generating the first data identifier based on the first traffic parameter to be identified includes:

[0013] Obtain the IPv6 address of the satellite base station directly connected to the satellite router;

[0014] The first data identifier is obtained by hashing the IPv6 address of the satellite base station, the IPv6 address of the UPF, and the GTP tunnel identifier using a hash function.

[0015] Furthermore, the first SRv6 instruction is transmitted between the onboard router and the first device.

[0016] Furthermore, the first GTP packet data is a service packet obtained by encapsulating the service traffic data sent by the terminal with a GTP tunnel header. The service packet includes the source and destination IPv6 addresses and the GTP tunnel identifier. The source and destination IPv6 addresses and the GTP tunnel identifier are used to generate a hash value for each service packet. The hash value is used to compare with the first SRv6 instruction. When the comparison result is consistent, the first SRv6 instruction is embedded in the service packet to obtain the first GTP packet data containing the first SRv6 instruction.

[0017] Furthermore, the destination IPv6 address of the first GTP message data containing the first SRv6 instruction is the first SRv6 instruction.

[0018] Further, the encapsulation of the first GTP message data includes:

[0019] Determine whether the destination IPv6 address of the first GTP message data is the same as the first SRv6 instruction;

[0020] If so, change the destination IPv6 address of the first GTP message data to the UPF IPv6 address corresponding to the first SRv6 instruction;

[0021] The first GTP message data is encapsulated with a bearer tunnel, and the first SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated first bearer data.

[0022] Furthermore, embodiments of this specification also provide a fine-grained identification method for satellite network traffic data, applied to a border router, the method comprising:

[0023] Receive the second traffic parameter to be identified from the bearer network controller;

[0024] A second data identifier is generated based on the second traffic parameter to be identified, and the second data identifier is sent to the second device as a second SRv6 instruction.

[0025] Receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0026] The second GTP message data is encapsulated to obtain second bearer data containing the second SRv6 instruction;

[0027] The second bearer data is forwarded to the router node of the corresponding bearer tunnel so that the router node can perform corresponding operations according to the second SRv6 instruction.

[0028] Furthermore, the second traffic parameter to be identified includes the satellite base station IPv6 address and the GTP tunnel identifier.

[0029] Further, generating the second data identifier based on the second traffic parameter to be identified includes:

[0030] Obtain the UPF IPv6 address that is routable to the border router;

[0031] The second data identifier is obtained by hashing the IPv6 address of the satellite base station, the IPv6 address of the UPF, and the GTP tunnel identifier using a hash function.

[0032] Furthermore, the second SRv6 instruction is transmitted between the border router and the second device.

[0033] Furthermore, the second GTP packet data is a service packet obtained by encapsulating the service traffic data sent by the data network with a GTP tunnel header. The service packet includes the source and destination IPv6 addresses and the GTP tunnel identifier. The source and destination IPv6 addresses and the GTP tunnel identifier are used to generate a hash value for each service packet. The hash value is used to compare with the second SRv6 instruction. When the comparison result is consistent, the second SRv6 instruction is embedded in the service packet to obtain the second GTP packet data containing the second SRv6 instruction.

[0034] Furthermore, the destination IPv6 address of the second GTP message data containing the second SRv6 instruction is the second SRv6 instruction.

[0035] Further, the encapsulation of the second GTP message data includes:

[0036] Determine whether the destination IPv6 address of the second GTP message data is the same as the second SRv6 instruction;

[0037] If so, the destination IPv6 address of the second GTP message data is changed to the IPv6 address of the satellite base station corresponding to the second SRv6 instruction;

[0038] The second GTP message data is encapsulated with a bearer tunnel, and the second SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated second bearer data.

[0039] Furthermore, embodiments of this specification also provide a fine-grained identification device for satellite network traffic data, applied to a spaceborne router, the device comprising:

[0040] The first receiving module is used to receive the first traffic parameter to be identified sent by the bearer network controller;

[0041] The first data identifier generation and sending module is used to generate a first data identifier based on the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device.

[0042] The second receiving module is used to receive the first GTP message data fed back by the first device according to the first SRv6 instruction;

[0043] The first encapsulation module is used to encapsulate the first GTP message data to obtain first bearer data containing the first SRv6 instruction;

[0044] The first forwarding module is used to forward the first bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the first SRv6 instruction.

[0045] Furthermore, embodiments of this specification also provide a fine-grained identification device for satellite network traffic data, applied to a border router, the device comprising:

[0046] The third receiving module is used to receive the second traffic parameter to be identified sent by the bearer network controller;

[0047] The second data identifier generation and sending module is used to generate a second data identifier based on the second traffic parameter to be identified, and send the second data identifier as a second SRv6 instruction to the second device.

[0048] The fourth receiving module is used to receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0049] The second encapsulation module is used to encapsulate the second GTP message data to obtain second bearer data containing the second SRv6 instruction;

[0050] The second forwarding module is used to forward the second bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the second SRv6 instruction.

[0051] In another aspect, embodiments of this specification also provide a network device, including a memory, a processor, and a computer program stored in the memory, wherein the computer program, when run by the processor, executes instructions of any of the methods described above.

[0052] In another aspect, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor of a computer device to perform instructions for any of the methods described above.

[0053] In another aspect, embodiments of this specification also provide a computer program product, which, when run by the processor of a computer device, executes instructions for any of the methods described above.

[0054] As can be seen from the technical solutions provided in the embodiments of this specification above, compared with existing network data identification methods, the embodiments of this specification convert the traffic parameters issued by the bearer network controller into SRv6 instructions and embed them into the bearer data of GTP messages. This enables the satellite router to break through the limitation of existing technologies that can only identify the bearer tunnel layer, and realize fine-grained identification of GTP internal data. This allows subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving the utilization rate of satellite network resources and the quality of service transmission.

[0055] The above description is merely an overview of some embodiments of the technical solutions in this specification. In order to better understand the technical means of some embodiments of this specification and to implement them in accordance with the content of the specification, and to make the above and other objects, features and advantages of the embodiments of this specification more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0056] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0057] Figure 1 This specification shows schematic diagrams of satellite internet architectures based on 5G systems in some embodiments;

[0058] Figure 2 This specification illustrates a schematic diagram of the data encapsulation process for satellite networks in some embodiments;

[0059] Figure 3 This specification illustrates the steps of a fine-grained identification method for satellite network traffic data applied to a spaceborne router in some embodiments of this specification;

[0060] Figure 4 This specification illustrates satellite network topology diagrams for downlink transmission scenarios in some embodiments;

[0061] Figure 5 This specification illustrates flowcharts for fine-grained data identification of satellite process data in downlink transmission scenarios, as shown in some embodiments.

[0062] Figure 6 This specification illustrates a data encapsulation diagram for fine-grained data identification of satellite process data in downlink transmission scenarios, as shown in some embodiments of this specification.

[0063] Figure 7 This specification illustrates schematic diagrams of hash mappings in some embodiments;

[0064] Figure 8 This specification illustrates a schematic representation of the mapping relationship between the bearer network controller and the spaceborne router in some embodiments;

[0065] Figure 9 This specification illustrates the steps for encapsulating the first GTP message data in some embodiments.

[0066] Figure 10 This specification shows a schematic diagram of the data packet format of the first bearer data after encapsulation in some embodiments;

[0067] Figure 11 This specification illustrates the steps of a fine-grained identification method for satellite network traffic data applied to a border router in some embodiments of this specification.

[0068] Figure 12This specification illustrates satellite network topology diagrams for uplink transmission scenarios in some embodiments;

[0069] Figure 13 This specification illustrates flowcharts for fine-grained data identification of satellite process data in uplink transmission scenarios in some embodiments;

[0070] Figure 14 This specification shows a schematic diagram of a fine-grained identification device for satellite network traffic data applied to a spaceborne router in some embodiments;

[0071] Figure 15 This specification shows a schematic diagram of a fine-grained identification device for satellite network traffic data applied to a border router in some embodiments;

[0072] Figure 16 A schematic diagram of the structure of a network device is shown in this specification.

[0073] Explanation of symbols in the attached drawings:

[0074] 1401, First receiving module;

[0075] 1402. First data identifier generation and transmission module;

[0076] 1403, Second receiving module;

[0077] 1404, First encapsulation module;

[0078] 1405, First forwarding module;

[0079] 1501, Third Receiving Module;

[0080] 1502. Second data identifier generation and transmission module;

[0081] 1503, Fourth Receiving Module;

[0082] 1504, Second encapsulation module;

[0083] 1505, Second forwarding module;

[0084] 1600. Network equipment;

[0085] 1610. Processor;

[0086] 1620. Memory;

[0087] 1630. Program;

[0088] 1640. Transceiver;

[0089] 1650, Antenna. Detailed Implementation

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

[0091] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the acquisition, storage, use, and processing of data in the technical solutions described in the embodiments of this application all comply with relevant regulations.

[0092] In the description of this application, unless otherwise stated, "and / or" is a term describing the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone, where A and B can be singular or plural. Furthermore, in the description of this disclosure, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0093] It should be noted that the terms "first," "second," etc., used in this specification, claims, and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0094] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual system or device products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel.

[0095] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0096] In the embodiments of this application, communication between devices in the communication system can be carried out according to communication protocols at any stage, such as including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR) and / or other currently known or future communication protocols.

[0097] 5G satellite internet architecture, such as Figure 1 As shown, a satellite network mainly consists of three parts: an access network, a bearer network, and a core network. The satellite-based base stations of the access network are deployed on satellites and connect to the Access Mobile Function (AMF) module of the core network via the N2 interface for transmitting control plane signaling. Simultaneously, the satellite-based base stations connect to the User Plain Function (UPF) module of the core network via the N3 interface. The UPF is deployed on the ground and is responsible for forwarding user plane data transmitted from the satellite-based base stations to external data networks, such as data centers and the Internet. Figure 1 As shown, the bearer network is located between the access network satellite base station and the core network UPF. It is responsible for encapsulating the data from the access network and transmitting it to the core network. During the transmission process, it performs traffic engineering, load balancing and other operations on the transmitted data to ensure the quality of service of the business data.

[0098] The current data encapsulation process of satellite networks is as follows: Figure 2As shown, after receiving user data, the satellite-based base station introduces it into the GTP tunnel. A User Plane GPRS Tunneling Protocol (GTP) header is encapsulated around the user data for customized processing of the user's service data. When the user data with the GTP header reaches the satellite-based router in the bearer network, it is introduced into the bearer network tunnel and further encapsulated with a bearer tunnel header to guide data forwarding to the core network. The bearer tunnel header terminates at the network boundary router preceding the UPF, while the GTP tunnel header terminates at the UPF in the core network. It should be noted that different service types of GTP tunnel data can be carried within the same bearer tunnel, and multiple types of user data can be carried within the same GTP tunnel.

[0099] The main principle behind current network traffic identification data is to add specific identification fields to the network or transport layer to distinguish different service flows. Specific implementations include: Differentiated Services Code Point (DSCP), Multiprotocol Label Switching Experimental (MPLS EXP), and IP Precedence, among other field identification methods. DSCP is a 6-bit field in IPv4 and IPv6 packets; different DSCP values ​​mark different service levels. MPLS EXP is a 3-bit field in the MPLS label; traffic entering the MPLS domain is assigned a corresponding EXP value for identification, and traffic is prioritized based on the EXP value. IP Precedence is a 3-bit field in the ToS field of the IPv4 packet header, used to identify the priority of data traffic, ensuring priority transmission of critical traffic. The above field identification method can only identify the outer layer message fields. In the 5G satellite network scenario, it cannot identify the source and destination IP addresses of the inner layer messages carrying the tunnel, nor can it perform fine-grained identification of data traffic. At the same time, it does not have enough field space to uniquely identify all tunnel traffic in the satellite network.

[0100] During user data transmission (i.e., between the onboard router and the border router), the onboard router can only identify the header of the bearer tunnel and cannot identify the finer-grained GTP tunnel data. Therefore, the onboard router cannot perform differentiated operations such as traffic engineering, load balancing, and path orchestration on GTP tunnel data of different service types, making it difficult to further improve network transmission quality.

[0101] To address the aforementioned issues, this specification provides a fine-grained identification method for satellite network traffic data, applicable to onboard routers in the aforementioned satellite internet architecture. (Refer to...) Figure 3As shown, in some embodiments of this specification, the method includes the following steps:

[0102] S101: Receive the first traffic parameter to be identified from the bearer network controller;

[0103] S102: Generate a first data identifier based on the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device;

[0104] SRv6 (Segment Routing IPv6) refers to IPv6 segment routing;

[0105] S103: Receive the first General Packet Radio Services Tunneling Protocol (GTP) message data fed back by the first device according to the first SRv6 instruction;

[0106] S104: Encapsulate the first GTP message data to obtain first bearer data containing the first SRv6 instruction;

[0107] S105: Forward the first bearer data to the router node of the corresponding bearer tunnel so that the satellite router node can perform corresponding operations according to the first SRv6 instruction.

[0108] The embodiments in this specification convert the traffic parameters issued by the bearer network controller into SRv6 instructions and embed them into the bearer data of GTP messages. This enables the satellite router to overcome the limitation of existing technologies that can only identify the bearer tunnel layer, and achieve fine-grained identification of GTP internal data. This allows subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving the utilization rate of satellite network resources and the quality of service transmission.

[0109] It should be noted that when the method is applied to a satellite router, corresponding to the downlink transmission scenario in traffic data transmission, the first device in step S102 is a satellite base station. Figure 4 This is a diagram of the satellite network topology in a downlink transmission scenario, such as... Figure 4 As shown, the satellite network topology includes multiple interconnected onboard router nodes. S1 is one of these onboard router nodes, and the curve represents the forwarding path of service traffic after a user terminal accesses the network. The bearer network controller can configure and distribute the onboard routers of the space bearer network, but it cannot configure and manage the onboard base stations. Regarding the topology, due to the dynamic nature of satellite networks, there are no fixed service traffic access nodes in the space bearer network, unlike in terrestrial networks. In terms of architecture, under the 5G NTN architecture, onboard routers do not function as service traffic entry points like terrestrial network routers; that is, service traffic in the satellite network must first be processed by the onboard base station before being forwarded to the onboard router.

[0110] Figure 5 This is a flowchart illustrating fine-grained data identification of satellite traffic data in downlink transmission scenarios, such as... Figure 5 As shown, after deploying and configuring the GTP tunnel traffic data identification function on the satellite router 1 through the bearer network controller, the first traffic parameter to be identified is sent to the satellite router 1. The satellite router 1 generates a first data identifier based on the first traffic parameter to be identified and sends the first data identifier as a first SRv6 instruction to the satellite base station. The satellite base station will encapsulate each service traffic data sent by the terminal device with a GTP tunnel header according to the received first SRv6 instruction, and send the encapsulated first GTP packet data to the satellite router 1. In this embodiment of the specification, the first GTP packet data is a service packet obtained by encapsulating the service traffic data sent by the terminal with a GTP tunnel header. The service packet includes the source and destination IPv6 addresses and the GTP tunnel identifier. The source and destination IPv6 addresses and the GTP tunnel identifier are used to generate a hash value for each service packet. The hash value is used to compare with the first SRv6 instruction. When the comparison result is consistent, the first SRv6 instruction is embedded in the service packet to obtain the first GTP packet data containing the first SRv6 instruction. Wherein, the destination IP address of the first GTP packet data containing the first SRv6 instruction is the first SRv6 instruction. After receiving the first GTP packet data, the spaceborne router 1 encapsulates a bearer tunnel header on the outer layer of the first GTP packet data and adds the first SRv6 instruction to the extension header of the outer IPv6 header of the bearer tunnel, thus obtaining the first bearer data containing the first SRv6 instruction. The spaceborne router directs the encapsulated first bearer data to the corresponding bearer tunnel according to a pre-stored mapping table and forwards it to the remaining destination router nodes in the bearer tunnel. After receiving the bearer tunnel traffic data, a certain node spaceborne router 2 in the bearer tunnel will perform corresponding operations, such as traffic statistics, ACL rule matching, policy routing, and load balancing, according to the data identifier filled in the extension header of the outer IPv6 header of the bearer tunnel. When the bearer data reaches the tail node border router in the bearer tunnel, the border router strips the bearer tunnel header and the extension header containing the data identifier, obtaining a traffic data packet containing only the GTP tunnel header, and forwards the stripped GTP tunnel traffic data to the corresponding UPF. In this way, the border router does not need to identify the service traffic; it can simply remove the first data identifier by stripping the bearer tunnel header.

[0111] Figure 6 This is a schematic diagram of data encapsulation in a downlink transmission scenario, such as... Figure 6As shown, the data transmitted between the user terminal (UE) and the satellite base station is the raw service data without encapsulation. The data transmitted between the satellite base station and satellite router 1 is GTP message data with a GTP tunnel header encapsulated on the outer layer of the raw service data. The data transmitted between satellite router 1 and the border router is bearer data with a bearer tunnel header encapsulated on the outer layer of the GTP message data. The data transmitted between the border router and the UPF is GTP message data with the bearer tunnel header stripped. The data transmitted between the UPF and the external data network (DN) is the raw service data.

[0112] In this embodiment, the first traffic parameter to be identified includes a UPF IPv6 address (128 bits) and a GTP tunnel identifier (32 bits), wherein the GTP tunnel identifier is the TEID field in the GTP packet. The specific mapping method for obtaining the first data identifier from the UPF IPv6 address, the TEID field in the GTP packet, and the IPv6 address of the directly connected satellite base station is as follows: Figure 7 As shown, a hash function is used to perform a hash operation on the IPv6 address of the satellite base station, the UPF IPv6 address, and the TEID (GTP tunnel identifier) ​​to obtain a first data identifier, which is then used as the first SRv6 instruction. Since the generated first data identifier has 128 bits, it can provide a globally unique identifier for any GTP packet data stream in a 5G satellite network. It should be noted that the first SRv6 instruction is only propagated between the satellite router and the satellite base station. It should also be noted that the data identifier and the SRv6 instruction are the same 128-bit binary string. The data identifier has SRv6 instruction functionality, meaning it can guide the routing device to complete corresponding actions. When identifying data, it is called a data identifier; when guiding router behavior, it is called an SRv6 instruction. When the data identifier is used as an SRv6 instruction, the router action is defined as follows: if the destination address of the received IP packet is the SRv6 instruction and the payload is GTP data, then pop the destination address of the IPv6 header, replace it with the IP address queried using the SRv6 instruction as an index, encapsulate the outer IPv6 header and extension header, and then add the data identifier to the extension header of the encapsulated IPv6 header.

[0113] In some embodiments of this specification, such as Figure 8 As shown, the bearer network controller and the onboard router each store a mapping table for data identifiers. The mapping table in the bearer network controller is as follows: Figure 8 As shown on the left, the data identifier serves as the index to the relation table, associated with the inputs to the hash operation: the satellite base station IPv6 address, the UPF IPv6 address, and the TEID. The mapping relation table in the router is as follows... Figure 8As shown on the right, the data identifier serves as an index to the relational table, associated with the bearer tunnel, and is used to guide different GTP message data into the corresponding bearer tunnel. At the same time, the data identifier is also associated with the IPv6 address of the satellite base station and the UPF.

[0114] In the embodiments of this specification, the spaceborne base station performs GTP tunnel header encapsulation on each service traffic data sent by the terminal device through the following steps: First, each received service traffic data is judged by calculating a hash value for each service packet based on the source and destination IPv6 addresses and GTP tunnel identifier of the service packet encapsulated with the GTP tunnel header. Then, this hash value is compared with the first SRv6 instruction generated by the spaceborne router. If the comparison result is consistent, it means that the traffic data corresponding to the service packet is the service traffic data that needs to be identified. At this time, the spaceborne base station embeds the first SRv6 instruction sent by the spaceborne router into the service packet. Specifically, the first SRv6 instruction is used as the destination IPv6 address, replacing the original UPF IPv6 address, to obtain the first GTP packet data containing the first SRv6 instruction.

[0115] In the embodiments of this specification, refer to Figure 9 As shown, after receiving the first GTP message data sent by the satellite-borne base station, the satellite-borne router 1 encapsulates the first GTP message data, including:

[0116] S201: Determine whether the destination IPv6 address of the first GTP message data is the same as the first SRv6 instruction;

[0117] S202: If so, change the destination IPv6 address of the first GTP message data to the UPF IPv6 address corresponding to the first SRv6 instruction;

[0118] S203: Perform bearer tunnel encapsulation on the first GTP message data, and encapsulate the first SRv6 instruction into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated first bearer data.

[0119] Understandably, after receiving the first GTP packet data sent by the satellite-based base station, the satellite-based router first checks the destination IPv6 address of each GTP packet. If it matches the first SRv6 instruction, it looks up the corresponding UPF IPv6 address in the mapping table pre-stored by the satellite-based router based on the data identifier (i.e., the first SRv6 instruction), modifies the destination IPv6 address of the first GTP packet data to the UPF IPv6 address, and encapsulates the first SRv6 instruction into the outer IPv6 header extension header of the bearer tunnel when encapsulating the bearer tunnel header, thus obtaining the encapsulated first bearer data. Its data packet format is as follows: Figure 10As shown.

[0120] This specification provides another method for fine-grained identification of satellite network traffic data, which can be applied to border routers in the aforementioned satellite internet architecture. (Refer to...) Figure 11 As shown, in some embodiments of this specification, the method includes the following steps:

[0121] S301: Receive the second traffic parameter to be identified from the bearer network controller;

[0122] S302: Generate a second data identifier based on the second traffic parameter to be identified, and send the second data identifier as a second SRv6 instruction to the second device;

[0123] S303: Receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0124] S304: Encapsulate the second GTP message data to obtain second bearer data containing the second SRv6 instruction;

[0125] S305: Forward the second bearer data to the router node of the corresponding bearer tunnel so that the router node can perform corresponding operations according to the second SRv6 instruction.

[0126] The embodiments in this specification convert the traffic parameters issued by the bearer network controller into SRv6 instructions and embed them into the bearer data of GTP messages. This enables the border router to overcome the limitation of existing technologies that can only identify the GTP tunnel layer, and achieve fine-grained identification of GTP internal data. This allows subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving the utilization rate of satellite network resources and the quality of service transmission.

[0127] It should be noted that when the method is applied to a border router, corresponding to the uplink transmission scenario in traffic data transmission, the second device in step S302 is a UPF. Figure 12 A flowchart for fine-grained data identification of satellite process data in uplink transmission scenarios, such as... Figure 12As shown, after deploying and configuring the GTP tunnel traffic data identification function on the border router through the bearer network controller, the second traffic parameter to be identified is sent to the border router, namely the IPv6 address of the satellite base station (128 bits) and the GTP tunnel identifier (32 bits). The border router uses a hash function to perform hash calculation based on the IPv6 address of the satellite base station, the GTP tunnel identifier, and the UPF IPv6 address that its route can reach, to obtain the 128-bit second data identifier, and sends it to the UPF as the second SRv6 instruction. The UPF will encapsulate each service traffic data sent by the external data network with a GTP tunnel header according to the received second SRv6 instruction, and send the encapsulated second GTP packet data to the border router. In this embodiment, the second GTP packet data is a service packet obtained by encapsulating service traffic data sent by the data network with a GTP tunnel header. The service packet includes source and destination IPv6 addresses and a GTP tunnel identifier. These addresses and identifier are used to generate a hash value for each service packet. The hash value is compared with the second SRv6 instruction. If the comparison is successful, the second SRv6 instruction is embedded into the service packet, resulting in second GTP packet data containing the second SRv6 instruction. The destination IPv6 address of the second GTP packet data containing the second SRv6 instruction is the second SRv6 instruction itself. After receiving the second GTP packet data, the border router encapsulates a bearer tunnel header around the second GTP packet data and adds the second SRv6 instruction to the extended IPv6 header of the bearer tunnel, resulting in second bearer data containing the second SRv6 instruction. The border router then routes the encapsulated second bearer data to the corresponding bearer tunnel according to a pre-stored mapping table and forwards it to the remaining router nodes within the bearer tunnel. After receiving the traffic data in the bearer tunnel, satellite router 1 performs corresponding operations based on the data identifier filled in the IPv6 header extension of the bearer tunnel, such as traffic statistics, ACL rule matching, policy routing, and load balancing. When the bearer data reaches satellite router 2, the tail node in the bearer tunnel, satellite router 2 strips the bearer tunnel header and the extension header containing the data identifier, obtaining a traffic data packet containing only the GTP tunnel header, and forwards the stripped GTP tunnel traffic data to the corresponding satellite base station. In this way, the satellite router does not need to identify the service traffic; it only needs to strip the bearer tunnel header to delete the second data identifier.

[0128] It should be noted that, in the embodiments of this specification, the second SRv6 instruction is only disseminated between the border router and the UPF.

[0129] In some embodiments of this specification, the border router similarly stores a mapping table of data identifiers. The data identifiers serve as indexes to the table, are associated with bearer tunnels, and are used to guide different GTP packet data into the corresponding bearer tunnels. At the same time, the data identifiers are also associated with the IPv6 addresses of the satellite base station and the UPF.

[0130] In the embodiments described in this specification, the UPF performs GTP tunnel header encapsulation on each service traffic data sent by the external data network through the following steps: First, each received service traffic data is judged by calculating a hash value for each service packet based on the source and destination IPv6 addresses and GTP tunnel identifier of the service packet encapsulated with the GTP tunnel header. Then, this hash value is compared with the second SRv6 instruction generated by the satellite router. If the comparison result is consistent, it means that the traffic data corresponding to the service packet is the service traffic data that needs to be identified. At this time, the UPF will embed the second SRv6 instruction sent by the border router into the service packet. Specifically, the second SRv6 instruction is used as the destination IPv6 address, replacing the original satellite base station IPv6 address, to obtain the second GTP packet data containing the second SRv6 instruction.

[0131] In the embodiments described in this specification, after the border router receives the second GTP packet data sent by the UPF, it encapsulates the second GTP packet data, including:

[0132] Determine whether the destination IPv6 address of the second GTP message data is the same as the second SRv6 instruction;

[0133] If so, change the destination IP address of the second GTP message data to the UPF IPv6 address corresponding to the second SRv6 instruction;

[0134] The second GTP message data is encapsulated with a bearer tunnel, and the second SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated second bearer data.

[0135] Understandably, after receiving the second GTP packet data sent by the UPF, the border router first checks the destination IPv6 address of each GTP packet data. If it is the same as the second SRv6 instruction, it will look up the corresponding satellite base station IPv6 address from the mapping table pre-stored by the border router according to the data identifier (i.e., the second SRv6 instruction), modify the destination IPv6 address of the second GTP packet data to the satellite base station IPv6 address, and encapsulate the second SRv6 instruction into the outer IPv6 header extension header of the bearer tunnel when encapsulating the bearer tunnel header, thus obtaining the encapsulated second bearer data.

[0136] Figure 13 This is a schematic diagram of data encapsulation in an uplink transmission scenario, such as... Figure 13 As shown, the data transmitted between the UPF and the external data network (DN) is the raw service data without encapsulation. The data transmitted between the border router and the UPF is GTP message data with a GTP tunnel header encapsulated on the outer layer of the raw service data. The data transmitted between the border router and satellite router 1 is bearer data with a bearer tunnel header encapsulated on the outer layer of the GTP message data. The data transmitted between satellite router 1 and satellite base station is GTP message data with the bearer tunnel header stripped. The data transmitted between satellite base station and user terminal is the raw service data.

[0137] Based on the fine-grained identification method for satellite network traffic data applied to spaceborne routers described above, this specification also provides a corresponding fine-grained identification device for satellite network traffic data. The device may include a system (including a distributed system), software (application), module, component, server, client, etc., using the method described in this specification, combined with necessary hardware implementation. Based on the same innovative concept, the devices in one or more embodiments provided in this specification are as described in the following embodiments. Since the implementation schemes and methods for solving the problem are similar, the implementation of specific devices in this specification can refer to the implementation of the aforementioned method, and repeated details will not be repeated. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0138] Specifically, Figure 14 This is a schematic diagram of the module structure of one embodiment of a fine-grained identification device for satellite network traffic data provided in this specification. (Refer to...) Figure 14 As shown in the embodiments of this specification, a fine-grained identification device for satellite network traffic data is provided and applied to a satellite-borne router. The device includes:

[0139] The first receiving module 1401 is used to receive the first traffic parameter to be identified sent by the bearer network controller;

[0140] The first data identifier generation and transmission module 1402 is used to generate a first data identifier based on the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device.

[0141] The second receiving module 1403 is used to receive the first GTP message data fed back by the first device according to the first SRv6 instruction;

[0142] The first encapsulation module 1404 is used to encapsulate the first GTP message data to obtain first bearer data containing the first SRv6 instruction.

[0143] The first forwarding module 1405 is used to forward the first bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the first SRv6 instruction.

[0144] The beneficial effects obtained by the apparatus provided in the embodiments of this specification are consistent with the beneficial effects obtained by the methods described above, and will not be repeated here.

[0145] Based on the fine-grained identification method for satellite network traffic data applied to border routers described above, this specification also provides a corresponding fine-grained identification device for satellite network traffic data. (Refer to...) Figure 15 As shown in the embodiments of this specification, a fine-grained identification device for satellite network traffic data is provided and applied to a border router. The device includes:

[0146] The third receiving module 1501 is used to receive the second traffic parameter to be identified sent by the bearer network controller;

[0147] The second data identifier generation and transmission module 1502 is used to generate a second data identifier according to the second traffic parameter to be identified, and send the second data identifier as a second SRv6 instruction to the second device.

[0148] The fourth receiving module 1503 is used to receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0149] The second encapsulation module 1504 is used to encapsulate the second GTP message data to obtain second bearer data containing the second SRv6 instruction;

[0150] The second forwarding module 1505 is used to forward the second bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the second SRv6 instruction.

[0151] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0152] Figure 16 The diagram shown is a schematic representation of the network device according to an embodiment of this specification. Figure 16As shown, the network device 1600 may include a processor 1610 (e.g., a central processing unit CPU) and a memory 1620; the memory 1620 is coupled to the processor 1610. The memory 1620 can store various types of data; it also stores an information processing program 1630, and executes the program 1630 under the control of the processor 1610.

[0153] For example, processor 1610 can be configured to execute a program to implement the cell reselection method as described in the previous embodiment. For example, processor 1610 can be configured to control the transmission of configuration parameters for interference avoidance between NGSO satellites and geostationary orbit GEO satellites to the terminal via a system information block (SIB).

[0154] In addition, such as Figure 16 As shown, network device 1600 may also include: transceiver 1640 and antenna 1650, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1600 is not necessarily required to include... Figure 16 All components shown; in addition, network device 1600 may also include Figure 16 For components not shown, please refer to existing technologies.

[0155] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), computer-readable storage media, and computer program products according to some embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processor to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processor, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0156] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processor to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0157] These computer program instructions may also be loaded onto a computer or other programmable data processor, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0158] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0159] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0160] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by computer equipment. As defined in this specification, computer-readable media does not include transient media, such as modulated data signals and carrier waves.

[0161] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of computer program products implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0162] The embodiments described in this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processors connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0163] It should also be understood that, in the embodiments of this specification, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0164] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0165] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the embodiments of this specification. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0166] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A fine-grained identification method for satellite network traffic data, characterized in that, Applied to satellite-borne routers, the method includes: Receive the first traffic parameter to be identified from the bearer network controller. The first traffic parameter to be identified includes the UPFIPv6 address and the GTP tunnel identifier. Generate a first data identifier based on the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device. The generation of the first data identifier based on the first traffic parameter to be identified includes: obtaining the IPv6 address of the satellite base station directly connected to the satellite router; and performing hash calculation on the satellite base station IPv6 address, UPF IPv6 address and GTP tunnel identifier using a hash function to obtain the first data identifier. Receive the first GTP message data fed back by the first device according to the first SRv6 instruction; The first GTP message data is encapsulated to obtain first bearer data containing the first SRv6 instruction, wherein the destination IPv6 address of the first GTP message data containing the first SRv6 instruction is the first SRv6 instruction. The first bearer data is forwarded to the router node of the corresponding bearer tunnel so that the router node can perform corresponding operations according to the first SRv6 instruction.

2. The method according to claim 1, characterized in that, The first SRv6 instruction is transmitted between the onboard router and the first device.

3. The method according to claim 1, characterized in that, The encapsulation of the first GTP message data includes: Determine whether the destination IPv6 address of the first GTP message data is the same as the first SRv6 instruction; If so, change the destination IPv6 address of the first GTP message data to the UPF IPv6 address corresponding to the first SRv6 instruction; The first GTP message data is encapsulated with a bearer tunnel, and the first SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated first bearer data.

4. A fine-grained identification method for satellite network traffic data, characterized in that, Applied to a first device, the method includes: Receive the first SRv6 command sent by the satellite router; According to the first SRv6 instruction, each service traffic data sent by the terminal is encapsulated with a GTP tunnel header to obtain several first service packets encapsulated with GTP tunnel. The hash value of each first service packet is calculated based on the source and destination IPv6 addresses and GTP tunnel identifier of each first service packet. The hash value of each first service message is compared with the first SRv6 instruction; If the comparison matches, the first SRv6 instruction is embedded into the first service message to obtain the first GTP message data containing the first SRv6 instruction.

5. A fine-grained identification method for satellite network traffic data, characterized in that, Applied to border routers, the method includes: Receive the second traffic parameter to be identified from the bearer network controller. The second traffic parameter to be identified includes the IPv6 address of the satellite base station and the GTP tunnel identifier. A second data identifier is generated based on the second traffic parameter to be identified, and the second data identifier is sent to the second device as a second SRv6 instruction. Generating the second data identifier based on the second traffic parameter to be identified includes: obtaining the UPF IPv6 address that is routable to the border router; and performing hash calculation on the satellite base station IPv6 address, the UPF IPv6 address, and the GTP tunnel identifier using a hash function to obtain the second data identifier. Receive the second GTP message data fed back by the second device according to the second SRv6 instruction; The second GTP message data is encapsulated to obtain second bearer data containing the second SRv6 instruction, wherein the destination IPv6 address of the second GTP message data containing the second SRv6 instruction is the second SRv6 instruction. The second bearer data is forwarded to the router node of the corresponding bearer tunnel so that the router node can perform corresponding operations according to the second SRv6 instruction.

6. The method according to claim 5, characterized in that, The second SRv6 instruction is transmitted between the border router and the second device.

7. The method according to claim 5, characterized in that, The encapsulation of the second GTP message data includes: Determine whether the destination IPv6 address of the second GTP message data is the same as the second SRv6 instruction; If so, the destination IPv6 address of the second GTP message data is changed to the IPv6 address of the satellite base station corresponding to the second SRv6 instruction; The second GTP message data is encapsulated with a bearer tunnel, and the second SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated second bearer data.

8. A fine-grained identification method for satellite network traffic data, characterized in that, Applied to a second device, the method includes: Receive the second SRv6 command sent by the border router; According to the second SRv6 instruction, each service traffic data sent by the data network is encapsulated with a GTP tunnel header to obtain several second service packets encapsulated with GTP tunnel. The hash value of each second service packet is calculated based on the source and destination IPv6 addresses and GTP tunnel identifier of each second service packet. The hash value of each second service message is compared with the second SRv6 instruction; If the comparison matches, the second SRv6 instruction is embedded into the second service message to obtain the second GTP message data containing the second SRv6 instruction.

9. A fine-grained identification device for satellite network traffic data, characterized in that, The device, applied to a spaceborne router, includes: The first receiving module is used to receive the first traffic parameter to be identified sent by the bearer network controller. The first traffic parameter to be identified includes the UPF IPv6 address and the GTP tunnel identifier. The first data identifier generation and transmission module is used to generate a first data identifier based on the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device. The generation of the first data identifier based on the first traffic parameter to be identified includes: obtaining the IPv6 address of the satellite base station directly connected to the satellite router; and performing hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier using a hash function to obtain the first data identifier. The second receiving module is used to receive the first GTP message data fed back by the first device according to the first SRv6 instruction; The first encapsulation module is used to encapsulate the first GTP message data to obtain first bearer data containing the first SRv6 instruction, wherein the destination IPv6 address of the first GTP message data containing the first SRv6 instruction is the first SRv6 instruction. The first forwarding module is used to forward the first bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the first SRv6 instruction.

10. A fine-grained identification device for satellite network traffic data, characterized in that, The device, applied to a border router, includes: The third receiving module is used to receive the second traffic parameters to be identified sent by the bearer network controller. The second traffic parameters to be identified include the IPv6 address of the satellite base station and the GTP tunnel identifier. The second data identifier generation and transmission module is used to generate a second data identifier based on the second traffic parameter to be identified, and send the second data identifier as a second SRv6 instruction to the second device. The generation of the second data identifier based on the second traffic parameter to be identified includes: obtaining the UPF IPv6 address that is routable to the border router; and performing hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier using a hash function to obtain the second data identifier. The fourth receiving module is used to receive the second GTP message data fed back by the second device according to the second SRv6 instruction; The second encapsulation module is used to encapsulate the second GTP message data to obtain second bearer data containing the second SRv6 instruction, wherein the destination IPv6 address of the second GTP message data containing the second SRv6 instruction is the second SRv6 instruction. The second forwarding module is used to forward the second bearer data to the router node of the corresponding bearer tunnel, so that the router node can perform corresponding operations according to the second SRv6 instruction.

11. A network device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 3, 4, 5 to 7, or 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 3, 4, 5 to 7, or 8.

13. A computer program product, characterized in that, It includes at least one instruction or at least one program segment, said at least one instruction or said at least one program segment being loaded and executed by a processor to implement the method as claimed in any one of claims 1 to 3, 4, 5 to 7, or 8.

Images