RAN level cellular-wlan convergence

Abstract

The present disclosure describes various example embodiments of cellular-Wireless Local Area Network (WLAN) Radio Access Network (RAN) convergence (CWRC) capabilities. The CWRC capabilities can be configured to support architectural and procedural solutions to enable Layer 2 (L2) convergence between cellular access and WLAN access within a RAN.

Description

Technical Field

[0001] The various example embodiments generally relate to communication networks, and more specifically, but not exclusively, to horizontal convergence of radio access networks (RANs) supporting multiple types of radio access technologies (RATs). Background Technology

[0002] Various communication technologies can be used to support communication in various types of communication systems. Summary of the Invention

[0003] In at least some example embodiments, a terminal device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: send a terminal device capability information message, wherein the terminal device capability information message indicates that the terminal device is capable of supporting Cellular Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) bearers; receive a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes a set of parameters for the CWRC bearers of the terminal device; and configure the CWRC bearers for the terminal device based on the set of parameters for the CWRC bearers of the terminal device. In at least some example embodiments, a computer-readable storage medium includes computer program code that, when executed by a terminal device, causes the terminal device to: transmit a terminal device capability information message, wherein the terminal device capability information message indicates that the terminal device is capable of supporting Cellular Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) bearers; receive a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes a set of parameters for the CWRC bearers of the terminal device; and configure a CWRC bearer for the terminal device based on the set of parameters for the CWRC bearers of the terminal device. In at least some example embodiments, a method includes: transmitting a terminal device capability information message, wherein the terminal device capability information message indicates that the terminal device is capable of supporting Cellular Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) bearers; receiving a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes a set of parameters for the CWRC bearers of the terminal device; and configuring a CWRC bearer for the terminal device based on the set of parameters for the CWRC bearers of the terminal device. In at least some example embodiments, an apparatus includes: components for transmitting a terminal device capability information message, wherein the terminal device capability information message indicates that the terminal device is capable of supporting Cellular Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) bearers; components for receiving a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes a set of parameters for the CWRC bearers of the terminal device; and components for configuring the CWRC bearers of the terminal device based on the set of parameters for the CWRC bearers of the terminal device. In at least some example embodiments, the terminal device capability information message includes a unique Layer 2 identifier specific to the terminal device for use in CWRC-related operations.In at least some example embodiments, the terminal device supports downlink and uplink, and the terminal device capability information message includes information elements that include at least one of the following: at least one parameter indicating whether the terminal device supports a first CWRC bearer type in one of the downlink or uplink links; at least one parameter indicating whether the terminal device supports a second CWRC bearer type in one of the downlink or uplink links; or at least one parameter indicating whether the terminal device supports a third CWRC bearer type in one of the downlink or uplink links. In at least some example embodiments, the RRC reconfiguration message includes a first information element, wherein the first information element includes: a data radio bearer type element indicating the data radio bearer type used for the CWRC bearer for the terminal device; a CWRC bearer type element indicating the bearer type for the CWRC bearer for the terminal device; a Serving Data Adaptation Protocol (SDAP) configuration element including one or more parameters for an SDAP entity for the CWRC bearer for the terminal device; and a Packet Data Convergence Protocol (PDCP) configuration element including one or more parameters for a PDCP entity for the CWRC bearer for the terminal device. In at least some example embodiments, the RRC reconfiguration message includes a second information element, wherein the second information element includes a unique Layer 2 identifier specific to a WLAN terminal element that supports CWRC bearers for the terminal device. In at least some example embodiments, the CWRC bearer for a terminal device includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising DDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising DDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.In at least some example embodiments, the terminal device is configured to support at least one of the following: a first service data adaptation protocol entity and a second service data adaptation protocol entity, the first service data adaptation protocol entity being mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access, and the second service data adaptation protocol entity being mapped to a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access; a service data adaptation protocol entity being mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access and a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access; or a service data adaptation protocol entity being mapped to a packet data aggregation protocol entity that supports a data radio bearer that supports a first logical channel based on cellular access and a second logical channel based on WLAN access.

[0004] In at least some example embodiments, an apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: sending a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to a wireless local area network (WLAN) terminal element of the RAN by a control element of the radio access network (RAN); and receiving a bearer context establishment response message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments, when executed by the at least one processor, the instructions cause the apparatus to at least perform: sending a bearer context establishment request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by the at least one processor, the instructions cause the apparatus to at least perform: sending a bearer context modification request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending a bearer context release command for CWRC bearer to a WLAN terminal element by a control element; and receiving a bearer context release completion message for CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by the control element. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending a bearer context release command message to a user plane element of the RAN by the control element before sending the bearer context release command for CWRC bearer; and sending a terminal device context release command for the terminal device of the CWRC bearer to a distributed unit of the RAN before sending the bearer context release command for CWRC bearer. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by a user plane element of the RAN. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on receiving a bearer context release complete message from a user plane element of the RAN and based on receiving a terminal device context release complete message from a terminal device for the CWRC bearer.In at least some example embodiments, the CWRC bearer includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.

[0005] In at least some example embodiments, an apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: sending a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to a wireless local area network (WLAN) terminal element of the RAN by a control element of the radio access network (RAN), and receiving a bearer context establishment response message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments, when executed by the at least one processor, the instructions cause the apparatus to at least perform: sending a bearer context establishment request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by the at least one processor, the instructions cause the apparatus to at least perform: sending a bearer context modification request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending a bearer context release command for CWRC bearer to a WLAN terminal element by a control element; and receiving a bearer context release completion message for CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by the control element. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending a bearer context release command message to a user plane element of the RAN by the control element before sending the bearer context release command for CWRC bearer; and sending a terminal device context release command for the terminal device of the CWRC bearer to a distributed unit of the RAN before sending the bearer context release command for CWRC bearer. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by a user plane element of the RAN. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on receiving a bearer context release complete message from a user plane element of the RAN and based on receiving a terminal device context release complete message from a terminal device for the CWRC bearer.In at least some example embodiments, the CWRC bearer includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.

[0006] In at least some example embodiments, a computer-readable storage medium includes computer program code that, when executed by a device, causes the device to at least perform: sending a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to a wireless local area network (WLAN) terminal element of the RAN by a control element of the radio access network (RAN), and receiving a bearer context establishment response message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments, when executed by a device, the computer program code causes the device to at least perform: sending a bearer context establishment request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by a device, the computer program code causes the device to at least perform: sending a bearer context modification request message to a user plane element of the RAN by the control element. In at least some example embodiments, when executed by the device, the computer program code causes the device to at least perform: sending a bearer context release command for CWRC bearer to a WLAN terminal element by a control element, and receiving a bearer context release completion message for CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by the control element. In at least some example embodiments, when executed by the device, the computer program code causes the device to at least perform: sending a bearer context release command message to a user plane element of the RAN before sending the bearer context release command for CWRC bearer, and sending a terminal device context release command for the terminal device of the RAN to a distributed unit of the RAN before sending the bearer context release command for CWRC bearer. In at least some example embodiments, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by a user plane element of the RAN. In at least some example embodiments, the bearer context release command for receiving CWRC bearer is sent based on a bearer context release complete message from a user plane element of the RAN and a terminal device context release complete message received from a terminal device for CWRC bearer.In at least some example embodiments, the CWRC bearer includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.

[0007] In at least some example embodiments, a method includes: sending a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to a wireless local area network (WLAN) terminal element of the RAN by a control element of the radio access network (RAN), and receiving a bearer context establishment response message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments, the method further includes: sending the bearer context establishment request message to a user plane element of the RAN by the control element. In at least some example embodiments, the method further includes: sending a bearer context modification request message to a user plane element of the RAN by the control element. In at least some example embodiments, the method further includes: sending a bearer context release command for the CWRC bearer to a WLAN terminal element by the control element, and receiving a bearer context release completion message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on a bearer context release process triggered by the control element. In at least some example embodiments, the method further includes: sending a bearer context release command message by a control element to a user plane element of the RAN before sending a bearer context release command for the CWRC bearer; and sending a terminal device context release command for the terminal device of the CWRC bearer to a distributed unit of the RAN before sending the bearer context release command for the CWRC bearer. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on a bearer context release process triggered by a user plane element of the RAN. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on a bearer context release completion message from a user plane element of the RAN and based on receiving a terminal device context release completion message for the CWRC bearer.In at least some example embodiments, the CWRC bearer includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.

[0008] In at least some example embodiments, an apparatus includes: means for sending a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to a wireless local area network (WLAN) terminal element of the RAN by a control element of the radio access network (RAN), and means for receiving a bearer context establishment response message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments, the apparatus further includes: means for sending the bearer context establishment request message to a user plane element of the RAN by the control element. In at least some example embodiments, the apparatus further includes: means for sending a bearer context modification request message to a user plane element of the RAN by the control element. In at least some example embodiments, the apparatus further includes: means for sending a bearer context release command for the CWRC bearer to the WLAN terminal element by the control element, and means for receiving a bearer context release completion message for the CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on a bearer context release process triggered by a control element. In at least some example embodiments, the apparatus further includes: components for sending a bearer context release command message by the control element to a user plane element of the RAN before sending the bearer context release command for the CWRC bearer; and components for sending a terminal device context release command for the terminal device of the CWRC bearer to a distributed unit of the RAN by the control element before sending the bearer context release command for the CWRC bearer. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on a bearer context release process triggered by a user plane element of the RAN. In at least some example embodiments, the bearer context release command for the CWRC bearer is sent based on receiving a bearer context release completion message from a user plane element of the RAN, and based on receiving a terminal device context release completion message for the terminal device of the CWRC bearer.In at least some example embodiments, the CWRC bearer includes one of the following: a bearer comprising multiple Protocol Data Unit (PDU) sessions based on multiple corresponding Service Data Adaptor (SDU) entities, the multiple corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding Packet Data Convergence (PDC) entities; a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or a bearer comprising PDU sessions based on corresponding SDU entities, the corresponding SDU entities being mapped to access-specific logical channels of data radio bearers associated with corresponding PDC entities, wherein at least one of the access-specific logical channels is based on WLAN access.

[0009] In at least some example embodiments, an apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer from a radio access network (RAN) wireless local area network (WLAN) terminal element toward a control element of the RAN, and sending a bearer context establishment response message for a CWRC bearer from the WLAN terminal element toward the control element. In at least some example embodiments, a computer-readable storage medium includes computer program code that, when executed by the apparatus, causes the apparatus to at least perform: receiving a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer from a radio access network (RAN) wireless local area network (WLAN) terminal element toward a control element of the RAN, and sending a bearer context establishment response message for a CWRC bearer from the WLAN terminal element toward the control element. In at least some example embodiments, a method includes: receiving a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer from a radio access network (RAN) WLAN terminal element toward a control element of the RAN; and sending a bearer context establishment response message for the CWRC bearer from the WLAN terminal element toward the control element. In at least some example embodiments, an apparatus includes: components for receiving a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer from a radio access network (RAN) WLAN terminal element toward a control element of the RAN; and components for sending a bearer context establishment response message for the CWRC bearer from the WLAN terminal element toward the control element.

[0010] In at least some example embodiments, an apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: supporting a set of communication interfaces for a radio access network (RAN) by a wireless local area network (WLAN) terminal element, the RAN including cellular base stations (BS), wherein the set of communication interfaces includes: a first communication interface configured to support access to the WLAN by the set of terminal devices; a second communication interface configured to support communication with a control plane element of the cellular BS; and a third communication interface configured to support communication with a user plane element of the cellular BS; and, based on the set of communication interfaces, supporting a cellular-WLAN RAN convergence (CWRC) bearer by the WLAN terminal element. In at least some example embodiments, the instructions, when executed by the at least one processor, cause the apparatus to at least perform: supporting a state machine by the WLAN terminal element, the state machine supporting a set of states, wherein the set of states includes an idle state, an active state, an associated state, and a connected state. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending an initialization request message to a control plane element of a cellular BS, the initialization request message being configured to request initialization of the WLAN terminal element; and receiving an initialization response message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: receiving a configuration update message from the control plane element of the cellular BS, the configuration update message being configured to update the usage in the configuration information of the WLAN terminal element; and sending a configuration update confirmation message to the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to at least perform: sending a configuration update message to the control plane element of the cellular BS, the configuration update message indicating an update to the configuration information of the WLAN terminal element; and receiving a configuration update confirmation message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to perform at least: receiving a deactivation request message from a control plane element of a cellular BS by a WLAN terminal element, the deactivation request message being configured to request deactivation of the WLAN terminal element; and sending a deactivation response message from a control plane element of the cellular BS by the WLAN terminal element.In at least some example embodiments, when executed by at least one processor, the instruction causes the apparatus to perform at least the following: sending a terminal device association message to a control plane element of a cellular BS, the terminal device association message being configured to indicate an association between a terminal device and the WLAN terminal element; and receiving a terminal device association confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by at least one processor, the instruction causes the apparatus to perform at least the following: receiving a CWRC bearer context establishment request message from the control plane element of the cellular BS, the CWRC bearer context establishment request message being configured to request the establishment of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context establishment response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to perform at least the following: receiving a CWRC bearer context modification request message from a control plane element of a cellular BS, the CWRC bearer context modification request message being configured to request modification of the context used for CWRC bearers within the WLAN terminal element; and sending a CWRC bearer context modification response message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to perform at least the following: receiving a CWRC bearer context release request message from a control plane element of the cellular BS, the CWRC bearer context release request message being configured to request release of the context used for CWRC bearers within the WLAN terminal element; and sending a CWRC bearer context release response message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the instruction causes the device to perform at least the following: supporting an application protocol procedure set by the WLAN terminal element based on a second communication interface with the control plane element of the cellular BS.In at least some example embodiments, the application protocol procedure set includes at least one of the following: an initialization procedure configured to support the initialization of a WLAN terminal element; a configuration procedure configured to support the configuration of a WLAN terminal element; a deactivation procedure configured to support the deactivation of a WLAN terminal element; an association procedure configured to support the association of a terminal device with a WLAN terminal element; a bearer context establishment procedure configured to support the establishment of a bearer context for CWRC bearers; a bearer context modification procedure configured to support the modification of a bearer context for CWRC bearers; a bearer context release procedure configured to support the release of a bearer context for CWRC bearers; a statistics subscription procedure configured to support the subscription of a control plane element of a cellular BS to receive statistics from the WLAN terminal element; and a statistics reporting procedure configured to support the reporting of statistics from the WLAN terminal element to the control plane element of the cellular BS. In at least some example embodiments, the WLAN terminal element includes a Next Generation Wireless Local Area Network (WLAN) Termination (NG-WT) element.

