Management methods, devices, storage media, and electronic devices based on XR services

Abstract

This disclosure provides a management method, device, computer storage medium, and electronic device based on XR services, relating to the field of communication technology. The method includes: receiving a service request for a target XR service from an XREC, where the target XR service is an XR service that the XREC obtains from an XR client and requires execution by an XR user; based on the service request, a first XRES network element sends an AF analysis request for an AF network element to an ADAES network element via a NEF network element, so that the ADAES network element determines service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client; and based on the service requirement parameters, searching for a target AF network element that matches the service requirement parameters from a pre-registered AF list, so that the XR client establishes data communication with the target AF network element. This method can provide unified management of diverse XR services in a 5G network architecture, thereby improving management efficiency while reducing management costs.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a management method, a management device, a computer storage medium, and an electronic device based on XR services. Background Technology

[0002] With the rapid development of computer and communication technologies, virtual reality devices are increasingly permeating people's daily lives. Existing extended reality (XR) hardware and software devices are diverse, but they cannot be efficiently integrated into a unified standard device. Therefore, the existing 5G network architecture lacks the capability to support and uniformly manage XR services. The diverse nature of XR services requires designers to specialize network elements in the 5G core network, impacting management efficiency. Furthermore, matching network element services and network architecture are needed for XR services, leading to high management costs.

[0003] Therefore, there is an urgent need for a method that is efficient and cost-effective in managing diverse XR businesses. Summary of the Invention

[0004] This disclosure provides a management method, a management device, a computer storage medium, and an electronic device based on XR services, thereby enabling unified management of diverse XR services in a 5G network architecture, which improves management efficiency while reducing management costs.

[0005] In a first aspect, one embodiment of this disclosure provides a management method based on XR services, applied to a first Extended Reality Enabled Service (XRES) network element that performs Extended Reality (XR) service management. The method includes: receiving a service request for a target XR service from an Extended Reality Enabled Client (XREC), wherein the target XR service is an XR service to be executed obtained by the XREC from an XR client; based on the service request, the first XRES network element sends an AF analysis request for an Application Function (AF) network element to an Application Data Analysis Service (ADAES) network element via a Network Open Function (NEF) network element, so that the ADAES network element determines the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client; and based on the service requirement parameters, searching for a target AF network element that meets the service requirement parameters from a pre-registered AF list, so that the XR client establishes data communication with the target AF network element.

[0006] In one optional embodiment of this disclosure, the service requirement parameters include one or more of the following: the maximum service bandwidth that the XR client can handle under the current network parameters, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

[0007] In an optional embodiment of this disclosure, after receiving a service request for a target XR service from the XREC, the method further includes: verifying the legality of the service request and verifying the feasibility of the XR client executing the target XR service; if the service request is legal and the feasibility verification passes, a success message is sent to the XREC; if the service request is illegal or the feasibility verification fails, a failure message is sent to the XREC.

[0008] In an optional embodiment of this disclosure, the method further includes: in response to receiving an XREC registration request sent by an XREC, determining the legitimacy of the identity information corresponding to the XREC; if the XREC is legitimate, allocating user identification information to the XREC and constructing a user configuration table corresponding to the user identification information, so that the AF analysis request includes the user identification information; wherein, the user configuration table includes one or more of the following configuration information:

[0009] User identification information corresponds to the software and hardware configuration information of the XR client;

[0010] User identification information corresponds to the mobility information of the XR client;

[0011] User identification information corresponds to the business synchronization requirements between XR clients.

[0012] In an optional embodiment of this disclosure, the method further includes: in response to the operation of switching from the first XRES network element to the second XRES network element, migrating the migration information of the XREC in the first XRES network element to the second XRES network element, wherein the migration information includes the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information.

[0013] In one optional embodiment of this disclosure, searching for a target AF network element that meets the service requirement parameters from a pre-registered AF list based on the service requirement parameters includes: searching for multiple initial AF network elements that meet the service requirement parameters from the pre-registered AF list based on the service requirement parameters, and determining the AF network element with the lowest bandwidth occupancy rate among the multiple initial AF network elements as the target AF network element.

[0014] In an optional embodiment of this disclosure, the method further includes: detecting communication quality parameters between the XR client and the target AF network element, disconnecting data communication between the XR client and the target AF network element when the parameter value of the communication quality parameter is less than a parameter threshold, and searching for other target AF network elements that meet the service requirement parameters, so as to establish data communication between the XR client and other target AF network elements.

[0015] Secondly, one embodiment of this disclosure provides a management device based on XR services, applied to a first Extended Reality Enabled Service (XRES) network element that performs Extended Reality (XR) service management. The device includes: a request receiving module, configured to receive a service request for a target XR service from an Extended Reality Enabled Client (XREC), wherein the target XR service is an XR service that the XREC obtains from an XR client and is required to be executed by an XR user; a parameter determination module, configured to, based on the service request, send an AF analysis request for an Application Function (AF) network element to an Application Data Analysis Service (ADAES) network element via a Network Open Function (NEF) network element, so that the ADAES network element determines service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client; and an AF network element lookup module, configured to, based on the service requirement parameters, look up a target AF network element that meets the service requirement parameters from a pre-registered AF list, so that the XR client can establish data communication with the target AF network element.

