Method and device for jointly serving user equipment by wireless access network nodes

Abstract

This disclosure relates to a method and device for serving user equipment by a first wireless network node. In one embodiment, the method may include the step of transmitting a request message for a non-radio communication service resource of a second wireless access network node to the second wireless access network node. The first wireless access network node may request a non-radio communication service resource to provide non-radio communication services to user equipment and to support providing non-radio communication services to user equipment. The method may further include the step of receiving a response message from the second wireless access network node allocating a non-radio communication service resource for user equipment.

Description

Technology Field

[0001] This application is a continuation of PCT international application PCT / CN2020 / 130726 filed with the National Intellectual Property Administration of China on November 23, 2020, the entire contents of which are incorporated herein by reference. This disclosure generally relates to wireless communication, and in particular to the joint serving of user equipment by wireless access network nodes. Background Technology

[0002] Wireless communication technologies are driving the world toward an increasingly connected and networked society. The rapid growth of mobile communications and technological advancements have driven greater demand for network service capabilities and connectivity. Other factors, such as energy consumption, reliability, spectrum efficiency, and latency, are also critical to meeting the requirements of various communication scenarios. Compared to existing wireless access networks, next-generation systems and wireless communication techniques are expected to go beyond radio communication services to provide a wide range of low-latency services to user terminals.

[0003] This disclosure relates to methods and devices for wireless communication, and more specifically, to methods and devices for providing various non-radio communication services to user equipment by jointly serving user equipment by wireless access network nodes.

[0004] In one embodiment, a method is disclosed that is performed by a first wireless access network node serving user equipment in a wireless communication network. The method may include the step of transmitting a request message for a non-radio communication service resource of a second wireless access network node to the second wireless access network node. The first wireless access network node may request a non-radio communication service resource to provide non-radio communication services to user equipment and to support providing non-radio communication services to user equipment. The method may further include the step of receiving a response message from the second wireless access network node allocating a non-radio communication service resource for user equipment.

[0005] In another embodiment, a method performed by a second wireless access network node in a wireless communication network is disclosed. The method may include the step of receiving a first request message for a non-radio communication service resource of the second wireless access network node from a first wireless access network node. The first wireless access network node may request a non-radio communication service resource to provide both radio communication services and non-radio communication services to user equipment and to support the provision of non-radio communication services to user equipment. The method may further include the step of transmitting a response message allocating a non-radio communication service resource to the first wireless access network node.

[0006] In another embodiment, a device for wireless communication may include a memory for storing instructions and a processing circuit that communicates with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0007] In another embodiment, a computer-readable medium is disclosed that includes instructions that cause the computer to perform the method when executed by a computer.

[0008] The above and other aspects and their implementations are described in more detail in the following drawings, descriptions, and claims. Brief explanation of the drawing

[0009] FIG. 1 illustrates an exemplary cellular wireless access network according to various embodiments. Figure 2 illustrates an exemplary diagram showing communication between wireless access network nodes in a wireless access network. FIGS. 3a and 3b illustrate exemplary architectural models of dual connections. FIG. 4 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 5 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 6 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 7 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 8 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 9 illustrates a flowchart of a method for serving a UE according to an embodiment. FIG. 10 illustrates a flowchart of a method for serving a UE according to an embodiment. Specific details for implementing the invention

[0010] The descriptions and examples of the implementations and / or embodiments of this disclosure may be used to improve performance in wireless communication systems. The term “exemplary” is used to mean “an example of” and, unless otherwise specified, does not imply an ideal or preferred example, implementation, or embodiment. However, implementations may be implemented in various different forms, and thus the subject matter included or claimed should be interpreted as not being limited to any of the embodiments described below. It should also be noted that implementations may be implemented as methods, devices, components, or systems. Accordingly, embodiments of this disclosure may take the form, for example, hardware, software, firmware, or a combination thereof.

[0011] A wireless access network typically provides radio link and backhaul connectivity between user equipment and information or data networks, such as voice or video communication networks or the Internet. An exemplary wireless access network may be based on cellular technologies, which may be based, for example, on 5G NR technologies and / or radio access types. In a cellular wireless access network, multiple wireless access network nodes (WANNs) of the same or different radio access technologies (RATs), e.g., eNB, en-gNB, ng-eNB, gNB, may be deployed on different frequency carriers but within the same geographical coverage area. They may interoperate through designated dual connectivity (DC) / multiple connectivity (MC) operations to provide joint radio communication services to target UE(s).