[0011] In at least some example embodiments, a computer-readable storage medium includes computer program code that, when executed by a device, causes the device to at least perform: supporting a set of communication interfaces for a radio access network (RAN) by a wireless local area network (WLAN) terminal element, the RAN including cellular base stations (BS), wherein the set of communication interfaces includes: a first communication interface configured to support access to the WLAN by the set of terminal devices; a second communication interface configured to support communication with a control plane element of the cellular BS; and a third communication interface configured to support communication with a user plane element of the cellular BS; and supporting a cellular-WLAN RAN convergence (CWRC) bearer by the WLAN terminal element based on the set of communication interfaces. In at least some example embodiments, the computer program code, when executed by a device, causes the device to at least perform: supporting a state machine by the WLAN terminal element, the state machine supporting a set of states, wherein the set of states includes an idle state, an active state, an associated state, and a connected state. In at least some example embodiments, when executed by a device, the computer program code causes the device to perform at least the following: sending an initialization request message to a control plane element of a cellular BS, the initialization request message being configured to request initialization of the WLAN terminal element; and receiving an initialization response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by a device, the computer program code causes the device to perform at least the following: receiving a configuration update message from the control plane element of the cellular BS, the configuration update message being configured to update the usage in the configuration information of the WLAN terminal element; and sending a configuration update confirmation message to the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: sending a configuration update message to the control plane element of the cellular BS, the configuration update message indicating an update to the configuration information of the WLAN terminal element; and receiving a configuration update confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: receiving a deactivation request message from a control plane element of a cellular BS by a WLAN terminal element, the deactivation request message being configured to request deactivation of the WLAN terminal element; and sending a deactivation response message from a control plane element of the cellular BS by the WLAN terminal element.In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: sending a terminal device association message to a control plane element of a cellular BS, the terminal device association message being configured to indicate an association between a terminal device and the WLAN terminal element; and receiving a terminal device association confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: receiving a CWRC bearer context establishment request message from the control plane element of the cellular BS by the WLAN terminal element, the CWRC bearer context establishment request message being configured to request the establishment of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context establishment response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, when executed by a device, the computer program code causes the device to perform at least the following: receiving a CWRC bearer context modification request message from a control plane element of a cellular BS, the CWRC bearer context modification request message being configured to request modification of the context used for CWRC bearers within the WLAN terminal element; and sending a CWRC bearer context modification response message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: receiving a CWRC bearer context release request message from a control plane element of the cellular BS, the CWRC bearer context release request message being configured to request release of the context used for CWRC bearers within the WLAN terminal element; and sending a CWRC bearer context release response message from the control plane element of the cellular BS. In at least some example embodiments, when executed by at least one processor, the computer program code causes the device to perform at least the following: supporting an application protocol procedure set by the WLAN terminal element based on a second communication interface with the control plane element of the cellular BS.In at least some example embodiments, the application protocol procedure set includes at least one of the following: an initialization procedure configured to support the initialization of a WLAN terminal element; a configuration procedure configured to support the configuration of a WLAN terminal element; a deactivation procedure configured to support the deactivation of a WLAN terminal element; an association procedure configured to support the association of a terminal device with a WLAN terminal element; a bearer context establishment procedure configured to support the establishment of a bearer context for CWRC bearers; a bearer context modification procedure configured to support the modification of a bearer context for CWRC bearers; a bearer context release procedure configured to support the release of a bearer context for CWRC bearers; a statistics subscription procedure configured to support the subscription of a control plane element of a cellular BS to receive statistics from the WLAN terminal element; and a statistics reporting procedure configured to support the reporting of statistics from the WLAN terminal element to the control plane element of the cellular BS. In at least some example embodiments, the WLAN terminal element includes a Next Generation Wireless Local Area Network (WLAN) Termination (NG-WT) element.

[0012] In at least some example embodiments, a method includes: a set of communication interfaces supported by a wireless local area network (WLAN) terminal element for a radio access network (RAN), the RAN including a cellular base station (BS), wherein the set of communication interfaces includes: a first communication interface configured to support access to the WLAN by the set of terminal devices; a second communication interface configured to support communication with a control plane element of the cellular BS; and a third communication interface configured to support communication with a user plane element of the cellular BS; and, based on the set of communication interfaces, the WLAN terminal element supports a cellular-WLAN RAN convergence (CWRC) bearer. In at least some example embodiments, the method further includes: a state machine supported by the WLAN terminal element, the state machine supporting a set of states, wherein the set of states includes an idle state, an active state, an associated state, and a connected state. In at least some example embodiments, the method further includes: the WLAN terminal element sending an initialization request message to a control plane element of the cellular BS, the initialization request message being configured to request initialization of the WLAN terminal element; and receiving an initialization response message from the control plane element of the cellular BS via the WLAN terminal element. In at least some example embodiments, the method further includes: receiving a configuration update message from a control plane element of a cellular BS by a WLAN terminal element, the configuration update message being configured to update the usage in the configuration information of the WLAN terminal element; and sending a configuration update confirmation message to the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the method further includes: sending a configuration update message to the control plane element of the cellular BS by the WLAN terminal element, the configuration update message indicating an update to the configuration information of the WLAN terminal element; and receiving a configuration update confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the method further includes: receiving a deactivation request message from the control plane element of the cellular BS by the WLAN terminal element, the deactivation request message being configured to request the deactivation of the WLAN terminal element; and sending a deactivation response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the method further includes: sending a terminal device association message to the control plane element of the cellular BS by the WLAN terminal element, the terminal device association message being configured to indicate an association between the terminal device and the WLAN terminal element; and receiving a terminal device association confirmation message from the control plane element of the cellular BS by the WLAN terminal element.In at least some example embodiments, the method further includes: receiving a CWRC bearer context establishment request message from a control plane element of a cellular BS, the CWRC bearer context establishment request message being configured to request the establishment of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context establishment response message from the control plane element of the cellular BS. In at least some example embodiments, the method further includes: receiving a CWRC bearer context modification request message from a control plane element of the cellular BS, the CWRC bearer context modification request message being configured to request the modification of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context modification response message from the control plane element of the cellular BS. In at least some example embodiments, the method further includes: receiving a CWRC bearer context release request message from a control plane element of the cellular BS, the CWRC bearer context release request message being configured to request the release of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context release response message from the control plane element of the cellular BS. In at least some example embodiments, the method further includes: a set of application protocol procedures supported by the WLAN terminal element based on a second communication interface with the control plane element of the cellular BS. In at least some example embodiments, the set of application protocol procedures includes at least one of the following: an initialization process configured to support the initialization of the WLAN terminal element; a configuration process configured to support the configuration of the WLAN terminal element; a deactivation process configured to support the deactivation of the WLAN terminal element; an association process configured to support the association between the terminal device and the WLAN terminal element; a bearer context establishment process configured to support the establishment of a bearer context for CWRC bearers; a bearer context modification process configured to support the modification of a bearer context for CWRC bearers; a bearer context release process configured to support the release of a bearer context for CWRC bearers; a statistics subscription process configured to support the subscription of the control plane element of the cellular BS to receive statistics from the WLAN terminal element; and a statistics reporting process configured to support the reporting of statistics from the WLAN terminal element to the control plane element of the cellular BS. In at least some example embodiments, the WLAN terminal element includes a next-generation wireless local area network (WLAN) termination (NG-WT) element.

[0013] In at least some example embodiments, an apparatus includes: components for supporting a set of communication interfaces for a radio access network (RAN) by a wireless local area network (WLAN) terminal element, the RAN including a cellular base station (BS), wherein the set of communication interfaces includes: a first communication interface configured to support access to the WLAN by the set of terminal devices; a second communication interface configured to support communication with a control plane element of the cellular BS; and a third communication interface configured to support communication with a user plane element of the cellular BS; and components for supporting cellular-WLAN RAN convergence (CWRC) bearers by the WLAN terminal element based on the set of communication interfaces. In at least some example embodiments, the apparatus further includes: components for supporting a state machine by the WLAN terminal element, the state machine supporting a set of states, wherein the set of states includes an idle state, an active state, an associated state, and a connected state. In at least some example embodiments, the apparatus further includes: means for sending an initialization request message from a WLAN terminal element to a control plane element of a cellular BS, the initialization request message being configured to request initialization of the WLAN terminal element; and means for receiving an initialization response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for receiving a configuration update message from the control plane element of the cellular BS by the WLAN terminal element, the configuration update message being configured to update the usage in the configuration information of the WLAN terminal element; and means for sending a configuration update confirmation message from the WLAN terminal element to the control plane element of the cellular BS. In at least some example embodiments, the apparatus further includes: means for sending a configuration update message from the WLAN terminal element to the control plane element of the cellular BS, the configuration update message indicating an update of the configuration information of the WLAN terminal element; and means for receiving a configuration update confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for receiving a deactivation request message from a control plane element of a cellular BS by a WLAN terminal element, the deactivation request message being configured to request deactivation of the WLAN terminal element; and means for sending a deactivation response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for sending a terminal device association message from the WLAN terminal element to the control plane element of the cellular BS, the terminal device association message being configured to indicate association between the terminal device and the WLAN terminal element; and means for receiving a terminal device association confirmation message from the control plane element of the cellular BS by the WLAN terminal element.In at least some example embodiments, the apparatus further includes: means for receiving a CWRC bearer context establishment request message from a control plane element of a cellular BS by a WLAN terminal element, the CWRC bearer context establishment request message being configured to request the establishment of a context for CWRC bearer within the WLAN terminal element; and means for sending a CWRC bearer context establishment response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for receiving a CWRC bearer context modification request message from the control plane element of the cellular BS by a WLAN terminal element, the CWRC bearer context modification request message being configured to request the modification of a context for CWRC bearer within the WLAN terminal element; and means for sending a CWRC bearer context modification response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for receiving a CWRC bearer context release request message from a control plane element of a cellular BS by a WLAN terminal element, the CWRC bearer context release request message being configured to request the release of a context within the WLAN terminal element used for a CWRC bearer; and means for sending a CWRC bearer context release response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments, the apparatus further includes: means for the WLAN terminal element to support a set of application protocol procedures based on a second communication interface with the control plane element of the cellular BS. In at least some example embodiments, the application protocol procedure set includes at least one of the following: an initialization procedure configured to support the initialization of a WLAN terminal element; a configuration procedure configured to support the configuration of a WLAN terminal element; a deactivation procedure configured to support the deactivation of a WLAN terminal element; an association procedure configured to support the association of a terminal device with a WLAN terminal element; a bearer context establishment procedure configured to support the establishment of a bearer context for CWRC bearers; a bearer context modification procedure configured to support the modification of a bearer context for CWRC bearers; a bearer context release procedure configured to support the release of a bearer context for CWRC bearers; a statistics subscription procedure configured to support the subscription of a control plane element of a cellular BS to receive statistics from the WLAN terminal element; and a statistics reporting procedure configured to support the reporting of statistics from the WLAN terminal element to the control plane element of the cellular BS. In at least some example embodiments, the WLAN terminal element includes a Next Generation Wireless Local Area Network (WLAN) Termination (NG-WT) element. Attached Figure Description

[0014] The teachings herein can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

[0015] Figure 1 An example embodiment of a Cellular-WLAN RAN Convergence (CWRC) system is shown, which is configured to support Cellular-WLAN RAN convergence based on the use of Next Generation Wireless LAN (NG-WT).

[0016] Figure 2 An example embodiment of NG-WT is shown to illustrate... Figure 1 An example embodiment of the protocol stack used for NG-WT in the CWRC system;

[0017] Figure 3 It shows that it can be made by Figure 1 Example embodiments of the three cellular-WLAN convergence bearer types supported by the CWRC system;

[0018] Figure 4 An example embodiment of an NG-WT-initiated initialization process to provide WLAN-related capability information to gNB-CU-CP is shown;

[0019] Figure 5 An example embodiment of the NG-WT state machine is shown, which is used by NG-WT to enable the transition between the idle state and the connected state;

[0020] Figure 6 An example embodiment of an NG-WT configuration update process initiated by gNB and used by gNB-CU-CP to update the configuration of NG-WT associated with gNB-CU-CP is shown.

[0021] Figure 7 An example embodiment of an NG-WT-initiated NG-WT configuration update process used by NG-WT to notify gNB-CU-CP of changes to the configuration of NG-WT, which may have been triggered by a non-3GPP node, is shown.

[0022] Figure 8 An example embodiment of the NG-WT deactivation process for deactivation of NG-WT using gNB-CU-CP is shown;

[0023] Figure 9 An example embodiment of the NG-WT UE association process used by NG-WT to notify gNB-CU-CP of new UE associations is shown;

[0024] Figure 10An example embodiment of the CWRC bearer context establishment process is shown, which is used to establish a bearer context within NG-WT as part of the establishment of the CWRC bearer;

[0025] Figure 11 An example embodiment of the CWRC bearer context modification process is shown, which is used to modify the bearer context within NG-WT, including modifying the configuration of existing bearers, creating new bearers, and releasing existing bearers;

