[go: up one dir, main page]

WO2016029962A1 - Établissement d'une double connectivité - Google Patents

Établissement d'une double connectivité Download PDF

Info

Publication number
WO2016029962A1
WO2016029962A1 PCT/EP2014/068372 EP2014068372W WO2016029962A1 WO 2016029962 A1 WO2016029962 A1 WO 2016029962A1 EP 2014068372 W EP2014068372 W EP 2014068372W WO 2016029962 A1 WO2016029962 A1 WO 2016029962A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
dual connectivity
request
radio access
response
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2014/068372
Other languages
English (en)
Inventor
Klaus Ingemann Pedersen
Claudio Rosa
Per Henrik Michaelsen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Priority to PCT/EP2014/068372 priority Critical patent/WO2016029962A1/fr
Publication of WO2016029962A1 publication Critical patent/WO2016029962A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the invention relates to the field of telecommunications and, particularly, to dual connectivity.
  • the basic principle of the dual connectivity is that the user apparatus may con- sume radio resources provided by at least two different network nodes, each network node controlling one or more cells, one of the network nodes being a master network node controlling radio resources for the user apparatus.
  • a general aspect of the invention provides a mechanism for a network triggered dual connectivity to a user apparatus connected to the network with a single connection.
  • Various aspects of the invention comprise methods, apparatuses, a computer program product and a system as defined in the independent claims. Further embodiments of the invention are disclosed in the dependent claims.
  • FIG. 1 shows simplified architecture of a system and block diagrams of some apparatuses according to an exemplary embodiment
  • Figures 2 and 3 are flow charts illustrating exemplary functionalities
  • Figure 4 illustrates exemplary signaling
  • Figure 5 is a schematic block diagram of an exemplary apparatus.
  • the present invention is applicable to any access network/system and apparatus that can be or are configured to support dual connectivity.
  • access networks/systems include LTE (Long Term Evolution) access system, World- wide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), LTE Advanced (LTE-A), and beyond LTE-A, such as 4G (fourth generation) and 5G (fifth generation).
  • WiMAX World- wide Interoperability for Microwave Access
  • WLAN Wireless Local Area Network
  • LTE-A LTE Advanced
  • 4G fourth generation
  • 5G farth generation
  • All words and expressions should be inter- preted broadly and they are intended to illustrate, not to restrict, the embodiment.
  • Figure 1 A general architecture of an exemplary system 100 is illustrated in Figure 1 .
  • Figure 1 is a simplified system architecture only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown. It is apparent to a person skilled in the art that the system may also comprise other functions and structures that are not illustrated, for example connections to the core network/system.
  • the exemplary system 100 illustrated in Figure 1 comprises user apparatuses 1 10 (only one illustrated in Figure 1 ) and two or more network nodes 120, 120' (only two illustrated in Figure 1 ) controlling one or more cells in a radio access system 101 , and a mobility management entity 130.
  • the mobility management entity (MME) 130 represents a mobility anchor entity in a core network that is involved in the bearer activation/deactivation processes, for example.
  • the mobility management entity is configured to support the network initiated dual connectivity and comprises for that purpose an updated control unit (C-u) 131.
  • the control unit 131 is updated to recognize signaling relating to the network initiated dual connectivity, and act upon it, as will be described in more detail with Figure 4.
  • the user apparatus (user equipment, UE) 1 10 illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with user apparatus (user equipment) may be implemented with a corresponding apparatus.
  • the user apparatus 1 10 refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: mobile phone, smart-phone, personal digital assistant (PDA), handset, laptop computer, e-reading device, tablet.
  • SIM subscriber identification module
  • the user apparatus 1 10 is configured to support also network initiated dual connectivity, and comprises for that purposes an updated dual connectivity (DC-u) unit 1 1 1 , the functionality of which is described in more detail with Figure 4.
  • DC-u updated dual connectivity
  • both network nodes 120, 120' depicts an appa- ratus controlling one or more cells via which access is provided to the network the user apparatuses and the network nodes are connected to.
  • a network node is an evolved node B (eNB).
  • the evolved node B 120, or any corresponding network apparatus controlling one or more cells, is a computing device configured to control the radio resources, and connected to the evolved packet core net- work, thereby providing the user equipment 1 10 a connection to the communication system.
  • the evolved node B comprises all radio-related functionalities of the communication whereby the evolved node B, for example, schedules transmissions by assigning certain uplink resources for the user equipment and informing the user equipment about transmission formats to be used.
  • the evolved node B 120, 120' is configured to perform one or more of evolved node B functionalities described below with an embodiment, and it may be configured to perform functionalities from different embodiments.
  • the evolved node B comprises a dual connectivity decision unit (DC dec U) 121 , 121 ' for network initiated dual connectivity and memory 122, 122' for at least temporarily buffering, as will be de- scribed in more detail below.
  • the evolved node B also provides the cells but the exemplary embodiments may be implemented with a solution having a separate controlling apparatus, and separate cell providing apparatuses controlled by a controlling apparatus. Further, the cells may be macro cells, and/or small cells.
  • a user apparatus In dual connectivity, a user apparatus is connected to a master evolved node B (MeNB) controlling a primary cell and comprising a radio resource controlling unit for the user apparatus, and to a secondary evolved node B (SeNB) controlling a secondary cell.
  • MeNB master evolved node B
  • SeNB secondary evolved node B
  • the evolved node B controlling the macro cell is typically selected to be the master evolved node B, since then fewer MeNB handovers are needed when the user apparatus moves compared to the situation in which the evolved node B controlling the small cell would have been selected to be MeNB.
  • FIG. 2 is a flow chart illustrating an exemplary functionality of an evolved node B, or more precisely, an exemplary functionality of the dual connectivity decision unit, in a situation in which the evolved node B is controlling a cell via which a user apparatus that is configured to support dual connectivity has a single connection to the network, and the radio resource control (RRC) of the user apparatus located in the evolved node B.
  • RRC radio resource control
  • responses to requests are received (i.e. monitoring whether a response is received and no resending is described), and sending/receiving mere acknowledgements "received" are not described.
  • the evolved node B is called below original master evolved node B.
  • a dual connectivity (DC) capable user apparatus is served in step 201 over a single connection, i.e. in a single connectivity (SC) mode, in a cell controlled by the original master evolved node B .and information relating the served user apparatus is monitored in step 202.
  • the monitored information may be any information, or combinations of different information that is usable to decide whether or not there is a need for dual connectivity. Examples of such monitoring and information include receiving a measurement report comprising one or more measurements, such as signal strength measurements, receiving a buffer status report, monitoring buffers for downlink data, monitoring cell load, monitoring the amount of buffer data, and monitoring achieved throughput.
  • the dual connectivity deci- sion unit determines in step 203, using the monitored information, whether or not to trigger network initiated dual connectivity. Any decision algorithm may be used, it suffices that the algorithm outputs a decision, using as input at least some of the monitored information.
  • step 203 If the network initiated dual connectivity is not triggered (step 203), the process returns to step 201 to serve the user apparatus in a single connectivity mode.
  • the dual connectivity decision unit selects (determines) in step 204, using the received signal strengths, for example, which one of the cells, and thereby which one of the evolved node Bs con- trolling the cell is to be a new MeNB. It should be appreciated that any selection criteria may be used.
  • a request to start to be MeNB is sent in step 205 to the selected evolved node B.
  • the request contains at least information necessary for the selected evolved node B to decide whether or not it can be MeNB. Further, the request may contain other information. For example, the content of the request may be similar to or exactly the same as is the information sent for handover preparation.
  • the content of the request may, for example, include signalling contexts (X2 and EPC), RRC context and E-RAB (radio access bearer) context that a "Handover Request" includes.
  • the request may contain information on resources available in the evolved node B, for example information on available cells, or any other suggested secondary cell configuration.
  • step 206 a response is received (step 206) from the selected evolved node B. If the response indicates a rejection (step 207) the network initiated dual connectivity procedure is ended in step 208, and the process returns to step 201 to serve the user apparatus in a single connectivity mode.
  • the response contains at least a master cell group (MCG) configuration and other information by means of which a secondary cell group (SCG) configuration is determined in step 208. Since no changes for the SCG configuration, or its determination, is needed, there is no need for a more detailed description herein.
  • the secondary cell group configuration con- tains serving cells associated with (controlled by) the original master evolved node B that is going to be SeNB.
  • the response may also contain other information.
  • the response may contain the dual connectivity configuration such as one or more cells to be used in the secondary cell group, one or more bearer types to be used, etc.
  • MCG configuration means configura- tion of cells aggregated on MeNB
  • SCG configuration means configuration of cells aggregated on SeNB
  • dual connectivity configuration means the combination of MCG and SCG.
  • the evolved node B se- lected to be the intended new MeNB is informed in step 21 1 by sending a rejection to the selected evolved node B.
  • the rejection may or may not comprise the reason why the configuration was rejected.
  • the rejection may comprise a reason for the rejection, that may be handled in a similar way, and therefore need not to be de- scribed in more detail herein.
  • the process then returns to step 201 to serve the user apparatus in a single connectivity mode.
  • a response indicating acceptance is sent in step 212 to the new MeNB and the user apparatus is instructed in step 212 to reconfigure its radio re- source control by sending to the user apparatus the determined SCG configuration, and the MCG configuration received in step 206 in the response, for example.
  • the MCG configuration indicates the group of the serving cells associated with MeNB, i.e. the selected evolved node B). In other words, preferably the same information is sent to the user apparatus that is sent during prior art (or future) SeNB addition procedure. Further, user data sending to UE is stopped in step 213.
  • step 214 it is determined in step 214 whether or not a path for user plane data needs to be switched, i.e. whether or not the user plane data needs to be redirected via the selected evolved node B. For example, if the determined SCG configuration in a cell controlled by the original master evolved node B is configured to be a split bearer after the MeNB addition procedure ends, the user plane data needs to be redirected via the selected evolved node B. It should be appreciated that also other reasons may cause that the user plane data needs to be redirected via the selected evolved node B, and the reason bears no significance for the current procedure, it suffices that the redirection is needed.
  • transmitter and receiver statuses are sent in step 215 to the selected evolved node B for information.
  • uplink PDCP SN Packet Data Convergence Protocol Sequence Number
  • HFN Hexaper Frame Number
  • downlink PDCP SN and HFN may be sent as a receiver status and a transmitter status, correspondingly.
  • buffering the received user data targeted to the user apparatus is continued in step 216 and the buffered data is forwarded in step 216 to the selected evolved node B. The buffering and forwarding of step 216 is continued until an indication that the downlink user data will end (step 217) is received.
  • the indication may be an end marker indicating that the path switching has been completed and no new data to UE will be received. When the indication is received, no new data will be received, and hence not buffered. Therefore, after all buffered data has been forwarded (step 218) to the selected evolved node B, path switching operations, as is the case with SeNB addition procedure, are performed and resources reserved for data transmission to UEZ are updated in step 219. When an indication that eNB2 is now acting as MeNB is received in step 220, the transmissions to UE are restarted in step 221 (using the new path). The indication may be a message "Self addition complete".
  • step 213 If the path switch is not needed (step 213), in the illustrated example, when the indication that eNB2 is now acting as MeNB is received in step 220, the transmissions to UE are restarted in step 221.
  • Figure 3 is a flow chart illustrating an exemplary functionality of an evolved node B, or more precisely, an exemplary functionality of the dual connectivity decision unit, in a situation in which the evolved node B receives a request from another evolved node B.
  • responses to requests are received (i.e. monitoring whether a response is received and no resending is de- scribed), and sending/receiving mere acknowledgements "received" are not described.
  • the evolved node B is called below intended master evolved node B.
  • a request to start to be a MeNB is received in step 300 from a requesting evolved node B, the request being described above with Figure 2, step 205.
  • step 301 Using the information in the request, and admission control decision, it is decided in step 301 whether or not the request is an acceptable one. If it is not, a response indicating a rejection is sent in step 302. Depending on an implementation, the rejection may or may not contain one or more reasons for the rejection. It should be appreciated that any admission control decision criteria may be implemented, and hence there is no need to describe it in more detail herein.
  • a dual connectivity configuration is determined in step 303, for example in a similar way as it is determined in SeNB process. It should be appreciated that the way how the dual connectivity con- figuration is determined is irrelevant for the invention and therefore it is not described in detail here.
  • a response indicating acceptance and containing at least master cell group (MCG) configuration and information needed by the requesting evolved node B to configure secondary cell group (SCG) is sent in step 304 to the requesting evolved node B.
  • MCG master cell group
  • SCG secondary cell group
  • the acceptance is a kind of request to enter dual connectivity, that would have been used, if the evolved node B has been MeNB from the very beginning and would have asked the requesting evolved node B to be SeNB.
  • an acknowledgement to the response is received in step 305 from the requesting evolved node B.
  • step 305 If the acknowledgement received in step 305 indicates (step 306) that the requesting evolved node B does not accept the configuration indicated in the response sent in step 304, the process ends in step 307.
  • step 305 indicates (step 306) that the requesting evolved node B accepts the configuration indicated in the response sent in step 304, in the illustrated example the intended master evolved node B simply waits for a next message. It should be appreciated that the acknowledgement may contain the final SCG configuration that has been determined taking into account the information provided by the evolved node B in the acceptance.
  • the next message received is a message containing status information, i.e. a message containing the transmitter and receiver statuses described above with Figure 2, and one or more buffers are allocated in step 310, and user data to the user apparatus is received and buffered in step 31 1 , as is performed in prior art SeNB addition procedure.
  • a random access request is received in step 312 from the user apparatus, and access information, such as uplink allocation and timing advance information is sent in step 313 to the user apparatus. No changes for the procedure are needed.
  • the radio resource control is now terminated in the intended master evolved node B, and a mobility management entity (MME) is informed correspondingly by sending in step 314 a path update request.
  • MME mobility management entity
  • MME triggers path switching and after it is performed, the new master evolved node B receives an acknowledgement in step 315 from the mobility management entity, sends in step 316 to the requesting evolved node B information that the process is now completed, and data transmission to UE is started (step 317).
  • Figure 4 illustrates an exemplary signaling in a situation in which a user apparatus UE is configured to support dual connectivity but is currently having a single connection (i.e. is in a single connectivity mode) over one or more cells controlled by an evolved node B, eNB1.
  • eNB1 maintains UE context for the sin- gle connection and has the radio resource control (RRC) entity for UE.
  • RRC radio resource control
  • eNB1 detects in point 4-1 that UE needs more resources, determines therefore in point 4-1 to trigger network initiated dual mode accession procedure, i.e. enter the dual mode to acquire more resources to UE, selects in point 4-1 an evolved node eNB2 to be a new master evolved node B and sends message 4-2 to eNB2.
  • Message 4-2 may be a "SeNB Self Addition Request" containing information described above with Figure 2, step 205, and indicating that eNB1 assumes to be a secondary evolved node B (SeNB).
  • eNB2 decides in point 4-3, whether or not to accept to become a master evolved node B (MeNB) for UE, as described above with Figure 3, step 301.
  • MeNB master evolved node B
  • eNB2 accepts to become MeNB, and sends message 4-4 to eNB1 .
  • Message 4-4 may be a "SeNB Self Addition Request Acknowledge" and in the illustrated example it is assumed that message 4-4 contains precise secondary cell group (SCG) configurations, and master cell group (MCG) configurations for UE, the configurations being config- ured by eNB2 in point 4-3.
  • SCG secondary cell group
  • MCG master cell group
  • eNB1 accepts the SCG configurations received in message 4-4 and acknowledges acceptance of the SCG configurations by sending message 4-5 to eNB2.
  • Message 4-5 may be "SeNB Self Addition Configuration Acknowledge", or "SeNB Self Addition Configuration Response”. The latter may be used in implementations in which eNB1 determines the SCG configurations at least partly, to convey the SCG configuration information.
  • eNB1 sends, in response to message 4-4, message 4-6 to UE instructing UE to reconfigure its radio resource connection, and thereby making the RRC entity in eNB1 useless.
  • message 4-6 may be "RRC Connection Reconfiguration", as used in handover or SCG modification procedures, for example.
  • the updated DC unit in UE detects, in response to receiving message 4-6, the new DC configurations in point 4-7, and reconfigures its radio resource connection correspondingly, and acknowledges the reconfiguration by sending message 4-8 to eNB1.
  • Message 4-8 may be "RRC Connection Reconfiguration Com- plete", for example.
  • eNB2 Since no changes are needed to the reconfiguration procedure and status transfer procedure from eNB1 to eNB2, they are not described in detail here.
  • eNB2 After the status transfer procedure eNB2 is the MeNB, and therefore eNB2 sends message 4-9 to eNB1 to inform that UE reconfiguration has been performed.
  • Message 4-9 may be "SeNB Self Addition Complete” and it may be similar to "SeNB addition complete” message, or to "SeNB Reconfiguration Complete” message.
  • eNB1 starts to act as a secondary evolved node B. Further, eNB1 starts to forward the user data to eNB2 and stops forwarding the user data to UE, but that is not illustrated in Figure 4.
  • eNB2 sends to a mobility management entity MME message 4-10 to inform MME that the master evolved node B has been changed and to request MME to update bearers to be according to the new SCG configuration.
  • MME mobility management entity
  • a termination (end point) of a bearer moves from eNB1 to eNB2, a new bearer is created at eNB1 or eNB2.
  • Message 4-10 may be a "Path Switch Request"
  • MME or more precisely, the updated control unit, detects in point 4-1 1 that a path change may be needed, and triggers a path switching procedure, that is used also with handover procedures, for example, and therefore it is not described in detail here.
  • MME sends to eNB2 message 4-12 to acknowledge that the termination has changed.
  • Message 4-12 may be "Path Switch Request Ack".
  • eNB2 sends to eNB1 message 4-13 to indicate that the network initiated dual mode accession procedure was successful and therefore UE context may be released.
  • message 4-13 After the dual mode accession procedure has ended, it is ensured that a prompt RRC reestablishment towards eNB1 may be performed if the dual mode accession procedure fails at some point. However, in some other implementations, the UE context may be released earlier.
  • the network nodes comprise a dual connectivity decision unit configured to both being the one configured to request the dual connectivity, or the one configured to accept the dual connectivity
  • a network node may be configured to comprise a corresponding requesting sub-unit or an accepting sub-unit.
  • eNB1 can continue transmissions on the split bearer and instead of forwarding data from eNB1 to eNB2, eNB1 can send the data to UE over the split bearer.
  • an apparatus/network node implementing one or more functions of a corresponding apparatus/network node described with an embodiment/example/implementation comprises not only prior art means, but also means for implementing the one or more functions of a corresponding apparatus described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more functions.
  • the dual connectivity decision unit and/or algorithms may be software and/or software-hardware and/or hardware and/or firmware components (recorded indelibly on a medium such as read-only- memory or embodied in hard-wired computer circuitry) or combinations thereof.
  • Software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers, hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof.
  • firmware or software implementation can be through modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • Software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers.
  • FIG. 5 is a simplified block diagram illustrating some units for an apparatus 500 configured to be a network apparatus (network node) comprising the dual connectivity decision unit, or corresponding functionality.
  • the apparatus comprises an interface (IF) 501 for receiving and transmitting information over the radio access network, a processor 502 configured to implement at least the dual connectivity decision unit functionality or the dual connectivity decision requesting sub-unit functionality or the dual connectivity decision accepting sub-unit functionality, described herein, with corresponding algorithms 503, and memory 504 usable for storing a program code required for the dual connectivity decision unit and the algorithms.
  • the memory 504 is also usable for storing other possible information, like information on configurations, and for buffering.
  • an apparatus configured to provide the network apparatus is a computing device that may be any apparatus or device or equipment or node configured to perform one or more of corresponding apparatus functionalities described with an embodiment/example/implementation, and it may be configured to perform functionalities from different embodiments/examples/implementations.
  • the dual connectivity decision unit, or its requesting sub-unit, and accepting sub-unit, as well as other units, described above with an apparatus may be separate units, even located in another physical apparatus, the distributed physical apparatuses forming one logical apparatus providing the functionality, or integrated to another unit in the same apparatus.
  • the apparatus configured to provide the network apparatus may generally include a processor, controller, control unit, micro-controller, or the like connected to a memory and to various interfaces of the apparatus.
  • the processor is a central processing unit, but the processor may be an additional opera- tion processor.
  • Each or some or one of the units/sub-units and/or algorithms described herein may be configured as a computer or a processor, or a microprocessor, such as a single-chip computer element, or as a chipset, including at least a memory for providing storage area used for arithmetic operation and an operation processor for executing the arithmetic operation.
  • Each or some or one of the units/sub-units and/or algorithms described above may comprise one or more computer processors, application-specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field- programmable gate arrays (FPGA), and/or other hardware components that have been programmed in such a way to carry out one or more functions of one or more embodiments/implementations/examples.
  • ASIC application-specific integrated circuits
  • DSP digital signal processors
  • DSPD digital signal processing devices
  • PLD programmable logic devices
  • FPGA field- programmable gate arrays
  • each or some or one of the units/sub-units and/or the algorithms described above may be an element that comprises one or more arithmetic logic units, a number of special registers and control circuits.
  • the apparatus configured to provide the network apparatus may generally include volatile and/or non-volatile memory, for example EEPROM, ROM, PROM, RAM, DRAM, SRAM, double floating-gate field effect transistor, firmware, programmable logic, etc. and typically store content, data, or the like.
  • volatile and/or non-volatile memory for example EEPROM, ROM, PROM, RAM, DRAM, SRAM, double floating-gate field effect transistor, firmware, programmable logic, etc. and typically store content, data, or the like.
  • the memory or memories may be of any type (different from each other), have any possible storage structure and, if required, being managed by any database management system.
  • the memory may also store computer program code such as software applications (for example, for one or more of the units/algorithms) or operating systems, information, data, content, or the like for the processor to perform steps associated with operation of the apparatus in accordance with examples/embodiments.
  • the memory or part of it, may be, for example, random access memory, a hard drive, or other fixed data memory or storage device implemented within the processor/apparatus or external to the processor/apparatus in which case it can be communicatively coupled to the processor/network node via various means as is known in the art.
  • An example of an external memory includes a removable memory detachably connected to the apparatus.
  • the apparatus configured to provide the network apparatus may generally comprise different interface units, such as one or more receiving units and one or more sending units.
  • the receiving unit and the transmitting unit each provides an interface in an apparatus, the interface including a transmitter and/or a receiver or any other means for receiving and/or transmitting information, and performing necessary functions so that the information, etc. can be received and/or sent.
  • the receiving and sending units may comprise a set of antennas, the number of which is not limited to any particular number.
  • the apparatus may comprise other units. It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways.
  • the invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Lorsqu'un besoin de double connectivité pour un appareil utilisateur desservi par au moins une cellule avec une seule connexion est détecté, un nœud de réseau commandant cette cellule sélectionne un second nœud de réseau qui commande au moins une seconde cellule afin qu'il devienne le nœud de réseau maître de la double connectivité, et il envoie une demande au second nœud de réseau pour lui demander de fonctionner en tant que nœud de réseau maître de la double connectivité.