[0012] FIG. 1 illustrates an exemplary cellular wireless access network (100) according to various embodiments. In the network (100), one macro WANN (104), also referred to as a master node (MN), can provide large coverage to a macro cell (110), while several micro WANNs (102), also referred to as secondary nodes (SN), can provide small, overlapping coverage to micro cells (120). A UE (106) can be jointly configured and served by the MN (104) and the SN (102) to improve user data peak rate / throughput, radio link reliability, etc. As the UE (106) moves around SN clusters, the serving SN(s) are changed accordingly based on the radio quality of the micro cell. From the perspective of the UE, a joint radio communication service between multiple WANNs is provided. The UE (202) may include, but is not limited to, mobile phones, smartphones, tablets, laptop computers, smart electronic products, wearable devices, video surveillance devices, industrial wireless sensors, or home appliances including air conditioners, televisions, refrigerators, ovens, etc., or other devices capable of wireless communication over a network.

[0013] FIG. 2 illustrates an exemplary system diagram illustrating communication between an MN (104) and an SN (102) in a wireless access network (100). WANNs within the wireless access network (100) may be configured to perform a corresponding set of wireless network functions. The sets of wireless network functions, capabilities, and resources may not be identical between different types of wireless access network nodes. However, the sets of wireless network functions, capabilities, and resources between different types of wireless access network nodes may overlap to some extent.

[0014] For example, MN (104) and SN (102) may each include a transceiver circuit (214) coupled to one or more antennas (216) to perform wireless communication with the UE (202). The transceiver circuit (214) may also be coupled to one or more processors (220) which may also be coupled to memory (222) or other storage devices. When read and executed by the processor (220), the memory (222) may store radio communication service modules (224) that enable the processor (220) to implement radio communication services such as radio access to UEs and data transmission between UEs. Additionally, when read and executed by the processor (220), the memory (222) may store non-radio communication service modules (226) that enable the processor (220) to implement non-radio communication services provided to UEs such as computing support services, intelligence support services, storage support services, etc. Additionally, the memory (222) may store instructions or code that, when read and executed by the processor (220), enable the processor (220) to implement various methods among those described herein. The MN (104) and SN (102) may have an intermediate direct or indirect communication interface for information coordination. The direct communication interface may be implemented in a wired or wireless manner, such as optical fiber. Additionally, while various embodiments will be discussed in the context of a specific exemplary wireless communication network (100), the basic principles apply to other applicable wireless communication networks.

[0015] For conceptual explanation, an exemplary architectural model of the dual connection is illustrated in FIGS. 3a and 3b. The Access Mobility Function / Session Management Function (AMF / SMF) is a control plane entity of the 5G Core (5GC), and the User Plane Function (UPF) is a user plane entity of the 5GC. The signaling connection between the AMF / SMF and the MN is a Next Generation Control Plane (NG-C) (MN) interface instance. The signaling connection between the MN and the SN is an Xn-Control Plane (Xn-C) interface instance. The signaling connection between the MN and the UE is a Uu-Control Plane (Uu-C) Radio Resource Control (RRC) interface instance. All of the above signaling connections together manage the configuration and operation of the DC. In FIG. 3a, the user plane connection between the UPF and the MN is a Next Generation User Plane (NG-U) (MN) interface instance, which corresponds to the MN terminated bearer. In FIG. 3b, the user plane connection between the UPF and the SN is an NG-U (SN) interface instance, which corresponds to the SN terminated bearer. The user plane connection between the MN and the SN is an Xn User Plane (Xn-U) interface instance, which corresponds to the split bearer. The user plane connection between the MN and the UE is a Uu User Plane (Uu-U) Master Cell Group (MCG) interface instance, and the user plane connection between the SN and the UE is a Uu-U Secondary Cell Group (SCG) interface instance. All of the above user plane connections together support user data transmission of the DC.From the perspective of a wireless communication network, the MN and SN provide joint radio communication services to the same target UE. The MN can provide radio communication services through local processing efforts within the MN and MCG resources via Uu-U (MCG), and the SN can provide communication services in parallel through local processing efforts within the SN and SCG resources via Uu-U (SCG).

[0016] In addition to radio communication services, the MN may have local resources and capacity for non-radio communication services for the target UE, such as computing, intelligence, and storage. If resources / capacity are insufficient, the MN may request assistance from the Cloud Resource Center (CRC) of the upstream network node. The MN may not transition to an SN and does not require processing support from the SN. Similarly, the SN may also have local resources and capacity for non-radio communication services for the target UE. If resources / capacity are insufficient, the SN may request assistance from the CRC of the upstream network node. The SN may not transition to an MN and does not require processing support from the MN.

[0017] With the emergence of more advanced and highly profiled services, such as enhanced Mobile Edge Computing (MEC) tasks and applications involving large-scale data processing and low-latency requirements, there may be insufficient local resources at the MN / SN; there may be unbalanced local resources where one side is resource-overloaded while the other is unused or idle; or it may not always be possible to switch from an upstream network node to a CRC for assistance because the long geographical and / or logical distance between the MN / SN and the CRC may fail to meet low-latency requirements. The present disclosure introduces a new mechanism that allows two WANs, such as an MN and an SN, to share non-radio communication service resources, such as computing, intelligence, and storage resources, locally in a faster and more efficient manner, instead of involving high-latency upstream network nodes. In this way, WANNs can partition local tasks and provide joint non-radio communication services to target UE(s).