[0026] Figure 12 An example embodiment of the CWRC bearer context release procedure is shown, which is used to release all active CWRC bearers associated with a specific UE;

[0027] Figure 13 An example embodiment of an NG-WT statistics subscription process used by gNB-CU-UP to initiate, modify, or delete one or more statistics subscriptions at NG-WT is shown;

[0028] Figure 14 An example embodiment of the bearer context establishment process configured to enable CWRC bearer establishment is shown;

[0029] Figure 15 An example embodiment of a bearer context release procedure initiated by the control plane and configured to enable CWRC bearer release is shown;

[0030] Figure 16 An example embodiment of a bearer context release procedure initiated by the user plane and configured to enable CWRC bearer release is shown;

[0031] Figure 17 An example embodiment of a method for use by NG-WT to support cellular-WLAN RAN convergence in a RAN is shown;

[0032] Figure 18 An example embodiment of a method for use by the control elements of the RAN to support cellular-WLAN RAN convergence in the RAN is shown;

[0033] Figure 19 An example embodiment of a method for use by WLAN terminal elements in a RAN to support cellular-WLAN RAN convergence is shown;

[0034] Figure 20 An example embodiment of a method used by a terminal device to support cellular-WLAN RAN convergence in a RAN is shown; and

[0035] Figure 21Example embodiments of computers suitable for performing the various functions described herein are shown.

[0036] For ease of understanding, the same reference numerals have been used as much as possible in this document to indicate the same common elements in the figures. Detailed Implementation

[0037] Various example implementations of Cellular-Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) capabilities are presented. This CWRC capability can be configured to support architectural and procedural solutions for enabling Layer 2 (L2) convergence between cellular and WLAN access within the RAN. The CWRC capability can be configured to support architectural and procedural solutions for enabling L2 convergence between cellular and WLAN access within the RAN in a manner that supports various types of applications, such as Mixed Reality (MR) applications, Extended Reality (XR) applications, and various combinations thereof. The CWRC capability can be configured to support extensions to the 3GPP system architecture to merge WLAN access within the 3GPP access network (typically referred to as the RAN), including extensions to the 3GPP control plane to support critical WLAN operations and performance measurement reporting extensions to the 3GPP user plane to merge various convergence mechanisms for cellular and WLAN traffic, providing associated control plane and user plane interfaces and procedures to support the aforementioned capabilities and their various combinations. CWRC capabilities can be configured to support a CWRC system architecture that includes nodes—referred to as Next-Generation WLAN Terminals (NG-WTs)—configured to terminate WLAN access within the RAN. CWRC capabilities can also be configured to support a new set of bearer types—three of which are referred to herein as CWRC Bearer Types A, B, and C—configured to enable user traffic aggregation across a variety of different scenarios. CWRC capabilities can be configured to support a set of communication interfaces for NG-WT, including interfaces for supporting communication between NG-WT and User Equipment (UE), and interfaces between NG-WT and Next Generation Node B Centralized Unit (gNB-CU). The interface between NG-WT and gNB-CU may include a control plane interface between NG-WT and gNB-CU control plane (gNB-CU-CP) elements (where such an interface may be referred to as Xnw-C), and a user plane interface between NG-WT and gNB-CU user plane (gNB-CU-UP) elements (where such an interface may be referred to as Xnw-U). Either or both of these can be supported by the new XnwAP protocol and a full suite of XnwAP system procedures and interactions. CWRC capabilities can be configured to support a full set of call flows to enable seamless CWRC operation for supporting cellular-WLAN RAN convergence. CWRC capabilities can be configured to support various enhancements to various 3GPP system procedures (e.g., E1AP bearer context establishment) for supporting cellular-WLAN RAN convergence.CWRC capabilities can also be configured to support various enhancements to a variety of protocols, including UE-side protocols and network-side protocols (e.g., Radio Resource Control (RRC) protocol, Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), and various combinations thereof), to support cellular-WLAN RAN convergence. It should be understood that these, and various other example embodiments, can be further understood by first considering various aspects of cellular systems more broadly.

[0038] As networks evolve from fourth-generation (4G) and fifth-generation (5G) networks to 5G-A, sixth-generation (6G), and beyond, industry and the enterprise sector have been working to bring emerging applications such as immersive mixed reality (MR), extended reality (XR), and others to fruition. Therefore, enterprise networks need to deliver ubiquitous wireless experiences that prioritize both high bandwidth and low latency to seamlessly handle such data-intensive applications. Anchored to both licensed and unlicensed spectrum, such networks are expected to require extremely high deployment flexibility, optimized interoperability, fine-grained control, and compatibility with commercial off-the-shelf (COTS) hardware. While traditional enterprise verticals have been served by WLAN, with the advent of dedicated 5G, WLAN and 3GPP cellular access often find themselves competing with each other in serving the same applications. Although most enterprise traffic currently flows through WLAN due to its widespread presence, WLAN-based networks typically suffer from performance limitations (e.g., interference) and struggle to consistently guarantee resources for latency-sensitive applications such as MR and XR. On the other hand, the centralized control and resource guarantees offered by cellular networks make them better suited for ensuring a smooth MR / XR experience. Therefore, strategically integrating the advantages of widely deployed WLANs with the structured characteristics of cellular networks enables both enterprises and service providers to deploy robust, scalable, and cost-effective enterprise networks, delivering the high-performance connectivity required by modern applications. Various example embodiments can be configured to support cellular-WLAN convergence based on RAN-level integration of cellular and WLAN radio access technologies (RATs). This allows service providers to seamlessly split, route, and exchange data streams between different RATs in a transparent manner to the core network. The proposed Layer 2 convergence is configured to enable the use of the 3GPP control plane to manage WLAN-related operations, thereby ensuring the high-quality user experience (QoE) required by modern applications.

[0039] 3GPP introduced limited support for RAN-centric multi-access capabilities in LTE through the WLAN Aggregated Link (LWA) and LTE-WLAN Radio Layer Integration with Internet Protocol Security (IPSec) Tunneling (LWIP) specifications, including Radio Termination (WT) entities and the XwAP and Xw-U protocols. While LWA attempts to provide multi-access RAN, certain characteristics limit its widespread adoption. First, LWA operation is typically eNB-centric, leaving little room for functional autonomy in WT. Second, statistical collection capabilities are limited, and it does not utilize advanced statistical features supported by IEEE 802.11k / r and 802.11v. Third, LWA does not allow for fine-grained traffic engineering of cellular and WLAN RATs, limiting its practical application in large enterprise environments. Furthermore, the LWA specification has not been updated for NR and NG-RAN, therefore, LWA may not be suitable for modern enterprise networks. On the other hand, LWIP introduces additional overhead due to its use of IPSec tunnels, while typically offering lower performance than LWA. Additionally, standardization efforts within 5G NR focus on integrating WLAN networks with the 5G core network through features such as Non-3GPP Interoperability Function (N3IWF), 5G Trusted Non-3GPP Gateway Function (TNGF), and Trusted WLAN Interoperability Function (TWIF). While N3IWF handles untrusted non-3GPP access, TNGF and TWIF are used for trusted non-3GPP access. Initially, untrusted access via N3IWF introduces significant overhead due to the presence of two separate IP layers, a GRE header, an IPSec header, and additional IPSec tunnel encryption. Nevertheless, both N3IWF and TNGF allow the 5G Access Traffic Bootstrapping, Switching, and Splitting (ATSSS) option for traffic bootstrapping, switching, and splitting. Network functions associated with ATSSS are deployed at both the UE and the UPF (5G core network). On the network side, the UPF serves as the aggregation point for cellular and WLAN access. ATSSS uses MPTCP / MPQUIC or a lower-layer multilink technology called ATSSS-LL. Regarding MPTCP and MPQUIC, note that as transport layer protocols, MPTCP and MPQUIC are invisible to lower layers, rendering them ineffective for L1 / L2 optimizations and thus suboptimal for wireless aggregation scenarios. On the other hand, ATSSS-LL lacks upper-layer protocols for providing switching and splitting services, thus ATSSS-LL is relegated to a traffic handover function. When comparing RAN-centric and core-network-centric integration approaches, it should be noted that RAN-centric approaches typically suffer from similar drawbacks to LWA, while core-network-centric approaches often lack LWA counterparts and may have other disadvantages (e.g., negative impacts of MEC, LBO inoperability, etc.).Based on various example embodiments, these embodiments can be configured to overcome various drawbacks or potential disadvantages of such RAN-centric and core-network-centric integration approaches, thereby supporting architectural and process solutions for achieving L2 convergence between cellular access and WLAN access within the RAN.

[0040] Various example implementations are configured to support intra-RAN cellular-WLAN convergence based on Layer 2 convergence between intra-RAN cellular and WLAN access. Intra-RAN support for cellular-WLAN convergence can be based on architectural and process solutions to enable Layer 2 convergence between intra-RAN cellular and WLAN access (e.g., providing improved or even optimized performance for various types of applications, including emerging applications in the MR domain). Intra-RAN support for cellular-WLAN convergence can be based on a CWRC system architecture that introduces a node called Next-Generation WLAN Termination (NG-WT) for terminating WLAN access within the RAN. Intra-RAN support for cellular-WLAN convergence can also be based on new CWRC bearer sets, which may include CWRC bearer types A, B, and C, to enable the convergence of user traffic in various scenarios. Support for cellular-WLAN convergence within the RAN can be based on the interface between the NG-WT and gNB-CU (referred to as the Xnw interface), which may include a control plane component (referred to as Xnw-C) between the NG-WT and gNB-CU-CP, and a user plane component (referred to as Xnw-U) between the NG-WT and gNB-CU-UP. Either or both of these can be supported by the new XnwAP protocol and associated XnwAP system procedures and interaction suites. Support for cellular-WLAN convergence within the RAN can also be based on call flow sets configured to enable seamless CWRC operation. Support for cellular-WLAN convergence within the RAN can also be based on various enhancements to various 3GPP system procedures (e.g., E1AP bearer context establishment) to enable the proposed convergence. Support for cellular-WLAN convergence within the RAN can be based on enhancements to both network-side and UE-side protocols (e.g., RRC, PDCP, SDAP, etc.) to allow the proposed convergence mechanism. Support for cellular-WLAN aggregation within the RAN can be based on the gNB-CU-CP configuration to integrate support for the new XnwAP protocol (which operates on the control plane interface between gNB-CU-CP and NG-WT), support for XnwAP operation procedures, integration of E1AP extensions to allow compatibility with CWRC bearers, integration of RRC extensions for managing CWRC bearers, and more. Support for cellular-WLAN aggregation within the RAN can also be based on the gNB-CU-UP configuration to integrate SDAP and PDCP extensions, allowing traffic mapping, redirection, switching, and splitting operations associated with CWRC bearers. Finally, support for cellular-WLAN aggregation within the RAN can be based on the NG-WT configuration to integrate support for the new XnwAP protocol (which operates on the control plane interface between gNB-CU-CP and NG-WT), support for XnwAP operation procedures, and the introduction of a new state machine for managing CWRC operations, and more.Support for cellular-WLAN aggregation within the RAN can be based on UE configuration to integrate RRC extensions (enabling management and configuration of CWRC bearers), SDAP and PDCP extensions (allowing traffic mapping, redirection, switching, and splitting operations associated with CWRC bearers), and so on. It should be understood that these, and various other embodiments, can be referenced as follows. Figure 1 The example CWRC system architecture shown is further understood.

[0041] Figure 1 An example embodiment of a cellular-WLAN RAN convergence (CWRC) system configured to support cellular-WLAN RAN convergence is shown.

[0042] like Figure 1 As shown, the CWRC system 100 includes a set of network devices that support communication between sets of UEs 101-1 to 101-N (collectively referred to as UE 101). This set of network devices includes an NG-WT 110 set, a gNB-DU 120 set, a gNB-CU-CP 130 set, a gNB-CU-UP 140 set, and a 5G core network (5GC) 150. The NG-WT 110 supports a WLAN interface 111 with UE 101 for WLAN-based communication. The gNB-DU 120 supports an NR-Uu interface 112 with UE 101 for cellular-based communication. The NG-WT 110 is configured to interface with the gNB-CU-CP 130 via an Xnw-C interface 131 and with the gNB-CU-UP 130 via an Xnw-U interface 141. The gNB-DU 120 is configured to interface with the gNB-CU-CP 130 via the F1-C interface 132 and with the NB-CU-UP 130 via the F1-U interface 142. The gNB-CU-CP 130 is configured to interface with the gNB-CU-CP via the E1 interface 135. The gNB-CU-CP 130 is configured to interface with the 5GC via the NG-C interface 151. The gNB-CU-UP 140 is configured to interface with the 5GC via the NG-U interface 152. It should be understood that although this description is primarily for de-aggregated RAN deployments (e.g., where the gNBs are de-aggregated into separate elements), monolithic RAN deployments (e.g., using integrated gNBs, where the NG-WT 110 interfaces with the gNBs via the Xnw-C and Xnw-U interfaces) can also be used.

[0043] In CWRC system 100, UE 101 may include any terminal device capable of wireless communication based on both cellular and WLAN communication. For example, UE 101 may include cellular phones, mobile phones, tablets, personal digital assistants, laptops, desktop computers, gaming devices, wireless endpoints, mobile stations, smart devices, Internet of Things (IoT) devices, consumer electronics, gaming systems, industrial equipment, medical devices, in-vehicle devices, vehicles, drones, head-mounted displays, and various combinations thereof. It should be understood that although this document primarily presents example embodiments of terminal devices communicating via CWRC system 100 as UEs (e.g., UE 101), various other types of terminal devices may also communicate via the CWRC system (e.g., terminal devices such as subscriber stations (SS), portable subscriber stations (PSS), mobile stations (MS), access terminals (AT), etc.).

