阅读说明：本技术 用于修改映射规则的方法和设备 (Method and apparatus for modifying mapping rules ) 是由 边大旭 赵嬉静 徐健 金鉐中 于 2019-02-13 设计创作，主要内容包括：提供了一种用于在无线通信系统中由基站(BS)的中央单元(CU)修改QoS流到DRB映射规则的方法以及支持该方法的设备。该方法可以包括以下步骤：修改QoS流到DRB映射规则；确定修改后的QoS流到DRB映射规则是否与反射映射有关；以及当确定修改后的QoS流到DRB映射规则与反射映射无关时,将修改后的QoS流到DRB映射规则发送到用户设备(UE)。(A method for modifying a QoS flow to DRB mapping rule by a Central Unit (CU) of a Base Station (BS) in a wireless communication system and an apparatus supporting the same are provided. The method may comprise the steps of: modifying the QoS flow to DRB mapping rule; determining whether the modified QoS flow to DRB mapping rule is related to a reflection mapping; and transmitting the modified QoS flow to DRB mapping rule to a User Equipment (UE) when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping.)

1. A method for modifying QoS flow to DRB mapping rules by a central unit, CU, of a base station, BS, in a wireless communication system, the method comprising the steps of:

modifying the QoS flow to DRB mapping rule;

determining whether the modified QoS flow to DRB mapping rule is related to a reflection mapping; and

sending the modified QoS flow to DRB mapping rule to a user Equipment, UE, when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping.

2. The method of claim 1, wherein the modified QoS flow to DRB mapping rule is not transmitted when it is determined that the modified QoS flow to DRB mapping rule relates to the reflection mapping.

3. The method of claim 1, wherein the CU comprises a CU-CP and at least one CU-UP.

4. The method of claim 3 wherein the CU-CP is a logical node hosting the control plane part of the RRC and PDCP protocols of the CU, and

wherein the at least one CU-UP is a logical node hosting the SDAP protocol of the CU and a user plane portion of the PDCP protocol.

5. The method of claim 3, wherein information for modifying the QoS flow to DRB mapping rule is sent from the at least one CU-UP to the CU-CP.

6. The method of claim 5, wherein the CU-CP modifies the QoS flow to DRB mapping rule based on the information.

7. The method of claim 6, wherein the modified QoS flow to DRB mapping rule is sent from the CU-CP to the at least one CU-UP.

8. The method of claim 5, wherein the information comprises at least one QoS flow that does not meet QoS requirements.

9. The method of claim 8, wherein the CU-CP modifies the QoS flow to DRB mapping rule based on the at least one QoS flow.

10. The method of claim 1, wherein the modified QoS flow to DRB mapping rule is transmitted to the UE via a distribution unit, DU, of the BS.

11. The method of claim 10, wherein the modified QoS flow to DRB mapping rule is sent to the DU by being included in a DL RRC messaging message.

12. The method of claim 10, wherein the modified QoS flow to DRB mapping rule is transmitted to the UE by being included in an RRC reconfiguration message.

13. The method of claim 10, wherein the CU is a logical node hosting RRC, SDAP, and PDCP protocols of the BS, and

wherein the DU is a logical node hosting RLC, MAC, and PHY layers of the BS.

14. A method for receiving a modified QoS flow to DRB mapping rule by a user equipment, UE, in a wireless communication system, the method comprising:

receiving said modified QoS flow to DRB mapping rule from the central unit CU of the base station BS,

wherein the modified QoS flow to DRB mapping rule is independent of a reflection mapping.

15. A central unit, CU, of a base station, BS, the CU of the BS being for modifying QoS flow to DRB mapping rules in a wireless communication system, the CU of the BS comprising:

a transceiver;

at least one processor; and

at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to:

modifying the QoS flow to DRB mapping rule;

determining whether the modified QoS flow to DRB mapping rule is related to a reflection mapping; and

and when the modified QoS flow-to-DRB mapping rule is determined to be unrelated to the reflection mapping, sending the modified QoS flow-to-DRB mapping rule to User Equipment (UE).

Technical Field

The present invention relates to a wireless communication system, and more particularly, to a method for modifying a QoS flow to DRB mapping rule by a Central Unit (CU) of a Base Station (BS) in a wireless communication system and an apparatus supporting the same.

Background

In order to meet the increasing demand for wireless data services since the commercialization of fourth generation (4G) communication systems, efforts are being made to develop improved fifth generation (5G) communication systems or 5G pre-communication systems. For this reason, the 5G communication system or the 5G pre-communication system is referred to as a super 4G network communication system or a post Long Term Evolution (LTE) system.

Disclosure of Invention

Technical problem

Furthermore, in 5G NR, the separation of gNB-CU-CP and gNB-CU-UP has been discussed. Because the CU-UP hosts the SDAP protocol that supports the functionality of mapping between QoS flows and DRBs for both downlink and uplink, the CU-UP may be able to modify QoS flow to DRB mapping rules based on the current status of downlink and/or uplink traffic on, for example, F1-U and/or NG-U. On the other hand, while a CU-UP hosts an SDAP protocol that supports the functionality of mapping between QoS flows and DRBs for both downlink and uplink, a CU-UP may be able to request from a CU-CP to modify QoS flow-to-DRB mapping rules based on current conditions. This is because the CU-CP can generate QoS flow to DRB mapping rules and the CU-UP performs mapping between QoS flows and DRBs. However, currently no QoS flow to DRB remapping hosted by CU-UP or CU-CP is supported in the separation of CU-CP and CU-UP. Therefore, there is a need to suggest a QoS flow to DRB remapping procedure in the split scenario of gNB-CU-CP and gNB-CU-UP.

Furthermore, there may be a reflection QoS flow to DRB mapping between QoS flow to DRB mappings. Unlike QoS flow to DRB remapping, there is no need (through CU-CP in the case where CU-UP provides QoS flow to DRB mapping rules) to provide a reflective QoS flow to DRB remapping for the UE. This is because the SDAP in the CU-UP sends downlink data with RQI set to 1 or RDI set to 1 to the UE through the remapped DRB. Upon receiving the data, the UE stores the QoS flow to DRB mapping as a QoS flow to DRB mapping rule for the uplink. Therefore, QoS flow to DRB remapping solutions hosted by CU-UP or CU-CP are necessary in view of the reflected QoS flow to DRB mapping.

