KR102296119B1 - Secondary path configuration - Google Patents

Abstract

One or more devices, systems, and/or methods are provided that facilitate the use of a radio bearer using a secondary path. For example, a configuration message may be used to determine whether a secondary path exists. The secondary path may be configured based on the configuration message.

Description

Secondary path configuration

<Cross reference to related applications>
This application claims priority under 35 USC §120 as an extension of PCT Patent Application No. PCT/CN2017/088729, filed on June 16, 2017, which PCT application is incorporated herein by reference in its entirety.
<background>
Communication between nodes (eg, communication devices, network entities, etc.), such as between user equipment (UE) and a base station (BS), between two UEs and/or between two BSs. A link may be facilitated using one or more radio bearers. For example, the BS may generate one or more signals and/or transmit one or more signals to the UE using a radio bearer. A UE may receive and/or process one or more signals using a radio bearer and process one or more signals received from a BS.

In accordance with the present disclosure, one or more devices and/or methods are provided for facilitating use of a radio bearer using a secondary path. In one example, a configuration message may be received from a network entity. At least one secondary path may be determined based on the configuration message. The at least one secondary path may be configured based on the configuration message. A response message may be sent to the network entity.

In one example, a request may be transmitted to the network entity to establish at least one secondary path in association with the radio bearer. A response to the request may be received from a network entity. The response may include radio resource information and address information. A configuration message may be generated based on the radio resource information and the address information. The configuration message may include at least one secondary path identity. The configuration message may be transmitted to the communication device.

In one example, radio resource information and address information may be determined based on a request to establish at least one secondary path. A configuration message may be generated based on the radio resource information and the address information. The configuration message may include at least one secondary path identity. The configuration message may be transmitted to the communication device.

Although the techniques presented herein may be practiced in alternative forms, the specific embodiments illustrated in the drawings are merely a few examples that supplement the description provided herein. These embodiments should not be construed in a limiting manner as limiting the claims appended hereto.
1A is a flow diagram illustrating an exemplary method of facilitating the use of a radio bearer using a secondary path.
1B is a flow diagram illustrating an exemplary method of facilitating the use of a radio bearer using a secondary path.
1C is a flow diagram illustrating an exemplary method of facilitating the use of a radio bearer using a secondary path.
2A is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
2B is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
3A is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
3B is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
4A is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
4B is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
5 is a component block diagram illustrating an example system that facilitates the use of a radio bearer using a secondary path.
6A is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
6B is a component block diagram illustrating an exemplary system that facilitates the use of a radio bearer using a secondary path.
7 is an illustrative diagram of a scenario involving an example configuration of a base station (BS) that may utilize and/or implement at least a portion of the techniques presented herein.
8 is an illustrative diagram of a scenario involving an example configuration of a user equipment (UE) that may use and/or implement at least a portion of the techniques presented herein.
9 is an illustrative diagram of a scenario featuring an example non-transitory computer readable medium in accordance with one or more of the countermeasures referred to herein.

BRIEF DESCRIPTION OF THE DRAWINGS The subject matter of the present invention will now be explained more fully below with reference to the accompanying drawings, which form a part of this application and which show by way of illustration specific exemplary embodiments. This description is not intended as an extensive or detailed discussion of known concepts. Details commonly known to those of ordinary skill in the art may be omitted or may be treated in summary form.

The following inventive subject matter may be embodied in a variety of different forms, such as methods, devices, components, and/or systems. Accordingly, the subject matter of this invention should not be construed as limited to any exemplary embodiments mentioned herein. Rather, the exemplary embodiments are provided by way of example only. Such embodiments may take the form of, for example, hardware, software, firmware, or any combination thereof.

One or more computing devices and/or techniques are provided that facilitate the use of a radio bearer using a secondary path. For example, a user equipment (UE) may be connected to a network (eg, wireless and/or wired) communication via a base station (BS) of the network. The BS transmits information to the UE via signals, so that the UE may receive the signals. Transmission of information via signals may involve a radio bearer (eg, anchored to a BS) that processes the information. In order to be able to use the information in the received signal, the UE may process the signal using a radio bearer. Some methods of processing information using radio bearers may use an increasing (eg, greater than a threshold) number of types of radio bearers, which introduces significant complexity in the maintenance of the protocol on the UE (eg, and thus providing more costly, unreliable and/or associated communication between the BS and the UE at lower data rates than possible and/or desirable). Moreover, complexity may arise in situations where a change in radio bearer type is necessary and/or desirable. Accordingly, in accordance with one or more of the techniques presented herein, processing information using radio bearers relieves complexity, improves efficiency, and/or a BS (eg, and/or one or more other BSs) and a UE (eg, , and/or one or more other UEs) in a manner that provides the UE's ability to provide optimal communication (eg, improved quality, reduced processing, memory and/or bandwidth usage, etc.) between the radio bearer and one or more entities of the UE) may be facilitated by introducing a secondary path.

An exemplary method 100A for facilitating the use of a radio bearer using a secondary path is shown in FIG. 1A . A radio bearer may be associated with (e.g., used by) a service being provided to a communication device (e.g., UE), and may be used to provide configuration to a layer (e.g., layer-2, physical, etc.); and/or may be used to pass user data and/or control data from that layer to one or more other (eg, upper) layers. Thus, the radio bearer may operate as a service access point between that layer and one or more other (eg, higher) layers. Accordingly, at 105A, the communication device (eg, UE) may receive a configuration message from a network entity (eg, a base station of the network). The configuration message may include a secondary path identity, such as a secondary logical channel identity. The configuration message may alternatively and/or additionally include a primary path identity, such as a primary logical channel identity.

At 110A, a secondary path (eg, secondary logical channel) may be determined based on the configuration message. For example, the secondary path may be determined based on the secondary path identity. Alternatively and/or additionally, a primary path (eg, primary logical channel) may be determined based on the configuration message. For example, the primary path may be determined based on the primary path identity.

In some examples, a determination may be made as to whether the first portion of the configuration message or the second portion of the configuration message includes secondary path information. The first portion may include information generated by and/or received from a network entity and/or may be used to configure one or more resources in a first (eg, master) cell group. The second portion may include information generated by and/or received by the second network entity and/or may be used to configure one or more resources in the second (eg, secondary) cell group. have. In response to the first portion comprising secondary path information, the first portion (eg, not the second portion) may be analyzed (eg, optionally) to identify a secondary path identity corresponding to the secondary path.

At 115A, the secondary path may be configured based on the configuration message.