[0044] In the CWRC system 100, network devices can be configured to support cellular-WLAN aggregation within the RAN. The network devices can be configured to support cellular-WLAN aggregation within the RAN based on support for Layer 2 aggregation between cellular access and WLAN access within the RAN. NG-WT 110 and gNB-CU-CP 130 can be configured to support cellular-WLAN aggregation within the RAN based on support for the XnwAP protocol, which operates on the Xnw-C interface 131 between NG-WT 110 and gNB-CU-CP 130. This XnwAP protocol can support various procedures for supporting cellular-WLAN aggregation within the RAN (e.g., NG-WT initialization, gNB-initiated NG-WT configuration update, NG-WT-initiated NG-WT configuration, NG-WT deactivation, NG-WT UE association, CWRC bearer context establishment, CWRC bearer context modification, CWRC bearer context release request, CWRC bearer context release, NG-WT statistics subscription, NG-WT statistics reporting, etc.).

[0045] In CWRC System 100, network devices can be configured to support cellular-WLAN convergence within the RAN based on support for various other capabilities. For example, support for cellular-WLAN convergence within the RAN can be based on NG-WT 110 (an example implementation of which is...) Figure 2 The configuration shown is used to introduce a new state machine for managing CWRC operations (an example implementation of which is shown in the image). Figure 3As shown in the figure, to integrate support for XnwAP operation procedures based on the XnwAP protocol, which operates on the Xnw-C interface 131 between NG-WT 110 and gNB-CU-CP 130 (example implementations of which are shown in the figure). Figure 4-13 (as shown in the diagram). For example, support for cellular-WLAN aggregation within the RAN can be based on the configuration of gNB-CU-CP 130 to integrate support for XnwAP operation procedures; integrate support for XnwAP operation procedures based on the XnwAP protocol, which operates on the control plane interface between gNB-CU-CP and NG-WT; integrate support for XnwAP operation procedures based on the XnwAP protocol, which operates on the Xnw-C interface 131 between NG-WT 110 and gNB-CU-CP 130 (example implementations include, for example...). Figure 4-13 (as shown in the diagram); integrate E1AP extensions to allow compatibility with CWRC bearers; integrate RRC extensions to enable management of CWRC bearers; integrate SDAP and PDCP extensions to support CWRC bearers (e.g., allowing traffic mapping, redirection, switching, and splitting operations associated with CWRC bearers), etc.

[0046] Figure 2 An example embodiment of NG-WT is shown to illustrate its use. Figure 1 An example implementation of the NG-WT protocol stack in the CWRC system. For example... Figure 2 As shown, the NG-WT 200 includes a protocol stack comprising a set of protocols, including a WLAN Physical (PHY) layer 210 (e.g., supporting multiple WLAN PHY layer protocols), a WLAN Media Access Control (MAC) layer 220 (e.g., supporting multiple WLAN MAC protocols), a WLAN Logical Link Control (LLC) layer 230 (e.g., supporting multiple WLAN LLC protocols), and a Cellular-WLAN RAN Convergence Protocol (CWRCP) layer 240 (e.g., supporting CWRCP). Figure 2 As shown, the NR-WT200 supports communication with gNB-CU-CP via the Xnw-C interface and with gNB-CU-UP via the Xnw-U interface. It should be understood that, due to the integration of the existing WLAN protocol layer, the NG-WT 200 can be considered to include all the functions associated with a traditional WLAN AP; that is, the NG-WT 200 continues to provide existing WLAN functions to users (UEs) not participating in cellular-WLAN converged data sessions.

[0047] Figure 3 It shows that it can be made by Figure 1Example implementation of three cellular-WLAN convergence bearer types supported by the CWRC system.

[0048] like Figure 3 As shown, the three cellular-WLAN convergence bearer types 310 include CWRC bearer type 310-A ​​(more generally referred to herein as CWRC bearer type A or type A bearer), CWRC bearer type 310-B (more generally referred to herein as CWRC bearer type B or type B bearer), and CWRC bearer type 310-C (more generally referred to herein as type C or type C bearer).

[0049] CWRC bearer type 310-A ​​is characterized by the presence of multiple PDU sessions, thus requiring different SDAP entities. These PDU sessions are then mapped to access-specific (i.e., cellular and WLAN-specific) DRBs represented by corresponding different PDCP entities.

[0050] When QoS flows in a single PDU session are mapped to more than one DRB, CWRC bearer type 310-B is used, where at least one DRB provides WLAN access. In this case, only a single SDAP entity and multiple PDCP entities are required, with one PDCP entity dedicated to each access-specific DRB.

[0051] CWRC bearer type 310-C is characterized by a single DRB with multiple logical channels, at least one of which is associated with WLAN access. In this case, QoS flows in a single PDU session can be mapped to a common PDCP entity and then split across multiple LCIDs (e.g., LCID 1 is associated with cellular access, while LCID 2 is associated with WLAN access), so that these bearers involve common SDAP and PDCP entities with different RLC and CWRC entities.

[0052] It should be noted that the CWRC architecture allows multiple bearer types to be active simultaneously for any given UE, where bearer selection is controlled by the relevant network management policy and configured by the RRC. For bearers utilizing a common PDCP entity (e.g., in the case of CWRC bearer type C), the receiving PDCP entity is responsible for the sequential delivery of packets to higher layers. This sequential delivery can be implemented through a window mechanism with CWRC-specific timeout parameters configured by the RRC during bearer establishment.

[0053] It should be noted that for each of the CWRC bearer types mentioned above, the distribution of downlink traffic across cellular and WLAN access can be fully controlled by the RAN and is completely transparent to the core network, allowing a single IP address for each PDU session even if two physically separate access schemes exist. In this context, the F1-U and Xnw-U interfaces carry GTP-encapsulated PDC PPDUs in both the downlink and uplink directions. This aggregation mechanism is also transparent to the WLAN protocol stack, reusing the existing LWA Ethernet type 0x9E65 for identifying CWRC PPDUs within the UE. Furthermore, the distribution of uplink traffic across cellular and WLAN access is controlled by: reflective QoS for type A bearers, network-provided QoS rules for type B bearers, and the UE-internal RRM mechanism for type C bearers.

[0054] As described above, the CWRC system can support Xnw Application Protocol (XnwAP) procedures configured to support cellular-WLAN RAN convergence. The CWRC system can support Xnw interfaces for interaction between the NG-WT and gNB-CU, including the Xnw-U (user plane) interface between gNB-CU-UP and NG-WT, and the Xnw-C (control plane) interface between gNB-CU-CP and NG-WT. Regarding the Xnw-U interface, note that the Xnw-U interface may be identical to the existing Xw-U interface defined in Technical Specification (TS) 36.465, and furthermore, the CWRC PPDU structure may be identical to the LWAA PPDU structure described in Clause 6 of TS 36.360. However, regarding the Xnw-C interface, the Xnw-C interface may differ significantly from the existing Xw-C interface defined in TS 36.463; therefore, both may include enhancements in terms of procedures and the information exchanged as part of these procedures. These enhancements may be based on XnwAP, which can be used as an application-layer signaling protocol operating through the Xnw-C interface. XnwAP may include the procedures outlined in Table 1 below. Table 1

[0055] Figure 4 An example embodiment of an initialization process initiated by NG-WT to provide WLAN-related capability information to gNB-CU-CP is shown.

[0056] like Figure 4 As shown, the NG-WT initialization process 400 involves operations via the NG-WT and gNB-CU-CP, including message exchange between the NG-WT and gNB-CU-CP. This process uses signaling not associated with the UE.

[0057] At step 410, NG-WT sends an NG-WT initialization request to gNB-CU-CP. The NG-WT initialization request message includes details related to NG-WT-specific identification information and WLAN-related capability information, which may take the form of the following information elements (IEs): ● NG-WTID: Uniquely identifies a given NG-WT within a specific PLMN. ● NG-WT Capability Information: Provides a list of WLAN-related capabilities supported by NG-WT, including but not limited to the following parameters. ◆WLAN operation category: such as the WLAN operation category defined in the IEEE 802.11 specification. ◆WLAN country code: such as the WLAN country code defined in the IEEE 802.11 standard. ◆ List of supported WLAN specifications: for example, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, etc. ◆802.11ax / be specific parameters– ● Resource Unit (RU) information for the selected channel ●Supports broadcast target wake-up time ◆MIMO Configuration: Provides information about the number of MIMO streams supported by NG-WT. ◆List of supported WLAN frequency bands: for example, 2.4GHz, 5GHz, 6GHz, 60GHz. ◆Transmit power: Maximum transmit power (dBm) supported by NG-WT. ◆Retry: The maximum number of L2 retries that NG-WT can attempt for a given group before failure. ◆MCS value: The maximum MCS value supported by NG-WT. ◆Guard band value: Provides the guard band spacing supported by NG-WT. ◆FTM Support: Provides information on whether NG-WT supports fine time measurement.

[0058] At step 420, the gNB-CU-CP responds to the NG-WT initialization response if initialization is successful (marked as step 420-A), or fails to initialize if initialization fails (marked as step 420-B). If initialization is successful and the gNB-CU-CP sends the NG-WT initialization response message, the gNB-CU-CP configures WLAN-specific parameters in the NG-WT as part of the NG-WT initialization response 420-A. The RAN only allows association and establishment with the CWRC-related bearer and the UE for a given NG-WT context upon successful completion of the NG-WT initialization process. The NG-WT initialization response message sent by the gNB-CU-CP may include the following information elements (IEs): ●Global RAN Node ID: Identifies information used for gNB-CU-CP. ●NG-WT ID: Information that identifies the NG-WT. ●NG-WT Configuration Information: A list of parameters used to configure NG-WT operations and their corresponding values, including but not limited to the following: ◆Operating Procedures: Operating procedures selected by gNB-CU-CP. ◆Transmit power: such as the maximum transmit power selected by gNB-CU-CP. ◆Retry: Maximum number of retries selected by gNB-CU-CP. ◆MCS value: such as the maximum MCS value selected by gNB-CU-CP. ◆SSID: The SSID that will be used by NG-WT for CWRC operations, as defined in the 802.11 specification. ◆Channel Selection: Select the channel (center frequency) and bandwidth. ◆Specific parameters for 802.11ax / be (WLAN6 / 7): ●Guidelines for the number of resource units and RU allocation for UEs ◆ Protection interval duration ●NG-WT operating status: for example, idle, active, active, associated, connected.

[0059] Regarding the aforementioned operational state IE, NG-WT can exist in one of the four states defined below. ● Idle: NG-WTs in idle state do not broadcast any CWRC-related SSIDs. Note that when an NG-WT is in idle state, its associated AP can still participate in regular WLAN operations unrelated to CWRC. ● Activated: NG-WT broadcasts SSIDs related to CWRC while in an activated state, but does not allow CWRC-related UE associations or the creation of CWRC bearers. ● Active: NG-WT in the associated state broadcasts CWRC-related SSIDs and allows CWRC-related UEs to associate, but there are no UEs associated with it yet. ● Associated: An NG-WT broadcasts a CWRC-related SSID in an associated state and has an associated CWRC UE, but no active CWRC bearer. ● Connected: NG-WT managed CWRC bearer in a connected state broadcasts CWRC-related SSIDs and allows additional CWRC UE associations.

[0060] Note that the difference between the associated state and the connected state is that while the NG-WT in the associated state has UEs associated with it, it does not host any CWRC bearers for activities of those UEs; unlike the connected state, where the NG-WT hosts one or more CWRC bearers for its associated UEs. Furthermore, the transitions between different states are controlled by the NG-WT state machine, such as... Figure 5 As shown in the image.

[0061] Figure 5 An example embodiment of the NG-WT state machine is shown, used by NG-WT to enable the transition between idle and connected states. Figure 5 As shown, upon power-up, the NG-WT is initially in idle state 510. Upon receiving the NG-WT initialization response from its peer gNB-CU-CP, the NG-WT may remain in idle state 510 or transition to active state 520 or active state 530 via an appropriate XnwAP procedure (e.g., a gNB-initiated NG-WT configuration update). Subsequently, the NG-WT in active state 530 transitions to associated state 540 after its first association with the UE. The NG-WT in associated state 540 can transition from associated state 540 to connected state 550 via an XnwAP procedure (such as CWRC bearer context establishment).

[0062] Figure 6 An example embodiment of an NG-WT configuration update process initiated by gNB and used by gNB-CU-CP to update the configuration of the NG-WT associated with gNB-CU-CP is shown.

[0063] like Figure 6As shown, the NG-WT initialization process 600 initiated by the gNB involves operations using both the NG-WT and gNB-CU-CP, including message exchange between the NG-WT and gNB-CU-CP. This process uses signaling not associated with the UE.

[0064] At step 610, gNB-CU-CP sends an NG-WT configuration update to NG-WT. The NG-WT configuration update message includes the following IE. • Global RAN Node ID • NG-WT ID • NG-WT configuration information • NG-WT operating status

[0065] At step 620, if the update is at least partially successful, NG-WT responds with an NG-WT configuration update acknowledgment (marked as step 620-A), or if initialization fails, the NG-WT configuration update fails (marked as step 620-B). Upon receiving an NG-WT configuration update message from gNB-CU-CP, NG-WT updates its configuration parameters as outlined in the request.

[0066] The NG-WT configuration update confirmation message conveys the results associated with each item in the NG-WT configuration information list and includes the following IEs: • Global RAN Node ID • NG-WT ID • NG-WT configuration information results: Indicates the success (or failure) of the configuration item for each request. • NG-WT Operation Status Result: Indicates the success (or failure) of the requested operation status.

[0067] If NG-WT fails to perform configuration updates for all items in the NG-WT configuration information list, and fails to update their operational status, an NG-WT configuration update failure message is sent. NG-WT configuration update failures destined for gNB-CU-CP can include appropriate reason values.

