System and method for task-driven collaborative smart clustering

Abstract

Embodiments of the present application relate to systems, methods, and non-transitory computer readable media for: a first wireless communication entity sending a first message to a second wireless communication entity, the first message indicating whether the first wireless communication entity supports a Collaborative Intelligent Cluster (CIC) function; a second message responsive to the first message is received by the first wireless communication entity from the second wireless communication entity.

Description

Technical Field

[0001] Embodiments of the present application relate generally to wireless communications, and more particularly, to collaborative intelligent clustering (CIC). Background Art

[0002] A New Radio (NR) system may utilize a network architecture comprising one or more base stations in communication with one or more core access and mobility management functions (AMFs) or one or more user plane functions (UPFs). Summary of the Invention

[0003] The present application embodiments relate to solving issues related to one or more of the problems raised in the prior art, and to providing additional features that will readily become apparent when taken in conjunction with the accompanying drawings by reference to the following detailed description. According to various embodiments, example systems, methods, devices, and computer program products are disclosed in the present application embodiments. However, it is understood that these embodiments are presented by way of example, not limitation, and it will be apparent to those of ordinary skill in the art reading the present application embodiments that various modifications to the disclosed embodiments may be made while remaining within the scope of the present application embodiments.

[0004] In some embodiments, a first message may be sent by a first wireless communication entity to a second wireless communication entity, the first message indicating whether the first wireless communication entity supports the CIC function. The first wireless communication entity may receive a second message from the second wireless communication entity in response to the first message.

[0005] The above aspects and other aspects and their implementations are described in more detail in the drawings, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Various exemplary embodiments of the present invention are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the present invention to facilitate the reader's understanding of the present invention. Therefore, the drawings should not be construed as limiting the breadth, scope, or applicability of the present invention. It should be noted that for clarity and convenience of description, these drawings are not necessarily drawn to scale.

[0007] Figure 1 A cellular communication system according to some embodiments is shown;

[0008] Figure 2 A block diagram illustrating a base station and an exemplary user equipment device according to some implementation examples is shown;

[0009] Figure 3shows a schematic diagram of an exemplary smart factory according to some embodiments;

[0010] Figure 4 A schematic diagram illustrating an exemplary network architecture according to some embodiments;

[0011] Figure 5 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0012] Figure 6 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0013] Figure 7 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0014] Figure 8 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0015] Figure 9 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0016] Figure 10 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0017] Figure 11 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0018] Figure 12A and Figure 12B A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0019] Figure 13 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0020] Figure 14 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0021] Figure 15 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0022] Figure 16 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0023] Figure 17 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0024] Figure 18 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0025] Figure 19A and Figure 19B A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0026] Figure 20 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0027] Figure 21 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0028] Figure 22 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0029] Figure 23 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0030] Figure 24A and Figure 24B A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0031] Figure 25 A schematic diagram illustrating an exemplary communication process according to some embodiments is shown;

[0032] Figure 26 A flow chart illustrating an exemplary method for task-driven CIC according to some embodiments is shown. DETAILED DESCRIPTION

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

[0034] In a wireless communication system, multiple wireless communication devices can perform group communication. For example, each of the multiple wireless communication devices can be an automatic (e.g., intelligent) device (e.g., smart home device, wearable device, UAV, autonomous vehicle, robot, sensor, etc.) that can perform various tasks. Some tasks can be better performed by a group of these devices. However, support for task-driven collaboration between multiple automatic devices may include various technical difficulties. For example, in order to meet the flexible and customized needs of an application, dynamic workgroup creation and intelligent management may be required based on specific tasks for the application. In addition, due to the limited capabilities of a single type of device, collaborative operation between multiple different types of devices is required to complete the required tasks, which may cause difficulties in communication between multiple types of devices. The embodiments disclosed in the embodiments of the present application provide systems and methods for supporting task-driven wireless communication between multiple devices. To this end, the wireless communication system can utilize wireless communication between a first wireless communication entity and a second wireless communication entity.

[0035] Figure 1 An example wireless communication system 100 according to an embodiment of the present application is shown, in which the technology disclosed in the embodiments of the present application can be implemented. In the following discussion, the wireless communication system 100 can implement any wireless network (such as a cellular network or a narrowband Internet of Things (NB-IoT) network) and is referred to as system 100 in the embodiments of the present application. Such an example system 100 includes a BS 102 and a UE 104 and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 covering a geographic area 101. The BS and the UE can communicate with each other via a communication link 110 (e.g., a wireless communication channel). Figure 1 1 , BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating within its allocated bandwidth to provide adequate radio coverage to its intended users.

[0036] For example, BS 102 can operate at the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which can include data symbols 122 / 128. In the embodiments of the present application, BS 102 and UE 104 are described as non-limiting examples of "communication nodes" in the embodiments of the present application, and communication nodes can generally practice the methods disclosed in the embodiments of the present application. According to various implementations of the embodiments of the present application, such communication nodes can perform wireless communication and / or wired communication.

[0037] In some implementations, the wireless communication system 100 may support MIMO communications. For example, MIMO is a key technology in new radio (NR) systems. MIMO can play a role in both frequency division duplex (FDD) systems and time division duplex (TDD) systems, as well as other systems. MIMO technology can utilize reporting mechanisms such as CSI to support communications. CSI reports can include various types, parts, groups, and fields. The techniques described in the embodiments of the present application can provide enhancements to various aspects of CSI reporting and reporting procedures. For example, a wireless communication device may receive multiple reference signals and configuration parameters from a network through the wireless communication device. The wireless communication device may determine a CSI report based on the multiple reference signals and configuration parameters, where the CSI report includes CSI part 1 and CSI part 2. The wireless communication device may report the CSI report to the network. In some cases, the reporting process may include one or more of the following: a configuration parameter may be configured to enable two or more CQIs in a CSI report, the reference signal is aperiodic or semi-persistent, and each of the following is greater than or equal to a threshold: CSI window length, DD basic unit size, offset between two CSI reference signal (CSI-RS) resources, and length of the DD basis vector. Additionally or alternatively, the wireless communication device may send a user equipment (UE) capability report to the network, the user equipment (UE) capability report indicating that the wireless communication device supports a number of CQI reports, where the number is a positive integer. The wireless communication system may implement a codebook to further support CSI reporting and various other uses.

[0038] Figure 2A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some implementations of the present invention is shown. The system 200 may include components and elements configured to support known or conventional operating features (not necessarily described in detail in the present invention). In one illustrative implementation, the system 200 may be used in a wireless communication environment (such as the one described above). Figure 1 The present invention relates to a method for transmitting (eg, sending and receiving) data symbols in a wireless communication environment 100 of the present invention.

[0039] System 200 generally includes a base station (BS) 202 and a user equipment (UE) 204. BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected as needed via a data communication bus 220. UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which may be any wireless channel or other medium suitable for transmitting data as described in the embodiments of the present application.

[0040] System 200 may also include, in addition to Figure 2 , modules other than the modules shown in . It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the implementation disclosed in the embodiments of the present application can be implemented with hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, they are generally described in terms of the functions of various illustrative components, blocks, modules, circuits, and steps. Whether such functions are implemented as hardware, firmware, or software can depend on specific applications and the design constraints imposed on the entire system. Personnel familiar with the concepts described in the embodiments of the present application can implement such functions in an appropriate manner for each specific application, but such implementation decision-making should not be interpreted as limiting the scope of the embodiments of the present application.

[0041] According to some implementations, the UE transceiver 230 may be referred to as an uplink transceiver 230 in embodiments of the present application, and the uplink transceiver includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time duplexing manner. Similarly, according to some implementations, the BS transceiver 210 may be referred to as a "downlink" transceiver 210 in embodiments of the present application, and the downlink transceiver includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplexing manner. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for receiving transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. In some implementations, there is tight time synchronization with minimal guard times between changes in duplex direction.

