Fine-grained identification method, device and equipment for satellite network traffic data

Abstract

The embodiment of the invention relates to the technical field of satellite communication, and provides a fine-grained identification method, device and equipment for satellite network flow data, the method is applied to a satellite-borne router, and the method comprises the following steps: receiving a first to-be-identified flow parameter issued by a bearer network controller; generating a first data identifier according to the first to-be-identified flow parameter, and sending the first data identifier as a first IPv6 segment routing SRv6 instruction to the 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; packaging the first GTP message data to obtain first bearing 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 operation according to the first SRv6 instruction. According to the embodiment of the invention, unique fine-grained identification can be carried out on the GTP tunnel flow data.

Description

Technical Field

[0001] The embodiments of 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 Art

[0002] In satellite networks, fine-grained identification of traffic data can ensure that the network can efficiently and accurately process and transmit different types of traffic, providing differentiated service quality. However, existing traffic identification methods have the problem of coarse marking granularity in the 5G satellite network service transmission scenario. Specifically, the onboard base station will first encapsulate the user data with a GPRS Tunneling Protocol (GTP) header, and then transmit the data to the onboard router for forwarding. The onboard router's identification granularity for traffic data is only at the bearer tunnel data level, and it is unable to perform fine-grained identification on the data encapsulated within the GTP. 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. Summary of the Invention

[0003] In response to the above-mentioned problems in the prior art, the purpose of the embodiments of this specification is to provide a method, device and equipment for fine-grained identification of satellite network traffic data to solve the problems of coarse granularity and insufficient characterization capability of satellite network data identification in the prior art.

[0004] In order to solve the above technical problems, the specific technical solutions of the embodiments of this specification are as follows:

[0005] On the one hand, an embodiment of this specification provides a fine-grained identification method for satellite network traffic data, which is applied to an onboard router. The method includes:

[0006] receiving a first traffic parameter to be identified issued by a bearer network controller;

[0007] Generate a first data identifier according to the first traffic parameter to be identified, and send the first data identifier as a first IPv6 segment routing SRv6 instruction to the first device;

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

[0009] Encapsulating the first GTP message data to obtain first bearer data including the first SRv6 instruction;

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

[0011] Furthermore, the first traffic parameters to be identified include a UPF IPv6 address and a GTP tunnel identifier.

[0012] Furthermore, generating a first data identifier according to the first traffic parameter to be identified includes:

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

[0014] A hash function is used to perform hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier to obtain a first data identifier.

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

[0016] Furthermore, the first GTP message data is a business message obtained by performing GTP tunnel header encapsulation based on the business traffic data sent by the terminal, and the business message 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 business message, and the hash value is used to be compared with the first SRv6 instruction. When the comparison result is consistent, the first SRv6 instruction is embedded in the business message to obtain the first GTP message data containing the first SRv6 instruction.

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

[0018] Furthermore, encapsulating the first GTP message data includes:

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

[0020] If yes, changing 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 in a bearer tunnel, and the first SRv6 instruction is encapsulated into an outer IPv6 header extension header of the bearer tunnel to obtain encapsulated first bearer data.

[0022] In another aspect, an embodiment of this specification further provides a fine-grained identification method for satellite network traffic data, which is applied to a border router, and the method includes:

[0023] receiving a second traffic parameter to be identified issued by the bearer network controller;

[0024] 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;

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

[0026] Encapsulating the second GTP message data to obtain second bearer data including the second SRv6 instruction;

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

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

[0029] Furthermore, generating a second data identifier according to the second traffic parameter to be identified includes:

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

[0031] A hash function is used to perform hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier to obtain a second data identifier.

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

[0033] Furthermore, the second GTP message data is a service message obtained by performing GTP tunnel header encapsulation on the service traffic data sent by the data network, and the service message 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 message, and the hash value is used to be compared with the second SRv6 instruction. When the comparison result is consistent, the second SRv6 instruction is embedded in the service message to obtain the second GTP message data containing the second SRv6 instruction.

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

[0035] Furthermore, encapsulating the second GTP message data includes:

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

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

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

[0039] In another aspect, an embodiment of the present specification further provides a fine-grained identification device for satellite network traffic data, which is applied to a satellite-borne router, and the device includes:

