Method, device and system for obtaining traceability information

Abstract

The present application provides a method, device and system for obtaining traceability information, which can be applied to a communication system including a control plane CP and a user plane UP separated, the communication system including a CP device and a first UP device, the method including: in response to satisfying a first condition, the CP device sends a first billing message to the first device, the first billing message includes an identifier of the first UP device, the first billing message is related to a message corresponding to a first user transmitted by the first UP device, and the identifier of the first UP device is used to indicate that the traceability information of the first user is related to the first UP device. The method for obtaining traceability information provided by the present application can meet the demand for obtaining more traceability information.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a method, device and system for obtaining traceability information. Background Art

[0002] Tracing the source refers to finding the relevant network access information of the user who initiated the network incident. Tracing the source of the user who accessed the network can improve the accountability of network attack incidents, thereby creating a more secure and reliable network environment.

[0003] In a network architecture where the control plane (CP) and user plane (UP) are decoupled (i.e., a CU-separated network architecture), since the CP and UP are located on different hardware devices, or the CP and UP are located in different functional units on the same hardware device, the tracing device usually obtains relevant network access information by receiving the billing message sent by the CP. However, the information carried by the billing message is limited, and the tracing device cannot obtain more network access information related to the user, resulting in the inability to meet the demand for obtaining more tracing information for the user. Summary of the invention

[0004] The present application provides a method, device and system for obtaining traceability information, which can meet the demand for obtaining more user-related traceability information.

[0005] In a first aspect, a method for obtaining traceability information is provided, which can be applied to a communication system including a control plane CP and a user plane UP separated, the communication system including a CP device and a first UP device, the method including:

[0006] In response to satisfying the first condition, the CP device sends a first billing message to the first device, and the first billing message includes an identifier of the first UP device. The first billing message is related to a message corresponding to a first user transmitted by the first UP device, and the identifier of the first UP device is used to indicate that the traceability information of the first user is related to the first UP device.

[0007] In a CU-separated network architecture, network access information related to the user is stored on both the UP and the CP that manages the UP. The first device can obtain part of the network access information related to the user stored on the CP. Since the existing billing message does not include the identifier of the UP device, the first device cannot obtain part of the network access information related to the user stored on the UP device corresponding to the identifier of the UP device, thereby failing to meet the need for comprehensive tracing of the first user.

[0008] Based on the above technical solution, the first device can obtain more network access information related to the first user from the UP device corresponding to the identifier of the first UP device included in the first billing message, thereby meeting the need for comprehensive tracing of the first user.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, satisfying the first condition includes:

[0010] The CP device successfully migrates the message corresponding to the first user from the second UP device to the first UP device.

[0011] Based on the above technical solution, when the second UP device cannot meet the transmission requirements of the first user's message, the second device can notify the CP device to migrate the first user's message from the second UP device to the first UP device, thereby providing better network services for the first user.

[0012] In combination with the first aspect, in some implementations of the first aspect, the communication system also includes a second device, and satisfying the first condition includes: the CP device receives a first message sent by the second device, and the first message is used to instruct the CP device to send the first billing message.

[0013] Based on the above technical solution, the second device may trigger the CP device to send the first charging message to the first device.

[0014] In combination with the first aspect, in some implementations of the first aspect, the method further includes:

[0015] The CP device receives a second message sent by the second device, where the second message is used to instruct the CP device to migrate a message corresponding to the first user from the second UP device to the first UP device, and the first message is a response message of the CP device to successfully execute the migration.

[0016] In combination with the first aspect, in some implementations of the first aspect, before the CP device migrates the message of the first user from the second UP device to the first UP device, the method further includes:

[0017] The CP device sends a second charging message to the first device, where the second charging message includes an identifier of the second UP device, and the second charging message is related to the first user.

[0018] Based on the above technical solution, the CP device can obtain more network access information related to the first user stored on the second UP device according to the identifier of the second UP device included in the second billing message, wherein the more network access information related to the first user stored on the second UP device can be understood as the network access information generated by the first user before the first user accesses the network through the second UP device and the message corresponding to the first user is migrated from the second UP device to the first UP device.

[0019] In combination with the first aspect, in some implementations of the first aspect, satisfying the first condition includes: the CP device determines that a sending cycle for sending the charging message is satisfied.

[0020] Based on the above technical solution, when the CP device determines that the sending cycle for sending the billing message is met, the CP device itself can send the first billing message to the first device, and the second device does not need to send a message to the CP device to trigger the CP device to send the first billing message, thereby reducing the interaction process between the CP device and the second device.

[0021] In combination with the first aspect, in some implementations of the first aspect, the second device includes a control device or a user plane migration function USF device.

[0022] In a second aspect, a method for obtaining traceability information is provided, which is applied to a communication system including a control plane CP and a user plane UP separated, the communication system including a CP device, a first UP device, a second UP device, a first device and a second device, the method including:

[0023] The second device is used to generate a second message in response to the first message, the second message is used to instruct the CP device to send a first billing message to the first device, the first billing message includes an identifier of the first UP device, and the first message is used to instruct the CP device to successfully migrate a message corresponding to a first user corresponding to the first billing message from the second UP device to the first UP device;

[0024] The second device sends the second message to the CP device.

[0025] Based on the above technical solution, when the second device determines that the message corresponding to the first user is successfully migrated from the second UP device to the first UP device, the second device can immediately trigger the CP device to send a billing message (i.e., the first billing message) including the identifier of the migrated UP device (i.e., the identifier of the first UP device) to the first device. Therefore, the first device can obtain network access information related to the first user on the first UP device based on the identifier of the first UP device, thereby meeting the need for comprehensive tracing of the first user.

[0026] In combination with the second aspect, in some implementations of the second aspect, the second device includes a control device or a user plane migration function USF device.

[0027] In a third aspect, a method for obtaining traceability information is provided, which is applied to a communication system including a control plane CP and a user plane UP separated, the communication system including a CP device, a first UP device and a first device, the method including:

[0028] The first device receives a first charging message sent by the CP device, where the first charging message includes an identifier of the first UP device, and the first charging message is related to a message corresponding to the first user;

[0029] The first device obtains the traceability information from the first UP device according to the identifier of the first UP device.

[0030] Based on the above technical solution, the first device determines to obtain the tracing information from the first UP device according to the identifier of the first UP device included in the first billing message.

[0031] In combination with the third aspect, in some implementations of the third aspect, the first device obtains the traceability information from the first UP device according to the identifier of the first UP device, including:

[0032] The first device obtains network access information related to the first user from the first UP device according to the identifier of the first UP device.

[0033] Based on the above technical solution, the first device obtains more network access information related to the first user from the first UP device according to the identifier of the first UP device included in the first billing message, thereby meeting the demand for comprehensive tracing of the first user.

[0034] In combination with the third aspect, in certain implementations of the third aspect, the communication system also includes a second UP device, the first billing message is related to the first user, and the first billing message includes a billing message sent by the CP device after migrating the message corresponding to the first user from the second UP device to the first UP device.

[0035] In combination with the third aspect, in some implementations of the third aspect, the first charging message further includes an identifier of the first user.

[0036] Before the first device receives the first charging message sent by the CP device, the method further includes:

[0037] The first device receives a second charging message sent by the CP device, where the second charging message includes an identifier of the second UP device and an identifier of the first user;

[0038] Before the first device acquires the traceability information from the first UP device according to the identifier of the first UP device, the method further includes:

[0039] The first device determines, according to the identifier of the first UP device, the identifier of the second UP device, and the identifier of the first user, that a message corresponding to the first user is migrated from the second UP device to the first UP device.

[0040] Based on the above technical solution, after the first device determines that the message corresponding to the first user has been migrated from the second UP device to the first UP device, the first device can obtain more network access information related to the first user from the first UP device and the second UP device respectively according to the identifier of the first UP device and the identifier of the second UP device, thereby meeting the need for comprehensive tracing of the first user.

[0041] In combination with the third aspect, in some implementations of the third aspect, the first device includes a remote dial-in user server RADIUS.

[0042] In a fourth aspect, a control plane CP device is provided, the CP device is applied to a communication system including CP and user plane UP separation, the communication system also includes a first UP device, the CP device includes a processing unit and a transceiver unit,

[0043] The processing unit is used to determine that a first condition is satisfied;

[0044] The transceiver unit is used to send a first billing message to the first device in response to satisfying the first condition. The first billing message includes an identifier of the first UP device. The first billing message is related to a message corresponding to the first user transmitted by the first UP device. The identifier of the first UP device is used to indicate that the traceability information of the first user is related to the first UP device.

[0045] In combination with the fourth aspect, in some implementations of the fourth aspect, the communication system further includes a second UP device, and the processing unit is further used to:

[0046] The message corresponding to the first user is successfully migrated from the second UP device to the first UP device.

[0047] In combination with the fourth aspect, in some implementations of the fourth aspect, the communication system further includes a second device.

[0048] The transceiver unit is further used to receive a first message sent by the second device, where the first message is used to instruct the CP device to send the first charging message;

[0049] The processing unit is used to confirm receipt of the first message.

[0050] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further used for:

[0051] A second message sent by the second device is received, where the second message is used to instruct the CP device to migrate the message corresponding to the first user from the second UP device to the first UP device, and the first message is a response message of the CP device to successfully perform the migration.

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further used for:

[0053] A second charging message is sent to the first device, where the second charging message includes an identifier of the second UP device, and the second charging message is related to the first user.

[0054] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is further used to determine a sending cycle that satisfies the requirements for sending the billing message.

[0055] In a fifth aspect, a second device is provided, the second device being applied to a communication system including a control plane CP and a user plane UP separation, the communication system further including a CP device, a first UP device and a first device, the second device including a processing unit and a transceiver unit,

[0056] The processing unit is configured to generate a second message in response to the first message, the second message being used to instruct the CP device to send a first billing message to the first device, the first billing message including an identifier of the first UP device, and the first message being used to instruct the CP device to successfully migrate a message corresponding to a first user corresponding to the first billing message from the second UP device to the first UP device;