Solution to the problem

One embodiment provides a method for modifying a QoS flow to DRB mapping rule by a Central Unit (CU) of a Base Station (BS) in a wireless communication system. The method can comprise the following steps: modifying the QoS flow to DRB mapping rule; determining whether the modified QoS flow to DRB mapping rule is related to a reflection mapping; and sending the modified QoS flow to DRB mapping rule to User Equipment (UE) when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping.

Another embodiment provides a Central Unit (CU) of a Base Station (BS) for modifying a QoS flow to DRB mapping rule in a wireless communication system. The CU may include: a transceiver; at least one processor; at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to: modifying the QoS flow to DRB mapping rule; determining whether the modified QoS flow to DRB mapping rule is related to a reflection mapping; and transmitting the modified QoS flow to DRB mapping rule to a User Equipment (UE) when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping.

Another embodiment provides a method for receiving a modified QoS flow to DRB mapping rule by a User Equipment (UE) in a wireless communication system. The method can comprise the following steps: receiving a modified QoS flow to DRB mapping rule from a Central Unit (CU) of a Base Station (BS), wherein the modified QoS flow to DRB mapping rule is independent of a reflection mapping.

Advantageous effects of the invention

The user experience may be improved and the RAN node may better process data packets for a particular UE.

Drawings

Fig. 1 shows an example of a wireless communication system to which the technical features of the present invention can be applied.

Fig. 2 shows another example of a wireless communication system to which the technical features of the present invention can be applied.

Fig. 3 shows a block diagram of a user plane protocol stack to which the technical features of the present invention can be applied.

Fig. 4 shows a block diagram of a control plane protocol stack to which the technical features of the present invention can be applied.

Fig. 5 shows a functional division between the NG-RAN and the 5GC to which the technical features of the present invention can be applied.

Fig. 6 shows the general architecture of a NG-RAN to which the technical features of the present invention can be applied.

Fig. 7 shows a separated general architecture of the gNB-CU-CP and the gNB-CU-UP to which the technical features of the present invention can be applied.

Fig. 8 illustrates a mapping between QoS flows and DRBs to which the technical features of the present invention can be applied.

Fig. 9 illustrates a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

Fig. 10a and 10b illustrate a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

Fig. 11 illustrates a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

Fig. 12 illustrates a procedure of modifying a QoS flow to DRB mapping rule by a Central Unit (CU) of a Base Station (BS) according to an embodiment of the present invention.

Fig. 13 shows a BS for implementing an embodiment of the present invention.

Fig. 14 illustrates a method for receiving a modified QoS flow to DRB mapping rule by a UE according to an embodiment of the present invention.

Fig. 15 shows a UE implementing an embodiment of the present invention.

Detailed Description

In this document, the terms "/" and "," should be interpreted as indicating "and/or". For example, the expression "a/B" may mean "a and/or B". Further, "A, B" may mean "a and/or B". Further, "a/B/C" may mean "A, B and/or at least one of C. "additionally," A, B, C "can mean" A, B and/or at least one of C. "

Further, in this document, the term "or" should be interpreted as indicating "and/or". For example, the expression "a or B" may include 1) only a, 2) only B and/or 3) both a and B. In other words, the term "or" in this document should be interpreted as indicating "additionally or alternatively".

The technical features described below may be used by communication standards of the third generation partnership project (3GPP) standardization organization, communication standards of the Institute of Electrical and Electronics Engineers (IEEE), and the like. For example, communication standards passing through the 3GPP standardization organization include Long Term Evolution (LTE) and/or evolution of LTE systems. The evolution of the LTE system includes LTE-advanced (LTE-A), LTE-A Pro, and/or 5G New Radio (NR). The IEEE organization for standardization's communication standards include Wireless Local Area Network (WLAN) systems such as IEEE 802.11 a/b/g/n/ac/ax. The above-described systems use various multiple access techniques, such as Orthogonal Frequency Division Multiple Access (OFDMA) and/or single carrier frequency division multiple access (SC-FDMA), for the Downlink (DL) and/or uplink (DL). For example, only OFDMA may be used for DL and only SC-FDMA may be used for UL. Alternatively, OFDMA and SC-FDMA can be used for DL and/or UL.

Fig. 1 shows an example of a wireless communication system to which the technical features of the present invention can be applied. In particular, FIG. 1 illustrates a system architecture based on an evolved UMTS terrestrial radio Access network (E-UTRAN). The aforementioned LTE is part of evolved UTMS (E-UMTS) using E-UTRAN.

Referring to FIG. 1, a wireless communication system includes one or more user equipments (UEs; 10), an E-UTRAN, and an Evolved Packet Core (EPC). The UE 10 refers to a communication device carried by a user. The UE 10 may be fixed or mobile. The UE 10 may be referred to by another terminology, such as a Mobile Station (MS), a User Terminal (UT), a Subscriber Station (SS), a wireless device, etc.

The E-UTRAN consists of one or more Base Stations (BSs) 20. The BS 20 provides the UE 10 with E-UTRA user plane and control plane protocol end points. The BS 20 is typically a fixed station that communicates with the UE 10. The BS 20 hosts functions such as inter-cell radio resource management (MME), Radio Bearer (RB) control, connection mobility control, radio admission control, measurement configuration/setting, dynamic resource allocation (scheduler), etc. The BS may be referred to as another term, such as evolved nodeb (enb), Base Transceiver System (BTS), Access Point (AP), and the like.

Downlink (DL) denotes communication from the BS 20 to the UE 10. The Uplink (UL) denotes communication from the UE 10 to the BS 20. The Sidelink (SL) represents communication between the UEs 10. In DL, a transmitter may be a part of the BS 20, and a receiver may be a part of the UE 10. In the UL, the transmitter may be a part of the UE 10, and the receiver may be a part of the BS 20. In SL, the transmitter and receiver may be part of the UE 10.

