Patent Description:
Virtual Local Area Network (VLAN) membership can be established either statically or dynamically. Static VLANs are also referred to as port-based VLANs. Static VLAN assignments are created by assigning ports to a VLAN. As a device enters the network, the device automatically assumes the VLAN of the port. If the user changes ports and needs access to the same VLAN, a network administrator must manually make a port-to-VLAN assignment for the new connection.

Dynamic VLANs are created using software or by protocol. With a VLAN Management Policy Server (VMPS), an administrator can assign switch ports to VLANs dynamically based on information such as the source Medium Access Control (MAC) address of the device connected to the port, or the username used to log onto that device. As a device enters the network, the switch queries a database for the VLAN membership of the port to which that device is connected. IEEE <NUM>. 1Q defines the Multiple VLAN Registration Protocol (MVRP), which is an application of the Multiple Registration Protocol and allows bridges to negotiate the set of VLANs to be used over a specific link.

A bridge port can be configured in either Access port mode or Trunk port mode for VLAN operation. Access port mode generally is connected to an end-device (e.g., a computer) for access purpose, and a single VLAN is assigned for the access port. Trunk port mode allows ports to transmit and receive data of multiple VLANs; normally, the trunk port mode is used for connection between network devices (bridges, routers).

Specifications promulgated by the Third Generation Partnership Project (3GPP) that define Fifth Generation (<NUM>) telecommunication networks have included some Ethernet support since Release <NUM>. Examples of such support include support for Ethernet Protocol Data Unit (PDU) sessions and MAC learning. Release <NUM> (Rel <NUM>) and Release <NUM> (Rel <NUM>) of the 3GPP specifications enhance the support. Rel <NUM>, for example, introduced <NUM> support for LAN-type services. Rel <NUM> also specified that a <NUM> system can be modelled as one or more logical Ethernet bridges, to support integration with Ethernet Time Sensitive Networking (TSN) network. IEEE <NUM>. 1Q defines TSN as a standard technology to provide deterministic messaging on standard Ethernet.

With example reference to the Third Generation Partnership Project (3GPP) Technical Specification (TS) <NUM> v17. <NUM>, <NUM> Virtual Network (VN) group communication includes one to one communication and one to many communication. One to one communication supports forwarding of unicast traffic between two User Equipments (UEs) within a <NUM> VN, or between a UE and a device on a Domain Network (DN). One to many communication supports forwarding of multicast traffic and broadcast traffic from one UE (or device on a DN) to many/all UEs within a <NUM> VN and devices on the DN.

<NUM> VN Group Data can be configured through an Application Function (AF) communicating with a <NUM> system (5GS) and associated with external group ID(s). See Section <NUM>. 3b of the `<NUM> specification. The <NUM> VN Group Data can contain: Domain Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), PDU session type, Application descriptor, and information related with secondary authentication/authorization. An AF configures the <NUM> VN Group Data together with an external group ID, which may be associated with a list of Generic Public Subscription Identifiers (GPSIs), identifying the UEs that belong to the <NUM> VN group. See Section <NUM>. 3c of the `<NUM> specification.

There currently exist certain challenge(s). Consider that Section <NUM>. <NUM> of 3GPP TS <NUM> v17. <NUM> specifies that a Session Management Function (SMF) may receive a list of allowed VLAN tags from a Domain Network Authentication, Authorization, and Accounting (DN-AAA) server, for a maximum of <NUM> VLAN tags, or such tags may be configured locally with allowed VLAN tag values. With local configuration of allowed VLAN tags, the configuration is static and cannot be changed. In the case of the SMF receiving a list of allowed VLAN tags from a DN-AAA, the maximum limit of <NUM> VLAN tags may be a problem, especially when a User Equipment (UE) is connected to a bridging network and more than <NUM> VLANs may be needed.

Further, in cases where the SMF receives a list of allowed VLAN tags from a DN-AAA, for a given UE, learning Medium Access Control (MAC) identities requires flooding to all VLAN tags on the list, even if only a few VLANs are active, because each VLAN tag corresponds to a broadcast domain. Flooding with respect to inactive VLANs wastes network resources, nor is the arrangement fully dynamic. Section <NUM>. <NUM> of the '<NUM> specification stipulates that, for an Ethernet Protocol Data Unit (PDU) Session, the SMF may instruct the involved User Plane Function(s) (UPFs) to classify frames based on VLAN tags, and to add and remove VLAN tags for frames received and sent on N6 or N19 or internal interfaces ("<NUM> VN internal"). However, the criteria and rules are not specified for classifying frames with different VLAN tags and adding and removing VLAN tag.

Similar systems and techniques are disclosed also in <CIT> (<NUM>-<NUM>-<NUM>), or in <NPL>).

Other challenges include the absence of criteria and rules for classifying frames with different VLAN tags and adding and removing VLAN tags. Where and how SMF obtains criteria and rules for VLAN classification, insertion, and deletion remains unsettled. Still further, the relationship between <NUM> VN groups and VLANs is not specified.

Methods and apparatuses for a <NUM> System (5GS) support dynamic and semi-dynamic VLAN configuration for Ethernet bridging services provided by the 5GS. The 5GS includes a node that is configured to receive and store VLAN configuration information for a User Equipment (UE). Particularly, the VLAN configuration information, which comprises a single predefined VLAN ID (VID) or a list of non-predefined VIDs or a single non-predefined VID, may be stored advantageously within <NUM> Virtual Network (VN) Group Data and indicates whether the UE acts as an Ethernet trunk port or access port. With respect to the 5GS establishing or modifying an Ethernet PDU session for the UE, a User Plane Function (UPF) of the 5GS configures Ethernet bridging operations for the UE as an access port or a trunk port, in dependence on the VLAN configuration information stored for the UE.