PCT/EP2014/068372 2014-08-29 2014-08-29 Établissement d'une double connectivité Ceased WO2016029962A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/068372 WO2016029962A1 (fr) 2014-08-29 2014-08-29 Établissement d'une double connectivité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/068372 WO2016029962A1 (fr) 2014-08-29 2014-08-29 Établissement d'une double connectivité

Publications (1)

Publication Number Publication Date
WO2016029962A1 true WO2016029962A1 (fr) 2016-03-03

Family

ID=51485587

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2014/068372 Ceased WO2016029962A1 (fr) 2014-08-29 2014-08-29 Établissement d'une double connectivité

Country Status (1)

Country Link
WO (1) WO2016029962A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018036673A1 (fr) * 2016-08-22 2018-03-01 Nokia Solutions And Networks Oy Procédé et appareil destinés à mettre en œuvre une commutation efficace sur un porteur divisé
CN109315008A (zh) * 2016-06-24 2019-02-05 华为技术有限公司 多连接通信方法和设备
EP3944722A1 (fr) * 2016-05-26 2022-01-26 NEC Corporation Système de communication, dispositif de commande, terminal de communication, dispositif de communication et procédé de communication
WO2023065095A1 (fr) * 2021-10-18 2023-04-27 北京小米移动软件有限公司 Procédé de communication et appareil de communication dans de multiples liaisons

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2408230A1 (fr) * 2009-04-22 2012-01-18 ZTE Corporation Procédé de transmission de messages de groupe coordonné d'émission/réception multipoint coordonnées et n ud b évolué
WO2013104269A1 (fr) * 2012-01-10 2013-07-18 华为技术有限公司 Procédé pour le transfert intercellulaire d'un enb, procédé pour l'établissement d'une interface x2, et enb, équipement d'utilisateur et système correspondants
WO2013117009A1 (fr) * 2012-02-10 2013-08-15 Nokia Corporation Procédé et appareil pour une meilleure commande des connexions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2408230A1 (fr) * 2009-04-22 2012-01-18 ZTE Corporation Procédé de transmission de messages de groupe coordonné d'émission/réception multipoint coordonnées et n ud b évolué
WO2013104269A1 (fr) * 2012-01-10 2013-07-18 华为技术有限公司 Procédé pour le transfert intercellulaire d'un enb, procédé pour l'établissement d'une interface x2, et enb, équipement d'utilisateur et système correspondants
EP2790443A1 (fr) * 2012-01-10 2014-10-15 Huawei Technologies Co., Ltd. Procédé pour le transfert intercellulaire d'un enb, procédé pour l'établissement d'une interface x2, et enb, équipement d'utilisateur et système correspondants
WO2013117009A1 (fr) * 2012-02-10 2013-08-15 Nokia Corporation Procédé et appareil pour une meilleure commande des connexions

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3944722A1 (fr) * 2016-05-26 2022-01-26 NEC Corporation Système de communication, dispositif de commande, terminal de communication, dispositif de communication et procédé de communication
US11510265B2 (en) 2016-05-26 2022-11-22 Nec Corporation Communication system, control device, communication terminal, communication device, and communication method
US11924900B2 (en) 2016-05-26 2024-03-05 Nec Corporation Communication system, control device, communication terminal, communication device, and communication method
EP4590038A3 (fr) * 2016-05-26 2025-09-03 NEC Corporation Système de communication, dispositif de commande, terminal de communication, dispositif de communication et procédé de communication
CN109315008A (zh) * 2016-06-24 2019-02-05 华为技术有限公司 多连接通信方法和设备
US10798766B2 (en) 2016-06-24 2020-10-06 Huawei Technologies Co., Ltd. Multi-connectivity communication method and device
US11412563B2 (en) 2016-06-24 2022-08-09 Huawei Technologies Co., Ltd. Multi-connectivity communication method and device
WO2018036673A1 (fr) * 2016-08-22 2018-03-01 Nokia Solutions And Networks Oy Procédé et appareil destinés à mettre en œuvre une commutation efficace sur un porteur divisé
US11057167B2 (en) 2016-08-22 2021-07-06 Nokia Solutions And Networks Oy Method and apparatus for implementing efficient switching on a split bearer
US11695520B2 (en) 2016-08-22 2023-07-04 Nokia Solutions And Networks Oy Method and apparatus for implementing efficient switching on a split bearer
WO2023065095A1 (fr) * 2021-10-18 2023-04-27 北京小米移动软件有限公司 Procédé de communication et appareil de communication dans de multiples liaisons