[0016] In one optional embodiment of this disclosure, the service requirement parameters include one or more of the following: the maximum service bandwidth that the XR client can handle under the current network parameters, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

[0017] In an optional embodiment of this disclosure, the device may further include a verification module and an information sending module. The verification module is used to verify the legality of the service request and the feasibility of the XR client executing the target XR service. The information sending module is used to send a success message to the XREC when the service request is legal and the feasibility verification is passed. The information sending module is used to send a failure message to the XREC when the service request is illegal or the feasibility verification is failed.

[0018] In an optional embodiment of this disclosure, the apparatus may further include a request sending module and an identifier allocation module; the request sending module is used to determine the legitimacy of the identity information corresponding to the XREC in response to receiving an XREC registration request sent by the XREC; the identifier allocation module is used to allocate user identifier information to the XREC when the XREC is legitimate, and construct a user configuration table corresponding to the user identifier information, so that the AF analysis request includes the user identifier information;

[0019] The user configuration table contains one or more of the following configuration information:

[0020] User identification information corresponds to the software and hardware configuration information of the XR client;

[0021] User identification information corresponds to the mobility information of the XR client;

[0022] User identification information corresponds to the business synchronization requirements between XR clients.

[0023] In an optional embodiment of this disclosure, the device may further include an information migration module; the information migration module is configured to migrate the migration information of the XREC in the first XRES network element to the second XRES network element in response to the operation of switching from the first XRES network element to the second XRES network element, the migration information including the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information.

[0024] In an optional embodiment of this disclosure, the AF network element lookup module is specifically used to search for multiple initial AF network elements that meet the service requirement parameters from a pre-registered AF list based on the service requirement parameters, and to determine the AF network element with the lowest bandwidth occupancy rate among the multiple initial AF network elements as the target AF network element.

[0025] In an optional embodiment of this disclosure, the device may further include a communication quality detection module; the communication quality detection module is used to detect the communication quality parameters between the XR client and the target AF network element, so as to disconnect the data communication between the XR client and the target AF network element when the parameter value of the communication quality parameter is less than the parameter threshold, and to find other target AF network elements that meet the service requirement parameters, so as to establish data communication between the XR client and other target AF network elements.

[0026] Thirdly, one embodiment of this disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described XR-based service management method.

[0027] Fourthly, one embodiment of this disclosure provides an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-described XR-based service management method by executing the executable instructions.

[0028] Fifthly, one embodiment of this disclosure provides a computer program product, including a computer program that is executed by a processor to implement the above-described XR-based service management method.

[0029] The technical solution disclosed herein has the following beneficial effects:

[0030] The aforementioned XR service-based management method receives service requests for a target XR service from the Extended Reality Enabled Client (XREC), where the target XR service is the XR service that the XREC needs to execute from the XR client. Based on the service request, the first XRES network element sends an AF analysis request for an Application Function (AF) network element to the Application Data Analysis Service (ADAES) network element via the Network Open Function (NEF) network element. This allows the ADAES network element to determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client. Based on these service requirement parameters, the method searches a pre-registered AF list for a target AF network element that matches the service requirement parameters, enabling the XR client to establish data communication with the target AF network element. On one hand, this method improves the management efficiency and effectiveness of diverse XR services by uniformly receiving and managing XR service requests through the first XRES network element. Furthermore, by analyzing the current network parameters during XR service operation through the ADAES network element, the operational requirements of the XR service can be determined. Then, target AF network elements matching the service requirements parameters are identified from the AF list to establish data channels. This allows for the allocation of appropriate AF network elements for XR service operation, thereby improving resource utilization and the effectiveness of XR service operation, optimizing network scheduling processes, and ultimately enhancing the user experience of XR services. On the other hand, allocating appropriate AF network elements for XR service operation through the XRES network element can also avoid network congestion and burden caused by high-volume XR services, thus improving network load and maintaining system stability.

[0031] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0032] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0033] Figure 1 This schematically illustrates an application architecture diagram of a management system based on XR services in one of the exemplary embodiments of this invention.

[0034] Figure 2 The flowchart illustrates one of the XR-based service management methods in this exemplary embodiment.

[0035] Figure 3 This schematic diagram illustrates one of the XREC registration processes in an XRES network element according to this exemplary embodiment.

[0036] Figure 4 This schematic diagram illustrates a flowchart of one of the overall XR service management methods in this exemplary embodiment;

[0037] Figure 5 This schematic diagram illustrates the structure of a management device based on XR services in this exemplary embodiment.

[0038] Figure 6 The schematic diagram illustrates the structure of an electronic device in this exemplary embodiment. Detailed Implementation