Certain aspects of the disclosure and corresponding embodiments may provide solutions to the challenges noted above or for other challenges. Among other things, the disclosed techniques provide a method for a 5GS to support Dynamic VLAN configuration for one or more UEs using an Application Function (AF), e.g., using a group management application programming interface (API). One approach disclosed reuses <NUM> VN Group Data as defined in the 3GPP specifications to convey VLAN configuration information for a UE to a <NUM> system via an AF. In such embodiments, the VLAN information is carried inside the <NUM> VN Group Data, which is identified by an External Group ID. In one or more embodiments, both <NUM> VN Group Data and an External Group ID are provided to Unified Data Management / User Data Repository (UDM / UDR) via a Network Exposure Function (NEF). Then, a Session Management Function (SMF) retrieves the VLAN configuration information for a UE and provides it or related control signaling to a User Plane Function (UPF) for VLAN handling. For example, with respect to establishing or modifying an Ethernet PDU session for a UE connected via a <NUM> System (5GS), the VLAN configuration information comprises one or more VLAN IDs (VIDs), indicating the VLAN association(s) of the UE.

Among the various advantages of the disclosed techniques is providing dynamic VLAN configuration from AFs, along with allowing for flexible dynamic reconfiguration, when needed, nor are there any practical limitations on the size of the allowed VLAN list. The allowed VLAN list may be hosted in an AF, a SMF, or a UPF. For a UE, a N6 or N19 interface used in VLAN trunk port mode, the allowed list can be used together with IEEE802. <NUM> Q Multiple VLAN Registration Protocol (MVRP). MVRP enables the 5GS to learn which VLANs are associated with UEs acting as Ethernet trunk ports. In at least one embodiment, considering an allowed VLAN list for a UE-based port allows the 5GS to determine final allowed active VLANs.

Thus, one aspect of the disclosed techniques is a binding of VLAN groups (e.g., as identified by VIDs) to a <NUM> VN Group, for a port working in access mode. For trunk ports, a two-step approach is taken. First, a pre-defined <NUM> VN Group (optionally with a pre-defined VID for the trunk group) is provided via group management API, regardless of how many VLANs are actively used on the port. Second, a SMF or UPF of the 5GS uses the pre-defined group ID or pre-defined VID as an indication of whether the MVRP process is needed. Based on the MVRP results, a list of VLANs that are learned by MVRP will be used for VLAN operations (instead of the pre-defined VID). Another aspect is reusing <NUM> VN Group Data to convey VLAN configuration information for a UE into the <NUM> system, so that the dynamic or semi-dynamic VLAN configuration of the 5GS can be carried out by exploiting underlying 3GPP methods.

One embodiment comprises a method performed by one or more network functions (NFs) of a 5GS that provides Ethernet bridging operations for UEs acting as Ethernet access ports or Ethernet trunk ports. The method comprises receiving VLAN configuration information for a UE, where the VLAN configuration information is received from an AF and comprises a predefined VID or a list of non-predefined VIDs if the UE is an Ethernet trunk port, or comprises a single non-predefined VID if the UE is an Ethernet access port. The method further includes storing the VLAN configuration data, for subsequent use by the 5GS in configuring Ethernet bridging operations with respect to the UE.

Another embodiment comprises a 5GS that is configured to provide Ethernet bridging operations for UEs acting as Ethernet access ports or Ethernet trunk ports. The 5GS comprises a network node that includes communication interface circuitry and processing circuitry operatively associated with the communication interface circuitry. The processing circuitry is configured to operate the network node as a NEF that is configured to receive VLAN configuration information for a UE from an AF and store the VLAN configuration information for subsequent use by the 5GS in configuring Ethernet bridging operations with respect to the UE. The VLAN configuration information comprises a predefined VID or a list of non-predefined VIDs if the UE is an Ethernet trunk port, or comprises a single non-predefined VID if the UE is an Ethernet access port.

In one or more embodiments, the VLAN configuration information for a UE is advantageously stored in <NUM> VN Group Data. Further, in one or more embodiments, using the VLAN configuration information stored for a UE when the 5GS is establishing or modifying an Ethernet PDU session for the UE comprises: in a case where the VLAN configuration information for the UE comprises a single non-predefined VID, configuring Ethernet bridging operations based on the UE being an Ethernet access port associated with a single VLAN identified by the single non-predefined VID; in a case where the VLAN configuration information for the UE comprises a list of non-predefined VIDs, configuring Ethernet bridging operations based on the UE being an Ethernet trunk port associated with multiple VLANs respectively identified by the list of non-predefined VIDs; or, in a case where the VLAN configuration information for the UE comprises a single predefined VID, initiating Multiple VLAN Registration Protocol (MVRP) for the UE, to learn VIDs of VLANs associated with the UE and configuring Ethernet bridging operations based on the UE being an Ethernet trunk port associated with multiple VLANs respectively identified by the learned VIDs.

Running MVRP to learn the VIDs associated with a trunk-port UE may be regarded as performing dynamic VLAN configuration, while configuring bridging operations for a trunk-port UE according to VIDs listed in VLAN configuration stored for the UE may be regarded as performing semi-dynamic VLAN configuration. Related example details include, in cases where the UE acts as an Ethernet trunk port and a list of multiple VLANs are associated with the trunk port, either based on being identified in the VLAN configuration information or being learned via MVRP, a Session Management Function (SMF) or User Plane Function (UPF) of the 5GS may filter the list, e.g., using whitelisting or blacklisting, to determine a filtered list of VLANs that are allowed for the UE and configure bridging operations for the UE accordingly.

Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Consider an example use case in association with <FIG>, where there are three Virtual Local Area Network (VLAN) Identifiers (VIDs), representing three different VLANs, denoted as VLAN100, VLAN200, and VLAN300. A number of end stations (ESs) <NUM> operate in each of the VLANs, where each ES is some form of computing device that supports Ethernet communications. Again, merely as an example for discussion, ES <NUM>-<NUM>, ES <NUM>-<NUM>, ES <NUM>-<NUM>, and ES <NUM>-<NUM> belong to VLAN100, ES <NUM>-<NUM>, ES <NUM>-<NUM>, ES <NUM>-<NUM>, and ES <NUM>-<NUM> belong to VLAN200, and ES <NUM>-<NUM> and <NUM>-<NUM> belong to VLAN300.