[0068] Note that gNB-CU-CP cannot be used as part of a gNB-initiated NG-WT configuration update routine to directly force a state transition from associated or connected states; instead, if a transition from connected states is required, gNB-CU-UP will first release all bearers associated with NG-WT through a gNB-initiated CWRC bearer release procedure.

[0069] Figure 7An example embodiment of an NG-WT-initiated NG-WT configuration update process used by NG-WT to notify gNB-CU-CP of changes to the configuration of NG-WT, which may have been triggered by a non-3GPP node, is shown.

[0070] like Figure 7 As shown, the NG-WT configuration update procedure 700 initiated by NG-WT involves operations via NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. This allows gNB-CU-CP to update any information it may have regarding the configuration parameters of NG-WT. The procedure uses non-UE associated signaling.

[0071] At step 710, gNB-CU-CP sends an NG-WT configuration update to gNB-CU-CP. This NG-WT configuration update message includes the following IE: • Global RAN Node ID • NG-WT ID • NG-WT configuration information • NG-WT operating status

[0072] At step 720, gNB-CU-CP responds with an NG-WT configuration update confirmation. Since the NG-WT configuration has already been updated, gNB-CU-CP sets all result-related IEs to success. Therefore, the NG-WT configuration update process initiated by NG-WT does not produce any unsuccessful result messages.

[0073] The NG-WT configuration update confirmation message conveys the results associated with each item in the NG-WT configuration information list and includes the following IE. • Global RAN Node ID • NG-WT ID • NG-WT configuration information results: Indicates the success of the configuration item for each request. • NG-WT Operation Status Result: Indicates the success of the requested operation status.

[0074] Figure 8 An example embodiment of the NG-WT deactivation process for deactivation of NG-WT is shown using gNB-CU-CP.

[0075] like Figure 8As shown, the NG-WT deactivation process 800 involves operations via NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. This allows gNB-CU-CP to terminate all CWRC operations associated with NG-WT, release all existing signaling connections associated with XnwAP, and remove any context associated with NG-WT at gNB-CU-CP, as well as any context associated with gNB at NG-WT.

[0076] At step 810, gNB-CU-CP sends an NG-WT deactivation request to NG-WT. If NG-WT is not in a connected state, NG-WT executes the NG-WT activation request (if NG-WT is in a connected state, gNB-CU-CP may perform a state transition through other procedures before attempting the NG-WT deactivation process a second time). The NG-WT deactivation request message includes the following IE: • Global RAN Node ID: Identifies information used for gNB-CU-CP. • NG-WT ID: Information that identifies the NG-WT. • Deactivation reason: CWRC-specific reasons for NG-WT deactivation, such as NG-WT node paused, CWRCC operation paused, persistent performance issues, etc.

[0077] At step 820, if deactivation is successful, NG-WT responds with an NG-WT deactivation response (marked as step 820-A), or if deactivation is unsuccessful, NG-WT deactivation fails (marked as step 820-B). The NG-WT deactivation failure response to gNB-CU-CP may include an appropriate reason value.

[0078] Figure 9 An example embodiment of the NG-WT UE association process used by NG-WT to notify gNB-CU-CP of new UE associations is shown.

[0079] like Figure 9 As shown, the NG-WT UE association procedure 900 involves operations via NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. This allows the establishment of the Xnw-related UE context within NG-WT and gNB-CU-CP prior to the establishment of the CWRC bearer, and upon successful execution of this procedure, a new logical Xnw connection for UE association is established. This procedure uses UE association signaling.

[0080] At step 910, NG-WT sends an NG-WT UE association notification to gNB-CU-CP. The NG-WT UE association notification message includes the following IEs: • NG-WT ID • NG-WT XnAP UE ID: Information that identifies the UE within the NG-WT used for communication via the Xnw interface. • WLAN UE ID: The WiFi MAC address of the UE.

[0081] At step 920, the gNB-CU-CP responds to the NG-WT UE association confirmation. This procedure uses the UE association signaling, and upon receiving the NG-WT UE association notification message, the gNB-CU-CP uses the MAC address contained in the message to identify the existence of the UE context for that signaling within the gNB-CU-CP; that is, the gNB-CU-CP checks whether the UE is known to it. If the NG-WT UE association notification is received for a known UE, the gNB-CU-CP assigns it a gNB UE XnwAP ID and includes it in the NG-WT UE association confirmation response message. Additionally, the gNB-CU-CP also marks the UE as eligible to establish a CWRC bearer. The NG-WT UE association confirmation message may include the following IEs. • Global RAN Node ID • NG-WT ID • NG-WT XnwAP UE ID • gNB XnwAP UE ID: Information that identifies the UE within the gNB-CU-CP used for communication via the Xnw interface.

[0082] Note that, although omitted for clarity, if the gNB-CU-CP is unaware of the notification to the UE to which it is received, the gNB-CU-CP will discard the notification message directly without taking any further action.

[0083] Figure 10 An example embodiment of the CWRC bearer context establishment process is shown, which is used to establish a bearer context within NG-WT as part of establishing a CWRC bearer.

[0084] like Figure 10As shown, the CWRC bearer context establishment procedure 1000 involves operations via the NG-WT and gNB-CU-CP, including message exchange between the NG-WT and gNB-CU-CP. Upon successful completion of the NG-WT UE association procedure, both gNB-CU-CP and NG-WT include relevant context information identifying the specific UE as having active air interfaces on both the cellular (via a given gNB-DU) and WLAN (via the NG-WT). Therefore, the UE is now eligible to establish a CWRC bearer. As part of establishing the CWRC bearer (the detailed call flow will be described below), the gNB-CU-CP utilizes the CWRC bearer context establishment procedure 1000 to establish a bearer context within the NG-WT. Note that the CWRC bearer context establishment procedure 1000 is independent of the specific bearer type (i.e., A, B, or C).

[0085] At step 1010, gNB-CU-CP sends a CWRC bearer context establishment request to NG-WT. The CWRC bearer context establishment request message includes information related to DRB configuration, CWRC horizontal rate control, and uplink GTP-U tunnel information pointing to gNB-CU-UP, as detailed in the following IE: • NG-WT XnwAP UE ID • gNB XnwAP UE ID • Service PLMN: The service PLMN used for this UE. • CWRC rate control: Applied on a per-UE basis, summing all active CWRC bearers at this NG-WT. If enabled, gNB-CU-CP will also specify a rate control target value, i.e., the maximum possible throughput. • List of DRBs to be built: For each item in this list: DRB ID, DRB QoS, S-NSSAI, QoS flow mapped to the DRB, UL user plane tunnel information, DL PDCP SN length, UL PDCP SN length.

[0086] At step 1020, if the establishment is successful, NG-WT responds with a CWRC bearer context establishment response (marked as step 1020-A), or if the establishment fails, the CWRC bearer context establishment fails (marked as step 1020-B). Upon receiving a CWRC bearer context establishment request message from gNB-CU-CP, NG-WT establishes and configures the required CWRC entity according to the parameters received from gNB-CU-CP, and establishes a downlink GTP-U tunnel for each established DRB to allow user plane traffic from gNB-CU-UP. The obtained Tunnel Endpoint Identifier (TEID) is returned to gNB-CU-CP as part of the CWRC bearer context establishment response message, which includes the following IE: • NG-WT XnwAP UE ID • gNB XnwAP UE ID • Service PLMN • DRB creation list: For each item in this list: DRB ID and DL user plane tunnel information. • DRB failure list: For each item in this list: DRB ID and CWRC specific reason.

[0087] If NG-WT fails to establish any requested DRB, a CWRC bearer context establishment failure message is sent. CWRC bearer context establishment failures destined for gNB-CU-CP can include appropriate CWRC-specific reason values.

[0088] Figure 11 An example embodiment of the CWRC bearer context modification process is shown, which is used to modify the bearer context within NG-WT, including modifying the configuration of existing bearers, creating new bearers, and releasing existing bearers.

[0089] like Figure 11 As shown, the CWRC bearer context modification process 1100 involves operations via NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. The CWRC bearer context modification process is used by gNB-CU-CP to modify the configuration of existing bearers, establish new bearers, and release established bearers. Figure 11 As shown, the CWRC bearer context modification process 1100 and Figure 10 The CWRC bearer context establishment process 1000 is similar in terms of the types of messages exchanged.

[0090] At step 1110, gNB-CU-CP sends a CWRC bearer context modification request to NG-WT. In addition to the information included in the CWRC bearer context establishment request message, the CWRC bearer context modification request message includes an additional list, including a list of DRBs to be modified and a list of DRBs to be released, as detailed in the following IE. • NG-WT XnwAP UE ID • gNB XnwAP UE ID • Service PLMN: The service PLMN used for this UE. • CWRC rate control: Applied on a per-UE basis, summing all active CWRC bearers at this NG-WT. If enabled, gNB-CU-CP will also specify a rate control target value, i.e., the maximum possible throughput. • List of DRBs to be built: For each item in this list: DRB ID, DRB QoS, S-NSSAI, QoS flow mapped to the DRB, UL user plane tunnel information, DL PDCP SN length, UL PDCP SN length. • List of DRBs to be modified • List of DRBs to be released ◆DL Forwarding Proposal: If the given DRB sent for its release using the signal belongs to bearer type C, the gNB-CU-CP can request DL data forwarding by including the IE of this DL forwarding proposal in the DRB entry to be released. The IE of the DL forwarding proposal indicates whether forwarding is requested, and if so, includes the UP tunnel information for the forwarding tunnel set at gNB-CU-UP.

[0091] At step 1120, if the modification is successful, NG-WT responds with a CWRC bearer context modification response (marked as step 1120-A), or if the modification fails, the CWRC bearer context modification fails (marked as step 1120-B). Upon receiving a CWRC bearer context modification request message from gNB-CU-CP, NG-WT modifies the required CWRC entity according to the parameters received from gNB-CU-CP.

[0092] In addition to the information included in the CWRC Bearer Context Modification Request message, the CWRC Bearer Context Modification Response message also includes additional lists, including the DRB Modification List, the DRB Failed Modification List, and the DRB Release List, as detailed in the following IE example. • NG-WT XnwAP UE ID • gNB XnwAP UE ID • Service PLMN • DRB creation list: For each item in this list: DRB ID and DL user plane tunnel information. • DRB failure list: For each item in this list: DRB ID and CWRC specific reason. • DRB Modification List • DRB Failure Modification List • DRB Release List: The DRB release list includes an IE that indicates whether NG-WT has accepted (or rejected) a DL data forwarding proposal from gNB-CU-CP.

[0093] In cases where NG-WT cannot modify any of the requested DRBs, a CWRC bearer context modification failure message is sent. A CWRC bearer context modification failure destined for gNB-CU-CP can include an appropriate CWRC-specific reason value.

[0094] Note that NG-WT may not be able to explicitly request bearer context modification. In this case, if NG-WT wishes to proactively update the bearer-related context, NG-WT will first request the bearer's release (via the CWRC bearer context release request process), and then wait for gNB-CU-CP to establish a new bearer. For clarity, from Figure 11 The CWRC bearer context release request procedure, omitted in the text, is used by NG-WT to request the release of one or more CWRC bearers associated with a specific UE. If NG-WT requests the release of all CWRC bearers for a given UE, gNB-CU-CP initiates the CWRC bearer context release procedure; otherwise, gNB-CU-CP initiates the CWRC bearer context modification procedure. The CWRC bearer context release request procedure may include a single message—a CWRC bearer context release request message sent from NG-WT to gNB-CU-CP—including the following IEs: • NG-WT XnwAP UE ID • gNB XnwAP UE ID • DRB Release Request List: For each item in the list: DRB ID.

[0095] Figure 12 An example embodiment of the CWRC bearer context release procedure used to release all active CWRC bearers associated with a specific UE is shown.

[0096] like Figure 12As shown, the CWRC bearer context release procedure 1200 involves operations by NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. The CWRC bearer context release procedure is used by gNB-CU-CP to release all active CWRC bearers associated with a specific UE, and to provide the necessary tunneling information for DL ​​data forwarding for Type C bearers.

[0097] At step 1210, gNB-CU-CP sends a CWRC bearer context release request to NG-WT. The CWRC bearer context release request message includes the following IE: • NG-WT XnwAP UE ID • gNB XnwAP UE ID • List of DRBs to be released: For each item in the list: DRB ID, DL forwarding proposal containing the forwarding request, and forwarding user plane tunnel information.

[0098] At step 1220, NG-WT responds to the CWRC bearer context release complete message. Upon receiving the CWRC bearer context release request message from gNB-CU-CP, NG-WT clears all CWRC bearer-related contexts for a given UE, releases all associated CWRC entities, and suspends the delivery of DL PDCP PDUs. NG-WT may optionally perform DL data forwarding for one or more DRBs in the DRBs for which forwarding is requested. NG-WT's decision regarding forwarding is provided to gNB-CU-CP via the CWRC bearer context release complete message, which includes the following IEs: • NG-WT XnwAP UE ID • gNB XnwAP UE ID • DRB Release List: For each item in the list: DRB ID, DL forwarding result including the forwarding request result (if applicable).

[0099] Figure 13 An example embodiment of an NG-WT statistics subscription process used by gNB-CU-UP to initiate, modify, or delete one or more statistics subscriptions at NG-WT is shown.

[0100] like Figure 13As shown, the NG-WT statistics subscription procedure 1300 involves operations via NG-WT and gNB-CU-CP, including message exchange between NG-WT and gNB-CU-CP. The NG-WT statistics subscription procedure is used by gNB-CU-CP to initiate, modify, or delete one or more statistics subscriptions at NG-WT. This procedure uses signaling not associated with the UE.

