VLAN Dynamic Configuration Method, 5GS Bridge, Electronic Device and Storage Medium

Abstract

An embodiment of the present application provides a method for dynamically configuring VLANs, a 5GS bridge, an electronic device, and a storage medium, which relate to the field of communication technologies. The method includes: receiving a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of a VLAN to be registered; determining a port in the 5GS bridge corresponding to the VLAN identifier, and generating VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number. The embodiment of the present application can support dynamic configuration of VLAN information, dynamically add or delete VLAN information on the 5G bridge and its ports, while ensuring the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured to ensure the connectivity between the end stations and the bridge. At the same time, it also avoids the limitation of pre-configured VLANs on the selectable communication paths.

Description

Technical Field

[0001] This application relates to the field of communication technologies. Specifically, this application relates to a method for dynamically configuring VLANs, a 5GS bridge, an electronic device, and a storage medium. Background Art

[0002] The current 5G system only supports pre-configuring virtual local area network (VLAN) configuration information in the application function (AF) of the time-sensitive networking (TSN) and the network-side TSN converter (NW-TT), and does not support the interaction of configuration information between the two.

[0003] In a large-scale and complex network environment, it is necessary to manually configure VLAN information for all devices in the entire network, resulting in great complexity. Pre-configuring VLANs also limits the available communication paths. In addition, the dynamic VLAN mechanism cannot support TSN (for example, the selected UPF does not support or cannot register VLAN due to capacity factors), and it is prone to problems such as packet loss and latency. Summary of the Invention

[0004] Embodiments of this application provide a method for dynamically configuring VLANs, a 5GS bridge, an electronic device, and a storage medium that overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect, a method for dynamically configuring VLANs is provided. The method includes:

[0006] Receiving a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of a VLAN to be registered;

[0007] Determining a port in the 5GS bridge corresponding to the VLAN identifier, and generating VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number.

[0008] In a second aspect, a 5GS bridge is provided, including:

[0009] A first request declaration receiving module, configured to receive a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of a VLAN to be registered;

[0010] A configuration information generating module, configured to determine a port in the 5GS bridge corresponding to the VLAN identifier, and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number.

[0011] In a third aspect, a VLAN dynamic configuration device is provided, including a memory, a transceiver, and a processor:

[0012] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and execute the method described in the first aspect.

[0013] In a fourth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the method provided in the first aspect are implemented.

[0014] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method provided in the first aspect are implemented.

[0015] In a sixth aspect, an embodiment of the present application provides a computer program, which includes computer instructions. The computer instructions are stored in a computer-readable storage medium. When the processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, the computer device is caused to execute the steps of the method provided in the first aspect.

[0016] The VLAN dynamic configuration method, 5GS bridge, electronic device, and storage medium provided by the embodiments of the present application receive a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of a VLAN to be registered; determine a port corresponding to the VLAN identifier in the 5GS bridge, and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number, support dynamic configuration of VLAN information, dynamically add or delete VLAN information on the 5G bridge and its ports, and at the same time ensure the consistency of the VLAN configuration information. Especially when the network topology changes, automatic configuration can be performed again, thereby ensuring the connectivity between the end site and the bridge. At the same time, it also avoids the limitation of pre-configured VLANs on the selectable communication paths. Description of the Drawings

[0017] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for the description in the embodiments of the present application.

[0018] Figure 1 It is a schematic diagram of a 5GS-supported TSN network architecture;

[0019] Figure 2 It is a schematic diagram of a 5GS-supported TSC and time synchronization network architecture;

[0020] Figure 3 This is the network architecture diagram for 5GS to support VLAN configuration in the embodiments of the present application;

[0021] Figure 4 This is the schematic flowchart of the VLAN dynamic configuration method in the embodiments of the present application;

[0022] Figure 5 This is the interactive schematic diagram for the TSN terminal in the embodiments of the present application to dynamically configure VLAN for the 5GS bridge and manage VLAN configuration information;

[0023] Figure 6 This is the interactive schematic diagram for selecting the UPF based on the VLAN configuration information during the establishment process of the user plane PDU session in the embodiments of the present application;

[0024] Figure 7 This is the interactive schematic diagram for transmitting data frames in the embodiments of the present application;

[0025] Figure 8 This is the schematic structural diagram of a 5GS bridge provided by the embodiments of the present application;

[0026] Figure 9 This is the schematic structural diagram of an electronic device provided by the embodiments of the present application;

[0027] Figure 10 This is the schematic structural diagram of the VLAN dynamic configuration device provided by the embodiments of the present application. Detailed implementation manners

[0028] The embodiments of the present application will be described in detail below. The examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions from beginning to end. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and should not be construed as a limitation to the present application.