The EPC includes a Mobility Management Entity (MME), a serving gateway (S-GW), and a Packet Data Network (PDN) gateway (P-GW). The MME hosts functions such as non-access stratum (NAS) security, idle state mobility handling, Evolved Packet System (EPS) bearer control, etc. The S-GW hosts functions such as mobility anchoring and the like. The S-GW is a gateway with E-UTRAN as an end. For convenience, the MME/S-GW 30 will be referred to herein simply as a "gateway," but it should be understood that this entity includes both an MME and an S-GW. The P-GW hosts such functions as UE Internet Protocol (IP) address assignment, packet filtering, etc. The P-GW is a gateway having a PDN as an end. The P-GW is connected to an external network.

The UE 10 is connected to the BS 20 through a Uu interface. The UEs 10 are interconnected to each other by a PC5 interface. The BSs 20 are interconnected with each other through an X2 interface. The BS 20 is also connected to the EPC through an S1 interface, more specifically, to the MME through an S1-MME interface and to the S-GW through an S1-U interface. The S1 interface supports a many-to-many relationship between the MME/S-GW and the BS.

Fig. 2 shows another example of a wireless communication system to which the technical features of the present invention can be applied. In particular, fig. 2 shows a system architecture based on a 5G new radio access technology (NR) system. An entity (hereinafter, abbreviated as "NR") used in the 5G NR system may include part or all of the functions of the entities (e.g., eNB, MME, S-GW) introduced in fig. 1. The entities used in the NR system may be identified by the name "NG" to distinguish them from LTE/LTE-a.

Referring to fig. 2, the wireless communication system includes one or more UEs 11, a next generation RAN (NG-RAN), and a fifth generation core network (5 GC). The NG-RAN comprises at least one NG-RAN node. The NG-RAN node is an entity corresponding to the BS 10 shown in fig. 1. The NG-RAN node comprises at least one gNB 21 and/or at least one NG-eNB 22. The gNB 21 provides NR user plane and control plane protocol endpoints to the UE 11. The ng-eNB 22 provides E-UTRA user plane and control plane protocol end points to the UE 11.

The 5GC includes an access and mobility management function (AMF), a User Plane Function (UPF), and a Session Management Function (SMF). The AMF hosts such functions as NAS security, idle state mobility handling, etc. The AMF is an entity that includes the functionality of a conventional MME. The UPF hosts functions such as mobility anchoring, Protocol Data Unit (PDU) handling. The UPF is an entity that includes the functionality of a conventional S-GW. SMF hosts functions such as UE IP address assignment, PDU session control.

The gNB and ng-eNB are interconnected to each other by an Xn interface. The gNB and NG-eNB are also connected to the 5GC over an NG interface, more specifically to the AMF over an NG-C interface and to the UPF over an NG-U interface.

The protocol structure between the above network entities is described. On the system of fig. 1 and/or 2, layers of a radio interface protocol (e.g., NG-RAN and/or E-UTRAN) between the UE and the network may be divided into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of an Open System Interconnection (OSI) model, which is well known in the communication systems.

Fig. 3 shows a block diagram of a user plane protocol stack to which the technical features of the present invention can be applied. Fig. 4 shows a block diagram of a control plane protocol stack to which the technical features of the present invention can be applied. The user/control plane protocol stacks shown in fig. 3 and 4 may be used in the NR. However, without loss of generality, the user/control plane protocol stack shown in fig. 3 or fig. 4 can be used in LTE/LTE-a by replacing the gbb/AMF with an eNB/MME.

Referring to fig. 3 and 4, a Physical (PHY) layer belongs to L1. The PHY layer provides an information transfer service to a Medium Access Control (MAC) sublayer and higher layers. The PHY layer provides a transport channel for the MAC sublayer. Data between the MAC sublayer and the PHY layer is transmitted through a transport channel. Between different PHY layers, that is, between a PHY layer of a transmitting side and a PHY layer of a receiving side, data is transmitted via a physical channel.

The MAC sublayer belongs to L2. The main services and functions of the MAC sublayer include mapping between logical channels and transport channels, multiplexing/de-multiplexing MAC Service Data Units (SDUs) belonging to one or different logical channels to/from the physical layer on the transport channels, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling between UEs through dynamic scheduling, priority handling between logical channels of one UE through Logical Channel Prioritization (LCP), and the like. The MAC sublayer provides logical channels to the Radio Link Control (RLC) sublayer.

The RLC sublayer belongs to L2. The RLC sublayer supports three transmission modes, i.e., a Transparent Mode (TM), an Unacknowledged Mode (UM), and an Acknowledged Mode (AM), to guarantee various qualities of service (QoS) required for radio bearers. The main services and functions of the RLC sublayer depend on the transmission mode. For example, the RLC sublayer provides transmission of upper layer PDUs for all three modes, but only error correction by ARQ for AM. In LTE/LTE-a, the RLC sublayer provides concatenation, segmentation and reassembly of RLC SDUs (for UM and AM data transmission only) and re-segmentation of RLC data PDUs (for AM data transmission only). In NR, the RLC sublayer provides segmentation (for AM and UM only) and re-segmentation (for AM only) of RLC SDUs and reassembly (for AM and UM only) of SDUs. That is, NR does not support connection of RLC SDUs. The RLC sublayer provides an RLC channel to a Packet Data Convergence Protocol (PDCP) sublayer.

The PDCP sublayer belongs to L2. The major services and functions of the PDCP sublayer for the user plane include header compression and decompression, transmission of user data, duplicate detection, PDCP PDU routing, retransmission of PDCP SDUs, ciphering and deciphering, etc. The PDCP sublayer has major services and functions for the control plane including ciphering and integrity protection, transmission of control plane data, and the like.

The Service Data Adaptation Protocol (SDAP) sublayer belongs to L2. The SDAP sublayer is defined only in the user plane. The SDAP sublayer is limited only to NR. The main services and functions of the SDAP include mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow ids (qfis) in both DL and UL data packets. The SDAP sublayer provides the 5GC with QoS flows.

The Radio Resource Control (RRC) layer belongs to L3. The RRC layer is defined only in the control plane. The RRC layer controls radio resources between the UE and the network. For this, the RRC layer exchanges RRC messages between the UE and the BS. The main services and functions of the RRC layer include broadcasting system information related to AS and NAS, paging, establishing, maintaining and releasing RRC connections between the UE and the network, security functions including key management, establishing, configuring, maintaining and releasing radio bearers, mobility functions, QoS management functions, UE measurement reporting and report control, NAS message transmission from the UE to the NAS or from the NAS to the UE.