[0101] At step 1310, gNB-CU-CP sends an NG-WT subscription request to NG-WT. The NG-WT subscription request message includes a list of subscriptions to be added, modified, or deleted. Note that because a given subscription is associated with the NG-WT itself or with an Xnw context active for it in a UE, the NG-WT subscription request message includes the following IE: ●Global RAN Node ID ●NG-WTID ● List of subscriptions to be added → Subscriptions to be added: ◆Subscription ID: Information used to identify this subscription. ◆Subscription target identifier: NG-WT or UE (with corresponding NG-WT XnwAP UE ID and gNB XnwAP UE ID). ◆Report type: Event-specific report (with a corresponding event) or periodic report (with a corresponding period). ◆Reporting parameters: A list of requested NG-WT or UE-specific measurement parameters. ● The list of subscriptions to be modified → The subscriptions to be modified: ■Subscription ID ■Report Type ■Report Parameters ●List of subscriptions to be deleted → Subscriptions to be deleted: ■Subscription ID

[0102] At step 1320, if the statistics subscription is successful, NG-WT responds with an NG-WT statistics subscription confirmation (marked as step 1320-A), or if the subscription is unsuccessful, NG-WT statistics subscription fails (marked as step 1320-B).

[0103] When receiving an NG-WT statistics subscription request message from gNB-CU-CP, NG-WT registers the request and returns an NG-WT statistics subscription acknowledgment if at least one of the subscription-related operations in the request is successful.

[0104] The list of NG-WT-specific measurement parameters includes, but is not limited to, the following. • NG-WT operating status • Number of UEs: The number of UEs associated with NG-WT: (a) those with active Xnw contexts, (b) those without active Xnw contexts. • Channel number: NG-WT operating center frequency / channel • Channel bandwidth: The total bandwidth of the operating channel

[0105] The list of UE-specific measurement parameters includes, but is not limited to, the following. • Average RSSI: An indication of the average received signal strength (RSSI / CSI) for a given UE, as calculated by NG-WT (dBm). • TX / RX packets: The number of packets sent and received by NG-WT to each UE. Measured from the time the first CWRC bearer is established for this UE. • TX retry: The average number of L2 retries for each packet sent from NG-WT to the UE. Measured starting from the establishment of the first CWRC bearer for this UE. • TX Failure: The number of L2 packet transmission failures from the AP to the UE, after reaching the maximum retry value. Measured from the time the first CWRC bearer is established for this UE. • TX MCS value: NG-WT is the average MCS value used to send packets to this UE. • RX MCS value: The average MCS value used by the UE to send its L2 packets to the AP. • Inactive time: For UEs with an active Xnw context but no active Xnw bearer, the time elapsed since the last Xnw bearer was released. • Specific statistics for 802.11ax / be: ◆RU distribution and RU allocation and utilization rate for each UE ◆ Target wake-up time configuration for each UE

[0106] If all requested subscription-related operations fail, an NG-WT statistics subscription failure message is sent. NG-WT statistics subscription failures destined for gNB-CU-CP can include appropriate CWRC-specific reason values.

[0107] Note that the NG-WT statistical reporting process can be used by NG-WT to deliver statistics requested by gNB-CU-CP as part of a specific subscription specified during the NG-WT statistical subscription process. NG-WT generates a statistical report for each subscription accepted by NG-WT. These reports are generated periodically or based on the detection of specific events as defined in the associated subscription. Therefore, NG-WT statistical reports include the following IEs. • Global RAN Node ID • NG-WT ID • Subscription ID • Reporting parameters with associated values

[0108] It should be understood that the reported parameters will include those specific parameters that have already been requested as part of the subscription, and may belong to either the NG-WT specific parameter list or the UE specific parameter list, as discussed above in the context of the NG-WT statistical subscription process.

[0109] In addition to the XnwAP process described above, CWRC operations related to bearer establishment and modification may also affect the E1 interface between gNB-CU-CP and gNB-CU-UP. More specifically, regarding the E1AP bearer context establishment process, the following optional IEs can be added to the bearer context establishment request message. ● PDU session resources need to be listed > DRB needs to be listed >> DRB needs to be created: ◆DRB Type: One of Cellular, WLAN, or Hybrid. DRBs of Cellular and WLAN types can be associated with CWRC bearer types A and / or B, while DRBs of Hybrid types are associated only with CWRC bearer type C. ◆QoS Flow QoS Parameter List > QoS Flow Item >> CWRC Fallback DRB ID: For WLAN type DRB definition, CWRC Fallback DRB ID IE defines the fallback DRB for cellular type, which will be used for the QoS flow specified based on a certain triggering criterion (i.e., the CWRC fallback threshold IE defined below). ◆SDAP Configuration > CWRC Backoff Threshold: For DRB definitions of type WLAN, the CWRC backoff threshold IE defines a threshold that, if exceeded, causes the transmitting SDAP entity to switch the QoS flow previously associated with the WLAN DRB to an alternative cellular DRB as specified by the CWRC backoff DRB ID IE defined above. When provided as part of the SDAP configuration, the CWRC backoff threshold applies only to DRBs associated with type B CWRC bearers. ◆PDCP Configuration > CWRC Partition Target: Expressed as a percentage and defined only for hybrid DRBs. The CWRC Partition Target (IE) is used by the sending PDCP entity to determine which portions of the PDCP PDUs will be submitted to the corresponding RLC entity and which PDCP PDUs will be submitted to the corresponding CWRC entity. ◆PDCP Configuration > CWRC Backoff Threshold: Defined only for hybrid DRBs, the CWRC backoff threshold defines a threshold that, if exceeded, triggers the sending PDCP entity to submit all PDCP PDUs only to the corresponding RLC entity. When provided as part of the PDCP configuration, the CWRC backoff threshold applies only to DRBs associated with type C CWRC bearers. ◆PDCP Configuration > CWRC Reordering Timeout: Defined only for hybrid DRBs. The CWRC reordering timeout IE is used by the receiving PDCP entity to determine the size of the reordering window that will be used for PDCP PDUs delivered via different RATs (i.e., cellular or WLAN).

[0110] Note that the IEs listed above can also be added to the DRB modification list included in the hosting context modification request message as part of the hosting context modification process.

[0111] As described above, various example embodiments can be based on the CWRC bearer context establishment, modification, and release process, as well as modifications to the E1 bearer context establishment and modification process to support CWRC bearers. Therefore, various aspects of the overall call flow associated with establishing such a bearer are provided below. In particular, in at least some example embodiments, modifications to the call flow can be supported to enable CWRC bearer-related operations in the RAN. • TS 38.401, Clause 8.9.2: Bearer Context Establishment on F1-U • TS 38.401, Clause 8.9.3.1: Bearer Context Release Initiated by gNB-CU-CP • TS 38.401, Clause 8.9.3.2: Bearer Context Release Initiated by gNB-CU-UP

[0112] Figure 14 An example embodiment of the bearer context establishment process configured to enable CWRC bearer establishment is shown.

[0113] like Figure 14 As shown, the bearer context establishment process 1400 involves operations via gNB-CU-CP, gNB-CU-UP, gNB-DU, and NG-WT.

[0114] like Figure 14As shown, the bearer context establishment procedure 1400 may be a modified version of the procedure defined in Clause 8.9.2 of TS 38.401, which is modified to enable CWRC bearer establishment. As discussed further below, the modification of the procedure defined in Clause 8.9.2 of TS 38.401 may include: (1) modifications to the E1AP bearer context establishment request and E1AP bearer context modification request messages to include the new IE as defined above; and (2) the integration of at least two new messages involving NG-WT, namely, the CWRC bearer context establishment request and CWRC bearer context establishment response messages, which are responsible for establishing the CWRC bearer.

[0115] like Figure 14 As shown, when bearer context establishment is triggered by gNB-CU-CP, the bearer context establishment process 1400 can proceed as follows. In step 1401, gNB-CU-CP sends a bearer context establishment request to gNB-CU-UP. This bearer context establishment request may include... Figure 10 The IE defined in step 1010. At step 1402, gNB-CU-UP responds by sending a bearer context establishment response to gNB-CU-CP. This bearer context establishment response may include... Figure 10 The IE defined in step 1020. At step 1403, gNB-CU-CP sends a UE context establishment request to gNB-DU. At step 1404, gNB-DU responds by sending a UE context establishment response to gNB-CU-CP. At step 1405, gNB-CU-CP sends a CWRC bearer context establishment request to NG-WT. At step 1406, NG-WT responds by sending a CWRC bearer context establishment response to gNB-CU-CP. At step 1407, gNB-CU-CP sends a bearer context modification request to gNB-CU-UP. This bearer context modification request may include... Figure 11 The IE defined in step 1110. At step 1408, gNB-CU-UP sends a bearer context modification response to gNB-CU-CP. This bearer context modification request may include... Figure 11 The IE is defined in step 1120. Note that the flow of uplink and downlink user data in the user plane is shown.

[0116] Figure 15 An example embodiment of a bearer context release procedure initiated by the control plane and configured to enable CWRC bearer release is shown.

[0117] like Figure 15As shown, the bearer context release process 1500 involves operations via gNB-CU-CP, gNB-CU-UP, gNB-DU, and NG-WT.

[0118] like Figure 15 As shown, the bearer context release procedure 1500 can be a modified version of the procedure defined in Clause 8.9.3.1 of TS 38.401, modified to enable CWRC bearer release. As discussed further below, the modification to the procedure defined in Clause 8.9.3.1 of TS 38.401 may include the integration of at least two new messages involving NG-WT: the CWRC bearer context release command and the CWRC bearer context release completion message, which are responsible for releasing the CWRC bearer.

[0119] like Figure 15 As shown, when the bearer context release is triggered by gNB-CU-CP, the bearer context release process 1500 can proceed as follows: At step 1501, gNB-CU-CP can send a bearer context modification request to gNB-CU-UP. At step 1502, gNB-CU-UP can send a bearer context modification response to gNB-CU-CP. At step 1503, gNB-CU-CP can send a UE context modification request to gNB-CU-UP. At step 1504, gNB-CU-UP can respond by sending a UE context modification response to gNB-CU-CP. At step 1505, gNB-CU-CP sends a bearer context release command to gNB-CU-UP. At step 1506, gNB-CU-CP sends a UE context release command to gNB-DU. At step 1507, gNB-CU-CP sends a CWRC bearer context release command to NG-WT. The CWRC bearer context release command may include, for example... Figure 12 The IE defined in step 1210. At step 1508, gNB-DU responds by sending a UE context release complete message to gNB-CU-CP. At step 1509, NG-WT responds by sending a CWRC bearer context release complete message to gNB-CU-CP. The CWRC bearer context release complete message may include, for example... Figure 12 The IE defined in step 1220. At step 1510, GNB-CU-UP responds by sending a bearer context release complete message to gNB-CU-CP.

[0120] It should be understood that PDCP state preservation does not apply to CWRC bearers; therefore, the CWRC bearer context modification process is not... Figure 15 The portion of the call flow shown.

[0121] Figure 16 An example embodiment of a bearer context release procedure initiated by the user plane and configured to enable CWRC bearer release is shown.

[0122] like Figure 16 As shown, the bearer context release process 1600 involves operations via gNB-CU-CP, gNB-CU-UP, gNB-DU, and NG-WT.

[0123] like Figure 16 As shown, the bearer context release procedure 1600 can be a modified version of the procedure defined in Clause 8.9.3.2 of TS 38.401, modified to enable CWRC bearer release. As discussed further below, the modification to the procedure defined in Clause 8.9.3.2 of TS 38.401 may include the integration of two new messages involving NG-WT: the CWRC bearer context release command and the CWRC bearer context release complete message, which are responsible for releasing the CWRC bearer.

[0124] like Figure 16 As shown, the bearer context release procedure 1600, when triggered by gNB-CU-UP, can proceed as follows: In step 1601, gNB-CU-CP sends a bearer context release request to gNB-CU-UP. In step 1602, gNB-CU-CP may send a bearer context modification request to gNB-CU-UP. In step 1603, gNB-CU-UP may respond by sending a bearer context modification response to gNB-CU-CP. In step 1604, gNB-CU-CP may send a UE context modification request to gNB-CU-UP. In step 1605, gNB-CU-UP may respond by sending a UE context modification response to gNB-CU-CP. In step 1606, gNB-CU-CP sends a bearer context release command to gNB-CU-UP. In step 1607, gNB-CU-UP sends a bearer context release completion message to gNB-CU-CP. At step 1608, gNB-CU-CP sends a UE context release command to gNB-DU. At step 1609, gNB-DU responds by sending a UE context release complete message to gNB-CU-CP. At step 1610, gNB-CU-CP sends a CWRC bearer context release command to NG-WT. The CWRC bearer context release command may include, for example... Figure 12 The IE defined in step 1210. At step 1611, NG-WT responds by sending a CWRC bearer context release complete message to gNB-CU-CP. The CWRC bearer context release complete message may include, for example... Figure 12The IE defined in step 1220.

[0125] It should be understood that PDCP state preservation does not apply to CWRC bearers; therefore, the CWRC bearer context modification process is not... Figure 16 The portion of the call flow shown.

[0126] CWRC capabilities can be supported based on various protocols. For example, CWRC capabilities can be supported using RRC, SDAP, and PDCP protocols. CWRC capabilities can also be supported based on a new protocol called CWRC Protocol (CWRCP), which can be deployed in NG-WT.

[0127] CWRC capabilities can be supported based on the RRC protocol. CWRC capabilities can be supported based on various enhancements to the RRC protocol.

[0128] For example, CWRC capabilities can be supported by enhancements to the RRC protocol to support various RRC connection control functions.

[0129] For example, the following can be added to Clause 4.4 of TS 38.331: (1) CWRC bearer establishment, modification and release; and (2) CWRC bearer type selection and configuration based on CWRC rate control and partition target parameters.