[0018] FIG. 4 illustrates an exemplary implementation (400) for jointly serving a UE, such as UE (106). A first WANN may send a request message to the second WANN for a non-radio communication service resource of the second WANN (402). The first WANN may be, for example, an MN (104) or SN (102) that provides radio communication services to the UE (106). The first WANN may request the non-radio communication service resource of the second WANN to support providing non-radio communication services to the UE (106). The first WANN may provide non-radio communication services to the UE (106). Non-radio communication services may include, for example, computing support services, intelligence support services, and storage support services. The request message may include, for example, the type of non-radio communication service and the amount of non-radio communication service resource. Alternatively or additionally, the request message may include, for example, the identification of the UE requesting the non-radio communication service resource to provide the non-radio communication service to the first WANN.

[0019] The second WANN may receive a request message from the first WANN (404). The second WANN may or may not provide radio communication services to the UE (106). In an example, the second WANN may be an MN (104) or an SN (102), and the UE (106) may be in a dual connection state with the first WANN and the second WANN so that the first WANN and the second WANN can jointly provide radio communication services to the UE (106). In another example, the first WANN may provide radio communication services to the UE (106), while the second WANN may have extra non-radio communication service resources to share with the first WANN but may serve a UE other than the UE (106).

[0020] Upon receiving a request message, the second WANN may determine whether to accept the requested allocation of non-radio communication service resources based on the request message. For example, the second WANN may check whether there are sufficient spare non-radio communication service resources for sharing. Additionally, if the second WANN is providing radio communication services to the UE to which the non-radio communication service resources are allocated in order to support the provision of non-radio communication services, the second WANN may be more likely to accept the allocation request.

[0021] If the second WANN decides to allocate the requested non-radio communication service resource, the second WANN may send a response message to the first WANN allocating the requested non-radio communication service resource (406). The response message may include an acknowledgment for allocating the non-radio communication service. Alternatively or additionally, the response message may include additional information regarding the allocation of the non-radio communication service resource. If the second WANN decides not to allocate the requested non-radio communication service resource, the second WANN may send a response message to the first WANN indicating that it simply rejects the resource allocation request.

[0022] When the first WANN receives a response message from the second WANN (408) allocating requested non-radio communication service resources to the UE (106), the first WANN may, for example, divide tasks for the non-radio communication service provided to the UE (106). Then, the first WANN may transmit a first non-radio communication service support data update message containing tasks for the non-radio communication service to the second WANN (410). Tasks may include, for example, intermediate data for computing services, training data for intelligence services, and storage data for storage services. Tasks may be included in the first non-radio communication service support data update message in the form of containers. A container is designated as an abstract communication block structure that encapsulates specific data to be transmitted. During transmission, the WANN may simply transmit or forward the container to a specific target module as needed, without necessarily learning the contents contained in the container.

[0023] Upon receiving a first non-radio communication support data update message containing a task of a non-radio communication service from the first WANN, the second WANN may complete the task of the non-radio communication service using the non-radio communication service resources allocated to the UE (106) and transmit a second non-radio communication service support data update message containing the result of the task of the first WANN (412). The result of the task may include, for example, the result of computing intermediate data, the result of an intelligence prediction, or an indication of the success or failure of data storage. The result of the task may be included in the second non-radio communication service support data update message in the form of a container. In this way, the first WANN and the second WANN may provide a joint non-radio communication service to the UE (106).

[0024] Request messages, response messages, and update messages transmitted between the first WANN and the second WANN may be carried by signaling. A signaling connection between the first WANN and the second WANN may be established through various existing or future communication interfaces between the WANNs. Communication interfaces may include, for example, the X2 Application Protocol (X2AP) between eNBs and the Xn Application Protocol (XnAP) between gNBs. Signaling may be transmitted / transmitted by the Streaming Control Transport Protocol (SCTP) or the General Packet Radio Services Tunnel Protocol (GTP-U). Alternatively, signaling may be transmitted / transmitted by other Transport Network Layer (TNL) protocols that are separate from the communication interfaces, such as the Transmission Control Protocol (TCP).

[0025] In some implementations, the first WANN may be adjacent to the second WANN, and the first WANN and the second WANN may have an intermediate direct communication interface for information coordination, such as the transmission and reception of signaling between the first WANN and the second WANN. The direct communication interface may be implemented via wired or wireless methods. In this way, the first WANN can communicate with the second WANN faster than upstream network nodes, such as cloud resource centers, and thus can jointly provide non-radio communication services to UEs served with much lower latency.

