System and method for task-driven collaborative smart cluster location reporting

Abstract

Systems and methods for task-driven collaborative smart cluster location reporting are provided. A first wireless communication entity may receive a first message from a second wireless communication entity, the first message including a collaborative smart cluster (CIC) location report configuration. The first wireless communication entity may send a second message to a second wireless communication entity, the second message including CIC location information determined based on the CIC location report configuration.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems and methods for task-driven collaborative intelligent cluster location reporting. Background Technology

[0002] Coverage is a key consideration in cellular network deployment. With the rise of interconnected devices, there is an increasing focus on efficient device communication. Current standards, from 3G (3rd Generation Mobile Communication) and 5G (5th Generation Mobile Communication) to the subsequent evolution of 3GPP (3rd Generation Partnership Project), emphasize the importance of seamless communication between various devices, from smart home devices to wearables. In industrial settings, the complexity of tasks often necessitates collaboration. This requires multiple collaborative operations management systems designed to create workgroups and efficiently gather information for various purposes. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more of the problems presented in the prior art and provide additional features that will become apparent when taken into account in conjunction with the following drawings and by reference to the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example only and are not restrictive, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A first wireless communication entity can receive / obtain / acquire a first message from a second wireless communication entity, the first message including a Cooperative Intelligence Cluster (CIC) location reporting configuration. The first wireless communication entity can send / provide / transmit a second message to the second wireless communication entity, the second message including CIC location information determined based on the CIC location reporting configuration.

[0005] In a particular implementation, the first wireless communication entity may be a CIC header, and the second wireless communication entity may be an NG-RAN (Next Generation Radio Access Network) node. The CIC location report configuration may be configured by a core network entity (e.g., an AMF (Access and Mobility Management Function)) and sent to the second wireless communication entity.

[0006] In a particular implementation, the first wireless communication entity may be an NG-RAN node, and the second wireless communication entity may be a core network entity.

[0007] In a particular implementation, the first wireless communication entity may be a CIC header, and the second wireless communication entity may be an NG-RAN node. The CIC location reporting configuration may be configured by the second wireless communication entity.

[0008] In a particular implementation, the CIC location report configuration may include at least one of the following: CIC identification (ID); area of ​​interest information, which may further include at least one of the following: reference ID, beam information list, cell global identifier (CGI) list, tracking area identifier (TAI) list, global RAN (Radio Access Network) node ID list, public land mobile network (PLMN) ID list, network identifier (NID) list, or area of ​​interest determined based on the location field; location reports to be cancelled; event information list; reporting rules; additional location information; and / or reporting period.

[0009] In a particular implementation, the CIC location information may include at least one of the following: CIC ID; event information; CIC presence of interest area information; and / or a list of reporting areas.

[0010] In a particular implementation, the first message may include a Radio Resource Control (RRC) message, an NGAP (NG Application Protocol) message, or an XnAP (Xn Application Protocol) message.

[0011] In a particular implementation, the first wireless communication entity may include a target NG-RAN node, and the second wireless communication entity may include a source NG-RAN node.

[0012] In a particular implementation, the first wireless communication entity can receive the CIC location report configuration through the core network entity.

[0013] In a particular implementation, the first wireless communication entity may include a source NG-RAN node, and the second wireless communication entity may include a target NG-RAN node.

[0014] In a particular implementation, the first wireless communication entity can receive the CIC location report configuration through the core network entity.

[0015] At least one aspect relates to a system, method, apparatus, or computer-readable medium for task-driven collaborative intelligent cluster (CIC) location reporting. A second wireless communication entity can send / provide / transmit a first message to a first wireless communication entity, the first message including a Collaborative Intelligent Cluster (CIC) location reporting configuration. The second wireless communication entity can receive / obtain / acquire a second message from the first wireless communication entity, the second message including CIC location information determined based on the CIC location reporting configuration.

[0016] In some implementations, the network nodes of the technical solution can perform task-driven collaborative intelligent cluster location reporting based on at least one of the following example configurations or solutions: Example configuration 1: CIC location report configuration.