ES <NUM>-<NUM> is communicatively connected via a UE <NUM>-<NUM>, ES <NUM>-<NUM> is communicatively connected via a UE <NUM>-<NUM>, ES <NUM>-<NUM> is communicatively connected via a UE <NUM>-<NUM>, ES <NUM>-<NUM> is communicatively connected via a UE <NUM>-<NUM>, ESs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> are communicatively connected via an Ethernet bridge <NUM>-<NUM>, which in turn relies on a UE <NUM>-<NUM> for its communication link, and ESs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> are communicatively connected via an Ethernet bridge <NUM>-<NUM>, which couples to a Fifth Generation System (5GS) <NUM> via a N6 interface. ESs <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> coupled to the 5GS <NUM> via their respective UEs <NUM>, as does the Ethernet bridge <NUM>-<NUM>.

The UEs <NUM> may be embedded in, integrated with, or otherwise associated with their respective ESs <NUM>, and they provide the radio connectivity for wirelessly connecting to the 5GS <NUM>, with the 5GS <NUM> advantageously providing bridging services for the Ethernet traffic flowing in the respective VLANs.

While the Radio Access Network (RAN) portion of the 5GS <NUM> is not shown in <FIG>, one or more radio access nodes, e.g., gNBs, provide the air interface supporting the wireless connections between the UEs <NUM> and the 5GS <NUM>, which comprises a telecommunication network operating according to the <NUM> specifications developed by the 3GPP. With respect to the bridging services and the configuration thereof, Network Functions (NFs) of interest in the 5GS <NUM> include a User Plane Function (UPF) <NUM>, which includes an Ethernet bridging function <NUM>. Additional NFs include a Session Management Function (SMF) <NUM>, a User Data Management (UDM) / User Data Repository (UDR) <NUM>, a Network Exposure Function (NEF) <NUM>, and an Application Function (AF) <NUM>. Any one or more of these NFs may be referred to as NFs <NUM>.

Approaches disclosed herein provide for dynamic or semi-dynamic configuration of VLAN bridges logically implemented in the 5GS <NUM> and, particularly, provide automated mechanisms for configuring the VID(s) used for processing Ethernet traffic associated with a UE <NUM> operating as an Ethernet access port or as an Ethernet trunk port. In one or more embodiments, the NEF <NUM> provides a VLAN group management Application Programming interface (API) that allows the AF <NUM> to input VLAN configuration information for individual UEs <NUM>, where the VLAN configuration information for a given UE <NUM> comprises one or more VIDs. If the UE <NUM> operates as an Ethernet access port-see the UE <NUM>-<NUM> embedded in the ES <NUM>-<NUM>, for example-the VID is the actual VID of the associated VLAN. However, if the UE <NUM> operates as an Ethernet trunk port-see the UE <NUM>-<NUM> associated with the Ethernet bridge <NUM>-<NUM>, for example-the VLAN configuration information comprises a VID that is a special value that is recognized within the 5GS <NUM> as indicating the trunk port operation, or the VLAN configuration information comprises a list of VIDs, identifying the VLANs that are associated with the trunk port.

Advantageously, when establishing or modifying an Ethernet Protocol Data Unit (PDU) session for a UE <NUM>, the 5GS <NUM> determines whether the UE <NUM> acts as an Ethernet access port or as an Ethernet trunk port. In the former case, the 5GS <NUM> performs Ethernet bridging operations for the UE <NUM> using the VID stored for the UE <NUM>. In the latter case, if the VLAN configuration information stored for the UE <NUM> comprises a list of VIDs, the 5GS <NUM> performs a semi-dynamic VLAN configuration, in which Ethernet bridging operations are configured for the UE <NUM> according to some or all of the listed VIDs. If the VLAN configuration information stored for the UE <NUM> comprises the aforementioned special value-i.e., a predefined VID-the 5GS <NUM> triggers Multiple VLAN Registration Protocol (MVRP) for the UE <NUM>, which allows the 5GS <NUM> to discover the identities of the VLANs associated with the UE <NUM> and correspondingly configure the Ethernet bridging operations provided by the 5GS <NUM> for the UE <NUM>.

In one or more embodiments, the 5GS <NUM> advantageously reuses or otherwise exploits the <NUM> Virtual Network (VN) Group Data defined by the Third Generation Partnership Project (3GPP) specifications as the mechanism for carrying and storing VLAN configuration information for individual UEs <NUM>, with, as noted, such information indicating access-port or trunk-port operation of individual UEs <NUM> and, thus, providing a basis for determining whether MVRP should be triggered for a given UE <NUM> when the 5GS <NUM> establishes or modifies an Ethernet PDU session of the UE <NUM>.

According to one or more embodiments disclosed herein, a NEF <NUM> of the 5GS <NUM> is configured to receives VLAN configuration information for a UE <NUM> from an Application Function (AF) <NUM> and store the VLAN configuration for use by the 5GS <NUM> when establishing or modifying an Ethernet PDU session for the UE <NUM>. For example, the NEF <NUM> stores the VLAN configuration information by sending signaling to a UDM/UDR <NUM> of the 5GS <NUM>, where the signaling indicates the VLAN configuration information. Subsequent use of the VLAN configuration information comprises, for example, a SMF <NUM> of the 5GS <NUM> retrieving the VLAN configuration from the UDM/UDR <NUM> and passing it or related control signaling along to a UPF <NUM>, for use in configuring the Ethernet bridging operations to be performed by the 5GS <NUM> with respect to the UE <NUM>.

