Patent Description:
The present disclosure relates generally to low latency wireless communications.

In computer networking, a wireless Access Point (AP) is a networking hardware device that allows a wireless compliant client device to connect to a wired network. The AP usually connects to a router (directly or indirectly via a wired network) as a standalone device, but it can also be an integral component of the router itself. Several APs may also work in coordination, either through direct wired or wireless connections, or through a central system, commonly called a Wireless Local Area Network (WLAN) controller. An AP is differentiated from a hotspot, which is the physical location where wireless access to a WLAN is available.

Prior to wireless networks, setting up a computer network in a business, home, or school often required running many cables through walls and ceilings in order to deliver network access to all of the network-enabled devices in the building. With the creation of the wireless AP, network users are able to add devices that access the network with few or no cables. An AP normally connects directly to a wired Ethernet connection and the AP then provides wireless connections using radio frequency links for other devices to utilize that wired connection. Most APs support the connection of multiple wireless devices to one wired connection. APs are built to support a standard for sending and receiving data using these radio frequencies.

<NPL>, is directed to cross-layer cooperation to boost multipath TCP performance in cloud networks.

<CIT> is directed to a method at a network node of a Radio Access Network (RAN) for controlling packet duplication. The method includes; receiving, via at least one network interface of the network node, information indicative of a quality of each one of at least two radio channels including a first radio channel between a user equipment and a master node and a second radio channel between the user equipment and a secondary node; determining based on the received information, a respective splitting flag value associated with each of the master and secondary nodes; and controlling packet duplication based on the respective splitting flag value associated with each of the master and secondary nodes.

Low latency wireless communications may be provided. A client device is authorized, by a first computing device, for a first association in response to the client device making a first concurrent association request that includes a first Media Access Control (MAC) address and identifies the first concurrent association request as an Ultra Reliable Low Latency Connection, URLLC request. In response to authorizing the client device for the first association, an Endpoint Identifier (EID) associated with the client device is registered with a first Routing Locator (RLOC) in a map server along with an indication that the first RLOC is for simulcasting, the first RLOC being associated with the first MAC address. The client device is then authorized for a second association in response to the client device making a second concurrent association request that includes a second MAC address and identifies the second concurrent association request as an Ultra Reliable Low Latency Connection, URLLC request. In response to authorizing the client device
for the second association, the EID associated with the client device is registered with a second RLOC in the map server, the second RLOC being associated with the second MAC address along with an indication that the second RLOC is for simulcasting.

Both the foregoing overview and the following example embodiments are examples and explanatory only, and should not be considered to restrict the disclosure's scope, as described and claimed. Furthermore, features and/or variations may be provided in addition to those described. For example, embodiments of the disclosure may be directed to various feature combinations and sub-combinations described in the example embodiments.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.

According to the 3rd Generation Partnership Project (3GPP) Release <NUM><NUM>-NR, Ultra-Reliable Low-Latency Communication (URLLC) is a set of features that provide low latency and ultra-high reliability for applications such as industrial internet, smart grids, factory automation, autonomous driving, remote surgery, and intelligent transportation systems. These applications may require, for example, sub-millisecond latency with error rates that are lower than <NUM> packet loss in <NUM><NUM>. Supporting URLLC applications for wireless (e.g., Wi-Fi) access may require new approaches for packet delivery. These approaches should meet the stringent URLLC requirements around packet loss and latency metrics on an air interface and in an access network.

Embodiments of the disclosure may provide a process for supporting URLLC capabilities for wireless (e.g., Wi-Fi) access based on a network fabric data plane. For example, embodiments of the disclosure may allow a wireless client device to establish concurrent Wi-Fi associations (e.g., two or more) either to a same Access Point (AP), or to different APs by using multiple Media Access Control (MAC) addresses. These MAC addresses may have been generated by the client device, or may have been obtained from a network function. Embodiments of the disclosure may allow the client device to obtain a same Internet Protocol (IP) address or different IP addresses for each of those associations. Furthermore, embodiments of the disclosure may extend a Software Defined Access (SDA) architecture for supporting URLLC capabilities. For example, a simulcasting property may be introduced in a map server for an Endpoint Identifier (EID) associated with the URLLC connection. This may allow a border node and other switches or routers to bi-cast the traffic to more than one Routing Locator (RLOC) at the same time.