In some examples, a determination may be made as to whether a secondary path exists (eg, and/or is in active use) at the communication device (eg, UE). For example, the determining may include determining whether a secondary path exists in the group of cells. The cell group may be determined and/or identified by the first portion of the configuration message determined to include secondary path information. A determination as to whether a secondary path exists may be made based on one or more parameters included in the configuration message and/or a secondary path in one or more portions of the communication device and/or one or more indications associated with the secondary path. It can also be done by searching people.

Alternatively and/or additionally, the determination is determined to be between a first component of the communication device and/or network entity and a second component of the communication device and/or network entity (eg, and/or the first component may be based on the number of paths (determined to be used to connect to the second component and/or transmit data between the components). For example, if it is determined that less than two (eg, zero, one, etc.) paths are between a first component of the communication device and/or network entity and a second component of the communication device and/or network entity, then the secondary path is A determination may be made that is not present in the communication device. In some examples, if it is determined that two or more paths are between a first component of the communication device and/or network entity and a second component of the communication device and/or network entity, then a determination may be made that a secondary path exists at the communication device. have.

In response to determining that a secondary path exists (eg, and/or is in active use) at the communication device, the secondary path may be modified based on the configuration message. For example, the mapping between the secondary path and the radio bearer may be modified. For example, the secondary path may be mapped from a radio bearer mapped to a radio bearer in a first configuration (eg, via one or more first components) to a radio bearer in a second configuration (eg, via one or more second components). may be changed to exist. In some examples, a radio bearer may be determined (eg, identified) based on a bearer identity included in the configuration message. In response to determining that the configuration message includes an instruction to change a type of a radio bearer from a first bearer type to a second bearer type, one or more components of the communication device and/or network entity are configured to: It may be modified from the configuration to the second configuration corresponding to the second bearer type.

In some examples, modifying the secondary path comprises (eg, according to one or more parameters in the configuration message) one or more radio link control (RLC) associated with the secondary path from the first RLC configuration to the second RLC configuration. reconfiguring the entities, reconfiguring (eg, according to one or more parameters in the configuration message) the operating mode of the secondary path from the first operating mode to the second operating mode and/or (eg, one in the configuration message); and reconfiguring a packet data convergence protocol (PDCP) entity from the first PDCP configuration to the second PDCP configuration (according to the above parameters).

In some examples, in response to determining that the configuration message includes an instruction to release the secondary path and/or an instruction to delete one or more radio bearers linked to the secondary path, a mapping between the secondary path and a radio bearer, one or more RLC entities , secondary path and/or radio bearer may be deleted from the communication device and/or network entity (eg, according to one or more parameters in the configuration message).

In some examples, in response to determining that the configuration message includes an instruction to release the at least one secondary path and/or does not correspond to a change to the first bearer type, a PDCP status report is triggered and/or sent to the network entity could be Based on the configuration message that does not include a command to change (eg, explicit) the first bearer type and/or one or more actions cause (eg, indirectly and/or implicitly) the change to the first bearer type. Based on the configuration message that does not cause it, it may be determined that the configuration message does not correspond to a change to the first bearer type.

In some examples, in response to determining that the configuration message includes an instruction to release the at least one secondary path and/or does not correspond to re-establishment of the PDCP entity, a PDCP status report may be triggered and/or transmitted to the network entity have. based on a configuration message that does not include a (eg, explicit) instruction to re-establish the PDCP entity and/or such that one or more actions do not result in (eg, indirectly and/or implicitly) re-establish the PDCP entity. Based on the configuration message, it may be determined that the configuration message does not correspond to the re-establishment of the PDCP entity.

In response to determining that the secondary path does not exist in the communication device, the secondary path may be established at the communication device based on the configuration message and/or connect the communication device to a network entity (eg, it is a radio bearer and/or a packet of the radio bearer). does not include a data convergence protocol configuration (PDCP) and is therefore anchored by this radio bearer and/or a second network entity (eg it does not contain a radio bearer and/or PDCP of the radio bearer, and therefore this radio not anchored by a bearer). For example, the secondary path may be created at the communication device and/or radio bearer, and the mapping between the RLC entity and/or the secondary path and the radio bearer may be created at the network entity. A radio bearer may be determined (eg, identified) and/or created based on a bearer identity included in the configuration message. Alternatively and/or additionally, a radio bearer may be determined and/or created based on a bearer identity included in a different (eg, previous) configuration message.

The secondary path may be generated based on at least a portion of a configuration message, such as a secondary path identity and/or an RLC configuration corresponding to an RLC entity (eg, of a network entity). The secondary path is connected to and/or may be enabled through the RLC entity.

The secondary path may be modified to have and/or generated to have a mode determined based on the secondary path mode identity included in the configuration message. For example, in response to determining that the secondary path mode identity includes the first identity (eg, indicative of a replication mode), the mode of the secondary path may be determined (eg, and set to) to be a replication mode. In another example, in response to determining that the secondary path mode identity includes the second identity (eg, indicative of a split mode), the mode of the secondary path may be determined (eg, and set to) to be a split mode.

At 120A, a response indicating the status of the configuration message and/or one or more actions taken after receipt of the configuration message may be sent from the communication device to the network entity and/or the second network entity.

At least some of the modules, diagrams, and/or techniques of FIGS. 2A, 2B, 3A, 3B, 4A, 4B (eg, and/or other figures) are incorporated into the performance of method 100A and It may be understood that/or may be implemented.

An exemplary method 100B for facilitating the use of a radio bearer using a secondary path is shown in FIG. 1B . Network entities (eg, within a network) may include one or more base stations, such as an evolved NodeB (eNB), MeNB, SgNB, serving gateway (S-GW) and/or mobility management entity (MME). ) may be included. Accordingly, at 105B, a second network entity (eg, in the network) may transmit a request to the network entity (eg, in the network) to establish (eg, and/or modify) a secondary path for the radio bearer. The request may include an indication of the communication device (eg, UE) that the secondary path will be established (eg, and/or modified).

At 110B, a response to the request is received from a network entity (eg, by a second network entity). The response may include one or more parameters (eg, associated with the communication device), such as radio resource information and/or address information. The address information may include an X2 downlink (DL) transport network layer (TNL) address.

At 115B, a configuration message may be generated based on radio resource information and/or address information. The configuration message may include a secondary path identity, such as a secondary logical channel identity. The configuration message may alternatively and/or additionally include a primary path identity, such as a primary logical channel identity.

At 120B, a configuration message may be transmitted to a communication device (eg, UE).

In some examples, a configuration status message may be received (eg, by a second network entity) from a communication device (eg, after and/or in response to transmission of the configuration message). The status of the secondary path (eg, on the communication device) may be determined based on the configuration status message. For example, the status may indicate full success, partial success, and/or failure of the communication device in establishing the secondary path.