[0029] Those skilled in the art of the present technology can understand that unless specifically stated otherwise, the singular forms "a", "an" and "the" used herein may also include the plural forms. It should be further understood that the term "including" used in the specification of the present application means the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups. It should be understood that when we say an element is "connected" or "coupled" to another element, it can be directly connected or coupled to other elements, or there may also be intermediate elements. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The phrase "and / or" used herein includes all or any unit and all combinations of one or more related listed items.

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the following will further describe the embodiments of this application in detail with reference to the accompanying drawings.

[0031] First, introduce and explain several terms related to this application:

[0032] 1) TSN

[0033] Currently, IEEE (Institute of Electrical and Electronics Engineers) 802.1 TSN is becoming the standard Ethernet technology for industrial 4.0 converged networks.

[0034] IEEE TSN defines three TSN time-sensitive network configuration models, including: 1) fully centralized model, 2) hybrid model: centralized network and distributed users, 3) fully distributed model. Different configuration models can be applied to different working scenarios. Among them, the deployment method of the fully distributed model can provide great flexibility and support the needs of future intelligent manufacturing.

[0035] In 3GPP Rel-16 and Rel-17, the 5G system only supports integration with a TSN network deployed based on the fully centralized model, and its architecture is as Figure 1 shown.

[0036] The 5G TSN technology has requirements for the transformation of terminals, base stations, transmission, and core networks. Terminals and UPFs need to support the TT (TSN Translator) function. 5GS can be regarded as a Bridge (network bridge), which consists of a port on the UPF (PSA) side, a user plane tunnel between the UE and the UPF, and a port on the DS-TT side.

[0037] In the system architecture where 5GS appears as a Bridge, the main network functions are introduced as follows:

[0038] CNC: Centralized Network Configuration, centralized network configuration, which can be applied to network devices (network bridges).

[0039] CUC: Centralized User Configuration, centralized user configuration, which can be applied to user devices (End Station).

[0040] AMF: Access and Mobility Management Function, access and mobility management function, registration, connection management, etc.

[0041] UPF: User Plan Function, the user plane function. It is an external PDU session node interconnected with the data network, responsible for message routing and forwarding.

[0042] SMF: Session Management Function, the session management function. It is responsible for session establishment, deletion, user plane selection and control, UE IP allocation, etc.

[0043] AF: Application Function, the application function. It interacts with the 3GPP core network to provide services. Based on the operator's deployment, a trusted AF can directly interact with relevant NFs, while an untrusted AF cannot directly interact with NFs and should use the publicly available framework to interact through the NEF. The TSN AF is the AF that represents the TSN domain (including CUC / CNC) to interact with the 5G system control plane.

[0044] PCF: Policy Control Function, the policy control function. It supports a unified policy framework to manage network behavior and provides policy rules for control plane NFs to execute.

[0045] UDM: Unified Data Management, the unified data management. It stores UE information, such as subscription information and information on established PDU sessions.

[0046] NEF: Network Exposure Function, the network exposure function. It provides the function of securely exposing the services and capabilities provided by the 3GPP network to external networks.

[0047] UDR: Unified Data Repository, the unified database UDR. It stores subscription data and enables the UDM FE to retrieve subscription data. It also stores policy information and enables the PCF to retrieve policy information.

[0048] 2) The 5GS supports a network architecture with TSC and time synchronization

[0049] Please refer to Figure 2, based on the 3GPP Rel-17 standard, the 5G system supports TSC (Time Sensitive Communication) and time synchronization services when TSN (including TSN CUC and TSN CNC) is not deployed. In this architecture, a new core network element is introduced: the Time Sensitive Communication and Time Synchronization function entity (TSCTSF). TSCTSF contains TSC and time synchronization service logic and can control the TSN converters DS-TT and NW-TT on the terminal side to form a (g)PTP instance.

[0050] 3) 5G TSN

[0051] The current 5GS only supports integration with a TSN network deployed based on a fully centralized model. Under the fully centralized model, the 5G system supports pre-configuring VLAN configuration information in the TSN AF and NW-TT and does not support the interaction of configuration information between the two. For the support of Ethernet-type PDU sessions, the SMF can receive a list of allowed VLAN identifiers from the DN-AAA or locally configure the allowed VLAN identifiers. And the SMF can be configured with VLAN processing instructions. The SMF determines the VLAN processing method for the PDU session and instructs the UPF to accept or discard the UE's data based on the allowed VLAN identifiers and process the VLAN identifiers (add / delete) according to rules such as PDR. For example, for data without a VLAN identifier, the UPF can insert a VLAN identifier (for uplink data) and delete the VLAN identifier (for downlink data) at the N6 interface. In the prior art, the network can select the UPF based on the VLAN identifier (also simply referred to as VID, the same below) subscribed by the UDM.

