Abstract: Disclosed herein is an apparatus (114) configured to obtain a number of Physical Resource Blocks (PRBs) corresponding to each of one or more DUs. The one or more DUs are associated with carrier aggregation for a carrier group. Further, the apparatus (114) is configured to identify a leader DU, from among the one or more DUs, based on the obtained number of PRBs associated with each of the one or more DUs. Further, the apparatus (114) is configured to assign a corresponding sequence identifier (ID) to each of the one or more DUs based on the obtained number of PRBs. Further, the apparatus (114) is configured to receive a set of tokens from the identified leader DU. Furthermore, the apparatus (114) is configured to perform a data transmission for the carrier group, based on the received set of tokens.

Abstract: In general, the current subject matter relates to triggering network redundancy based on LBM. In some implementations, triggering network redundancy based on LBM can include, via a DU, transmitting an LBM data request to an RU, receiving an LBM data response from the RU, enabling user plane communications with the RU based on receiving the LBM data response, transmitting, based on the established periodicity, a second LBM data request based on a MAC address to a plurality of RUs including the RU, marking the RU as non-responsive when a second LBM data response to the second LBM data request from the RU is not received or the second LBM data response indicates an issue for a consecutive number of times, and establishing a second MAC address for communicating with the plurality of RUs when each of the plurality of RUs are marked as non-responsive.

Abstract: A computer-implemented method of distributing traffic includes distributing, to a first distributed unit (DU), traffic via a first path, receiving, from the first DU, an indication generated by a first dry contact alarm of the first DU that a state has changed in the first DU, switching, by an optical switch, the traffic from the first path to a second path based on the indication from the first DU, and distributing, to a second DU, the traffic via the second path.

Abstract: Methods to overcome Logical Channel ID (LCID) limitations during bearer type switching when multiple ENDC bearers are supported. Initially, the method recites determining a configuration mode of a bearer to be added for the UE, which may be either MCG mode or SCG-split mode. Further, the method recites allocating an LCID to the bearer based on the configuration mode and one or more criteria. The method recites performing, upon detecting an addition of a secondary node in the communication network by checking whether LCIDs are available for allocating corresponding bearers requiring SCG-split mode in response to the addition of the secondary node. The method further recites assigning the LCIDs to the corresponding bearers requiring the SCG-split mode, when the LCIDs are available for the bearers and switching a set of bearers, among the bearers, into the SCG-split mode when the LCIDs are available only for the set of bearers.

Abstract: A UE reports an ECGI of a target eNB/gNB missing an X2/Xn interface to a source eNB/gNB. The source eNB/gNB sends a configuration transfer message to a network element to get the X2/Xn interface TNLA of the target eNB/gNB. The source eNB/gNB initiates an initial backoff timer and an exponential backoff multiplier. The source eNB/gNB determines whether the TNLA discovery procedure time is equal to or greater than a current backoff time, the current backoff time being equal to a previous backoff period multiplied by the exponential backoff multiplier. The source eNB/gNB may resend the configuration transfer message to the network element when a previous TNLA discovery procedure time for the same ECGI is equal to or greater than the current backoff time, and not resend the configuration transfer message to the network element when the previous TNLA discovery procedure time is less than the current backoff time.

Abstract: In general, the current subject matter relates to triggering network redundancy based on LBM. In some implementations, triggering network redundancy based on LBM can include, via a DU, transmitting an LBM data request to an RU, receiving an LBM data response from the RU, enabling user plane communications with the RU based on receiving the LBM data response, transmitting, based on the established periodicity, a second LBM data request based on a MAC address to a plurality of RUs including the RU, marking the RU as non-responsive when a second LBM data response to the second LBM data request from the RU is not received or the second LBM data response indicates an issue for a consecutive number of times, and establishing a second MAC address for communicating with the plurality of RUs when each of the plurality of RUs are marked as non-responsive.

Abstract: A UE reports an ECGI of a target eNB/gNB missing an X2/Xn interface to a source eNB/gNB. The source eNB/gNB sends a configuration transfer message to a network element to get the X2/Xn interface TNLA of the target eNB/gNB. The source eNB/gNB initiates an initial backoff timer and an exponential backoff multiplier. The source eNB/gNB determines whether the TNLA discovery procedure time is equal to or greater than a current backoff time, the current backoff time being equal to a previous backoff period multiplied by the exponential backoff multiplier. The source eNB/gNB may resend the configuration transfer message to the network element when a previous TNLA discovery procedure time for the same ECGI is equal to or greater than the current backoff time, and not resend the configuration transfer message to the network element when the previous TNLA discovery procedure time is less than the current backoff time.

Abstract: In general, the current subject matter relates to automated basic input/output system (BIOS) recovery. In some implementations, automated BIOS recovery can include attempting to boot an operating system (OS) from a BIOS while running an Intelligent Platform Management Interface (IPMI) watchdog timer. The BIOS can be stored in a first partition of a memory of a communication device in a wireless communication system. After a timeout of the watchdog timer, performance of a BIOS recovery procedure can be automatically triggered. After the performance of the BIOS recovery procedure, the OS can be automatically re-attempted to boot from the BIOS.

Abstract: A computer-implemented method of distributing traffic includes distributing, to a first distributed unit (DU), traffic via a first path, receiving, from the first DU, an indication generated by a first dry contact alarm of the first DU that a state has changed in the first DU, switching, by an optical switch, the traffic from the first path to a second path based on the indication from the first DU, and distributing, to a second DU, the traffic via the second path.