In response to determining that the status corresponds to a first status (eg, complete success), facilitate use of and/or interaction with the communication device based on a first action (eg, the existence of a secondary path) ) may be performed. In response to determining that the status corresponds to a second status (eg, partial success), a second action (eg, use and/or interaction with the communication device based on the presence of a change in the secondary path) facilitating) may be performed. In response to determining that the status corresponds to a third status (eg, failed), facilitating a third action (eg, facilitating use and/or interaction with the communication device based on the absence of a secondary path) ) may be performed.

It may be understood that at least some of the modules, diagrams, and/or techniques of FIG. 5 (eg, and/or other figures) may be incorporated and/or implemented in performance of method 100B.

An exemplary method 100C for facilitating the use of a radio bearer using a secondary path is shown in FIG. 1C . Accordingly, at 105C, radio resource information and/or address information may be determined based on the request to establish a secondary path associated with the radio bearer. The request may include an indication of the communication device (eg, UE) that the secondary path will be established (eg, and/or modified).

At 110C, a configuration message may be generated based on radio resource information and/or address information. The configuration message may include a secondary path identity, such as a secondary logical channel identity. The configuration message may alternatively and/or additionally include a primary path identity, such as a primary logical channel identity. The request may be generated by and/or received by the network entity from the second network entity that generates the configuration message.

At 115C , a configuration message may be transmitted from a network entity to a communication device (eg, UE).

It may be understood that at least some of the modules, diagrams, and/or techniques of FIG. 5 (eg, and/or other figures) may be incorporated and/or implemented in performance of method 100C.

2A shows an example of a system 200A that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, a UE) and/or a network entity 210 (eg, one or more base stations and/or a network) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity. 235 (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 determines a secondary path (eg, to the network entity 210 and/or to another network entity that does not have a radio bearer) (eg, one or more dimensions of the secondary path and/or or compute aspects) may use the secondary logical channel identity of configuration message 215 . In some examples, the communication device 205 may use the primary logical channel identity of the configuration message 215 to determine a primary path (eg, calculate one or more dimensions and/or aspects of the primary path).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the network entity 210). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 . Alternatively and/or additionally, the determination is made between a first component of the network entity 210 , such as a radio bearer 220 , and a second component of the network entity 210 , such as a MAC entity 235 . It may be based on the number of paths determined to be

The communication device 205 may determine that no secondary path exists in the communication device 205 (eg, so the secondary path does not connect the communication device 205 to the network entity 210 ). In response, secondary path 243 may be established (eg, created) at communication device 205 such that the secondary path connects communication device 205 to network entity 210 . A secondary RLC entity 240 may be established at the network entity 210 in association with the secondary path 243 (eg, to facilitate such secondary path). For example, secondary RLC entity 240 may connect PDCP 225 and/or radio bearer 220 to MAC entity 235 (eg, in addition to existing primary RLC entity 230 ).

In some examples, in response to determining that the secondary path does not exist in the communication device 205 , the radio bearer 220 , the PDCP 225 , the primary RLC entity 230 , the primary path 242 , the secondary path 243 . and mapping between radio bearers 220 , MAC entity 235 and/or network entity 210 and/or one or more other components of communication device 205 to (eg, newly established) secondary path 243 . may be created and/or modified accordingly.

2B shows an example of a system 200B that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, a UE) and/or a network entity 210 (eg, one or more base stations and/or a network) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity 235 . may include (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 uses the secondary logical channel identity in the configuration message 215 to determine a secondary path to the second network entity 211 (eg, not having a radio bearer) (eg, one or more dimensions of such secondary path). and/or aspects). In some examples, the communication device 205 uses the primary logical channel identity of the configuration message 215 to determine a primary path (eg, to the network entity 210 ) (eg, one or more dimensions of the primary path and/or or calculate aspects).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the second network entity 211). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 and/or the second network entity 211 . Alternatively and/or additionally, the determination may be made between the first component of the network entity 210 and/or the second network entity 211 , such as the radio bearer 220 , the network entity 210 and/or the second network entity 211 . It may be based on the number of paths determined to be between the second component of the two network entities 211 , such as the MAC entity 235 .

The communication device 205 may determine that a secondary path does not exist in the communication device 205 (eg, so the secondary path does not connect the communication device 205 to the second network entity 211 ). In response, secondary path 243 may be established (eg, created) at communication device 205 such that the secondary path connects communication device 205 to second network entity 211 . A secondary RLC entity 240 may be established in the second network entity 211 in association with the secondary path 243 (eg, to facilitate such secondary path). For example, the secondary RLC entity 240 transmits the PDCP 225 (eg, in the network entity 210 ) and/or the radio bearer 220 to the second (eg, in the second network entity 211 ). MAC entity 236 may be connected.

In some examples, in response to determining that the secondary path does not exist in the communication device 205 , the radio bearer 220 , the PDCP 225 , the primary RLC entity 230 , the primary path 242 , the secondary path 243 . and a mapping between the radio bearers 220 , one or more of the MAC entity 235 , the second MAC entity 236 and/or the network entity 210 , the second network entity 211 and/or the communication device 205 . Other components may be created and/or modified according to the (eg, newly established) secondary path 243 .

3A shows an example of a system 300A that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, UE) and/or a network entity 210 (eg, UE) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity 235 . may include (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 determines (eg, determines one or more dimensions and/or aspects of the secondary path (eg, to the network entity 210 , and/or to another network entity that does not have a radio bearer)). calculation) may use the secondary logical channel identity of the configuration message 215 . In some examples, the communication device 205 may use the primary logical channel identity of the configuration message 215 to determine a primary path (eg, calculate one or more dimensions and/or aspects of the primary path).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the network entity 210). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 . Alternatively and/or additionally, the determination is made between a first component of the network entity 210 , such as a radio bearer 220 , and a second component of the network entity 210 , such as a MAC entity 235 . It may be based on the number of paths determined to be

The communication device 205 may determine that a secondary path 243 exists in the communication device 205 (eg, so that the secondary path 243 connects the communication device 205 to the network entity 210 ). In response, the secondary path 243 at the communication device 205 may be modified based on the configuration message 215 . For example, secondary path 243 connecting PDCP 225 and/or radio bearer 220 to MAC entity 235 may be modified to create a modified secondary path 244 . The modified secondary path 244 may include one or more parameters different from those of the secondary path 243 . The one or more parameters may be based on the configuration message 215 . The modification of the secondary path 243 to create a modified secondary path 244 is performed to create a modified mapping between the modified secondary path 244 and the radio bearer 220 and the secondary path 243 and the radio bearer. It may include modifying the mapping between 220 . The secondary RLC entity 240 may be modified to generate a modified secondary RLC entity 245 in the network entity 210 in association with (eg, to facilitate such secondary paths) the modified secondary path 244 . . For example, the modified secondary RLC entity 245 may connect the PDCP 225 and/or radio bearer 220 to the MAC entity 235 (eg, in addition to the existing primary RLC entity 230 ). .