[0039] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of exemplary embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0040] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0041] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all steps. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0042] To help those skilled in the art better understand the technical solutions provided in the embodiments of this disclosure, the relevant content involved in the technical solutions of this disclosure will be introduced below.

[0043] 1) Extended Reality (XR): This is a collection of virtual and real technologies, typically including Virtual Reality (VR), Augmented Reality (AR), and Mixed Reality (MR). XR technology transforms human interaction from 2D to a more efficient 3D interaction. VR simulates the real world through hardware and software; AR overlays information and images onto the real world using various devices; and MR enables real-time interaction between the virtual and real worlds through digital technology.

[0044] 2) Application Data Analytics Server (ADAES): In this embodiment, the ADAES network element is a network element in the 5G network architecture that has data analysis capabilities.

[0045] 3) Extended Reality Enable Server (XRES): The XRES network element in this embodiment is used to collect and analyze the XR service requirements of users in order to manage the diverse XR services in a unified manner.

[0046] 4) Extended Reality Enable Client (XREC): In this embodiment, the XREC client is used to collect users' XR service requirements from the XR client.

[0047] In the relevant technological context, with the rapid development of computer and communication technologies, the application of virtual reality devices is increasingly permeating people's daily lives. Existing extended reality (XR) hardware and software devices are diverse, but they cannot be efficiently integrated into a unified standard device. Therefore, the existing 5G network architecture lacks the capability to support and uniformly manage XR services. Furthermore, the diverse nature of XR services requires designers to specialize network elements in the 5G core network, providing dedicated network element services and network architectures for these services. This impacts the management efficiency of XR services and results in high management costs.

[0048] Therefore, there is an urgent need for efficient and cost-effective management methods for diverse XR services.

[0049] This exemplary embodiment addresses the aforementioned problems and proposes a management method based on XR services. This method provides an enabling network architecture for XR services, enabling unified management of diverse XR services. Specifically, in this enabling network architecture, XRES network elements are used to uniformly receive and manage XR service requests, thereby improving the management efficiency and effectiveness of diverse XR services. Furthermore, ADAES network elements analyze the current network parameters during XR service operation to determine the operational requirements of the XR services. Target AF network elements matching the service requirement parameters are then located in the AF list to establish data channels. This allows for the allocation of appropriate AF network elements for XR service operation, improving resource utilization and the effectiveness of XR service operation, optimizing network scheduling processes, and ultimately enhancing the user experience of XR services. On the other hand, allocating appropriate AF network elements for XR service operation through XRES network elements can also avoid network congestion and burden caused by high-volume XR services, thus improving network load and maintaining system stability.

[0050] For ease of understanding, this disclosure proposes a management method and apparatus based on XR services, which can be applied to... Figure 1 In the system architecture of the exemplary application environment shown.

[0051] like Figure 1 As shown, the system architecture 100 may include terminal equipment 101, UPF (User Plane Function) network element 102, PCF (Policy Control Function) network element 103, NEF (Network Exposure Function) network element 104, ADAES (Application Data Analytics Server) network element 105, XRES network element 106, and AF (Application Function) network element 107 in the 3GPP network architecture.

[0052] The terminal device 101 includes an XR client 1011 and an XREC 1012. The XR client 1011 runs on the terminal device 101, allowing users to log in using their corresponding user accounts and trigger service requests for the target XR service. The XREC 1012 collects the service requests for the target XR service from the XR client 1011 and then sends the service request for the target XR service to the XRES network element 106.

[0053] XRES network element 106 receives a service request for a target XR service and sends an AF analysis request for AF network element 107 to ADAES network element 105 via NEF network element 104. This allows ADAES network element 105 to determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to XR client 1011. ADAES network element 105 then sends the AF analysis results to XRES network element 106 via NEF network element 104 to inform XRES network element 106 of the service requirement parameters related to the target XR service. XRES network element 106 then iterates through the pre-registered AFs on the server according to the received service requirement parameters to find the target AF network element that meets the service requirement parameters. This enables XR client 1011 to establish a data transmission channel with the target AF network element based on UPF network element 102 and to request session resources from PCF network element 103 to realize data communication functions.

[0054] The terminal device 101 can be, for example, a smartphone, a PDA, a laptop, a server, a desktop computer, or any other computing device with network connectivity, but is not limited to these. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The network is the medium used to provide communication links between the terminal device 101, network elements, and the server. The network can include various connection types, such as wired and wireless communication links or fiber optic cables, but is not limited to these.

[0055] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, network elements, and servers can be included, and the embodiments of this disclosure do not impose any special limitations on this.

[0056] However, those skilled in the art will readily understand that the above application scenarios are merely illustrative and are not intended to limit the scope of this exemplary embodiment.

[0057] The following example uses the aforementioned XRES network element as the execution subject to illustrate how the XR service-based management method is applied to the XRES network element. Figure 2 This schematically illustrates a flowchart of one of the XR-based service management methods in this exemplary embodiment. Please refer to [link / reference]. Figure 2The XR service-based management method provided in this embodiment includes the following steps S201-S203:

[0058] Step S201: Receive a service request for a target XR service from the Extended Reality Enabled Client XREC. The target XR service is the XR service that XREC obtains from the XR client and needs to be executed.

[0059] Step S202: According to the service request, the first XRES network element sends an AF analysis request for the application function AF network element to the application data analysis service ADAES network element through the network open function NEF network element, so that the ADAES network element can determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client.

[0060] Step S203: Based on the business requirement parameters, find the target AF network element that meets the business requirement parameters from the pre-registered AF list so that the XR client can establish data communication with the target AF network element.

[0061] In some embodiments of this disclosure, the technical solutions provided involve receiving service requests for target XR services from an Extended Reality Enabled Client (XREC). The target XR service is the XR service that the XREC obtains from the XR client and needs to be executed. Based on the service request, the first XRES network element sends an AF analysis request for an Application Function (AF) network element to the Application Data Analysis Service (ADAES) network element via a Network Open Function (NEF) network element. This allows the ADAES network element to determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client. Based on the service requirement parameters, the ADAES network element searches a pre-registered AF list for a target AF network element that matches the service requirement parameters, enabling the XR client to establish data communication with the target AF network element. On one hand, this method improves the management efficiency and effectiveness of diverse XR services by uniformly receiving and managing service requests for XR services through the first XRES network element. Furthermore, by analyzing the current network parameters during XR service operation through the ADAES network element, the operational requirements of the XR service can be determined. Then, target AF network elements matching the service requirements parameters are identified from the AF list to establish data channels. This allows for the allocation of appropriate AF network elements for XR service operation, thereby improving resource utilization and the effectiveness of XR service operation, optimizing network scheduling processes, and ultimately enhancing the user experience of XR services. On the other hand, allocating appropriate AF network elements for XR service operation through the XRES network element can also avoid network congestion and burden caused by high-volume XR services, thus improving network load and maintaining system stability.

[0062] The following will describe in conjunction with specific embodiments Figure 2 The specific implementation methods of each step in the illustrated embodiment are described in detail below:

[0063] In step S201, a service request for a target XR service is received from the Extended Reality Enabled Client XREC. The target XR service is the XR service that XREC obtains from the XR client and needs to be executed.

[0064] In this process, by running an XR client on a terminal device, users can log in to the XR client with their user accounts and trigger corresponding target XR services. The XREC then retrieves the service requirements of the target XR service from the XR client. XR services can be, for example, VR sessions, AR rendering, virtual reality game interaction, or any other services involving virtual or reality technologies; this disclosure does not exhaustively list them all.

[0065] The business request includes the business type of the target XR business.

[0066] For example, after XREC collects the target XR service that the user needs to perform from the XR client, it sends a service request for the target XR service to the XRES network element, and the XRES network element can then receive the service request for the target XR service.

[0067] Before the XRES network element receives the service request for the target XR service from the XREC in step S201 above, the XREC needs to be pre-registered in the XRES network element in order to carry out the information communication process between the XREC client and the XRES network element.

[0068] Figure 3 This schematic diagram illustrates one of the XREC registration processes in an XRES network element according to this exemplary embodiment. Please refer to [link / reference]. Figure 3 The XREC registration process provided in the embodiments of this disclosure includes the following steps S301-S304:

[0069] Step S301: Send an XREC registration request.

[0070] For example, the XREC sends an XREC registration request to the XRES network element. The XREC registration request includes the configuration information (e.g., software and hardware configuration information) of the XR user corresponding to the XREC, as well as the mobility information of the XR user. The XREC registration request can be for a single XR user or for a group of multiple users. When the XREC registration request is for a group of multiple users, it also needs to include synchronization requirement information between the multiple user services, such as "whether to synchronize information between multiple user groups."

[0071] Step S302: Verification of the legitimacy of the identity information corresponding to XREC.

[0072] In one optional embodiment, the XRES network element, upon receiving an XREC registration request from the XREC, determines the legitimacy of the identity information corresponding to the XREC.

[0073] For example, in step S302, the identity information of XREC is verified to determine whether XREC is a legitimate user. For example, the legitimacy of the identity corresponding to XREC can be determined through a whitelist or other methods, and this embodiment of the disclosure does not impose any special limitations on this.

[0074] If XREC is valid, proceed to step S303: assign user identification information to XREC and construct a user configuration table corresponding to the user identification information.

[0075] The user configuration table contains one or more of the following configuration information:

[0076] User identification information corresponds to the software and hardware configuration information of the XR client;

[0077] User identification information corresponds to the mobility information of the XR client;

[0078] User identification information corresponds to the business synchronization requirements between XR clients.

[0079] The business synchronization requirement information indicates that XREC is registered as a multi-user group. This information determines whether information synchronization is required within the multi-user group. If synchronization is not required, a new data channel needs to be established; otherwise, if synchronization is required, a new data channel can be established to continue data transmission.

[0080] The user identification information can be the XREC's Identity Document (ID).