[0042] The UE transceiver 230 and the BS transceiver 210 are configured to communicate via a wireless data communication link 250 and, in conjunction with an appropriately configured RF antenna arrangement 212 / 232, the RF antenna embodiment can support a specific wireless communication protocol and modulation scheme. In some illustrative implementations, the UE transceiver 210 and the BS transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, it is understood that the embodiments of the present application are not necessarily limited to application to specific standards and associated protocols. Instead, the UE transceiver 230 and the BS transceiver 210 can be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0043] According to various implementations, BS202 can be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a micro station. In some implementations, UE 204 can be various types of user devices, such as mobile phones, smart phones, personal digital assistants (PDAs), tablet devices, laptop computers, wearable computing devices, etc. Processor modules 214 and 236 can be implemented or implemented using a general-purpose processor, content addressable memory, digital signal processor, application-specific integrated circuit, field programmable gate array, any appropriate programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the embodiments of the present application. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0044] In addition, the methods described in conjunction with the implementations disclosed in the embodiments of the present application can be implemented directly in hardware, firmware, or software modules executed by processor modules 214 and 236, respectively, or in any practical combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230, respectively, so that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some implementations, memory modules 216 and 234 can each include a 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.

[0045] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of BS202, which enable two-way communication between the BS transceiver 210 and other network components and communication nodes configured to communicate with the BS202. For example, the network communication module 218 can be configured to support Internet or WiMAX services. In a typical deployment (without limitation), the network communication module 218 provides an 802.3 Ethernet interface so that the BS transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). As used in the embodiments of the present application with respect to a specified operation or function, the terms "configured for", "configured to" and their variants refer to devices, components, circuits, structures, machines, signals, etc. that are physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0046] Figure 3 3 is a diagram illustrating an example smart factory 300 associated with a task-driven CIC according to various embodiments. The smart factory 300 may include a server 302, a CN 304, a first network entity (e.g., a node) 306, a second network entity 310, and a collaborative smart cluster 308, wherein the cluster 308 may include multiple members or wireless devices, such as member 312, member 314, and member 316. The members within the cluster 308 may communicate wirelessly (e.g., intra-CIC communication).