[0017] Example Configuration 2: CIC Location Report.

[0018] Example Configuration 3: Enhanced CIC location reporting on Xn mobility.

[0019] Example Configuration 4: Enhanced CIC location reporting on NG-based handover. Attached Figure Description

[0020] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of this solution to aid the reader's understanding of it. Therefore, these figures should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0021] Figure 1 An example cellular communication network that can implement the techniques disclosed herein is shown according to an embodiment of the present disclosure; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 A schematic diagram of an example network according to some embodiments of the present disclosure is shown; Figure 4 Example implementations of configuring CIC location reporting information in the UE (User Equipment) header via AMF according to some embodiments of this disclosure are shown; Figure 5 Example implementations of configuring CIC location reporting information for NG-RAN nodes via AMF according to some embodiments of this disclosure are shown; Figure 6A An example implementation of configuring CIC location reporting information in the UE header via an NG-RAN node is shown, according to some embodiments of this disclosure; Figure 6B A structural diagram of CIC location reporting configuration information according to some embodiments of this disclosure is shown; Figure 7 Example implementations of CIC location reporting to the AMF via the UE according to some embodiments of this disclosure are shown; Figure 8 An example implementation of CIC location reporting for the AMF via an NG-RAN node is shown, according to some embodiments of this disclosure; Figure 9A Example implementations of CIC location reporting of NG-RAN nodes via a UE according to some embodiments of this disclosure are shown; Figure 9B A structural diagram of another CIC location reporting configuration information according to some embodiments of this disclosure is shown; Figure 10 An example implementation of enhanced CIC location reporting on Xn mobility according to some embodiments of this disclosure is shown; Figure 11 An example implementation of enhanced CIC location reporting on NG-based handover is shown according to some embodiments of this disclosure; Figure 12 A flowchart is shown as an example method for task-driven collaborative intelligent cluster location reporting according to an embodiment of the present disclosure. Detailed Implementation

[0022] 1. Mobile communication technology and environment Figure 1An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the technologies disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are included within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to the intended users of that cell.

[0023] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0024] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (orthogonal frequency division multiplexing) / OFDMA (orthogonal frequency division multiple access) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating features that do not need to be described in detail herein. In one exemplary embodiment, system 200 may be configured to... Figure 1The wireless communication environment 100 is a wireless communication environment in which communication (e.g., transmission and reception) data symbols are as described above.

[0025] System 200 generally includes base station 202 (hereinafter referred to as "BS 202") and user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes BS (base station) transceiver module 210 (hereinafter also referred to as transceiver module 210, transceiver 210 or base station transceiver 210), BS antenna 212 (hereinafter also referred to as antenna 212, downlink antenna 212 or RF antenna arrangement 212), BS processor module 214 (hereinafter also referred to as processor module 214), BS memory module 216 (hereinafter also referred to as memory module 216) and network communication module 218, each module being coupled and interconnected to each other as needed via data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (hereinafter also referred to as UE transceiver 230, transceiver module 230, or transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232, uplink antenna 232, or RF antenna arrangement 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236). Each module is coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250 (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250), which may be any wireless channel or other medium suitable for the data transmission described herein.

[0026] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally according to their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0027] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 to receive transmissions on the wireless transmission link 250 while the uplink receiver is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0028] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0029] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using the following devices designed to perform the functions described herein: general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors coupled with a digital signal processor core, or any other such configuration.

[0030] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any practical combination thereof. Storage modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, optical disc read-only memory (CD-ROM), or any other form of storage medium known in the art. In this respect, storage modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to storage modules 216 and 234 respectively. Storage modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0031] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical but non-limiting deployment, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their various variations used in this document in relation to a specified operation or function refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0032] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and effectively describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer may be any other layer.