In some examples, in response to determining that the secondary path 243 exists at the communication device 205 , the radio bearer 220 , the PDCP 225 , the primary path 230 , the MAC entity 235 and/or the network entity. 210 and/or one or more other components of the communication device 205 may be added, deleted, and/or modified according to the modified secondary path 244 .

3B shows an example of a system 300B that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, UE) and/or a network entity 210 (eg, UE) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity 235 . may include (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 determines (eg, determines one or more dimensions and/or aspects of the secondary path (eg, to the network entity 210 , and/or to another network entity that does not have a radio bearer)). calculation) may use the secondary logical channel identity of the configuration message 215 . In some examples, the communication device 205 may use the primary logical channel identity of the configuration message 215 to determine a primary path (eg, calculate one or more dimensions and/or aspects of the primary path). In some examples, the communication device 205 may use the bearer identity of the configuration message 215 to determine a radio bearer (eg, calculate one or more dimensions and/or aspects of the radio bearer).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the network entity 210). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 . Alternatively and/or additionally, the determination is made between a first component of the network entity 210 , such as a radio bearer 220 , and a second component of the network entity 210 , such as a MAC entity 235 . It may be based on the number of paths determined to be

The communication device 205 may determine whether the determined radio bearer is connected to the communication device 205 and/or operates in the network entity 210 based on the bearer identity. The determination may be made based on one or more parameters included in the configuration message 215 and/or the radio bearer and/or radio in one or more parts of the communication device 205 and/or the network entity 210 . This may be done by retrieving one or more indicators associated with the bearer.

The communication device 205 may determine that a secondary path 243 exists in the communication device 205 (eg, so that the secondary path 243 connects the communication device 205 to the network entity 210 ). In response, the secondary path 243 at the communication device 205 may be modified based on the configuration message 215 . For example, secondary path 243 connecting PDCP 225 and/or radio bearer 220 to MAC entity 235 may be modified to create a modified secondary path 244 .

The communication device 205 may determine that the radio bearer 220 is connected to the communication device 205 and/or is operating in the network entity 210 . In response, the radio bearer 220 at the network entity 210 may be modified based on and in accordance with the configuration message 215 . For example, the radio bearer 220 (eg, of the first type) connected to the PDCP 225 , the primary RLC entity 230 , the secondary RLC entity 240 and/or the MAC entity 235 may (eg, It may be modified to create a modified radio bearer 250 (of a second type).

In response to determining that the configuration message 215 includes an instruction to change the type of the radio bearer 220 from the first bearer type to the second bearer type, one or more components of the communication device 205 are configured to conform to the first bearer type. It may be modified from a corresponding first configuration to a second configuration corresponding to the second bearer type.

The modified secondary path 244 may include one or more parameters that are different from the parameters of the secondary path 243 . The one or more parameters may be based on the configuration message 215 . The modified radio bearer 250 may include one or more parameters that are different from the parameters of the radio bearer 220 . The one or more parameters may be based on the configuration message 215 . The first configuration may include one or more parameters different from the parameters of the second configuration. The one or more parameters may be based on the configuration message 215 .

The modification of the secondary path 243 to generate the modified secondary path 244 is performed with the secondary path 243 and It may include modifying the mapping between radio bearers 220 . The secondary RLC entity 240 is a network entity in association with the modified secondary path 244 and/or the modified radio bearer 250 (eg, to facilitate such modified secondary path and/or the modified radio bearer). It may be modified to create a modified secondary RLC entity 245 at 210 . For example, the modified secondary RLC entity 245 may connect the PDCP 225 and/or the modified radio bearer 250 to the MAC entity 235 (eg, in addition to the existing primary RLC entity 230 ). may be

The radio bearer 220 may be a first type of radio bearer, while the modified radio bearer 250 may be a second type of radio bearer (eg, different from the first type of radio bearer). A radio bearer of the first type and/or the second type includes a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, an MCG split bearer, an SCG split bearer, an MCG replicated bearer, may include and/or be based on SCG replicated bearer, MCG anchored bearer and/or SCG anchored bearer(s).

In some examples, in response to determining that secondary path 243 and/or radio bearer 220 exists in communication device 205 , PDCP 225 , primary path 230 , MAC entity 235 and/or Network entity 210 and/or one or more other components of communication device 205 may be added, deleted, and/or modified according to modified secondary path 244 and/or modified radio bearer 250 .

4A shows an example of a system 400A that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, UE) and/or a network entity 210 (eg, UE) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity 235 . may include (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 determines (eg, determines one or more dimensions and/or aspects of the secondary path (eg, to the network entity 210 , and/or to another network entity that does not have a radio bearer)). calculation) may use the secondary logical channel identity of the configuration message 215 . In some examples, the communication device 205 may use the primary logical channel identity of the configuration message 215 to determine a primary path (eg, calculate one or more dimensions and/or aspects of the primary path).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the network entity 210). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 . Alternatively and/or additionally, the determination is made between a first component of the network entity 210 , such as a radio bearer 220 , and a second component of the network entity 210 , such as a MAC entity 235 . It may be based on the number of paths determined to be

The communication device 205 may determine that a secondary path 243 exists in the communication device 205 (eg, so that the secondary path 243 connects the communication device 205 to the network entity 210 ). In response, the secondary path 243 at the communication device 205 may be deleted based on the configuration message 215 . For example, the configuration message 215 may include an instruction to release the secondary path 243 and/or an instruction to delete one or more radio bearers linked to the secondary path 243 . The secondary path 243 connecting the communication device 205 to the network entity 210 may be removed from the communication device 205 and/or will stop connecting the communication device 205 to the network entity 210 . may be Alternatively and/or additionally, the secondary RLC entity 240 connecting the PDCP 225 and/or radio bearer 220 to the MAC entity 235 may be removed from the network entity 210 and/or Alternatively, the PDCP 225 and/or radio bearer 220 may stop connecting to the MAC entity 235 .

In some examples, in response to determining that secondary path 243 exists at communication device 205 , one or more of PDCP 225 , primary path 230 , MAC entity 235 , and/or network entity 210 . Other components may be added, deleted, and/or modified according to the secondary path 243 .