In other words, the RRC layer controls logical channels, transport channels, and physical channels related to configuration, reconfiguration, and release of radio bearers. The radio bearer refers to a logical path provided by L1(PHY layer) and L2(MAC/RLC/PDCP/SDAP sublayer) for data transmission between the UE and the network. Setting the radio bearer means defining the characteristics of a radio protocol layer and a channel for providing a specific service, and setting each specific parameter and operation method. Radio bearers can be divided into signaling rbs (srbs) and data rbs (drbs). The SRB serves as a path for transmitting RRC messages in the control plane, and the DRB serves as a path for transmitting user data in the user plane.

The RRC state indicates whether the RRC layer of the UE is logically connected to the RRC layer of the E-UTRAN. In LTE/LTE-A, when an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in an RRC CONNECTED state (RRC _ CONNECTED). Otherwise, the UE is in an RRC IDLE state (RRC _ IDLE). In NR, an RRC invalid state (RRC _ INACTIVE) is also introduced. RRC _ INACTIVE may be used for various purposes. For example, a large-scale machine type communication (MMTC) UE may be efficiently managed in RRC _ INACTIVE. When a certain condition is satisfied, a transition is made from one of the above three states to the other state.

The predetermined operation may be performed according to the RRC state. In RRC _ IDLE, Public Land Mobile Network (PLMN) selection, broadcasting of System Information (SI), cell reselection mobility, Core Network (CN) paging, and Discontinuous Reception (DRX) configured by NAS may be performed. A UE should be assigned an Identifier (ID) that uniquely identifies the UE in the tracking area. No RRC context is stored in the base station.

In RRC _ CONNECTED, the UE has an RRC connection with the network (i.e., E-UTRAN/NG-RAN). network-CN connections (C-plane as well as U-plane) are also established for the UE. The UE AS context is stored in the network and in the UE. The RAN knows the cell to which the UE belongs. The network may transmit data to and/or receive data from the UE. Network controlled mobility including measurements is also performed.

Most of the operations performed in RRC _ IDLE may be performed in RRC _ INACTIVE. However, unlike CN paging in RRC _ IDLE, RAN paging is performed in RRC _ INACTIVE. In other words, in RRC _ IDLE, paging of mobile endpoint (MT) data is initiated by the core network, while the paging area is managed by the core network. In RRC _ INACTIVE, paging is initiated by the NG-RAN, while RAN-based notification areas (RNAs) are managed by the NG-RAN. Further, unlike DRX configured by NAS for CN paging in RRC IDLE, DRX for RAN paging is configured by NG-RAN in RRC IDLE. Meanwhile, in RRC _ INACTIVE, 5GC-NG-RAN connections (C-plane and U-plane) are established for the UE, and UE AS context is stored in NG-RAN and UE. The NG-RAN knows the RNA to which the UE belongs.

The NAS layer is located on top of the RRC layer. The NAS control protocol performs functions such as authentication, mobility management, and security control.

The physical channel may be modulated according to the OFDM process and utilize time and frequency as radio resources. The physical channel is composed of a plurality of Orthogonal Frequency Division Multiplexing (OFDM) symbols in a time domain and a plurality of subcarriers in a frequency domain. One subframe is composed of a plurality of OFDM symbols in the time domain. A resource block is a resource allocation unit and is composed of a plurality of OFDM symbols and a plurality of subcarriers. In addition, each subframe may use a specific subcarrier of a specific OFDM symbol (e.g., a first OFDM symbol) of the corresponding subframe for a Physical Downlink Control Channel (PDCCH), i.e., an L1/L2 control channel. A Transmission Time Interval (TTI) is a basic unit of time used by a scheduler for resource allocation. The TTI may be defined in units of one or more slots, or may be defined in units of minislots.

The transmission channels are classified according to the way and characteristics of data transmission over the radio interface. The DL transport channels include a Broadcast Channel (BCH) for transmitting system information, a downlink shared channel (DL-SCH) for transmitting user traffic or control signals, and a Paging Channel (PCH) for paging the UE. The UL transport channels include an uplink shared channel (UL-SCH) for transmitting user traffic or control signals and a Random Access Channel (RACH) generally used for initial access to a cell.

The MAC sublayer provides different kinds of data transmission services. Each logical channel type is defined according to the type of information transmitted. Logical channels are divided into two categories: control channels and traffic channels.

The control channel is used only for transmission of control plane information. The control channels include a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), and a Dedicated Control Channel (DCCH). The BCCH is a DL channel for broadcasting system control information. The PCCH is a DL channel for transmitting paging information, system information change notification. The CCCH is a channel for transmitting control information between the UE and the network. This channel is used for UEs that have no RRC connection with the network. The DCCH is a point-to-point bi-directional channel that transports dedicated control information between the UE and the network. The UE having the RRC connection uses the channel.

The traffic channel is used only for transmission of user plane information. The traffic channels include a Dedicated Traffic Channel (DTCH). A DTCH is a point-to-point channel dedicated to one UE for the transmission of user information. DTCH may be present in both UL and DL.

Regarding the mapping between logical channels and transport channels, in DL, BCCH may be mapped to BCH, BCCH may be mapped to DL-SCH, PCCH may be mapped to PCH, CCCH may be mapped to DL-SCH, DCCH may be mapped to DL-SCH, and DTCH may be mapped to DL-SCH. In the UL, CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, and DTCH may be mapped to UL-SCH.

Fig. 5 shows a functional division between the NG-RAN and the 5GC to which the technical features of the present invention can be applied.

Referring to fig. 5, the gNB and ng-eNB may host the following functions:

-functions for radio resource management: radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink and downlink (scheduling);

-IP header compression, encryption and integrity protection of data;

-selection of AMF at UE attachment when the information provided from UE cannot determine the route to AMF;

-routing of user plane data towards the UPF;

-routing of control plane information towards the AMF;

-connection establishment and release;

-scheduling and transmission of paging messages;

scheduling and transmission of system broadcast information (originating from AMF or O & M);

-measurement and measurement reporting configuration with respect to mobility and scheduling;

-transport layer packet marking in uplink;

-session management;

-supporting network fragmentation;

-QoS traffic management and mapping to data radio bearers;