[0052] 4) IEEE TSN network

[0053] The basic functions of a TSN bridge include: frame forwarding and filtering, maintaining information for making forwarding and filtering decisions, and the management of the bridge.

[0054] In a fully distributed model, the IEEE defines MRP (Multiple Registration Protocol) to implement dynamic flow joining and leaving, as well as dynamic resource management, etc. MRP (Multiple Registration Protocol), the multi-attribute registration protocol, enables the declaration, registration, propagation, and cancellation of a certain attribute among devices within the same switching network. Devices supporting MRP can quickly spread their own attribute information to the switching network, and the field information contained in the attributes can be used to achieve the function of "signaling". This attribute is defined by specific MRP applications. For example, in MVRP (Multiple VLAN Registration Protocol), the VLAN attribute is defined. The main function of MVRP is to dynamically propagate and maintain VLAN information. Ethernet switches supporting the protocol can receive information propagated by other switches and dynamically update the local registration information, mainly including which VLANs are registered on the current switch and which VLANs are joined to each interface. The locally registered information can be dynamically propagated to other switches, so that all protocol-supporting switches on the same Ethernet can reach an agreement in configuration and achieve interoperability.

[0055] In a bridge, there is a Filtering Database (FDB), which stores all the information for the bridge to make forwarding decisions and is the core of the bridge. The FDB supports determining whether the received frames (specific MAC addresses, VIDs) can be forwarded through possible transmission ports. The filtering information contained in the FDB can be in two forms: static, configured through management operations; and dynamic, automatically configured into the FDB through operations supported by the bridge.

[0056] Among them, 4 types of entries are used to represent dynamic filtering information:

[0057] 1) Each dynamic filtering entry determines which data frames with specific MAC addresses and VIDs (if VLAN bridges are supported) have been or can be received.

[0058] 2) MAC Address Registration Entries support the registration of MAC addresses. They can be created, updated, or deleted through the MMRP mechanism.

[0059] 3) Dynamic VLAN Registration Entries are used to determine on which ports the VLAN membership has been dynamically registered. They can be created, updated, or deleted through the MVRP mechanism.

[0060] 4) Dynamic Reservation Entries can be used to determine on which port the flow reservation has been completed.

[0061] An End Station (ES) can propagate attribute declarations to other End Stations through one or more Bridges.

[0062] The VLAN dynamic configuration method, 5GS bridge, electronic device, and storage medium provided in this application aim to solve the problem that the existing 5GS cannot support dynamic configuration of VLAN information, including dynamically adding or deleting VLAN information on 5G bridges and their ports, and the pre-configured VLAN limits the selectable communication paths. Since it only supports selecting the UPF based on the VLAN (VID) subscribed by the UDM and cannot select a suitable UPF, the dynamic VLAN mechanism cannot support the TSN network, resulting in problems such as packet loss and latency.

[0063] The technical solution of this application and how the technical solution of this application solves the above technical problems will be described in detail below with specific embodiments. These several specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0064] Please refer to Figure 3 , which exemplarily shows the network architecture diagram of 5GS supporting VLAN configuration in the embodiments of this application. As shown in the figure, the 5GS bridge in the embodiments of this application includes a functional entity at the entrance (entrance TT, which can be a UE or a DS-TT), a functional entity at the exit (exit TT, which can be a UPF or an NW-TT), NG-RAN, and AF / TSCTSF. Optionally, the AF in the embodiments of this application can be a TSN AF or a non-TSN AF.

[0065] ES1 to 3 are respectively connected to the entrance TT through ports PORT1 to 3 to send data frames. AF / TSCTSF sends data transmission rules such as VLAN configuration information to the entrance TT and the exit TT, enabling the entrance TT and the exit TT to discard or transmit the data frames to ES4 and ES5 through PORT4 and 5 according to the data transmission rules.

[0066] The 5GS bridge in the embodiments of this application supports the TSN MVRP mechanism to realize the dynamic configuration (registration / deregistration) of VLANs from TSN terminals to the 5GS bridge. AF / TSCTSF or UPF / NW-TT manages the VLAN configuration information and supports filtering or forwarding of data frames.

[0067] Please refer toFigure 4 , which exemplarily shows a schematic flowchart of the VLAN dynamic configuration method according to an embodiment of the present application. As shown in the figure, it includes:

[0068] S101. Receive a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of a VLAN to be registered.

[0069] Specifically, an ES or a talker (sender) sends a MAD_Join.request request attribute declaration (i.e., the first request attribute declaration). The first request attribute declaration includes an attribute_type field, which is the VLAN identifier. The request attribute declaration is used to register a VLAN membership to indicate to the bridge the VLAN that it hopes to join and receive data sent to the target VLAN identified by the VID.