[0040] A first receiving module, configured to receive a first traffic parameter to be identified issued by the bearer network controller;

[0041] A first data identifier generating and sending module, configured to generate a first data identifier according to the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device;

[0042] A second receiving module, configured to receive first GTP message data fed back by the first device according to the first SRv6 instruction;

[0043] A first encapsulation module is configured to encapsulate the first GTP message data to obtain first bearer data including the first SRv6 instruction;

[0044] The first forwarding module is configured to forward 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.

[0045] In another aspect, an embodiment of the present specification further provides a fine-grained identification device for satellite network traffic data, which is applied to a border router, and includes:

[0046] A third receiving module is configured to receive a second traffic parameter to be identified issued by the bearer network controller;

[0047] A second data identifier generating and sending module, configured 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;

[0048] A fourth receiving module, configured to receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0049] A second encapsulation module is configured to encapsulate the second GTP message data to obtain second bearer data including the second SRv6 instruction;

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

[0051] On the other hand, an embodiment of this specification further provides a network device, comprising a memory, a processor, and a computer program stored in the memory, wherein when the computer program is run by the processor, the computer program executes instructions of any one of the above methods.

[0052] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor of a computer device, executes instructions of any one of the above methods.

[0053] On the other hand, the embodiments of this specification further provide a computer program product, which, when executed by a processor of a computer device, executes instructions of any one of the above methods.

[0054] It can be seen from the technical solutions provided in the above embodiments of this specification that, compared with the existing network data identification method, 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 the GTP message, so that the onboard router breaks through the limitation of the existing technology that can only identify the bearer tunnel level, and realizes fine-grained identification of GTP internal data, thereby guiding subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving satellite network resource utilization and service transmission quality.

[0055] The above description is only an overview of the technical solutions of some embodiments of this specification. In order to more clearly understand the technical means of some embodiments of this specification, they can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiments of this specification more obvious and easy to understand, the following specifically cites preferred embodiments and provides detailed descriptions in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0057] Figure 1 A schematic diagram of a 5G satellite Internet architecture in some embodiments of this specification is shown;

[0058] Figure 2 A schematic diagram of a data encapsulation process for a satellite network in some embodiments of this specification is shown;

[0059] Figure 3 A schematic diagram showing the steps of a fine-grained identification method for satellite network traffic data applied to onboard routers in some embodiments of this specification is shown;

[0060] Figure 4 A diagram showing a satellite network topology structure in a downlink transmission scenario in some embodiments of this specification is shown;

[0061] Figure 5 A flowchart of fine-grained data identification of satellite process data in a downlink transmission scenario in some embodiments of this specification is shown;

[0062] Figure 6 A schematic diagram of data encapsulation for fine-grained data identification of satellite process data in a downlink transmission scenario in some embodiments of this specification is shown;

[0063] Figure 7 A schematic diagram of hash mapping in some embodiments of this specification is shown;

[0064] Figure 8 The figure shows a schematic representation of the mapping relationship between the bearer network controller and the onboard router in some embodiments of this specification;

[0065] Figure 9 A schematic diagram showing the steps of encapsulating the first GTP message data in some embodiments of this specification is shown;

[0066] Figure 10 A schematic diagram of the format of a data message carrying first data after encapsulation in some embodiments of this specification is shown;

[0067] Figure 11 A schematic diagram showing the steps of a fine-grained identification method for satellite network traffic data applied to a border router in some embodiments of this specification is shown;

[0068] Figure 12A diagram showing a satellite network topology structure in an uplink transmission scenario in some embodiments of this specification is shown;

[0069] Figure 13 A flowchart of fine-grained data identification of satellite process data in an uplink transmission scenario in some embodiments of this specification is shown;

[0070] Figure 14 A schematic diagram of the structure of a fine-grained identification device for satellite network traffic data applied to a satellite-borne router in some embodiments of this specification is shown;

[0071] Figure 15 A schematic diagram of the structure of a fine-grained identification device for satellite network traffic data applied to a border router in some embodiments of this specification is shown;

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

[0073] Description of the accompanying symbols:

[0074] 1401, first receiving module;

[0075] 1402, first data identifier generating and sending module;

[0076] 1403, second receiving module;

[0077] 1404, first packaging module;

[0078] 1405, first forwarding module;

[0079] 1501, third receiving module;

[0080] 1502, second data identifier generating and sending module;

[0081] 1503, fourth receiving module;

[0082] 1504, second packaging module;

[0083] 1505, second forwarding module;

[0084] 1600, network equipment;

[0085] 1610, processor;

[0086] 1620, memory;

[0087] 1630, procedure;

[0088] 1640, transceiver;

[0089] 1650. Antenna. DETAILED DESCRIPTION

[0090] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making any creative efforts 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, storage, and display, 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 comply with relevant regulations.

[0092] In the description of this application, unless otherwise specified, "and / or" is a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In addition, in the description of this disclosure, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions refers 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 mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0093] It should be noted that the terms "first," "second," and the like in this specification, the claims, and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or device comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products, or devices.

[0094] This specification provides method operation steps as described in the embodiments or flowcharts, but more or fewer operation steps may be included based on routine or non-creative work. The order of steps listed in the embodiments is only one way of executing the steps among many orderings and does not represent the only execution order. When a system or device product is actually executed, the method can be executed in the order shown in the embodiments or the drawings or in parallel.

[0095] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0096] In an embodiment of the present application, communication between devices in a communication system may be performed according to a communication protocol of any stage, for example, 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), etc., and / or other communication protocols currently known or to be developed in the future.

[0097] The satellite Internet architecture of the 5G system is as follows Figure 1 As shown in the figure, the satellite network mainly consists of three parts: access network, bearer network and core network. The satellite base station of the access network is deployed on the satellite and connected to the access mobile function module (AMF) of the core network through the N2 interface for transmitting control plane signaling. At the same time, the satellite base station is connected to the user plane function module (UPF) of the core network through the N3 interface. The UPF is deployed on the ground and is responsible for forwarding the user plane data transmitted by the satellite base station to external data networks, such as data centers, the Internet, etc. Figure 1 As shown in the figure, the bearer network is located between the access network's satellite base station and the UPF of the core network. It is responsible for encapsulating the access network data 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 service quality of the business data.

[0098] The current data packaging process of satellite networks is as follows: Figure 2As shown in the figure, after receiving user data, the satellite base station introduces it into the GTP tunnel and encapsulates the user plane GPRS Tunneling Protocol (GTP) message header outside the user data to customize the user's service data. When the user data encapsulated with the GTP message header reaches the satellite router of the bearer network, it is introduced into the bearer network tunnel and additionally encapsulated with the bearer tunnel header to guide data forwarding to the core network. The bearer tunnel header terminates at the previous hop network border router of the UPF, while the GTP tunnel header terminates at the UPF of the core network. It should be noted that the same bearer tunnel carries GTP tunnel data of different service types, and the same GTP tunnel carries multiple types of user data.

[0099] The current network traffic data identification principle primarily involves adding specific identification fields to the network or transport layer to distinguish different service flows. This is achieved through various field identification methods, including Differentiated Services Code Point (DSCP), Multiprotocol Label Switching Experimental (MPLS EXP), and IP Precedence. DSCP is a 6-bit field in IPv4 and IPv6 packets, marking different service levels by setting different DSCP values. MPLS EXP is a 3-bit field in the MPLS label. Traffic entering the MPLS domain is identified by a corresponding EXP value, and traffic is prioritized based on this EXP value. IP Precedence is a 3-bit field in the ToS field of the IPv4 packet header, used to prioritize data traffic and ensure the transmission of critical traffic. The above field identification method can only identify the outer message fields. In the 5G satellite network scenario, it cannot identify the source and destination IP addresses of the inner messages of the tunnel and perform fine-grained identification of data traffic. At the same time, it also 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 satellite router and the border router), the satellite router can only identify the bearer tunnel header and cannot identify the more granular GTP tunnel data. Consequently, the satellite 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] In order to solve the above problems, the embodiment of this specification provides a fine-grained identification method for satellite network traffic data, which can be applied to the satellite router in the above satellite Internet architecture. Figure 3As shown, in some embodiments of this specification, the method includes the following steps:

[0102] S101: Receive a first traffic parameter to be identified issued by a bearer network controller;

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

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

[0105] S103: Receive first General Packet Radio Service 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 including the first SRv6 instruction;

[0107] S105: Forward the first bearer data to a router node of a corresponding bearer tunnel, so that the onboard router node performs corresponding operations according to the first SRv6 instruction.

[0108] 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 the GTP message. This enables the onboard router to break through the limitation of the existing technology that can only identify the bearer tunnel level, and achieve fine-grained identification of GTP internal data, thereby guiding subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving satellite network resource utilization and service transmission quality.

[0109] It should be noted that when the method is applied to a satellite-borne router, corresponding to a downlink transmission scenario in traffic data transmission, the first device in step S102 is a satellite-borne base station. Figure 4 This is a satellite network topology diagram in the downlink transmission scenario, such as Figure 4 As shown in the figure, the satellite network topology includes multiple topologically connected onboard router nodes, with S1 representing one of the onboard router nodes. The curve represents the forwarding path for service traffic after user terminals access the network. The bearer network controller can configure and issue configurations to the onboard routers of the space bearer network, but cannot configure and manage the onboard base stations. In terms of topology, due to the dynamic nature of satellite networks, the space bearer network does not have the fixed service traffic access nodes found in terrestrial networks. In terms of the system, under the 5G NTN system, onboard routers cannot serve as service traffic access 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 The flowchart for fine-grained data identification of satellite traffic data in downlink transmission scenario is as follows: Figure 5 As shown, after the GTP tunnel traffic data identification function is deployed and configured to 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 the first SRv6 instruction to the satellite base station. The satellite base station will perform GTP tunnel header encapsulation on each service traffic data sent by the terminal device according to the received first SRv6 instruction, and send the encapsulated first GTP message data to the satellite router 1. In the embodiment of this specification, the first GTP message data is a service message obtained by performing GTP tunnel header encapsulation on the service traffic data sent by the terminal, and the service message includes the source and destination IPv6 address and the GTP tunnel identifier. The source and destination IPv6 address and the GTP tunnel identifier are used to generate a hash value for each service message, and 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 message to obtain the first GTP message data containing the first SRv6 instruction. The destination IP address of the first GTP message data containing the first SRv6 instruction is the first SRv6 instruction. After receiving the first GTP message data, onboard router 1 encapsulates the first GTP message data with a bearer tunnel header and adds the first SRv6 instruction to the bearer tunnel's outer IPv6 header extension, obtaining first bearer data containing the first SRv6 instruction. The onboard 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, onboard router 2 at a node in the bearer tunnel performs corresponding operations based on the data identifier filled in the bearer tunnel's outer IPv6 header extension, such as traffic statistics, ACL rule matching, policy routing, and load balancing. 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. The stripped GTP tunnel traffic data is then forwarded to the corresponding UPF. In this way, the border router does not need to identify the service traffic, and can delete the first data identifier by simply stripping off 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 original unencapsulated business data, the data transmitted between the satellite base station and the satellite router 1 is the GTP message data with the GTP tunnel header encapsulated in the outer layer of the original business data, the data transmitted between the satellite router 1 and the border router is the bearer data with the bearer tunnel header encapsulated in the outer layer of the GTP message data, the data transmitted between the border router and the UPF is the GTP message data with the bearer tunnel header stripped off, and the data transmitted between the UPF and the external data network (DN) is the original business data.