Abstract: An example method is provided in one example embodiment and includes receiving, by a user equipment device, a list including at least one location identifier associated with an area for location reporting and an area identifier identifying the area for location reporting. The method further includes receiving a location identifier broadcast by a wireless network element, and determining whether the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The method further includes sending a location reporting message by the user equipment device to a first network node when it is determined that the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The location reporting message is indicative of the user equipment device either entering or exiting the area for location reporting.

Abstract: An example method is provided in one example embodiment and may include determining that a user equipment (UE) is approximately stationary for a threshold period of time within a particular geographic area based, at least in part, on a radio access network (RAN) node to which the UE is attached; notifying the UE that the UE has been associated with the particular geographic area; and transitioning the UE into an idle mode from an active mode, wherein the transitioning is performed without notifying a core network that the UE has transitioned to the idle mode. Determining that the UE is approximately stationary can include monitoring mobility signaling from the UE and comparing an amount of time that the UE has been attached to the RAN node with a threshold period of time. The core network can be notified when the UE moves out of the particular geographic area.

Abstract: In an example, there is disclosed a computing apparatus, having: a processor; a memory; a network interface to communicatively couple to a mobile data network; and an interconnection and routing function (IRF) server engine to: receive an incoming Control plane message from a source network function (NF) via the network interface; examine a header of the incoming Control plane message to determine a destination NF of the Control plane message; and route the Control plane message to the destination NF.

Abstract: An example method is provided in one example embodiment and may include communicating a message for a group of one or more user equipment (UE) from a machine type communication-interworking function (MTC-IWF) to a packet data network gateway (PGW), wherein the message includes a group identity (ID) associated with the group of one or more UE; communicating the message from the PGW to one or more serving gateways (SGWs); and communicating the message from each of the one or more SGWs to each of the one or more UE of the group of the one via a tunnel for each of the one or more UE.

Abstract: An example method is provided in one example embodiment and includes receiving, by a user equipment device, a list including at least one location identifier associated with an area for location reporting and an area identifier identifying the area for location reporting. The method further includes receiving a location identifier broadcast by a wireless network element, and determining whether the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The method further includes sending a location reporting message by the user equipment device to a first network node when it is determined that the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The location reporting message is indicative of the user equipment device either entering or exiting the area for location reporting.

Abstract: A method is provided in one example embodiment and may include determining a location for a user equipment (UE); determining whether at least one user data plane entity servicing at least one packet data network (PDN) flow for the UE is to be changed based, at least in part, on the location of the UE; if at least one user data plane entity is to be changed, selecting at least one new user data plane entity to service the at least one PDN flow for the UE; allocating a new PDN Internet Protocol (IP) address for the at least one PDN flow for which the user data plane entity is changed; and communicating the new PDN IP address to the UE.

Abstract: An example method is provided in one example embodiment and includes receiving, by a user equipment device, a list including at least one location identifier associated with an area for location reporting and an area identifier identifying the area for location reporting. The method further includes receiving a location identifier broadcast by a wireless network element, and determining whether the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The method further includes sending a location reporting message by the user equipment device to a first network node when it is determined that the broadcast location identifier matches the at least one location identifier associated with the area for location reporting. The location reporting message is indicative of the user equipment device either entering or exiting the area for location reporting.

Abstract: A method is provided in one example embodiment and may include determining that a periodic timer for a user equipment (UE) is about to expire; communicating to an application service, prior to expiration of the periodic timer for the UE, an indication associated with an availability of the UE to receive data from the application service; and communicating the data from the application service to the UE upon receiving the indication. In some cases, the method can include registering, by the application service, to receive the indication from a Mobility Management Entity (MME) or a serving General Packet Radio Service (GPRS) support node (SGSN), wherein the registering is performed via a service capability exposure function (SCEF) in communication with the MME or the SGSN and the application service.

Abstract: An example method is provided in one example embodiment and may include determining that a user equipment (UE) is approximately stationary for a threshold period of time within a particular geographic area based, at least in part, on a radio access network (RAN) node to which the UE is attached; notifying the UE that the UE has been associated with the particular geographic area; and transitioning the UE into an idle mode from an active mode, wherein the transitioning is performed without notifying a core network that the UE has transitioned to the idle mode. Determining that the UE is approximately stationary can include monitoring mobility signaling from the UE and comparing an amount of time that the UE has been attached to the RAN node with a threshold period of time. The core network can be notified when the UE moves out of the particular geographic area.

Abstract: A method is provided in one example embodiment and may include determining that a periodic timer for a user equipment (UE) is about to expire; communicating to an application service, prior to expiration of the periodic timer for the UE, an indication associated with an availability of the UE to receive data from the application service; and communicating the data from the application service to the UE upon receiving the indication. In some cases, the method can include registering, by the application service, to receive the indication from a Mobility Management Entity (MME) or a serving General Packet Radio Service (GPRS) support node (SGSN), wherein the registering is performed via a service capability exposure function (SCEF) in communication with the MME or the SGSN and the application service.

Abstract: A method is provided in one example embodiment and may include determining that a periodic timer for a user equipment (UE) is about to expire; communicating to an application service, prior to expiration of the periodic timer for the UE, an indication associated with an availability of the UE to receive data from the application service; and communicating the data from the application service to the UE upon receiving the indication. In some cases, the method can include registering, by the application service, to receive the indication from a Mobility Management Entity (MME) or a serving General Packet Radio Service (GPRS) support node (SGSN), wherein the registering is performed via a service capability exposure function (SCEF) in communication with the MME or the SGSN and the application service.