-support for UEs in RRC _ INACTIVE (RRC _ deactivated) state;

-a function of distribution of NAS messages;

-radio access network sharing;

-dual connectivity;

tight interworking between-NR and E-UTRA.

The access and mobility management function (AMF) may host the following main functions:

-NAS signaling termination;

-NAS signalling security;

-AS security control;

-inter-CN node signalling for mobility between 3GPP access networks;

idle mode UE reachability (including control and execution of paging retransmissions);

-registration area management;

-supporting intra-system and inter-system mobility;

-an access authentication;

-access authorization, including checking roaming rights;

mobility management control (subscription and policy);

-supporting network fragmentation;

-SMF selection.

The User Plane Function (UPF) may host the following main functions:

anchor point of intra/inter RAT mobility (when applicable);

-an external PDU session point interconnected to the data network;

-packet routing and forwarding;

-a user plane part of packet inspection and policy rule enforcement;

-service usage reporting;

-an uplink classifier to support routing of traffic to a data network;

-a branch point to support multi-homed PDU sessions;

QoS handling for the user plane, e.g. packet filtering, gating, UL/DL rate enforcement;

-uplink traffic validation (SDF to QoS traffic mapping);

-downlink packet buffering and downlink data notification triggering.

The Session Management Function (SMF) may host the following main functions:

-session management;

-UE IP address assignment and management;

-selection and control of UP functions;

-configuring traffic steering at the UPF to route traffic to an appropriate destination;

-control part of policy enforcement and QoS;

-downlink data notification.

Fig. 6 shows the general architecture of a NG-RAN to which the technical features of the present invention can be applied.

Referring to fig. 6, the NG-RAN may include a group of gnbs connected to the 5GC through an NG interface. The gbb may support FDD mode, TDD mode, or dual mode operation. The gnbs may be interconnected by an Xn interface. The gNB can include a gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU). The gNB-CU can be a logical node hosting the RRC, SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB that control the operation of one or more gNB-DUs. The gNB-CU may terminate the F1 interface connected with the gNB-DU. The gNB-DU may be a logical node of the RLC, MAC, and PHY layers hosting the gNB or en-gNB, and its operation is controlled in part by the gNB-CU. One gNB-DU may support one or more cells. One cell can be supported by only one gbb-DU. The gNB-DU may terminate the F1 interface connected with the gNB-CU. One gNB-DU is connected to only one gNB-CU. To be resilient, the gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. NG, Xn, and F1 are logical interfaces.

Fig. 7 shows a separated general architecture of the gNB-CU-CP and the gNB-CU-UP to which the technical features of the present invention can be applied.

Referring to fig. 7, the gNB may include a gNB-CU control plane (gNB-CU-CP), a plurality of gNB-CU user planes (gNB-CU-UP), and a plurality of gNB-DUs. The gNB-CU-CP may be a logical node hosting the control plane portion of the PDCP protocol for the RRC and gNB-CUs of the en-gNB or gNB. The gNB-CU-CP may terminate the E1 interface connected with the gNB-CU-UP and the F1-C interface connected with the gNB-DU. The gNB-CU-UP can be a logical node hosting the user plane part of the PDCP protocol for the gNB-CU of the en-gNB and the user plane part of the SDAP protocol and PDCP protocol for the gNB-CU of the gNB. The gNB-CU-UP may terminate the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU.

The gNB-CU-CP may be connected to the gNB-DU via the F1-C interface. The gNB-CU-UP may be connected to the gNB-DU via the F1-U interface. The gNB-CU-UP may be connected to the gNB-CU-CP through an E1 interface. One gNB-DU can only be connected to one gNB-CU-CP. One gNB-CU-UP can only be connected to one gNB-CU-CP. To be resilient, the gNB-DU and/or gNB-CU-UP may be connected to multiple gNB-CU-CPs by a suitable implementation. One gNB-DU may be connected to multiple gNB-CU-UP under the control of the same gNB-CU-CP. One gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP. The gNB-CU-CP may use a bearer context management function to establish a connection between the gNB-CU-UP and the gNB-DU. The gNB-CU-CP may select the appropriate gNB-CU-UP for the service requested by the UE. In the case of multiple CU-Up, they may belong to the same security domain. The Xn-U may support data forwarding between the gNB-CU-UPs during intra-gNB-CU-CP handover within the gNB.

Fig. 8 illustrates a mapping between QoS flows and DRBs to which the technical features of the present invention can be applied.

In the uplink, the BS may control the mapping of QoS flows to DRBs using reflection mapping or explicit configuration. In the reflective mapping, for each DRB, the UE may monitor the QoS flow ID of the downlink packet and may apply the same mapping in the uplink. That is, for a DRB, the UE may map uplink packets belonging to a QoS flow corresponding to a PDU session and a QoS flow ID observed in downlink packets of the DRB. To enable reflection mapping, the BS may mark downlink packets via Uu with QoS flow IDs. However, in an explicit configuration, the BS may configure QoS flow to DRB mapping. That is, the QoS flow to DRB mapping rule may be explicitly signaled by RRC.

A reflected QoS flow to DRB mapping indication (RDI) may be defined that indicates whether the QoS flow to DRB mapping rule should be updated. For example, the RDI may be defined as in table 1.

[ Table 1]

Bit	Description of the invention
		0	Without movement
1	Storing QoS flow to DRB mapping rules

As described above, in 5G NR, the separation of gNB-CU-CP and gNB-CU-UP has been discussed. Because the CU-UP hosts the SDAP protocol that supports the functionality of mapping between QoS flows and DRBs for both downlink and uplink, the CU-UP may be able to modify QoS flow to DRB mapping rules based on the current status of downlink and/or uplink traffic on, for example, F1-U and/or NG-U. On the other hand, while a CU-UP hosts an SDAP protocol that supports the functionality of mapping between QoS flows and DRBs for both downlink and uplink, a CU-UP may be able to request from a CU-CP to modify QoS flow-to-DRB mapping rules based on current conditions. This is because the CU-CP can generate QoS flow to DRB mapping rules and the CU-UP performs mapping between QoS flows and DRBs. However, currently no QoS flow to DRB remapping hosted by CU-UP or CU-CP is supported in the separation of CU-CP and CU-UP. Therefore, there is a need to suggest a QoS flow to DRB remapping procedure in the split scenario of gNB-CU-CP and gNB-CU-UP.