[0070] S102. Determine a port corresponding to the VLAN identifier in the 5GS bridge and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number.

[0071] A functional entity at the entrance of the 5GS bridge, such as NW-TT or DS-TT, receives the first request attribute declaration and registers the VLAN identifier at the port. After that, the AF in the 5GS bridge can generate the VLAN configuration information. The AF can generate a corresponding port set (Port Map) for each VLAN identifier. The VLAN configuration information may include: 1) VID; 2) a port set, which defines for each exit port whether the VID is registered at this port. An example is shown in Table 1 below:

[0072] VLAN ID (VID) Port Number VID 1 P1, P2 VID 2 P2, P4 VID 3 P1, P3, P4 VID 4 P3, P4

[0073] Table 1 VLAN configuration information

[0074] A total of 4 VLAN identifiers are shown in Table 1. Each VLAN identifier corresponds to at least one port number. Taking the VLAN identifier of VID1 as an example, a data frame with this VLAN identifier can be sent through the ports with port numbers P1 and / or P2.

[0075] The VLAN dynamic configuration method of the embodiments of the present application receives a first request attribute declaration, where the first request attribute declaration includes the VLAN identifier of the VLAN to be registered; determines the port corresponding to the VLAN identifier in the 5GS bridge, and generates VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number, supports dynamic configuration of VLAN information, dynamically adds or deletes VLAN information on the 5G bridge and its ports, and at the same time ensures the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured to ensure the connectivity between the end site and the bridge. At the same time, it also avoids the limitation of pre-configured VLANs on the selectable communication paths.

[0076] Based on the above embodiments, as an optional embodiment, after generating the VLAN configuration information, it further includes:

[0077] Receiving a cancellation attribute declaration, where the cancellation attribute declaration includes the VLAN identifier of the VLAN to be cancelled; deleting the VLAN identifier and the corresponding information in the VLAN configuration information.

[0078] In the embodiments of the present application, the ES or talker (sender) sends a MAD_Leave.request (attribute_type, attribute_value, new) cancellation attribute declaration to cancel the membership of a VLAN, indicating that it no longer wishes to receive data sent to the target VLAN of the VID. When the 5GS bridge receives the cancellation attribute declaration, it will delete the entry of the VID to be cancelled included in the cancellation attribute declaration in the VLAN configuration information.

[0079] Taking Table 1 as an example, if the VID included in the cancellation attribute declaration is VID3 and the port number of the port receiving this declaration is P1, then the VID and the corresponding port P1 are deleted.

[0080] Please refer to Figure 5 , which exemplarily shows the interaction schematic diagram of the TSN terminal of the embodiments of the present application dynamically configuring (registering / cancelling) VLANs with the 5GS bridge, and the AF (which can also be the TSCTSF) manages the VLAN configuration information. As shown in the figure, the interaction process includes:

[0081] 0. Select the UPF and establish one or more PDU sessions for the UE / DS-TT to the TSN system through the same UPF.

[0082] 1. The ES / talker (sender) sends a MAD_Join.request (attribute_type, attribute_vaule, new) request for attribute declaration to the 5GS bridge, where the attribute_type field is the VID Vector attribute type (used to identify the value of the VLAN). This request information is used to register a VLAN membership to indicate to the 5GS bridge the VLAN that it wishes to join and receive data sent to the target VLAN identified by the VLAN.

[0083] In addition, the ES or talker can send a MAD_Leave.reqest to cancel the attribute declaration to cancel a VLAN membership and indicate that it no longer wishes to receive data sent to the target VLAN identified by the VID.

[0084] This MRP protocol packet (MRP Protocol Data Unit, MRPDU) can be encapsulated in a general Ethernet data frame for propagation.

[0085] 2. NW-TT or DS-TT, as the entry of the 5GS bridge, receives the information from the sender. NW-TT / DS-TT sends indication information containing the registered or cancelled VID and the corresponding port number to the TSN AF / TSCTSF (filtering database). Optionally, the indication information can be reported to the TSN AF or TSCTSF through the PMIC or UMIC.

[0086] NW-TT or DS-TT also registers this attribute on its port. For example, it registers VID1, VID3, etc. on port P1 and sends the MAD_join.request (register / cancel VLAN membership) received from the ES to the DS-TT / NW-TT at the exit of the bridge. This MRP protocol packet is encapsulated in a 5G transport packet for propagation.

[0087] 3. The AF or TSCTSF maintains the VLAN configuration information and modifies the VLAN configuration information accordingly based on the information received in step 2.

[0088] For example, when receiving the registration information, if this VLAN configuration information does not exist and there is sufficient storage space, the receiving port is registered from the port set related to this VLAN identifier. When receiving the cancellation information, the receiving port is cancelled from the port set related to this VID. If this entry does not exist, this information is ignored.