[0047] In some cases, group communication may correspond to forming a set of devices to be operated. However, such a set of devices may involve applications that utilize multiple types of devices, which may lead to challenges in implementing the operations in an intelligent manner. In the example, Figure 3 Task-driven group communication can be demonstrated. In some cases, inspection tasks vary depending on task complexity (e.g., the product line being inspected and the factory floor's production environment (e.g., lighting, noise, and temperature)). Therefore, a single device may not be sufficient to ensure efficient operation and provide real-time warnings (e.g., a robotic arm has mobility but may have blind spots). Therefore, inspection tasks can be completed collaboratively by a robotic arm together with a high-definition camera and sensors (e.g., gas sensors, thermal sensors).

[0048] In this case, task-driven collaborative intelligent cluster services composed of different types of network-controlled devices (e.g., UAVs, autonomous vehicles, robots, sensors) can support task completion that enables multi-node intelligent collaboration. To support such services, the following can be considered: task-driven CIC management, adaptive task-driven traffic management, and task-level QoS management.

[0049] For example, when managing an appropriate cluster for a specific task (including selecting a "head"), different aspects need to be considered (e.g., which device capabilities are required for the task, and whether the current network status can meet the communication requirements of cluster members). Therefore, it is necessary to support dynamic cluster configuration, which takes into account different conditions (e.g., device capabilities, location, power, radio quality, etc.) to provide non-client-aware cluster services. To efficiently complete tasks, different cluster members can be assigned different subtasks and configured with different transmission paths that take into account (e.g., differences in member capabilities and radio quality). Such task-driven service management and on-demand resource orchestration between members can efficiently complete tasks in a flexible manner. Application users can determine performance requirements and results at the level of each task, while some 5G systems only support QoS monitoring / measurement for each flow or each set of flows. Support for QoS management at the task level (e.g., task-level QoS monitoring, measurement, and prediction). In this way, the intrinsic relationship between different QoS flows for specific applications can also be obtained. The technology described in the embodiments of the present application can support CIC functions, including network support for CIC functions, handover-related processes, CIC-related paging, CIC-related user equipment (UE) context processes, etc.

[0050] Figure 4 FIG4 is a diagram illustrating an example network architecture 400 for task-driven CIC according to various embodiments. The architecture 400 may include multiple wireless communication entities, such as a first wireless communication entity 404 and a second wireless communication entity 402. In some cases, the first wireless communication entity 404 may be a base station, and the second wireless communication entity may be an AMF.

[0051] Figure 5FIG1 is a diagram illustrating an example communication process 500 for task-driven CIC according to various embodiments. Process 500 may include communications between a first wireless communication entity 502 and a second wireless communication entity 504. The first wireless communication entity 502 may send a first message 506 to the second wireless communication entity 504. The second wireless communication entity 504 may send a second message 508 to the first wireless communication entity. In some implementations, the first wireless communication entity 502 may be an NG-RAN node, and the second wireless communication entity 504 may be an AMF.

[0052] In some cases, the NG-RAN node establishes an NG connection to the AMF. An NG request message (e.g., first message 506) with CIC information 1 is sent from the NG-RAN node to the AMF. The AMF may be notified of at least one of the following information: whether the NG-RAN node supports the CIC function; a list of CIC IDs or CIC categories: which types of CIC the NG-RAN node can support. After the AMF receives the NG request message, the AMF may store the received information and consider the following (depending on the received information): whether the NG-RAN node supports or does not support the CIC function; and whether the NG-RAN node supports the following types of CIC (with one or more CIC IDs and / or CIC categories).

[0053] The AMF may then send a response message (e.g., a second message 508) with the CIC information 2 to the NG-RAN node. The NG-RAN node will be informed of at least one of the following information: ACK information (the AMF stores the received CIC information and will consider it for other CIC-related procedures); whether the AMF supports the CIC function; a CIC ID list or CIC category: which types of CIC the AMF can support; the AMF may configure the NG-RAN node with one of the following information based on the received NG-RAN node CIC information 1: (1) whether the NG-RAN node can enable the CIC function, (2) a CIC ID list or CIC category about which types of CIC the NG-RAN node can support.

[0054] After the NG-RAN node receives the response message, the NG-RAN node may store the received information and consider the following aspects based on the received information: whether the AMF supports or does not support the CIC function; the AMF supports the following types of CIC (with one or more CIC IDs and / or CIC categories). If the NG-RAN node receives a configuration about CIC activation information, the NG-RAN node shall be set based on the received configuration.

[0055] Figure 6FIG6 is a diagram illustrating an example communication process for task-driven CIC according to various embodiments. Process 600 may include communication between a first wireless communication entity 602 and a second wireless communication entity 604. The first wireless communication entity 602 may send a first message 606 to the second wireless communication entity 604. The second wireless communication entity 604 may send a second message 608 to the first wireless communication entity. In some implementations, the first wireless communication entity 602 may be an NG-RAN node, and the second wireless communication entity 604 may be an AMF.

[0056] In some embodiments, a configuration update procedure between an NG-RAN node and an AMF may be described. Existing messages (e.g., NG-RAN Node Configuration Update message, NG-RAN Node Configuration Update Confirm message, AMF Configuration Update message, AMF Configuration Update Confirm message) or newly defined messages may be used in this embodiment. Two branches are described in this embodiment.

[0057] For an NG-RAN node-initiated update procedure, the NG-RAN node will modify its CIC support status and trigger this update procedure to notify the AMF of the update. The NG-RAN node will send an NGAP Update Request message along with a CIC Configuration message to the AMF. The AMF will be notified of at least one of the following: 1. Whether the NG-RAN node supports CIC functionality. 2. CIC ID list or CIC categories: The types of CIC supported by the NG-RAN node.

[0058] When the AMF receives an NGAP Update Request message from an NG-RAN node, it may store the received information and consider that the NG-RAN node may make at least one of the following modifications (depending on the received information): the NG-RAN node prefers to change its CIC activation state (e.g., from CIC support to non-CIC support, or from non-CIC support to CIC support, etc.). The NG-RAN node prefers to support the type of CIC (e.g., CIC ID, CIC category, etc.).

[0059] The AMF then replies to the NG-RAN node with an Update Response message. The NG-RAN node will be informed of at least one of the following: ACK information (e.g., the AMF successfully received the NGAP Update Request message); AMF status for CIC support: whether the AMF supports the CIC function, CIC ID list or CIC category: which types of CIC the AMF can support; when the AMF is not satisfied with the received modification, it may modify the received support information and send a new configuration to the NG-RAN node: whether the NG-RAN node supports the CIC function, CIC ID list or CIC category: which types of CIC the NG-RAN node can support.

[0060] Figure 7 FIG2 is a diagram illustrating an example communication process 700 for task-driven CIC according to various embodiments. Process 700 may include communications between a first wireless communication entity 702 and a second wireless communication entity 704. The first wireless communication entity 702 may send a first message 707 to the second wireless communication entity 704. The second wireless communication entity 704 may send a second message 708 to the first wireless communication entity. In some implementations, the first wireless communication entity 702 may be an NG-RAN node, and the second wireless communication entity 704 may be an AMF.

[0061] In some embodiments, a configuration update procedure between an NG-RAN node and an AMF may be described. For an AMF-initiated update procedure: the AMF shall modify the CIC support status for the NG-RAN node and / or the AMF itself. The AMF sends an NGAP Update Request message to the NG-RAN node. The NG-RAN node shall be notified of at least one of the following information: AMF CIC support status: whether the AMF supports CIC functionality; CIC ID list or CIC categories: which types of CIC the AMF can support; NG-RAN node CIC support status: whether the NG-RAN node supports CIC functionality; CIC ID list or CIC categories: which types of CIC the NG-RAN node can support.

[0062] The NG-RAN node receives the Update Request message and replies with an Update Response message. The AMF is notified of at least one of the following: ACK information (e.g., the NG-RAN node successfully receives the NGAP Update Request message); the NG-RAN node may also provide the AMF with its CIC status support modification or its current CIC support status (if necessary) in this message: whether the NG-RAN node supports CIC functionality, CIC ID list or CIC category: which types of CIC the NG-RAN node can support.

[0063] Figure 8 FIG2 is a diagram illustrating an example communication process 800 for task-driven CIC according to various embodiments. Process 800 may include communications between a first wireless communication entity 802, a second wireless communication entity 804, and a third wireless communication entity 806. The first wireless communication entity 802 may transmit one or more initial messages with the second wireless communication entity 804 to establish access to a network. The first wireless communication entity 802 may send a first message to the second wireless communication entity. The second wireless communication entity 804 may send a second message to the third wireless communication entity 806. The third wireless communication entity 806 may send a third message to the second wireless communication entity 804. The second wireless communication entity 804 may send a fourth message to the first wireless communication entity 802. In some embodiments, the first wireless communication entity 802 may be a UE, the second wireless communication entity 804 may be an NG-RAN node, and the third wireless communication entity 806 may be an AMF.

[0064] In some embodiments, initial access to a network may be described. At step 808: In this embodiment, the UE triggers an initial access procedure and is attempting to access a NW with CIC enabled functionality.

[0065] At step 810: the UE sends an RRC message A to the NG-RAN node.

[0066] At step 812, the NG-RAN node receives the RRC message A and sends an NGAP message A with initial CIC information to the AMF. The NGAP message can be an existing message (e.g., an initial UE message or a newly defined NGAP message). The AMF is notified of at least one of the following information: the CIC ID list or CIC category of the serving cell: This is used to inform the AMF of the CIC ID list / CIC category supported by the cell. The cell can be the current serving cell of the UE; CIC support information: whether the cell supports CIC functionality.

[0067] At step 814: AMF receives NGAP message A. Based on the received information, AMF verifies whether the UE can be authorized as a CIC-enabled UE in the current cell. And AMF can also reconfigure / modify CIC information for the UE. AMF sends NGAP message B to the NG-RAN node. The NGAP message can be an existing message (for example, an initial context setup request message, a UE context modification request message, or a newly defined NGAP message). At least one of the following information can be notified to the NG-RAN node: CIC authorization information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC information list: ID is used to indicate different CICs. AMF can configure one or more CIC IDs that the UE can join for the UE. For each CIC ID in the list, at least one of the following information can also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used for the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may include one or more UE IDs; CIC Access Information: This is used to inform the UE whether it can access the CIC. Service CIC Information: This may display one or more CIC IDs. This information indicates that the UE can only access the service CIC(s). If this IE (Service CIC Information) is not present, the following alternatives are possible: the UE may autonomously access one of the CICs listed in the CIC Information List for which CIC access is enabled; or the RAN node may configure the service CIC for the UE.

[0068] At step 816, the NG-RAN node receives NGAP message B and forwards RRC message B to the UE. RRC message B can be an existing RRC message, such as an RRC reconfiguration message or a newly defined RRC message. The UE may be notified of at least one of the following information described in RRC message B: CIC authorization information: This information informs the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information list: This ID is used to indicate different CICs. The AMF may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, at least one of the following information may also be provided: CIC header information: For each CIC ID, CIC header information is configured for that CIC. The CIC header information allows the NG-RAN node and / or UE to identify the UE as the head UE in the CIC. The CIC header information may include one or more UE IDs. CIC access information: This information informs the UE whether it can access the CIC. Service CIC information: This information may include one or more CIC IDs. This information indicates that the UE can only access the service CIC(s). If this IE (Serving CIC Information) does not appear, the following alternative may be selected: the UE may autonomously access one of the CICs already displayed in the CIC information list in which CIC access is enabled.

[0069] Figure 9 FIG1 is a diagram illustrating an example communication process 900 for task-driven CIC according to various embodiments. Process 900 may include communications between a first wireless communication entity 902, a second wireless communication entity 904, and a third wireless communication entity 906. The first wireless communication entity 902 may transmit one or more initial messages with the second wireless communication entity 904 to establish access to a network. The first wireless communication entity 902 may send a first message to the second wireless communication entity 904. The second wireless communication entity 904 may send a second message to the third wireless communication entity 906. The third wireless communication entity 906 may send a third message to the second wireless communication entity 904. The second wireless communication entity 904 may send a fourth message to the first wireless communication entity 902. In some embodiments, the first wireless communication entity 902 may be a UE, the second wireless communication entity 904 may be an NG-RAN node, and the third wireless communication entity 906 may be an AMF.

[0070] In some embodiments, initial access to a network may be described. At step 908: In this embodiment, the UE triggers an initial access procedure and is attempting to access a NW with CIC enabled functionality.

[0071] At step 910: The UE sends an RRC message A with initial CIC information to the NG-RAN node. RRC message A can be an existing RRC message (e.g., RRC setup request, RRC setup complete, or a newly defined RRC message). The NG-RAN node will be notified of at least one of the following information: CIC indication information: This information is used by the UE to notify the NW that the UE supports the CIC function and can join the CIC. CIC function capability information: This is used to indicate the UE CIC capabilities. By using the UE CIC capabilities, the CIC can send appropriate tasks to each UE within the CIC. This information can be an indicator, a bitmap, the level of each capability, the value of each capability, etc. At least one of the following capabilities can be provided here: vision, hearing, hash rate, mobility (e.g., UAV, tracks, wheels, etc.), gas sensing, temperature sensing, etc. CIC head capability: This is used to notify whether the UE can be the head of the CIC. This information can be an indicator, the level of the head capability (e.g., Level A to Level B), or the value of the hash rate. CIC ID information: An ID is used to indicate different CICs. The UE may upload one or more CIC IDs that it may join. CIC Header Indication: This is used to inform the NW that this UE is the head of a CIC.

[0072] Step 912: The NG-RAN node receives RRC message A and sends an NGAP message A with initial CIC information to the AMF. The NGAP message can be an existing message (e.g., an initial UE message or a newly defined NGAP message). The AMF can be notified of at least one item of information described in NGAP message A. CIC indication information: This information is used by the UE to notify the NW that the UE supports the CIC function and can join the CIC. CIC functional capability information: This information is used to indicate the UE's CIC capabilities. By using the UE's CIC capabilities, the CIC can send appropriate tasks to each UE within the CIC. This information can include an indicator, a bitmap, the level of each capability, the value of each capability, etc. At least one of the following capabilities can be provided: vision, hearing, hash rate, mobility (e.g., UAV, tracks, wheels, etc.), gas sensing, temperature sensing, etc. CIC header capability: This information is used to notify whether the UE can be a CIC leader. This information can include an indicator, a header capability level (e.g., Level A to Level B), or a hash rate value. CIC ID information: An ID is used to indicate different CICs. The UE can upload one or more CIC IDs that it can join. CIC Header Indication: This is used to inform the NW that the UE is the head of the CIC. CIC ID List or CIC Class of Serving Cell: This is used to inform the AMF of the CIC ID list / CIC class supported by the cell. This cell may be the current serving cell of the UE.

[0073] Step 914: AMF receives NGAP message A. Based on the received information, AMF verifies whether the UE can be authorized as a CIC-enabled UE. And AMF can also reconfigure / modify CIC information for the UE. AMF sends NGAP message B to the NG-RAN node. The NGAP message can be an existing message (for example, an initial context setup request message, a UE context modification request message, or a newly defined NGAP message). At least one of the following information can be notified to the NG-RAN node: CIC authorization information: This is used to notify the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CICID information: ID is used to indicate different CICs. AMF can configure one or more CIC IDs for the UE to which the UE can join.

[0074] For each CIC ID in the list, at least one of the following information may also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used by the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC access information: This is used to inform the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these service CICs. If this IE (service CIC information) does not appear, the following alternative may be selected: the UE may autonomously access one of the CICs displayed in the CIC information list where CIC access is enabled. The RAN node may configure the service CIC to the UE.

[0075] At step 916: The NG-RAN node receives NGAP message B and forwards RRC message B to the UE. RRC message B may be an existing RRC message (e.g., an RRC reconfiguration message or a newly defined RRC message). The UE may be notified of at least one item of information described in NGAP message B. CIC authorization information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information list: An ID is used to indicate different CICs. The AMF may configure the UE with one or more CIC IDs that the UE can join.

[0076] For each CIC ID, at least one of the following information may also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used for the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC access information: This is used to inform the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these service CICs. If this IE (service CIC information) does not appear, the following alternative may be selected: the UE may autonomously access one of the CICs that is already displayed in the CIC information list and in which CIC access is enabled.

[0077] Figure 10 FIG1 is a diagram illustrating an example communication process 1000 for task-driven CIC according to various embodiments. Process 1000 may include communications between a first wireless communication entity 1002, a second wireless communication entity 1004, and a third wireless communication entity 1006. The first wireless communication entity 1002 may send a first message to the third wireless communication entity 1004. The third wireless communication entity 1002 may send a second message to the second wireless communication entity 1004. The second wireless communication entity 1004 may send a third message to the third wireless communication entity 1006. The third wireless communication entity 1006 may send a fourth message to the first wireless communication entity 1004. In some embodiments, the first wireless communication entity 1002 may be a source NG-RAN node, the second wireless communication entity 1004 may be a target NG-RAN node, and the third wireless communication entity 1006 may be an AMF.

[0078] In some embodiments, NG-based handover may be described. The source NG-RAN node triggers an NG-based handover procedure for a UE in one or more CICs and sends an NGAP message (e.g., a handover request message) to the AMF. When the AMF receives the message, the AMF sends an NGAP message (e.g., a handover request) to the target NG-RAN node. The UE's CIC information may be added to the NGAP message.

[0079] The target NG-RAN node should be notified of at least one of the following: CIC indication information: This information indicates that the UE supports CIC functionality and can join CIC. CIC authorization information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC functional capability information: This is used to indicate the UE CIC capabilities. By using the UE CIC capabilities, the CIC can send appropriate tasks to each UE within the CIC. This information can be an indicator, a bitmap, the level of each capability, the value of each capability, etc. At least one of the following capabilities can be provided: vision, hearing, hash rate, mobility (e.g., UAV, tracks, wheels, etc.), gas sensing, temperature sensing, etc. CIC header capability: This is used to inform whether the UE can be a CIC leader. This information can be an indicator, a header capability level (e.g., Level A to Level B), or a hash rate value. CIC header indication: This is used to inform the NW that the UE is a CIC leader. CIC ID list / CIC category list: This is used to identify the types of CICs that the UE can join. Serving CIC ID / Serving CIC Category (Multiple Serving CIC Categories): This is used to identify which CIC the UE is subscribed to. This may include one or more CIC IDs or CIC categories.

[0080] After the target NG-RAN node receives the NG message (e.g., Handover Request), it shall reply with an NG message (e.g., Handover Requirement Confirm) to the AMF. The AMF then sends an NG message (e.g., Handover Command) to the source NG-RAN node.

[0081] Figure 11 FIG1 is a diagram illustrating an example communication process 1100 for task-driven CIC according to some embodiments. Process 1100 may include communications between a first wireless communication entity 1102 and a second wireless communication entity 1104. The first wireless communication entity 1102 may send a first message 1106 to the second wireless communication entity 1104. The second wireless communication entity 1104 may send a second message 1108 to the first wireless communication entity. In some embodiments, the first wireless communication entity 1102 may be an NG-RAN node, and the second wireless communication entity 1104 may be an AMF.

[0082] In some embodiments, a path switching process may be described. Following an NGAP handover command, the target node may trigger an NGAP path switching process for the UE. New NGAP messages or existing messages (e.g., path switch request, path switch request confirmation) may be used in this process.

[0083] The AMF may be notified of at least one of the following information. Information on the target serving cell for the UE: CIC ID list or CIC category of the target serving cell: This is used to inform the AMF of the CIC ID list / CIC category supported by the cell. Information on the UE: CIC authorization information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE; CIC ID information: The ID is used to indicate different CICs. The AMF may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID in the list, at least one of the following information may also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used by the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs. CIC access information: This is used to inform the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these service CICs. If this IE (Service CIC Information) does not appear, the AMF may regard the CIC ID information as Service CIC Information.

[0084] When the AMF receives this message, the AMF may verify whether the target serving cell supports the UE's current CIC. If so, the AMF shall approve the path switch and reply with a Path Switch Request Confirm message.

[0085] Figure 12A and Figure 12B 1 is a diagram illustrating example communication processes 1200 and 1201 for task-driven CIC according to various embodiments. Processes 1200 and 1201 may include communications between a first wireless communication entity 1202 and a second wireless communication entity 1204. For process 1200, the first wireless communication entity 1202 may send a first message 1206 to the second wireless communication entity 1204. For process 1201, the second wireless communication entity 1204 may send a first message 1208 to the first wireless communication entity. In some implementations, the first wireless communication entity 1202 may be an NG-RAN node, and the second wireless communication entity 1204 may be an AMF.

[0086] In some embodiments, a UE context release procedure may be described. The UE context release procedure is used to release the UE context when the UE is no longer eligible to use the CIC function (e.g., no longer subscribed, unauthorized, etc.). It may be triggered by an NG-RAN node or an AMF. A new NGAP message or an existing message (e.g., UE context release request, UE context release command) may be used for this procedure. At least one of the following information may be notified from one side to the other (e.g., the NG-RAN node sends information to the AMF. The AMF sends information to the NG-RAN node):

[0087] Indication for leaving the CIC: This indicator indicates that the UE can no longer join the current CIC. This may be due to various reasons, such as CIC subscription expiration, unauthorized CIC, or ineligible UE. In some cases, this indicator may be a new top-level indicator in the NGAP message, or a new cause value in the Cause IE.

[0088] Figure 13 13 is a diagram illustrating an example communication process 1300 for task-driven CIC according to various embodiments. Process 1300 may include communication between a first wireless communication entity 1302 and a second wireless communication entity 1304. The first wireless communication entity 1302 may send a first message 1306 to the second wireless communication entity 1304. In some implementations, the first wireless communication entity 1302 may be an NG-RAN node, and the second wireless communication entity 1304 may be an AMF.

[0089] In some implementations, CIC paging may be described. For CM_IDLE UEs, the AMF may trigger a paging procedure and wake up the CM_IDLE UE on demand. The AMF sends a paging message to the NG-RAN node. The NG-RAN node shall be notified of at least one of the following: CIC ID information: This may include one or more CIC IDs.

[0090] When the NG-RAN node receives this information, it can use the CIC ID to avoid paging UEs that do not belong to that CIC. For example, cell A only supports CICs 1, 2, and 3. Cell B supports CICs 2, 3, and 4. If the CIC ID "CIC4" appears in the paging message, paging will only be triggered in cell B.

[0091] Figure 14FIG1 is a diagram illustrating an example communication process 1400 for task-driven CIC according to various embodiments. Process 1400 may include communications between a first wireless communication entity 1402 and a second wireless communication entity 1404. The first wireless communication entity 1402 may send a first message 1406 to the second wireless communication entity 1404. The second wireless communication entity 1404 may send a second message 1408 to the first wireless communication entity. In some implementations, the first wireless communication entity 1402 may be a first NG-RAN node, and the second wireless communication entity 1404 may be a second NG-RAN node.

[0092] In some embodiments, an Xn setup and configuration update process may be described. NG-RAN node 1 sends an Xn request message to NG-RAN node 2 and notifies NG-RAN node 2 of the CIC information of NG-RAN node 1. NG-RAN node 2 replies with an Xn response message and notifies NG-RAN node 1 of the ACK information and / or CIC information of NG-RAN node 2 (the ACK information or CIC information in the Xn response message may be optional). In this embodiment, new XnAP messages or existing XnAP messages (e.g., Xn setup request, Xn setup response, NG-RAN node configuration update, NG-RAN node configuration update confirmation) may be used.

[0093] For the Xn setup procedure: NG-RAN node 1 sends an Xn request message with its CIC support status and / or CIC capabilities to NG-RAN node 2. The Xn request message may inform at least one of the following: whether one or more cells in the NG-RAN node 1 supports CIC functionality; which types of CIC (e.g., CIC category, CIC ID, etc.) are supported by one or more cells in the NG-RAN node 1; for each supported CIC (e.g., ID, category), which serving cells of the NG-RAN node 1 should be supported; CIC ID list or CIC category: which types of CIC the NG-RAN node 1 can support.

[0094] The NG-RAN node 2 replies with an Xn response message, which contains the CIC support status and / or capabilities of the NG-RAN node 2. The Xn response message may notify at least one of the following: ACK information: the NG-RAN node 2 has received the CIC information and will take the received information into consideration; for one or more cells in the NG-RAN node 2, whether the cell supports the CIC function; for one or more cells in the NG-RAN node 2, which types of CIC are supported (e.g., CIC category, CIC ID, etc.); for each supported CIC (e.g., ID, category), which serving cells of the NG-RAN node 2 should be supported; CIC ID list or CIC category: which types of CIC the NG-RAN node 2 can support.

[0095] For the NG-RAN node configuration update procedure: NG-RAN node 1 sends an Xn request message with its CIC support status and / or CIC capabilities to NG-RAN node 2. The Xn request message may inform at least one of the following: whether one or more cells in the NG-RAN node 1 supports CIC functionality; which types of CIC (e.g., CIC category, CIC ID, etc.) are supported by one or more cells in the NG-RAN node 1; for each supported CIC (e.g., ID, category), which serving cells of the NG-RAN node 1 should be supported; CIC ID list or CIC category: which types of CIC the NG-RAN node 1 can support.

[0096] The NG-RAN node 2 replies with an Xn response message, which contains the CIC support status and / or capabilities of the NG-RAN node 2. The Xn response message may notify at least one of the following: ACK information: the NG-RAN node 2 has received the CIC information and will take the received information into consideration; for one or more cells in the NG-RAN node 2, whether the cell supports the CIC function; for one or more cells in the NG-RAN node 2, which types of CIC are supported (e.g., CIC category, CIC ID, etc.); for each supported CIC (e.g., ID, category), which serving cells of the NG-RAN node 2 should be supported; CIC ID list or CIC category: which types of CIC the NG-RAN node 2 can support.

[0097] Figure 15FIG1 is a diagram illustrating an example communication process 1500 for task-driven CIC according to various embodiments. Process 1500 may include communications between a first wireless communication entity 1502 and a second wireless communication entity 1504. The first wireless communication entity 1502 may send a first message 1506 to the second wireless communication entity 1504. The second wireless communication entity 1504 may send a second message 1508 to the first wireless communication entity. In some embodiments, the first wireless communication entity 1502 may be a source NG-RAN node, and the second wireless communication entity 1504 may be a target NG-RAN node.

[0098] In some embodiments, an Xn-based handover may be described. A source node may trigger an Xn-based handover procedure for a UE. New or existing messages (e.g., Xn Handover Request, Xn Handover Request Ack) may be used in the procedure.

[0099] The source NG-RAN node sends an Xn message (e.g., a handover request) to the target NG-RAN node. The target node may be notified of at least one of the following information: CIC authorization information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information: The ID is used to indicate different CICs. The AMF may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used by the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC access information: This is used to inform the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these service CICs.

[0100] When the target NG-RAN node receives the Xn message, it may reply an Xn message (e.g., a handover request confirmation) to the source node.

[0101] Figure 1616 is a diagram illustrating an example communication process 1600 for task-driven CIC according to various embodiments. Process 1600 may include communications between a first wireless communication entity 1602 and a second wireless communication entity 1604. The first wireless communication entity 1602 may send a first message 1606 to the second wireless communication entity 1604. The second wireless communication entity 1604 may send a second message 1608 to the first wireless communication entity. In some implementations, the first wireless communication entity 1602 may be a first (new) NG-RAN node, and the second wireless communication entity 1604 may be a second (old) NG-RAN node.

[0102] In some embodiments, UE context retrieval may be described. When a UE switches from RRC_INACTIVE to RRC_CONNECTED in a new NG-RAN node, the new NG-RAN node may trigger an Xn Retrieve UE Context procedure. New or existing messages (e.g., Xn Retrieve UE Context Request, Xn Retrieve UE Context Response) may be used for this procedure. The new NG-RAN node sends an Xn message (e.g., Retrieve UE Context Request) to the old NG-RAN node for UE context retrieval.

[0103] When the old NG-RAN node receives this message, it may reply with an Xn message (e.g., a Retrieve UE Context Response). The target node may be notified of at least one of the following information: CIC Authorization Information: This is used to inform the NG-RAN node and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID Information: This ID is used to indicate different CICs. The AMF may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC Header Information: For each CIC ID, CIC header information will be configured for that CIC. The CIC header information is used by the NG-RAN node and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC Access Information: This is used to inform the UE whether it can access the CIC. Service CIC Information: This may display one or more CIC IDs. This information indicates that the UE can only access this / these service CICs. If this IE (Service CIC Information) is not present, the AMF may treat the CIC ID information as service CIC information.

[0104] Figure 171 is a diagram illustrating an example communication process 1700 for task-driven CIC according to various embodiments. The process 1400 may include communication between a first wireless communication entity 1402 and a second wireless communication entity 1404. The first wireless communication entity 1402 may send a first message 1406 to the second wireless communication entity 1404. In some implementations, the first wireless communication entity 1402 may be a first NG-RAN node, and the second wireless communication entity 1404 may be a second NG-RAN node.

[0105] In some embodiments, CIC paging may be described. NG-RAN node 1 may trigger a RAN paging procedure and request paging of a UE in NG-RAN node 2. NG-RAN node 2 may be notified of at least one of the following: CIC ID information: This may include one or more CIC IDs. When NG-RAN node 2 receives a CIC ID, it will only perform paging in cells that support the provided CIC ID.

[0106] Figure 18 FIG1 is a diagram illustrating an example communication process 1800 for task-driven CIC according to various embodiments. Process 1800 may include communications between a first wireless communication entity 1802 and a second wireless communication entity 1804. The first wireless communication entity 1802 may send a first message 1806 to the second wireless communication entity 1804. The second wireless communication entity 1804 may send a second message 1808 to the first wireless communication entity. In some embodiments, the first wireless communication entity 1802 may be a gNB-DU node, and the second wireless communication entity 1804 may be a gNB-CU node.

[0107] In some embodiments, F1 setup may be described. In this embodiment, the gNB-DU establishes an F1 connection to the gNB-CU. An F1 setup request message with CIC information 1 is sent from the gNB-DU to the gNB-CU. The gNB-CU is informed of at least one of the following: whether the cell supports CIC functionality for one or more cells in the gNB-DU; which types of CIC are supported for one or more cells in the gNB-DU (e.g., CIC ID list or CIC category); which cells of the gNB-DU can support different types of CIC (e.g., ID list, category); CIC ID list or CIC category: which types of CIC are supported by the gNB-DU; and CIC support indicator (for DU): This is used to inform the gNB-CU whether the gNB-DU supports CIC functionality.

[0108] After the gNB-CU receives the F1 Setup Request message, it sends a Response message with CIC information to the gNB-DU. The gNB-DU is notified of at least one of the following: ACK information. The gNB-CU stores the received CIC information and considers it for other CIC-related procedures; CIC ID list or CIC categories: which types of CIC are supported by the gNB-CU; and CIC support indicator (for the CU): which notifies the gNB-DU whether the gNB-CU supports CIC functionality.

[0109] For the reconfiguration of CIC information for the gNB-DU, at least one of the following information may be notified to the NG-RAN node: whether one or more cells in the gNB-DU can support the CIC function; which types of CIC (e.g., CIC category, CIC ID, etc.) can be supported by one or more cells in the gNB-DU; which cells of the gNB-DU can support different types of CIC (e.g., ID, category); which types of CIC (e.g., CIC category, CIC ID, etc.) the gNB-DU supports; CIC support indicator (for DU): This is used to inform the gNB-CU whether the gNB-DU supports the CIC function.

[0110] If the gNB-DU receives CIC information in the response message, the gNB-DU shall take it into account and modify its CIC support status (if needed) based on the received configuration.

[0111] Figure 19A and Figure 19B 19 is a diagram illustrating example communication processes 1900 and 1901 for task-driven CIC according to various embodiments. Processes 1900 and 1901 may include communications between a first wireless communication entity 1902 and a second wireless communication entity 1904. For process 1900, the first wireless communication entity 1902 may send a first message 1906 to the second wireless communication entity 1904, and the second wireless communication entity 1904 may send a second message 1908 to the first wireless communication entity. For process 1901, the second wireless communication entity 1904 may send a first message 1910 to the first wireless communication entity, and the first wireless communication entity 1902 may send a second message 1912 to the second wireless communication entity 1904. In some embodiments, the first wireless communication entity 1902 may be a gNB-DU node, and the second wireless communication entity 1904 may be a gNB-CU node.

[0112] In some embodiments, a configuration update procedure may be described. A DU or CU may trigger the configuration update procedure. A configuration update procedure is initiated for a DU. The F1 Configuration Update message and F1 Configuration Update Confirm message may be newly defined messages or existing messages (e.g., gNB-DU Configuration Update, gNB-DU Configuration Update Confirm). The DU shall modify its CIC support status and send an F1 Configuration Update message to the CU.

[0113] The gNB-DU may notify the gNB-CU of at least one of the following: whether one or more cells in the gNB-DU supports the CIC function; which types of CIC (e.g., CIC ID list or CIC category) are supported by one or more cells in the gNB-DU; which cells of the gNB-DU can support different types of CIC (e.g., ID list, category); CIC ID list or CIC category: which types of CIC are supported by the gNB-DU; CIC support indicator (for DU): this is used to notify the gNB-CU whether the gNB-DU supports the CIC function.

[0114] After the CU receives the F1 Configuration Update message from the DU, it replies with an F1 Configuration Update Acknowledgement message. The DU is notified of at least one of the following: ACK information. The gNB-CU stores the received CIC information and considers it for other CIC-related procedures. CIC ID List or CIC Category: This indicates which types of CIC the gNB-CU supports. CIC Support Indicator (for the CU): This indicates to the gNB-DU whether the gNB-CU supports CIC functionality. For the reconfiguration of CIC information for the gNB-DU, at least one of the following information may be notified to the NG-RAN node: whether one or more cells in the gNB-DU can support the CIC function; which types of CIC (e.g., CIC category, CIC ID, etc.) can be supported by one or more cells in the gNB-DU; which cells of the gNB-DU can support different types of CIC (e.g., ID, category); which types of CIC (e.g., CIC category, CIC ID, etc.) the gNB-DU supports; CIC support indicator (for DU): This is used to inform the gNB-CU whether the gNB-DU supports the CIC function.

[0115] The CU initiates a configuration update procedure. The F1 Configuration Update message and F1 Configuration Update Confirm message can be newly defined messages or existing messages (e.g., gNB-CU Configuration Update, gNB-CU Configuration Update Confirm). The CU will modify the CIC support status for itself and / or the gNB-DU. The CU sends the F1 Configuration Update to the DU. The gNB-CU may notify the gNB-DU of at least one of the following: a CIC ID list or CIC category: which types of CIC the gNB-DU supports; a CIC support indicator (for the DU): which notifies the gNB-CU whether the gNB-DU supports the CIC function.

[0116] After the DU receives the F1 Configuration Update message from the CU, it replies with an F1 Configuration Update Acknowledgement message. The CU is notified of at least one of the following: ACK information (e.g., the gNB-DU stores the received CIC information and will consider it for other CIC-related procedures). The DU may also send the CU its CIC support status information: whether the cell supports CIC functionality for one or more cells in the gNB-DU; which types of CIC (e.g., CIC category, CIC ID, etc.) it supports for one or more cells in the gNB-DU; which cells of the gNB-DU support different types of CIC (e.g., ID, category); which types of CIC (e.g., CIC category, CIC ID, etc.) the gNB-DU supports; and a CIC support indicator (for the DU): This is used to inform the gNB-CU whether the gNB-DU supports CIC functionality.

[0117] Figure 20 FIG2 is a diagram illustrating an example communication process 2000 for task-driven CIC according to various embodiments. Process 2000 may include communications between a first wireless communication entity 2002 and a second wireless communication entity 2004. The second wireless communication entity 2002 may send a first message 2006 to the first wireless communication entity 2004. The first wireless communication entity 2004 may send a second message 2008 to the second wireless communication entity. In some embodiments, the first wireless communication entity 2002 may be a gNB-DU node, and the second wireless communication entity 2004 may be a gNB-CU node.

[0118] In some embodiments, UE context setup may be described. The CU triggers the context setup process and sends an F1AP message (e.g., an F1AP UE context setup request message) with UE CIC information to the DU. For UE CIC information, the DU is notified of at least one of the following: CIC authorization information: This is used to notify the DU and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information: The ID is used to indicate different CICs. The NW may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC header information: For each CIC ID, CIC header information will be configured for the CIC. The CIC header information is used by the DU and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC access information: This is used to notify the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these service CICs.

[0119] When the DU receives the UE CIC information, the DU may reply with a UE context setup response message with ack information and take the received UE CIC information into account for UE context establishment.

[0120] Figure 21 FIG2 is a diagram illustrating an example communication process 2100 for task-driven CIC according to various embodiments. Process 2100 may include communications between a first wireless communication entity 2102 and a second wireless communication entity 2104. The second wireless communication entity 2102 may send a first message 2106 to the first wireless communication entity 2104. The first wireless communication entity 2104 may send a second message 2108 to the second wireless communication entity. In some embodiments, the first wireless communication entity 2102 may be a gNB-DU node, and the second wireless communication entity 2104 may be a gNB-CU node.

[0121] In some embodiments, a UE context modification (gNB-CU initiated) may be described. The CU triggers the context modification procedure and sends a F1AP message (e.g., a F1AP UE Context Modification Request message) with UE CIC information to the DU. Regarding the UE CIC information, the DU is notified of at least one of the following: CIC Authorization Information: This information informs the DU and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID Information: This ID indicates different CICs. The NW can configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC Header Information: For each CIC ID, CIC header information is configured for that CIC. The CIC header information allows the DU and / or UE to identify the UE as the head UE in the CIC. The CIC header information may include one or more UE IDs. CIC Access Information: This information informs the UE whether it can access the CIC. Service CIC Information: This information may include one or more CIC IDs. This information indicates that the UE can only access the service CIC(s).

[0122] When the DU receives the UE CIC information, the DU may reply with an F1AP message (eg, a UE context setup response message) with ack information and take the received UE CIC information into account for UE context establishment.

[0123] Figure 22 FIG2 is a diagram illustrating an example communication process 2200 for task-driven CIC according to various embodiments. Process 2200 may include communications between a first wireless communication entity 2202 and a second wireless communication entity 2204. The first wireless communication entity 2202 may send a first message 2206 to the second wireless communication entity 2204. The second wireless communication entity 2204 may send a second message 2208 to the first wireless communication entity. In some embodiments, the first wireless communication entity 2202 may be a gNB-DU node, and the second wireless communication entity 2204 may be a gNB-CU node.

[0124] In some embodiments, a UE context modification request (gNB-DU initiated) may be described. The DU triggers the context modification request procedure and sends a F1AP message (e.g., a F1AP UE context modification request message) to the CU with UE CIC information. Regarding the UE CIC information, the CU is notified of at least one of the following: CIC authorization information: This information informs the DU and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information: This ID indicates different CICs. The NW may configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC header information: For each CIC ID, CIC header information is configured for that CIC. The CIC header information allows the DU and / or UE to identify the UE as the head UE in the CIC. The CIC header information may include one or more UE IDs. CIC access information: This information informs the UE whether it can access the CIC. Service CIC information: This information may include one or more CIC IDs. This information indicates that the UE can only access the service CIC(s).

[0125] The CU replies to the DU with an F1AP message (e.g., an F1AP UE Context Setup Acknowledge message) for approval. In addition, the CU may also modify the received UE CIC information and configure the modified UE CIC information to the DU. When the DU receives the modified UE CIC information, the DU should store the information and take it into account for the UE context. For the UE CIC information, the DU is notified of at least one of the following: CIC authorization information: This is used to inform the DU and / or UE whether the UE is authorized to access the NW as a CIC-enabled UE. CIC ID information: The ID is used to indicate different CICs. The NW can configure the UE with one or more CIC IDs that the UE can join. For each CIC ID, the following information may also be provided: CIC header information: For each CIC ID, the CIC header information will be configured for the CIC. The CIC header information is used by the DU and / or UE to know which UE in the CIC is the head. The CIC header information may be one or more UE IDs; CIC access information: This is used to inform the UE whether it can access the CIC. Service CIC information: One or more CIC IDs may be displayed here. This information indicates that the UE can only access this / these serving CICs.

[0126] Figure 23FIG2 is a diagram illustrating an example communication process 2300 for task-driven CIC according to various embodiments. Process 2300 may include communication between a first wireless communication entity 2302 and a second wireless communication entity 2304. The second wireless communication entity 2302 may send a first message 2306 to the first wireless communication entity 2304. In some implementations, the first wireless communication entity 2302 may be a gNB-DU node, and the second wireless communication entity 2304 may be a gNB-CU node.

[0127] In some embodiments, CIC paging may be described. A paging procedure may be triggered by the gNB-CU to wake up UEs belonging to a specific CIC. The CU may notify the DU of at least one of the following: CIC ID information: This may include one or more CIC IDs. When the DU receives a paging message, it may use the received CIC ID to avoid paging UEs not belonging to that CIC. For example, the gNB-DU may perform paging only in specific cells that support the provided CIC ID.

[0128] Figure 24A and Figure 24B 24 is a diagram illustrating example communication processes 2400 and 2401 for task-driven CIC according to various embodiments. Processes 2400 and 2401 may include communications between a first wireless communication entity 2402 and a second wireless communication entity 2404. For process 2400, the first wireless communication entity 2402 may send a first message 2406 to the second wireless communication entity 2404, and the second wireless communication entity 2404 may send a second message 2408 to the first wireless communication entity. For process 2401, the second wireless communication entity 2404 may send a first message 2410 to the first wireless communication entity, and the first wireless communication entity 2402 may send a second message 2412 to the second wireless communication entity 2404. In some embodiments, the first wireless communication entity 2402 may be a gNB-DU node, and the second wireless communication entity 2404 may be a gNB-CU node.

[0129] In some embodiments, E1 setup may be described. CIC information regarding the CIC support status / capabilities of the gNB-CU-UP may be sent from the gNB-CU-UP to the gNB-CU-CP during the E1 setup procedure. After the CP receives the CIC information from the UP, it should store the information and may take it into account for bearer context establishment.

[0130] For the gNB-CU-CP triggered setup procedure, new or existing messages (e.g., gNB-CU-CP E1 Setup Request, gNB-CU-CP E1 Setup Response) will be used. CIC information will be sent to the CP via the E1 Setup Response message. The CIC information will include at least one of the following: whether the CP supports CIC functionality; and a list of CIC IDs or CIC categories indicating which types of CIC the CP can support.

[0131] For the setup procedure triggered by the gNB-CU-UP, new or existing messages (e.g., gNB-CU-UP E1 Setup Request, gNB-CU-CP E1 Setup Response) will be used. CIC information will be sent to the CP via the E1 Setup Request message. The CIC information will include at least one of the following: whether the UP supports CIC functionality; and a list of CIC IDs or CIC categories indicating which types of CIC the UP can support.

[0132] Figure 25 FIG2 is a diagram illustrating an example communication process 2500 for task-driven CIC according to various embodiments. Process 2500 may include communications between a first wireless communication entity 2502 and a second wireless communication entity 2504. The second wireless communication entity 2502 may send a first message 2506 to the first wireless communication entity 2504. The first wireless communication entity 2504 may send a second message 2508 to the second wireless communication entity. In some embodiments, the first wireless communication entity 2502 may be a gNB-DU node, and the second wireless communication entity 2504 may be a gNB-CU node.

[0133] In some implementations, a UP configuration update may be described. If a UP modifies its CIC support information, it should notify the CP of the change. The configuration update procedure is triggered by the UP. New or existing messages (e.g., gNB-CU-UP Configuration Update, gNB-CU-UP Configuration Update Confirm) may be used for this procedure. The CIC information includes at least one of the following: whether the UP supports CIC functionality; a CIC ID list or CIC categories: which types of CIC the UP supports.

[0134] Figure 26 is a flow chart illustrating an example method 1700 for task-driven CIC in accordance with various embodiments. In some cases, the method 1700 may include a first message indicating whether the first wireless communication entity supports CIC functionality.

[0135] At 2602, a first wireless communication entity may send a first message to a second wireless communication entity indicating whether the first wireless communication entity supports CIC functionality. In some cases, the first message may also include a list of CIC IDs or a CIC category. In some cases, the second message may include at least one of the following: ACK information confirming the CIC functionality; whether the second wireless communication entity supports the CIC functionality; a list of CIC IDs or a CIC category; or whether the first wireless communication entity can enable the CIC functionality. At 2604, the first wireless communication device may receive a second message from the second wireless communication entity in response to the first message.

[0136] In some embodiments, the first wireless communication entity may send a third message to the second wireless communication entity requesting an update of the CIC support status. The first wireless communication entity may receive a fourth message from the second wireless communication entity in response to the third message. In some embodiments, the third message also includes at least one of the following: whether the first wireless communication entity supports the CIC function; or a list of CIC IDs or CIC categories. In some embodiments, the fourth message also includes at least one of the following: ACK information confirming the request; or the second wireless communication entity's status regarding CIC support.

[0137] In some embodiments, the first wireless communication entity may receive a third message from the second wireless communication entity requesting an update of the CIC support status. The first wireless communication entity may send a fourth message to the second wireless communication entity in response to the third message. In some embodiments, the third message also includes at least one of the following: the status of the first wireless communication entity regarding CIC support; or the status of the second wireless communication entity regarding CIC support. In some embodiments, the fourth message also includes at least one of the following: ACK information confirming the request; whether the first wireless communication entity supports the CIC function; or a CIC ID list or CIC category.

[0138] In some embodiments, the first wireless communication entity may send a third message including initial CIC information to the second wireless communication entity. The first wireless communication entity may receive a fourth message including CIC configuration and / or CIC authorization information from the second wireless communication entity. The first wireless communication entity may send a fifth message including CIC configuration and / or CIC authorization information to the third wireless communication entity.

[0139] In some embodiments, the first wireless communication entity may receive a radio resource control (RRC) message including initial CIC information from a third wireless communication entity. The first wireless communication entity may send a third message including initial CIC information to a second wireless communication entity. The first wireless communication entity may receive a fourth message including CIC configuration and / or CIC authorization information from the second wireless communication entity. The first wireless communication entity may send a fifth message including CIC configuration and / or CIC authorization information to the third wireless communication entity.

[0140] In some embodiments, the first wireless communication entity may receive a third message from the second wireless communication entity including a handover request from the third wireless communication entity to the first wireless communication entity. The third message includes CIC configuration and / or CIC authorization information. The first wireless communication entity may send a fourth message to the second wireless communication entity including a path switch request. The fourth message includes CIC configuration and / or CIC authorization information.

[0141] In some embodiments, the first wireless communication entity may, in response to identifying that the third communication entity is not eligible for CIC functionality, send a third message to the second wireless communication entity requesting release of the context of the third communication entity. The first wireless communication entity may receive a fourth message from the second wireless communication entity instructing the third communication entity to leave the corresponding CIC.

[0142] In some embodiments, the first wireless communication entity may receive a third message including a paging request from the second wireless communication entity, wherein the third message includes a CIC configuration.

[0143] Although various embodiments of the present application embodiments have been described above, it should be understood that they are presented only by way of example rather than by way of limitation. Similarly, various schematic diagrams can depict example architectures or configurations, and example architectures or configurations are provided to enable those of ordinary skill in the art to understand the example features and functions of the present application embodiments. However, such personnel will understand that the present application embodiments are not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of some embodiments can be combined with one or more features of another embodiment described in the present application embodiments. Therefore, the breadth and scope of the present application embodiments should not be limited by any illustrative embodiment in the illustrative embodiments described above.

[0144] It is also understood that any reference to an element using nomenclature such as "first," "second," etc., in the embodiments of the present application generally does not limit the quantity or order of those elements. On the contrary, these nomenclatures can be used as a convenient means of distinguishing between two or more elements or instances of elements in the embodiments of the present application. Therefore, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some way.

[0145] In addition, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0146] Those skilled in the art will also understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed in the embodiments of the present application can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes incorporating instructions (for convenience, programs or design codes may be referred to as "software" or "software modules" in the embodiments of the present application), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, they have been generally described above in terms of the functions of various illustrative components, blocks, modules, circuits, and steps. Whether such functions are implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the entire system. Skilled technicians can implement the described functionality in various ways for each specific application, but such implementation decisions do not result in departure from the scope of the embodiments of the present application.