[0026] To further clarify the signaling procedure for achieving a common non-radio communication service between the first WANN and the second WANN, various embodiments will be discussed with reference to FIGS. 5 through 10. The signaling procedures may be UE-associated or non-UE-associated. In the case of UE association, the signaling procedure may be for establishing a common non-radio communication service dedicated to a specific UE that is already in DC / MC mode along with a common radio communication service. In the case of non-UE association, the signaling procedure may be for establishing a common non-radio communication service generally applicable to a group of UEs that are not yet in DC / MC mode without a common radio communication service.

[0027] FIG. 5 illustrates an exemplary implementation (500) for jointly providing computing support services to a UE. In the implementation (500), the MN (104) and SN (102) may provide joint radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over the air. Meanwhile, the MN (104) may provide computing support services to the UE (106). Computing support services may represent any service that provides various advanced computing capabilities to the UE, such as blockchain services, business analytics services, collaborative editing services, etc. If the local computing resources of the MN (104) are overloaded, the MN (104) may choose to queue all pending tasks (e.g., for the UE's high-profile data services) or request computing support from other WANNs, such as the SN (102). When the capability and quality of the TNL signaling connection between MN (104) and SN (102) (e.g., SCTP) is sufficiently good in terms of data transmission bandwidth, latency / jitter and reliability, MN (104) may request SN (102) to support MN (104) in the computing area for its divided tasks.

[0028] MN (104) may send a "SN computing resource request" message to SN (102), which may include information requesting SN (102) to allocate expected computing resources and, upon approval, start computing support operations (502). Upon receiving the "SN computing resource request" message and accepting the request, SN (102) may allocate corresponding computing resources and provide the capacity allowed in the computing area. Afterward, SN (102) may send a "SN computing resource request acknowledgment" message to MN (104) containing information regarding the allocation of computing resources (506). In this way, a joint computing service between MN (104) and SN (102) can be established.

[0029] During the joint computing service, MN (104) may send one or more "SN computing intermediate data update" messages to SN (102) containing, for example, relevant intermediate data information of partitioned tasks (510). The relevant intermediate data information may include, for example, blockchain transactions to be synchronized to the blockchain, business data for interactive visualization and analysis, etc. SN (102) may perform corresponding computing assistance operations based on the intermediate data information. Then, SN (102) may send corresponding "SN computing intermediate data update" messages to MN (104) containing relevant data information of computing results (512). For example, MN (104) may leverage computing results from SN (102) to calculate the final result of the computing service for UE (106). After that, MN (104) can transmit the final result, namely user data obtained from the joint computing service and related processing by MN (104) and SN (102), to UE (106) (514). It should be noted that transmission between MN (104) and SN (102) can be achieved in the control plane as signaling, whereas transmission between MN (104) and UE (106) can be achieved in the user plane as user data.

[0030] If MN (104) does not require computing support from SN (102), MN (104) may send a “SN computing resource release” message to SN (102) that may include information requesting SN (102) to release / revoke previously allocated computing resources (516). In response, SN (102) may release and revoke allocated storage resources to stop computing support. Following the termination of the joint non-radio communication service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0031] FIG. 6 illustrates an exemplary implementation (600) for jointly providing computing support services to a UE. In the implementation (600), the MN (104) and SN (102) may provide joint radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over the wireless. Meanwhile, the SN (102) may provide computing support services to the UE (106). Computing support services may represent any services that provide various advanced computing capabilities to the UE, such as blockchain services, business analytics services, collaborative editing services, etc. If the local computing resources of the SN (102) are overloaded, the SN (102) may choose to queue all pending tasks (e.g., for the UE's high-profile data services) or request computing support from other WANNs, such as the MN (104). When the capability and quality of the TNL signaling connection between MN (104) and SN (102) (e.g., SCTP) is sufficiently good in terms of data transmission bandwidth, latency / jitter and reliability, SN (102) may request MN (104) to support SN (102) in the computing area for its divided tasks.

[0032] SN (102) may send a "SN computing resource needed" message to MN (104), which may include information requesting MN (104) to allocate expected computing resources and, upon approval, start computing support operations (602). Upon receiving the "SN computing resource needed" message and accepting the request, MN (104) may allocate corresponding computing resources and provide the capacity allowed in the computing area. Afterward, MN (104) may send a "SN computing resource confirmed" message to SN (102) containing information regarding the allocation of computing resources (606). In this way, a joint computing service between SN (102) and MN (104) can be established.

[0033] During the joint computing service, SN (102) may send one or more "MN computing intermediate data update" messages to MN (104) containing, for example, relevant intermediate data information of partitioned tasks (610). The relevant intermediate data information may include, for example, blockchain transactions to be synchronized to the blockchain, business data for interactive visualization and analysis, etc. MN (104) may perform corresponding computing assistance operations based on the intermediate data information. Then, MN (104) may send corresponding "MN computing intermediate data update" messages to SN (102) containing relevant data information of computing results (612). For example, SN (102) may leverage computing results from MN (104) to obtain the final result of the computing service for UE (106). After that, SN (102) can transmit the final result, namely user data obtained from the joint computing service and related processing by SN (102) and MN (104), to UE (106) (614). It should be noted that transmission between MN (104) and SN (102) can be achieved in the control plane as signaling, whereas transmission between SN (102) and UE (106) can be achieved in the user plane as user data.

[0034] If SN (102) does not require computing support from MN (104), SN (102) may send a “SN computing resource release” message to MN (104) that may include information requesting MN (104) to release / revocate previously allocated computing resources (616). In response, MN (104) may release and revocate the allocated computing resources to stop computing support operations. Following the termination of the joint non-radio communication service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0035] FIG. 7 illustrates an exemplary implementation (700) for jointly providing intelligence support services to a UE. In the implementation (700), the MN (104) and SN (102) may provide joint radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over wireless. Meanwhile, the MN (104) may provide intelligence support services to the UE (106). The intelligence support services may include, for example, natural language processing (NLP), speech recognition, autonomous driving, or navigation. If the local intelligence capabilities of the MN (104) are limited, for example, if the Deep Neural Network (DNN) parameter settings of the Artificial Intelligence (AI) model are not optimal due to a lack of sufficient training data, the MN (104) may choose to wait for and collect additional training data from local serving cells (e.g., from various UEs served by the MCG) or request intelligence support from other WANNs such as the SN (102). If the capability and quality of the TNL signaling connection between the MN (104) and the SN (102) (e.g., SCTP) are sufficiently good in terms of data transmission bandwidth, latency / jitter, and reliability, the MN (104) may request the SN (102) to support the MN (104) in the area of ​​intelligence support services. SN (102) can provide additional training data to MN (104) to facilitate improving the AI ​​intelligence model of MN (104).Alternatively or additionally, SN (102) may use its own local AI intelligence model to support performing intelligence operations, such as performing NLP on text data received from MN (104) or performing speech recognition on audio data received from MN (104).