[0057] The transceiver unit is used to send the second message to the CP device.

[0058] In combination with the fifth aspect, in certain implementations of the fifth aspect, the second device includes a control device or a user plane migration function USF device.

[0059] In a sixth aspect, a first device is provided, the first device being applied to a communication system including a control plane CP and a user plane UP separated, the communication system further including a CP device and a first UP device, the first device including a transceiver unit and a processing unit,

[0060] The transceiver unit is configured to receive a first charging message sent by the CP device, where the first charging message includes an identifier of the first UP device, and the first charging message is related to a message corresponding to the first user;

[0061] The processing unit is used to obtain traceability information from the first UP device according to the identifier of the first UP device.

[0062] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the processing unit is further used to:

[0063] The network access information related to the first user is obtained from the first UP device according to the identifier of the first UP device.

[0064] In combination with the sixth aspect, in certain implementations of the sixth aspect, the communication system also includes a second UP device, the first billing message is related to the first user, and the first billing message includes a billing message sent by the CP device after migrating the message corresponding to the first user from the second UP device to the first UP device.

[0065] In combination with the sixth aspect, in some implementations of the sixth aspect, the first charging message further includes an identifier of the first user.

[0066] The transceiver unit is further configured to receive a second charging message sent by the CP device, where the second charging message includes an identifier of the second UP device and an identifier of the first user;

[0067] The processing unit is further configured to determine, based on the identifier of the first UP device, the identifier of the second UP device, and the identifier of the first user, that the first user migrates from the second UP device to the first UP device.

[0068] In combination with the sixth aspect, in some implementations of the sixth aspect, the first device includes a remote dial-in user server RADIUS.

[0069] In a seventh aspect, the present application provides a communication device, which has the function of implementing the method in the first aspect, the second aspect, or the third aspect and any possible implementation of the first aspect, the second aspect, or the third aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0070] In an eighth aspect, the present application provides a communication device, comprising at least one processor and a communication interface. The at least one processor is configured to execute a computer program or instruction so that the communication device can implement the communication method in the above-mentioned first aspect, second aspect, or third aspect and any possible implementation of the first aspect, second aspect, or third aspect.

[0071] Optionally, the communication device further comprises at least one memory, the at least one memory is coupled to the at least one processor, and the computer program or instruction is stored in the at least one memory.

[0072] In one implementation, the communication device is a CP device. When the communication device is a CP device, the communication interface may be a transceiver, or an input / output interface.

[0073] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0074] In another implementation, the communication device is a chip or a chip system configured in a CP device.

[0075] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0076] In a ninth aspect, the present application provides a communication device, comprising at least one processor and a communication interface. The at least one processor is configured to execute a computer program or instruction so that the communication device can implement the communication method in the first aspect, the second aspect, or the third aspect and any possible implementation of the first aspect, the second aspect, or the third aspect.

[0077] Optionally, the communication device further comprises at least one memory, the at least one memory is coupled to the at least one processor, and the computer program or instruction is stored in the at least one memory.

[0078] In one implementation, the communication device is a second device. When the communication device is a second device, the communication interface may be a transceiver, or an input / output interface.

[0079] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0080] In another implementation, the communication device is a chip or a chip system configured in the second device.

[0081] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0082] In a tenth aspect, the present application provides a communication device, comprising at least one processor and a communication interface. The at least one processor is used to execute a computer program or instruction so that the communication device can implement the communication method in the above-mentioned first aspect, second aspect or third aspect and any possible implementation of the first aspect, second aspect or third aspect.

[0083] Optionally, the communication device further comprises at least one memory, the at least one memory is coupled to the at least one processor, and the computer program or instruction is stored in the at least one memory.

[0084] In one implementation, the communication device is a first device. When the communication device is a first device, the communication interface may be a transceiver, or an input / output interface.

[0085] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0086] In another implementation, the communication device is a chip or a chip system configured in the first device.

[0087] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0088] In the eleventh aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method in the first aspect, the second aspect or the third aspect and any possible implementation of the first aspect, the second aspect or the third aspect.

[0089] In the twelfth aspect, a chip is provided, comprising at least one processor and an interface; the at least one processor is used to call and run a computer program so that the chip executes the method in the above-mentioned first aspect and any possible implementation of the above-mentioned first aspect.

[0090] In the thirteenth aspect, a communication system with separated control plane CP and user plane UP is provided, comprising the CP device as described in the fourth or eighth aspect, the second device as described in the fifth or ninth aspect, and the first device as described in the sixth or tenth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Figure 1 A schematic diagram of a system architecture 100 applicable to an embodiment of the present application is shown.

[0092] Figure 2A schematic flowchart of the traceability information acquisition method 100 provided in the present application is shown.

[0093] Figure 3 A schematic flowchart of the traceability information acquisition method 200 provided in the present application is shown.

[0094] Figure 4 A schematic diagram showing the format of the billing message provided in the present application.

[0095] Figure 5 A schematic flowchart of the traceability information acquisition method 300 provided in the present application is shown.

[0096] Figure 6 A schematic flowchart of the traceability information acquisition method 400 provided in the present application is shown.

[0097] Figure 7 A schematic flowchart of the traceability information acquisition method 600 provided in the present application is shown.

[0098] Figure 8 A schematic structural diagram of a CP device 800 provided in the present application is shown.

[0099] Fig. 9 A schematic structural diagram of a second device 900 provided in the present application is shown.

[0100] Fig.10 A schematic structural diagram of a first device 1000 provided in the present application is shown.

[0101] Fig.11 A schematic diagram of the structure of a network device 1100 provided in the present application is shown.

[0102] Fig.12 A schematic diagram of the structure of a network device 1200 provided in the present application is shown.

[0103] Fig.13 A schematic diagram of the structure of a network system 1300 provided by the present application is shown. DETAILED DESCRIPTION

[0104] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0105] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0106] In this application, the terms "first", "second", "third", etc. are used to distinguish between identical or similar items with substantially the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "third", and no limitation is imposed on the quantity and execution order.

[0107] The present application will present various aspects, embodiments or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.

[0108] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0109] In the embodiments of the present application, "corresponding (corresponding, relevant)" and "corresponding (corresponding)" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0110] In the embodiments of the present application, sometimes a subscript such as W1 may be mistakenly written as a non-subscript such as W1. When the difference is not emphasized, the meanings to be expressed are consistent.

[0111] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0112] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0113] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes 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. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "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, c can be single or multiple.

[0114] The following describes the related technologies of the embodiments of the present application:

[0115] In related technologies, such as home broadband access networks, BRAS devices usually send traceability information to authentication servers through billing messages. In one example, the traceability information includes: the public IP address of the device after NAT conversion, the starting port number after NAT conversion, or the ending port number after NAT conversion. However, these traceability information are not comprehensive enough in actual usage scenarios to meet the traceability requirements.

[0116] Especially in a network architecture with CU separation, since CP and UP are located on different hardware devices, or CP and UP are located in different functional units on the same hardware device, the tracing device usually obtains relevant network access information by receiving billing messages sent by CP. The tracing device cannot obtain more network access information related to the user, and thus cannot meet the demand for obtaining more tracing information about the user.

[0117] Especially in a special case, when the message corresponding to the user in the above network architecture is migrated from one UP to another UP, since the tracing device cannot know that the message corresponding to the user has undergone the above migration, the tracing device will not obtain the network access information related to the user from the migrated UP. In this case, it is not conducive to the tracing device to obtain the network access information of the user before and after the migration. This causes the problem of insufficient or unavailable tracing information. For example, the CU-separated network architecture includes CP, UP1 and UP2. When the user goes online normally, he accesses the network through UP2 (for example, Internet Protocol version 6 (IPv6)). When the message corresponding to the user is migrated from UP2 to UP1 according to the control of CP, the tracing device cannot know that the message corresponding to the user has undergone the above migration. In this case, the tracing device will not obtain the network access information related to the user from UP1.

[0118] The present application provides a method for obtaining traceability information, which can meet the demand for obtaining more user-related traceability information.

[0119] First, combine Figure 1 The system architecture applicable to the traceability information acquisition method provided in this application is specifically introduced.

[0120] Figure 1 A schematic diagram of a system architecture 100 applicable to an embodiment of the present application is shown.

[0121] like Figure 1 As shown, the system architecture 100 may include 9 parts, which may be represented as: residential gateway (RG) 110, access node (AN) 120, migration / adjustment function 130 (steering function, SF), controller 140, user plane migration function (user steering function, USF) device 150, authentication device 160, CP 170, UP 180 and provider edge router (provider edge, PE) 190. The above devices may be virtual devices or physical devices. At the same time, some devices may also be combined into one, such as USF device, remote authentication dial in user service (RADIUS) server, and CP device may be the same device. Figure 1 The dotted line in indicates that the devices can communicate with each other (eg, wireless communication or wired communication, etc.).

[0122] The following is a detailed introduction to the functions of each of the above parts.

[0123] 1. RG 110

[0124] RG110 is used to provide basic functions for user equipment to access the network.

[0125] For example, the RG 110 can be used to connect a user device (eg, a computer, a television, or a mobile phone) connected thereto to the network.

[0126] 2. AN 120

[0127] AN 120 is used to connect to the RG device, receive user data sent by the RG device, and transmit user data packets to SF 130.

[0128] In the embodiment of the present application, the device type of AN 120 is not specifically limited.

[0129] For example, AN 120 may be an optical line terminal (OLT). For example, AN 120 may also be an optical line terminal device (digital subscriber line access multiplexer, DSLAM). For example, AN 120 may also be a switch.

[0130] 3. SF 130

[0131] SF 130 is used to determine the access UP for user data when the user equipment is online. For example, SF 130 may access the message corresponding to the user equipment from UP 181 when the user equipment is online. For example, SF 130 may access the message corresponding to the user equipment from UP 182 when the user equipment is online. For example, SF 130 may access the message corresponding to the user equipment from UP 183 when the user equipment is online.