[0147] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, modules, devices, components and circuits described in the embodiments of the present application can be implemented in or performed by an integrated circuit (IC), which can 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 device, or any combination thereof. The logic blocks, modules and circuits can also include an antenna and / or a transceiver to communicate with various components within a network or within a device. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration for performing the functions described in the embodiments of the present application.

[0148] If implemented in software, these functions can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed in the embodiments of the present application can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any media that can enable a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by 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 device, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0149] In the embodiments of the present application, the term "module" as used in the embodiments of the present application refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described in the embodiments of the present application. In addition, for the purpose of discussion, various modules are described as separate modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the associated functions of the embodiments of the present application.

[0150] In addition, memory or other storage devices and communication components can be used in the embodiments of the present application. It will be understood that, for clarity purposes, the above description has described the embodiments of the present application with reference to different functional units and processors. However, it will be apparent that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without detracting from the embodiments of the present application. For example, functions shown as being performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to appropriate means for providing the described functions, rather than indicating a strict logical or physical structure or organization.

[0151] Various modifications to the implementations described in the embodiments of the present application will be readily apparent to those skilled in the art, and the general principles defined in the embodiments of the present application may be applied to other implementations without departing from the scope of the embodiments of the present application. Therefore, the embodiments of the present application are not intended to be limited to the implementations shown in the embodiments of the present application, but are intended to conform to the broadest scope consistent with the novel features and principles disclosed in the embodiments of the present application (as described in the claims below).