For example, the UPF <NUM> operates as follows: in a case where the VLAN configuration information for the UE <NUM> comprises a single non-predefined VID, the UPF <NUM> configures Ethernet bridging operations based on the UE <NUM> being an Ethernet access port associated with a single VLAN identified by the single non-predefined VID; or, in a case where the VLAN configuration information for the UE <NUM> comprises a list of non-predefined VIDs, the UPF <NUM> configures Ethernet bridging operations based on the UE <NUM> being an Ethernet trunk port associated with multiple VLANs respectively identified by the list of non-predefined VIDs; or, in a case where the VLAN configuration information for the UE <NUM> comprises a single predefined VID, the UPF <NUM> initiates MVRP for the UE <NUM>, to learn VIDs of VLANs associated with the UE <NUM> and configures Ethernet bridging operations based on the UE <NUM> being an Ethernet trunk port associated with multiple VLANs respectively identified by the learned VIDs.

A proposed technique of obtaining VLAN configuration information for individual UEs <NUM> makes use of an Application Programming Interface (API) provided by a NEF <NUM> of the 5GS <NUM>, by which the NEF <NUM> enables an Application Function (AF) <NUM> to enter <NUM> VN Group Data that includes the VLAN configuration information. Example details on the conventional contents and use of <NUM> VN Group Data appear in the 3GPP Technical Specifications (TSs) <NUM> v17. <NUM> and <NUM> v17. As explained in the '<NUM> specification, the term "<NUM> VN Group" refers to a set of UEs using private communications for <NUM> LAN-type service. However, such group operations are tied to the <NUM> "User Plane" (UP) and Ethernet-based VLANs are defined outside of the <NUM> UP; thus, use of <NUM> VN Group Data to carry VIDs and, particularly, to provide a basis for conditional triggering of MVRP for Ethernet UEs <NUM> represents an advantageous reuse of <NUM> VN Group Data.

The VLAN related functions described herein can be divided in two parts: one part relates to NEF/AF/UDM/UDR operations and is shown as "VLAN configuration Part <NUM>" in <FIG>. The other part is shown as "VLAN configuration Part <NUM>" in <FIG> and involves SMF/UPF operations.

The VLAN configuration information provided by an AF <NUM> (i.e., the information associated with VLAN configuration Part <NUM>), needs to be passed to the 5GS <NUM>, so that the 5GS <NUM> handles the VLANs properly. One aspect of providing for proper VLAN handling by the 5GS <NUM> is based on using <NUM> VN Group Data (<NUM> VN configuration parameters) to carry VLAN information into the 5GS <NUM>. There are several options to convey the VLAN configuration information from the operations involved in the "VLAN config. Part <NUM>," with example details given below.

A UE <NUM> to be used in support of VLAN-based communications carried by the 5GS <NUM> is assigned to a group depending on the VLAN usage. For each group, there is a unique "external group ID" which is associated with a set of <NUM> VN Group Data.

In the UDM/UDR <NUM>, the UE subscription information and local identifiers are stored and managed. The <NUM> VN Group Data inside the UDM/UDR <NUM> can be provisioned through an AF <NUM> and a NEF <NUM> and stored by the NEF <NUM> in the UDM/UDR <NUM>. Based on such information being stored at the UDM/UDR <NUM>, a SMF <NUM> in the 5GS <NUM> that is involved with supporting an Ethernet PDU session of a UE <NUM> finds out if the PDU session is related to a VLAN group or a trunk group, based on the VLAN configuration information stored for the UE <NUM> in corresponding <NUM> VN Group Data. For a UE belonging to one dedicated VLAN group (i.e., the UE acts as an access port of the <NUM> bridge), the indicated VID value is directly used for VLAN operations such as tagging and filtering. For a UE acting as an Ethernet trunk port, the indicated VID has a special value-i.e., it comprises a predefined VID-and that triggers the SMF <NUM> and/or UPF <NUM> to initiate MVRP for the UE, to learn the VLANs with which the UE is associated. That is, the SMF can either instruct the UPF regarding VLAN operation accordingly, or the SMF can pass the VLAN ID value to the UPF, with the UPF then performing VLAN operations.

For a UE in trunk port mode, there can be two options for trunk port configuration: dynamic trunk configuration using MVRP, and semi-dynamic trunk configuration from the AF with group management.

With dynamic trunk configuration using MVRP, the VLAN setting for a trunk port at VLAN config. Part <NUM> can be either a predefined VLAN value (e.g., <NUM>) or empty (no VLAN value is assigned). A group can be created for the UEs in trunk mode, a pre-defined "external group ID" can be used to represent the "trunk group". The corresponding <NUM> VN Group Data can also contain the "pre-defined VLAN ID" for trunk usage.

Based on UDR/UDM information, a SMF may determine that the UE provides trunk-port operation. Either the SMF understands that the VID value stored for the UE is a trunk-port indication, and it correspondingly instructs the involved UPF to perform MVRP, or the SMF passes the predefined VLAN ID to the UPF. In this latter case, the UPF has the logic to understand that the predefined VLAN ID is an indication of trunk port operation, and, therefore, the UPF performs MVRP operation. An allowed VLAN list can be also provided in the <NUM> VN Group Data, for example, if certain VLANs are reserved for other purposes, and so cannot be used, or for supporting secondary authentication/authorization purposes. The list can be provisioned as part of <NUM> VN Group Data.

After the VLAN MVRP and filtering based on an "allowed VLAN list", an updated VLAN list for a trunk port can be decided, and the UPF can perform VLAN operations according to updated VLAN list.

Now consider semi-dynamic trunk configuration from AF with group management. Assume the network administrator knows a list of VLANs that are active or will be active for a given trunk port (e.g., a UE operating in trunk mode). Alternatively, another external VLAN configuration server knows the list. In either case, the VLAN ID list can be directly provisioned at the AF, with group management API. Optionally, the trunk VLAN list can be future filtered by checking if any VLAN on the list is on the blacklist of an "allowed VLAN list," e.g., for secondary authentication/authorization purposes.

The VLAN ID list can be carried inside <NUM> VN group configuration data associated with the trunk group, and then provisioned in the UDM/UDR.