[0132] 4. Controller 140

[0133] The controller 140 is used to obtain the load status of UP devices in the network, such as UP 180 and / or CP 170. In addition, the controller 140 can also communicate with the SF 130. Specifically, when the controller 140 learns that the user equipment has migrated from the UP1 device (the UP device to which the user equipment is connected when it goes online) to the UP2 device, the controller 140 can notify the SF 130 that the user equipment has migrated to the UP2 device.

[0134] The present application does not specifically limit the controller 140. For example, the controller 140 may be a software defined network (SDN) controller.

[0135] 5. USF equipment 150

[0136] The USF device 150 is used to establish migration rules for user equipment UP. Specifically, the USF device 150 can determine which UP the user equipment needs to access from, or which UP to migrate from the currently accessed UP, based on information such as the network load obtained from the controller 140 or the user's service level agreement (SLA) obtained from the authentication device 160.

[0137] In the embodiment of the present application, there is no specific limitation on the deployment locations of the USF 150 and the controller 140 in the network.

[0138] In some embodiments, the USF 150 and the controller 140 may be deployed in the same physical or virtual entity in the network. For example, the USF 150 and the controller 140 may be deployed in the same functional unit of the same physical or virtual entity. Alternatively, the USF 150 and the controller 140 may also be deployed in different functional units of the same physical or virtual entity.

[0139] In other embodiments, the USF 150 and the controller 140 may also be deployed in different physical or virtual entities in the network.

[0140] 6. Authentication device 160

[0141] The authentication device is usually used to authenticate and authorize users to access the network. In the embodiment of the present application, the authentication device can also be a traceability device. For example, the authentication device 160 can receive a billing message related to the user sent by the CP 170, and obtain traceability information according to the billing message.

[0142] The present application does not specifically limit the authentication device 160. For example, the authentication device may be a RADIUS server.

[0143] 7. CP 170

[0144] CP 170 is a control device of UP, which is responsible for controlling functions related to UP. For example, CP 170 can be responsible for mobility management control and session management control. For example, when USF 150 determines that the user equipment needs to be migrated from UP2 to UP1 according to the information obtained from controller 140, CP 170 can send the relevant table items of the user equipment to UP1 and delete the relevant table items of the user equipment stored in UP1. For example, CP 170 can send the charging message of the user equipment to authentication device 160.

[0145] 8. UP 180

[0146] like Figure 1 As shown, in the system architecture 100, three UPs may be included, which may be marked as UP181, UP182 and UP183. UP 180 (eg, UP181, UP182 or UP183) is a user plane device of the network, which is used to receive the session of the user equipment from CP 170 and forward the data packet of the user equipment.

[0147] In the embodiment of the present application, UP 180 (eg, UP 181, UP 182 or UP 183) may be a physical device or a virtual device.

[0148] In the embodiment of the present application, the deployment location of the UP included in UP 180 in the network is not specifically limited.

[0149] In some embodiments, the UPs included in UP 180 may be respectively deployed in different or the same physical devices in the network. That is, UP 181, UP 182 and UP 183 are respectively deployed in different physical devices in the network.

[0150] It should be understood that Figure 1 This is only for illustration and does not constitute any limitation on the system architecture of the present application. For example, in some implementations, when the control device has the functions of USF 150, controller 140 and CP 170, it can be Figure 1 The USF 150, the controller 140, and the CP 170 in the control device are replaced with the control device. Specifically, the USF 150, the controller 140, and the CP 170 may be deployed in the same physical functional unit of the control device, or the USF 150, the controller 140, and the CP 170 may be deployed in different physical functional units of the control device. For example, in some implementations, a greater number (e.g., 4 UPs) or a smaller number (e.g., 2 UPs) of UPs may also be included.

[0151] Combine the following Figures 2 to 7 , specifically introduces the method for obtaining traceability information provided by this application.

[0152] Figure 2 FIG. 1 is a schematic flow chart of a method 100 for obtaining traceability information provided by the present application. Figure 2 As shown, method 100 may include step 110 and step 120. Step 110 and step 120 are described in detail below.

[0153] Step 110: In response to the first condition being met, the CP device sends a first charging message to the first device, where the first charging message includes an identifier of the first UP device.

[0154] The first billing message can be used to enable the first device to obtain traceability information according to the identifier of the first UP device, and the first billing message is related to the message corresponding to the first user transmitted by the first UP device. The identifier of the first UP device includes but is not limited to: the IP address of the first UP device, the media access control (MAC) address of the first UP device, the equipment serial number (ESN) of the first UP device, the equipment number of the first UP device or the equipment name of the first UP device, etc., which can identify the first UP device.

[0155] In the embodiments of the present application, when any one of the following conditions is met, the first condition can be considered to be met:

[0156] (1) The CP device receives message #2 sent by the second device, and message #2 is used to instruct the CP device to send a first charging message. In this case, it can be considered that the first condition is met; or,

[0157] (2) The CP device determines that the sending period of the charging message is met. In this case, it can be considered that the first condition is met; or

[0158] (3) The CP device determines that the message corresponding to the first user is migrated from the first UP device to the second UP device. In this case, the CP device can determine a migration strategy for the first user according to the network load and execute the migration strategy.

[0159] In an example, the message #2 sent by the second device is sent according to a corresponding configuration, such as when the first user successfully comes online.

[0160] In another example, the message #2 sent by the second device is generated after receiving the migration success message sent by the CP device. The migration success message is used to indicate that the CP device successfully migrated the message corresponding to the first user from the second UP device to the first UP device. In this example, before the CP device sends the first billing message to the first device, the following steps may also be included:

[0161] The CP device receives message #3 sent by the second device, where message #3 is used to instruct the CP device to migrate the message corresponding to the first user from the second UP device to the first UP device;

[0162] The CP device migrates the message corresponding to the first user from the second device to the first UP device according to the message #3.

[0163] The message corresponding to the first user can be transmitted to the CU-separated network architecture through a user device. The user device includes but is not limited to: a computer, a mobile phone, a handheld terminal, etc.

[0164] Optionally, before the CP device migrates the message corresponding to the first user from the second UP device to the first UP device, the following steps may also be included:

[0165] The CP device sends a second charging message to the first device, where the second charging message includes an identifier of the second UP device, and the second charging message is related to the first user.

[0166] In the embodiment of the present application, the first device may include a RADIUS server. The second device may include a control device, such as a controller or a USF device.

[0167] Step 120: The first device obtains traceability information from the first UP device according to the identifier of the first UP device.

[0168] The details of this step can be found below Figure 3 The detailed description of step 240 in the embodiment shown is not repeated here. It should be understood that Figure 2 The method for obtaining traceability information provided by the present application is introduced by taking the example that a first user accesses the network through a second UP device when going online, and after the first user accesses the network, a message corresponding to the first user is migrated from the second UP device to the first UP device. Figure 2 This is for illustration only and does not constitute any limitation to the present application. In some implementations, a greater number of UP devices associated with the CP device may be included. For example, the UP devices associated with the CP device are three UP devices, which may be represented as a first UP device, a second UP device, and a third UP device, respectively.

[0169] Now combine Figure 3 Taking "satisfying the first condition includes: the CP device determines that the sending cycle for sending the billing message is met" in method 100 as an example, the traceability information acquisition method 100 provided in this application is introduced in detail.

[0170] Figure 3 FIG. 2 shows a schematic flow chart of a method 200 for obtaining traceability information provided by the present application. Figure 3 As shown, the method 200 includes steps 210 to 240, and steps 210 to 240 are described in detail below.

[0171] Step 210: The second device sends a second message to the CP device: message #3.

[0172] In the embodiment of the present application, the second device may include a control device or a USF device. It should be understood that the second device may also be other devices with a control function or a migration function, and the present application does not specifically limit this. In the embodiment of the present application, message #3 is used to instruct the CP device to migrate the message corresponding to the first user from the second UP device to the first UP device.

[0173] Optionally, before step 210, the following steps may also be included:

[0174] The second device determines, based on the SLA information of the first user, that the first user can access the network through the second UP device, so that the first user accesses the network through the second UP device;

[0175] The second device may determine that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device according to the load of the network to which the second UP device is connected. For example, when the second device determines that the load of the second UP device is greater than or equal to the first threshold and the load of the first UP device is less than the first threshold, the second device may determine that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device. The first threshold may be set according to a specific application scenario.

[0176] It should be understood that the first UP device and the second UP device are UP devices managed by the CP device, and the identifier of the first UP device is different from the identifier of the second UP device. Among them, the identifier of the first UP device is used to indicate the first UP device. For example, the identifier of the first UP device may be the IP address of the first UP device. For example, the identifier of the first UP device may be the device number of the first UP device. For example, the identifier of the first UP device may be the device name of the first UP device, etc. This application does not specifically limit the identifier of the first UP device, as long as it is ensured that the identifier of the selected first UP device can be used to indicate the first UP device. The identifier of the second UP device is used to indicate the second UP device. For example, the identifier of the second UP device may be the IP address of the second UP device. For example, the identifier of the second UP device may be the device number of the second UP device. For example, the identifier of the second UP device may be the device name of the second UP device, etc. This application does not specifically limit the identifier of the second UP device, as long as it is ensured that the identifier of the selected second UP device can be used to indicate the second UP device.

[0177] The identifier of the first UP device is different from the identifier of the second UP device. It can be understood that the type of the identifier of the first UP device is the same as the type of the identifier of the second UP device, but the content corresponding to the type of the identifier of the first UP device is different from the content corresponding to the type of the identifier of the second UP device.

[0178] For example, the identifier of the first UP device is the device identifier of the first UP device, and the device identifier of the first UP device is 1025. The identifier of the second UP device is the device identifier of the second UP device, and the device identifier of the second UP device is 1020. In this case, it can be considered that the identifier of the first UP device is different from the identifier of the second UP device.