[0130] For example, the following information can be added to the UECapabilityInformation message defined in TS 38.331: ●UECapabilityInformation>UECapabilityInformation-IEs>ue-CapabilityRAT-ContainerList>UE-CapabilityRAT-Container (Type: UE-NR-Capability)>UE-NR-Capability-v1530>…>UE-NR-Capability-vXXXX: ◆cwrc-Parameters-rX, including the following optional parameters: ●cwrc-UE-Layer2-Id: A unique UE-specific Layer 2 identifier used for CWRC-related operations. For example, the XnwAP UE ID can be derived from this Layer 2 ID. ●cwrc-TypeA-DL-rX: Indicates support for CWRC type A bearers in the downlink. ●cwrc-TypeB-DL-rX: Indicates support for CWRC type B bearers in the downlink. ●cwrc-TypeC-DL-rX: Indicates support for CWRC type C bearers in the downlink. ●cwrc-TypeA-UL-rX: Indicates support for CWRC type A bearers in the uplink. ●cwrc-TypeB-UL-rX: Indicates support for CWRC type B bearers in the uplink. ◆cwrc-TypeC-UL-rX: Indicates support for CWRC type C bearers in the uplink.

[0131] For example, the RRCConnectionReconfiguration message, which is used as part of the RRC reconfiguration procedure defined in Clause 5.3.5 of TS 38.331, can be expanded to include the following: ●RRCReconfiguration>RRCReconfiguration-IEs>RadioBearerConfig>DRB-ToAddModList>DRB-ToAddMod: ◆… ◆drb-Type: Cellular, WLAN, or Hybrid. ◆cwrc-Type: Type A, B, or C. ◆cnAssociation>SDAP-Config: •… •fallbackQoS-FlowsToAdd: Used only for cellular DRBs. Specifies the QoS flows for which this DRB provides CWRC fallback capability. •cwrc-FallbackTreshold: Used only for WLAN DRBs. Defined in section 7.2.2. ◆PDCP-Config: •… • cwrc-SplitTarget: Used only for mixing DRBs. Defined in section 7.2.2. • cwrc-FallbackTreshold: Used only for mixed DRBs. Defined in section 7.2.2. • cwrc-ReorderingTimeout: Only used for mixed DRBs. Defined in section 7.2.2. ●RRCReconfiguration>RRCReconfiguration-IEs>RRCReconfiguration-v1530-IEs>…>RRCReconfiguration-vXXXX-IEs>cwrc-Configuration-rX: ◆cwrc-NG-WT-Layer2-Id: A unique NG-WT specific Layer 2 identifier used for CWRC-related operations. For example, the XnwAP UE ID can be derived from this Layer 2 ID.

[0132] For example, when receiving an RRCConnectionReconfiguration message with the above parameters, the UE can establish a related bearer, which includes any associated PDCP and SDAP entities.

[0133] For example, to assist RRC in making decisions related to the CWRC bearer context modification and release process, additional parameters can also be introduced for LogMeasResultListWLANIE, as follows: • LogMeasResultListWLAN>LogMeasResultWLAN>cwrc-Status: ◆cwrc-LastPDU: Indicates the time elapsed since the last CWRCP PDU was received and processed by any CWRCP entity associated with the bearer involved in the AP, and this report is generated for that AP. ◆cwrc-TimeoutEvent: Defined only for bearers of type C. Indicates the number of times cwrc-ReorderingTimeout has expired since this report was last generated.

[0134] It should be understood that CWRC capabilities can also be supported in various other ways based on the RRC protocol.

[0135] CWRC capabilities can be supported based on SDAP. CWRC capabilities can be supported based on various enhancements to SDAP.

[0136] For example, for a Type B CWRC bearer, SDAP can integrate a fallback mechanism, whereby if the value defined in the CWRC fallback threshold IE is exceeded, the sending SDAP entity switches the QoS flow previously associated with the WLAN DRB to an alternative cellular DRB as specified by the CWRC fallback DRB ID IE.

[0137] It should be understood that CWRC capabilities can be supported in various other ways based on SDAP.

[0138] CWRC capabilities can be supported based on PDCP. CWRC capabilities can be supported based on various enhancements to PDCP.

[0139] For example, for a hybrid DRB (i.e., involving a CWRC bearer of type C), the transmitting PDCP entity can be responsible for distributing traffic across cellular and WLAN RATs according to the values ​​configured in the CWRC partition target IE. For example, the transmitting PDCP entity can also suspend PDU delivery to the CWRC PDCP entity if the CWRC backoff threshold IE is exceeded. For example, for a hybrid DRB, the receiving PDCP entity can be responsible for recording received PDCP PDUs based on the window size of the portion of the IE configured for CWRC reordering timeout.

[0140] It should be understood that CWRC capabilities can be supported based on PDCP in various other ways.

[0141] Figure 17 An example embodiment of a method for use by NG-WT to support cellular-WLAN convergence in a RAN is shown. It should be understood that although presented herein primarily as performed serially, at least a portion of the functionality of method 1700 may be performed concurrently or in conjunction with... Figure 17The different sequences shown are executed. At block 1701, method 1700 begins. At block 1710, a set of communication interfaces for a radio access network (RAN) supported by a wireless local area network (WLAN) terminal element, the RAN including cellular base stations (BS), wherein the set of communication interfaces includes: a first communication interface configured to support access to the WLAN by the set of terminal devices; a second communication interface configured to support communication with a control plane element of the cellular BS; and a third communication interface configured to support communication with a user plane element of the cellular BS. At block 1720, a cellular-WLAN RAN convergence (CWRC) bearer is supported by the WLAN terminal element based on the set of communication interfaces. At block 1799, method 1700 ends. In at least some example embodiments of method 1700, the method may include: a state machine supported by the WLAN terminal element, the state machine supporting a set of states, wherein the set of states includes an idle state, an active state, an associated state, and a connected state. In at least some example embodiments of method 1700, the method may include: sending an initialization request message to a control plane element of a cellular BS, the initialization request message being configured to request initialization of the WLAN terminal element; and receiving an initialization response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: receiving a configuration update message from the control plane element of the cellular BS by the WLAN terminal element, the configuration update message being configured to update the usage in the configuration information of the WLAN terminal element; and sending a configuration update confirmation message to the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: sending a configuration update message indicating an update of the configuration information of the WLAN terminal element to the control plane element of the cellular BS by the WLAN terminal element; and receiving a configuration update confirmation message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: receiving a deactivation request message from the control plane element of the cellular BS by the WLAN terminal element, the deactivation request message being configured to request deactivation of the WLAN terminal element; and sending a deactivation response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: sending a terminal device association message to a control plane element of a cellular BS by a WLAN terminal element, the terminal device association message being configured to indicate an association between a terminal device and a WLAN terminal element; and receiving a terminal device association confirmation message from the control plane element of the cellular BS by the WLAN terminal element.In at least some example embodiments of method 1700, the method may include: receiving a CWRC bearer context establishment request message from a control plane element of a cellular BS by a WLAN terminal element, the CWRC bearer context establishment request message being configured to request the establishment of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context establishment response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: receiving a CWRC bearer context modification request message from a control plane element of a cellular BS by a WLAN terminal element, the CWRC bearer context modification request message being configured to request the modification of a context for CWRC bearer within the WLAN terminal element; and sending a CWRC bearer context modification response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: receiving a CWRC bearer context release request message from a control plane element of a cellular BS by a WLAN terminal element, the CWRC bearer context release request message being configured to request the release of a context within the WLAN terminal element used for CWRC bearer; and sending a CWRC bearer context release response message from the control plane element of the cellular BS by the WLAN terminal element. In at least some example embodiments of method 1700, the method may include: supporting an application protocol procedure set by the WLAN terminal element based on a second communication interface with the control plane element of the cellular BS. In at least some example embodiments of method 1700, the application protocol procedure set includes at least one of the following: an initialization procedure configured to support the initialization of a WLAN terminal element; a configuration procedure configured to support the configuration of a WLAN terminal element; a deactivation procedure configured to support the deactivation of a WLAN terminal element; an association procedure configured to support the association of a terminal device with a WLAN terminal element; a bearer context establishment procedure configured to support the establishment of a bearer context for CWRC bearers; a bearer context modification procedure configured to support the modification of a bearer context for CWRC bearers; a bearer context release procedure configured to support the release of a bearer context for CWRC bearers; a statistics subscription procedure configured to support the subscription of a cellular BS control plane element to receive statistics from a WLAN terminal element; and a statistics reporting procedure configured to support the reporting of statistics from the WLAN terminal element to the cellular BS control plane element. In at least some example embodiments of method 1700, the WLAN terminal element includes a next-generation wireless local area network (WLAN) termination (NG-WT) element.It should be understood that various other example embodiments, including the various capabilities described herein such as those supported by NG-WT, can be integrated. Figure 17 In the context of method 1700.

[0142] Figure 18 An example embodiment of a method for use by RAN control elements to support cellular-WLAN RAN convergence in the RAN is shown. It should be understood that although presented herein primarily as performed serially, at least a portion of the functionality of method 1800 may be performed concurrently or in conjunction with... Figure 18The different sequences shown are executed. At block 1801, method 1800 begins. At block 1810, the control element of the radio access network (RAN) sends a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer to the wireless local area network (WLAN) terminal element of the radio access network. At block 1820, the control element receives a bearer context establishment response message for the CWRC bearer from the WLAN terminal element. At block 1899, method 1800 ends. In at least some example embodiments of method 1800, the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element. In at least some example embodiments of method 1800, the method may include: sending a bearer context establishment request message by the control element to the user plane element of the RAN. In at least some example embodiments of method 1800, the method may include: sending a bearer context modification request message by the control element to the user plane element of the RAN. In at least some example embodiments of method 1800, the method may include: sending a bearer context release command for CWRC bearer to a WLAN terminal element by a control element; and receiving a bearer context release completion message for CWRC bearer from the WLAN terminal element by the control element. In at least some example embodiments of method 1800, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by the control element. In at least some example embodiments of method 1800, the method may include: sending a bearer context release command message to a user plane element of the RAN by the control element before sending the bearer context release command for CWRC bearer; and sending a terminal device context release command for the terminal device of the RAN to a distributed unit of the RAN before sending the bearer context release command for CWRC bearer. In at least some example embodiments of method 1800, the bearer context release command for CWRC bearer is sent based on a bearer context release process triggered by the user plane element of the RAN. In at least some example embodiments of method 1800, the bearer context release command for the CWRC bearer is sent based on receiving a bearer context release complete message from a user plane element of the RAN and based on receiving a terminal device context release complete message for the terminal device used for the CWRC bearer.In at least some example embodiments of method 1800, the CWRC bearer includes one of the following: (1) a bearer comprising multiple protocol data unit sessions based on multiple corresponding service data adaptation protocol entities, the multiple corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities; (2) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or (3) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific logical channels of data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific logical channels is based on WLAN access. It should be understood that various other example embodiments, including the various capabilities supported by gNB-CU-CP as described herein, can be integrated. Figure 18 Method 1800.

[0143] Figure 19 An example embodiment of a method for use by WLAN terminal elements in a RAN to support cellular-WLAN RAN convergence is shown. It should be understood that although presented herein primarily as performed serially, at least a portion of the functionality of method 1900 may be performed concurrently or in conjunction with... Figure 19The different sequences shown are executed. At block 1901, method 1900 begins. At block 1910, a wireless local area network (WLAN) terminal element of the radio access network (RAN) receives a bearer context establishment request message for a cellular-WLAN RAN convergence (CWRC) bearer towards the control element of the RAN. At block 1920, the WLAN terminal element sends a bearer context establishment response message for the CWRC bearer towards the control element. At block 1999, method 1900 ends. In at least some example embodiments of method 1900, the bearer context establishment request message for the CWRC bearer is received based on a bearer context establishment process triggered by the control element. In at least some example embodiments of method 1900, method 1900 includes: receiving a bearer context release command for the CWRC bearer from the control element by the WLAN terminal element, and sending a bearer context release completion message for the CWRC bearer towards the control element by the WLAN terminal element. In at least some example embodiments of method 1900, the bearer context release command for the CWRC bearer is received based on a bearer context release process triggered by the control element. In at least some example embodiments of method 1900, a bearer context release command for a CWRC bearer is received based on a bearer context release procedure triggered by a user plane element of the RAN. In at least some example embodiments of method 1900, a bearer context release command for a CWRC bearer is received based on receiving a bearer context release completion message from a user plane element of the RAN and based on receiving a terminal device context release completion message for a terminal device used for a CWRC bearer. In at least some example embodiments of method 1900, the CWRC bearer includes one of the following: (1) a bearer comprising multiple protocol data unit sessions based on multiple corresponding service data adaptation protocol entities, the multiple corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities; (2) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or (3) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific logical channels of data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific logical channels is based on WLAN access. It should be understood that various other example embodiments, including the various capabilities supported by NG-WT as described herein, can be integrated into Figure 19 Method 1900.