[0081] For example, if XREC is registered as a multi-user group, the user identification information assigned to XREC in step S303 can be multiple user IDs for each user in the multi-user group.

[0082] For example, assigning user identification information to XREC facilitates the sending of XREC's user identification information when XRES network elements send AF analysis requests to ADAES network elements via NEF network elements.

[0083] Conversely, if XREC is invalid, the registration request for XREC will be rejected.

[0084] Based on the above embodiments, after determining the above registration result, the XRES network element can execute step S304 and send the XREC registration result reply information.

[0085] The XREC registration result includes whether the registration was successful or failed.

[0086] For example, if XREC registration is successful, the XRES network element will send a registration success identifier to XREC, along with the assigned user identification information. To improve the user experience, the reason for registration failure can also be sent to XREC if registration fails.

[0087] Through the above embodiments, the registration process of XREC clients in XRES network elements has been improved in the enabling network architecture for XR services, so as to provide a basis for establishing data channels for the subsequent allocation of corresponding AFs for XR services, and further improve the unified management process for diverse XR services.

[0088] Continuing to focus on step S201, in an optional embodiment, after receiving the service request for the target XR service from the XREC in step S201, the XRES network element first needs to verify the legality of the service request and verify the feasibility of the XR client executing the target XR service; when the service request is legal and the feasibility verification passes, a success message is sent to the XREC; when the service request is illegal or the feasibility verification fails, a failure message is sent to the XREC.

[0089] For example, after the XRES network element receives a service request for a target XR service from the XREC, it verifies the validity of the service request and analyzes whether the software and hardware configurations of the XR client meet the service requirements for executing the target XR service. For instance, if the target XR service is a VR session service, it needs to verify whether the XR client is configured with a VR device and has session software configuration, etc.

[0090] If the business request is valid and the XR client's feasibility verification passes, a success message can be sent to the XREC, and the following step S202 can continue. Conversely, if the business request is invalid or the XR client's feasibility verification fails, a failure message can be sent to the XREC, and the identification information may include the reason for the failure. For example, if the XR client's feasibility verification fails specifically because the VR device is not connected, a message "No VR device connected, unable to conduct VR session" can be sent to the XREC client.

[0091] It should be explained that the content of the above prompts is merely exemplary, and can be adjusted according to actual needs. The embodiments disclosed herein do not impose any special limitations on this.

[0092] In step S202, according to the service request, the first XRES network element sends an AF analysis request for the application function AF network element to the application data analysis service ADAES network element via the network open function NEF network element, so that the ADAES network element can determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client.

[0093] Among them, the ADAES network element is a network element that determines the service requirement parameters of the target XR service based on the current network parameters corresponding to the XR client.

[0094] For example, the XRES network element shown in any of the above embodiments is the first XRES network element. After the XRES network element receives a service request for the target XR service from the XREC, it can send an AF analysis request for the application function AF network element to the application data analysis service ADAES network element via the NEF network element according to the service request. After receiving the AF analysis request, the ADAES network element determines the service requirement parameters that meet the target XR service based on the current network parameters of the XR client.

[0095] In one optional embodiment of this disclosure, the service requirement parameters include one or more of the following: the maximum service bandwidth that the XR client can handle under the current network parameters, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

[0096] For example, the ADAES network element determines the service requirement parameters that the target XR service needs to meet based on the current network parameters of the XR client, namely, one or more of the maximum service bandwidth that the XR client can bear, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

[0097] In step S203, based on the service requirement parameters, a target AF network element that meets the service requirement parameters is found from the pre-registered AF list so that the XR client can establish data communication with the target AF network element.

[0098] For example, based on the service requirement parameters required for the operation of the target XR service, an AF network element that can meet the above service requirement parameters can be found from the AF list pre-registered by the server, so as to use it as the target AF network element, and then send the information of the target AF network element to the XR client, so that the XR client can establish a data channel with the target AF network element through the UPR network element.

[0099] In one embodiment, if the AF list contains multiple AF network elements that meet the above-mentioned service requirement parameters, then one AF network element can be selected as the target AF network element from among the multiple AF network elements that meet the above-mentioned service requirement parameters. The following will describe this in conjunction with specific embodiments:

[0100] In one optional embodiment of this disclosure, based on service requirement parameters, multiple initial AF network elements that meet the service requirement parameters are searched from a pre-registered AF list, and the AF network element with the lowest bandwidth occupancy rate among the multiple initial AF network elements is determined as the target AF network element.

[0101] For example, when the AF list contains multiple initial AF network elements that meet the above service requirement parameters, the AF network element with the lowest bandwidth utilization can be identified as the target AF network element to minimize bandwidth consumption from the perspective of resource consumption, thereby improving resource utilization.

[0102] In addition to the above embodiments, other methods can be used to determine a target AF network element from multiple initial AF network elements that meet the service requirement parameters, such as random determination or methods where the provided service requirement parameters are not significantly different from the service requirement parameters required by the target XR service, in order to improve resource utilization and avoid resource idleness.