[0036] MN (104) may send a "SN Intelligence Resource Request" message to SN (102), which may include information requesting SN (102) to allocate expected intelligence resources and, upon approval, start an intelligence support operation (702). Upon receiving the "SN Intelligence Resource Request" message and accepting the request, SN (102) allocates corresponding intelligence resources, such as training data for improving SN (102)'s local AI intelligence model and MN (104)'s AI intelligence model, to provide an authorized intelligence support service. Subsequently, SN (102) may send a "SN Intelligence Resource Request Acknowledgment" message to MN (104) containing information regarding the allocation of intelligence resources (706). In this way, a joint intelligence service between MN (104) and SN (102) can be established.

[0037] During the joint intelligence service, MN (104) may, for example, send one or more "SN Intelligence Data Update" messages to SN (102) (710). The "SN Intelligence Data Update" messages may include, for example, relevant information about training data required by MN (104) and / or relevant data to be processed by the AI ​​intelligence model of SN (102), such as text data for NLP and audio data for speech recognition. SN (102) may perform corresponding intelligence support operations based on the information in the "SN Intelligence Data Update" messages. Then, MN (104) may send corresponding "SN Intelligence Data Update" messages to SN (102) (712). The corresponding "SN Intelligence Data Update" messages may include, for example, expected training data and / or prediction results generated by the AI ​​intelligence model of SN (102). For example, MN (104) may leverage training data from SN (102) to improve its intelligence model and / or prediction results from SN (102) to obtain the final result of the intelligence service for UE (106). MN (104) may transmit to UE (106) the final result, i.e., user data, obtained from the joint intelligence service and related processing by MN (104) and SN (102) (714).

[0038] If MN (104) does not require intelligence support from SN (102), MN (104) may send a “SN Intelligence Resource Release” message to SN (102) that may include information requesting SN (102) to release / revoke previously allocated intelligence resources (716). In response, SN (102) may discontinue intelligence support by releasing and revoking storage resources allocated to UE (106). Following the termination of the joint non-radio communication service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0039] FIG. 8 illustrates an exemplary implementation (800) for jointly providing intelligence support services to a UE. In the implementation (800), the SN (102) and MN (104) may provide joint radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over wireless. Meanwhile, the SN (102) may provide intelligence support services to the UE (106). The intelligence support services may include, for example, natural language processing, speech recognition, autonomous driving, or navigation. If the local intelligence capabilities of the SN (102) are limited, for example, if the DNN parameter settings of an AI model are not optimal due to a lack of sufficient training data, the SN (102) may choose to wait for and collect additional training data from local serving cells (e.g., from various UEs served by the MCG) or to request intelligence support from other WANNs such as the MN (104). When the capability and quality of the TNL signaling connection between MN (104) and SN (102) (e.g., SCTP) is sufficiently good in terms of data transmission bandwidth, latency / jitter, and reliability, SN (102) may request MN (104) to support SN (102) in the area of ​​intelligence support services. MN (104) may provide additional training data to SN (102) to facilitate training SN (102)'s AI intelligence model. Alternatively or additionally, MN (104) may use its AI intelligence model to support performing predictive actions, such as performing NLP on text data received from SN (102) or performing speech recognition on audio data received from SN (102).