[0179] Step 220: The CP device migrates the message corresponding to the first user from the second UP device to the first UP device.

[0180] When the CP device has the same function as the control device, the CP device can determine, based on its own judgment, that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device. That is, the above step 210 is an optional step. After that, the CP device can also determine, based on message #3, that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device.

[0181] In the embodiment of the present application, the CP device migrates the message corresponding to the first user from the second UP device to the first UP device, which can be understood as the CP device sends the table item (or session) related to the first user to the first UP device, and the message related to the first user can be transmitted via the first UP device. The CP device can also delete the table item (or session) related to the first user stored on the second UP device. In this case, it can be considered that the CP device successfully migrates the message corresponding to the first user from the second UP device to the first UP device.

[0182] Step 230: When the CP device determines that the sending period of sending the billing message is satisfied, the CP device sends a first billing message to the first device, where the first billing message includes an identifier of the first UP device.

[0183] When the CP device determines that the sending cycle of sending the billing message is met, the CP device sends the first billing message to the first device. It can be understood that after the CP device successfully migrates the message corresponding to the first user from the second UP device to the first UP device and the sending cycle of sending the billing message is met, the CP device sends the first billing message to the first device.

[0184] Among them, the present application does not specifically limit the size of the sending period for sending the billing message. For example, the sending period for sending the billing message can be set according to the specific application scenario. Alternatively, the sending period for sending the billing message can be pre-configured. For example, the sending period for sending the billing message can be 10ms, 20ms, 3s, 5s, etc.

[0185] In an embodiment of the present application, the first billing message may include an identifier of the first UP device, and the first billing message is related to the message corresponding to the above-mentioned first user transmitted by the first UP device, that is, the first billing message may be obtained based on the message of the first user transmitted by the first UP device, and the identifier of the first UP device is used to indicate that the traceability information of the first user is related to the first UP device.

[0186] Optionally, the first charging message may further include an identifier of the first user. The identifier of the first user is used to identify the first user.

[0187] In the embodiment of the present application, the identifier of the first user is not specifically limited.

[0188] In some implementations, the identification of the first user may be an account number of the first user.

[0189] In some other implementations, the identifier of the first user may be an identifier of a terminal device used by the first user, wherein the identifier of the terminal device may be a MAC address of the terminal device and / or an IP address of the terminal device.

[0190] In some other implementations, the identifier of the first user may include the public network address of the first user and the public network port number of the first user. The public network port number of the first user is used to indicate the terminal device used with the first user. The terminal device used by the first user can access the network through the public network port number of the first user using the public network address of the first user. In one example, the public network address of the first user and the public network port number of the first user are generated by performing network address conversion on the private network IP address assigned to the first user according to the carrier-grade network address translation (CGN) technology. The CGN technology is an existing CGN technology, so it will not be described in detail here.

[0191] In the embodiment of the present application, the first device may include a RADIUS server.

[0192] See also Figure 4 , the following specifically introduces a schematic diagram of a billing message format provided by an embodiment of the present application. It should be understood that, Figure 4 This is for illustration only and does not constitute any limitation on the format of the billing message involved in the embodiments of the present application.

[0193] like Figure 4 As shown, the format of the accounting message may include 6 parts, namely: a code (Code) field, an authentication (Identifier) ​​field, a length (Length) field, a 16-byte long "0", an attribute (Attribute) field and a key (Key) field.

[0194] The Code field may be 1 byte long. The Code field is used to indicate the type of the charging message. Specifically, in the embodiment of the present application, Code=4 indicates that the message type is a charging request message.

[0195] The length of the Identifier field, the Length field, the 16-byte "0" and the Key field have the same specific meanings as those in the existing RADIUS protocol message structure and are not described in detail here.

[0196] The Attribute field includes the identifier of the UP device and optionally, the Attribute field may also include the user identifier.

[0197] For example, when Figure 4 When the billing message shown is the first billing message, the Attribute field includes the identifier of the first UP device and the identifier of the first user. Specifically, when the identifier of the first user includes the public network address of the first user and the public network port number of the first user, and the identifier of the first UP device is the device identifier of the first UP device, the Attribute field may include the following: the public network address of the first user, the public network port number of the first user, and the device identifier of the first UP device.

[0198] Optionally, before step 230, the following steps may also be included:

[0199] The first device receives a second charging message sent by the CP device, where the second charging message includes an identifier of the second UP device and an identifier of the first user.

[0200] Step 240: The first device obtains traceability information from the first UP device according to the identifier of the first UP device.

[0201] The first device can obtain network access information related to the first user from the first UP device and the second UP device according to the identifier of the first UP device and the identifier of the second UP device, respectively. Among them, the traceability information can be understood as information generated on the corresponding UP device and related to the first user. For example, the information can be a web page visited by the first user. The information can be network access log information corresponding to the first user, such as IP access records, access time, or related interfaces, forwarding time, boards, slot numbers, interface status and other information on the UP device for forwarding messages related to the user. It should be understood that the first device obtains the traceability information from the first UP device according to the identifier of the first UP device, including the first device directly obtaining it from the first UP device, and also including the first device providing the identifier of the first UP device to other devices, and the other devices perform the acquisition of the traceability information.

[0202] Before step 240, the following steps may also be included:

[0203] The first device determines, according to the identifier of the first UP device, the identifier of the second UP device, and the identifier of the first user, that a message corresponding to the first user is migrated from the second UP device to the first UP device.

[0204] Specifically, when the first device detects that the first billing message includes the identifier of the first user, the second billing message includes the identifier of the first user, and the identifier of the first UP device included in the first billing message and the identifier of the second UP device included in the second billing message are different, the first device can determine that the message corresponding to the first user is migrated from the second UP device to the first UP device.

[0205] As an example, taking the example that the first user's identifier includes the public network address #1 of the terminal device used by the first user and the public network port number of the terminal device used by the first user, it is introduced how the first device determines that the message corresponding to the first user is migrated from the second UP device to the first UP device.

[0206] The first device receives the second billing message sent by the CP device, including the public network address #1 of the terminal device used by the first user, the public network port number #2 of the terminal device used by the first user, and the identifier of the second UP device; and the first device receives the first billing message sent by the CP device, including the public network address #3 of the terminal device used by the first user, the public network port number #4 of the terminal device used by the first user, and the identifier of the second UP device. When the first device determines that the public network address #1 is the same as the public network address #3, the public network port number #2 is the same as the public network port number #4, and the identifier of the first UP device is different from the identifier of the second UP device, the first device can determine that the message corresponding to the first user is migrated from the second UP device to the first UP device.

[0207] It should be understood that Figure 3 This is for illustration only and does not constitute any limitation to the present application. In some implementations, a greater number of UP devices associated with the CP device may also be included. For example, the UP devices associated with the CP device are three UP devices, which may be represented as a first UP device, a second UP device, and a third UP device, respectively. In some implementations, the CP device may have the functions of the CP device in method 100 or method 200 and the functions of the second device in method 100 or method 200 at the same time. In this case, the CP device may determine the migration strategy for the message corresponding to the first user according to the network load and execute the migration strategy.

[0208] Combine the following Figure 5 Taking "satisfying the first condition includes: the CP device receives a first message sent by the second device" in method 100 as an example, the traceability information acquisition method 100 provided in this application is introduced in detail. Figure 5FIG. 3 is a schematic flow chart of a method 300 for obtaining traceability information provided by the present application. Figure 5 As shown, method 300 includes steps 310 to 360, and steps 310 to 360 are described in detail below.

[0209] Step 310: The second device sends message #3 to the CP device.

[0210] In an embodiment of the present application, the second device may include a control device or a user plane migration function USF device. It should be understood that the second device may also be other devices with a control function or a migration function, and the present application does not specifically limit this. In an embodiment of the present application, message #3 may be used to instruct the CP device to migrate the message corresponding to the first user from the second UP device to the first UP device.

[0211] Optionally, before step 310, the following steps may also be included:

[0212] The second device determines, based on the SLA information of the first user, that the first user can access the network through the second UP device, so that the first user accesses the network through the second UP device;

[0213] The second device may determine that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device according to the load of the network to which the second UP device is connected. For example, when the second device determines that the load of the second UP device is greater than or equal to the first threshold and the load of the first UP device is less than the first threshold, the second device may determine that the message corresponding to the first user needs to be migrated from the second UP device to the first UP device. The first threshold may be set according to a specific application scenario.

[0214] It should be understood that the first UP device and the second UP device are UP devices managed by the CP device, and the identifier of the first UP device is different from the identifier of the second UP device. Among them, the identifier of the first UP device is used to indicate the first UP device. For example, the identifier of the first UP device may be the IP address of the first UP device. For example, the identifier of the first UP device may be the device number of the first UP device. For example, the identifier of the first UP device may be the device name of the first UP device, etc. This application does not specifically limit the identifier of the first UP device, as long as it is ensured that the identifier of the selected first UP device can be used to indicate the first UP device. The identifier of the second UP device is used to indicate the second UP device. For example, the identifier of the second UP device may be the IP address of the second UP device. For example, the identifier of the second UP device may be the device number of the second UP device. For example, the identifier of the second UP device may be the device name of the second UP device, etc. This application does not specifically limit the identifier of the second UP device, as long as it is ensured that the identifier of the selected second UP device can be used to indicate the second UP device.

[0215] The identifier of the first UP device is different from the identifier of the second UP device. It can be understood that the type of the identifier of the first UP device is the same as the type of the identifier of the second UP device, but the content corresponding to the type of the identifier of the first UP device is different from the content corresponding to the type of the identifier of the second UP device.

[0216] For example, the identifier of the first UP device is the device identifier of the first UP device, and the device identifier of the first UP device is 1025. The identifier of the second UP device is the device identifier of the second UP device, and the device identifier of the second UP device is 1020. In this case, it can be considered that the identifier of the first UP device is different from the identifier of the second UP device.