Further, as described above, there may be a reflection QoS flow to DRB mapping between QoS flow to DRB mappings. The reflection QoS flow to DRB mapping may be referred to as a reflection mapping. Unlike QoS flow to DRB remapping, there is no need (through CU-CP in the case where CU-UP provides QoS flow to DRB mapping rules) to provide a reflective QoS flow to DRB remapping for the UE. This is because the SDAP in the CU-UP sends downlink data with RQI set to 1 or RDI set to 1 to the UE through the remapped DRB. Upon receiving the data, the UE stores the QoS flow to DRB mapping as a QoS flow to DRB mapping rule for the uplink. Therefore, QoS flow to DRB remapping solutions hosted by CU-UP or CU-CP are necessary in view of the reflected QoS flow to DRB mapping.

Hereinafter, a method for modifying a QoS flow to DRB mapping rule when CU-CP and CU-UP are separated and an apparatus supporting the same will be described according to an embodiment of the present invention. In the specification, the QoS flow to DRB mapping rule may be referred to as a mapping rule.

Fig. 9 illustrates a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

Referring to fig. 9, in step S910, a CU may decide to modify QoS flow-to-DRB mapping rules for one or more DRBs or QoS flows established based on current conditions. For example, a CU may decide to modify the QoS flow to DRB mapping rules based on downlink traffic and/or uplink traffic on F1-U and/or NG-U. The CU may then modify the QoS flow-to-DRB mapping rules for one or more DRBs or QoS flows. For example, the QoS flow-to-DRB mapping rules for one or more DRBs or QoS flows may be modified by the CU-CP. Alternatively, the QoS flow to DRB mapping rules may be modified for one or more DRBs or QoS flows by CU-UP.

In step S920, the CU may determine whether the modified QoS flow to DRB mapping rule relates to a reflection mapping.

In step S930, if the CU determines that the modified QoS flow to DRB mapping rule is not related to the reflection mapping, the CU sends the modified QoS flow to DRB mapping rule to the UE. The modified QoS flow to DRB mapping rule may be sent to the UE via the DU. For example, the modified QoS flow to DRB mapping rule may be transmitted from the CU to the DU by being included in a DL RRC messaging message and may be transmitted from the DU to the UE by being included in an RRC reconfiguration message. On the other hand, if the CU determines that the modified QoS flow to DRB mapping rule is related to the reflection mapping, the CU does not send the modified QoS flow to DRB mapping rule to the UE.

According to embodiments of the present invention, a CU may decide to modify the QoS flow to DRB mapping rules for one or more DRBs or QoS flows established based on current conditions, such as current downlink and/or uplink traffic conditions. In addition, the CU may send the modified QoS flow to DRB mapping rule to the UE only if the modified QoS flow to DRB mapping rule is not related to the reflection mapping. Thus, the user experience may be improved and the RAN node may better process data packets for a particular UE.

Fig. 10a and 10b illustrate a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

The control plane part of the gNB-CU may be referred to as the CU-CP, and the user plane part of the gNB-CU may be referred to as the CU-UP. The gNB-DU may be referred to as a DU.

Referring to fig. 10a, in step S1000, the UE may be in an RRC _ CONNECTED mode.

In step S1001, the CU-UP may decide to modify the QoS flow to DRB mapping rules for one or more DRBs or QoS flows established based on the current conditions. For example, the CU-UP may decide to modify the QoS flow to DRB mapping rules based on downlink traffic and/or uplink traffic on F1-U and/or NG-U.

In step S1002, the CU-UP may transmit a bearer modification request message, an existing message, or a new message to the CU-CP if the mapping rule needs to be modified for the setting of the at least one DRB. Alternatively, if L1/L2 reconfiguration for an established DRB is required to modify the mapping rules, the CU-UP can send a bearer modification required message, an existing message, or a new message to the CU-CP. Alternatively, if L1/L2 reconfiguration for an established DRB and modification of mapping rules for the settings of at least one DRB are required, the CU-UP can send a bearer modification request message, an existing message, or a new message to the CU-CP. The bearer modification requirement message may include a DRB list to be set and/or a DRB list to be modified with QoS flow indicators and/or QoS flow level QoS parameters. The DRB list to be set may include at least one identifier of the set DRB. The DRB list to be modified may include at least one identifier of the DRB to be modified. The QoS flow indicator may identify a QoS flow within a PDU session. The QoS flow level QoS parameters may define the QoS to be applied to the QoS flow or DRB. The QoS flow indicator may be as defined in table 2. The QoS flow level QoS parameters may be defined as in table 3.

[ Table 2]

IE/group name	Presenting	Range of	IE type and reference	Semantic description
					QoS flow indicator	M		Integer (0..63)

[ Table 3]

Upon receiving the bearer modification request message from the CU-UP, the CU-CP may transmit a UE context modification request message, an existing message, or a new message to the DU to request setting of one or more DRBs and/or L1/L2 reconfiguration based on the received DRB list to be set and/or the DRB list to be modified in step S1003.

In step S1004, upon receiving the UE context modification request message from the CU-CP, the DU may establish the requested DRB. The DU may allocate required resources over the radio interface for the DRB requested to be established and/or perform L1/L2 reconfiguration for the requested DRB. The DU may then respond to the CU-CP with a UE context modification response message, an existing message, or a new message. A UE context modification response message may be transmitted to the CU-CP to indicate whether the requested DRB is established or whether L1/L2 reconfiguration for the requested DRB is performed.

In step S1005, upon receiving the UE context modification response message from the DU, the CU-CP may transmit a bearer modification confirm message, an existing message, or a new message to the CU-UP. The bearer modification confirm message may include a DRB setup list and/or a DRB modification list with DRB ID and/or DRB related QoS parameters.

In step S1006, when deciding to modify the QoS flow to DRB mapping rule, the CU-UP may send a bearer modification request message, an existing message, or a new message to the CU-CP. The bearer modification requirement message may include a modified QoS flow to DRB mapping rule per QoS flow or a modified QoS flow to DRB mapping rule per DRB level. The bearer modification request message may include a reflection map indication informing the CU-CP whether the modified mapping rule to be provided by the CU-UP relates to a reflection map. The reflection mapping indication may be communicated at the QoS flow or DRB level.