In an example considered in the context of <FIG>, the administrator knows VLAN ID#<NUM>, #<NUM>, #<NUM> will be used in connection with UE5. Therefore, the VLAN list contains #<NUM>, <NUM>, <NUM>, and can be provided as part of a data set comprising a list of VIDs, in association with VLAN config. Part <NUM>.

The VLAN list for UE5 is provisioned to the UDM/UDR, and the SMF retrieves the trunk VLAN list associated with the UE <NUM>-<NUM>. The SMF can pass the VLAN ID list to a UPF, and the UPF can then perform VLAN filtering and forwarding operations, which are more generally referred to as VLAN operations. In contrast to the option of using MVRP, another option is to create multiple trunk groups, one for each trunk port, as another UE acting as trunk port may have a completely different trunk VLAN list. For example, if a UE A acting as trunk port has a list of VLAN <NUM>, <NUM>, and <NUM>, and another UE B acting as trunk port has a list of <NUM>, <NUM>, then two trunk groups (trunk group A and trunk group B) may need to be created. The active VLAN list of UE A can be carried in the group data of trunk group A, and the active VLAN list of UE B can be carried in the group data of trunk group B. This approach does not use <NUM> VN Group Data for traffic forwarding; rather, it only uses the <NUM> VN Group Data to carry the VLAN ID information. , Therefore, even UEs that belong to different trunk groups may still communicate. In this case the traffic forwarding is not controlled by the SMF based on the <NUM> VN group communication. Instead, communication between different trunk ports is based on the trunk VLAN list. For example, if a UE A acting as trunk port has a list of VLAN <NUM>, <NUM>,<NUM>, the other UE B acting as trunk port has a list of <NUM>, <NUM>, then those two UEs can communicate using VLAN <NUM> and <NUM>.

The N6 and N19 interfaces normally are used for Ethernet trunk port mode. Therefore, the VLAN configurations for these interfaces can be handled the same way as done for UEs that act as virtual trunk ports.

Several different approaches to using <NUM> VN Group Data to carry VLAN configuration information-i.e., a VID-for a UE <NUM> are possible, including modifying the data structure to include a dedicated information field for carrying VLAN configuration information, or, alternatively, "embedding" the VLAN configuration information in a preexisting (currently defined) information field. For example, the VLAN configuration information may be embedded in any one of the following: the Application Descriptor field, the Domain Network Name (DNN) field, or the Single Network Slice Selection Assistance Information (S-NSSAI) field.

The below table illustrates embedded VLAN configuration information as part of the DNN field, where "GPSI" denotes Generic Public Subscription Identifier:.

In more detail, the above table illustrates an example of using the DNN field defined in the <NUM> VN Group Data to carry the VLAN configuration information that received by a NEF <NUM> from an AF <NUM>, for storage in the 5GS <NUM>. Note that the "Type" and "VLAN ID" columns in the above table are not part of the <NUM> VN Group Data set passed from the AF into the 5GS.

One approach is defining the VLAN group of a given network using a specific prefix of the DNN. That is, the <NUM> VN Group Data in an example case links the external group IDs (used for VLAN creation) to VIDs by embedding or incorporating VID information into the DNN data field. For example, for VID <NUM> of domain. com (as the DNN), an example DNN is vlan100. This approach effectively puts the VLAN indication in the DNN, which provides for proper configuration and operation of the 5GS <NUM>, for handling VLAN traffic.

A UE in access port mode (e.g., UE <NUM>-<NUM> or UE <NUM>-<NUM>) has DNN information in the <NUM> VN Group Data, the prefix of the DNN (e.g., "vlan100" in the "vlan100. com") indicates which VLAN the UE belongs to.

For a UE in trunk port mode, the VLAN setting in the Part <NUM> VLAN configuration can be a predefined VID (e.g., the value <NUM> or an empty or null value). A group can be created for the UEs in trunk mode, a pre-defined "external group ID" can be used to represent the "trunk group. " The corresponding <NUM> VN data are associated to the "external group id" of the trunk group, where the DNN prefix can indicate "vlan4094".

The below table illustrates the example of embedding the VLAN configuration information in the S-NSSAI field of <NUM> VN Group Data:.

With the approach represented in the table immediately above, the S-NSSAI field of the <NUM> VN Group Data is used to carry the VLAN configuration information, e.g., from an AF into a UDM / UDR of a 5GS for use by a SMF and/or UPF of the 5GS for performing VLAN operations in support of the 5GS implementing a logical VLAN bridge.

Currently, the 3GPP-defined S-NSSAI may have both a slice service type SST field and a slice differentiator field, corresponding to a S-NSSAI length of <NUM> bits. The network operator associated with the 5GS can predefine the relationship between S-NSSAIs and VLANs in the UDM/UDR, and a SMF in the 5GS uses that information to derive the VLAN ID information and pass it to a UPF in support of providing VLAN operations in association with a UE that belongs to a VLAN.

The below table illustrates yet another variation or alternative embodiment, wherein VLAN information is embedded in the Application Descriptor field defined in <NUM> VN Group Data.

Thus, as an alternative to using the domain-name or network slice fields in the <NUM> VN Group Data to indicate VLAN information, the table immediately above indicates that VLAN configuration information may be carried in the Application Descriptor field of the <NUM> VN Group Data. With this approach, the AF uses the Application Descriptor filed to pass VLAN configuration information from the AF to the 5GS. The application descriptor for each group indicates the VLAN ID information and may be used to build URSP (UE route selection policy) sent to the group members.

The below table illustrates yet another approach where VLAN IDs are included as individual elements inside <NUM> VN Group Data-i.e., the <NUM> VN Group Data is extended with a dedicated information field to carry VLAN configuration information. As currently defined, the data structure for holding 3GPP <NUM> VN Group Data does not provide for VLAN IDs as separate elements, and one approach disclosed is based on adding such a field to the data structure. With this approach, the <NUM> VN Group Data provides VLAN provisioning information for storage in the UDM / UDR, which can then be retrieved by a SMF of the 5GS and used by the SMF or the involved UPF to carry out VLAN-related operations.