[0033] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings to enable those skilled in the art to formulate and use the present solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution after reading this disclosure. Therefore, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of the steps in the methods disclosed herein is merely illustrative. Based on design preferences, the specific order or hierarchy of the steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0034] 2. Systems and methods for task-driven collaborative intelligent cluster management Industry standards (e.g., 3GPP standards) for group communications (e.g., in a 5G core network) focus on forming collections of devices for operation, such as collections of smart home devices or wearable devices, etc. Figure 3 As shown. However, in certain systems (e.g., 5G-A (5G-Advanced, 5G evolution) and / or 6G (6th Generation Mobile Communication)), significant challenges can arise in coordinating the location of devices within a workgroup when applications involve various automated equipment. Addressing this challenge may require overcoming several technical hurdles, such as dynamic cluster location reporting, adaptive task-driven service management, or task-level QoS (Quality of Service) management.

[0035] Using the method described herein, the UE header or NG-RAN node can proactively upload CIC location information to the CN (Core Network) at any time without requiring NW (Network) configuration. Furthermore, one-time reports, event-triggered CIC location reports, and periodic reports can also be configured for the UE header and / or NG-RAN node. Upon receiving the configuration, the NG-RAN node or UE header can send requested CIC location information (including the CIC header, real-time and / or historical information for all CIC entities and / or some CIC members) to the NW. By using the method described herein, the NW and / or authorized third parties can better view CIC location information at different granularities.

[0036] In certain embodiments, CIC location reporting can be configured to be sent to entities (e.g., UE header, NG-RAN node, etc.). The AMF or NG-RAN node can trigger / initiate CIC location reporting configuration, and / or the NG-RAN node or UE can be responsible for CIC location reporting, depending on the detailed configuration. In some implementations, the AMF can be configured to report CIC location to the UE header for CIC. When the UE header receives the configuration, it can report the CIC location accordingly. Figure 4 As shown, the AMF sends an NGAP message A containing CIC location reporting configuration information to the NG-RAN node. When the NG-RAN node receives this message, it can send the information included in the CIC location reporting configuration information to the UE via an RRC message A. The messages used in this process can be existing NGAP / RRC messages or newly introduced messages. In some implementations, the AMF can configure CIC location reporting to the NG-RAN node. When the NG-RAN node receives the CIC location reporting configuration, it can report the CIC location accordingly. Figure 5 As shown, the AMF sends an NGAP message A containing CIC location reporting configuration information to the NG-RAN node. The NGAP message can be an existing NGAP message or a newly introduced message. In some implementations, the NG-RAN node can configure CIC location reporting to the UE header. When the UE header receives the configuration, it can report the CIC location accordingly. Figure 6A As shown, the NG-RAN node sends an RRC message containing CIC location report configuration information to the UE. The RRC message can be an existing RRC message or a newly introduced message.

[0037] In a particular implementation, the CIC location reporting configuration information can be structured as follows: Figure 6B As shown. Figure 6B As shown, for each involved CIC, at least one of the following information may be notified / provided: CIC ID; area of ​​concern information; location reports to be cancelled; event information list; reporting area rules; additional location information; and / or reporting cycle.

[0038] In certain implementations, the CIC ID can be used to identify which CIC is associated with the CIC location reporting configuration. In certain implementations, some region-related information can be included in the CIC location reporting configuration information. The NW can configure specific regions for NG-RAN nodes or UE headers. When the CIC interacts with the configured regions of interest, the NG-RAN node or UE header can trigger / initiate a location report. The NW can configure various regions of interest for NG-RAN nodes or UE headers. For each area of ​​interest, at least one of the following information may be notified / provided: a reference ID, which can be used to identify the area; a beam information list, which may include one or more beam identifiers and (one or more) corresponding cell identifiers; a CGI list, which may include one or more CGIs; a TAI list, which may include one or more TAIs; a global RAN node ID list, which may include one or more global RAN node IDs; a PLMN ID list, which may include one or more PLMN IDs; an NID list, which may include one or more NIDs; and / or an area of ​​interest, which, by using the definition in the positioning field, may include at least one of the following: an ellipsoidal point, an ellipsoidal point with elevation, an ellipsoidal arc, a polygon, an ellipsoidal point with an uncertain circle, an ellipsoidal point with an uncertain ellipse, a high-precision ellipsoidal point with an uncertain ellipse, and / or a high-precision ellipsoidal point with both elevation and uncertain ellipsoids, etc.

