Patent Application
20230076746
Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for New Radio (NR) wireless networks. These TSs describe aspects related to user plane and control plane signaling over the networks.
The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, and techniques in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A/B” and “A or B” mean (A), (B), or (A and B).
The following is a glossary of terms that may be used in this disclosure.
The term “circuitry” as used herein refers to, is part of, or includes hardware components that are configured to provide the described functionality. The hardware components may include an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), or a digital signal processor
(DSP). In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit
(CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.
The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, and network interface cards.
The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities that may allow a user to access network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, or workload units. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware elements. A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio-frequency carrier,” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.
The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, or a virtualized network function.
The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.
The network environment 100 may further include a core network (CN) 82. For example, the CN 112 may comprise a 5th Generation Core network (5GC). The CN 112 may be coupled to the base station(s) of the RAN 108 via a fiber optic or wireless backhaul. The CN 112 may provide functions for the UEs 104 via the RAN 108. These functions may include managing subscriber profile information, subscriber location, authentication of services, or switching functions for voice and data sessions.
The CN 112 may include an access and mobility management function (AMF) 116. The AMF 116 may be a control plane function that provides registration management, connection management, reachability management, and mobility management services. Registration management may allow a UE to register and deregister with the CN 112. Upon registration, a UE context may be created within the CN 112. The UE context may be a set of parameters that identify and characterize the UE. The UE context may include identity information, subscription information, capability information, access and mobility information, or protocol data unit (PDU) session information.
In some embodiments, the group of UEs 104 may be associated with one another to coordinate transmissions with the RAN 108. For example, the group of UEs 104, as a collective, may be capable of obtaining and using more network and platform resources than the capabilities of any individual UE. The network resources may include bandwidth, uplink transmit power, etc., while the platform resources may include processing resources, transmit/receive resources, antennas, etc. This may be beneficial in a number of end-user scenarios including, for example, uploading live video content to an application server.
In related art, grouped UE communications has been described as UE aggregation as provided in over-the-top products. These systems describe a sublayer above the packet data convergence protocol (PDCP) sublayer to allow aggregated UEs to receive communication in the coordinated mode without data disorder or duplication during the data splitting between the aggregated UEs. UE aggregation designed for specific use cases is associated with unnecessary complexity.
Grouped UE communication may be divided into user plane aspects and control plane aspects. While existing over-the-top UE aggregation may be sufficient to address user plane aspects, it may be inefficient in addressing control plane aspects. Thus, embodiments of the present disclosure address control plane aspects of group UE communication with modest standardization/implementation impacts.
In particular, some embodiments describe control-plane aspects that may be used to efficiently form and manage the group of UEs 104. The UE association described in various embodiments may be a control-plane only association, with the user plane being handled by an over-the-top UE aggregation solution. The control-plane aspects of this disclosure may be a part of a standardized UE aggregation solution.
The RAN 108 may have knowledge of the UEs associated with one another in the group 104. The associated UEs will move together and, therefore, experience similar radio propagation conditions. Further, in many instances, the assocaited UEs may use the same applications. The RAN 108 may use this association information to efficiently manage the group of UEs 104 by coordinating handover operations, measurements, and radio resource management decisions.
The embodiments of the present disclosure may be associated with a number of advantages with respect to a UE aggregation solution for both control/data plane. These advantages may include a significant reduction in complexity while maintaining control plane advantages, providing similar performance, and avoiding system architecture security issues.
At 216, the UE 204 may send a registration request to the AMF 212. The registration request may be a non-access stratum (NAS) registration request serves as a request to join a group of UEs. The AMF 212 may check subscription information corresponding to the UE 204 in order to determine whether the UE 204 is authorized to join the group of UEs. The subscription information may be stored in a subscription repository in the core network.
The UE 204 may identify the UEs with which it desires to be associated in a group in accordance with various options. A first option may be based solely on subscription information. For example, the subscription information may indicate that the UE 204 belongs to a group of UEs. With the first option, the UE 204 may only need to include an identifier of the UE (UE ID) (or other information that allows the AMF 212 to identify the UE 204) and an indication that the UE 204 wishes to join a group (without the group itself being explicitly identified) in the registration request transmitted at 2016. Upon receiving the registration request and identifying the UE 204, the AMF 212 may determine the group of UEs for which an association is requested based on the UE subscription information. While this option may be effective in some situations, it may also limit flexibility by requiring the UE to only be part of a single group.
In a second option, the UE 204 may include a UE ID (or other information that allows the AMF 212 to identify the UE 204) and a group ID. The group ID may be pre-provisioned in the UE 204 (for example, in a universal subscriber identity module) and may also be stored in the UE subscription information in the core network. When the UE 204 wishes to join a specific group, it may indicate the group that wants to join by transmitting the corresponding group ID to the AMF 212. The AMF 212 may check the UE subscription information to determine whether the UE 204 is authorized to join that group.
If the AMF 212 determines that the UE 204 is not authorized to join a group as requested by the registration request, the AMF 212 may send a registration reject message (not shown) to the UE 204.
If the AMF 212 determines that the UE 204 is authorized to join a group as requested by the registration request, the AMF 212 may send a UE context setup request to the base station 208 at 220 and may further send a registration accept message to the UE 204 at 224.
The UE context setup request may include an indication that the UE 204 has been authorized to join a group. The UE context setup request may also include a list of the UEs that belong to the group or a group ID that is being joined by the UE 204. This may provide the base station 208 with information as to which UEs are associated with one another. The base station 208 may use this information to coordinate network management of the UEs.
The registration accept message may provide the UE 204 with an indication that the request to join the group is authorized/accepted.
At 316 the UE 304 may send an RRC connection request to the base station 308. The RRC connection request may be a request to join a group. The RRC connection request may include a UE/group ID similar to that discussed above with respect to the registration request 216 of
The base station 308 may generate and transmit an initial UE message (or some other NG-AP signal) based on the RRC connection request to the AMF 312. The base station 308 may transmit the initial UE message to the AMF 312 to check whether the UE 304 is authorized to join the group. The initial UE message may include the UE/group ID included in the RRC connection request.
The AMF 312 may determine whether the UE 304 is authorized to join the group as discussed above with respect to
If the AMF 312 determines that the UE 304 is not authorized to join the group, the AMF 312 may send a reject message (not shown).
If the AMF 312 determines that the UE 304 is authorized to join the group, the AMF 312 may send an accept message 324. The accept message may include an indication of the authorization and a list of the associated UEs.
At 328, the base station 308 may transmit an RRC connection response message to the UE 304 to indicate that the UE 304 is authorized to join the group.
Knowledge of which UEs are associated with one another in a group may allow a network (for example, RAN 108) to efficiently manage network operations. For example, the base station may reduce measurement overhead by configuring measurements to one UE (or a subset of UEs) of a group. This may be based on the assumption that the UEs of a group are proximate to one another in a common location. Thus, measurements from a representative UE may be assumed to be applicable to the other UEs of the group. Communication parameters (for example, modulation and coding schemes (MCSs), beamforming coefficients, etc.) applicable to one UE of a group can be applied to all UEs of the group.
In some embodiments, a base station may manage group mobility based on grouping information. For example, the base station may handover all UEs of a group together. Alternatively, one UE of a group may be handed over ahead of other UEs of the group to ensure uninterrupted service during handover. The remaining UEs may be handed over after confirming the successful handover of the first UE of a group.
In some embodiments, a base station may keep one UE of the group connected to a macrocell, and connect the other UEs of the group to booster cells that may be handed over more frequently.
The operation flow/algorithmic structure 400 may include, at 404, identifying one or more UEs. The UEs identified at 404 may be those with which the executing UE wishes to associate in a group, for grouped communications with a network. In some embodiments, a UE may identify the UEs based on group configuration information stored at the UE. Additionally/alternatively, the UE may identify the UEs based on a discovery process.
The operation flow/algorithmic structure 400 may further include, at 408, generating a request to associate with the one or more UEs in a group. The request may be a NAS registration request or an RRC connection request. The request may be generated to include an identifier of the executing UE or a group ID. In some embodiments, the request may include identifiers corresponding to the UEs of the group with which the UE wishes to join.
The operation flow/algorithmic structure 400 may further include, at 412, transmitting the request to a network. If the request is a NAS registration request, the request may be sent to an AMF. If the request is an RRC connection request, the request may be sent to a base station.
The operation flow/algorithmic structure 500 may include, at 504, receiving a request for a UE to be associated with one or more other UEs in a group. In some embodiments, the request may be received from the UE itself, or from a base station that has received a request from the UE.
The operation flow/algorithmic structure 500 may further include, at 508, accessing UE subscription information. The UE subscription information may be stored in a subscription repository in the core network that is accessible to the AMF.
The operation flow/algorithmic structure 500 may further include determining whether the UE is authorized to join the group at 512. This may be done by referencing information in the UE subscription information.
If it is determined, at 512, that the UE is not authorized to join the group, the operation flow/algorithmic structure may advance to transmitting a reject message at 516.
If it is determined, at 512, that the UE is authorized to join the group, the operation flow/algorithmic structure may advance to transmitting an accept message at 520.
If the request is a NAS registration request, the accept message may be a registration accept message transmitted to the UE. The AMF may also send a UE context set up request that includes an indication of the authorization and a list of the associated UEs or group ID to a base station that provides service to the UE 204.
The operation flow/algorithmic structure 600 may include, at 604, receiving an indication that a plurality of UEs are associated with one another in a group. The indication may be from a UE context setup request or an accept message received from an AMF that includes an indication of the authorization of a UE joining a group, and a list of associated UEs.
The operation flow/algorithmic structure 600 may further include, at 608, performing a RAN management operation based on the indication. The RAN management operation may be a mobility operation or a measurement operation.
In some embodiments, the RAN management operation may include selecting a representative UE from the plurality of UEs of a group and configuring the representative UE with measurements to perform on behalf of the plurality of UEs of the group. The base station may receive, from the representative UE, measurements based on the measurement configurations. The base station may then determine configuration parameters for the plurality of UEs of the group based on the measurements. The base station may then transmit the configuration parameters to the plurality of UEs.
In some embodiments, the RAN management operation may include collectively handing over the plurality of UEs to a target base station. For example, all the UEs of the group may be handed over to the target base station at one time. The decision to handover the plurality of UEs may be based on feedback from one or more representative UEs.
In other embodiments, the RAN management operation may include handing over the plurality of UEs to one or more target base stations and a plurality of stages. For example, a first UE of the group may be handed over in a first stage. Upon determining that the first UE was successfully handed over, the base station may handover one or more additional UEs in a second stage.
In some embodiments, the RAN management operation may include connecting a first UE of the group to a special cell (for example, a PCell or a PSCell) and connecting one or more of the remaining UEs of the group to a secondary cell (for example, an SCell).
The UE 700 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage/current meters, or actuators), video surveillance/monitoring devices (for example, cameras or video cameras), wearable devices (for example, a smart watch), or Internet-of-things devices.
The UE 700 may include processors 704, RF interface circuitry 708, memory/storage 712, user interface 716, sensors 720, driver circuitry 722, power management integrated circuit (PMIC) 724, antenna structure 726, and battery 728. The components of the UE 700 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of
The components of the UE 700 may be coupled with various other components over one or more interconnects 732, which may represent any type of interface, input/output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
The processors 704 may include processor circuitry such as, for example, baseband processor circuitry (BB) 704A, central processor unit circuitry (CPU) 704B, and graphics processor unit circuitry (GPU) 704C. The processors 704 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory/storage 712 to cause the UE 700 to perform operations as described herein.
In some embodiments, the baseband processor circuitry 704A may access a communication protocol stack 736 in the memory/storage 712 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 704A may access the communication protocol stack 736 to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a NAS layer. In some embodiments, the PHY layer operations may additionally/alternatively be performed by the components of the RF interface circuitry 708.
The baseband processor circuitry 704A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
The memory/storage 712 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 736) that may be executed by one or more of the processors 704 to cause the UE 700 to perform various operations described herein. The memory/storage 712 include any type of volatile or non-volatile memory that may be distributed throughout the UE 700. In some embodiments, some of the memory/storage 712 may be located on the processors 704 themselves (for example, L1 and L2 cache), while other memory/storage 712 is external to the processors 704 but accessible thereto via a memory interface. The memory/storage 712 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.
The RF interface circuitry 708 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 700 to communicate with other devices over a radio access network. The RF interface circuitry 708 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.
In the receive path, the RFEM may receive a radiated signal from an air interface via antenna structure 726 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 704.
In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 726.
In various embodiments, the RF interface circuitry 708 may be configured to transmit/receive signals in a manner compatible with NR access technologies.
The antenna 726 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 726 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 726 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 726 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
The user interface circuitry 716 includes various input/output (I/O) devices designed to enable user interaction with the UE 700. The user interface 716 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (for example, binary status indicators such as light emitting diodes (LEDs) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 700.
The sensors 720 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, or subsystem. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers;
and microphones or other like audio capture devices.
The driver circuitry 722 may include software and hardware elements that operate to control particular devices that are embedded in the UE 700, attached to the UE 700, or otherwise communicatively coupled with the UE 700. The driver circuitry 722 may include individual drivers allowing other components to interact with or control various input/output (I/O) devices that may be present within, or connected to, the UE 700. For example, driver circuitry 722 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensor circuitry 720 and control and allow access to sensor circuitry 720, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
The PMIC 724 may manage power provided to various components of the UE 700. In particular, with respect to the processors 704, the PMIC 724 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
A battery 728 may power the UE 700, although in some examples the UE 700 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 728 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 728 may be a typical lead-acid automotive battery.
The network device 800 may include processors 804, RF interface circuitry 808 (if implemented as a base station), core network (CN) interface circuitry 812, memory/storage circuitry 816, and antenna structure 826 (if implemented as a base station).
The components of the network device 800 may be coupled with various other components over one or more interconnects 828.
The processors 804, RF interface circuitry 808, memory/storage circuitry 816 (including communication protocol stack 810), antenna structure 826, and interconnects 828 may be similar to like-named elements shown and described with respect to
The CN interface circuitry 812 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to/from the base station 800 via a fiber optic or wireless backhaul. The CN interface circuitry 812 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 812 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
In some embodiments, the base station 800 may be coupled with transmit receive points (TRPs) using the antenna structure 826, CN interface circuitry, or other interface circuitry.
It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, or network element as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
In the following sections, further exemplary embodiments are provided.
Example 1 includes a method of operating a user equipment (UE), the method comprising: identifying one or more UEs; generating a request to associate with the one or more UEs in a group; and transmitting the request to a network.
Example 2 includes a method of example 1 or some other example herein, further comprising: generating the request as a non-access stratum (NAS) message; and transmitting the NAS message to an access and mobility management function (AMF).
Example 3 includes the method of example 2 or some other example herein, wherein the NAS message is a NAS registration request.
Example 4 includes the method of example 1 or some other example herein, further comprising: generating the request as a radio resource control (RRC) message; and transmitting the RRC message to a base station.
Example 5 includes the method of example 4 or some other example herein, wherein the RRC message is an RRC connection request.
Example 6 includes the method of example 1 some other example herein, further comprising: obtaining a group identifier of the group; and generating the request to include the group identifier.
Example 7 includes the method of example 6 or some other example herein, further comprising: obtaining the group identifier from a subscriber identity module of the UE.
Example 8 includes a method of operating an access and mobility management function (AMF), the method comprising: receiving a request for a user equipment (UE) to be associated with one or more UEs in a group; accessing UE subscription information to determine the UE is authorized to join the group; and transmitting an accept message to indicate that the UE is authorized to join the group.
Example 9 includes the method of example 8 or some other example herein, further comprising: transmitting a UE context set up request message to a base station to indicate that the UE is authorized to join the group and to identify a plurality of UEs that are in the group, the plurality of UEs to include the UE and the one or more UEs.
Example 10 includes the method of example 8 or some other example herein, wherein the request includes a group ID and the method further comprises: identifying the one or more UEs based on the group ID and the UE subscription information.
Example 11 includes the method of example 8 or some other example herein, wherein the UE subscription information includes membership information of the group and the registration request does not specifically identify the group.
Example 12 includes the method of example 8 or some other example herein, wherein the request includes identities of the one or more UEs.
Example 13 includes the method of example 8 or some other example herein, wherein the request is a non-access stratum registration request from the UE or is an initial UE message from a base station.
Example 14 includes a method of operating a base station, the method comprising: receiving an indication that a plurality of user equipments (UEs) are associated with one another in a group; and performing a radio access network (RAN) management operation based on the indication.
Example 15 includes the method of example 14 or some other example herein, wherein the RAN management operation is a mobility operation or a measurement operation.
Example 16 includes the method of example 14 or some other example herein, wherein performing the RAN management operation comprises: selecting a representative UE from the plurality of UEs; configuring the representative UE with measurements to perform on behalf of the plurality of UEs.
Example 17 includes the method of example 14 or some other example herein, wherein performing the RAN management operation comprises: collectively handing over the plurality of UEs to a target base station.
Example 18 includes a method of example 14 or some other example herein, wherein performing the RAN management operation comprises: handing over the plurality of UEs to one or more target base stations in a plurality of stages.
Example 19 includes the method of example 18 or some other example herein, wherein handing over the plurality of UEs in a plurality of stages comprises: handing over a first UE of the plurality of UEs to a first target base station in a first stage; confirming the first UE is successfully handed over to the first target base station; and handing over one or more second UEs of the plurality of UEs to the first target base station or a second target base station in a second stage based on said confirming the first UE is successfully handed over.
Example 20 includes the method of example 14 or some other example herein, wherein performing the RAN management operation comprises: connecting a first UE of the plurality of UEs to a special cell; and connecting one or more second UEs of the plurality of UEs to at least one secondary cell.
Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 23 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 24 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof
Example 26 may include a signal as described in or related to any of examples 1-20, or portions or parts thereof.
Example 27 may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 28 may include a signal encoded with data as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.
Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof
Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
Example 32 may include a signal in a wireless network as shown and described herein.
Example 33 may include a method of communicating in a wireless network as shown and described herein.
Example 34 may include a system for providing wireless communication as shown and described herein.
Example 35 may include a device for providing wireless communication as shown and described herein.
Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed.
Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
This application claims the benefit of U.S. Provisional Patent Application No. 63/240,842, filed on Sep. 3, 2021, which is herein incorporated by reference in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 63240842 | Sep 2021 | US |