[0089] AF or TSCTSF generates a separate registration entry containing a specific Port Map (set of ports) for each VLAN identifier. Specifically, the VLAN configuration information may include: 1) VID; 2) a set of ports that defines for each egress port whether the VID is registered on this port.

[0090] Based on the above embodiments, as an alternative embodiment, the VLAN configuration information further includes a UPF identifier corresponding to the VLAN identifier; the UPF corresponding to the UPF identifier supports the VLAN corresponding to the VLAN identifier.

[0091] Please refer to Table 2, which shows the VLAN configuration information of another embodiment of the present application.

[0092]

[0093]

[0094] As shown in Table 2, the VLAN configuration information further includes the UPF identifier of the UPF that supports the corresponding VLAN identifier. For example, the UPF with the UPF identifier of ID1 supports the propagation of data frames with VID2 and VID1.

[0095] Correspondingly, after generating the VLAN configuration information, it further includes:

[0096] Receiving a second request attribute declaration, where the second request attribute declaration includes a target VLAN identifier;

[0097] According to the target VLAN identifier, in combination with the VLAN configuration information, determine the target UPF required to establish a PDU session from the UPF that supports the VLAN corresponding to the target VLAN identifier or all UPFs that support VLAN dynamic configuration.

[0098] The embodiments of the present application avoid the limitation of pre-configured VLANs on selectable communication paths. The network provides VLAN information with dynamic configuration for UPF selection to select a suitable UPF.

[0099] Please refer to Figure 6 , which exemplarily shows an interaction schematic diagram of selecting a UPF based on VLAN configuration information during the establishment process of a user plane PDU session in the embodiments of the present application. As shown in the figure, the interaction process includes:

[0100] 1. The ES sends a request attribute declaration to the 5GS bridge, the same as Figure 5 Step 1 in the shown embodiment.

[0101] 2. The UE initiates the establishment of a PDU session and sends the VID received in step 1 included in the PCO.

[0102] 3. Based on the prior art, the AMF performs SMF selection.

[0103] 4. The AMF sends an Nsmf_PDUSession_CreateSMContext Request message to the SMF to request the establishment of an AMF-SMF association that supports the PDU session. The message contains the VID.

[0104] 5. The SMF sends a query message to the AF / TSCTSF through the PCF. The message may include VID information. The AF / TSCTSF queries the User-Plane Node ID or UPF ID that supports the VID based on the VLAN configuration information and the VID. Returns the data corresponding to the queried VID to the SMF, or returns the information of all UPFs that support VLAN dynamic configuration (for example, no UPF is registered to support the VID).

[0105] 6. The SMF determines a suitable UPF based on the received information. For example, a UPF that can support VLAN dynamic configuration or a UPF that can support the corresponding VID.

[0106] 7. The SMF replies to the AMF with an Nsmf_PDUSession_CreateSMContext Response message.

[0107] 8. Complete the establishment of the PDU session according to the prior art.

[0108] Based on the above embodiments, as an alternative embodiment, after generating the VLAN configuration information, it further includes:

[0109] Receiving a data frame. If it is determined that the data frame includes a VLAN identifier, then filter or forward the data frame according to the VLAN configuration information and the VLAN identifier in the data frame.

[0110] Specifically, if the VLAN identifier in the data frame exists in the VLAN configuration information, select at least one port number corresponding to the VLAN identifier to forward the data frame;

[0111] If the VLAN identifier in the data frame does not exist in the VLAN configuration information, filter the data frame.

[0112] Please refer to Figure 7 , which exemplarily shows an interaction diagram for transmitting data frames in an embodiment of the present application. As shown in the figure, the interaction process includes:

[0113] 1. The ES sends an Ethernet data frame to the 5GS bridge.

[0114] 2. The ingress DS-TT / NW-TT receives Ethernet data frames and determines whether to discard the frame based on pre-configured or AF-configured input rules (the AF can configure the input rules for DS-TT / NW-TT through the PMIC). For example, if the port only accepts tagged frames and the received data frame does not carry a VID, the frame is discarded. If not discarded, the frame is assigned to a VLAN. For example, the value in vlan_identifier (such as VID1) or the PVID of the receiving port (such as VID3) can be used.

[0115] 3. The egress DS-TT / NW-TT receives data frames and determines whether to filter or forward the data frames based on VLAN configuration information obtained from local storage or AF / TSCTSF (including VLAN dynamic configuration information (generated through Embodiment 1 of this application) and pre-configured static configuration information). The VLAN configuration information defines a member set, and through which ports the members of the VLAN identified by the VID can reach. By querying the registration entries, for example, by inputting the VID, the corresponding port set is queried. If the output port does not appear in its member set for the VID of the frame, the data frame is filtered. For a specific example, according to the table in Embodiment 1, if VID1 is input and port1 and port2 support VID1, then VID1 can be transmitted through port1 / port2. If VID9 is input and no port supports this VLAN, the data frame is filtered out.