[0103] Based on the above embodiments, a data transmission channel is constructed between the XR client and the target AF network element. Session resources can be requested from the PCF network element to create a session between the XR client and the target AF network element. Furthermore, in this embodiment, the session quality between the XR client and the target AF network element can be monitored in real time.

[0104] In one optional embodiment of this disclosure, the communication quality parameters between the XR client and the target AF network element are detected. If the parameter value of the communication quality parameter is less than the parameter threshold, the data communication between the XR client and the target AF network element is disconnected, and other target AF network elements that meet the service requirement parameters are searched to establish data communication between the XR client and other target AF network elements.

[0105] For example, if the communication quality parameter value between the XR client and the target AF network element is less than the parameter threshold, it indicates that the current target AF network element cannot meet the service requirement parameters of the target XR service. In this case, the data communication between the XR client and the target AF network element can be disconnected, so that other AF network elements can be searched from the pre-registered AF list, and then the XR client can re-establish data communication with other target AF network elements.

[0106] Through the above embodiments, it can be ensured that the AF network element that establishes a connection with the target XR service can meet the service requirements of the target XR service, thereby improving the reliability and real-time performance of XR service management.

[0107] Furthermore, based on any of the above embodiments, XREC can also select to switch the XRES network element currently connected to it, for example, in the following embodiment, switching from the first XRES network element to the second XRES network element.

[0108] In an optional embodiment of this disclosure, in response to switching from the first XRES network element to the second XRES network element, the migration information of the XREC in the first XRES network element is migrated to the second XRES network element. The migration information includes at least the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information.

[0109] The context information is used to record the interaction progress between the XREC and the first XRES network element.

[0110] For example, when an XREC needs to switch to an XRES network element, that is, switch from the first XRES network element to the second XRES network element, the migration information of the XREC located in the first XRES network element can be transferred to the second XRES network element, so that the XREC can continue to operate in the second XRES network element based on the interaction information with the first XRES network element, without having to re-establish the communication connection in the second XRES network element.

[0111] This embodiment allows for the seamless transition between XREC and XRES network elements without the need to re-establish connections. Instead, it enables the inheritance of the interaction process with the original XRES network element, thereby improving the efficiency of XR service implementation.

[0112] The following will refer to Figure 4 The entire XR-based service management process of the exemplary embodiment of the present disclosure will be described in detail.

[0113] Figure 4 This schematic diagram illustrates a flowchart of one exemplary embodiment of a method for managing overall XR services; see reference. Figure 4 As shown, taking the target XR service as a VR session as an example, firstly, in an optional embodiment of this disclosure, the XREC sends an XREC registration request to the XRES network element in advance, that is, performs step S401 and sends the XREC registration request.

[0114] For example, the XREC registration request includes the XR user's configuration information (such as software and hardware information) and the user's mobility information. When XREC is registered as a multi-user group, the group provides additional information on the synchronization requirements of multi-user services in addition to the above information.

[0115] After receiving the registration request, XRES will perform step S402 to verify the legality of XREC.

[0116] If XREC is valid, then proceed to step S403: allocate user identification information to XREC and construct the user configuration table corresponding to the user identification information.

[0117] For example, by assigning user identification information and constructing a user configuration table corresponding to the user identification information, the user identification information can be included in the AF analysis request subsequently sent by the XRES network element to the ADAES network element.

[0118] In an optional embodiment of this disclosure, the XR client executes step S404 to initiate the target XR service. That is, the XR client initiates a VR session service, while the XREC client collects the service requirements of the VR session service from the XR client and executes step S405 to send the service request of the target XR service to the XRES network element.

[0119] The XRES network element receives a service request for the target XR service from the XREC and then executes step S406 to verify the legality of the service request and the feasibility of the XR client.

[0120] For example, the legality of the business request is verified, and the feasibility of the XR client executing the target XR business is verified, that is, whether the software configuration and hardware configuration of the XR client meet the business requirements of the target XR business.

[0121] If the business request is valid and the feasibility verification passes, proceed to step S4071 and send a success message. Conversely, if the business request is invalid or the feasibility verification fails, proceed to step S4072 and send a failure message.

[0122] After the business request is deemed legitimate and its feasibility is verified, step S408 can be executed to send an AF analysis request to the ADAES network element via the NEF network element.

[0123] When the ADAES network element receives the AF analysis request, it executes step S409 to determine the service requirement parameters that meet the target XR service based on the current network parameters of the XR client.

[0124] In one optional embodiment of this disclosure, the service requirement parameters for satisfying the target XR service can be the maximum service bandwidth that the XR client can handle in the current network environment, the corresponding actual allocated bandwidth parameters, and the QoS configuration required by the service, etc.

[0125] Then, the ADAES network element performs step S410 and sends the AF analysis results to the XRES network element via NEF. For example, the AF analysis results include the service requirement parameters that need to meet the target XR service.