[0217] Step 320: The CP device migrates the message corresponding to the first user from the second UP device to the first UP device.

[0218] Optionally, in some implementations, when the CP device has the same function as the control device, the CP device may determine, based on its own judgment, that it is necessary to migrate the message corresponding to the first user from the second UP device to the first UP device. That is, the above step 310 is an optional step. After this, the CP device may also determine, based on message #3, to migrate the message corresponding to the first user from the second UP device to the first UP device.

[0219] In the embodiment of the present application, the CP device migrates the message corresponding to the first user from the second UP device to the first UP device, which can be understood as the CP device sends the table item (or session) related to the first user to the first UP device, and the message related to the first user can be transmitted via the first UP device. The CP device can also delete the table item (or session) related to the first user stored on the second UP device. In this case, it can be considered that the CP device successfully migrates the message corresponding to the first user from the second UP device to the first UP device.

[0220] Step 330: The CP device sends a message #1 to the second device, where the message #1 is used to indicate that the message of the first user is successfully migrated from the second UP device to the first UP device.

[0221] Step 340: The second device sends message #2 to the CP device in response to message #1.

[0222] Message #2 is used to instruct the CP device to send a first charging message to the first device.

[0223] The first charging message includes an identifier of the first UP device, and the first charging message is related to the first user transmitted by the first UP device, that is, the first charging message may be obtained based on a message of the first user transmitted by the first UP device.

[0224] The second device sends message #2 to the CP device in response to message #1. It can be understood that when the second device receives message #1, the second device sends message #2 to the CP device.

[0225] Optionally, the first charging message may further include an identifier of the first user, wherein the identifier of the first user is used to identify the first user.

[0226] In the embodiment of the present application, the identifier of the first user is not specifically limited.

[0227] In some implementations, the identification of the first user may be an account number of the first user.

[0228] In some other implementations, the identifier of the first user may be an identifier of a terminal device used by the first user, wherein the identifier of the terminal device may be a MAC address of the terminal device and / or an IP address of the terminal device.

[0229] In some other implementations, the identifier of the first user may include the public network address of the first user and the public network port number of the first user. The public network port number of the first user is used to indicate a terminal device used by the first user. The terminal device used by the first user can access the network through the public network port number of the first user using the public network address of the first user. In one example, the public network address of the first user and the public network port number of the first user are generated by performing network address conversion on the private network IP address assigned to the first user according to the CGN technology, wherein the CGN technology is an existing CGN technology, so it will not be described in detail here.

[0230] Step 350: In response to message #2, the CP device sends a first charging message to the first device, where the first charging message includes an identifier of the first UP device.

[0231] Specifically, when the CP device determines that the received message is message #2, the CP device sends a first charging message to the first device.

[0232] In the embodiment of the present application, the first device may include a RADIUS server.

[0233] Step 360: The first device obtains traceability information from the first UP device according to the identifier of the first UP device.

[0234] Among them, the method of step 360 is the same as the method of step 240. For details, please refer to the content of step 240, which will not be repeated here.

[0235] It should be understood that the format of the first billing message and / or the format of the second billing message involved in steps 310 to 360 can refer to the format of the first billing message and / or the format of the second billing message in method 200. Figure 4The corresponding content will not be described in detail here.

[0236] It should be understood that Figure 5 This is for illustration only and does not constitute any limitation to the present application. In some implementations, a greater number of UP devices associated with the CP device may also be included. For example, the UP devices associated with the CP device are three UP devices, which may be represented as a first UP device, a second UP device, and a third UP device, respectively. In some implementations, the CP device may have the functions of the CP device in method 100, method 200, or method 300 and the functions of the second device in method 100, method 200, or method 300 at the same time. In this case, the CP device may determine the migration strategy for the message corresponding to the first user according to the network load and execute the migration strategy.

[0237] Combine the following Figure 6 and Figure 7 , introduces the traceability information acquisition method provided by this application and applies it to Figure 1 Two specific embodiments of the network structure are shown.

[0238] Figure 6 FIG. 4 is a schematic flow chart of a method 400 for obtaining traceability information provided by the present application. Figure 6 As shown, the method 400 includes steps 401 to 413, and steps 401 to 413 are introduced below.

[0239] First, combine Figure 1 and Figure 6 The following describes a device for executing the traceability information acquisition method provided in the embodiment of the present application. Figure 6 As shown, RG can be understood as Figure 1 RG 110 in. AN can be understood as Figure 1 AN 120 in. SF can be understood as Figure 1 UP2 can be understood as the second UP device in method 100, method 200 or method 300. UP1 can be understood as the first UP device in method 100, method 200 or method 300. For example, when UP2 is Figure 1 When UP 181 is selected, UP1 can be Figure 1 UP 182 or UP 183 in the method 100, the method 200 or the method 300. Specifically, the CP may be Figure 1 RADIUS can be understood as the first device in method 100, method 200 or method 300. Specifically, RADIUS can be Figure 1The control device may be understood as the second device in method 100, method 200 or method 300. Specifically, the control device may include Figure 1 The controller 140 and Figure 1 The USF device 150 in.

[0240] It should be understood that Figure 6 The SDN controller and USF device in the embodiment may be deployed in the same or different physical devices or virtual devices, which is not limited in the embodiments of the present application.

[0241] Step 401: User #1 (i.e., an example of the first user in the above method 100, method 200 or method 300) accessing the RG accesses the network through the UP2 device (i.e., an example of the second UP device in the above method 100, method 200 or method 300).

[0242] Among them, step 401 can be understood as the process of user #1 going online normally through the UP2 device, which is the same as the existing process of users going online.

[0243] As an example, when user #1 requests to go online, the RADIUS server can authenticate user #1's online request and obtain user #1's SLA information. The RADIUS server can send user #1's SLA information to the USF device. The USF device can determine to connect user #1 to the network through the UP2 device based on user #1's SLA information, that is, use the UP2 device as the device for transmitting the message corresponding to user #1.

[0244] Step 402: The CP device sends accounting message #2 (ie, an example of the second accounting message in the above method 100, method 200 or method 300) to the RADIUS server (ie, an example of the first device in the above method 100, method 200 or method 300).

[0245] Step 403: The SDN controller in the control device (ie, an example of the second device in the above method 100 or method 300) obtains the load of the UP2 device.

[0246] Step 404: The SDN controller in the control device obtains the load of the UP1 device (ie, an example of the first device in the above method 100, method 200 or method 300).

[0247] Step 405: The SDN controller in the control device obtains the load of the CP device.

[0248] It should be understood that the present application does not specifically limit the execution order of step 403 to step 405. For example, after step 402, step 405 may be executed first, then step 403, and finally step 404. Alternatively, after step 402, step 403 may be executed first, then step 405, and finally step 404.

[0249] Step 406: The SDN controller in the control device sends message #4 to the USF device in the control device.

[0250] Message #4 includes the network load of the network accessed by user #1. Specifically, the network load may include the load of the UP2 device obtained in step 403, the load of the UP1 obtained in step 403, and the load of the CP device obtained in step 405.

[0251] Step 407: The USF device in the control device determines that the message corresponding to user #1 is migrated from the UP2 device to the UP1 device.

[0252] Specifically, when the control device receives the message #4 in step 406, the control device may indeed need to migrate the message corresponding to user #1 from the UP2 device to the UP1 device.

[0253] Step 408: The USF device in the control device sends message #3 (ie, message #3 in the above method 100, method 200 or method 300) to the CP device. Message #3 is used to instruct the CP device to migrate the message corresponding to user #1 from the UP2 device to the UP1 device.

[0254] Step 409: The CP device sends the table entry related to user #1 to the UP1 device.

[0255] Specifically, when the CP device receives message #3, the CP device sends the table entry related to user #1 to the UP1 device.

[0256] Step 410: The CP device notifies the UP2 device to delete the entry related to user #1.

[0257] It should be understood that before step 410, the UP1 device also sends a user #1 entry delivery response to the CP device. The user #1 entry delivery response is used to indicate that the entry related to user #1 has been successfully delivered to the UP1 device, that is, the UP1 device stores the entry related to user #1.

[0258] The CP device notifies the UP2 device to delete the table entry related to user #1. It can be understood that after the CP device receives the response of sending the table entry of user #1 sent by the UP1 device, the CP device can notify the UP2 device to delete the table entry related to user #1.

[0259] It should be understood that after step 410 and before step 411, the UP2 device also sends a delete user #1 entry response to the CP device, and the delete user #1 entry response is used to indicate that the UP2 device has successfully deleted the entry related to user #1 from the UP2 device.

[0260] Step 411, the CP device sends message #1 (ie, message #1 in the above method 100, method 200 or method 300) to the USF device in the control device, where message #1 is used to instruct the CP device to successfully migrate the message corresponding to user #1 from the UP2 device to the UP1 device.

[0261] It should be understood that after the above steps 401 to 411, the message corresponding to the user #1 accessing the RG can be transmitted through the UP1 device.

[0262] Optionally, after step 411, the following steps may also be included:

[0263] The USF device in the control device sends message #1 to the SDN controller in the control device; and

[0264] The SDN controller in the control device sends message #1 to the SF.

[0265] Step 412: The USF device in the control device sends message #2 (ie, message #2 in the above method 100, method 200 or method 300) to the CP device in response to message #1.

[0266] Message #2 is used to instruct the CP device to send accounting message #1 (ie, an example of the first accounting message in the above method 100, method 200 or method 300) to the RADIUS server.

[0267] Step 413: The CP device sends an accounting message #1 to the RADIUS server in response to message #2.