Network fabric will now be described. The complexity in networks may come from policies being tied to network constructs such as IP addresses, VLANs, ACLs, etc. In order to address these complexities, an enterprise network may be divided into two different layers, each for different objectives. One layer may be dedicated to the physical devices and forwarding of traffic (known as an underlay), and another virtual layer (known as an overlay) may be where wired and wireless users and devices may be logically connected together, and services and policies may be applied. This may provide a separation of responsibilities and may maximize the capabilities of each layer while simplifying deployment and operations since a change of policy may only affect the overlay, and the underlay may not be touched. The combination of an underlay and an overlay may be referred to as a network fabric.

As referenced above, SDA may comprise an intent-based networking solution for an enterprise. An intent-based network may treat the network as a single system that may provide the translation and validation of business intent (or goals) into the network and may return actionable insights. SDA may provide automated end-to-end services (e.g., segmentation, quality of service, and analytics) for user, device, and application traffic. SDA may automate user policy so organizations may ensure the appropriate access control and application experience maybe set for any user or device to any application across the network. This may be accomplished with a single network fabric across LAN and WLAN, which may create a consistent user experience, anywhere, without compromising security. SDA benefits may include, but are not limited to: i) automation (e.g., plug-and-play for simplified deployment of new network devices, along with consistent management of wired and wireless network configuration provisioning); ii) policy (e.g., automated network segmentation and group-based policy; iii) assurance (e.g., contextual insights for fast issue resolution and capacity planning; and iv) integration (e.g., open and programmable interfaces for integration with third-party solutions).

By allowing a Wi-Fi client device to establish concurrent wireless associations and by introducing a simulcasting property in a mapping system (and in combination with efficient Wi-Fi6 radios for example), the Wi-Fi client device may receive packets from multiple paths (i.e., that same packets may be received over different paths), thus reducing packet loss and packet delays and meeting the URLLC requirements. In other words, embodiments of the disclosure may stitch an end-to-end system for providing a URLLC capability to wireless access by providing a logic for extending the mapping system (e.g., LISP mapping system) for realizing simulcasting and leveraging dynamic MAC address usage and concurrent Wi-Fi associations. With this approach, embodiments of the disclosure may provide a URLLC capability to wireless access in SDA. This, in conjunction with Institute of Electrical and Electronic Engineers (IEEE) <NUM>. 11ax compliant radios for example, may provide a powerful tool for enabling delay and loss-sensitive communications over wireless access.

<FIG> shows an operating environment <NUM>. Operating environment <NUM> illustrates an example topology with configured routers and switches. Networks may be deployed in other topologies consistent with embodiments of the disclosure. As shown in <FIG>, operating environment <NUM> may comprise a client device <NUM>, a network <NUM>, and an application server <NUM>. Network <NUM> may include a first pathway <NUM> and a second pathway <NUM> over which packets may be bi-casted (i.e., simulcasted). Network <NUM> may comprise a first Access Point (AP) <NUM>, a second AP <NUM>, a first switch <NUM>, a second switch <NUM>, a first router <NUM>, a second router <NUM>, a third router <NUM>, a fourth router <NUM>, and a border node <NUM>. Consistent with embodiments of the disclosure, first pathway <NUM> may be established between border node <NUM> and client device <NUM> over first AP <NUM>, first switch <NUM>, first router <NUM>, and third router <NUM>. Similarly, second pathway <NUM> may be established between border node <NUM> and client device <NUM> over second AP <NUM>, second switch <NUM>, second router <NUM>, and fourth router <NUM>. Network <NUM> may be controlled by Wireless Local Area Network Controller (WLC) <NUM> that may query map server <NUM> and Digital Network Architecture Controller (DNA-C) <NUM> as described in greater detail below.

