Patent classifications
H04W40/02
Optimizing user equipment operation by conditioning multiple policies on information elements
A method and system for protocol data unit (PDU) session release due to violation of time or location information element constraints is provided. Operations may be part of optimizing operation of a user equipment (UE) in a wireless communications network. A policy control function (PCF) determines whether there is a violation of at least one of location information and time information associated with a background data transfer. Upon detecting such a violation, the PCF requests a session management function (SMF) to release a PDU session associated with the background data transfer. The SMF responds by releasing the PDU session.
Devices and methods for multipath communications
Broadband communications devices and methods operate with at least two separate communication paths between the devices and the network, such as the Internet. The broadband devices and methods receive data concurrently over the communication paths or separately. The bandwidth is increased when the separate communication paths are combined. The broadband devices employ packetized data with Voice over Internet Protocol (VoIP) technologies combined with RF communications technologies.
Systems and methods for user-specific slice configuration for an application
A device may receive, from a user equipment, a token request associated with an application, wherein the token request is associated with a device identifier. The device may generate a device token for the application and the user equipment. The device may provide, using the device identifier, the device token to the user equipment to enable a user to access the application via an application platform. The device may receive, from the application platform, a slice request for a network slice of a network that is to be used for an application session. The device may determine that the user equipment is associated with the application session based on the device token and the device identifier. The device may configure a network slice instance of the network slice. The device may determine a user equipment route selection policy for the application session according to the network slice instance.
Systems and methods for user-specific slice configuration for an application
A device may receive, from a user equipment, a token request associated with an application, wherein the token request is associated with a device identifier. The device may generate a device token for the application and the user equipment. The device may provide, using the device identifier, the device token to the user equipment to enable a user to access the application via an application platform. The device may receive, from the application platform, a slice request for a network slice of a network that is to be used for an application session. The device may determine that the user equipment is associated with the application session based on the device token and the device identifier. The device may configure a network slice instance of the network slice. The device may determine a user equipment route selection policy for the application session according to the network slice instance.
Flow Control Method and Apparatus
A flow control method and an apparatus, the method including receiving, by a first integrated access and backhaul (IAB) node, a radio link failure (RLF) notification from a second IAB node, where the first IAB node is a child node of the second IAB node and the second IAB node is a parent node of the first IAB node, and rerouting, by the first IAB node, based on the RLF notification, uplink data that corresponds to N backhaul adaptation protocol (BAP) routing identifiers, where N is an integer greater than or equal to 1.
SUPPORTING CBRS OPERATION USING NON-REAL TIME RAN INTELLIGENT CONTROLLER (NON-RT RIC) APPLICATIONS
A wireless communications system includes radio components (O-RU, O-DU, O-CU), an ORAN Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework, an O-RU Controller and a CBSD Controller interfacing with a Spectrum Access System (SAS) using the Wireless Innovation Forum (WINNF) CBSD-SAS Interface. An example of CBSD Controller is a Domain Proxy (DP) defined by WINNF. The CBSD Controller is disclosed as an application belonging to the Non-RT RIC. This application could be an rApp. The Non RT MC Framework operates as a broker to route information between the O-RU Controller and the CBSD Controller. Data types are defined to be exchanged over the R1 interface.
SUPPORTING CBRS OPERATION USING NON-REAL TIME RAN INTELLIGENT CONTROLLER (NON-RT RIC) APPLICATIONS
A wireless communications system includes radio components (O-RU, O-DU, O-CU), an ORAN Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework, an O-RU Controller and a CBSD Controller interfacing with a Spectrum Access System (SAS) using the Wireless Innovation Forum (WINNF) CBSD-SAS Interface. An example of CBSD Controller is a Domain Proxy (DP) defined by WINNF. The CBSD Controller is disclosed as an application belonging to the Non-RT RIC. This application could be an rApp. The Non RT MC Framework operates as a broker to route information between the O-RU Controller and the CBSD Controller. Data types are defined to be exchanged over the R1 interface.
Methods for handling anomaly notification messages
In systems and methods for communicating an anomaly notification message to a wireless communication network, a wireless device may generate an anomaly notification message comprising an anomaly notification object in response to determining that the received information satisfies one or more threshold criteria indicative of the anomaly condition, configure the anomaly notification message with a transport layer anomaly code, and send sending the configured anomaly notification message via an anomaly-specific network communication link to a wireless communication network. A communication network device may receive the anomaly notification message, and in response to determining that the anomaly notification message was received via the anomaly-specific network communication link may associate the anomaly notification message with an anomaly priority that is higher than a normal traffic priority.
Methods for handling anomaly notification messages
In systems and methods for communicating an anomaly notification message to a wireless communication network, a wireless device may generate an anomaly notification message comprising an anomaly notification object in response to determining that the received information satisfies one or more threshold criteria indicative of the anomaly condition, configure the anomaly notification message with a transport layer anomaly code, and send sending the configured anomaly notification message via an anomaly-specific network communication link to a wireless communication network. A communication network device may receive the anomaly notification message, and in response to determining that the anomaly notification message was received via the anomaly-specific network communication link may associate the anomaly notification message with an anomaly priority that is higher than a normal traffic priority.
Secure creation of application containers for fifth generation cellular network slices
Systems, methods, and computer-readable media for the secure creation of application containers for 5G slices. A MEC application in a MEC layer of a 5G network can be associated with a specific network slice of the 5G network. A backhaul routing policy for the MEC application can be defined based on the association of the MEC application with the specific network slice of the 5G network. Further, a SID for the MEC application that associates the MEC application with a segment routing tunnel through a backhaul of the 5G network can be generated. A MEC layer access policy for the MEC application can be defined based on the SID for the MEC application. As follows, access to the MEC application through the 5G network can be controlled based on both the backhaul routing policy for the MEC application and the MEC layer access policy for the application.