[0268] For the contents not described in detail in the above steps 401 to 413 (for example, the identification of user #1, billing message #1 and billing message #2, etc.), please refer to the contents of method 300 and / or method 200 and / or method 100, and will not be repeated here.

[0269] Figure 7 FIG. 5 shows a schematic flow chart of a method 500 for obtaining traceability information provided by the present application. Figure 7 As shown, the method 500 includes steps 501 to 512, and steps 501 to 512 are introduced below.

[0270] First, combine Figure 1 and Figure 7 The following describes a device for executing the traceability information acquisition method of the present application. Figure 7 As shown, RG can be understood as Figure 1 RG 110 in. AN can be understood as Figure 1 AN 120 in. SF can be understood as Figure 1 UP2 can be understood as the second UP device in method 100 or method 200. UP1 can be understood as the first UP device in method 100 or method 200. For example, when UP2 is Figure 1 When UP181 is selected, UP1 can be Figure 1 UP 182 or UP 183 in the method 100 or the method 200. CP can be understood as the CP device in the method 100 or the method 200. Specifically, CP can be Figure 1 RADIUS can be understood as the first device in method 100, method 200 or method 300. Specifically, RADIUS can be Figure 1 The control device can be understood as the second device in method 100, method 200 or method 300. Specifically, the control device has Figure 1 The functions of the controller 140 and Figure 1 The function of the USF device 150.

[0271] Step 501: User #1 (i.e., an example of the first user in the above method 100, method 200 or method 300) accessing the RG accesses the network through the UP2 device (i.e., an example of the second UP device in the above method 100, method 200 or method 300).

[0272] Among them, step 501 can be understood as the process of user #1 going online normally through the UP2 device, which is the same as the existing process of users going online.

[0273] As an example, when user #1 requests to go online, RADIUS can authenticate user #1's online request and obtain user #1's SLA information. RADIUS can send user #1's SLA information to the control device, and the control device can determine to connect user #1 to the UP2 device based on user #1's SLA information, that is, use the UP2 device as the device for transmitting user #1's messages.

[0274] Step 502: The CP device sends accounting message #2 (ie, an example of the second accounting message in the above method 100, method 200 or method 300) to the RADIUS server (ie, an example of the first device in the above method 100, method 200 or method 300).

[0275] Step 503: The control device (ie, an example of the second device in the above method 100, method 200 or method 300) obtains the load of the UP2 device.

[0276] Step 504: The control device obtains the load of the UP1 device (ie, an example of the first UP device in the above method 100, method 200 or method 300).

[0277] Step 505: The control device obtains the load of the CP device.

[0278] It should be understood that the present application does not specifically limit the execution order of step 503 to step 505. For example, after step 502, step 505 may be executed first, then step 503, and finally step 504. Alternatively, after step 502, step 504 may be executed first, then step 505, and finally step 503.

[0279] Step 506: The control device determines that the message corresponding to user #1 needs to be migrated from the UP2 device to the UP1 device.

[0280] Specifically, the control device may determine that the message corresponding to user #1 needs to be migrated from the UP2 device to the UP1 device according to the network load of the network accessed by user #1. The network load may include the load of the UP2 device obtained in step 503, the load of the UP1 device obtained in step 504, and the load of the CP device obtained in step 505.

[0281] In the embodiment of the present application, the method by which the control device determines that the message corresponding to user #1 needs to be migrated from the UP2 device to the UP1 device is not specifically limited.

[0282] In some embodiments, when the control device determines that the load of the UP2 device is greater than or equal to the first threshold and the load of the UP1 device is less than the first threshold, the control device may determine that the message corresponding to the first user needs to be migrated from the UP2 device to the UP1 device. The first threshold may be set according to a specific application scenario.

[0283] Step 507: The control device sends message #3 (ie, message #3 in the above method 100, method 200 or method 300) to the CP device.

[0284] Among them, message #3 is used to instruct to migrate the message corresponding to user #1 from the UP2 device to the UP1 device.

[0285] Step 508: The CP device sends the entry of user #1 to the UP1 device.

[0286] Specifically, in response to message #3, the CP device sends a table entry related to user #1 to the UP1 device.

[0287] Step 509: The CP device sends a message to the UP2 device to delete the entry of user #1.

[0288] Step 510: The CP device sends message #1 (ie, message #1 in the above method 100, method 200 or method 300) to the control device.

[0289] Message #1 is used to instruct the CP device to successfully migrate the message corresponding to user #1 from the UP2 device to the UP1 device.

[0290] It can be understood that after step 510, the message corresponding to user #1 accessing the RG can be transmitted through the UP1 device.

[0291] Step 511: The control device sends message #2 (ie, message #2 in the above method 100, method 200 or method 300) to the CP device in response to message #1.

[0292] Message #2 is used to instruct the CP device to send an accounting message #1 (i.e., an example of the first accounting message in the above method 100, method 200, or method 300) to the RADIUS server. The accounting message #1 may include the identifier of the user #1 and the identifier of the UP1 device. Specifically, the identifier of the user #1 and the identifier of the UP1 device can refer to the contents of the method 100 and / or the method 200 and / or the method 300, which will not be described in detail here.

[0293] Step 512: The CP device sends an accounting message #1 to the RADIUS server in response to message #2.

[0294] For the contents not described in detail in the above steps 501 to 512 (for example, the identifier of user #1, the control device, the RADIUS server, the billing message #1 and the billing message #2, etc.), please refer to the contents of method 100 and / or method 200 and / or method 300, and will not be repeated here.

[0295] It should be understood that Figure 6 and Figure 7 This does not constitute any limitation on the method for obtaining traceability information provided in this application. Figure 6 and Figure 7 In the embodiment, two embodiments are specifically introduced in which the CP device sends the first billing message to the first device according to the second device triggering the CP device to send the first billing message to the first device. The specific embodiment in which the CP device sends the first billing message to the first device according to the sending cycle of the billing message is also applicable to the above Figure 6 or Figure 7 At this time, you can skip executing Figure 6Step 412 in the above example is replaced by step 413 in which the CP device determines that the period for sending the billing message is met and sends the billing message #1 to the RADIUS server. Alternatively, the above example may not be executed. Figure 7 Step 511 in the embodiment and step 512 is replaced by the CP device determining that the sending cycle of the accounting message is satisfied and sending the accounting message #1 to the RADIUS server.

[0296] Above. Combined Figures 1 to 7 The traceability information acquisition method provided by this application and the system architecture applicable to the method are introduced in detail. Figures 8 to 12 The hardware structure of the CP device, the second device, the first device, and the network device provided in this application is introduced in detail.

[0297] Figure 8 The schematic diagram of the structure of a CP device 800 provided in the present application is shown. The device 800 has any function of the CP device in the above method 100, method 200 or method 300, or has any function of the second device in the above method 100, method 200 or method 300. Figure 8 As shown, the CP device 800 includes: a processing unit 802, which is used to execute the steps related to determining that the first condition is met in the above-mentioned step 110, step 230 or step 350, step 220 or step 320, etc.; optionally, the CP device 800 also includes: a transceiver unit 801, which is used to execute the steps related to sending the first billing message in step 110, step 230 or step 350, step 330, etc.

[0298] The CP device 800 corresponds to the CP device in the above method embodiment, such as: the second device. The modules in the CP device 800 and the above other operations and / or functions are respectively for implementing the various steps and methods implemented by the CP device in the method embodiment. For specific details, please refer to the above method 100, method 200 or method 300. For the sake of brevity, they will not be repeated here.

[0299] When the CP device 800 obtains traceability information, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the CP device 800 is divided into different functional modules to complete all or part of the functions described above.

[0300] Fig. 9 The schematic diagram of the structure of a second device 900 provided in the present application is shown. The device 900 has any function of the second device in the above method 100, method 200 or method 300, or has any function of the CP device in the above method 100, method 200 or method 300. Fig. 9As shown, the second device 900 includes: a processing unit 902, used to execute the above-mentioned steps 130, 340 to determine the relevant steps in response to message #1, etc.; optionally, the second device 900 also includes: a transceiver unit 901, used to execute steps 140, 210, 310, 330, etc.

[0301] The second device 900 corresponds to the second device in the above method embodiment, such as: a CP device. The modules in the second device 900 and the above other operations and / or functions are respectively for implementing the various steps and methods implemented by the second device in the method embodiment. For specific details, please refer to the above method 100, method 200 or method 300. For the sake of brevity, they will not be repeated here.

[0302] When the second device 900 acquires traceability information, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the second device 900 is divided into different functional modules to complete all or part of the functions described above.

[0303] Fig.10 FIG. 1 is a schematic diagram showing the structure of a first device 1000 provided in the present application. The device 1000 has any function of the first device of the above-mentioned method 100, method 200 or method 300. Fig.10 As shown, the first device 1000 includes: a processing unit 1002, used to execute the above-mentioned step 120, step 240 or step 360, etc.; optionally, the first device 1000 also includes: a transceiver unit 1001, used to execute the first billing message sent in the receiving step 110, step 230 or step 350, etc.

[0304] The first device 1000 corresponds to the first device in the above method embodiment, such as: the modules in the first device 1000 and the above other operations and / or functions are respectively for implementing the various steps and methods implemented by the first device in the method embodiment. For specific details, please refer to the above method 100, method 200 or method 300. For the sake of brevity, they will not be repeated here.

[0305] When the first device 1000 acquires traceability information, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the first device 1000 is divided into different functional modules to complete all or part of the functions described above.

[0306] Corresponding to the method embodiment and virtual device embodiment provided in the present application, the embodiment of the present application further provides a network device, and the hardware structure of the network device is introduced below.

[0307] The network device 1100 or network device 1200 described below corresponds to the CP device, the second device or the first device in the above method embodiment. The hardware, modules and other operations and / or functions in the network device 1100 or the network device 1200 are respectively for implementing the various steps and methods implemented by the network device 1100 or the network device 1200 in the method embodiment. For the detailed process of how the network device 1100 or the network device 1200 obtains the traceability information based on the CP device, the first device and the second device, the specific details can be found in the above method embodiment. For the sake of brevity, it will not be repeated here. Among them, each step of the above method 100, method 200, method 300, method 400 or method 500 is completed by the hardware integrated logic circuit or software instruction in the processor of the network device 1100 or the network device 1200. The steps of the method disclosed in the embodiment of the present application can be directly reflected as the execution of the hardware processor, or the execution is completed by the combination of the hardware and software modules in the processor. The software module can be located in a random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register or other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0308] The network device 1100 or the network device 1200 corresponds to the CP device 800, the second device 900 or the first device 1000 in the above-mentioned virtual device embodiment, and each functional module in the CP device 800, the second device 900 or the first device 1000 is implemented by the software of the network device 1100 or the network device 1200. In other words, the functional modules included in the CP device 800, the second device 900 or the first device 1000 are generated after the processor of the network device 1100 or the network device 1200 reads the program code stored in the memory.

[0309] See also Fig.11 , Fig.11 The schematic diagram of the structure of a network device 1100 provided by the present application is shown. The network device 1100 can be configured as a CP device, a second device or a first device. The network device 1100 can be implemented by a general bus architecture.

[0310] The network device 1000 includes at least one processor 1101 , a communication bus 1102 , a memory 1103 , and at least one communication interface 1104 .

[0311] The processor 1101 may be a general-purpose CPU, NP, microprocessor, or may be one or more integrated circuits for implementing the solution of the present application, such as an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0312] The communication bus 1102 is used to transmit information between the above components. The communication bus 1102 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0313] The memory 1103 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1103 may exist independently and be connected to the processor 1101 via the communication bus 1102. The memory 1103 may also be integrated with the processor 1101.