[0126] When the XRES network element receives the AF analysis results sent by the ADAES network element, it can search for the target AF network element that matches the service requirement parameters from the pre-registered AF list based on the service requirement parameters in the AF analysis results, that is, execute step S411 to search for the target AF network element.

[0127] Before executing step S411, step S4110 and pre-registration need to be executed first.

[0128] This means that multiple AF network elements need to be registered in advance on the server so that their corresponding service parameters can be updated to the XRES network element in real time, so that the XRES network element can find the target AF network element that meets the service requirement parameters from the pre-registered AF list.

[0129] In an optional embodiment of this disclosure, after the target AF network element is located, the XRES network element can perform step S412 and send the identification information of the target AF network element to the XR client.

[0130] Upon receiving the identification information of the target AF network element, the XR client establishes a data transmission channel with the target AF network element for data communication. This involves executing step S403, establishing the data channel. Simultaneously, the XR client requests session resources from the PCF network element via step S414. VR session services are then executed based on the requested session resources.

[0131] Furthermore, based on the above embodiments, when XREC needs to switch XRES network elements, it can obtain the required migration information from the original XRES network elements (i.e., if XREC is a newly registered user, it is not necessary to obtain migration information including XREC's user identification information, the user configuration table corresponding to the user identification information, and context information, so as to continue to realize the target XR service without re-registering and establishing a communication channel, thereby improving the efficiency of XR service management.

[0132] In order to implement the above-mentioned management method based on XR services, one embodiment of this disclosure provides a management device based on XR services. Figure 5 The schematic diagram illustrates a schematic architecture of a management device based on XR services.

[0133] The XR service-based management device 500 is applied to a first Extended Reality Enabled Service (XRES) network element that performs Extended Reality XR service management. The device includes a request receiving module 501, a parameter determination module 502, and an AF network element lookup module 503.

[0134] The request receiving module 501 is used to receive a service request for a target XR service from the Extended Reality Enabled Client (XREC). The target XR service is the XR service that the XREC obtains from the XR client and is required to be executed by the XR user. The parameter determination module 502 is used to send an AF analysis request for the Application Function (AF) network element to the Application Data Analysis Service (ADAES) network element via the Network Open Function (NEF) network element according to the service request, so that the ADAES network element can determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client. The AF network element lookup module 503 is used to look up the target AF network element that meets the service requirement parameters from the pre-registered AF list based on the service requirement parameters, so that the XR client can establish data communication with the target AF network element.

[0135] In one optional embodiment of this disclosure, the service requirement parameters include one or more of the following: the maximum service bandwidth that the XR client can handle under the current network parameters, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

[0136] In an optional embodiment of this disclosure, the device may further include a verification module and an information sending module. The verification module is used to verify the legality of the service request and the feasibility of the XR client executing the target XR service. The information sending module is used to send a success message to the XREC when the service request is legal and the feasibility verification is passed. The information sending module is used to send a failure message to the XREC when the service request is illegal or the feasibility verification is failed.

[0137] In an optional embodiment of this disclosure, the apparatus may further include a request sending module and an identifier allocation module; the request sending module is used to determine the legitimacy of the identity information corresponding to the XREC in response to receiving an XREC registration request sent by the XREC; the identifier allocation module is used to allocate user identifier information to the XREC when the XREC is legitimate, and construct a user configuration table corresponding to the user identifier information, so that the AF analysis request includes the user identifier information;

[0138] The user configuration table contains one or more of the following configuration information:

[0139] User identification information corresponds to the software and hardware configuration information of the XR client;

[0140] User identification information corresponds to the mobility information of the XR client;

[0141] User identification information corresponds to the business synchronization requirements between XR clients.

[0142] In an optional embodiment of this disclosure, the device may further include an information migration module; the information migration module is configured to migrate the migration information of the XREC in the first XRES network element to the second XRES network element in response to the operation of switching from the first XRES network element to the second XRES network element, the migration information including the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information.

[0143] In an optional embodiment of this disclosure, the AF network element lookup module 503 is specifically used to search for multiple initial AF network elements that meet the service requirement parameters from a pre-registered AF list based on the service requirement parameters, and to determine the AF network element with the lowest bandwidth occupancy rate among the multiple initial AF network elements as the target AF network element.

[0144] In an optional embodiment of this disclosure, the device may further include a communication quality detection module; the communication quality detection module is used to detect the communication quality parameters between the XR client and the target AF network element, so as to disconnect the data communication between the XR client and the target AF network element when the parameter value of the communication quality parameter is less than the parameter threshold, and to find other target AF network elements that meet the service requirement parameters, so as to establish data communication between the XR client and other target AF network elements.

[0145] The XR service-based management device 500 provided in this embodiment can execute the technical solution of the XR service-based management method in any of the above embodiments. Its implementation principle and beneficial effects are similar to those of the XR service-based management method. Please refer to the implementation principle and beneficial effects of the XR service-based management method. It will not be repeated here.

[0146] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the present invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the present invention described in the "Exemplary Methods" section above.

[0147] According to embodiments of the present invention, a program product for implementing the above-described method may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0148] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0149] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0150] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0151] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0152] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0153] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely hardware implementations, entirely software implementations (including firmware, microcode, etc.), or implementations combining hardware and software aspects, collectively referred to herein as “circuits,” “modules,” or “systems.”