[0040] SN (102) may send a "SN Intelligence Resource Needed" message to MN (104), which may include information requesting MN (104) to allocate expected intelligence resources and, upon approval, start an intelligence support operation (802). Upon receiving the "SN Intelligence Resource Needed" message and accepting the request, MN (104) allocates corresponding intelligence resources, such as MN (104)'s local AI intelligence model and training data for training SN (102)'s AI intelligence model, to provide an authorized intelligence support service. Subsequently, MN (104) may send a "SN Intelligence Resource Confirmed" message to SN (102) containing information regarding the allocation of intelligence resources (806). In this way, a joint intelligence service between MN (104) and SN (102) can be established.

[0041] During the joint intelligence service, the SN (102) may, for example, send one or more "MN Intelligence Data Update" messages to the MN (104) (810). The "MN Intelligence Data Update" messages may include, for example, relevant information about training data that the SN (102) expects and / or relevant data to be processed by the AI ​​intelligence model of the MN (104), such as text data for NLP and audio data for speech recognition. The MN (104) may perform corresponding intelligence support actions based on the information in the "MN Intelligence Data Update" messages. Then, the MN (104) may send corresponding "MN Intelligence Data Update" messages to the SN (102) (812). The corresponding "MN Intelligence Data Update" messages may include, for example, expected training data and / or prediction results generated by the AI ​​intelligence model of the MN (104). For example, SN (102) may leverage training data from MN (104) to improve its intelligence model and / or prediction results from MN (104) to obtain the final result of the intelligence service for UE (106). SN (102) may transmit to UE (106) the final result, i.e., user data, obtained from the joint intelligence service and related processing by MN (104) and SN (102) (814).

[0042] If SN (102) does not require intelligence support from MN (104), SN (102) may send a “MN Intelligence Resource Release” message to MN (104) that may include information requesting MN (104) to release / revoke previously allocated intelligence resources (816). In response, MN (104) may stop intelligence support by releasing and revoking the allocated intelligence resources. Following the termination of the joint non-radio communication service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0043] FIG. 9 illustrates an exemplary implementation (900) for jointly providing storage support services to a UE. In the implementation (900), the MN (104) and SN (102) may jointly provide radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over the wireless. Meanwhile, the MN (104) may provide storage support services to the UE (106). The storage support services may allow the UE (106) to store user data online, which eliminates the need for the UE to maintain a large amount of memory space locally. If the local storage capacity of the MN (104) is limited, for example, due to the large amount of data existing for MEC applications, the MN (104) may choose to store this data in an upstream cloud database or request other WANNs, such as the SN (102), for storage support. When the capability and quality of the TNL signaling connection between MN (104) and SN (102) (e.g., SCTP) is sufficiently good in terms of data transmission bandwidth, latency / jitter and reliability, MN (104) may request SN (102) to support MN (104) in the storage area.

[0044] MN (104) may send a “SN storage resource request” message to the serving SN (102), which may include information requesting the SN (102) to allocate expected storage resources and, upon approval, start storage support operations (902). Upon receiving the “SN storage resource request” message and accepting the request, the SN (102) may allocate corresponding storage resources and provide the allowed capacity in the storage area. Subsequently, the SN (102) may send a “SN computing resource request acknowledgment” message to the MN (104), which includes information regarding the resource allocation of storage resources, for example, the amount of allocated storage space (906). In this way, a joint storage service between the MN (104) and the SN (102) can be established.

[0045] During the shared storage service, the MN (104) may, for example, send one or more "SN storage intermediate data updates" to the SN (102) (910). The "SN storage intermediate data updates" messages may include relevant user data of the UE (106) to be stored online, for example, mobile edge multimedia cache data. The SN (102) may, for example, perform a corresponding storage support operation using the storage space allocated to store the UE (106)'s user data. Then, the SN (102) may send corresponding "SN storage intermediate data updates" messages to the MN (104) containing relevant information regarding the results of the data storage operation, such as the success or failure of data storage (912). The MN (104) may notify the UE (106) of the results of the data storage operation (914). In some implementations, when MN (104) acquires sufficient spare storage resources, SN (102) can transfer the stored user data of UE (106) back to MN (104) for storage via “SN storage intermediate data update” messages.