[0039] In a particular implementation, one or more reference IDs for a region of interest can be notified / provided to cancel a location report. If a reference ID is shown, the NG-RAN node or UE header can remove a previously configured region of interest with that reference ID. In a particular implementation, an event information list can be used to trigger an event location report. If the CIC meets one or more configured events, the NG-RAN node or UE header can send one or more location reports to the CN. This can also be used for event reporting of a CIC that has been deconfigured by the NW. In this section, at least one of the following information can be notified / provided: >>>If head switching is triggered, report the location directly.

[0040] >>>If the head switching is complete, report the location directly.

[0041] >>>If a new member is added, report their location directly.

[0042] >>>If any member is removed, report the location directly.

[0043] >>>If member configurations are modified, report the location directly.

[0044] >>>If the application task configured for this CIC is completed, the location will be reported directly.

[0045] >>>If the application task configured for this CIC completes M%, then report the location directly.

[0046] >>>Report location directly for any entity in CIC.

[0047] >>>Report the location directly for one or more CIC headers in CIC.

[0048] >>>Report your location directly to any CIC member in the CIC.

[0049] >>>If there are more than or equal to N CIC entities at this location, report the location directly.

[0050] >>>Any entity entering / leaving the area of ​​interest in CIC.

[0051] >>>One or more CIC headers enter / leave the area of ​​interest.

[0052] >>>Any CIC member entering / leaving the area of ​​interest.

[0053] >>> More than or no less than N CIC entities enter / leave the region of interest.

[0054] >>>Any entity in CIC experiences a change in serving cell.

[0055] >>>One or more CIC headers have changed serving cells.

[0056] >>>Any CIC member experiences a change in serving cell.

[0057] >>> More than or no less than N CIC entities have experienced changes in serving cells.

[0058] >>>Any entity in CIC exists in the region of interest.

[0059] >>>One or more CIC headers exist in the region of interest.

[0060] >>>Any CIC member exists in the area of ​​interest.

[0061] >>> There are more or less N CIC entities in the region of interest.

[0062] >>>Any entity in CIC ceases to exist in the region of interest.

[0063] >>>One or more CIC headers cease to exist in the region of interest.

[0064] >>>Any CIC member ceases to exist in the area of ​​interest.

[0065] >>>Normal or more N CIC entities cease to exist in the region of interest.

[0066] >>>Cancel CIC event location reporting.

[0067] It should be noted that N can be a specific number (e.g., 1, 2, 3...) or a percentage (e.g., 1%, 2%, 1 / 2...). Similarly, M can be any specific number between 0 and 100.

[0068] In certain implementations, instead of event-triggered location reporting, the NG-RAN node or UE header can report the current CIC location by considering at least one of the following: the granularity of the reporting area; the confidence level of the reporting area; and / or the CIC entity information involved. The granularity of the reporting area can be used by the NW to configure the level of detail (or granularity) that the NG-RAN node or UE header can use for location reporting. At least one of the following different levels can be notified / provided here: beam level, cell level, TAI level, PLMN level, TA level, NID level, and / or NTN TAI level, etc. In some implementations, the NW can configure a standard for the reporting area in the NG-RAN node or UE header. This may vary depending on the implementation or configuration. If an NG-RAN node meets at least one of the following criteria: any CIC entity in the area; one or more CIC headers in the area; or more than or equal to (or not less than) N entities in the CICs of the area, then the NG-RAN node may add / count reference IDs of different levels (e.g., beam level, cell level, TAI level, PLMN level, TA level, NID level, NTN TAI level, etc.). It should be noted that N can be a specific number (e.g., 1, 2, 3...) or a percentage (e.g., 1%, 2%, 1 / 2...). In some implementations, the CIC entity information involved may be configured as an optional field with one or more CIC entity IDs. If this information is configured, it may indicate / indicate that the NW only needs location reporting information for CIC entities with the specified IDs.