Consistent with embodiments of the disclosure, an application <NUM> may be running on client device <NUM>. Application <NUM> may be a URLLC application configured to support concurrent wireless associations. Client device <NUM> may establish a first association <NUM> with first AP <NUM>. Similarly, client device <NUM> may establish a second association <NUM> with second AP <NUM>. First association <NUM> may have a first MAC address <NUM> (e.g., M1) and second association <NUM> may have a second MAC address <NUM> (e.g., M2). First association <NUM> and second association <NUM> may share the same IP address <NUM> (also called an Endpoint Identifier (EID)) (e.g., IP1).

Client device <NUM> and application server <NUM> may comprise, but are not limited to, a smart phone, a personal computer, a tablet device, a mobile device, a cable modem, a cellular base station, a telephone, a remote control device, a set-top box, a digital video recorder, an Internet-of-Things (IoT) device, a network computer, a mainframe, a router, or other similar microcomputer-based device. First AP <NUM> and second AP <NUM> may provide wireless access to network <NUM> for client device <NUM> and may operate using the IEEE <NUM> standard for example.

Embodiments of the disclosure may allow client device <NUM> to establish concurrent wireless (e.g., Wi-Fi) associations (e.g., first association <NUM> and second association <NUM>) to different APs (e.g., first AP <NUM> and second AP <NUM>) by using multiple MAC addresses (e.g., first MAC address <NUM> and second MAC address <NUM>). These MAC addresses may have been generated by client device <NUM>, or may have been obtained from a network function such as WLC <NUM> or DNA-C <NUM>. Embodiments of the disclosure may allow client device <NUM> to obtain a same EID (e.g., IP address <NUM>) for both first association <NUM> and second association <NUM>. Furthermore, embodiments of the disclosure may provide a simulcasting property introduced by map server <NUM> for an EID associated with a URLLC connection for example. This may allow border node <NUM> and other switches or routers in network <NUM> to bi-cast the traffic to more than one RLOC at the same time.

An RLOC may comprise, for example, an IPv4 or IPv6 address of an Egress Tunnel Router (ETR). An RLOC may be obtained from the output of an EID-to-RLOC mapping lookup in map server <NUM>. An EID may comprise, for example, an IPv4 or IPv6 address used in the source and destination address fields of the first (i.e., most inner) Locator/ID Separation Protocol (LISP) header of a packet. An ETR may comprise a device that is a tunnel endpoint and may accept an IP packet where the destination address in the "outer" IP header in one of its own RLOCs. An Ingress Tunnel Router (ITR) may comprise a device that is a tunnel start point. The ITR may receive IP packets from site end-systems on one side and may send IP packets (e.g., encapsulated using LISP headers or similar encapsulation headers such as VXLAN or GRE) across a network to an ETR on the other side. The terms ITR and ETR may be reversed for the up link traffic from the client. In some deployments, LISP devices may act both as ITR and ETR depending on the direction of the traffic (and may be referred to as xTRs). In the example shown in <FIG>, first pathway <NUM> may comprise a tunnel with an ITR comprising border node <NUM> and an ETR comprising first switch <NUM> with a first RLOC (e.g., RLOC-<NUM>). Similarly, second pathway <NUM> may comprise a tunnel with an ITR comprising border node <NUM> and an ETR comprising second switch <NUM> with a second RLOC (e.g., RLOC-<NUM>).

Consistent with embodiments of the disclosure, client device <NUM> running URLLC application <NUM> may be configured to support concurrent wireless associations (i.e., first association <NUM> and second association <NUM>). These associations may be to the same or a different APs. Client device <NUM> may present a unique MAC address (e.g., M1 and M2) for each association. Client device <NUM> may present a URLLC indication (e.g., URLLC-CAPABILITY-REQUEST) in the respective association and/or in authorization procedures.