[0046] If MN (104) does not require storage support from SN (102), MN (104) may send a “SN storage resource release” message to SN (102) that may include information requesting SN (102) to release / revolve previously allocated storage resources (916). In response, SN (102) may stop storage support by releasing and revolving the allocated storage resources. Following the termination of the joint storage service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0047] FIG. 10 illustrates an exemplary implementation (1000) for jointly providing storage support services to a UE. In the implementation (1000), the SN (102) and MN (104) may jointly provide radio communication services to the UE (106) in a dual connection mode, for example, through separate MCG / SCG radio links over the wireless. Meanwhile, the SN (102) may provide storage support services to the UE (106). The storage support services may allow the UE (106) to store user data online, which eliminates the need for the UE to maintain a large amount of memory space locally. If the local storage capacity of the SN (102) is limited, for example, due to the large amount of data existing for MEC applications, the SN (102) may choose to store this data in an upstream cloud database or request other WANNs, such as the MN (104), for storage support. When the capability and quality of the TNL signaling connection between MN (104) and SN (102) (e.g., SCTP) is sufficiently good in terms of data transmission bandwidth, latency / jitter and reliability, SN (102) may request MN (104) to support SN (102) in the storage area.

[0048] SN (102) may send a "SN storage resource needed" message to MN (104), which may include information requesting MN (104) to allocate expected storage resources and, upon approval, start storage support operations (1002). Upon receiving the "SN storage resource needed" message and accepting the request, MN (104) may allocate corresponding storage resources and provide the allowed capacity in the storage area. Afterward, MN (104) may send a "SN storage resource check" message to SN (102) containing information related to the allocation of storage resources, for example, the amount of allocated storage resources (906). In this way, a joint storage service between MN (104) and SN (102) can be established.

[0049] During the shared storage service, the SN (102) may, for example, send one or more "MN storage intermediate data update" messages to the MN (104) (1010). The "SN storage intermediate data update" messages may include relevant user data of the UE (106) to be stored online, for example, mobile edge multimedia cache data. The MN (104) may, for example, perform a corresponding storage support operation using storage resources allocated to store the UE (106)'s user data. Then, the MN (104) may send corresponding "MN storage data update" messages to the SN (102) including relevant information regarding the result of the data storage operation, for example, data storage success or failure (1012). The SN (102) may notify the UE (106) of the result of the data storage operation (1014).

[0050] If SN (102) does not require storage support from MN (104), SN (102) may send a “release MN storage resource” message to MN (104) that may include information requesting MN (104) to release / revolve previously allocated storage resources (1016). In response, MN (104) may stop storage support by releasing and revolving the allocated storage resources. Following the termination of the joint non-radio communication service between MN (104) and SN (102), the DC operation for the joint radio communication service between MN (104) and SN (102) may be maintained in an ongoing state if possible.

[0051] Throughout the specification and claims, terms may have nuances suggested or implied by the context beyond their explicitly stated meanings. Likewise, the phrase “in one embodiment / implementation” as used herein does not necessarily refer to the same embodiment, nor does the phrase “in another embodiment / implementation” as used herein refer to different embodiments. For example, the claimed subject matter is intended to include combinations of exemplary embodiments, wholly or partially.

[0052] Generally, terms may be understood at least in part from their usage in context. For example, terms such as “and,” “or,” or “and / or” as used herein may include various meanings that may depend at least in part on the context in which such terms are used. Typically, when “or” is used to associate a list such as A, B, or C, it is intended to mean A, B, and C as used here in an inclusive sense, as well as A, B, or C as used here in an exclusive sense. Additionally, the term “one or more” as used herein may, at least in part depending on the context, be used to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Likewise, terms such as “a,” “an,” or “the” may be understood to convey a singular usage or a plural usage, at least in part, depending on the context. Furthermore, the term "based on" may be understood as not necessarily intended to convey an exclusive set of elements, but instead may allow for the existence of additional elements that are not explicitly described, at least partially, depending on the context.

[0053] References throughout this specification to features, benefits, or similar language do not imply that all features and benefits that can be realized by the solution must be included or are included in any single implementation thereof. Rather, language referring to features and benefits is understood to mean that a specific feature, benefit, or characteristic described in relation to an embodiment is included in at least one embodiment of the solution. Accordingly, discussions of features and benefits and similar language throughout the specification may refer to the same embodiment, but are not necessarily so.

[0054] Additionally, the described features, benefits, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. A person skilled in the art will recognize, in light of the description in this specification, that the present solution may be implemented without one or more of the specific features or benefits of a particular embodiment. In other cases, additional features and benefits that may not be present in all embodiments of the present solution may be recognized in specific embodiments.

Claims