[0069] In certain implementations, the NW can request the CIC's NG-RAN node or UE header to report relevant DC information (if any). The granularity of this information can be cell-level or beam-level, depending on the NW configuration. In certain implementations, the NW can be configured to have the NG-RAN node or UE header report the CIC location only once or periodically. Using a reporting period / frequency, the NG-RAN node or UE header can periodically send CIC location reports.

[0070] In certain embodiments, the UE head can collect / update the location information of CIC members using direct or indirect communication methods and store the received information in the UE head. The NG-RAN node or UE head can proactively or based on NW configuration report CIC location information. In some embodiments, the UE head can proactively report CIC location information to the AMF without receiving any configuration regarding location reporting. The UE head can also report CIC location information to the AMF based on received CIC location reports. Figure 7 As shown, the UE header sends an RRC message A with CIC location report information to the NG-RAN node. When the NG-RAN node receives the RRC message, it sends an NGAP message A with CIC location report information to the AMF. Existing messages or newly defined messages can be used for RRC message A and / or NGAP message A.

[0071] In some implementations, NG-RAN nodes can proactively report CIC location information without receiving any configuration regarding location reporting. NG-RAN nodes can also report CIC location information based on received CIC location report configurations. Figure 8 As shown, the NG-RAN node sends an NGAP message with CIC location report information to the AMF. For NGAP message A, either an existing message or a newly defined message can be used. In some implementations, the UE header can proactively report CIC location information to the NG-RAN node without receiving any configuration regarding location reporting. The UE header can also report CIC location information to the NG-RAN node based on the received CIC location report configuration. For example... Figure 9A As shown, the UE header sends an RRC message A containing CIC location report information to the NG-RAN node. For RRC message A, either an existing message or a newly defined message can be used.

[0072] In a particular implementation, CIC location reporting information can be structured as follows: Figure 9B As shown. Figure 9B As shown, for each involved CIC, at least one of the following information may be notified / provided: CIC ID; event information; information on the CIC's area of ​​concern; and / or a list of reporting areas.

[0073] In certain implementations, the CIC ID can be used to identify which CIC is associated with the CIC location reporting configuration. In certain implementations, CIC location reporting can be triggered / initiated by an event-triggered report previously configured for the NG-RAN node or UE header. The reporting entity (UE header or NG-RAN node) can notify the NW of the triggered event. As described herein, details of the event information can be viewed in the event information list. In certain implementations, if area of ​​interest information is configured for the reporting entity (UE header or NG-RAN node), the presence of area of ​​interest information can be achieved using the CIC. As described herein, details of the area of ​​interest information can be viewed in the area of ​​interest information.

[0074] For each region of interest, at least one of the following information may be notified / provided: region of interest reference ID; CIC presence; and / or location duration. In some implementations, an ID may exist to identify the region for each region of interest. In some implementations, CIC presence may be used to indicate / notify whether (one or more) a CIC exists in the region of interest and how. This region of interest may include at least one of the following: the CIC is entirely located in the region; one or more CIC headers of the CIC are located in the region; a portion (percentage or number) of the CIC is located in the region; the CIC is completely outside the region; one or more CIC headers of the CIC are outside the region; a portion (percentage or number) of the CIC is outside the region; and / or no information exists for the CIC. In some implementations, timestamp or periodic information may be notified / provided in the location duration. The NG-RAN node or UE header may also report the time the CIC is currently / was located at the location, or the duration the CIC is currently / was located in the region of interest, based on configuration.

[0075] In certain implementations, the NG-RAN node or UE header can report the locations of some or all CIC entities in a reporting area list. For each involved CIC entity (CIC header or CIC member), at least one of the following can be notified / provided: CIC entity ID and / or a reporting area information list. The CIC entity ID can be used to identify a specific CIC entity (e.g., CIC header, CIC member). The reporting area information list is location information for the CIC entity. At least one of the following can be included / provided: area information and / or location timeliness. Area information can include area information for the CIC entity. The granularity used for this area information can be based on the implementation or configured by the NW. Details can be found in the granularity, as described herein. Location timeliness can provide / notify timestamps or periodic information. The NG-RAN node or UE header can also report the time when the CIC is currently / was located at that location, or the duration for which the CIC is currently / was located at that location, based on configuration.