[0112] In the embodiment of this specification, the first traffic parameter to be identified includes the UPF IPv6 address (128 bits) and the GTP tunnel identifier (32 bits), wherein the GTP tunnel identifier is the TEID field in the GTP message. The specific mapping method for obtaining the first data identifier from the UPF IPv6 address, the TEID field in the GTP message, and the IPv6 address of the satellite base station directly connected thereto is as follows: Figure 7 As shown, a hash function is used to hash the satellite base station IPv6 address, the UPF IPv6 address, and the TEID (GTP tunnel identifier) ​​to generate a first data identifier, which is used as the first SRv6 instruction. Since the generated first data identifier consists of 128 bits, it can provide a globally unique identifier for any GTP message data flow 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 be noted that the data identifier and the SRv6 instruction are the same 128-bit binary string. The data identifier has the function of an SRv6 instruction, that is, it can instruct the routing device to complete the corresponding action. When identifying data, it is called a data identifier, and when instructing router behavior, it is called an SRv6 instruction. When the data identifier is used as an SRv6 instruction, the defined router action is: if the destination address of the received IP data packet is the SRv6 instruction and the payload part is GTP data, then the destination address of the IPv6 header is popped out and replaced with the IP address queried using the SRv6 instruction as the index, and the outer IPv6 header and extension header are encapsulated. After that, the data identifier is added to the extension header of the encapsulated IPv6 header.

[0113] In some embodiments of this specification, Figure 8 As shown in the figure, the bearer network controller and the satellite router will store a mapping table of data identifiers respectively. Figure 8 As shown on the left, the data identifier is the index of the relational table, which is associated with the input of the hash operation, namely the satellite base station IPv6 address, UPF IPv6 address and TEID. The mapping relation table in the router is as follows: Figure 8As shown on the right, the data identifier serves as the index of the relationship table and is associated with the bearer tunnel, which 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 UPF.

[0114] In the embodiment of this specification, the satellite base station performs GTP tunnel header encapsulation on each service flow data sent by the terminal device through the following steps: First, each received service flow data is judged in the following manner: based on the source and destination IPv6 addresses and GTP tunnel identifier of the service message encapsulated with the GTP tunnel header, a hash value of each service message is generated by hash calculation, and then this hash value is compared with the first SRv6 instruction generated by the satellite router. If the comparison result is consistent, it means that the flow data corresponding to the service message is the service flow data that needs to be identified. At this time, the satellite base station will embed the first SRv6 instruction sent by the satellite router in the service message. The specific embedding method is: using the first SRv6 instruction as the destination IPv6 address, replacing the original UPF IPv6 address, and obtaining the first GTP message 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 base station, the satellite 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 yes, 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 encapsulated first bearer data.

[0119] It can be understood that after the onboard router receives the first GTP message data sent by the onboard base station, it will first check the destination IPv6 address of each GTP message data. If it is the same as the first SRv6 instruction, it will search the corresponding UPF IPv6 address according to the data identifier (i.e., the first SRv6 instruction) from the mapping relationship table pre-stored by the onboard router, modify the destination IPv6 address of the first GTP message data to the UPF IPv6 address, and encapsulate the first SRv6 instruction into the outer IPv6 header extension header of the bearer tunnel when encapsulating the bearer tunnel header to obtain the encapsulated first bearer data. The data message format is as follows: Figure 10shown.

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

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

[0122] S302: 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;

[0123] S303: Receive 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 including the second SRv6 instruction;

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

[0126] 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 the GTP message, so that the border router can break through the limitation of the existing technology that can only identify the GTP tunnel level, and achieve fine-grained identification of GTP internal data, thereby guiding subsequent router nodes to perform differentiated scheduling, path optimization and other operations for different service types, thereby improving satellite network resource utilization and service transmission quality.

