Patent Application
20240349129
The subject matter disclosed herein relates generally to wireless communications and more particularly relates to group-based mobility configuration.
In wireless networks, group-based mobility—changing a primary cell of a group of user equipment devices (“UEs”) simultaneously—may be useful for various scenarios, e.g., non-terrestrial network (“NTN”) feeder link switching, offloading a large number of UEs connected with one cell to a neighboring cell in order to turn off a network node for power saving, a change of a serving cell for a mobile integrated access backhaul (“IAB”)-node, and/or the like.
Disclosed are solutions for group-based mobility configuration. The solutions may be implemented by apparatus, systems, methods, or computer program products.
In one embodiment, a first apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to receive a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor is configured to cause the apparatus to receive a group handover command message based on the first identifier. In one embodiment, the processor is configured to cause the apparatus to perform handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, a first method receives a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the first method receives a group handover command message based on the first identifier. In one embodiment, the first method performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, a second apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to transmit, to a UE apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor is configured to cause the apparatus to generate a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the processor is configured to cause the apparatus to transmit, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, a second method transmits, to a UE apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the second method generates a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the second method transmits, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of” includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
Generally, the present disclosure describes systems, methods, and apparatuses for group-based mobility configuration. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.
Group-based mobility (e.g., changing a primary cell of a group of UEs simultaneously) may be useful for various scenarios, e.g., non-terrestrial network (“NTN”) feeder link switching, offloading a large number of UEs connected with one cell to a neighboring cell in order to turn off a network node for power saving, and a change of a serving cell for a mobile IAB-node.
For example, in NTN, it may be necessary to switch a feeder link of a satellite from one NTN gateway (“GW”) to another. This may be due to, e.g., maintenance, traffic offloading, or the satellite moving out of visibility with respect to the current NTN GW. The switchover should be performed without causing service disruption to served UEs. In one NTN architecture, gNBs are on the ground (terrestrial), thus the feeder link switch means a switch from a gNB1 to a gNB2. That is, all or a majority UEs served by the satellite/gNB1 may have to perform handover in short duration to gNB2. Similar to NTN feeder link switching, a mobile IAB-node may have to switch from one parent IAB-node or one IAB-donor to another and, accordingly, may have to change an IAB-DU cell configuration (e.g., cell identity, SSB beams). In such a scenario, all UEs and/or a child IAB-nodes served by the IAB-DU cell may have to perform handover in short time.
In another example, when a network node provides overlapped coverage with another network node and/or traffic load is light, it may be beneficial to turn off or put in a dormant state the network node for network power saving. Before turning off a cell, a number of UEs served by the cell may need to be moved by handover to another cell in short time.
In Rel-15/16 NR, an RRC-connected UE can receive a conditional handover (“CHO”) command for robust handover. One drawback of CHO is that a network entity may have to reserve one or more physical random access channel (“PRACH”) resources for each UE until handover is triggered by a UE. If a significant percentage of UEs in a source cell are configured with CHO to a particular target cell, it may be difficult to efficiently utilize PRACH resources and may increase PRACH collisions for idle UEs in the target cell. Further, an RRC signaling overhead for handover commands is expected to be high with individual delivery of handover commands to a large number of UEs.
This disclosure presents detailed signaling methods to enable group-based serving cell change. In some embodiments, the proposed group-based mobility configuration allows a large number of UEs to perform handover with reduced signaling overhead. Different handover initiation time for different UEs in a group can solve a potential PRACH capacity issue in a target cell.
In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a New Generation Radio Access Network (“NG-RAN”), implementing NR RAT and/or 3GPP Long-Term Evolution (“LTE”) RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123. Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 130.
In some embodiments, the remote units 105 communicate with an application server via a network connection with the mobile core network 130. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Internet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 130 via the RAN 120. The mobile core network 130 then relays traffic between the remote unit 105 and the application server (e.g., the content server 151 in the packet data network 150) using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 131.
In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 130 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150, e.g., representative of the Internet. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
In the context of a 5G system (“5GS”), the term “PDU Session” a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 131. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QOS Identifier (“5QI”).
In the context of a 4G/LTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., a tunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 130. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).
The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 130 via the RAN 120.
The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR-U operation, the base unit 121 and the remote unit 105 communicate over unlicensed radio spectrum.
In one embodiment, the mobile core network 130 is a 5GC or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
The mobile core network 130 includes several network functions (“NFs”). As depicted, the mobile core network 130 includes at least one UPF 131. The mobile core network 130 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 133 that serves the RAN 120, a Session Management Function (“SMF”) 135, a Network Exposure Function (“NEF”), a Policy Control Function (“PCF”) 137, a Unified Data Management function (“UDM”) and a User Data Repository (“UDR”) 139.
The UPF(s) 131 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (“DN”), in the 5G architecture. The AMF 133 is responsible for termination of NAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 135 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DL data notification, and traffic steering configuration for UPF for proper traffic routing.
The NEF is responsible for making network data and resources easily accessible to customers and network partners. Service providers may activate new capabilities and expose them through APIs. These APIs allow third-party authorized applications to monitor and configure the network's behavior for a number of different subscribers (i.e., connected devices with different applications). The PCF 137 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR.
The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and can be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 139.
In various embodiments, the mobile core network 130 may also include an Authentication Server Function (“AUSF”) (which acts as an authentication server), a Network Repository Function (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), or other NFs defined for the 5GC. In certain embodiments, the mobile core network 130 may include an authentication, authorization, and accounting (“AAA”) server.
In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 130 optimized for a certain traffic type or communication service. A network instance may be identified by a single-network slice selection assistance information (“S-NSSAI,”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”).
Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 135 and UPF 131. In some embodiments, the different network slices may share some common network functions, such as the AMF 133. The different network slices are not shown in
Although specific numbers and types of network functions are depicted in
While
In the following descriptions, the term “gNB” is used for the base station but it is replaceable by any other radio access node, e.g., RAN node, eNB, Base Station (“BS”), Access Point (“AP”), NR, etc. Further the operations are described mainly in the context of 5G NR. However, the proposed solutions/methods are also equally applicable to other mobile communication systems supporting CSI enhancements for higher frequencies.
The AS layer (also referred to as “AS protocol stack”) for the User Plane protocol stack 201 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer for the Control Plane protocol stack 203 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-2 (“L2”) is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-3 (“L3”) includes the RRC sublayer 245 and the NAS layer 250 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer and/or PDU Layer (not depicted) for the user plane. L1 and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”
The physical layer 220 offers transport channels to the MAC sublayer 225. The physical layer 220 may perform a Clear Channel Assessment and/or Listen-Before-Talk (“CCA/LBT”) procedure using energy detection thresholds, as described herein. In certain embodiments, the physical layer 220 may send a notification of UL Listen-Before-Talk (“LBT”) failure to a MAC entity at the MAC sublayer 225. The MAC sublayer 225 offers logical channels to the RLC sublayer 230. The RLC sublayer 230 offers RLC channels to the PDCP sublayer 235. The PDCP sublayer 235 offers radio bearers to the SDAP sublayer 240 and/or RRC layer 245. The SDAP sublayer 240 offers QOS flows to the core network (e.g., 5GC). The RRC layer 245 provides for the addition, modification, and release of Carrier Aggregation and/or Dual Connectivity. The RRC layer 245 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”).
The NAS layer 250 is between the UE 205 and the 5GC 215. NAS messages are passed transparently through the RAN. The NAS layer 250 is used to manage the establishment of communication sessions and for maintaining continuous communications with the UE 205 as it moves between different cells of the RAN. In contrast, the AS layer is between the UE 205 and the RAN (e.g., RAN node 210) and carries information over the wireless portion of the network.
As background, in NR, a handover command is provided by a gNB using the RRCReconfiguration message including the parameter reconfigurationWithSync. Radio resource control (“RRC”) reconfiguration procedure, including the parameter reconfigurationWithSync (e.g., change of special cell (“SpCell”) of master cell group (“MCG”) or secondary cell group (“SCG”)) in Rel-16 NR is described as follows:
Regarding reception of an RRCReconfiguration by the UE, e.g. as described in TS 38.331, the UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO or CPC):
It is noted that the UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, e.g., the broadcast and unicast beams are quasi co-located.
It is further noted that the UE sets the content of UEAssistanceInformation according to latest configuration (i.e., the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message might not be the same as the content of the previous UEAssistanceInformation message.
Regarding timer T304 expiry (Reconfiguration with sync failure), the UE shall:
It is noted that in the context above, “the UE configuration” includes state variables and parameters of each radio bearer.
It is noted that the term ‘handover failure’ has been used to refer to ‘reconfiguration with sync failure’.
Regarding full configuration, the UE shall:
Regarding VarConditionalReconfig, the UE variable VarConditionalReconfig includes the accumulated configuration of the conditional handover or conditional PSCell change configurations including the pointers to conditional handover or conditional PSCell change execution condition (associated measId(s)) and the stored target candidate SpCell RRCReconfiguration.
Regarding CondReconfigToAddModList, the IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond and condRRCReconfig.
As briefly discussed above, the subject matter herein presents detailed signaling methods to enable group-based serving cell change. Regarding group handover configuration and command, throughout this document, a handover refers to a change of a special cell (SpCell) (e.g., PCell of MCG or PSCell of SCG).
In one embodiment, a UE receives a group handover configuration e.g., in an RRCReconfiguration message, that includes information of a group identity and a UE index (or UE identity) within a group. Additionally, the UE may receive a physical downlink control channel (“PDCCH”) monitoring configuration (e.g., a search space and a corresponding control resource set (“CORESET”) and a downlink control information (“DCI”) format) associated with a group common PDCCH for a group handover.
For example, the UE receives information of a first RNTI (e.g., C-RNTI, MCS-C-RNTI) used for unicast communications in one or more serving cells and information of a second RNTI (e.g., Group (G)-RNTI) and the UE index/identity associated with a group handover command. The UE further receives a group handover command based on the configured group identity (e.g., G-RNTI) and determines whether to perform a handover to a target cell based on the received group handover command. For example, the UE determines to perform a handover if a handover parameter set addressed to the UE (e.g., using the UE index/identity) is included in the group handover command. In another example, the UE determines to perform a handover if a handover parameter set addressed to the UE is included in a conditional group handover command and if one or more conditions (e.g., measurements, timing, or the like) configured for a conditional handover is satisfied. In one embodiment, in response to determining to perform the handover to the target cell, the UE identifies parameters associated with the target cell, e.g., a new UE identity (e.g., a new C-RNTI used in the target cell), a dedicated RACH resource(s), a first active DL BWP, a first active UL BWP, and/or the like), from the received group handover command based on the UE index/identity within the group.
In one implementation, a network entity determines a group of UEs for a group mobility configuration based on UE locations, UE geometry, spatial coverage, supported services/slices, and/or the like. For example, the network entity may send a group handover command to the group of UEs since the source cell does not support a specific slice/service or does not support a specific slice/service at the time of handover. In another example, the network entity may send a group handover command to a group of UEs to move to a target cell based on the supported services/slices of the target cell and the services/slices requirement of the group of UEs, e.g., services/slices requirement of the UEs are satisfied by the target cell.
In one implementation, if a UE initiates a handover to a target cell upon receiving a group handover command, the UE may initiate a random access procedure unless a handover with skipping the random access procedure and reusing one of maintained uplink timing information (e.g., timing advance values) is indicated. Upon successful completion of the random access procedure (within a configured time duration, e.g., completion before expiration of the T304A timer), in one embodiment, the UE may apply group-specific configured measurement and/or radio resource configuration (e.g., measurement gap, group-specific BWP configurations). Further, in one embodiment, the UE may acquire SIB1 if an active DL BWP of a target SpCell of an MCG configured for the UE (e.g., firstActiveDownlinkBWP-Id configured for the UE) has a common search space configured by searchSpaceSIBI. The UE may remove all the entries within VarConditionalReconfig if receiving a conditional group handover command (e.g., groupConditionalReconfiguration included in GroupRRCReconfiguration message).
In one example, a group handover command is delivered via a group-common PDCCH, which may carry scheduling information of a physical downlink shared channel (“PDSCH”), and the scheduled PDSCH, where the group-common PDCCH includes cyclic redundancy check (“CRC”) bits scrambled with a group identity (e.g., G-RNTI). As shown in Example 1 below, the corresponding PDSCH carries a group RRC reconfiguration message (e.g., a GroupRRCReconfiguration message) that includes a GroupBasedCellGroupConfig IE for an MCG. If the GroupBasedCellGroupConfig IE for the MCG includes an indication of SpCell reconfiguration with synchronization (e.g. the parameter groupSpCellConfig with the parameter groupReconfigurationWithSync), the UE further checks whether the parameter groupReconfigurationWithSync includes handover related resources (e.g., a cell-ID, a new RNTI, a dedicated RACH resource, first active DL/UL BWPs spatial information (e.g., TCI-state, source reference signal(s) (e.g., SSB), quasi-collocation relationship information (e.g., QCL type parameter(s)) associated with the first active BWPs, and/or the like) for the UE, e.g. the parameter mobilityConfigList intended for the UE. The UE, in one embodiment, maintains a MAC entity and a set of logical channels with associated RLC entities of a current configuration. The UE may release all configured SCells in the current configuration to ease the admission control of a target gNB.
In one example, a UE determines when to start monitoring a group-common PDCCH to receive a group handover command based on broadcasted timing information e.g., based on when a cell is going to stop serving the area or based on an indicated time duration [t1, t2], which may be determined by the network e.g., based on trajectory of satellites in NTN, mobile-IAB node, and/or the like. This trajectory information may be computed based on at least one piece of ephemeris information, which may be actual or nominal or a combination thereof and determined by a specification, configuration, or implementation. In addition, the determining may be additionally based on the location of GWs or other terrestrial or non-terrestrial nodes involved in a handover. In the case that the node(s) are mobile, their location may be computed based on a trajectory obtained by actual or nominal ephemeris of the node(s) or a combination thereof. In another example, a UE receives a search space set activation/deactivation indication (e.g., via MAC CE or DCI) for a search space set associated with a group-common PDCCH of a group handover command, and initiates/stops monitoring the group-common PDCCH of the group handover command based on the received search space set activation/deactivation indication.
In one example, a UE considers the source cell in response to receiving the group handover command as barred, since the source cell will not be available any further e.g., due to a network node being turned off. The UE may not, after execution of the handover triggered by the group handover command, attempt to re-establish RRC connection to this source cell. For cases when groups of UEs are handed over to a different cell for the purpose of e.g., network energy saving, UEs shall not reselect this source cell or try to re-establish to this source cell in case of handover failure. In one example, source cell barring is explicitly indicated by one information element (“IE”) in the group handover message, e.g., whether UEs shall consider the source cell as barred after the handover, e.g., the UE shall not return to source cell. In one implementation, the UE does not expect to receive a group handover command or does not expect to receive a group handover command with an indication of source cell barring, if the UE is configured with DAPS operation.
In one example involving GroupRRCReconfiguration message and GroupBasedCellGroupConfig IE, the GroupRRCReconfiguration message is the command to modify an RRC connection for a group of UEs. It may convey information for group-specific measurement configuration, group-based mobility control, and group-specific radio resource configuration (excluding MAC configuration and radio bearers).
In one implementation, a UE receives a plurality of T304A timer values (see Table 3 below) in a group handover command message and selects a T304A timer value intended for the UE from the plurality of T304A timer values. For example, a UE-specific T304A timer value is included in the parameter mobilityConfigList intended for the UE. Further, the UE may receive a UE-specific T304A timer starting time offset (e.g., the UE starts the T304A timer and initiates the handover when the indicated starting time offset elapsing after reception of GroupRRCReconfiguration message including groupReconfigurationWithSync).
In one embodiment, different handover initiation times for different UEs in the group can solve a potential PRACH capacity issue in a target cell due to handover of a large number of UEs. In one example, a time range, e.g., maximum time, (e.g., common to the group of UEs) for executing the handover is signaled within the group handover command. Individual UEs may determine a random value within the signaled time range (e.g., to determine the UE-specific T304A timer starting time offset) to start the handover execution phase. In some realizations, the timer plus UE-specific offset may or may not take into account different propagation times associated with different UEs. If the range of propagation times is large or highly variable, the UE may be required to take the variable propagation delay into account when determining the UE-specific RACH timing.
In another implementation, a UE receives a reference T304A timer value and applies an offset value to the reference T304A timer value. The offset value may be determined based on a UE index (e.g., UE-IndexforGroupMobility) within a UE group for a group handover command from a predefined or configured plurality of offset values.
In one implementation, a UE keeps its MAC configuration, RLC bearer configuration, logical channel configurations, DRB configurations, and SRB configurations upon receiving a GroupRRCReconfiguration message. If the parameter ‘fullConfig’ is included in the GroupRRCReconfiguration message, in one embodiment, the UE resets its SRB configurations to default SRB configurations but maintains the current DRB configurations.
Example—Full configuration procedure in a group handover. The UE shall:
In an example shown in
Further, in one embodiment, the source gNB 503 sends (see messaging 508) a search space activation command to the UE 501 so that the UE 501 can start monitoring (see block 510) the search space related to receiving the group handover command. When the UE 501 detects a PDCCH with CRC scrambled with the G-RNTI and further receives a PDSCH carrying an GroupRRCReconfiguration message (see messaging 512), the UE 501 determines (see block 514) whether to initiate the handover and identifies handover related parameters (e.g., a new C-RNTI for a target cell) based on the decoded GroupRRCReconfiguration message. After switching (see block 516) to the target cell of the target gNB 505 (e.g., with successful completion of a random access procedure with the target cell), the UE 501 sends (see messaging 518) a RRCReconfigurationComplete message to the target gNB 505.
As depicted, the transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, the transceiver 625 communicates with one or more base units 121. Additionally, the transceiver 625 may support at least one network interface 640 and/or application interface 645. The application interface(s) 645 may support one or more APIs. The network interface(s) 640 may support 3GPP reference points, such as Uu and PC5. Other network interfaces 640 may be supported, as understood by one of ordinary skill in the art.
The processor 605, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 605 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 605 executes instructions stored in the memory 610 to perform the methods and routines described herein. The processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625. In certain embodiments, the processor 605 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
The memory 610, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 610 includes volatile computer storage media. For example, the memory 610 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 610 includes non-volatile computer storage media. For example, the memory 610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 610 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 610 stores data related to CSI enhancements for higher frequencies. For example, the memory 610 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 600, and one or more software applications.
The input device 615, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 615 may be integrated with the output device 620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 615 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 615 includes two or more different devices, such as a keyboard and a touch panel.
The output device 620, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 620 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 600, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 620 includes one or more speakers for producing sound. For example, the output device 620 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 620 may be integrated with the input device 615. For example, the input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 620 may be located near the input device 615.
The transceiver 625 includes at least transmitter 630 and at least one receiver 635. The transceiver 625 may be used to provide UL communication signals to a base unit 121 and to receive DL communication signals from the base unit 121, as described herein. Similarly, the transceiver 625 may be used to transmit and receive SL signals (e.g., V2X communication), as described herein. Although only one transmitter 630 and one receiver 635 are illustrated, the user equipment apparatus 600 may have any suitable number of transmitters 630 and receivers 635. Further, the transmitter(s) 630 and the receiver(s) 635 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 625 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 640.
In various embodiments, one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 640 or other hardware components/circuits may be integrated with any number of transmitters 630 and/or receivers 635 into a single chip. In such embodiment, the transmitters 630 and receivers 635 may be logically configured as a transceiver 625 that uses one more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or in a multi-chip module.
In one embodiment, the processor 605 is configured to receive, via the transceiver 625, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor 605 is configured to receive, via the transceiver 625, a group handover command message based on the first identifier. In one embodiment, the processor 605 is configured to perform handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, the first identifier is assigned to the group of UE apparatuses and the second identifier corresponds to a UE index of the UE apparatus within the group of UE apparatuses.
In one embodiment, the handover information for the UE apparatus comprises a handover parameter set in the group handover command message, the handover parameter set addressed to the UE apparatus based on the second identifier.
In one embodiment, the handover parameter set comprises at least one selected from the group comprising a new C-RNTI for a target cell, at least one dedicated PRACH resource, a first active DL BWP, a first active UL BWP, and a timer value.
In one embodiment, the processor 605 is configured to determine when to initiate the handover in response to determining to perform the handover based on a determined initiation time.
In one embodiment, the processor 605 is configured to receive, via the transceiver 625, a PDCCH monitoring configuration for the group handover command message and detect a PDCCH associated with the PDCCH monitoring configuration based on the first identity, wherein the PDCCH comprises a group-common PDCCH that schedules a PDSCH carrying the group handover command
In one embodiment, the processor 605 is configured to receive, via the transceiver 625, an indication of whether a source cell is barred after the handover.
In one embodiment, the handover comprises at least one selected from the group comprising a change of a primary cell of a master cell group and a change of a primary secondary cell of a secondary cell group.
In one embodiment, the processor 605 is configured to release current dedicated radio configurations except for a MCG C-RNTI, AS security configurations associated with a master key, a MAC configuration, a RLC bearer configuration, and one or more logical channel configurations in response to the group handover command message comprising an indication of a full configuration.
As depicted, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, the transceiver 725 communicates with one or more remote units 105. Additionally, the transceiver 725 may support at least one network interface 740 and/or application interface 745. The application interface(s) 745 may support one or more APIs. The network interface(s) 740 may support 3GPP reference points, such as Uu, N1, N2, N3, N5, N6 and/or N7 interfaces. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.
When implementing an NEF, the network interface(s) 740 may include an interface for communicating with an application function (i.e., N5) and with at least one network function (e.g., UDR, SFC function, UPF) in a mobile communication network, such as the mobile core network 130.
The processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, a DSP, a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725. In certain embodiments, the processor 705 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function. In various embodiments, the processor 705 controls the network apparatus 700 to implement the above described network entity behaviors (e.g., of the gNB) for group-based mobility configuration.
The memory 710, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 710 includes volatile computer storage media. For example, the memory 710 may include a RAM, including DRAM, SDRAM, and/or SRAM. In some embodiments, the memory 710 includes non-volatile computer storage media. For example, the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 710 stores data relating to CSI enhancements for higher frequencies. For example, the memory 710 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 710 also stores program code and related data, such as an OS or other controller algorithms operating on the network apparatus 700, and one or more software applications.
The input device 715, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touch panel.
The output device 720, in one embodiment, may include any known electronically controllable display or display device. The output device 720 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 720 includes an electronic display capable of outputting visual data to a user. Further, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 720 includes one or more speakers for producing sound. For example, the output device 720 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 720 may be integrated with the input device 715. For example, the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, all, or portions of the output device 720 may be located near the input device 715.
As discussed above, the transceiver 725 may communicate with one or more remote units and/or with one or more interworking functions that provide access to one or more PLMNs. The transceiver 725 may also communicate with one or more network functions (e.g., in the mobile core network 80). The transceiver 725 operates under the control of the processor 705 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 705 may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages.
The transceiver 725 may include one or more transmitters 730 and one or more receivers 735. In certain embodiments, the one or more transmitters 730 and/or the one or more receivers 735 may share transceiver hardware and/or circuitry. For example, the one or more transmitters 730 and/or the one or more receivers 735 may share antenna(s), antenna tuner(s), amplifier(s), filter(s), oscillator(s), mixer(s), modulator/demodulator(s), power supply, and the like. In one embodiment, the transceiver 725 implements multiple logical transceivers using different communication protocols or protocol stacks, while using common physical hardware.
In one embodiment, the processor 700 is configured to transmit, via the transceiver 725, to a UE apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor 705 is configured to generate a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the processor 705 is configured to transmit, via the transceiver 725, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, the method 800 begins and receives 805 a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the method 800 receives 810 a group handover command message based on the first identifier. In one embodiment, the method 800 performs 815 handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier, and the method 800 ends.
In one embodiment, the method 900 begins and transmits 905, to a user equipment (“UE”) apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the method 900 generates 910 a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the method 900 transmits 915, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier, and the method 900 ends.
A first apparatus is disclosed for group-based mobility configuration. The first apparatus may include a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 600. In some embodiments, the first apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the first apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to receive a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor is configured to cause the apparatus to receive a group handover command message based on the first identifier. In one embodiment, the processor is configured to cause the apparatus to perform handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, the first identifier is assigned to the group of UE apparatuses and the second identifier corresponds to a UE index of the UE apparatus within the group of UE apparatuses.
In one embodiment, the handover information for the UE apparatus comprises a handover parameter set in the group handover command message, the handover parameter set addressed to the UE apparatus based on the second identifier.
In one embodiment, the handover parameter set comprises at least one selected from the group comprising a new C-RNTI for a target cell, at least one dedicated PRACH resource, a first active DL BWP, a first active UL BWP, and a timer value.
In one embodiment, the processor is configured to cause the apparatus to determine when to initiate the handover in response to determining to perform the handover based on a determined initiation time.
In one embodiment, the processor is configured to cause the apparatus to receive a PDCCH monitoring configuration for the group handover command message and detect a PDCCH associated with the PDCCH monitoring configuration based on the first identity, wherein the PDCCH comprises a group-common PDCCH that schedules a PDSCH carrying the group handover command
In one embodiment, the processor is configured to cause the apparatus to receive an indication of whether a source cell is barred after the handover.
In one embodiment, the handover comprises at least one selected from the group comprising a change of a primary cell of a master cell group and a change of a primary secondary cell of a secondary cell group.
In one embodiment, the processor is configured to cause the apparatus to release current dedicated radio configurations except for a MCG C-RNTI, AS security configurations associated with a master key, a MAC configuration, a RLC bearer configuration, and one or more logical channel configurations in response to the group handover command message comprising an indication of a full configuration.
A first method is disclosed for group-based mobility configuration. The first method may be performed by a UE as described herein, for example, the remote unit 105 and/or the user equipment apparatus 600. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the first method receives a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the first method receives a group handover command message based on the first identifier. In one embodiment, the first method performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
In one embodiment, the first identifier is assigned to the group of UE apparatuses and the second identifier corresponds to a UE index of the UE apparatus within the group of UE apparatuses.
In one embodiment, the handover information for the UE apparatus comprises a handover parameter set in the group handover command message, the handover parameter set addressed to the UE apparatus based on the second identifier.
In one embodiment, the handover parameter set comprises at least one selected from the group comprising a new C-RNTI for a target cell, at least one dedicated PRACH resource, a first active DL BWP, a first active UL BWP, and a timer value.
In one embodiment, the first method determines when to initiate the handover in response to determining to perform the handover based on a determined initiation time.
In one embodiment, the first method receives a PDCCH monitoring configuration for the group handover command message and detects a PDCCH associated with the PDCCH monitoring configuration based on the first identity, wherein the PDCCH comprises a group-common PDCCH that schedules a PDSCH carrying the group handover command message.
In one embodiment, the first method receives an indication of whether a source cell is barred after the handover.
In one embodiment, the handover comprises at least one selected from the group comprising a change of a primary cell of a master cell group and a change of a primary secondary cell of a secondary cell group.
In one embodiment, the first method releases current dedicated radio configurations except for a MCG C-RNTI, AS security configurations associated with a master key, a MAC configuration, a RLC bearer configuration, and one or more logical channel configurations in response to the group handover command message comprising an indication of a full configuration.
A second apparatus is disclosed for group-based mobility configuration. The second apparatus may include a network device as described herein, for example, the gNB, the base unit 121, and/or the network equipment apparatus 700. In some embodiments, the second apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the second apparatus includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the apparatus to transmit, to a UE apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the processor is configured to cause the apparatus to generate a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the processor is configured to cause the apparatus to transmit, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
A second method is disclosed for group-based mobility configuration. The second method may be performed by a network device as described herein, for example, the gNB, the base unit 121, and/or the network equipment apparatus 700. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
In one embodiment, the second method transmits, to a UE apparatus, a group handover configuration comprising a first identifier and a second identifier, the first identifier for a group of UE apparatuses and the second identifier for the UE apparatus within the group of UE apparatuses. In one embodiment, the second method generates a group handover command message based on the first identifier, the group handover command message comprising handover information for the UE apparatus indicated based on the second identifier. In one embodiment, the second method transmits, to the UE apparatus, the group handover command message based on the first identifier, wherein the UE apparatus performs handover of the UE apparatus to a target cell in response to determining that the group handover command comprises handover information for the UE apparatus based on the second identifier.
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of U.S. Provisional Patent Application No. 63/225,265, entitled “GROUP BASED MOBILITY CONFIGURATION” and filed on Jul. 23, 2021, for Hyejung Jung et al., which is incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2022/056812 | 7/22/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63225265 | Jul 2021 | US |