4B shows an example of a system 400B that facilitates the use of a radio bearer using a secondary path. A communication device 205 (eg, UE) and/or a network entity 210 (eg, UE) may communicate with each other. The network entity 210 may include one or more components and/or entities, such as a radio bearer 220 , a PDCP entity 225 , a primary RLC entity 230 , and/or a medium access control (MAC) entity 235 . may include (eg, one or more of them may be associated with a service). The communication device 205 may include a primary path 242 that may be associated with (eg, facilitated by) a primary RLC entity 230 (eg, and/or a network via such primary path). may be connected to entity 210).

The network entity 210 may transmit a configuration message 215 to the communication device 205 . The configuration message 215 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a radio bearer identity, one or more (eg, other) parameters, and/or one or more instructions. have.

The communication device 205 may receive and analyze the configuration message 215 to identify one or more identities, parameters, and/or commands. The communication device 205 determines (eg, determines one or more dimensions and/or aspects of the secondary path (eg, to the network entity 210 , and/or to another network entity that does not have a radio bearer)). calculation) may use the secondary logical channel identity of the configuration message 215 . In some examples, the communication device 205 may use the primary logical channel identity of the configuration message 215 to determine a primary path (eg, calculate one or more dimensions and/or aspects of the primary path). In some examples, the communication device 205 may use the bearer identity of the configuration message 215 to determine a radio bearer (eg, calculate one or more dimensions and/or aspects of the radio bearer).

The communication device 205 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, and is operating in) the communication device 205 (eg, the secondary path is 205) to the network entity 210). The determination may be made based on one or more parameters included in the configuration message 215 and/or the secondary path in one or more portions of the communication device 205 and/or one or more indicators associated with the secondary path. This can also be done by searching. Alternatively and/or additionally, the determination may be based on the number of paths determined to be between the communication device 205 and the network entity 210 . Alternatively and/or additionally, the determination is made between a first component of the network entity 210 , such as a radio bearer 220 , and a second component of the network entity 210 , such as a MAC entity 235 . It may be based on the number of paths determined to be

The communication device 205 may determine whether the determined radio bearer is connected to the communication device 205 and/or operates in the network entity 210 based on the bearer identity. The determination may be made based on one or more parameters included in the configuration message 215 and/or the radio bearer and/or radio in one or more parts of the communication device 205 and/or the network entity 210 . This may be done by retrieving one or more indicators associated with the bearer.

The communication device 205 may determine that a secondary path 243 exists in the communication device 205 (eg, so that the secondary path 243 connects the communication device 205 to the network entity 210 ). In response, the secondary path 243 at the communication device 205 may be deleted based on the configuration message 215 . For example, the configuration message 215 may include an instruction to release the secondary path 243 and/or an instruction to delete one or more radio bearers linked to the secondary path 243 . The secondary path 243 connecting the communication device 205 to the network entity 210 may be removed from the communication device 205 and/or will stop connecting the communication device 205 to the network entity 210 . may be Alternatively and/or additionally, the secondary RLC entity 240 connecting the PDCP 225 and/or radio bearer 220 to the MAC entity 235 may be removed from the network entity 210 and/or Alternatively, the PDCP 225 and/or radio bearer 220 may stop connecting to the MAC entity 235 .

The communication device 205 may determine that the radio bearer 220 is connected to the communication device 205 and/or is operating in the network entity 210 . In response, the radio bearer 220 at the network entity 210 may be deleted based on and/or in conjunction with the configuration message 215 .

In response to determining that the configuration message 215 includes an instruction to delete the radio bearer 220 , one or more components of the communication device 205 may be deleted from the first configuration corresponding to the radio bearer 220 , and It may be modified to a second configuration corresponding to the second bearer type and/or to no radio bearer.

In some examples, in response to determining that secondary path 243 and/or radio bearer 220 exists in communication device 205 , PDCP 225 , primary path 230 , MAC entity 235 and/or Network entity 210 and/or one or more other components of communication device 205 may be added, deleted, and/or modified in accordance with deletion of radio bearer 220 and/or secondary path 243 .

5 shows an example of a system 500 that facilitates the use of a radio bearer using a secondary path. A network entity 505 (eg, a first base station in the network) (eg, SgNB), a second network entity 510 (eg, a second base station in the network) (eg, MeNB) and/or a communication device 515 . ) (eg, UEs) may communicate with each other.

The second network entity 510 may transmit a request message 520 to the network entity 505 to establish (eg, and/or modify) a secondary path and/or radio bearer. The request message 520 is an indication of the communication device 515 that a secondary path and/or radio bearer will be established (eg, and/or modified), information about the radio bearer, and corresponding (eg, data forwarding) address information and/or capability adjustment information. The request message 520 (eg, and/or one or more other messages sent from the second network entity 510 to the network entity 505 ) may include one or more (eg, E-UTRAN) radio access bearers (radio access). X2 downlink (DL) transport network layer (TNL) addresses for bearers, RABs) and/or (eg, maximum) quality of service (QoS) level that the second network entity 510 can support may include an indication of

The network entity 505 may send a response message 525 to the second network entity 510 (eg, in response to the request message 520 ). The response message 525 may include an acknowledgment of the request message 520 and/or address information (eg, for use in establishing a new secondary path in an existing (eg, MCG) anchor bearer) and/or may include one or more parameters (eg, associated with communication device 515 ), such as radio resource information. The address information may include an X2 downlink (DL) transport network layer (TNL) address.

The second network entity 510 may generate a configuration message 530 corresponding to the secondary path and/or radio bearer (eg, in response to the response message 525 ). The configuration message 530 may be generated using at least a portion of the response message 525 , such as radio resource information, address information, and the like. The configuration message 530 may include a secondary path identity, such as a secondary logical channel identity, a primary path identity, such as a primary logical channel identity, a bearer identity, one or more parameters, and/or one or more instructions.

The second network entity 510 may transmit a configuration message 530 to the communication device 515 . Communication device 515 may parse configuration message 530 to identify one or more identities, parameters, and/or commands. The communication device 515 may use the secondary logical channel identity of the configuration message 530 to determine (eg, calculate one or more dimensions and/or aspects of the secondary path). In some examples, communication device 515 may use the primary logical channel identity of configuration message 530 to determine a primary path (eg, calculate one or more dimensions and/or aspects of such primary path). In some examples, communication device 515 may use the bearer identity of configuration message 530 to determine a radio bearer (eg, calculate one or more dimensions and/or aspects of such radio bearer).