The "Type" column shown above is included as an individual data elements or fields of <NUM> VN Group Data, in one or more embodiments.

With the above examples in mind, related methods or operations according to one embodiment disclosed herein includes an AF embedding VLAN configuration in the defined data structure used in 3GPP to carry <NUM> VN Group Data. As a particular example, the <NUM> VN Group Data structure links group IDs with VLANs, and includes, where appropriate, values or indicators that trigger MVRP operations in the 5GS, for dynamic configuration of a logical VLAN bridge implemented in a UPF of the 5GS. The VLAN configuration information may further include an "allowed VLAN list" that can be used for secondary authentication in the 5GS, e.g., info to the UPF for whitelisting / blacklisting of VLANs.

A network administrator sets up different VLANs for different groupings of end stations, e.g., for different groupings of computers, sensors, controllers, or other nodes that include or are coupled to UEs that communicatively connect the end stations to the 5GS. The administrator assigns respective VLAN IDs to the different groupings, to restrict which end stations are able to communicate with one another.

Consider a case where the administrator knows that a given UE, say UE <NUM>-<NUM>, is a trunk port and knows which VLANs will use the trunk port. In such cases, the administrator may input such information as part of the VLAN configuration information and the 5GS does not need to invoke MVRP later during operation.

However, in another case and with reference back to <FIG>, the administrator knows that UE <NUM>-<NUM> is a trunk port but does not know the associated VLANs that use the trunk. In this case, the VLAN ID linked to the <NUM> VN Group may be set to a predefined special value or a default value that is operative to trigger the 5GS to perform MVRP, e.g., a UPF supporting UE#<NUM> runs MVRP to discover which VLANs are on the trunk port. Logic to trigger MVRP by the UPF may reside in the SMF. As such, not only do the techniques disclosed herein provide an efficient mechanism to feed VLAN configuration information into a 5GS, e.g., through the use of an AF group management API, the disclosed techniques provide for automatic triggering of MVRP, and corresponding dynamic configuration of trunk ports supported by a logical VLAN bridge implemented in a UPF of the 5GS.

Note that with triggering of MVRP and corresponding dynamic configuration in the 5GS, all trunk ports represented in the VLAN configuration fed into the 5GS via the AF may use the same group identifier, because the 5GS dynamically determines which VLANs are on which trunk ports. In instances where the administrator preconfigures the VLAN IDs that are on respective trunk ports, such preconfigured trunk ports will have different group names in the VLAN configuration data that is set up in the VLAN config. Part <NUM>, shown in the earlier 5GS diagram included herein.

One advantage with the disclosed techniques is that the group names can be arbitrary and the VLAN ID information (known or unknown) is reflected elsewhere in the <NUM> VN Group Data set. For example, the <NUM> VN Group Data uses the DNN data field to link VLAN ID with group name. Alternatively, the group names can be linked to VLAN IDs using the S-NSSAI data field or Application Descriptor data field.

<FIG> depicts a network node ("NW NODE") <NUM> that implements one or more Network Functions (NFs) <NUM> in or associated with a 5GS <NUM>. For example, the network node <NUM> implements any one or more of a SMF <NUM>, a UPF <NUM>, a NEF <NUM>, a UDM/UDR <NUM>, or an AF <NUM>. There may multiple computer servers or other computing platforms as example network nodes <NUM>, each implementing one or of the NFs <NUM> depicted in <FIG>. As such, any of the nodes/functions in <FIG> depicting dynamic VLAN configuration in a 5GS <NUM> may be implemented according to the example node details depicted in <FIG>. Of course, the particular NF <NUM> or functionality implemented by the network node <NUM> may be determined according to the specifics of the computer program instructions stored in and executed by the processing circuitry of the node.

In more detail, an example network node <NUM> comprises communication interface circuitry <NUM>, including transmitter circuitry (TX) <NUM> and receiver circuitry (RX) <NUM>, that is configured to communicatively couple the network node <NUM> to one or more other nodes in the involved telecommunication network. Such circuitry comprises the physical-medium interface circuitry along with protocol processing-e.g., for implementation of one or more protocols used in or by the telecommunication network for inter-node communications. Non-limiting examples include Ethernet-based interfaces or other data network interfaces. Particulars of the communication interface circuitry depend upon the NF(s) implemented by the network node and the manner in which the network node <NUM> is implemented, e.g., as a standalone server or as virtualized processing and communication circuitry within a cloud computing center.

The processing circuitry <NUM> of the depicted network node <NUM> comprises fixed circuitry or programmatically-configured circuitry or a mix of fixed and programmatically-configured circuitry. Example implementations of the processing circuitry include any one or more of microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), or other digital processing circuitry. In at least one embodiment, one or more microprocessors or other digital processors are specially adapted to operate as the depicted processing circuitry, based on executing computer program instructions stored in the network node.

To that end, in one or more embodiments, storage <NUM> included in the network node <NUM> comprises one or more types of computer readable media that provide non-transitory storage of computer program instructions in one or more computer programs ("CP(s)") <NUM>. Here, "non-transitory" does not necessarily mean permanent or unchanging but does connote at least some persistence, such as temporary storage of computer program instructions in working memory for program execution by one or more microprocessors or other digital processors. The storage <NUM>, which may store data <NUM> (provisioned or working), may include a mix of memory or storage circuits or devices, such as volatile memory for runtime operations-program execution-and non-volatile memory or storage for retention of program instructions and/or data, such as provisioning information, VLAN configuration data, subscriber data, etc. Non-limiting examples of storage include any one or more of SRAM, DRAM, FLASH, EEPROM, Solid State Disk (SSD), and magnetic storage.