[0116] 4. If the data frame is not filtered, the egress DS-TT / NW-TT forwards the data frame to other bridges or the target ES.

[0117] Based on the above embodiments, as an optional embodiment, when the VLAN configuration information is stored in the AF or TSCTSF, the receiving of the first request attribute declaration further includes:

[0118] The functional entity at the ingress of the 5GS bridge sends indication information to the AF or TSCTSF storing the VLAN configuration information. The indication information includes the VLAN identifier of the VLAN to be registered and the corresponding port number.

[0119] In the embodiments of the present application, since the VLAN configuration information is not maintained by the functional entity at the ingress, when the functional entity at the ingress receives the request attribute information or the deregistration attribute information, the functional entity at the ingress needs to send indication information to the AF / TSCTSF to instruct the AF / TSCTSF to generate VLAN configuration information according to the indication information.

[0120] Based on the above embodiments, as an alternative embodiment, when the VLAN configuration information is stored in the functional entity at the ingress of the 5GS bridge, after receiving the first request attribute declaration, the following further includes:

[0121] Send the first request attribute declaration to the functional entity at the egress of the 5GS bridge.

[0122] It should be noted that the embodiments of the present application support the dynamic configuration (registration / deregistration) of VLANs for TSN terminals to the 5GS bridge based on the MVRP mechanism, and the UPF / NW-TT manages the VLAN configuration information. Different from the Figure 5 illustrated embodiment, in steps 2 and 3, NW-TT or DS-TT serves as the ingress of the 5GS bridge and does not need to send indication information to the AF. It only needs to register this attribute on the port and send the MAD_join.request received from the ES to the DS-TT / NW-TT at the egress of the bridge. NW-TT / UPF maintains the VLAN configuration information and performs the same operations as AF / TSCTSF in Embodiment 1.

[0123] Based on the above embodiments, as an alternative embodiment, in the case where the VLAN configuration information is stored in the functional entity at the ingress of the 5GS bridge:

[0124] When the functional entity at the egress of the 5GS bridge is DS-TT, process the data frame according to the VLAN configuration information stored locally or obtained from the functional entity at the ingress of the 5GS bridge;

[0125] When the functional entity at the egress of the 5GS bridge is NW-TT, process the data frame according to the VLAN configuration information stored locally.

[0126] The embodiments of the present application provide a 5GS bridge, as Figure 8 shown, the 5GS bridge may include: a first request declaration receiving module 101 and a configuration information generating module 102. Specifically:

[0127] The first request declaration receiving module 101 is configured to receive a first request attribute declaration, and the first request attribute declaration includes a VLAN identifier of the VLAN to be registered;

[0128] The configuration information generating module 102 is configured to determine the port in the 5GS bridge corresponding to the VLAN identifier, and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number.

[0129] The 5GS bridge provided by the embodiment of the present application specifically executes the process of the above method embodiment. For specific details, please refer to the content of the above embodiment of the VLAN dynamic configuration method, which will not be elaborated here. The 5GS bridge provided by the embodiment of the present application receives a first request attribute declaration, where the first request attribute declaration includes the VLAN identifier of the VLAN to be registered; determines the port corresponding to the VLAN identifier in the 5GS bridge, generates VLAN configuration information, and the VLAN configuration information includes the registered VLAN identifier and the corresponding port number, supports dynamic configuration of VLAN information, dynamically adds or deletes VLAN information on the 5G bridge and its ports, and at the same time ensures the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured, thus ensuring the connectivity between the end site and the bridge. At the same time, it also avoids the limitation of pre-configured VLAN on the selectable communication paths.

[0130] An electronic device is provided in an embodiment of the present application. The electronic device includes: a memory and a processor; at least one program stored in the memory and used to be executed by the processor, which can achieve, compared with the prior art: by receiving a first request attribute declaration, where the first request attribute declaration includes the VLAN identifier of the VLAN to be registered; determines the port corresponding to the VLAN identifier in the 5GS bridge, generates VLAN configuration information, and the VLAN configuration information includes the registered VLAN identifier and the corresponding port number, supports dynamic configuration of VLAN information, dynamically adds or deletes VLAN information on the 5G bridge and its ports, and at the same time ensures the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured, thus ensuring the connectivity between the end site and the bridge. At the same time, it also avoids the limitation of pre-configured VLAN on the selectable communication paths.

[0131] In an optional embodiment, an electronic device is provided, as Figure 9 shown, Figure 9 The electronic device 4000 shown includes a processor 4001 and a memory 4003. Among them, the processor 4001 and the memory 4003 are connected, such as connected through a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation to the embodiment of the present application.