The communication device 515 determines whether a secondary path determined based on the secondary logical channel identity exists (eg, is operating in) the communication device 515 (eg, the secondary path is 515 ) to connect to the network entity 505 , the second network entity 510 and/or one or more other network entities. The determination is made based on (i) one or more parameters included in the configuration message 530 , (ii) a secondary path in one or more portions of the communication device 515 and/or one or more indicators associated with the secondary path. (iii) based on the number of paths determined to be between the communication device 515 and the network entity 505 , the second network entity 510 and/or one or more other network entities and/or (iv) the paths determined to be between the first component of the communication device 515 and/or the second network entity 510 and the second component of the communication device 515 and/or the second network entity 510 . It may be done based on the number.

The communication device 515 may determine based on the bearer identity whether the determined radio bearer exists (eg, and is operating in) the communication device 515 and/or the second network entity 510 . have. The determination may be made based on one or more parameters included in the configuration message 530 and/or select a radio bearer in one or more parts of the communication device 515 and/or the second network entity 510 and/or or by retrieving one or more indicators associated with the radio bearer.

Communication device 515 indicates that a secondary path and/or radio bearer exists (eg, and is operating in such communication device and/or second network entity) at communication device 515 and/or second network entity 510 . ) , the radio bearer and/or secondary path at the communication device 515 and/or the second network entity 510 may be modified based on the configuration message 530 .

Communication device 515 indicates that a secondary path and/or radio bearer exists (eg, and is operating in such communication device and/or second network entity) at communication device 515 and/or second network entity 510 . ) , the radio bearer and/or secondary path at the communication device 515 is established (eg, at the communication device 515 and/or the second network entity 510 ) based on the configuration message 530 . , can be created).

The communication device 515 sends a configuration status message 535 corresponding to whether it has been determined that a secondary path and/or radio bearer exists and/or whether one or more actions have been taken in connection with such secondary path and/or radio bearer. can also create The configuration status message 535 may be generated using at least a portion of the response message 525, such as radio resource information, address information, and the like. The configuration status message 535 may include the secondary path status, radio bearer and/or instructions in the configuration message 530 . For example, the status may be indicative of full success, partial success, and/or failure of the communication device 515 in establishing and/or modifying a secondary path and/or radio bearer.

The communication device 515 may transmit a configuration status message 535 to the second network entity 510 . The second network entity 510 may analyze the configuration status message 535 to determine the status of the secondary path, a radio bearer and/or instructions in the configuration message 530 .

In response to determining that the status corresponds to a first status (eg, complete success), the second network entity 510 (eg, and/or one or more other network entities) may (eg, based on the existence of a secondary path) to facilitate use and/or interaction with the communication device 515 ). In response to determining that the status corresponds to a second status (eg, partial success), the second network entity 510 (eg, and/or one or more other network entities) may (eg, in the presence of a change in the secondary path) a second operation (facilitating use and/or interaction with the communication device 515 ) based on the communication device 515 . In response to determining that the status corresponds to a third status (eg, failed), the second network entity 510 (eg, and/or one or more other network entities) may (eg, based on the absence of a secondary path) a third operation (facilitating use and/or interaction with the communication device 515 ) may be performed.

The second network entity 510 checks the configuration status message 535 and/or whether it has been determined that a secondary path and/or radio bearer exists and/or whether one or more actions have been taken in connection with such secondary path and/or radio bearer. A reconfiguration completion message 540 corresponding to whether or not may be generated. For example, the reconfiguration complete message 540 may indicate whether reconfiguration of the communication device 515 according to the configuration message 530 , the request message 520 and/or its response message 525 has been successfully performed. have.

The second network entity 510 may send a reconfiguration complete message 540 to the network entity 505 . A random access procedure 545 and/or synchronization may be performed between a network entity 505 (eg, a primary SCell of such network entity) and a communication device 515 . The communication device 515 may perform uplink transmissions using the modified configuration (eg, resulting from implementation of the configuration message 530 ).

The second network entity 510 may transmit the status transmission information 550 to the network entity 505 and/or may transmit the forwarding information 555 to the network entity 505 . The forwarding information 555 may include a bearer context corresponding to a radio bearer of the communication device 515 . In some examples, the route update may be performed across the network entity 505 , the second network entity 510 , the communication device 515 , and/or one or more other network entities.

6A shows an example of a system 600A having a control plane of a radio bearer 605A that may be used by a communication device (eg, UE) using a secondary path. A representation of the radio bearer 605A is a first representation of a first logical channel 610A corresponding to a radio resource control (RRC) configuration associated with a first communication standard and a second logical corresponding to an RRC configuration associated with a second communication standard. a second representation of channel 615A. For example, the first logical channel 610A may correspond to a Long-Term Evolution (LTE) RRC configuration and/or the second logical channel 615A may correspond to a 5G New Radio (NR) RRC configuration. have.

The first logical channel 610A may include a (eg, data) radio bearer configuration 620A, which may include a (eg, EPC) bearer identity, (eg, data) radio bearer identity and/or PDCP. It may also include configuration information. The first logical channel 610A may include a first logical channel configuration 625A, which first logical channel configuration (eg, of the first logical channel 610A) may include a first logical channel identity, an anchor (eg, of the first logical channel 610A). , data) radio bearer identity, RLC configuration information, and/or first logical channel configuration information may alternatively and/or additionally include. In particular, the radio bearer configuration 620A may be separate from the first logical channel configuration 625A. However, at least a portion of the radio bearer configuration 620A is associated (eg, a link) with the first logical channel configuration 625A based on a (eg, data) radio bearer identity (eg, it may be included in both configurations). could be

The second logical channel 615A may include a second logical channel configuration 630A, which second logical channel configuration (eg, of the second logical channel 615A) may include a second logical channel identity, an anchor (eg, of the second logical channel 615A). , data) radio bearer identity, RLC configuration information, and/or second logical channel configuration information. In some examples, at least a portion of the second logical channel configuration 630A is different from at least a portion of the first logical channel configuration 625A. In some examples, at least a portion of the second logical channel configuration 630A is the same as at least a portion of the first logical channel configuration 625A. In some examples, the second logical channel 615A may not include a radio bearer configuration. In some examples, the second logical channel 615A may include a second radio bearer configuration. In some examples, the second radio bearer configuration may be the same as the radio bearer configuration 620A. In some examples, the second radio bearer configuration may be different from the radio bearer configuration 620A.