[0144] Figure 20 An example embodiment of a method for use by a terminal device to support cellular-WLAN aggregation in a RAN is shown. It should be understood that although presented herein primarily as performed serially, at least a portion of the functionality of method 2000 may be performed concurrently or in conjunction with... Figure 20The different sequences shown are executed. At block 2001, method 2000 begins. At block 2010, a terminal device capability information message is sent, indicating that the terminal device is capable of supporting Cellular Wireless Local Area Network (WLAN) Radio Access Network (RAN) Convergence (CWRC) bearers. At block 2020, a Radio Resource Control (RRC) reconfiguration message is received, including a set of parameters for the CWRC bearer of the terminal device. At block 2030, the CWRC bearer for the terminal device is configured based on the set of parameters. At block 2099, method 2000 ends. In at least some example embodiments of method 2000, the terminal device capability information message includes a unique Layer 2 identifier specific to the terminal device for use in CWRC-related operations. In at least some example embodiments of method 2000, the terminal device supports downlink and uplink, and the terminal device capability information message includes information elements that include at least one of the following: at least one parameter indicating whether the terminal device supports a first CWRC bearer type in one of the downlink or uplink links; at least one parameter indicating whether the terminal device supports a second CWRC bearer type in one of the downlink or uplink links; or at least one parameter indicating whether the terminal device supports a third CWRC bearer type in one of the downlink or uplink links. In at least some example embodiments of method 2000, the RRC reconfiguration message includes a first information element, wherein the first information element includes: a data radio bearer type element indicating the data radio bearer type for the CWRC bearer for the terminal device; a CWRC bearer type element indicating the bearer type for the CWRC bearer for the terminal device; a Serving Data Adaptation Protocol (SDAP) configuration element including one or more parameters for an SDAP entity for the CWRC bearer for the terminal device; and a Packet Data Convergence Protocol (PDCP) configuration element including one or more parameters for a PDCP entity for the CWRC bearer for the terminal device. In at least some example embodiments of method 2000, the RRC reconfiguration message includes a second information element, wherein the second information element includes a unique Layer 2 identifier specific to a WLAN terminal element that supports CWRC bearers for the terminal device.In at least some example embodiments of method 2000, the CWRC bearer for a terminal device includes one of the following: (1) a bearer comprising multiple protocol data unit sessions based on multiple corresponding service data adaptation protocol entities, the multiple corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities; (2) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific data radio bearers is based on WLAN access; or (3) a bearer comprising protocol data unit sessions based on corresponding service data adaptation protocol entities, the corresponding service data adaptation protocol entities being mapped to access-specific logical channels of data radio bearers associated with corresponding packet data convergence protocol entities, wherein at least one of the access-specific logical channels is based on WLAN access. In at least some example embodiments of method 2000, the terminal device is configured to support: (1) a first service data adaptation protocol entity and a second service data adaptation protocol entity, the first service data adaptation protocol entity being mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access, and the second service data adaptation protocol entity being mapped to a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access; (2) a service data adaptation protocol entity being mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access, and a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access; or (3) a service data adaptation protocol entity being mapped to a packet data aggregation protocol entity supporting a data radio bearer that supports a first logical channel based on cellular access and a second logical channel based on WLAN access. It should be understood that various other example embodiments, including the various capabilities supported by the UE or terminal device described herein, can be integrated. Figure 20 Method 2000.

[0145] Various embodiments of CWRC capabilities can be configured to provide a variety of advantages or potential advantages.

[0146] For example, various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and WLAN access in ways that tend to prevent joint programmability and use case-based customization, thereby enabling support for joint programmability and use case-based customization. For example, various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and WLAN access based on: support for extending the 3GPP system architecture to integrate WLAN access in 3GPP access networks; support for extending the 3GPP control plane to support various WLAN operations and performance measurement reports; support for extending the 3GPP user plane to integrate various convergence mechanisms for cellular and WLAN traffic; support for providing related control plane and user plane interfaces and procedures to support the resolution of the above capabilities, and various combinations thereof.

[0147] For example, various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and WLAN access at Layer 2 without relying on LWA and LWIP capabilities (although it should be understood that at least some of these mechanisms can still be used). Note that such LWA and LWIP specifications are typically geared towards a single eNB and have not yet been updated for NG-RAN architectures. Therefore, as mentioned above, LWA and LWIP are far from sufficient for modern enterprise networks, requiring a robust multi-access connectivity solution that leverages LTE, NR, and WLAN. Various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and WLAN access at Layer 2 in a manner that tends to overcome at least some of these limitations.

[0148] For example, various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and WLAN access at Layer 2 without relying on Layer 4 convergence mechanisms such as MPTCP and MQUIC-based ATSSS (although it should be understood that at least some of these mechanisms can still be used). The core principle of Layer 4 convergence advocated by ATSSS is to merge data streams at the network endpoints (i.e., UE and UPF). However, this approach may have certain drawbacks. First, the network endpoints are not aware of resource management priorities at the RAN, and therefore cannot make informed decisions regarding the splitting and switching of traffic between the two RATs. Second, the network endpoint traffic manager responds too slowly to channel outages occurring at the RAN. Previous research has shown that the average RTT from UE to edge / cloud server on commercial networks can exceed 150ms to 200ms. Modern augmented reality / virtual reality (AR / VR) applications require latency below 50ms, so application servers may struggle to rebalance traffic during RAN outages. Various example embodiments of CWRC capabilities can be configured to support the convergence of cellular and wireless LAN (WLAN) access at Layer 2 in a manner that tends to overcome at least some of these limitations.

[0149] It should be understood that various other example embodiments of CWRC capabilities can also be configured to provide various other advantages or potential advantages.

[0150] Figure 21 Example embodiments of computers suitable for performing the various functions described herein are shown.

[0151] Computer 2100 includes processor 2102 (e.g., central processing unit (CPU), graphics processing unit (GPU), network processor (NPU), processor, processor core of processor, subset of processor cores of processor, set of processor cores of processor, etc.) and memory 2104 (e.g., random access memory (RAM), read-only memory (ROM), etc.). In at least some example embodiments, computer 2100 may include at least one processor and at least one memory storing instructions that, when executed by at least one processor, cause computer 2100 to perform the various functions described herein.

[0152] Computer 2100 may also include a cooperating element 2105. Cooperating element 2105 may be a hardware device. Cooperating element 2105 may include firmware. Cooperating element 2105 may be a process capable of being loaded into memory 2104 and executed by processor 2102 to perform the various functions described herein (in which case, for example, cooperating element 2105 (including associated data structures) may be stored on a non-transitory computer-readable medium, such as a storage device or other suitable type of storage element (e.g., a magnetic drive, an optical drive, etc.)).

[0153] Computer 2100 may also include one or more input / output devices 2106. Input / output devices 2106 may include one or more of the following: user input devices (e.g., keyboard, keypad, mouse, microphone, camera, etc.), user output devices (e.g., monitor, speakers, etc.), one or more network communication devices or components (e.g., input port, output port, receiver, transmitter, transceiver, etc.), one or more storage devices (e.g., tape drive, floppy disk drive, hard disk drive, optical disk drive, etc.), and various combinations thereof.

[0154] It should be understood that computer 2100 may represent a general architecture and functionality suitable for implementing the functional elements described herein, portions thereof, and various combinations thereof. For example, computer 2100 may provide a general architecture and functionality suitable for implementing one or more elements described herein; or it may provide a general architecture and functionality in which one or more elements described herein may be utilized.

[0155] It should be understood that the various functions described herein can be implemented in hardware, software, and combinations thereof. For example, at least some of the functions described herein can be implemented in hardware (e.g., using a general-purpose computer, one or more application-specific integrated circuits, and / or any other equivalent hardware). For example, at least some of the functions described herein can be implemented in a combination of software and hardware (e.g., via software implementation on one or more processors for execution on a general-purpose computer (e.g., via execution by one or more processors) to provide a special-purpose computer, etc.).

[0156] It should be understood that at least some of the functions described herein can be implemented in hardware, for example, as a circuit system that works with a processor to perform various functions. Parts of the functions / components described herein can be implemented as computer program products, wherein computer instructions, when processed by a computer, adjust the operation of the computer so that the methods and / or techniques described herein are invoked or otherwise provided. Instructions for invoking the various methods can be stored in a non-transitory computer-readable medium, such as memory in a computing device that operates according to the instructions, fixed or removable media, etc. It should be understood that the term "non-transitory" as used herein refers to a limitation of the medium itself (i.e., tangible, not tactile), not a limitation of data storage persistence (e.g., RAM and ROM).

[0157] It should be understood that, as used herein, the term "circuit system" can refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry having software / firmware, and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions); and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of circuit system applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term circuit system also covers implementations of hardware circuitry or processors (or multiple processors) or portions thereof and their accompanying software and / or firmware. For example, and if applicable to certain claim elements, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0158] It should be understood that, as used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0159] It should be understood that, as used herein, “at least one of a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, refers to at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0160] It should be understood that the term “or” as used herein means non-exclusive “or” unless otherwise stated (e.g., “otherwise” or “or as an alternative”).

[0161] It should be understood that although various embodiments incorporating the teachings set forth herein have been shown and described in detail herein, those skilled in the art can readily devise many other various embodiments that still incorporate these teachings.

Claims

1. A terminal device for cellular wireless local area network (WLAN) convergence, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to perform at least the following: Send a terminal device capability information message, wherein the terminal device capability information message indicates that the terminal device can support Cellular-WLAN Radio Access Network RAN ​​Convergence (CWRC) bearer; Receive a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message includes a set of parameters for the CWRC bearer of the terminal device; as well as Configure the CWRC bearer for the terminal device based on the set of parameters for the CWRC bearer for the terminal device.

2. The terminal device according to claim 1, wherein the terminal device capability information message includes a unique Layer 2 identifier specific to the terminal device for use in supporting CWRC-related operations.

3. The terminal device according to any one of claims 1 to 2, wherein the terminal device supports downlink and uplink, and wherein the terminal device capability information message includes information elements, the information elements including at least one of the following: At least one parameter, the at least one parameter indicating whether the terminal device supports a first CWRC bearer type in one of the downlink or the uplink; At least one parameter, the at least one parameter indicating whether the terminal device supports a second CWRC bearer type in one of the downlink or the uplink; or At least one parameter, the at least one parameter indicating whether the terminal device supports a third CWRC bearer type in one of the downlink or the uplink.

4. The terminal device according to any one of claims 1 to 2, wherein the RRC reconfiguration message includes a first information element, wherein the first information element includes: A data radio bearer type element, which indicates the data radio bearer type used for the CWRC bearer for the terminal device; CWRC bearer type element, wherein the CWRC bearer type element indicates the bearer type of the CWRC bearer for the terminal device; A Service Data Adaptation Protocol (SDAP) configuration element, the SDAP configuration element including one or more parameters for the SDAP entity carried by the CWRC for the terminal device; and A Packet Data Convergence Protocol (PDCP) configuration element, the PDCP configuration element including one or more parameters for the PDCP entity of the CWRC bearer for the terminal device.

5. The terminal device according to claim 4, wherein the RRC reconfiguration message includes a second information element, wherein the second information element includes a unique Layer 2 identifier specific to a WLAN terminal element, the WLAN terminal element supporting the CWRC bearer for the terminal device.

6. The terminal device according to any one of claims 1 to 2, wherein the CWRC bearer for the terminal device comprises one of the following: The bearer includes multiple protocol data unit sessions based on multiple corresponding service data adaptation protocol entities, which are mapped to access-specific data radio bearers associated with corresponding packet data aggregation protocol entities. The bearer includes a protocol data unit session based on a corresponding service data adaptation protocol entity, the corresponding service data adaptation protocol entity being mapped to an access-specific data radio bearer associated with a corresponding packet data convergence protocol entity, wherein at least one of the access-specific data radio bearers is based on WLAN access. or The bearer includes a protocol data unit session based on a corresponding service data adaptation protocol entity, the corresponding service data adaptation protocol entity being mapped to an access-specific logical channel of a data radio bearer associated with a corresponding packet data convergence protocol entity, wherein at least one of the access-specific logical channels is based on WLAN access.

7. The terminal device according to any one of claims 1 to 2, wherein the terminal device is configured to support at least one of the following: A first service data adaptation protocol entity and a second service data adaptation protocol entity, wherein the first service data adaptation protocol entity is mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access, and the second service data adaptation protocol entity is mapped to a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access. A service data adaptation protocol entity, which is mapped to a first data radio bearer associated with a first packet data aggregation protocol entity based on cellular access and a second data radio bearer associated with a second packet data aggregation protocol entity based on WLAN access; or A service data adaptation protocol entity is mapped to a packet data aggregation protocol entity that supports data radio bearers, the data radio bearers supporting a first logical channel based on cellular access and a second logical channel based on WLAN access.

8. An apparatus for cellular wireless local area network (WLAN) convergence, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: The control element of the Radio Access Network (RAN) sends a Bearer Context Establishment Request message for the Cellular-WLAN RAN Convergence (CWRC) Bearer to the WLAN terminal element of the RAN; as well as The control element receives a bearer context establishment response message for the CWRC bearer from the WLAN terminal element.

9. The apparatus of claim 8, wherein the bearer context establishment request message for the CWRC bearer is sent based on a bearer context establishment process triggered by the control element.

10. The apparatus according to any one of claims 8 to 9, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: The control element sends a bearer context establishment request message toward the user plane element of the RAN.

11. The apparatus according to any one of claims 8 to 9, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: The control element sends a bearer context modification request message toward the user plane element of the RAN.

12. The apparatus according to any one of claims 8 to 9, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: The control element sends a bearer context release command for the CWRC bearer to the WLAN terminal element; and The control element receives a bearer context release complete message for the CWRC bearer from the WLAN terminal element.

13. The apparatus of claim 12, wherein the bearer context release command for the CWRC bearer is sent based on a bearer context release procedure triggered by the control element, wherein the instruction, when executed by the at least one processor, causes the apparatus to perform at least: Before sending the bearer context release command for the CWRC bearer, the control element sends a bearer context release command message toward the user plane element of the RAN; and Before sending the bearer context release command for the CWRC bearer, the control element sends a terminal device context release command for the terminal device of the CWRC bearer to the distributed unit of the RAN.

14. The apparatus of claim 12, wherein the bearer context release command for the CWRC bearer is sent based on a bearer context release procedure triggered by a user plane element of the RAN, wherein the bearer context release command for the CWRC bearer is sent based on receiving a bearer context release completion message from a user plane element of the RAN and based on receiving a terminal device context release completion message for the terminal device for the CWRC bearer.

15. An apparatus for cellular wireless local area network (WLAN) aggregation, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least the following: The WLAN terminal element of the Radio Access Network (RAN) receives a bearer context establishment request message for the Cellular-WLAN RAN Convergence (CWRC) bearer from the control element of the RAN. as well as The WLAN terminal element sends a bearer context establishment response message for the CWRC bearer to the control element.

Images