Claims

1. A wireless communication method, comprising: The first wireless communication entity sends a first message to the second wireless communication entity, where the first message indicates whether the first wireless communication entity supports a collaborative intelligent cluster CIC function; The first wireless communication entity receives a second message in response to the first message from the second wireless communication entity.

2. The wireless communication method according to claim 1, wherein: The first message also includes a CIC identification ID list or a CIC category.

3. The wireless communication method according to claim 1, wherein: The second message further includes at least one of the following: ACK information confirming the CIC function; whether the second wireless communication entity supports the CIC function; a CICID list or a CIC category; and whether the first wireless communication entity can enable the CIC function.

4. The wireless communication method according to claim 1, further comprising: The first wireless communication entity sends a third message requesting to update the CIC support status to the second wireless communication entity; The first wireless communication entity receives a fourth message in response to the third message from the second wireless communication entity. The wireless communication method according to claim 4 , wherein: The third message includes at least one of the following: whether the first wireless communication entity supports the CIC function; a CIC ID list; and a CIC category. The wireless communication method according to claim 4 , wherein: The fourth message includes: ACK information of the confirmation request and / or the status of the second wireless communication entity regarding the CIC support status.

7. The wireless communication method according to claim 1, further comprising: The first wireless communication entity receives a third message requesting to update the CIC support status from the second wireless communication entity; The first wireless communication entity sends a fourth message in response to the third message to the second wireless communication entity.