[0076] In certain embodiments, such as Figure 10 As shown, during UE head mobility, the CIC location reporting context can be transmitted from NG-RAN node 1 to NG-RAN node 2 via XnAP message A. This XnAP message A can be a newly introduced message or an existing message (e.g., a handover request, a UE context retrieval response). When NG-RAN node 2 receives the CIC location reporting context, it can store this information and, if necessary, execute the CIC location reporting procedure. In certain implementations, the CIC location reporting context may include at least one of the following: CIC location reporting configuration information and / or CIC location reporting information.

[0077] In certain embodiments, such as Figure 11 As shown, for NG-based handover, the CIC location reporting context can be transmitted from the source NG-RAN node to the target NG-RAN node via the AMF. The source NG-RAN node can send an NGAP handover request message with the CIC location reporting context to the AMF. The AMF can send an NGAP handover request message with the CIC location reporting context to the target NG-RAN node. When the target NG-RAN node receives the CIC location reporting context, it can store the information and, if necessary, execute the CIC location reporting procedure. The CIC location reporting context can be transmitted in either the handover request message or the handover request message. In certain embodiments, the CIC location reporting context may include at least one of the following: CIC location reporting configuration information and / or CIC location reporting information.

[0078] Now for reference Figure 12 , Figure 12 A flowchart of method 1200 for task-driven collaborative intelligent cluster location reporting is shown. Method 1200 can be used in conjunction with this document. Figures 1 to 11 This can be implemented using any of the detailed components and devices. In general, method 1200 may include receiving / obtaining / acquiring a first message from a second wireless communication entity, the first message including a Cooperative Intelligent Cluster (CIC) location reporting configuration (1202). The method may also include sending / providing / transmitting a first message, including a CIC location reporting configuration, from the second wireless communication entity to the first wireless communication entity (1204).

[0079] In operation (1202), and in a particular arrangement, the first wireless communication entity may receive / acquire / obtain a first message from the second wireless communication entity, the first message including a Cooperative Intelligent Cluster (CIC) location reporting configuration. The first wireless communication entity may send / provide / transmit a second message to the second wireless communication entity, the message including CIC location information determined based on the CIC location reporting configuration.

[0080] In a specific configuration, the first wireless communication entity can be a CIC header, and the second wireless communication entity can be an NG-RAN node. The CIC location report configuration can be configured by a core network entity (e.g., AMF) and sent to the second wireless communication entity.

[0081] In a specific configuration, the first wireless communication entity can be an NG-RAN node, and the second wireless communication entity can be a core network entity.

[0082] In a specific configuration, the first wireless communication entity can be a CIC header, and the second wireless communication entity can be an NG-RAN node. The CIC location reporting configuration can be configured by the second wireless communication entity.

[0083] In a specific configuration, the CIC location reporting configuration may include at least one of the following: CIC identifier (ID); area of ​​interest information, which may further include at least one of the following: reference ID, beam information list, cell global identifier (CGI) list, tracking area identifier (TAI) list, global RAN node ID list, public land mobile network (PLMN) ID list, network identifier (NID) list, or area of ​​interest determined based on the location field; location reports to be cancelled; event information list; reporting rules; additional location information; and / or reporting period.

[0084] In a specific configuration, the CIC location information may include at least one of the following: CIC ID; event information; CIC presence of interest area information; and / or a list of reporting areas.

[0085] In a particular configuration, the first message may include a Radio Resource Control (RRC) message, an NGAP message, or an XnAP message.

[0086] In a particular configuration, the first wireless communication entity may include a target NG-RAN node, and the second wireless communication entity may include a source NG-RAN node.

[0087] In a specific configuration, the first wireless communication entity can receive the CIC location report configuration through the core network entity.