[0127] It should be noted that, when the method is applied to a border router, it corresponds to an uplink transmission scenario in traffic data transmission, and in this case, the second device in step S302 is a UPF. Figure 12 The flowchart for fine-grained data identification of satellite process data in the uplink transmission scenario is as follows: Figure 12As shown, after the GTP tunnel traffic data identification function is deployed and configured on the border router through the bearer network controller, the second traffic parameter to be identified, namely the satellite base station IPv6 address (128 bits) and the GTP tunnel identifier (32 bits), is sent to the border router. The border router uses a hash function to perform a hash calculation based on the satellite base station IPv6 address, the GTP tunnel identifier, and the routable UPF IPv6 address to obtain a 128-bit second data identifier, which is sent to the UPF as the second SRv6 instruction. Based on the received second SRv6 instruction, the UPF will encapsulate the GTP tunnel header for each service traffic data sent from the external data network and send the encapsulated second GTP message data to the border router. In an embodiment of this specification, the second GTP message data is a service message obtained by encapsulating the service traffic data sent by the data network in a GTP tunnel header. The service message includes a source and destination IPv6 address and a GTP tunnel identifier. The source and destination IPv6 address and GTP tunnel identifier are used to generate a hash value for each service message. The hash value is compared with the second SRv6 instruction. When the comparison result is consistent, the second SRv6 instruction is embedded in the service message to obtain second GTP message data containing the second SRv6 instruction. The destination IPv6 address of the second GTP message data containing the second SRv6 instruction is the second SRv6 instruction. After receiving the second GTP message data, the border router encapsulates the outer layer of the second GTP message data with a bearer tunnel header and adds the second SRv6 instruction to the outer IPv6 header extension header of the bearer tunnel to obtain second bearer data containing the second SRv6 instruction. The border router then directs 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 in the bearer tunnel. After receiving the bearer tunnel traffic data, onboard router 1 in the bearer tunnel performs corresponding operations based on the data identifier filled in the bearer tunnel's outer IPv6 header extension header, such as traffic statistics, ACL rule matching, policy routing, and load balancing. When the bearer data reaches the tail node onboard router 2 in the bearer tunnel, onboard router 2 strips off the bearer tunnel header and the extension header containing the data identifier, obtaining a traffic data packet containing only the GTP tunnel header. The stripped GTP tunnel traffic data is then forwarded to the corresponding onboard base station. In this way, the onboard router does not need to identify the service traffic; it only needs to strip off the bearer tunnel header to delete the second data identifier.

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

[0129] In some embodiments of this specification, similarly, the border router will store a mapping relationship table of data identifiers. The data identifier serves as an index of the relationship table and is associated with the bearer tunnel, which 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 UPF.

[0130] In the embodiment of this specification, the UPF performs GTP tunnel header encapsulation on each service flow data sent by the external data network through the following steps: First, each service flow data received is judged in the following manner: Based on the source and destination IPv6 addresses and GTP tunnel identifier of the service message encapsulated with the GTP tunnel header, a hash value of each service message is generated by hash calculation, and then this hash value is compared with the second SRv6 instruction generated by the onboard router. If the comparison result is consistent, it means that the flow data corresponding to the service message is the service flow data that needs to be identified. At this time, the UPF will embed the second SRv6 instruction sent by the border router in the service message. The specific embedding method is: the second SRv6 instruction is used as the destination IPv6 address to replace the original onboard base station IPv6 address, and the second GTP message data containing the second SRv6 instruction is obtained.

[0131] In the embodiment of this specification, after the border router receives the second GTP message data sent by the UPF, the border router encapsulates the second GTP message data, including:

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

[0133] If yes, 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 in a bearer tunnel, and the second SRv6 instruction is encapsulated into an outer IPv6 header extension header of the bearer tunnel to obtain encapsulated second bearer data.

[0135] It can be understood that after the border router receives the second GTP message data sent by the UPF, it will first check the destination IPv6 address of each GTP message data. If it is the same as the second SRv6 instruction, it will search the corresponding satellite base station IPv6 address according to the data identifier (i.e., the second SRv6 instruction) from the mapping relationship table pre-stored by the above-mentioned border router, and modify the destination IPv6 address of the second GTP message data to the satellite base station IPv6 address. When encapsulating the bearer tunnel header, the second SRv6 instruction is encapsulated into the outer IPv6 header extension header of the bearer tunnel to obtain the encapsulated second bearer data.

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

[0137] Based on the above-described method for fine-grained identification of satellite network traffic data applied to an onboard router, an embodiment of this specification also provides a corresponding device for fine-grained identification of satellite network traffic data. The device may include a system (including a distributed system), software (application), modules, components, server, client, etc. that utilizes the method described in the embodiments of this specification, combined with the necessary implementation hardware. Based on the same innovative concept, the device in one or more embodiments provided in the embodiments of this specification is described in the following embodiments. Because the implementation solutions to the problems solved by the devices are similar to the methods, the specific implementation of the devices in the embodiments of this specification can be referred to as the implementation of the aforementioned methods, and any repetitions will not be repeated. As used below, the terms "unit" or "module" may 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, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