In one or more embodiments, a network node <NUM>, or at least the NF(s) provided via the network node <NUM>, is implemented as a number of processing modules or units <NUM>, such as shown in <FIG>. In at least one embodiment, the processing modules/units <NUM> can be understood as functional or logical elements realized via programmatic configuration of underlying computer circuitry.

With the above example details in mind, a 5GS <NUM> according to an example embodiment is configured to provide Ethernet bridging operations for UEs <NUM> acting as Ethernet access ports or Ethernet trunk ports. The 5GS <NUM> comprises a network node <NUM> that includes communication interface circuitry <NUM> and processing circuitry <NUM> that is operatively associated with the communication interface circuitry <NUM> and configured to operate the network node <NUM> as a NEF <NUM>. Here, the NEF <NUM> is configured to: (a) include VLAN configuration information in <NUM> VN Group Data. The VLAN configuration information is received by the NEF <NUM> from an AF <NUM> and, for a UE <NUM> associated with the <NUM> VN Group Data, comprises a predefined VID if the UE <NUM> is an Ethernet trunk port, and comprises a non-predefined VID if the UE <NUM> is an Ethernet access port. A "non-predefined VID" shall be understood as an actual value that identifies the VLAN association of the UE <NUM>, whereas as "predefined VID" shall be understood as a special value, such a pre-agreed value or null value, that indicates trunk operation rather than indicating the VID(s) of actual VLANs.

The NEF <NUM> is further configured to store the <NUM> VN Group Data, for subsequent use by the 5GS <NUM> in determining whether to initiate MVRP for the UE <NUM> to learn VIDs of VLANs associated with the UE <NUM>, when establishing or modifying an Ethernet PDU session for the UE <NUM>.

In one embodiment, a data structure containing the <NUM> VN Group Data is extended to include a VID field, and the NEF <NUM> is configured to include the VLAN configuration information in the <NUM> VN Group Data by including the VLAN configuration information in the VID field.

The NEF <NUM> in another embodiment is configured to include the VLAN configuration information in the <NUM> VN Group Data by embedding the VLAN configuration information in a Domain Network Name (DNN) field that is comprised in the <NUM> VN Group Data according to 3GPP specifications. See 3GPP TSs <NUM> v17. <NUM> and <NUM> v17.

The NEF <NUM> in another embodiment is configured to include the VLAN configuration information in the <NUM> VN Group Data by embedding the VLAN configuration information in an Application Descriptor field that is comprised in the <NUM> VN Group Data according to the 3GPP specifications.

The NEF <NUM> in another embodiment is configured to include the VLAN configuration information in the <NUM> VN Group Data by embedding the VLAN configuration information in a S-NSSAI field that is comprised in the <NUM> VN Group Data according to the 3GPP specifications.

To receive the VLAN configuration information from an AF <NUM>, the NEF <NUM> in one or more embodiments is configured to provide a configuration API, which enables the AF <NUM> to provision the <NUM> VN Group Data, including the VLAN configuration information.

In one or more embodiments, the NEF <NUM> is configured to recognize the VLAN configuration information, as received from the AF <NUM> as part of provisioning the <NUM> VN Group Data and place the VLAN configuration information in a dedicated data field added to the <NUM> VN Group Data for carrying the VLAN configuration information. In other embodiments, such as where the VLAN configuration information is embedded with data comprised in a preexisting field of the data structure that carriers the <NUM> VN Group Data, the VLAN configuration information is transparent to the NEF <NUM>. However, even in such cases, the NEF <NUM> cooperates with the AF <NUM> for provisioning of the VLAN configuration information as part of the <NUM> VN Group Data.

The NEF <NUM> in an example embodiment is configured to store the <NUM> VN Group Data for subsequent use by the 5GS <NUM> by sending signaling indicating the <NUM> VN Group Data to another node <NUM> of the 5GS <NUM> operating as a UDM/UDR <NUM>. That is, saying that the NEF <NUM> is configured to "store" the <NUM> VN Group Data may mean that the NEF <NUM> initiates storage, such as by sending the <NUM> VN Group Data to another node responsible for holding the <NUM> VN Group Data.

The 5GS <NUM> in one or more embodiments further comprises a SMF <NUM> that is configured to subsequently retrieve the VLAN configuration information from the stored <NUM> VN Group Data in conjunction with the 5GS <NUM> establishing or modifying an Ethernet PDU session for the UE <NUM>, and perform one of the following operations: (a) determine from the VLAN configuration information that the UE <NUM> acts as an Ethernet trunk point and send signaling to a UPF <NUM> of the 5GS <NUM>, indicating the trunk port determination; or (b) send the VLAN configuration information to the UPF <NUM>, for determination by the UPF <NUM> as to whether the UE <NUM> acts as an Ethernet trunk port or an Ethernet access port.

In at least one such embodiment, the UPF <NUM> of the 5GS <NUM> is configured to, responsive to the determination that the UE <NUM> acts as an Ethernet trunk port, initiate MVRP for the UE <NUM>, to learn VIDs of VLANs associated with the UE <NUM>. The UPF <NUM> in an example embodiment is configured to subsequently perform corresponding Ethernet bridging operations with respect to the Ethernet PDU session of the UE <NUM>, according to the learned VIDs.

<FIG> illustrates a method <NUM> performed by one or more NFs <NUM> of a 5GS <NUM> that provides Ethernet bridging operations for UEs <NUM> acting as Ethernet access ports or Ethernet trunk ports. The method <NUM> comprises: (a) receiving (Block <NUM>) VLAN configuration information for a UE <NUM> from an AF <NUM>, and (b) storing (Block <NUM>) the VLAN configuration information, for subsequent use by the 5GS <NUM> when establishing or modifying an Ethernet PDU session for the UE <NUM>. Receiving the VLAN configuration information comprises, for example, receiving the VLAN configuration information as part of or for inclusion in <NUM> VN Group Data, e.g., a NEF <NUM> of the 5GS <NUM> provides an API that enables the AF <NUM> to input the VLAN configuration into the <NUM> VN Group Data. In one or more embodiments, the VLAN configuration information comprises one of: a special value-i.e., a predefined VID-that is used to trigger the 5GS <NUM> to initiate MVRP for the UE <NUM>, to learn the VLANs associated with the UE <NUM> for trunk port operation; or a list of non-predefined VIDs that identify the VLANs associated with the UE <NUM> for trunk port operation; or a single non-predefined VID that identifies the VLAN associated with the UE <NUM> for access port operation.