[0132] The processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application. The processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0133] The bus 4002 may include a path for transmitting information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 9 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0134] The memory 4003 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, or it may also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, 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.

[0135] The memory 4003 is used to store the application program code for implementing the solution of this application, and is controlled by the processor 4001 to execute. The processor 4001 is used to execute the application program code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0136] As Figure 10 shown, an embodiment of this application further provides a VLAN dynamic configuration device, including a memory 1020, a transceiver 1040, and a processor 1010;

[0137] The memory 1020 is used to store a computer program;

[0138] The transceiver 1040 is used to receive and send data under the control of the processor 1010;

[0139] The processor 1010 is used to read the computer program in the memory 1020 and perform the following operations:

[0140] Receive a first request attribute declaration, where the first request attribute declaration includes a VLAN identifier of the VLAN to be registered;

[0141] Determine the port corresponding to the VLAN identifier in the 5GS bridge, and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port number.

[0142] Among them, in Figure 10 , the bus architecture may include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors 1010 represented by the processor 1010 and the memory 1020 represented by the memory 1020 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, the embodiments of this application will not further describe them. The bus interface 1030 provides an interface. The transceiver 1040 may be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical cables, and other transmission mediums. The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 can store the data used by the processor 1010 when performing operations.

[0143] The processor 1010 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 1010 may also adopt a multi-core architecture.

[0144] The processor 1010 is configured to execute the VLAN dynamic configuration method provided in the embodiments of the present application according to the obtained executable instructions by calling a computer program stored in the memory 1020. The processor 1010 and the memory 1020 may also be physically separated.

[0145] The embodiments of the present application provide a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program runs on a computer, the computer can execute the corresponding content in the foregoing method embodiments. Compared with the prior art, by receiving a first request attribute declaration including a VLAN identifier of a VLAN to be registered, determining a port corresponding to the VLAN identifier in the 5GS bridge, and generating VLAN configuration information including the registered VLAN identifier and the corresponding port number, it supports dynamic configuration of VLAN information, dynamically adds or deletes VLAN information on the 5G bridge and its ports, and at the same time ensures the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured to ensure the connectivity between the end stations and the bridge. At the same time, it also avoids the limitation of pre-configured VLANs on the selectable communication paths.

[0146] An embodiment of the present application provides a computer program, which includes computer instructions stored in a computer-readable storage medium. When a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, the computer device is caused to execute the content shown in the foregoing method embodiment. Compared with the prior art, by receiving a first request attribute declaration, the first request attribute declaration includes a VLAN identifier of a VLAN to be registered; determining a port corresponding to the VLAN identifier in the 5GS bridge, generating VLAN configuration information, the VLAN configuration information includes the registered VLAN identifier and the corresponding port number, supports dynamic configuration of VLAN information, dynamically adds or deletes VLAN information on the 5G bridge and its ports, and at the same time ensures the consistency of the VLAN configuration information. Especially when the network topology changes, it can be automatically reconfigured to ensure the connectivity between the end site and the bridge. At the same time, it also avoids the limitation of pre-configured VLAN on the selectable communication paths.

[0147] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise clearly stated in this article, there is no strict order restriction for the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0148] The above are only some embodiments of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A method for dynamically configuring a Virtual Local Area Network (VLAN), characterized in that, it is applied to a 5GS bridge, and the 5GS bridge includes a functional entity at the entrance and an AF. The functional entity at the entrance is NW-TT or DS-TT. The above method includes: The functional entity at the entrance receives a first request attribute statement sent by an ES or a talker. The first request attribute statement includes a VLAN identifier of the VLAN to be registered. The first request attribute statement is used to register a VLAN membership to indicate to the 5GS bridge the VLAN that it hopes to join and receive data sent to the target VLAN corresponding to the VLAN identifier; The AF generates a corresponding port set for the VLAN identifier, determines the ports in the 5GS bridge corresponding to the VLAN identifier, and generates VLAN configuration information. The VLAN configuration information includes the registered VLAN identifier and the corresponding port set; The VLAN configuration information further includes a UPF identifier corresponding to the VLAN identifier; the user plane function entity UPF of the UPF identifier supports the VLAN corresponding to the VLAN identifier; After generating the VLAN configuration information, it further includes: The AF receives a second request attribute statement sent by the SMF through the PCF. The second request attribute statement includes a target VLAN identifier; The AF determines the target UPF required to establish a PDU session from the UPFs that support the VLAN corresponding to the target VLAN identifier or all UPFs that support VLAN dynamic configuration, in combination with the VLAN configuration information, according to the target VLAN identifier; Among them, the second request attribute statement is sent by the SMF to the AF after receiving the Nsmf_PDUSession_CreateSMContext Request information sent by the AMF. The Nsmf_PDUSession_CreateSMContext Request information requests to establish an AMF-SMF association that supports a PDU session, and the Nsmf_PDUSession_CreateSMContext Request information includes the target VLAN identifier.