[0138] Specifically, Figure 14 This is a module structure diagram of an embodiment of a fine-grained identification device for satellite network traffic data provided by an embodiment of this specification, with reference to Figure 14 As shown, an embodiment of this specification provides a fine-grained identification device for satellite network traffic data, which is applied to a satellite-borne router. The device includes:

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

[0140] A first data identifier generating and sending module 1402 is configured to generate a first data identifier according to 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 configured to receive the first GTP message data fed back by the first device according to the first SRv6 instruction;

[0142] A first encapsulation module 1404 is configured to encapsulate the first GTP message data to obtain first bearer data including the first SRv6 instruction;

[0143] The first forwarding module 1405 is configured to forward 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.

[0144] The beneficial effects achieved by the device provided in the embodiments of this specification are consistent with the beneficial effects achieved by the above-mentioned method and will not be repeated here.

[0145] Based on the above-mentioned fine-grained identification method for satellite network traffic data applied to a border router, the embodiment of this specification also provides a fine-grained identification device for satellite network traffic data. Figure 15 As shown, an embodiment of this specification provides a fine-grained identification device for satellite network traffic data, which is applied to a border router. The device includes:

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

[0147] A second data identifier generating and sending module 1502 is configured 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 configured to receive the second GTP message data fed back by the second device according to the second SRv6 instruction;

[0149] A second encapsulation module 1504 is configured to encapsulate the second GTP message data to obtain second bearer data including the second SRv6 instruction;

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

[0151] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0152] Figure 16 The diagram shows the structure of the network device according to the embodiment of this specification. Figure 16As shown, 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 may store various data; in addition, it may store an information processing program 1630, and the program 1630 may be executed under the control of the processor 1610.

[0153] For example, the processor 1610 may be configured to execute a program to implement the cell reselection method described in the previous embodiment. For example, the processor 1610 may be configured to perform the following control: sending the configuration parameters for the NGSO satellite to avoid interference with the geostationary orbit (GEO) satellite to the terminal via the system information block (SIB).

[0154] In addition, if Figure 16 As shown, the network device 1600 may also include: a transceiver 1640 and an antenna 1650, etc.; wherein, the functions of the above components are similar to those of the prior art and are not described here. It is worth noting that the network device 1600 does not necessarily have to include Figure 16 In addition, the network device 1600 may also include Figure 16 For components not shown, reference may be made to the prior art.

[0155] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), computer-readable storage media, and computer program products of some embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processor to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processor generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0156] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processor to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, the instruction device being implemented in the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

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

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

[0159] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

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

[0161] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware. Furthermore, the embodiments of this specification 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, CD-ROMs, optical storage, etc.) containing computer-usable program code.

[0162] Embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. Embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processors connected via a communications network. In distributed computing environments, program modules may be located 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 association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0164] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0165] In the description of this specification, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiments of this specification. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0166] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A fine-grained identification method for satellite network traffic data, characterized in that: Applied to a satellite-borne router, the method includes: receiving a first traffic parameter to be identified issued by a bearer network controller; Generate a first data identifier according to the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device; receiving first 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 including the first SRv6 instruction; The first bearer data is forwarded to a router node of a corresponding bearer tunnel, so that the router node performs corresponding operations according to the first SRv6 instruction.

2. The method according to claim 1, characterized in that The first traffic parameters to be identified include the UPF IPv6 address and the GTP tunnel identifier.

3. The method according to claim 2, characterized in that Generating a first data identifier according to the first traffic parameter to be identified includes: Obtaining the IPv6 address of the satellite base station directly connected to the satellite router; A hash function is used to perform hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier to obtain a first data identifier.

4. The method according to claim 1, wherein The first SRv6 instruction is transmitted between the onboard router and the first device.

5. The method according to claim 1, wherein The first GTP message data is a business message obtained by performing GTP tunnel header encapsulation based on the business traffic data sent by the terminal. The business message includes a source and destination IPv6 address and a GTP tunnel identifier. The source and destination IPv6 address and GTP tunnel identifier are used to generate a hash value for each business message. The hash value is used to be compared with the first SRv6 instruction. When the comparison result is consistent, the first SRv6 instruction is embedded in the business message to obtain the first GTP message data containing the first SRv6 instruction.