[0314] The communication interface 1104 uses any transceiver-like device for communicating with other devices or communication networks. The communication interface 1104 includes a wired communication interface and may also include a wireless communication interface. Among them, the wired communication interface may be, for example, an Ethernet interface. The Ethernet interface may be an optical interface, an electrical interface, or a combination thereof. The wireless communication interface may be a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof, etc.

[0315] In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as Fig.11 CPU0 and CPU1 are shown in the figure.

[0316] In a specific implementation, as an embodiment, the network device 1000 may include multiple processors, such as Fig.11 1 and 1105. Each of these processors may be a single-CPU or a multi-CPU. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0317] In a specific implementation, as an embodiment, the network device 1000 may further include an output device 1106 and an input device 1107. The output device 1106 communicates with the processor 1101 and may display information in a variety of ways. For example, the output device 1106 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1107 communicates with the processor 1101 and may receive user input in a variety of ways. For example, the input device 1107 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0318] In some embodiments, the memory 1103 is used to store the program code 1110 for executing the solution of the present application, and the processor 1101 can execute the program code 1110 stored in the memory 1103. That is, the network device 1000 can implement the method 100, method 200, method 300, method 400 or method 500 provided in the method embodiment through the processor 1101 and the program code 1110 in the memory 1103.

[0319] The network device 1100 of the embodiment of the present application may correspond to the CP device, the second device or the first device in the above-mentioned various method embodiments, and the processor 1101, the communication interface 1104, etc. in the network device 1100 may implement the functions and / or various steps and methods implemented by the devices in the above-mentioned various method embodiments. For the sake of brevity, it will not be repeated here.

[0320] The transceiver unit 801 in the CP device 800 may be equivalent to the communication interface 1104 in the network device 1100 ; the processing unit 802 in the CP device 800 may be equivalent to the processor 1101 in the network device 1100 .

[0321] The transceiver unit 901 in the second device 900 may be equivalent to the communication interface 1104 in the network device 1100 ; the processing unit 902 in the second device 900 may be equivalent to the processor 1101 in the network device 1100 .

[0322] The transceiver unit 1001 in the first device 1000 may be equivalent to the communication interface 1104 in the network device 1100 ; the processing unit 1002 in the first device 1000 may be equivalent to the processor 1101 in the network device 1100 .

[0323] See also Fig.12 , Fig.12 The schematic diagram of the structure of a network device 1200 provided by the present application is shown. The network device 1200 can be configured as a CP device, a second device or a first device. The network device 1200 includes: a main control board 1210 and an interface board 1230 .

[0324] The main control board 1210 is also called a main processing unit (MPU) or a route processor card. The main control board 1210 is used to control and manage various components in the network device 1200, including routing calculation, device management, device maintenance, and protocol processing functions. The main control board 1210 includes: a central processing unit 1211 and a memory 1210.

[0325] The interface board 1230 is also called a line processing unit (LPU), a line card or a service board. The interface board 1230 is used to provide various service interfaces and realize the forwarding of data packets. The service interface includes but is not limited to an Ethernet interface, a POS (Packet over SONET / SDH) interface, etc., and the Ethernet interface is, for example, a Flexible Ethernet Clients (FlexE Clients) service interface. The interface board 1230 includes: a central processing unit 1231, a network processor 1232, a forwarding table entry memory 1234 and a physical interface card (PIC) 1233.

[0326] The central processor 1231 on the interface board 1230 is used to control and manage the interface board 1230 and communicate with the central processor 1211 on the main control board 1210 .

[0327] The network processor 1232 is used to implement the forwarding processing of the message. The network processor 1232 can be in the form of a forwarding chip. Specifically, the network processor 1232 is used to forward the received message based on the forwarding table stored in the forwarding table entry memory 1234. If the destination address of the message is the address of the network device 1200, the message is sent to the CPU (such as the central processor 1211) for processing; if the destination address of the message is not the address of the network device 1200, the next hop and the output interface corresponding to the destination address are found from the forwarding table according to the destination address, and the message is forwarded to the output interface corresponding to the destination address. Among them, the processing of the uplink message includes: processing of the message input interface, forwarding table search; processing of the downlink message: forwarding table search, etc.

[0328] The physical interface card 1233 is used to implement the physical layer docking function, whereby the original traffic enters the interface board 1230, and the processed message is sent out from the physical interface card 1233. The physical interface card 1233, also called a daughter card, can be installed on the interface board 1230, and is responsible for converting the photoelectric signal into a message and forwarding the message to the network processor 1232 for processing after performing a validity check on the message. In some embodiments, the central processor can also perform the functions of the network processor 1232, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1232 is not required in the physical interface card 1233.

[0329] Optionally, the network device 1200 includes multiple interface boards. For example, the network device 1200 further includes an interface board 1240 . The interface board 1240 includes: a central processor 1241 , a network processor 1242 , a forwarding table entry memory 1244 , and a physical interface card 1243 .

[0330] Optionally, the network device 1200 further includes a switching fabric board 1220. The switching fabric board 1220 may also be referred to as a switch fabric unit (SFU). When the network device has multiple interface boards 1230, the switching fabric board 1220 is used to complete data exchange between the interface boards. For example, the interface board 1230 and the interface board 1240 may communicate through the switching fabric board 1220.

[0331] The main control board 1210 is coupled to the interface board 1230. For example, the main control board 1210, the interface board 1230, the interface board 1240, and the switching network board 1220 are connected to the system backplane through a system bus to achieve intercommunication. In a possible implementation, an inter-process communication (IPC) channel is established between the main control board 1210 and the interface board 1230, and the main control board 1210 and the interface board 1230 communicate through the IPC channel.

[0332] Logically, the network device 1200 includes a control plane and a forwarding plane. The control plane includes a main control board 1210 and a central processor 1231. The forwarding plane includes various components for performing forwarding, such as a forwarding table entry memory 1234, a physical interface card 1233, and a network processor 1232. The control plane performs functions such as a router, generating a forwarding table, processing signaling and protocol messages, and configuring and maintaining the status of the device. The control plane sends the generated forwarding table to the forwarding plane. On the forwarding plane, the network processor 1232 forwards the message received by the physical interface card 1233 based on the forwarding table sent by the control plane. The forwarding table sent by the control plane can be stored in the forwarding table entry memory 1234. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.

[0333] If the network device 1200 is configured as a CP device, the network processor 1232 may generate a first charging message including an identifier of the first UP device, and send the first charging message from the physical interface card 1233 .

[0334] If the network device 1200 is configured as the second device, the physical interface card 1233 receives the first message and sends it to the network processor 1232 . The network processor 1232 responds to the first message and generates a second message and sends the second message to the CP device through the physical interface card 1233 .

[0335] If the network device 1200 is configured as the first device, the physical interface card 1233 receives the billing message carrying the first UP device identifier or the second UP device identifier and sends it to the network processor 1232. The network processor 1232 obtains relevant traceability from the first UP device or the second UP device based on the message.

[0336] The transceiver unit 801 in the CP device 800 is equivalent to the physical interface card 1233 in the network device 1200 ; the processing unit 802 in the CP device 800 may be equivalent to the network processor 1232 or the central processor 1211 in the network device 1200 .

[0337] The transceiver unit 901 in the second device 900 is equivalent to the physical interface card 1233 in the network device 1200 ; the processing unit 902 in the second device 900 may be equivalent to the network processor 1232 or the central processor 1211 in the network device 1200 .

[0338] The transceiver unit 1001 in the first device 1000 is equivalent to the physical interface card 1233 in the network device 1200 ; the processing unit 1002 in the CP device may be equivalent to the network processor 1232 or the central processor 1211 in the network device 1200 .

[0339] The operation on the interface board 1240 in the embodiment of the present application is consistent with the operation of the interface board 1230, and for the sake of brevity, it will not be repeated. The network device 1200 of this embodiment can correspond to the CP device, the second device or the first device in the above-mentioned various method embodiments, and the main control board 1210, the interface board 1230 and / or 1240 in the network device 1200 can implement the functions and / or various steps implemented by the CP device, the second device or the first device in the above-mentioned various method embodiments, and for the sake of brevity, it will not be repeated here.