The embodiments described in the present disclosure may be compatible with the case where the two MACs used by the UE (e.g., client device) are attached behind the same switch (through two APs connected to the same switch or through one AP with two associations with the UE). In that scenario, the EID of the UE may be associated with a single RLOC (the single switch) and regular LISP operation may happen to deliver packets to the switch without the need to use bi-casting over the LISP network. Packet replication and bi-casting may happen at the switch itself (in the case of two APs connected to the switch) or at the AP (in the case of an AP with two associations with the UE).

When requesting, for example, an IPv4/IPv6 address, client device <NUM> may include a URLLC request tag in the DHCPv4/DHCPv6 or other address assignment procedures. Network <NUM> may ensure the same IP address (i.e., EID) is given to both of the URLLC associations. For example, first association <NUM> may have a MAC and an IP address {M1, IP1} and second association <NUM> may have a MAC and an IP address {M2, IP1}. This may allow application <NUM> on client device <NUM> to bind to a single IP address.

WLC <NUM> may register the EID entry (e.g., IP1) in map server <NUM> with an indication that the EID is an URLLC address (i.e., client device <NUM> has presented the URLLC indication). Border node <NUM> and other xTR functions may receive two RLOC entries for the same EID {IP <NUM>: RLOC-<NUM>, RLOC-<NUM>}, marked with the URLLC indication attribute. Application <NUM> running on client device <NUM> may associate to a logical interface using both first association <NUM> and second association <NUM>.

Border node <NUM>, on receiving a packet from application server <NUM>, may see if there is a cache entry for that EID (i.e., the destination IP address of the packet). If there is no cache entry, border node <NUM> may make a query to the map server <NUM>. Map server <NUM> may return both of the RLOCs (i.e., RLOC-<NUM> and RLOC-<NUM>) and with a special indication that the EID is a URLLC address and that the packet should be bi-casted to both of the RLOCs associated with the EID address.

Because of the URLLC indication on the retrieved mapping, border node <NUM> may duplicate the packet addressed towards the EID, encapsulate each copy with outer destination addresses of RLOC <NUM> and RLOC2 respectively, and send the copies over both first pathway <NUM> and second pathway <NUM> to RLOC-<NUM> and RLOC-<NUM>. First switch <NUM> with RLOC-<NUM> receiving the packet may send it to client device <NUM>'s MAC address M1 (i.e., first association <NUM>). Second switch <NUM> with RLOC-<NUM> receiving the packet may send it to client device <NUM>'s MAC address M2 (i.e., second association <NUM>).

URLLC capable client device <NUM> may have a Redundancy Handler (RH) <NUM> function. For example, application <NUM> running on client device <NUM> may keep receiving multiple packets on both first pathway <NUM> and second pathway <NUM>. Application <NUM> may drop the duplicate packets and may use a single copy. This RH <NUM> function may take care of packet duplication on the up link path, and duplicate removal in the down link path. For up link traffic, RH <NUM> function may duplicate the packets and send it on both first pathway <NUM> and second pathway <NUM>. Border node <NUM> may drop the duplicate packet and may do so by maintaining a hash of the last "n" packets, and comparing it with a current packet's hash.

The elements described above of operating environment <NUM> (e.g., client device <NUM>, application server <NUM>, first AP <NUM>, second AP <NUM>, first switch <NUM>, second switch <NUM>, first router <NUM>, second router <NUM>, third router <NUM>, fourth router <NUM>, border node <NUM>, WLC <NUM>, map server <NUM>, and DNA-C <NUM>) may be practiced in hardware and/or in software (including firmware, resident software, micro-code, etc.) or in any other circuits or systems. The elements of operating environment <NUM> may be practiced in electrical circuits comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Furthermore, the elements of operating environment <NUM> may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. As described in greater detail below with respect to <FIG>, the elements of operating environment <NUM> may be practiced in a computing device <NUM>.