[0154] The following reference Figure 6 To describe an electronic device 600 according to this embodiment of the present invention. Figure 6 The electronic device 600 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0155] like Figure 6 As shown, the electronic device 600 is presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including storage unit 620 and processing unit 610), and a display unit 640.

[0156] The storage unit stores program code, which can be executed by the processing unit 610 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 610 can perform actions such as... Figure 2 Steps S201 to S203 are shown in the figure.

[0157] Storage unit 620 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 6201 and / or cache memory 6202, and may further include a read-only memory (ROM) 6203.

[0158] Storage unit 620 may also include a program / utility 6204 having a set (at least one) program module 6205, such program module 6205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0159] Bus 630 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0160] Electronic device 600 can also communicate with one or more external devices 1000 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 600, and / or with any device that enables electronic device 600 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 650. Furthermore, electronic device 600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 660. As shown, network adapter 660 communicates with other modules of electronic device 600 via bus 630. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, Redundant Arrays of Independent Disks (RAID) systems, tape drives, and data backup storage systems.

[0161] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0162] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0163] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0164] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0165] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is defined only by the appended claims.

Claims

1. A management method based on XR services, characterized in that, The method, applied to a first Extended Reality Enabled Service (XRES) network element performing Extended Reality (XR) service management, includes: The Extended Reality Enabled Client (XREC) receives a service request for a target XR service, which is the XR service that the XREC obtains from the XR client and needs to execute. According to the service request, the first XRES network element sends an AF analysis request to the Application Data Analysis Service ADAES network element via the Network Open Function (NEF) network element, so that the ADAES network element can determine the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client. Based on the business requirement parameters, a target AF network element that matches the business requirement parameters is found from the pre-registered AF list, so that the XR client can establish data communication with the target AF network element.

2. The method according to claim 1, characterized in that, The service requirement parameters include one or more of the following: the maximum service bandwidth that the XR client can handle under the current network parameters, the actual bandwidth parameters, and the Quality of Service (QoS) parameters required by the target XR service.

3. The method according to claim 1, characterized in that, After receiving a service request for a target XR service from an Extended Reality Enabled Client (XREC), the method further includes: The legality of the business request is verified, and the feasibility of the XR client executing the target XR service is verified. If the business request is valid and the feasibility verification is successful, a success message is sent to the XREC. If the business request is invalid or the feasibility verification fails, a failure message is sent to the XREC.

4. The method according to claim 1, characterized in that, The method further includes: In response to receiving the XREC registration request sent by the XREC, the legitimacy of the identity information corresponding to the XREC is determined; If the XREC is valid, then user identification information is assigned to the XREC, and a user configuration table corresponding to the user identification information is constructed so that the AF analysis request includes the user identification information; The user configuration table contains one or more of the following configuration information: The user identification information corresponds to the software configuration information and hardware configuration information of the XR client; The user identification information corresponds to the mobility information of the XR client; The user identification information corresponds to the business synchronization requirements between XR clients.

5. The method according to claim 4, characterized in that, The method further includes: In response to the operation of switching from the first XRES network element to the second XRES network element, the migration information of the XREC in the first XRES network element is migrated to the second XRES network element. The migration information includes the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information.

6. The method according to claim 1, characterized in that, The step of searching for a target AF network element that matches the service requirement parameters from a pre-registered AF list includes: Based on the service requirement parameters, multiple initial AF network elements that meet the service requirement parameters are searched from the pre-registered AF list, and the AF network element with the lowest bandwidth occupancy rate among the multiple initial AF network elements is determined as the target AF network element.

7. The method according to claim 1 or 6, characterized in that, The method further includes: The communication quality parameters between the XR client and the target AF network element are detected. If the value of the communication quality parameter is less than the parameter threshold, the data communication between the XR client and the target AF network element is disconnected. Other target AF network elements that meet the service requirement parameters are then searched to establish data communication between the XR client and the other target AF network elements.

8. A management device based on XR services, characterized in that, A first Extended Reality Enabled Service (XRES) network element applied to perform Extended Reality (XR) service management, the apparatus comprising: The request receiving module is used to receive a service request for a target XR service from the Extended Reality Enabled Client (XREC), wherein the target XR service is the XR service that the XREC obtains from the XR client to be executed. The parameter determination module is used to send an AF analysis request for the application function AF network element to the application data analysis service ADAES network element via the network open function NEF network element according to the service request, so that the ADAES network element determines the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client. The AF network element lookup module is used to search for a target AF network element that matches the business requirement parameters from a pre-registered AF list, so that the XR client can establish data communication with the target AF network element.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the XR-based service management method according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the XR-based service management method according to any one of claims 1 to 7 by executing the executable instructions.

Images