2. The VLAN dynamic configuration method according to claim 1, characterized in that, After generating the VLAN configuration information, it further includes: Receiving a cancellation attribute statement, the cancellation attribute statement includes a VLAN identifier of the VLAN to be cancelled; Deleting the VLAN identifier and the corresponding information in the VLAN configuration information.

3. The VLAN dynamic configuration method according to claim 1, characterized in that, After generating the VLAN configuration information, it further includes: Receiving a data frame; If it is determined that the data frame includes a VLAN identifier, then filter or forward the data frame according to the VLAN configuration information and the VLAN identifier in the data frame.

4. The VLAN dynamic configuration method according to claim 3, characterized in that, Judging whether to filter or forward the data frame according to the VLAN configuration information and the VLAN identifier in the data frame includes: If the VLAN identifier in the data frame exists in the VLAN configuration information, select at least one port number corresponding to the VLAN identifier and forward the data frame through the port; If the VLAN identifier in the data frame does not exist in the VLAN configuration information, filter the data frame.

5. The VLAN dynamic configuration method according to claim 1, wherein, when the VLAN configuration information is stored in the Application Function (AF) or the Time-Sensitive Communication and Time Synchronization Function Entity (TSCTSF), receiving a first Request Attribute Declaration further includes: sending indication information from the functional entity at the ingress of the 5GS bridge to the AF or TSCTSF storing the VLAN configuration information, where the indication information includes the VLAN identifier of the VLAN to be registered and the corresponding port set.

6. The VLAN dynamic configuration method according to claim 1, wherein, when the VLAN configuration information is stored in the functional entity at the ingress of the 5GS bridge, after receiving the first Request Attribute Declaration, further includes: sending the first Request Attribute Declaration to the functional entity at the egress of the 5GS bridge.

7. The VLAN dynamic configuration method according to claim 6, wherein, when the functional entity at the egress of the 5GS bridge is the terminal-side TSN converter, process the data frame according to the VLAN configuration information stored locally or obtained from the functional entity at the ingress of the 5GS bridge; when the functional entity at the egress of the 5GS bridge is the network-side TSN converter, process the data frame according to the VLAN configuration information stored locally.

8. A 5GS bridge, wherein, it includes: A functional entity at the ingress, configured to receive a first Request Attribute Declaration sent by an ES or a talker, where the first Request Attribute Declaration includes the VLAN identifier of the VLAN to be registered, and the first Request Attribute Declaration is used to register a VLAN membership to indicate the VLAN that the 5GS bridge is desired to join, and receive data sent to the target VLAN corresponding to the VLAN identifier, and the functional entity at the ingress is NW-TT or DS-TT; AF, configured to generate a corresponding port set for the VLAN identifier, determine the ports in the 5GS bridge corresponding to the VLAN identifier, and generate VLAN configuration information, where the VLAN configuration information includes the registered VLAN identifier and the corresponding port set; The VLAN configuration information further includes a UPF identifier corresponding to the VLAN identifier; the User Plane Function (UPF) of the UPF identifier supports the VLAN corresponding to the VLAN identifier; After generating the VLAN configuration information, AF is further configured to: receive a second Request Attribute Declaration sent by the SMF through the PCF, where the second Request Attribute Declaration includes the target VLAN identifier; Determine a target UPF required for establishing a PDU session from the UPF of the VLAN that supports the target VLAN identifier or all UPFs that support VLAN dynamic configuration, in combination with the VLAN configuration information according to the target VLAN identifier; Among them, the second request attribute statement is sent by the SMF to the AF after receiving the Nsmf_PDUSession_CreateSMContext Request message sent by the AMF. The Nsmf_PDUSession_CreateSMContext Request message requests to establish an AMF-SMF association that supports the PDU session, and the Nsmf_PDUSession_CreateSMContext Request message includes the target VLAN identifier.

9. A VLAN dynamic configuration device, Characterized in that, It includes a memory, a transceiver, and a processor: The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is used to read the computer program in the memory and execute the steps of VLAN dynamic configuration as described in any one of claims 1 to 7.

10. An electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, Characterized in that, When the processor executes the computer program, it implements the steps of the VLAN dynamic configuration method as described in any one of claims 1 to 7.

11. A computer-readable storage medium, Characterized in that, The computer-readable storage medium stores computer instructions, and the computer instructions cause the computer to execute the steps of the VLAN dynamic configuration method as described in any one of claims 1 to 7.

Images