8. The wireless communication method according to claim 7, wherein: The third message includes: a status of the first wireless communication entity regarding the CIC support status, and / or a status of the second wireless communication entity regarding the CIC support status.

9. The wireless communication method according to claim 7, wherein: The fourth message further includes at least one of the following: ACK information of a confirmation request; whether the first wireless communication entity supports the CIC function; a CIC ID list; and a CIC category.

10. The wireless communication method according to claim 1, further comprising: The first wireless communication entity sends a third message including initial CIC information to the second wireless communication entity; receiving, by the first wireless communication entity, a fourth message including CIC configuration and / or CIC authorization information from the second wireless communication entity; The first wireless communication entity sends a fifth message including the CIC configuration and / or CIC authorization information to the third wireless communication entity.

11. The wireless communication method according to claim 1 , further comprising: The first wireless communication entity receives a radio resource control (RRC) message including initial CIC information from a third wireless communication entity; The first wireless communication entity sends a third message including the initial CIC information to the second wireless communication entity; receiving, by the first wireless communication entity, a fourth message including CIC configuration and / or CIC authorization information from the second wireless communication entity; The first wireless communication entity sends a fifth message including the CIC configuration and / or CIC authorization information to the third wireless communication entity.

12. The wireless communication method according to claim 1, further comprising: The first wireless communication entity receives a third message from the second wireless communication entity, wherein the third message includes a handover request from the third wireless communication entity to the first wireless communication entity.

13. The wireless communication method according to claim 12, wherein: The third message includes CIC configuration and / or CIC authorization information.

14. The wireless communication method according to claim 12, further comprising: The first wireless communication entity sends a fourth message including a path switch request to the second wireless communication entity.

15. The wireless communication method according to claim 14, wherein: The fourth message includes CIC configuration and / or CIC authorization information.

16. The wireless communication method according to claim 1, further comprising: In response to identifying that the third communication entity is not qualified for the CIC function, the first wireless communication entity sends a third message to the second wireless communication entity requesting to release the context of the third communication entity; The first wireless communication entity receives a fourth message from the second wireless communication entity, instructing the third communication entity to leave the corresponding CIC.

17. The wireless communication method according to claim 1, further comprising: The first wireless communication entity receives a third message including a paging request from the second wireless communication entity; The third message includes CIC configuration.

18. 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 recited in any one of claims 1 to 17 .

19. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method recited in any one of claims 1 to 17.

Images