6B shows an example of a system 600B with a user plane of a radio bearer 605A that may be used by a communication device (eg, UE) using a secondary path. The representation of the radio bearer 605B includes a first representation of a first logical channel 610B corresponding to an RRC configuration associated with a first communication standard and a second logical channel 615B corresponding to an RRC configuration associated with a second communication standard. It may include a second expression. For example, the first logical channel 610B may correspond to an LTE RRC configuration and/or the second logical channel 615B may correspond to an NR RRC configuration.

The first logical channel 610B may include a (eg, data) radio bearer configuration 620B, which may include PDCP configuration information (eg, it may be mapped to a PDCP entity). . The first logical channel 610B may alternatively and/or additionally include a first logical channel configuration 625B, which may include RLC configuration information. When the RLC configuration information includes configurations that can be mapped to two or more RLC entities, an unacknowledged mode (UM) may be implemented. When the RLC configuration information includes configurations that can be mapped to (eg, only) one RLC entity, acknowledgment mode (AM) may be implemented. In particular, the radio bearer configuration 620B may be separate from the first logical channel configuration 625B.

The second logical channel 615B may include a second logical channel configuration 630B, which may include RLC configuration information. When the RLC configuration information includes configurations that can be mapped to two or more RLC entities, UM may be implemented. When the RLC configuration information includes configurations that can be mapped to (eg, only) one RLC entity, AM may be implemented. In some examples, at least a portion of the second logical channel configuration 630B is different from at least a portion of the first logical channel configuration 625B. In some examples, at least a portion of the second logical channel configuration 630B is the same as at least a portion of the first logical channel configuration 625B.

7 presents a schematic architectural diagram 700 of a base station 750 (eg, a network entity) that may utilize at least a portion of the techniques provided herein. This base station 750 may be configured and configured, alone or in conjunction with other base stations, nodes, end units and/or servers, etc., to provide a service, such as at least some of one or more other disclosed techniques, scenarios, etc. may vary widely in capabilities. For example, the base station 750 may include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks. A (eg, wireless and/or wired) network (eg, it may be connected to one or more other base stations and/or such as networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, etc.) one or more user equipments (UEs) (which may include other such base stations). Networks are wireless technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, Global System for Mobile Communications (GSM), Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM, etc. may be implemented. The base station 750 and/or the network may communicate using a standard, such as LTE (Long-Term Evolution).

Base station 750 may include one or more (eg, hardware) processors 710 that process instructions. The one or more processors 710 may include a plurality of cores; one or more coprocessors, such as mathematical coprocessors or an integrated graphical processing unit (GPU); and/or one or more layers of local cache memory. The base station 750 may be used for various types of applications, such as an operating system 704; one or more base station applications 706; and/or memory 702 that stores various types of data, such as a database 708 and/or a file system. The base station 750 may include various peripheral components such as a wired and/or wireless network adapter 714 connectable to a local area network and/or a wide area network; one or more storage components 716 , such as a hard disk drive, a solid-state storage device (SSD), a flash memory device, and/or a magnetic and/or optical disk reader; and/or other peripheral components.

The base station 750 may include a serial or parallel AT Attachment (ATA) bus protocol; Uniform Serial Bus (USB) protocol; and/or one or more communications interconnecting the processor 710 , the memory 702 , and/or the various peripherals using various bus technologies, such as variants of the Small Computer System Interface (SCI) bus protocol. It may also include a motherboard featuring buses 712 . In a multibus scenario, a communication bus 712 may interconnect the base station 750 and at least one other server. Base station 750 and other components that may optionally be included (not shown in schematic 700 of FIG. 7 ) include a display; a display adapter such as a graphics processing unit (GPU); input peripherals such as a keyboard and/or mouse; and/or a flash memory device that may store basic input/output system (BIOS) routines that facilitate booting the base station 750 to a readiness state.

Base station 750 may operate in various physical enclosures, such as a desktop or tower, and/or may be integrated with a display as an “all-in-one” device. Base station 750 may be mounted horizontally and/or in a cabinet or rack, and/or may simply include a set of interconnected components. Base station 750 may include a dedicated and/or shared power supply 718 that powers and/or regulates other components. Base station 750 may provide power to and/or receive power from other base stations and/or servers and/or other devices. Base station 750 may include a shared and/or dedicated climate control unit 720 that adjusts climate characteristics, such as temperature, humidity, and/or airflow. Many such base stations 750 may be configured and/or adapted to utilize at least a portion of the techniques presented herein.

8 presents a schematic architectural diagram 800 of a user equipment (UE) 850 (eg, a communication device) in which at least a portion of the techniques presented herein may be implemented. Such a UE 850 may vary widely in configuration and/or capabilities to provide various functionality to a user. The UE 850 may come in a variety of form factors, such as a mobile phone (eg, a smartphone); desktop or tower workstation; an “all-in-one” device with an integrated display 808 ; a laptop, tablet, convertible tablet, or palmtop device; wearable devices, such as mountable on headsets, eyeglasses, earphones, and/or wristwatches, and/or integrated with apparel articles; and/or a component of a piece of furniture, such as a tabletop, and/or of another device, such as a vehicle or residence. The UE 850 may serve a user in various roles, such as a phone, workstation, kiosk, media player, gaming device, and/or appliance.

The UE 850 may include one or more (eg, hardware) processors 810 that process instructions. The one or more processors 810 may include a plurality of cores; one or more coprocessors, such as numerical coprocessors or an integrated graphics processing unit (GPU); and/or one or more layers of local cache memory. The UE 850 may be configured for various types of applications, such as an operating system 803 ; One or more user applications 802 , such as document applications, media applications, file and/or data access applications, communication applications, such as web browsers and/or email clients, utilities, and/or games ; and/or a memory 801 for storing drivers for various peripheral devices. The UE 850 may include various peripheral components such as a wired and/or wireless network adapter 806 connectable to a local area network and/or a wide area network; one or more output components, such as a display 808 coupled to a display adapter (optionally including a graphics processing unit (GPU)) coupled with a display adapter, a sound adapter coupled to a speaker, and/or a printer; input devices for receiving input from a user, such as a keyboard 811 , a mouse, a microphone, a camera, and/or a touch-sensitive component of the display 808 ; and/or environmental sensors such as a GPS receiver 819 to detect the location, velocity, and/or acceleration of the UE 850 , a compass, an accelerometer, and/or a gyroscope to detect the physical orientation of the UE 850 . You may. Other components that may not optionally be included in the UE 850 (not shown in the schematic architecture diagram 800 of FIG. 8 ) include a hard disk drive, a solid state storage device (SSD), a flash memory device, and/or or one or more storage components, such as a magnetic and/or optical disk reader; a flash memory device that may store basic input/output system (BIOS) routines that facilitate booting the UE 850 to a ready state; and/or a climate control unit that adjusts climate characteristics such as temperature, humidity, and airflow.