<FIG> is a flow chart setting forth the general stages involved in a method <NUM> consistent with embodiments of the disclosure for providing low latency wireless communications. While method <NUM> describes the down link direction, the processes described herein may be used for both up link and down link packets consistent with embodiments of the disclosure. Method <NUM> may be implemented using, for example, WLC <NUM> and border node <NUM> as described in more detail above with respect to <FIG>. A flow diagram <NUM> in <FIG> will be used to explain the stages of <FIG>. Ways to implement the stages of method <NUM> will be described in greater detail below.

Method <NUM> begins at starting block <NUM> and proceed to stage <NUM> where WLC <NUM> may authorize client device <NUM> for first association <NUM> in response to client device <NUM> making a first concurrent association request that includes first MAC address <NUM> (e.g., M1). For example, application <NUM> may be running on client device <NUM> and may comprise a URLLC application configured to support concurrent wireless associations. Client device <NUM> may send the first concurrent association request to first AP <NUM> (stage <NUM>). The first concurrent association request indicates it is a URLLC request and includes first MAC address <NUM>. In response to the first concurrent association request, first AP <NUM> may request authorization from WLC <NUM> to allow first association <NUM>. WLC <NUM> may grant the requested authorization (stage <NUM>). After a policy check (stage <NUM>) from WLC <NUM>, DNA-C <NUM> may allocate an EID (i.e., IP address <NUM> (e.g., IP1)) with URLLC capability to client device <NUM> for first association <NUM> (stage <NUM>).

From stage <NUM>, where WLC <NUM> authorizes client device <NUM> for first association <NUM> in response to client device <NUM> making the first concurrent association request that includes first MAC address <NUM>, method <NUM> advances to stage <NUM> where WLC <NUM> may register, in response to authorizing client device <NUM> for first association <NUM>, the EID (i.e., IP address <NUM> (e.g., IP1)) associated with client device <NUM> with a first RLOC (e.g., RLOC-<NUM>) in map server <NUM> (stage <NUM>). The first RLOC isassociated with first MAC address <NUM>. For example, WLC <NUM> may register the EID entry (i.e., IP1) in map server <NUM> with an indication (e.g., "S" for simulcast) that the EID is a URLLC address (i.e., that client <NUM> has presented a URLLC indication). This entry in map server <NUM> may also include first MAC address <NUM> for first association <NUM> and the first RLOC (e.g., RLOC-<NUM>) for first switch <NUM> because first association <NUM> is with first AP <NUM>, which is connected to first switch <NUM>. For example, the entry in map server <NUM> may comprise:
IP1:
Ml, RLOC-<NUM> (S).

Once WLC <NUM> registers the EID in map server <NUM> in stage <NUM>, method <NUM> continues to stage <NUM> where WLC <NUM> may authorize client device <NUM> for second association <NUM> in response to client <NUM> device making a second concurrent association request that includes second MAC address <NUM> (e.g., M2). For example, application <NUM> may be running on client device <NUM> and may comprise a URLLC application configured to support concurrent wireless associations. Client device <NUM> may send the second concurrent association request to second AP <NUM> (stage <NUM>). The second concurrent association request indicates it is a URLLC request and it includes second MAC address <NUM>. In response to the second concurrent association request, second AP <NUM> may request authorization from WLC <NUM> to allow second association <NUM>. WLC <NUM> may grant the requested authorization (stage <NUM>). After a policy check (stage <NUM>) from WLC <NUM>, DNA-C <NUM> may allocate the EID (i.e., IP address <NUM> (e.g., IP1)) with URLLC capability to client device <NUM> for second association <NUM> (stage <NUM>).