<FIG> illustrates a method <NUM> by a collection of NFs <NUM> comprised in a 5GS <NUM>, for dynamic VLAN configuration, which can be understood as a collection of operations performed by different NFs <NUM>, according to at least one embodiment of the method <NUM>.

The method <NUM> comprises a NEF <NUM> providing an AF <NUM> with the ability to configured dynamic VLAN configuration information for UEs <NUM>, e.g., by providing an API that enables the AF <NUM> to add VLAN configuration for UEs <NUM> to <NUM> VN Group Data (Block <NUM>). In this context, the AF <NUM> assigns single non-predefined VIDs for UEs <NUM> acting as Ethernet access ports ("virtual Access Ports" or "vAPs") for single VLANs. For a UE <NUM> acting as a trunk port for two or more VLANs, the AF <NUM> assigns a predefined VID or a list of non-predefined VIDs that identify the VLANs associated with trunk port operation of the UE <NUM>. Assigning the non-predefined VID will cause the 5GS <NUM> to later trigger MVRP for the UE <NUM>, to learn the VLANs associated with the UE <NUM>. The method <NUM> further includes the NEF <NUM> providing (Block <NUM>) the VLAN configuration information to a UDM/UDR <NUM>.

Still further, the method <NUM> includes the UDM/UDR <NUM> performing (Block <NUM>) GPSI to Subscription Permanent Identifier (SUPI) resolution (to associate VLAN information with the SUPI(s)), with respect to UEs <NUM> represented in the VLAN configuration information included in <NUM> VN Group Data stored in the UDM/UDR <NUM>, and an SFM <NUM> determining (retrieving) the VLAN configuration information for a given UE <NUM>, when establishing or modifying an Ethernet PDU session for the UE <NUM>. Correspondingly, the method <NUM> includes the UPF <NUM> performing (Block <NUM>) VLAN configuration for the UE <NUM>, in dependence on the VLAN configuration information retrieved for the UE <NUM>.

To consider further example embodiments, <FIG> shows an example of a communication system QQ100 in accordance with some embodiments. The communication system QQ100 can be understood as a depiction of a 5GS that is configured to <NUM> VN Group Data to carry VLAN configuration information for a UE <NUM>, and further configured to use that information to trigger MVRP for the UE <NUM> on a conditional basis, when establishing or modifying an Ethernet PDU session for the UE <NUM>.

In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar <NUM>rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.

In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. The core network <NUM> includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108.

The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102 and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service.

As a whole, the communication system QQ100 of Figure QQ1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable <NUM>, <NUM>, <NUM>, <NUM> standards, or any applicable future generation standard (e.g., <NUM>); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards (Wi-Fi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network <NUM> and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network <NUM> and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

In one or more embodiments, the telecommunication network QQ102 provides one or more logical bridges for use in VLAN-based communications. For example, one or more network nodes/NFs implemented in the core network QQ106 and/or elsewhere within the network QQ102 implement the dynamic VLAN configuration techniques disclosed herein.

<FIG> shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. In an example context, the UE QQ200 operates either as an access port for a single VLAN or as a trunk port for multiple VLANs and provides connectivity for Ethernet traffic into and out of a 5GS <NUM> acting as an Ethernet bridge for such traffic.

Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof.

The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. An input device may allow a user to capture information into the UE QQ200.

In some embodiments, the power source QQ208 is structured as a battery or battery pack. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. ' The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE <NUM>, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), OUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node.

in response to the received wireless input the states of the actuator, the motor, or the switch may change.

A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in <FIG>.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. As one particular example, the UE may implement the 3GPP NB-loT standard.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

<FIG> shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.

The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

The memory QQ304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

The communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302.

In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node.

The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.

Embodiments of the network node QQ300 may include additional components beyond those shown in <FIG> for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

<FIG> is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of <FIG>, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as <FIG>, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400, or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset, or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G. The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc..

<FIG> is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. in the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.

Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways.

In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

<FIG> shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of <FIG> and/or UE QQ200 of <FIG>), network node (such as network node QQ110a of <FIG> and/or network node QQ300 of <FIG>), and host (such as host QQ116 of <FIG> and/or host QQ400 of <FIG>) discussed in the preceding paragraphs will now be described with reference to <FIG>.

Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network <NUM> of <FIG>) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.

The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app" that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve VLAN operations for RAN-based VLANs and thereby provide benefits such as dynamic VLAN configuration in 5GS.

In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc..

It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information, or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Claim 1:
A method (<NUM>) performed by one or more network functions (NFs) (<NUM>) of a Fifth Generation System (5GS) (<NUM>) that provides Ethernet bridging operations for User Equipments (UEs) (<NUM>) acting as Ethernet access ports or Ethernet trunk ports, the method (<NUM>) comprising the steps of:
receiving (<NUM>) Virtual Local Area Network (VLAN) configuration information for a User Equipment (UE) (<NUM>) from an Application Function (AF) (<NUM>), the VLAN configuration information for the UE (<NUM>) comprising a predefined VLAN ID (VID) or a list of non-predefined VIDs if the UE (<NUM>) is an Ethernet trunk port, or comprising a single non-predefined VID if the UE (<NUM>) is an Ethernet access port; and
storing (<NUM>) the VLAN configuration information, for subsequent use by the 5GS (<NUM>) in configuring Ethernet bridging operations with respect to the UE (<NUM>), when establishing or modifying an Ethernet Protocol Data Unit (PDU) session for the UE (<NUM>).