In step S1007, upon receiving the bearer modification request message from the CU-UP, the CU-CP may store the modified QoS flow-to-DRB mapping rule received from the CU-UP. Depending on the received reflection mapping indication for the QoS flow or the DRB, the CU-CP may prepare to provide the modified mapping rule to the UE if the modified mapping rule is not related to the reflection mapping. The modified mapping rule may be provided to the UE through an RRC message. On the other hand, if the modified mapping rule relates to a reflection mapping, the CU-CP does not provide the modified mapping rule to the UE.

In step S1008, the CU-CP may respond to the CU-UP with a bearer modification confirm message, an existing message, or a new message. Alternatively, a bearer modification confirm message may be sent to the CU-UP after step S1012.

Referring to fig. 10b, in step S1009, if a modified mapping rule unrelated to the reflection mapping has been received from the CU-UP in step S1006, the CU-CP may send a DL RRC messaging message to the DU. The DL RRC messaging message may include an RRC reconfiguration message with a modified QoS flow to DRB mapping rule independent of the reflection mapping.

Upon receiving the DL RRC messaging message from the CU-CP, the DU may transmit an RRC reconfiguration message with a modified QoS flow to DRB mapping rule regardless of the reflection mapping to the UE in step S1010.

In step S1011, the UE may transmit an RRC reconfiguration complete message to the DU.

In step S1012, when the DU has received an RRC reconfiguration complete message from the radio interface to be forwarded to the CU-CP, the DU may send an UL RRC messaging message including RRC reconfiguration complete information to the CU-CP.

According to embodiments of the present invention, when a CU-UP decides to modify a QoS flow to DRB mapping rule based on current conditions of downlink and/or uplink traffic on, for example, F1-U and/or NG-U, the CU-UP may inform the CU-CP of the modified QoS flow to DRB mapping rule. In addition, the CU-UP can inform the CU-CP whether the modified QoS flow to DRB mapping rule is related to reflection mapping. If setup or modification for DRBs is necessary to modify the QoS flow to DRB mapping rules, the CU-UP can request from the CU-CP to do setup and/or L/L2 reconfiguration of one or more DRBs. Thus, according to embodiments of the present invention, a CU-UP may modify a QoS flow to DRB mapping rule to use radio resources appropriate for the current downlink and/or uplink traffic conditions. Furthermore, the user experience may be improved and the RAN node may better process data packets for a particular UE.

Fig. 11 illustrates a procedure for modifying a QoS flow to DRB mapping rule in a CP-UP split case according to an embodiment of the present invention.

Referring to fig. 11, in step S1100, the UE may be in an RRC _ CONNECTED mode.

In step S1101, the CU-UP may decide to request from the CU-CP to modify the QoS flow-to-DRB mapping rules for one or more DRBs or QoS flows established according to the current conditions of downlink and/or uplink traffic on, for example, F1-U and/or NG-U.

In step S1102, the CU-UP may send a bearer modification request message, an existing message, or a new message to the CU-CP. The bearer modification requirement message may include a remapping indication and/or QoS flows that do not meet the QoS requirements. The QoS flow may be an indication or information requesting a remapping of QoS flows to DRBs.

Upon receiving the bearer modification request message from the CU-UP, the CU-CP may perform modifying the QoS flow to DRB mapping rule based on the received QoS flow in step S1103. The CU-CP may then send a UE context modification request message, an existing message, or a new message to the DU. A UE context modification request message may be sent to request setup of one or more DRBs and/or L1/L2 reconfiguration based on the modified QoS flow to DRB mapping rule.

Upon receiving the UE context modification request message from the CU-CP, the DU may establish the requested DRB for the UE and allocate required resources for the requested DRB over the radio interface and/or perform L1/L2 reconfiguration for the requested DRB in step S1104. The DU may then respond to the CU-CP with a UE context modification response message, an existing message, or a new message. A UE context modification response message may be transmitted to the CU-CP to indicate whether the requested DRB is established or whether L1/L2 reconfiguration for the requested DRB is performed.

In step S1105, upon receiving the UE context modification response message from the DU, the CU-CP may transmit a bearer modification confirm message, an existing message, or a new message to the CU-UP. The bearer modification confirm message may include a modified QoS flow to DRB mapping rule and/or a corresponding DRB configuration. Alternatively, after the CU-CP receives the bearer modification request message in step S1102, a bearer modification confirm message may be transmitted to the CU-UP. That is, before transmitting the UE context modification request message in step S1103, the bearer modification confirm message may be transmitted to the CU-UP after the CU-CP modifies the QoS flow to DRB mapping rule.

Upon receiving the bearer modification confirm message from the CU-CP, the CU-UP may store the modified QoS flow to DRB mapping rule in step S1106. The CU-UP may then perform QoS flow to DRB mapping based on the received QoS flow to DRB mapping rules modified by the CU-CP.

In step S1107, if the modified mapping rule is not related to the reflection mapping, the CU-CP may send a DL RRC messaging message to the DU. The DL RRC messaging message may include an RRC reconfiguration message with a modified QoS flow to DRB mapping rule independent of the reflection mapping.

In step S1108, upon receiving the DL RRC messaging message from the CU-CP, the DU may send an RRC reconfiguration message to the UE with a modified QoS flow to DRB mapping rule that is independent of the reflection mapping.

In step S1109, the UE may transmit an RRC reconfiguration complete message to the DU.

In step S1110, when the DU has received an RRC reconfiguration complete message from the radio interface to be forwarded to the CU-CP, the DU may send an UL RRC messaging message including the RRC reconfiguration complete message to the CU-CP.

According to embodiments of the present invention, the CU-CP may modify the QoS flow to DRB mapping rules based on the QoS flows indicated from CU-UP that do not meet the QoS requirements. Thus, according to embodiments of the present invention, the user experience may be improved and the RAN node may better process data packets for a particular UE.

Fig. 12 illustrates a method of modifying a QoS flow to DRB mapping rule by a Central Unit (CU) of a Base Station (BS) according to an embodiment of the present invention. The present invention described above for the BS side can be applied to this embodiment.

Referring to fig. 12, in step S1210, a CU may modify a QoS flow to DRB mapping rule.

