Patent Application
20190028931
When user equipment (UE), such as a mobile device, accesses an evolved packet core (EPC) core network via 3GPP access, end to end QoS differentiation is supported via EPS bearer services. Both the E-RAB Radio Access bearer between the UE and the serving gateway of the EPC (SGW), and Core Network S5/S8 bearer between the SGW and packet data network gateway (PDN-GW) are established with specified quality of service (QoS) characteristics and a mapping of a QoS Class Index (QCI) that describes the type of service (data traffic) expected for the bearer (e.g., signaling, conversational voice, streaming video, best effort, etc.). The QCI also defines the traffic performance and QoS forwarding behavior (e.g. packet loss rate, maximum delay, residual error rate, etc.). In contrast, when UE accesses the EPC via a trusted wireless local area network (WLAN) access, end to end QoS differentiation cannot be provided.
Although QoS differentiation support is possible for a Core Network S2a bearer between a trusted wireless access gateway (TWAG) and the PDN-GW of the core network, when TSCM connection mode or SCM connection mode is used, QoS differentiation cannot be supported since these are single connection modes. When MCM (multi-connection mode) is used, multiple packet data network (PDN) connections may be supported, yet differentiated treatments towards service data flows (SDFs) cannot be achieved because all service data flows (data traffic) are transported via a single point-to-point link between an UE and its serving TWAG for the PDN connection, thus distinction of different service data flows within a PDN connection is not possible. A wireless LAN control plane (WLCP) protocol extension for the over the air (SWw) interface is required in order to enable QoS signaling for QoS differentiation at the service data flow level in order to provide end to end QoS differentiation.
Methods, apparatuses, and computer program products are provided in accordance with example embodiments in order to support QoS signaling over SWw Trusted WLAN Access for the UEs in Multi-Connection Mode (MCM), thus enabling the end to end QoS differentiation for service data flows.
In one embodiment, a method for quality of service (QoS) differentiation is provided. The method comprises determining, at a trusted wireless access gateway (TWAG), if multi-connection mode is available between User Equipment (UE) and a trusted wireless local area network (WLAN), establishing, at the TWAG, a packet data network connection between the UE and the WLAN to connect the UE to a core network with a default bearer connection, establishing, at the TWAG, one or more additional bearers, wherein each of the additional bearers and the default bearer are established with a specified QoS characteristic and a QoS mapping (QCI), and transmitting, at the TWAG, data traffic over the default bearer and the one or more additional bearers, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In one example embodiment, an apparatus for quality of service (QoS) differentiation is provided. The apparatus includes at least one processor and at least one memory including computer program code with at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least: determine if multi-connection mode is available between User Equipment (UE) and a trusted wireless local area network (WLAN), establish a packet data network connection between the UE and the WLAN to connect the UE to a core network with a default bearer connection, establish one or more additional bearers, wherein each of the additional bearers and the default bearer are established with a specified QoS characteristic and a QoS mapping (QCI), and transmit at the TWAG, data traffic over the default bearer and the one or more additional bearers, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In a further embodiment, a computer program product is provided that includes at least one non-transitory computer readable storage medium having computer-executable program code portions stored therein with the computer-executable program code portions including program code instructions configured to provide quality of service (QoS) differentiation. The program code portions of an example embodiment also include program code instructions configured to determine if multi-connection mode is available between User Equipment (UE) and a trusted wireless local area network (WLAN), establish a packet data network connection between the UE and the WLAN to connect the UE to a core network with a default bearer connection, establish one or more additional bearers, wherein each of the additional bearers and the default bearer are established with a specified QoS characteristic and a QoS mapping (QCI), and transmit at the TWAG, data traffic over the default bearer and the one or more additional bearers, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In yet another example embodiment, an apparatus is provided that includes means for quality of service (QoS) differentiation. The apparatus includes means for determining if multi-connection mode is available between User Equipment (UE) and a trusted wireless local area network (WLAN), establishing a packet data network connection between the UE and the WLAN to connect the UE to a core network with a default bearer connection, establishing one or more additional bearers, wherein each of the additional bearers and the default bearer are established with a specified QoS characteristic and a QoS mapping (QCI), and transmitting traffic over the default bearer and the one or more additional bearers, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In another embodiment, a method for quality of service (QoS) differentiation is provided. The method comprises establishing, at a user equipment (UE), a trusted wireless network connection with a trusted wireless local area network (WLAN), indicating, at the UE, to the WLAN that a multi-connection mode is available between User Equipment (UE) and the WLAN, selecting from an established packet data network connection between the UE and the WLAN, a bearer connection, wherein the bearer connection includes a specified QoS characteristic and a QoS mapping (QCI), transmitting, at the UE, data traffic over the selected bearer, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In one example embodiment, an apparatus for quality of service (QoS) differentiation is provided. The apparatus includes at least one processor and at least one memory including computer program code with at least one memory and the computer program code configured to, with the processor, cause the apparatus to at least: establish a trusted wireless network connection with a trusted wireless local area network (WLAN), indicate, at the UE, to the WLAN that a multi-connection mode is available between User Equipment (UE) and the WLAN, select from an established packet data network connection between the UE and the WLAN, a bearer connection, wherein the bearer connection includes a specified QoS characteristic and a QoS mapping (QCI), and transmit data traffic over the selected bearer, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In a further embodiment, a computer program product is provided that includes at least one non-transitory computer readable storage medium having computer-executable program code portions stored therein with the computer-executable program code portions including program code instructions configured to provide quality of service (QoS) differentiation. The program code portions of an example embodiment also include program code instructions configured to establish a trusted wireless network connection with a trusted wireless local area network (WLAN), indicate, at the UE, to the WLAN that a multi-connection mode is available between User Equipment (UE) and the WLAN, select from an established packet data network connection between the UE and the WLAN, a bearer connection, wherein the bearer connection includes a specified QoS characteristic and a QoS mapping (QCI), and transmit data traffic over the selected bearer, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
In yet another example embodiment, an apparatus is provided that includes means for quality of service (QoS) differentiation. The apparatus includes means for establishing a trusted wireless network connection with a trusted wireless local area network (WLAN), indicating to the WLAN that a multi-connection mode is available between User Equipment (UE) and the WLAN, selecting from an established packet data network connection between the UE and the WLAN, a bearer connection, wherein the bearer connection includes a specified QoS characteristic and a QoS mapping (QCI), and transmitting data traffic over the selected bearer, wherein the data traffic is transmitted according to differentiated QoS based on the specified QoS characteristics and the QCIs.
Having thus described certain example embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
Additionally, as used herein, the term ‘circuitry’ refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term ‘circuitry’ also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term ‘circuitry’ as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device (such as a WLAN including a TWAG), field programmable gate array, and/or other computing device.
As defined herein, a “computer-readable storage medium,” which refers to a physical storage medium (e.g., volatile or non-volatile memory device), may be differentiated from a “computer-readable transmission medium,” which refers to an electromagnetic signal.
A method, apparatus and computer program product are provided in accordance with an example embodiment to provide QoS differentiation as described herein.
Examples of an UE apparatus (UE 102) are configured in accordance with an example embodiments of the present disclosure are depicted in
In the processing circuitry 200, the processor 202 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 204 via a bus for passing information among components of the UE 102. The memory device may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.
The UE 102 may, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
The processor 202 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g., an encoder and/or a decoder) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
In embodiments that include a communication interface 208, the communication interface may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the UE 102, such as an WLAN, Core network, a database or other storage device, etc. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
In some embodiments, the UE 102 may include a user interface 206 that may, in turn, be in communication with the processing circuitry 202 to receive an indication of a user input and/or to cause presentation of visual representations of the functions described herein, or the data traffic flow described. As such, the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen(s), touch areas, soft keys, a microphone, a speaker, or other input/output mechanisms. Alternatively or additionally, the processor 202 may comprise user interface circuitry configured to control at least some functions of one or more user interface elements such as, for example, a speaker, ringer, microphone, display, and/or the like. The processor and/or user interface circuitry comprising the processor may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor (e.g., memory device 204, and/or the like).
Examples of a WLAN apparatus (including WLAN 104) as configured in accordance with an example embodiments of the present disclosure are depicted in
In the processing circuitry 300, the processor 302 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 304 via a bus for passing information among components of the WLAN 104. The memory device may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.
The WLAN 104 may, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
The processor 302 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
In an example embodiment, the processor 302 may be configured to execute instructions stored in the memory device 304 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g., an encoder and/or a decoder) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
In embodiments that include a communication interface 306, the communication interface may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the WLAN 104, such as UE, Core network, a database or other storage device, etc. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
As part of EAP-AKA′ authentication via the WLAN 104, the UE 102 and the WLAN 104 first negotiates a trusted wireless network connection mode usage. If Multi-Connection mode (MCM) is selected, the UE 102 establishes a DTLS connection with the TWAG 106 and initiates WLCP procedures. During PDN connection establishment, the UE 102 indicates to the TWAG whether WLCP multiple bearer PDN connectivity capability is supported. If the UE 102 does not indicate that WLCP multiple bearer PDN connectivity is supported, or if the UE 102 indicates that WLCP multiple bearer PDN connectivity is supported but the TWAG does not support WLCP multiple bearer PDN connectivity, then QoS differentiation is not supported. In this instance, single point-to-point PDN connection is used to carry all S2a bearers traffic between the UE 102 and TWAG 106. If WLCP multiple bearer PDN connectivity is supported by both the UE 102 and WLAN 104, then QoS differentiation is supported and multiple bearer PDN connectivity is used between the UE 102 and TWAG. During PDN connection establishment, the TWAG, using processor 302 and memory 304, establishes a default WLCP bearer for the PDN connection. The default WLCP bearer remains established throughout the lifetime of the PDN connection. The TWAG, using processor 302 and memory 304, establishes a separate WLCP bearer for each additional S2a dedicated bearer of the PDN connection. Each WLCP bearer is associated with TFT and bearer level QoS (i.e. QCI, GBR and MBR) for one-to-one mapping between a WLCP bearer and a S2a bearer. The TWAG, using processor 302 and memory 304, maintains the WLCP bearer to the S2a bearer mapping table.
After a WLCP multiple bearer PDN connectivity is established between the UE 102 and the TWAG 106, for uplink packets, the UE 102, using processor 202 and memory 204, selects a WLCP bearer based on the uplink packet filters in the TFTs. If no match is found, the UE 102 selects the WLCP bearer that does not have any uplink packet filter assigned. If all bearers have been assigned an uplink packet filter, the UE 102 using processor 202, discards the uplink data packet. The UE 102 then uses the QCI in WLCP bearer level QoS information to derive a DSCP value for uplink packets. The DSCP value is used to determine the WLAN 802.11 QoS class, user priority and EDCA Access Category over the radio SWw. The TWAG 106 then routes the uplink packets to the corresponding S2a bearers based on the WLCP bearer and the S2a bearer mapping table, which may be stored in memory 304. In some embodiments, UE 102 may map QoS/QCI to DSCP value, for example, by using the recommended mappings between standardized QCIs and Release 99 QoS parameter value, or the mapping specified in IEEE Std. 802.11—2012.
In some examples, for downlink packets, a PDN-GW routes the packets to S2a bearers based on the downlink packet filters in the TFTs assigned to each of the S2a bearers. The TWAG 106 then selects the corresponding WLCP bearer for the downlink packets based on the WLCP bearer and the S2a bearer mapping table. The TWAG 106 may also use the QCI in WLCP bearer level QoS information to derive the DSCP value for uplink packets. The DSCP value is then used to determine the WLAN 802.11 QoS class, user priority and EDCA Access Category over the radio SWw. In some examples, the TWAG, using processor 302 and memory 304, can map QoS/QCI to DSCP value, for example, by using the recommended mappings between standardized QCIs and Release 99 QoS parameter value, or the mapping specified in IEEE Std. 802.11—2012. The operations provide end-to-end QoS differentiation from the core network 108 to the UE 102.
Turning now to
Table 1 illustrates PDN Connectivity Request message. This message is sent by the UE 102 to the TWAG 106 to initiate establishment of a PDN connection.
The UE 102 includes this information element (IE) to indicate UE capabilities related to non-3GPP access when the UE 102 is accessing EPC via trusted non-3GPP access during the PDN connection establishment procedure.
Table 2 illustrates UE N3G capability. The purpose of the UE 102 N3G capability information element is to provide the WLAN 104 with information concerning aspects of the UE 102 capabilities related to trusted non-3GPP access. The contents of UE N3G capability may affect the manner in which the WLAN 104 handles the operation of the UE 102. The UE 102 N3G capability is a type 3 information element and coded as shown in Table 2.
Referring back to
Additionally, the TWAG 106 proceeds as shown in
Otherwise, if the UE 102 did not indicate support of multiple bearer PDN connectivity capability in the received PDN CONNECTIVITY REQUEST message or if the UE 102 indicated support of multiple bearer PDN connectivity capability but the TWAG 106 does not support multiple bearer PDN connectivity feature, the TWAG 106 selects to use a Single point-to-point connectivity model. The TWAG 106 then assigns a PDN connection ID and include in the PDN CONNECTIVITY ACCEPT message. The message includes a PDN connection ID to identify the PDN connection between the UE 102 and the TWAG 106 and MAC address of the TWAG to the UE 102. This MAC address is used by the UE 102 and the TWAG to send the user plane packets for this PDN connection.
Table 3 illustrates a PDN Connectivity Accept message according to example embodiments. The message illustrated is sent by the WLAN 104 to the UE 102 to acknowledge activation of a PDN connection.
In some examples, the TWAG 106 includes this IE if multiple bearer PDN connectivity is used and the TWAG 106 has assigned a WLCP bearer identity for the default WLCP bearer of the newly activated PDN connection.
Table 4 illustrates a WLCP bearer identity Information element according to example embodiments. The WLCP bearer identity IE identifies a WLCP bearer (default or dedicated) with which one or more packet filters specified in a traffic flow aggregate are associated. The WLCP bearer identity information element is coded as shown in Table 4. In some examples, the WLCP bearer identity is a type 3 information element.
Table 5 illustrates a PDN Connectivity Complete message according to an example embodiment. In some examples, This message is sent by the UE 102 to acknowledge establishment of a PDN connection.
As shown, the UE 102 includes this IE to acknowledge usage of multiple bearer PDN connectivity if WLCP bearer identity was included in the PDN connectivity accept message.
In an instant the WLCP bearer setup procedure is initiated by the TWAG 106, the TWAG 106 initiates the WLCP bearer setup procedure by sending a WLCP BEARER SETUP REQUEST message to the UE 102, starts the timer T3587, and enter the state WLCP BEARER CONTEXT ACTIVE PENDING as shown in
Upon receipt of the WLCP BEARER SETUP REQUEST message, the UE 102 checks the received TFT before taking it into use, sends a WLCP BEARER SETUP ACCEPT message and enters the state WLCP BEARER CONTEXT ACTIVE. The WLCP BEARER SETUP ACCEPT message includes the WLCP bearer identity. The UE 102 uses the received TFT to apply mapping of uplink traffic flows to the WLCP bearer and treats any packet filter without explicit direction as being bi-directional.
Upon receipt of the WLCP BEARER SETUP ACCEPT message, the TWAG 106 stops the timer T3587 and enters the state WLCP BEARER CONTEXT ACTIVE, as shown in
In another example, upon receipt of the WLCP BEARER SETUP REQUEST message, the UE 102 may reject the request from the TWAG 106 by sending a WLCP BEARER SETUP REJECT message. The UE 102 includes the WLCP bearer identity and cause the IE to indicate the reason for rejection in the WLCP BEARER SETUP REJECT message. Upon receipt of the WLCP BEARER SETUP REJECT message in state WLCP BEARER CONTEXT ACTIVE PENDING, the TWAG 106 aborts the WLCP bearer setup procedure, stops the timer T3587, if the timer is running, and enters the state WLCP BEARER CONTEXT INACTIVE, as shown in
Upon receipt of the WLCP BEARER MODIFY REQUEST message, the UE 102 checks the received TFT before taking it into use, sends a WLCP BEARER MODIFY ACCEPT message and enter the state WLCP BEARER CONTEXT ACTIVE. The WLCP BEARER MODIFY ACCEPT message includes the WLCP bearer identity. The UE 102 uses the received TFT to apply mapping of uplink traffic flows to the WLCP bearer and treats any packet filter without explicit direction as being bi-directional. If the bearer level QoS parameter contained in WLCP BEARER MODIFY REQUEST message does not contain the Guaranteed Bit Rate (GBR) and the Maximum Bit Rate (MBR) values for uplink and downlink, and the WLCP bearer being modified is a GBR bearer, the UE 102 continues to use the previously received GBR and MBR values.
The UE 102 uses the received TFT to apply mapping of uplink traffic flows to the WLCP bearer if the TFT contains packet filters for the uplink direction. Upon receipt of the WLCP BEARER MODIFY ACCEPT message, the TWAG 106 stops the timer T3588 and enter the state WLCP BEARER CONTEXT ACTIVE, as shown in
In another example as shown in
Upon receipt of the WLCP BEARER MODIFY REJECT message with cause value other than “invalid WLCP bearer identity” (where this cause code is used by the TWAG 106 or the UE 102 to indicate that the WLCP bearer identity value provided to it is not a valid value for the received message or the PDN connection ID provided in the request is not active) in state BEARER CONTEXT MODIFY PENDING, the TWAG 106 aborts the WLCP bearer modify procedure, stops the timer T3588, if the timer is running, and enters the state WLCP BEARER CONTEXT ACTIVE. If the TWAG receives the WLCP BEARER MODIFY REJECT message with cause “invalid WLCP bearer identity.” The TWAG 106 also locally deactivates the WLCP bearer without peer-to-peer signaling.
If the WLCP bearer to be released is a default WLCP bearer, the TWAG 106 invokes PDN disconnect procedure to disconnect the PDN connection and release all associated WLCP bearers.
In some examples, the TWAG 106 initiates the WLCP bearer release procedure by sending a WLCP BEARER RELEASE REQUEST message to the UE 102, starts the timer T3597, and enters the state WLCP BEARER CONTEXT INACTIVE PENDING. The WLCP BEARER RELEASE REQUEST message contains a cause typically indicating one of the following: #8 operator determined barring; #26 insufficient resources; #36 regular deactivation; or #38 network failure.
Upon receipt of the WLCP BEARER RELEASE REQUEST message, the UE 102 deletes the WLCP bearer identified by the WLCP bearer identity, sends a WLCP BEARER RELEASE ACCEPT message, and enters the state WLCP BEARER CONTEXT INACTIVE. The WLCP BEARER RELEASE ACCEPT message includes the WLCP bearer identity.
Furthermore, upon receipt of the WLCP BEARER RELEASE ACCEPT message, the TWAG 106 stops the timer T3597 and enters the state WLCP BEARER CONTEXT INACTIVE, as shown in
In another example, the WLCP bearer release procedure is not accepted by the UE 102, as shown in
Upon receipt of the WLCP BEARER RELEASE REJECT message in state WLCP BEARER CONTEXT INACTIVE PENDING, the TWAG 106 aborts the WLCP bearer release procedure, stops the timer T3597, if the timer is running, and enters the state WLCP BEARER CONTEXT INACTIVE.
As described above, the system 100 may include new WLCP Timers on TWAG 106 side. The following new WLCP timers include: T3587—Wait for WLCP BEARER SETUP ACCEPT message, T3588—Wait for WLCP BEARER MODIFY ACCEPT message, and T3597—Wait for WLCP BEARER RELEASE ACCEPT message. Table 6A below shows the handlings of the timers:
As described above, the system 100 may include new WLCP Messages, as shown in Table 6B, including a WLCP bearer setup request, a WLCP bearer setup accept, a WLCP bearer setup reject, a WLCP bearer modify request, a WLCP bearer modify accept, a WLCP bearer modify reject, a WLCP bearer release request, a WLCP bearer release accept, and a WLCP bearer release reject. These are shown in Table 6B.
Each of the messages are described further including the WLCP bearer setup procedure related messages which includes the Bearer setup request. This message is sent by the TWAG 106 to the UE 102 to request activation of a WLCP bearer for the given PDN connection as shown in Table 7.xx.1.1.
The Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer setup procedure related messages also includes bearer setup accept shown in Table 7.xy.1.1. This message is sent by the UE 102 to the TWAG to acknowledge activation of a WLCP bearer context associated with the given PDN connection ID.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer setup procedure related messages also includes Bearer setup reject shown in Table 7.xz.1.1. This message is sent by the UE 102 to the TWAG to reject creation of a WLCP bearer for the given PDN connection.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer modify procedure related messages include a bearer modify request as shown in Table 7.yx.1.1. This message is sent by the TWAG to the UE 102 to request activation of a WLCP bearer for the given PDN connection.
The Bearer QoS is included in the message when the TWAG requests a change of QoS for the indicated traffic flows.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer modify procedure related messages also include bearer modify accept as shown in Table 7.yy.1.1. This message is sent by the UE 102 to the TWAG to acknowledge activation of a WLCP bearer context associated with the given PDN connection ID.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer modify procedure related messages also include bearer modify reject as shown in Table 7.yz.1.1. This message is sent by the UE 102 to the TWAG to reject creation of a WLCP bearer for the given PDN connection.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer release procedure related messages include a bearer release request as shown in Table 7.zx.1.1. This message is sent by the TWAG to the UE 102 to request activation of a WLCP bearer for the given PDN connection.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer release procedure related messages also include bearer release accept as shown in Table 7.zy.1.1. This message is sent by the UE 102 to the TWAG to acknowledge activation of a WLCP bearer context associated with the given PDN connection ID.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
The WLCP bearer release procedure related messages also include bearer release reject as shown in Table 7.zz.1.1. This message is sent by the UE 102 to the TWAG to reject creation of a WLCP bearer for the given PDN connection.
Protocol configuration options are included in the message when the UE 102 or the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE 102.
Referring now to
As shown in block 1004 of
As shown in block 1006 of
As shown in block 1008 of
Referring now to
As shown in block 1104 of
As shown in block 1106 of
As shown in block 1108 of
Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
| Number | Date | Country | |
|---|---|---|---|
| 62534355 | Jul 2017 | US |