UE 850 may use a serial or parallel ATA bus protocol; Uniform Serial Bus (USB) protocol; and/or one or more communication buses 812 interconnecting the processor 810, memory 801, and/or various peripherals using various bus technologies, such as variants of the Small Computer System Interface (SCI) bus protocol. It may include a main board characterized in that. The UE 850 may have a dedicated and/or shared power supply 818 that powers and/or modulates such power to other components, and/or the UE 850 may be powered via a power supply 818 . It may also include a battery 804 that stores power for use while not connected. The UE 850 may provide power to and/or receive power from other client devices.

9 is an illustration of a scenario 900 involving an example non-transitory computer-readable medium 902 . The non-transitory computer-readable medium 902 includes processor-executable instructions 912 that, when executed by the processor 916 , cause performance (eg, by the processor 916 ) of at least some of those provided herein. You may. The non-transitory computer-readable medium 902 may include a memory semiconductor (eg, static random access memory (SRAM), dynamic random access memory (DRAM), and/or synchronous dynamic random access memory (SRAM) semiconductors using synchronous dynamic random access memory (SDRAM) technologies), platters of hard disk drives, flash memory devices, or magnetic or optical disks (such as compact discs (CDs), digital versatile discs (DVDs) ), and/or a floppy disk). The example non-transitory computer-readable medium 902 may undergo a read 906 by a reader 910 of the device 908 (eg, a read operation invoked on a read head of a hard disk drive, or a solid state storage device). when stored, computer-readable data 904 representing processor-executable instructions 912 . In some embodiments, the processor-executable instruction 912, when executed, is, for example, the example method 100A of FIG. 1A , the example method 100B of FIG. 1B and/or the example method 100B of FIG. 1C ( 100C). In some embodiments, the processor-executable instruction 912 may include, for example, the example system 200A of FIG. 2A , the example system 200B of FIG. 2B , the example system 300A of FIG. 3A , the example system 300A of FIG. 3B , for example. Exemplary system 300B, exemplary system 400A of FIG. 4A , exemplary system 400B of FIG. 4B , exemplary system 500 of FIG. 5 , exemplary system 600A of FIG. 6A and/or FIG. and enable implementation of a system and/or scenario, such as at least a portion of example system 600B of 6b.

As used herein, “component,” “module,” “system,” “interface,” and the like, are computer-related entities that are either hardware, a combination of hardware and software, software, or software in execution. It is generally intended to refer to For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of example, both the controller and the application running on the controller can be one component. One or more components may reside within a process and/or thread of execution and/or a component may be localized on one computer and/or distributed between two or more computers (eg, node(s)). .

Unless otherwise specified, “first,” “second,” etc. are not intended to mean temporal, spatial, regular, or the like. Rather, these terms are only used as identifiers, names, etc., for features, elements, items, and the like. For example, a first object and a second object generally correspond to object A and object B or two different or two identical objects or the same object.

Moreover, “example” is used herein to mean serving as an instance, example, etc., but is not necessarily advantageous. As used herein, “or” is intended to mean an inclusive “or” rather than an exclusive “or.” Incidentally, as used in this application, the singular corresponding to the use of "a" and "an" is generally interpreted to mean "one or more," unless otherwise specified or clear from the context for the singular. could be Also, at least one of A and B and the like generally mean A or B or both A and B. Moreover, to the extent that “comprises”, “having”, “having”, “having”, and/or variations thereof are used in either the specification or the claims, these terms are in a manner analogous to the term “comprising”. It is intended to be included as

Although the subject matter of the present invention has been described in language specific to structural features and/or methodological acts, the subject matter defined in the appended claims need not be limited to the specific features and acts described above. It is understood that there is no Rather, the specific features and acts described above are disclosed as example forms of implementing at least some of the claims.

Moreover, the claimed subject matter uses standard programming and/or engineering techniques to create software, firmware, hardware, or any combination thereof, that control a computer (eg, a node) to implement the disclosed subject matter. may be implemented as a method, apparatus, or article of manufacture using As used herein, the term "article of manufacture" is intended to encompass a computer program accessible from any computer readable device, carrier, or medium. Of course, it will be appreciated that many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.

Various acts of embodiments and/or examples are provided herein. The order in which some or all of the operations are described herein should not be construed as implying that these operations are necessarily order dependent. Alternative orderings will be understood by those of ordinary skill in the art having the benefit of this specification. Moreover, not necessarily all acts are necessarily presented in each embodiment and/or example provided herein. Also, it will be understood that not all acts are required in some embodiments and/or examples.

Moreover, although this disclosure has been shown and described with respect to one or more implementations, equivalent modifications and variations will occur to those skilled in the art based on a reading and understanding of this specification and the appended drawings. . This disclosure includes all such modifications and variations and is limited only by the scope of the following claims. In particular with respect to the various functions performed by the components (eg, elements, resources) described above, the terms used to describe these components, unless otherwise indicated, even if not structurally equivalent to the disclosed structure. , is intended to correspond to any component that performs (eg, functionally equivalent) a specified function of the described component. In addition, while a particular feature of the present disclosure may have been disclosed for only one of several implementations, such feature may be combined with one or more other features of other implementations such that it may be desirable and beneficial for any given or particular application. could be

Claims (35)

In the method,
receiving, by a communication device connected to the network entity via a primary path, a configuration message from the network entity;
identifying, from the configuration message by the communication device, a secondary logical channel identity configured to identify a secondary path;
configuring, by the communication device, the secondary path based on the configuration message; and
sending, by the communication device, a response message to the network entity in response to the configuration message;
The step of constructing the secondary path comprises:
determining whether the secondary path exists;
in response to determining that the secondary path does not exist, establishing the secondary path based on the configuration message;
generating a mapping between the secondary path and a radio bearer; and
identifying, from the configuration message, a radio bearer identity to identify the radio bearer;
A method further comprising: The method of claim 1, wherein the configuring of the secondary path comprises:
in response to, by the communication device, determining that the secondary path exists, releasing the secondary path based on the configuration message. The method of claim 2, wherein the step of releasing the secondary path comprises:
removing, by the communication device, a second radio link control entity corresponding to the secondary path, connected to a packet data convergence protocol entity. The method of claim 1, wherein the configuring of the secondary path comprises:
modifying, by the communication device, the secondary path based on the configuration message in response to determining that the secondary path exists. 5. A wireless communications device comprising a processor and a memory, wherein the processor is configured to read code from the memory and perform the method of any one of claims 1-4. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete

Images