After WLC <NUM> authorizes client device <NUM> for second association <NUM> in response to client device <NUM> making the second concurrent association request that includes second MAC address <NUM> in stage <NUM>, method <NUM> proceeds to stage <NUM> where WLC <NUM> may register, in response to authorizing client device <NUM> for the second association, the EID (i.e., IP address <NUM> (e.g., IP1)) associated with client device <NUM> with a second RLOC (e.g., RLOC-<NUM>) in map server <NUM> (stage <NUM>). The second RLOC isbe associated with second MAC address <NUM>. For example, WLC <NUM> may register the EID entry (i.e., IP1) in map server <NUM> with an indication (e.g., "S" for simulcast) that the EID is a URLLC address (i.e., that client <NUM> has presented a URLLC indication). This entry in map server <NUM> may also include second MAC address <NUM> for second association <NUM> and the second RLOC (e.g., RLOC-<NUM>) for second switch <NUM> because second association <NUM> is with second AP <NUM>, which is connected to second switch <NUM>. For example, the entry in map server <NUM> may now comprise:
IP1:.

From stage <NUM>, where WLC <NUM> registers the EID (i.e., IP address <NUM> (e.g., IP1)) in map server <NUM>, method <NUM> may advance to stage <NUM> where border node <NUM> may receive a down link packet destined to the EID (i.e., IP address <NUM> (e.g., IP1)) associated with client device <NUM>. For example, client device <NUM> may use a logical interface (e.g., per RFC7847) for binding first association <NUM> and second association <NUM> and may establish a new application flow between client device <NUM> and application server <NUM> (stage <NUM>). Consistent with embodiments of the disclosure, client device <NUM> may also have an RH functionality as described above. Then border node <NUM> may receive the down link packet from application server <NUM> (stage <NUM>).

Once border node <NUM> receives the down link packet in stage <NUM>, method <NUM> may continue to stage <NUM> where border node <NUM> may send, in response to receiving the down link packet, a map request having the EID associated with client device <NUM> extracted from the down link packet. For example, border node <NUM> may send the map request to map server <NUM> (stage <NUM>).

From stage <NUM>, where border node <NUM> sends the map request, method <NUM> may advance to stage <NUM> where border node <NUM> may receive, in response to sending the map request, the first RLOC (e.g., RLOC-<NUM>) and the second RLOC (e.g., RLOC-<NUM>). For example, map server <NUM>, upon receiving the map request may make a query to the map server <NUM> using the EID (i.e., IP address <NUM> (e.g., IP1)). In response, map server <NUM> may return both the RLOCs (i.e., the first RLOC (e.g., RLOC-<NUM>) and the second RLOC (e.g., RLOC-<NUM>)) to border node <NUM> in a map reply (stage <NUM>). The map reply may also include a special indication that the EID is a URLLC address and that border node <NUM> should bi-cast the down link packet to both of the RLOCs associated with the EID address. Stages <NUM> and <NUM> may be skipped if border node <NUM> already has an entry for the EID in its cache because the RLOCs for the destination EID may already be available in the local cache.

After border node <NUM> receives the first RLOC (e.g., RLOC-<NUM>) and the second RLOC (e.g., RLOC-<NUM>) in stage <NUM>, method <NUM> may proceed to stage <NUM> where border node <NUM> may send the down link packet to the first RLOC and to the second RLOC. For example, border node <NUM> may enable simulcasting of packets to IP address <NUM> (e.g., IP1) corresponding to client device <NUM> through RLOC-<NUM> and through RLOC-<NUM> (stage <NUM>). Border node <NUM> may tunnel a copy of the down link packet to first switch <NUM> at RLOC-<NUM> (stage <NUM>). From first switch <NUM>, the copy of the down link packet may be forwarded to client device <NUM> through first AP <NUM> (stage <NUM>). Similarly, border node <NUM> may tunnel a copy of the down link packet to second switch <NUM> at RLOC-<NUM> (stage <NUM>). From second switch <NUM>, the copy of the down link packet may be forwarded to client device <NUM> through second AP <NUM> (stage <NUM>). Similarly, up link packets may be simulcasted over first pathway <NUM> and second pathway <NUM> from client device <NUM> to application server <NUM>. Once border node <NUM> sends the down link packet in stage <NUM>, method <NUM> may then end at stage <NUM>.