[0340] It is worth noting that there may be one or more main control boards, and when there are multiple boards, they may include a primary main control board and a backup main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There may also be one or more physical interface cards on the interface board. There may be no switching network board, or there may be one or more switching network boards. When there are multiple switching network boards, they can jointly realize load sharing and redundant backup. In a centralized forwarding architecture, network devices may not need switching network boards, and the interface board is responsible for processing the service data of the entire system. In a distributed forwarding architecture, network devices can have at least one switching network board, which realizes data exchange between multiple interface boards and provides large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices with distributed architecture are greater than those of devices with centralized architecture. Optionally, the network device may have only one board, that is, no switching board, and the functions of the interface board and the main control board are integrated on the board. In this case, the central processor on the interface board and the central processor on the main control board can be combined into one central processor on the board to perform the functions of the two. This type of device has low data exchange and processing capabilities (for example, low-end switches or routers and other network devices). The specific architecture to be adopted depends on the specific networking deployment scenario, and no limitation is made here.

[0341] In some possible embodiments, the above-mentioned CP device, the second device or the first device may be implemented as a virtualized device.

[0342] For example, a virtualized device may be a virtual machine (English: Virtual Machine, VM) running a program for sending message functions, and the virtual machine is deployed on a hardware device (for example, a physical server). A virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. The virtual machine can be configured as a CP device, a second device, or a first device. For example, a CP device, a second device, or a first device can be implemented based on a general physical server in combination with Network Function Virtualization (NFV) technology. The CP device, the second device, or the first device is a virtual host, a virtual router, or a virtual switch. Those skilled in the art can virtualize a CP device, a second device, or a first device with the above functions on a general physical server in combination with NFV technology by reading this application. No further details will be given here.

[0343] For example, the virtualized device may be a container, which is an entity for providing an isolated virtualized environment, for example, the container may be a docker container. The container may be configured as a CP device, a second device, or a first device. For example, a CP device, a second device, or a first device may be created through a corresponding image, for example, through an image of a proxy-container (a container providing proxy services), three container instances may be created for the proxy-container, namely, container instance proxy-container1, container instance proxy-container2, and container instance proxy-container3, and container instance proxy-container1 may be provided as a CP device, container instance proxy-container2 may be provided as a second device, and container instance proxy-container3 may be provided as a first device. When implemented using container technology, the CP device, the second device, or the first device may be run using the kernel of a physical machine, and multiple CP devices, second devices, or first devices may share the operating system of a physical machine. Different CP devices, second devices, or first devices may be isolated through container technology. The containerized CP device, the second device or the first device may be run in a virtualized environment, for example, in a virtual machine. The containerized CP device, the second device or the first device may also be run directly in a physical machine.

[0344] For example, a virtualized device may be a Pod, which is a basic unit for Kubernetes (Kubernetes is a container orchestration engine open sourced by Google, referred to as K8s in English) to deploy, manage, and orchestrate containerized applications. A Pod may include one or more containers. Each container in the same Pod is usually deployed on the same host, so each container in the same Pod can communicate through the host and can share the storage resources and network resources of the host. A Pod may be configured as a CP device, a second device, or a first device. For example, specifically, a container as a service (full name in English: containers a service, referred to in English as CaaS, is a container-based PaaS service) may be instructed to create a Pod and provide the Pod as a CP device, a second device, or a first device.

[0345] Of course, the CP device, the second device or the first device may also be other virtualized devices, which are not listed here one by one.

[0346] In some possible embodiments, the above-mentioned CP device, the second device or the first device may also be implemented by a general-purpose processor. For example, the general-purpose processor may be in the form of a chip. Specifically, the general-purpose processor that implements the CP device, the second device or the first device includes a processing circuit and an input interface and an output interface that are internally connected and communicated with the processing circuit. The processing circuit is used to perform the message generation step in the above-mentioned various method embodiments through the input interface, the processing circuit is used to perform the receiving step in the above-mentioned various method embodiments through the input interface, and the processing circuit is used to perform the sending step in the above-mentioned various method embodiments through the output interface. Optionally, the general-purpose processor may also include a storage medium, and the processing circuit is used to perform the storage step in the above-mentioned various method embodiments through the storage medium. The storage medium may store instructions executed by the processing circuit, and the processing circuit is used to execute the instructions stored in the storage medium to execute the above-mentioned various method embodiments.

[0347] See also Fig.13 , Fig.13 The present application provides a schematic structural diagram of a network system 1300, wherein the system 1300 includes: a CP device 1310 and / or a second device 1320 and / or a first device 1330. Optionally, the CP device 1310 is, for example, a CP device 800, a second device 900, a network device 1000, or a network device 1100, the second device 1320 is, for example, a second device 900, a CP device 800, a network device 1000, or a network device 1100, and the first device 1330 is, for example, a first device 1000, a network device 1000, or a network device 1100.

[0348] An embodiment of the present application provides a computer program product. When the computer program product is run on a CP device, a second device or a first device, the CP device, the second device or the first device executes method 100, method 200, method 300, method 400 or method 500 in the above method embodiments.

[0349] The above-mentioned devices in various product forms respectively have any functions of the CP device, the second device or the first device in the above-mentioned method embodiment, which will not be described in detail here.

[0350] Those of ordinary skill in the art will appreciate that the various method steps and units described in the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0351] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0352] In several embodiments provided in the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0353] The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present application.

[0354] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0355] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0356] The above description is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0357] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer program instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program instructions can be transmitted from a website site, a computer, a server or a data center to another website site, a computer, a server or a data center by wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a tape), an optical medium (for example, a digital video disc (digitalvideo disc, DVD), or a semiconductor medium (such as a solid state drive), etc.

[0358] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0359] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for obtaining traceability information, characterized in that: Applied to a communication system including separation of a control plane CP and a user plane UP, the communication system including a CP device and a first UP device, the method including: In response to satisfying the first condition, the CP device sends a first billing message to the first device, the first billing message includes an identifier of the first UP device, the first billing message is related to a message corresponding to a first user transmitted by the first UP device, and the identifier of the first UP device is used to indicate that the traceability information of the first user is related to the first UP device; the first billing message is used to instruct the first device to obtain the traceability information from the first UP device according to the identifier of the first UP device.

2. The method according to claim 1, characterized in that The communication system further includes a second UP device, and the satisfying the first condition includes: The CP device successfully migrates the message corresponding to the first user from the second UP device to the first UP device.

3. The method according to claim 1, characterized in that: The communication system further includes a second device, and the satisfying of the first condition includes: the CP device receiving a first message sent by the second device, where the first message is used to instruct the CP device to send the first charging message.

4. The method according to claim 3, characterized in that The communication system further includes a second UP device, and the method further includes: The CP device receives a second message sent by the second device, where the second message is used to instruct the CP device to migrate the message corresponding to the first user from the second UP device to the first UP device, and the first message is a response message of the CP device that successfully executes the migration.

5. The method according to claim 2 or 4, characterized in that: Before the CP device migrates the message of the first user from the second UP device to the first UP device, the method further includes: The CP device sends a second charging message to the first device, where the second charging message includes an identifier of the second UP device, and the second charging message is related to the first user.

6. The method according to claim 1, characterized in that The satisfying of the first condition includes: the CP device determining that a sending cycle for sending the charging message is satisfied.

7. The method according to claim 3 or 4, characterized in that: The second device includes a control device or a user plane migration function USF device.

8. A method for obtaining traceability information, characterized in that: Applied to a communication system including separation of a control plane CP and a user plane UP, the communication system including a CP device, a first UP device, a second UP device, a first device and a second device, the method including: The second device is used to generate a second message in response to the first message, the second message is used to instruct the CP device to send a first billing message to the first device, the first billing message includes an identifier of the first UP device, and the first message is used to instruct the CP device to successfully migrate a message corresponding to a first user corresponding to the first billing message from the second UP device to the first UP device; the first billing message is used to instruct the first device to obtain the traceability information from the first UP device according to the identifier of the first UP device; The second device sends the second message to the CP device.

9. The method according to claim 8, characterized in that The second device includes a control device or a user plane migration function USF device.

10. A method for obtaining traceability information, characterized in that: Applied to a communication system including separation of a control plane CP and a user plane UP, the communication system including a CP device, a first UP device and a first device, the method including: The first device receives a first charging message sent by the CP device, where the first charging message includes an identifier of the first UP device, and the first charging message is related to a message corresponding to the first user; The first device obtains the traceability information from the first UP device according to the identifier of the first UP device.

11. The method according to claim 10, characterized in that The first device obtains the traceability information from the first UP device according to the identifier of the first UP device, including: The first device obtains network access information related to the first user from the first UP device according to the identifier of the first UP device.

12. The method according to claim 10 or 11, characterized in that: The communication system further includes a second UP device, the first charging message is related to the first user, and the first charging message includes a charging message sent by the CP device after migrating a message corresponding to the first user from the second UP device to the first UP device.

13. The method according to claim 12, characterized in that The first charging message also includes an identifier of the first user. Before the first device receives the first charging message sent by the CP device, the method further includes: The first device receives a second charging message sent by the CP device, where the second charging message includes an identifier of the second UP device and an identifier of the first user; Before the first device acquires the traceability information from the first UP device according to the identifier of the first UP device, the method further includes: The first device determines, according to the identifier of the first UP device, the identifier of the second UP device, and the identifier of the first user, that a message corresponding to the first user is migrated from the second UP device to the first UP device.

14. The method according to claim 10 or 11, characterized in that: The first device includes a Remote Access Dial-In User Server (RADIUS).

15. A communication device, characterized in that: The communication device comprises at least one processor and a communication interface, wherein the at least one processor is configured to execute a computer program or instruction so that the communication device executes the method according to any one of claims 1 to 14.

16. The communication device according to claim 15, characterized in that: The apparatus further comprises at least one memory coupled to the at least one processor, the computer program or instructions being stored in the at least one memory.

17. A computer-readable storage medium, characterized in that: Used to store computer instructions, when the computer instructions are executed, the method according to any one of claims 1 to 14 is implemented.

18. A communication system with separate control plane CP and user plane UP, characterized in that: Comprising a communication device as claimed in claim 15 or 16.

Images