In step S1220, the CU may determine whether the modified QoS flow to DRB mapping rule relates to a reflection mapping.

In step S1230, when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping, the CU may transmit the modified QoS flow to DRB mapping rule to the User Equipment (UE). Alternatively, when it is determined that the modified QoS flow to DRB mapping rule relates to a reflection mapping, the modified QoS flow to DRB mapping rule is not transmitted.

The CU may include a CU-CP and at least one CU-UP. The CU-CP may be a logical node hosting the control plane portion of the RRC and PDCP protocols of the CU, and the at least one CU-UP may be a logical node hosting the user plane portion of the SDAP protocol and PDCP protocols of the CU.

Information for modifying the QoS flow to DRB mapping rule may be sent from at least one CU-UP to the CU-CP. The QoS flow to DRB mapping rule may be modified by the CU-CP based on this information. The modified QoS flow to DRB mapping rule may be sent from the CU-CP to at least one CU-UP. The information may include at least one QoS flow that does not meet the QoS requirements. The QoS flow to DRB mapping rule may be modified by the CU-CP based on the at least one QoS flow.

The modified QoS flow to DRB mapping rule may be transmitted to the UE via a Distribution Unit (DU) of the BS. The modified QoS flow to DRB mapping rule may be sent to the DU by being included in a DL RRC messaging message. The modified QoS flow to DRB mapping rule may be transmitted to the UE by being included in an RRC reconfiguration message. The CUs may be logical nodes hosting the RRC, SDAP, and PDCP protocols of the BS, and the DUs may be logical nodes hosting the RLC, MAC, and PHY layers of the BS.

Fig. 13 shows a BS for implementing an embodiment of the present invention. The present invention described above for the BS side can be applied to this embodiment.

BS 1300 includes a processor 1310, a memory 1320, and a transceiver 1330. The processor 1310 may be configured to implement the proposed functions, processes, and/or methods described in this specification. Layers of a radio interface protocol may be implemented in the processor 1310.

In particular, the processor 1310 may modify the QoS flow to DRB mapping rule.

Further, the processor 1310 may determine whether the modified QoS flow to DRB mapping rule relates to a reflection mapping.

Further, when it is determined that the modified QoS flow to DRB mapping rule is not related to the reflection mapping, the processor 1310 may control the transceiver 1330 to transmit the modified QoS flow to DRB mapping rule to the transceiver 1530. Alternatively, when it is determined that the modified QoS flow to DRB mapping rule relates to a reflection mapping, then the modified QoS flow to DRB mapping rule is not sent.

The CU may include a CU-CP and at least one CU-UP. The CU-CP may be a logical node hosting the control plane portion of the RRC and PDCP protocols of the CU, and the at least one CU-UP may be a logical node hosting the user plane portion of the SDAP protocol and PDCP protocols of the CU.

Information for modifying the QoS flow to DRB mapping rule may be sent from at least one CU-UP to the CU-CP. The QoS flow to DRB mapping rule may be modified by the CU-CP based on this information. The modified QoS flow to DRB mapping rule may be sent from the CU-CP to at least one CU-UP. The information may include at least one QoS flow that does not meet the QoS requirements. The QoS flow to DRB mapping rule may be modified by the CU-CP based on the at least one QoS flow.

The modified QoS flow to DRB mapping rule may be transmitted to the UE via a Distribution Unit (DU) of the BS. The modified QoS flow to DRB mapping rule may be sent to the DU by being included in a DL RRC messaging message. The modified QoS flow to DRB mapping rule may be transmitted to the UE by being included in an RRC reconfiguration message. The CUs may be logical nodes hosting the RRC, SDAP, and PDCP protocols of the BS, and the DUs may be logical nodes hosting the RLC, MAC, and PHY layers of the BS.

The memory 1320 can be operatively coupled to the processor 1310 and store various information for operating the processor 1310. The transceiver 1330 can be operatively coupled with the processor 1310 and transmit and/or receive radio signals.

Fig. 14 illustrates a method for receiving a modified QoS flow to DRB mapping rule by a UE according to an embodiment of the present invention. The invention described above for the UE side can be applied to this embodiment.

Referring to fig. 14, in step S1410, the UE may receive a modified QoS flow to DRB mapping rule from a Central Unit (CU) of a Base Station (BS). The modified QoS flow to DRB mapping rule may be independent of the reflection mapping.

Fig. 15 shows a UE implementing an embodiment of the present invention. The invention described above for the UE side can be applied to this embodiment.

The UE 1500 includes a processor 1510, memory 1520, and a transceiver 1530. The processor 1510 may be configured to implement the proposed functions, procedures, and/or methods described in this specification. Layers of the radio interface protocol may be implemented in the processor 1510.

In particular, the processor 1510 may control the transceiver 1530 to receive the modified QoS flow to DRB mapping rule from the transceiver 1330. The modified QoS flow to DRB mapping rule may be independent of the reflection mapping.

The memory 1520 is capable of being operatively coupled to the processor 1510 and storing various information for operating the processor 1510. The transceiver 1530 is capable of operatively coupling with the processor 1510 and transmitting and/or receiving radio signals.

The processors 1310, 1510 may include Application Specific Integrated Circuits (ASICs), separate chipsets, logic circuits, and/or data processing units. The memory 1320, 1520 may include Read Only Memory (ROM), Random Access Memory (RAM), flash memory, memory cards, storage media, and/or other equivalent storage devices. The transceivers 1330, 1530 may include baseband circuitry for processing wireless signals. When the embodiments are implemented in software, the aforementioned methods may be implemented with modules (i.e., processes, functions, and so on) for performing the aforementioned functions. The modules may be stored in memory and executed by the processors 1310, 1510. The memory 1320, 1520 may be located internal or external to the processor 1310, 1510 and may be coupled to the processor 1310, 1510 using a variety of well-known means.

In view of the exemplary systems described herein, methodologies that may be implemented in accordance with the disclosed subject matter have been described with reference to various flow diagrams. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of steps or blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the steps or blocks, as some steps may occur in different orders or concurrently with other steps from that shown and described herein. Further, those of skill in the art will understand that the steps shown in the flowcharts are not exclusive and may include other steps or one or more steps in the example flowcharts may be deleted without affecting the scope of the present disclosure.