Accordingly, by allowing client device <NUM> to establish concurrent wireless associations and by introducing a simulcasting property in a mapping system, client device <NUM> may receive packets from multiple pathways, thus reducing packet loss and packet delays and meeting the URLLC requirements. In other words, embodiments of the disclosure may provide an end-to-end system for providing a URLLC capability to wireless access by providing a logic for extending the mapping system for realizing simulcasting and leveraging dynamic MAC address usage and concurrent Wi-Fi associations for example. With this approach, embodiments of the disclosure may provide a URLLC capability to wireless access in SDA. This may provide a powerful tool for enabling delay and loss-sensitive communications over wireless access.

<FIG> shows computing device <NUM>. As shown in <FIG>, computing device <NUM> may include a processing unit <NUM> and a memory unit <NUM>. Memory unit <NUM> may include a software module <NUM> and a database <NUM>. While executing on processing unit <NUM>, software module <NUM> may perform, for example, processes for providing low latency wireless communications as described above with respect to <FIG>. Computing device <NUM>, for example, may provide an operating environment for client device <NUM>, application server <NUM>, first AP <NUM>, second AP <NUM>, first switch <NUM>, second switch <NUM>, first router <NUM>, second router <NUM>, third router <NUM>, fourth router <NUM>, border node <NUM>, WLC <NUM>, map server <NUM>, or DNA-C <NUM>. Client device <NUM>, application server <NUM>, first AP <NUM>, second AP <NUM>, first switch <NUM>, second switch <NUM>, first router <NUM>, second router <NUM>, third router <NUM>, fourth router <NUM>, border node <NUM>, WLC <NUM>, map server <NUM>, and DNA-C <NUM> may operate in other environments and are not limited to computing device <NUM>.

Computing device <NUM> may be implemented using a Wi-Fi access point, a cellular base station, a tablet device, a mobile device, a smart phone, a telephone, a remote control device, a set-top box, a digital video recorder, a cable modem, a personal computer, a network computer, a mainframe, a router, a switch, a server cluster, a smart TV-like device, a network storage device, a network relay devices, or other similar microcomputer-based device. Computing device <NUM> may comprise any computer operating environment, such as hand-held devices, multiprocessor systems, microprocessor-based or programmable sender electronic devices, minicomputers, mainframe computers, and the like. Computing device <NUM> may also be practiced in distributed computing environments where tasks are performed by remote processing devices. The aforementioned systems and devices are examples and computing device <NUM> may comprise other systems or devices.

Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the element illustrated in <FIG> may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which may be integrated (or "burned") onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality described herein with respect to embodiments of the disclosure, may be performed via application-specific logic integrated with other components of computing device <NUM> on the single integrated circuit (chip).

Claim 1:
A method performed by a computer system comprising:
authorizing, by a first computing device, a client device for a first association in response to the client device making a first concurrent association request that includes a first Media Access Control (MAC) address and identifies the first concurrent association request as an Ultra Reliable Low Latency Connection, URLLC request;
registering, in response to authorizing the client device for the first association, an Endpoint Identifier (EID) associated with the client device with a first Routing Locator (RLOC) in a map server along with an indication that the first RLOC is for simulcasting, the first RLOC being associated with the first MAC address;
authorizing the client device for a second association in response to the client device making a second concurrent association request that includes a second MAC address and identifies the second concurrent association request as an Ultra Reliable Low Latency Connection, URLLC request; and
registering, in response to authorizing the client device for the second association, the EID associated with the client device with a second RLOC in the map server, the second RLOC being associated with the second MAC address along with an indication that the second RLOC is for simulcasting.