[0088] In a particular configuration, the first wireless communication entity may include a source NG-RAN node, and the second wireless communication entity may include a target NG-RAN node.

[0089] In a specific configuration, the first wireless communication entity can receive the CIC location report configuration through the core network entity.

[0090] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A second wireless communication entity can send / provide / transmit a first message (1204) to a first wireless communication entity, the first message including a Cooperative Intelligent Cluster (CIC) location reporting configuration. The second wireless communication entity can receive / obtain / acquire a second message from the first wireless communication entity, the second message including CIC location information determined based on the CIC location reporting configuration.

[0091] While various embodiments / implementations of this solution have been described above, it should be understood that these embodiments are presented by way of example only and not by way of limitation. Similarly, various schematic diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand exemplary features and functions of this solution. However, those skilled in the art will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment / implementation herein may be combined with one or more features of another embodiment / implementation described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0092] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient means of distinguishing two or more elements, or multiple instances of a single element. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0093] Furthermore, those skilled in the art will understand that various techniques and skills can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0094] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate the interchangeability of hardware, firmware, and software, the various exemplary components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0095] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable configuration that performs the functions described herein.

[0096] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, with the latter including any medium capable of transferring a computer program or code from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and that is accessible to a computer.

[0097] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for purposes of discussion, individual modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0098] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution described with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains can be used without impairing this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0099] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A wireless communication method, comprising: A first wireless communication entity receives a first message from a second wireless communication entity, the first message including a Cooperative Intelligent Cluster (CIC) location report configuration; as well as The first wireless communication entity sends a second message to the second wireless communication entity, the second message including CIC location information determined based on the CIC location report configuration.

2. The wireless communication method according to claim 1, wherein, The first wireless communication entity is a CIC header, and the second wireless communication entity is an NG-RAN node, wherein the CIC location report configuration is configured by the core network entity and sent to the second wireless communication entity.

3. The wireless communication method according to claim 1, wherein, The first wireless communication entity is an NG-RAN node, and the second wireless communication entity is a core network entity.

4. The wireless communication method according to claim 1, wherein, The first wireless communication entity is a CIC header, and the second wireless communication entity is an NG-RAN node, wherein the CIC location report configuration is configured by the second wireless communication entity.

5. The wireless communication method according to claim 1, wherein, The CIC location reporting configuration includes at least one of the following: CIC Identifier (ID); The area of ​​interest information further includes at least one of the following: reference ID, beam information list, cell global identifier (CGI) list, tracking area identifier (TAI) list, global RAN node ID list, public land mobile network (PLMN) ID list, network identifier (NID) list, or area of ​​interest determined based on the location field. Location reports pending cancellation; Event information list; Reporting rules; Additional location information; or Reporting cycle.

6. The wireless communication method according to claim 1, wherein, The CIC location information includes at least one of the following: CIC ID; Event information; CIC has information on areas of interest; or List of reporting areas.

7. The wireless communication method according to claim 1, wherein, The first message includes a Radio Resource Control (RRC) message, an NGAP message, or an XnAP message.

8. The wireless communication method according to claim 1, wherein, The first wireless communication entity includes a target NG-RAN node, and the second wireless communication entity includes a source NG-RAN node.

9. The wireless communication method according to claim 8, further comprising: The first wireless communication entity receives the CIC location report configuration through the core network entity.

10. The wireless communication method according to claim 1, wherein, The first wireless communication entity includes a source NG-RAN node, and the second wireless communication entity includes a target NG-RAN node.

11. The wireless communication method according to claim 10, further comprising: The first wireless communication entity receives the CIC location report configuration through the core network entity.

12. A wireless communication method, comprising: A first message is sent from a second wireless communication entity to a first wireless communication entity, the first message including Cooperative Intelligent Cluster (CIC) location reporting configuration; as well as The second wireless communication entity receives a second message from the first wireless communication entity, the second message including CIC location information determined based on the CIC location report configuration.

13. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 12.

14. A computer program product comprising a computer-readable program medium, wherein code is stored on the computer-readable program medium, and the code, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 12.

Images