Claim 1 A method performed by a first wireless access network node serving user equipment in a wireless communication network, comprising the steps of: transmitting a request message for a non-radio resource of a second wireless access network node to the second wireless access network node; wherein the first wireless access network node requests the non-radio resource to support providing the non-radio communication service to the user equipment; and receiving a response message from the second wireless access network node allocating the non-radio resource to the user equipment. Claim 2 A method performed by a first wireless access network node serving a user device in a wireless communication network, wherein, in claim 1, the user device is in a dual connection state with the first wireless access network node and the second wireless access network node, and the first wireless access network node and the second wireless access network node provide a joint radio communication service to the user device. Claim 3 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in the dual connection above, the first wireless access network node is a master node and the second wireless access network node is a secondary node, or the first wireless access network node is a secondary node and the second wireless access network node is a master node. Claim 4 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in claim 1, the first wireless access network node is adjacent to the second wireless access network node, and the first wireless access network node and the second wireless access network node have a direct communication interface between them for information coordination. Claim 5 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in response to the reception of the response message in claim 1, the first non-radio-communication service support data update message including a task of the non-radio-communication service is transmitted to the second wireless access network node. Claim 6 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in claim 5, the method further comprises the step of receiving a second non-radio-communication service support data update message containing the result of the task from the second wireless access network node. Claim 7 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in claim 6, the task is included in the first non-radio-communication service support data update message in the form of a container, and the result of the task is included in the second non-radio-communication service support data update message in the form of a container. Claim 8 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in claim 1, a non-radio resource release message is transmitted to the second wireless access network node so that the second wireless access network node releases and revokes the non-radio resource allocated to the user equipment to terminate the joint non-radio communication service between the first wireless access network node and the second wireless access network node, and the dual connection operation for the joint radio communication service between the first wireless access network node and the second wireless access network node can be maintained even after the termination of the joint non-radio communication service. Claim 9 A method performed by a first wireless access network node serving user equipment in a wireless communication network, wherein, in claim 1, the non-radio-communication service comprises at least one of a computing support service, an intelligence support service, or a storage support service. Claim 10 A method performed by a first wireless access network node serving user equipment in a wireless communication network, further comprising the step of transmitting user data, which is the result of joint non-radio-communication services and related processing by the first wireless access network node and the second wireless access network node, to the user equipment in the first wireless access network node and the second wireless access network node. Claim 11 A method performed by a second wireless access network node in a wireless communication network, comprising the steps of: receiving a request message for a non-radio resource of the second wireless access network node from a first wireless access network node; wherein the first wireless access network node requests the non-radio resource to support providing both radio communication services and non-radio communication services to user equipment; and transmitting a response message allocating the non-radio resource to the first wireless access network node. Claim 12 A method performed by a second wireless access network node in a wireless communication network, wherein, in claim 11, the user equipment is in a dual connection state with the first wireless access network node and the second wireless access network node, and the first wireless access network node and the second wireless access network node provide a joint radio communication service to the user equipment. Claim 13 A method performed by a second wireless access network node in a wireless communication network, further comprising the step of allocating the non-radio resource to the user equipment in claim 11. Claim 14 A method performed by a second wireless access network node in a wireless communication network, wherein, in response to receiving from the first wireless access network node a first non-radio communication service support data update message including a task of the non-radio communication service, the second wireless access network node completes the task of the non-radio communication service using the non-radio resources allocated to the user equipment, and transmits to the first wireless access network node a second non-radio communication service support data update message including the result of the task. Claim 15 A method performed by a second wireless access network node in a wireless communication network, wherein, in response to receiving a non-radio resource release message from the first wireless access network node, the method further comprises the step of releasing and revocation the non-radio resource allocated to the user equipment to terminate a joint non-radio communication service between the first wireless access network node and the second wireless access network node, and wherein a dual connection operation for a joint radio communication service between the first wireless access network node and the second wireless access network node can be maintained even after the termination of the joint non-radio communication service. Claim 16 A device comprising: a memory operable to store computer-readable instructions; and a processor circuit operable to read said computer-readable instructions, wherein, upon execution of said computer-readable instructions: the processor circuit is configured to transmit, from a first wireless access network node serving user equipment in a wireless communication network to the second wireless access network node a request message for a non-radio resource of the second wireless access network node, wherein the first wireless access network node requests the non-radio resource to provide non-radio communication services to the user equipment and to support providing said non-radio communication services to the user equipment; and receive a response message from the second wireless access network node allocating said non-radio resource to the user equipment. Claim 17 A device according to claim 16, wherein the user equipment is in a dual connection state with the first wireless access network node and the second wireless access network node, such that the first wireless access network node and the second wireless access network node provide a joint radio communication service to the user equipment. Claim 18 A device according to claim 16, wherein the first wireless access network node is adjacent to the second wireless access network node, and the first wireless access network node and the second wireless access network node have a direct communication interface between them for information coordination. Claim 19 In paragraph 16, the processor circuit is also configured to transmit a first non-radio-communication service support data update message, including a task of the non-radio-communication service, to the second wireless access network node in response to the reception of the response message. Claim 20 In claim 16, the processor circuit is also configured to transmit a non-radio resource release message to the second wireless access network node so that the second wireless access network node releases and revokes the non-radio resource allocated to the user equipment to terminate the joint non-radio communication service between the first wireless access network node and the second wireless access network node, and the dual connection operation for the joint radio communication service between the first wireless access network node and the second wireless access network node can be maintained even after the termination of the joint non-radio communication service, the device.

Images