6. The method according to claim 4, characterized in that The destination IPv6 address of the first GTP message data including the first SRv6 instruction is the first SRv6 instruction.

7. The method according to claim 1, characterized in that The encapsulating the first GTP message data includes: Determining whether the destination IPv6 address of the first GTP message data is the same as the first SRv6 instruction; If yes, changing 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 in a bearer tunnel, and the first SRv6 instruction is encapsulated into an outer IPv6 header extension header of the bearer tunnel to obtain encapsulated first bearer data.

8. A fine-grained identification method for satellite network traffic data, characterized in that: Applied to a border router, the method includes: receiving a second traffic parameter to be identified issued by the bearer network controller; 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; receiving second GTP message data fed back by the second device according to the second SRv6 instruction; Encapsulating the second GTP message data to obtain second bearer data including the second SRv6 instruction; The second bearer data is forwarded to a router node of a corresponding bearer tunnel, so that the router node performs corresponding operations according to the second SRv6 instruction.

9. The method according to claim 8, characterized in that The second traffic parameter to be identified includes the satellite base station IPv6 address and the GTP tunnel identifier.

10. The method according to claim 9, characterized in that Generating a second data identifier according to the second traffic parameter to be identified includes: Obtaining a UPF IPv6 address that is routable to the border router; A hash function is used to perform hash calculation on the satellite base station IPv6 address, the UPF IPv6 address and the GTP tunnel identifier to obtain a second data identifier.

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

12. The method according to claim 8, characterized in that The second GTP message data is a service message obtained by performing GTP tunnel header encapsulation on the service traffic data sent by the data network. The service message includes a source and destination IPv6 address and a GTP tunnel identifier. The source and destination IPv6 address and the GTP tunnel identifier are used to generate a hash value for each service message. The hash value is used to be compared with the second SRv6 instruction. When the comparison result is consistent, the second SRv6 instruction is embedded in the service message to obtain the second GTP message data containing the second SRv6 instruction.

13. The method according to claim 12, characterized in that The destination IPv6 address of the second GTP message data including the second SRv6 instruction is the second SRv6 instruction.

14. The method according to claim 8, characterized in that The encapsulating the second GTP message data includes: Determining whether the destination IPv6 address of the second GTP message data is the same as the second SRv6 instruction; If so, changing the destination IPv6 address of the second GTP message data to the onboard base station IPv6 address corresponding to the second SRv6 instruction; The second GTP message data is encapsulated in a bearer tunnel, and the second SRv6 instruction is encapsulated into an outer IPv6 header extension header of the bearer tunnel to obtain encapsulated second bearer data.

15. A fine-grained identification device for satellite network traffic data, characterized in that: Applied to a satellite-borne router, the device comprises: A first receiving module, configured to receive a first traffic parameter to be identified issued by a bearer network controller; A first data identifier generating and sending module, configured to generate a first data identifier according to the first traffic parameter to be identified, and send the first data identifier as a first SRv6 instruction to the first device; A second receiving module, configured to receive first GTP message data fed back by the first device according to the first SRv6 instruction; A first encapsulation module is configured to encapsulate the first GTP message data to obtain first bearer data including the first SRv6 instruction; The first forwarding module is configured to forward 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.

16. A fine-grained identification device for satellite network traffic data, characterized in that: Applied to a border router, the device includes: A third receiving module is configured to receive a second traffic parameter to be identified issued by the bearer network controller; A second data identifier generating and sending module, configured 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; A fourth receiving module, configured to receive the second GTP message data fed back by the second device according to the second SRv6 instruction; A second encapsulation module is configured to encapsulate the second GTP message data to obtain second bearer data including the second SRv6 instruction; The second forwarding module is configured to forward the second bearer data to a router node of a corresponding bearer tunnel, so that the router node performs corresponding operations according to the second SRv6 instruction.

17. A network device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 7 or claims 8 to 14 is implemented.

18. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 or claims 8 to 14 is implemented.

19. A computer program product, characterized in that The method comprises at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded and executed by a processor to implement the method according to any one of claims 1 to 7 or claims 8 to 14.

Images