Similar Documents

Publication Publication Date Title
CN113615253B (zh) 到潜在目标节点的有条件切换执行概率信息
US12336047B2 (en) Dual active protocol stack operation for handover and PSCell change
US10554763B2 (en) Method and apparatus for virtual base station migration in BBU pool
US9467912B2 (en) Method and apparatus for managing handovers
US12464464B2 (en) Managing a ue preferred configuration
US11412414B2 (en) Communication methods and communications apparatuses
US11490438B2 (en) Protocols and architectures for NR-NR dual connectivity (NR-DC)
CN109246770B (zh) 一种切换的方法、终端设备及网络设备
KR102219052B1 (ko) 통신 장치 및 통신 방법
CN111200850A (zh) 一种通信方法及装置
TWI755581B (zh) 附加上行鏈路故障處理
JP6325119B2 (ja) ユーザ機器履歴情報を提供することによって、ユーザ機器とＭｅＮＢとＳｅＮＢとの間にデュアルコネクティビティを確立するための方法および装置
US20210259038A1 (en) Communication system
WO2016119210A1 (fr) Connectivité double et transfert intercellulaire
US20210410144A1 (en) MAC Reset Procedures
US20170374578A1 (en) Mobility control in dual connectivity operation mode
US20210306946A1 (en) Secondary network node selection for dual connectivity
WO2016029962A1 (fr) Établissement d'une double connectivité
CN114009076A (zh) 一种通信方法、设备及系统
JP7669484B2 (ja) Ｍｒｏ臨界シーンの判定方法、装置及び機器
EP4312452B1 (fr) Gestion de préparations de transfert conditionnel dans des scénarios de défaillance
WO2020029167A1 (fr) Procédés, appareil et systèmes de gestion d'un cache local associé à un noeud de communication sans fil
US20210329509A1 (en) Nodes and method for handling message delivery to a ue
US20250175871A1 (en) Communication method and apparatus
WO2024235556A1 (fr) Indication de type d'ajout de pscell conditionnelle en tant que partie d'activation sélective

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14758842

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14758842

Country of ref document: EP

Kind code of ref document: A1