Management method and device based on XR service, storage medium and electronic equipment

Abstract

The invention provides a management method based on an XR service, a management device based on the XR service, a computer storage medium and electronic equipment, and relates to the technical field of communication. The method comprises the following steps: receiving a service request for a target XR service from an XREC, wherein the target XR service is an XR service which is acquired by the XREC from an XR client and needs to be executed for an XR user; according to the service request, the first XRES network element sends an AF analysis request for an AF network element to an ADAES network element through an NEF network element, so that the ADAES network element determines a service demand parameter meeting the target XR service based on a current network parameter corresponding to the XR client; and based on the service demand parameter, searching a pre-registered AF list for a target AF network element conforming to the service demand parameter, so that the XR client establishes data communication with the target AF network element. According to the method, diversified XR services can be uniformly managed in a 5G network architecture, so that the management cost is reduced while the management efficiency is improved.

Description

Background Art

[0002] With the rapid development of computer and communication technology, the application of virtual reality devices continues to penetrate into people's daily lives. Among the existing devices, there are various extended reality (XR) hardware and software devices, but they cannot be efficiently integrated into a unified standard device. Therefore, the existing 5G network architecture does not have the function of supporting and uniformly managing XR services, and the diverse XR services require designers to specialize the network elements in the 5G core network, which affects the management efficiency of XR services, and also requires matching network element services and network architecture for XR services, which leads to higher management costs.

[0003] Therefore, there is an urgent need for a method that is efficient and has low management costs for diverse XR services. Summary of the invention

[0004] The present disclosure provides a management method based on XR services, a management device based on XR services, a computer storage medium and an electronic device, so as to uniformly manage diversified XR services in a 5G network architecture, thereby improving management efficiency and reducing management costs.

[0005] In the first aspect, an embodiment of the present disclosure provides a management method based on XR services, which is applied to a first extended reality enabling service XRES network element that performs extended reality XR service management, the method comprising: receiving a service request for a target XR service from an extended reality enabling client XREC, the target XR service being the XR service to be executed that the XREC obtains 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 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; 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 can establish data communication with the target AF network element.

[0006] In an optional embodiment of the present disclosure, the service demand parameters include one or more of the maximum service bandwidth that the XR client can bear 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 the present disclosure, after receiving a service request for a target XR service from an XREC, the method further includes: verifying the legitimacy 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, sending a success prompt message to the XREC; if the service request is not legal, or the feasibility verification fails, sending a failure prompt message to the XREC.

[0008] In an optional embodiment of the present disclosure, the method further includes: in response to receiving an XREC registration request sent by the XREC, determining the legitimacy of the identity information corresponding to the XREC; if the XREC is legal, assigning 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] The user identification information corresponds to the software configuration information and hardware configuration information of the XR client;

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

[0011] The user identification information corresponds to the business synchronization requirement information between XR clients.

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

[0013] In an optional embodiment of the present disclosure, based on the business demand parameters, a target AF network element that meets the business demand parameters is searched from a pre-registered AF list, including: based on the business demand parameters, multiple initial AF network elements that meet the business demand parameters are searched from a pre-registered AF list, and the AF network element with the smallest bandwidth occupancy among the multiple initial AF network elements is determined as the target AF network element.

[0014] In an optional embodiment of the present disclosure, the method also includes: detecting a communication quality parameter between the XR client and the target AF network element, disconnecting 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 a parameter threshold, and searching for other target AF network elements that meet the business requirement parameters to establish data communication between the XR client and the other target AF network elements.

[0015] In the second aspect, an embodiment of the present disclosure provides a management device based on XR services, which is applied to a first extended reality enabling service XRES network element that performs extended reality XR service management, and the device includes: a request receiving module, which is used to receive a service request for a target XR service from an extended reality enabling client XREC, and the target XR service is an XR service that is obtained by the XREC from the XR client and needs to be executed by the XR user; a parameter determination module, which is used to 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 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; an AF network element search module, which is used to search for a target AF network element that meets the service requirement parameters from a 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.

[0016] In an optional embodiment of the present disclosure, the service demand parameters include one or more of the maximum service bandwidth that the XR client can bear 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 the present disclosure, the device may also include a verification module and an information sending module, the verification module is used to verify the legitimacy of the service request and verify the feasibility of the XR client executing the target XR service; the information sending module is used to send a success prompt message to the XREC when the service request is legal and the feasibility verification passes; and the information sending module is used to send a failure prompt message to the XREC when the service request is illegal or the feasibility verification fails.

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

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

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

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

[0022] The user identification information corresponds to the business synchronization requirement information between XR clients.

[0023] In an optional embodiment of the present disclosure, the device may also include an information migration module; the information migration module is used 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, and the migration information includes user identification information of the XREC, a user configuration table corresponding to the user identification information, and context information.

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

[0025] In an optional embodiment of the present disclosure, the device may also 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 search for other target AF network elements that meet the business requirement parameters to establish data communication between the XR client and the other target AF network elements.

[0026] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned XR business-based management method when executed by a processor.

[0027] In a fourth aspect, an embodiment of the present disclosure provides an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned XR business-based management method by executing the executable instructions.

[0028] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, which is executed by a processor to implement the above-mentioned XR business-based management method.

[0029] The technical solution disclosed in this disclosure has the following beneficial effects:

[0030] The above-mentioned management method based on XR services receives a service request for a target XR service from an extended reality enabling client XREC, where the target XR service is the XR service that XREC needs to execute and obtains from the XR client; according to 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, 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; based on the service requirement parameters, the target AF network element that meets the service requirement parameters is searched from the pre-registered AF list, so that the XR client can establish data communication with the target AF network element. On the one hand, the method uniformly receives and manages the service requests for XR services through the first XRES network element, thereby improving the management efficiency and effectiveness of diverse XR services. And through the ADAES network element, the current network parameters when running the XR service are analyzed, and then the operation requirements of the XR service are determined, so as to find the target AF network element that meets the service requirement parameters in the AF list to establish a data channel, and the appropriate AF network element can be allocated for the operation of the XR service, thereby improving resource utilization and the effectiveness of the XR service operation, optimizing the network scheduling process, and thus improving the user experience of the XR service. On the other hand, by allocating appropriate AF network elements for the operation of the XR service through the XRES network element, the congestion and burden brought to the network by the high-traffic XR service can be avoided, so as to improve the network burden and maintain system stability.

[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure. Obviously, the drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0033] Figure 1 The following schematically shows an application architecture diagram of a management system based on XR services in this exemplary embodiment;

[0034] Figure 2 A flowchart schematically illustrates a management method based on XR services in this exemplary embodiment;

[0035] Figure 3 A schematic diagram of a process of registering an XREC in an XRES network element in this exemplary embodiment is shown schematically;

[0036] Figure 4 A schematic diagram schematically illustrates a flow chart of a method for managing an overall XR service in this exemplary embodiment;

[0037] Figure 5 A schematic diagram of the structure of a management device based on XR services in this exemplary embodiment is shown;

[0038] Figure 6 The structure diagram of an electronic device in this exemplary embodiment is schematically shown. DETAILED DESCRIPTION

[0039] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, exemplary embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the exemplary embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0040] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0041] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

[0042] In order to help those skilled in the art better understand the technical solution provided by the embodiments of the present disclosure, the relevant contents involved in the technical solution of the present disclosure are introduced below.

[0043] 1) Extended Reality (XR): It is a collection of virtual and real technologies, which usually include Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR) and other technologies. XR technology changes the way humans interact from 2D interaction to more efficient 3D interaction. VR is virtual reality, which simulates the real world through software and hardware; AR is augmented reality, which overlays information and images on the real world through various devices; MR is mixed reality, which realizes real-time interaction between the virtual world and the real world through digital technology.

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

[0045] 3) Extended Reality Enable Sever (XRES): The XRES network element in this embodiment is used to collect and analyze the XR service requirements required by users so as to uniformly manage diverse XR services.

[0046] 4) Extended Reality Enable Client (XREC): The XREC client in this embodiment is used to collect the user's XR service requirements from the XR client.

[0047] In the relevant technical background, with the rapid development of computer and communication technology, the application of virtual reality devices continues to penetrate into people's daily lives. Among the existing devices, there are various extended reality (XR) hardware and software devices, but they cannot be efficiently integrated into a unified standard device. Therefore, the existing 5G network architecture does not have the function of supporting and uniformly managing XR services, and the diversified XR services require designers to specialize the network elements in the 5G core network and provide specialized network element services and network architectures for the services, which affects the management efficiency of XR services and has high management costs.

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

[0049] Taking the above problems into consideration, the exemplary embodiments of the present disclosure propose a management method based on XR services, which provides an enabling network architecture for XR services so as to uniformly manage diverse XR services. Specifically, in the enabling network architecture, through the XRES network element. The service requests of the XR services are uniformly received and managed, thereby improving the management efficiency and effectiveness of diverse XR services. And through the ADAES network element, the current network parameters when running the XR service are analyzed to determine the operation requirements of the XR service, so as to find the target AF network element that meets the service requirement parameters in the AF list to establish a data channel, and appropriate AF network elements can be allocated for the operation of the XR service, thereby improving resource utilization and the effectiveness of the XR service operation, optimizing the network scheduling process, and improving the user experience of the XR service. On the other hand, by allocating appropriate AF network elements to the operation of the XR service through the XRES network element, congestion and burden on the network caused by high-traffic XR services can also be avoided, so as to improve the network burden and maintain system stability.

[0050] For ease of understanding, the present disclosure proposes a management method and device 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 a terminal device 101, a UPF (User Plane Function) network element 102, a PCF (Policy Control Function) network element 103, a NEF (Network Exposure Function) network element 104, an ADAES (Application Data Analytics Server) network element 105, an XRES network element 106, and an 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 is run through the terminal device 101, and the user can log in to the XR client 1011 using the corresponding user account, and trigger the service requirements of the corresponding target XR service; the XREC 1012 collects the service requirements of the target XR service to be executed from the XR client 1011, and sends a service request for the target XR service to the XRES network element 106.

[0053] The XRES network element 106 receives the service request for the target XR service, and sends an AF analysis request for the AF network element 107 to the ADAES network element 105 through the NEF network element 104, so that the ADAES network element 105 determines the service requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client 1011; the ADAES network element 105 then sends the AF analysis result to the XRES network element 106 through the NEF network element 104 to inform the XRES network element 106 of the service requirement parameters related to the target XR service, so that the XRES network element 106 traverses the AFs pre-registered on the server according to the received service requirement parameters to find the target AF network element that meets the service requirement parameters, so that the XR client 1011 establishes a data transmission channel with the target AF network element based on the UPF network element 102, and applies for session resources from the PCF network element 103 to realize the data communication function.

[0054] Among them, the terminal device 101 can be, for example, a smart phone, a PDA (Personal Digital Assistant), a laptop, a server, a desktop computer or any other computing device with networking capabilities, but is not limited to this. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. The network is used to provide a medium for communication links between the terminal device 101, network elements and servers. The network can include various connection types, such as wired, wireless communication links or optical fiber cables, etc., but is not limited to this.

[0055] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. According to the implementation requirements, there may be any number of terminal devices, network elements and servers, and the embodiments of the present disclosure do not impose any special restrictions on this.

[0056] However, it is easy for those skilled in the art to understand that the above application scenarios are only used as examples and are not limited to this in the present exemplary embodiment.

[0057] The following uses the above-mentioned XRES network element as an execution entity and illustrates the application of the XR service-based management method to the above-mentioned XRES network element. Figure 2 A flowchart schematically shows a management method based on XR services in this exemplary embodiment. Figure 2The XR service management method provided in the embodiment of the present disclosure includes the following steps S201 to S203:

[0058] Step S201: receiving a service request for a target XR service from an extended reality enabling client XREC, where the target XR service is an XR service to be executed and obtained by the XREC from the XR client.

[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 via the 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.

[0060] Step S203: Based on the service requirement parameters, search for 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.

[0061] In the technical solutions provided by some embodiments of the present disclosure, by receiving a service request for a target XR service from an extended reality enabling client XREC, the target XR service is an XR service to be executed that XREC obtains from an XR client. According to 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, 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; based on the service requirement parameters, the target AF network element that meets the service requirement parameters is searched from the pre-registered AF list, so that the XR client can establish data communication with the target AF network element. On the one hand, the method uniformly receives and manages the service requests of the XR service through the first XRES network element, thereby improving the management efficiency and effectiveness of diverse XR services. And through the ADAES network element, the current network parameters when running the XR service are analyzed, and then the operation requirements of the XR service are determined, so as to find the target AF network element that meets the service requirement parameters in the AF list to establish a data channel, and the appropriate AF network element can be allocated for the operation of the XR service, thereby improving resource utilization and the effectiveness of the XR service operation, optimizing the network scheduling process, and thus improving the user experience of the XR service. On the other hand, by allocating appropriate AF network elements for the operation of the XR service through the XRES network element, the congestion and burden brought to the network by the high-traffic XR service can be avoided, so as to improve the network burden and maintain system stability.

[0062] The following will be combined with specific embodiments to Figure 2 The specific implementation methods of each step in the embodiment shown are described in detail:

[0063] In step S201, a service request for a target XR service is received from an extended reality enabled client XREC, where the target XR service is an XR service to be executed and obtained by the XREC from the XR client.

[0064] Among them, by running the XR client on the terminal device, the user can log in to the XR client based on the user account and trigger the corresponding target XR service, so that the XREC obtains the service requirements of the target XR service to be executed from the XR client. XR services can be, for example, VR sessions, AR rendering, virtual reality game interactions, or any other services involving virtual and real technologies, which are not exhaustively listed in this disclosure.

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

[0066] Exemplarily, after XREC collects the target XR service that the user needs to execute 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 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 the above step S201, the XREC needs to be pre-registered in the XRES network element to facilitate the information communication process between the XREC client and the XRES network element.

[0068] Figure 3 Schematically shows a schematic diagram of a process of registering an XREC in an XRES network element in this exemplary embodiment, see Figure 3 The XREC registration process provided by the embodiment of the present disclosure includes the following steps S301 to S304:

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

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

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

[0072] In an optional embodiment, the XRES network element determines the legitimacy of the identity information corresponding to the XREC in response to receiving the XREC registration request sent by the XREC.

[0073] Exemplarily, in step S302, the legality of the identity information of XREC is verified to check whether XREC is a legal user. For example, the legality of the identity corresponding to XREC can be determined by a whitelist or other methods, and the embodiments of the present disclosure do not impose any special restrictions on this.

[0074] If the XREC is legal, step S303 is executed to allocate user identification information to the 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] The user identification information corresponds to the software configuration information and hardware configuration information of the XR client;

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

[0078] The user identification information corresponds to the business synchronization requirement information between XR clients.

[0079] Among them, the business synchronization requirement information is that XREC is registered as a multi-user group. Through the business synchronization requirement information, it can be obtained whether information synchronization is performed in the multi-user group. If information synchronization is not required, the data channel needs to be re-established; conversely, if the information is synchronized, there is no need to re-establish the data channel to continue data transmission.

[0080] The user identification information may be an identity document (ID) of XREC.

[0081] Exemplarily, in the case where the XREC is registered as a multi-user group, the user identification information allocated to the XREC in step S303 may be multiple user IDs for each user in the multi-user group.

[0082] Exemplarily, user identification information is allocated to the XREC so that when the XRES network element subsequently sends an AF analysis request to the ADAES network element through the NEF network element, the user identification information of the XREC is carried.

[0083] On the contrary, if the XREC is not legal, the registration request of the XREC will be rejected.

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

[0085] The XREC registration result includes registration success or registration failure.

[0086] Exemplarily, if the XREC registers successfully, the XRES network element sends the XREC a registration success flag and also sends the allocated user identification information to the XREC. In order to improve the user interaction experience, the reason for the registration failure can also be sent to the XREC when the registration is unsuccessful.

[0087] Through the above embodiments, the registration process of the XREC client in the XRES network element is improved in the enabling network architecture for XR services, so as to provide a basis for establishing a data channel for the subsequent allocation of the corresponding AF 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 executing step S201 to receive a service request for the target XR service from the XREC, the XRES network element first needs to verify the legitimacy 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 prompt message is sent to the XREC; when the service request is illegal or the feasibility verification fails, a failure prompt message is sent to the XREC.

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

[0090] If the service request is legal and the feasibility verification of the XR client is passed, a success prompt message can be sent to the XREC, and the following step S202 is continued; otherwise, if the service request is illegal, or the feasibility verification of the XR client is not passed, a failure prompt message is sent to the XREC, and the identification information can include the reason for the failure. For example, if the feasibility verification of the XR client is not passed, specifically, the VR device is not connected, then a prompt message "VR device is not connected, VR session cannot be performed" can be sent to the XREC client.

[0091] It should be explained that the content of the above prompt information is merely exemplary and can be adjusted according to actual needs. The embodiments of the present disclosure do not impose any special restrictions 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 determines 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 the network element that determines the business requirement parameters that meet the target XR service based on the current network parameters corresponding to the XR client.

[0094] Exemplarily, the XRES network element shown in any of the above embodiments is the first XRES network element. When the XRES network element receives a service request for a target XR service from the XREC, it can send an AF analysis request for an 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 an optional embodiment of the present disclosure, the service demand parameters include one or more of the maximum service bandwidth that the XR client can bear under the current network parameters, the actual bandwidth parameters, and the quality of service QoS parameters required by the target XR service.

[0096] Exemplarily, the ADAES network element determines the service demand parameters that need to be met for the operation of the target XR service 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 for 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 searched from a pre-registered AF list, so that the XR client can establish data communication with the target AF network element.

[0098] Exemplarily, based on the business requirement parameters required for the operation of the target XR business, an AF network element that can meet the above business requirement parameters can be searched from the AF list pre-registered by the server, so that it can be used as the target AF network element, and the information of the target AF network element can be sent 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, the AF list contains multiple AF network elements that meet the above service requirement parameters, and one AF network element can be selected from the multiple AF network elements that meet the above service requirement parameters as the target AF network element. The following will be described in conjunction with specific embodiments:

[0100] In an optional embodiment of the present disclosure, based on the 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 smallest bandwidth occupancy among the multiple initial AF network elements is determined as the target AF network element.

[0101] Exemplarily, when the AF list contains multiple initial AF network elements that meet the above service requirement parameters, the AF network element with the smallest bandwidth occupancy rate can be determined as the target AF network element to reduce bandwidth consumption as much as possible from the perspective of resource consumption, thereby improving resource utilization.

[0102] In addition to the above embodiments, other methods may be used to determine a target AF network element from multiple initial AF network elements that meet the business requirement parameters, such as random determination, providing business requirement parameters that are slightly different from the business requirement parameters required by the target XR service, etc., to improve resource utilization and avoid resource idleness.

[0103] When constructing a data transmission channel between the XR client and the target AF network element based on the above embodiment, a session resource can be applied to the PCF network element to create a session between the XR client and the target AF network element. In addition, in the embodiment of the present application, the session quality between the XR client and the target AF network element can also be monitored in real time.

[0104] In an optional embodiment of the present disclosure, a communication quality parameter between the XR client and the target AF network element is detected, so that when 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 business requirement parameters are found to establish data communication between the XR client and the other target AF network elements.

[0105] Exemplarily, when the parameter value of the communication quality parameter 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 business requirement parameters of the target XR business. Then, the data communication between the XR client and the target AF network element can be disconnected to re-search other AF network elements from the pre-registered AF list, and then re-establish data communication between the XR client and 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] Further, based on any of the above embodiments, the XREC may also choose to switch the XRES network element currently connected thereto, for example, in the following embodiment, the XREC switches from the first XRES network element to the second XRES network element.

[0108] In an optional embodiment of the present disclosure, in response to switching from a first XRES network element to a second XRES network element, migration information of the XREC in the first XRES network element is migrated to the second XRES network element, and the migration information includes at least user identification information of the XREC, a 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] Exemplarily, when the XREC needs to switch XRES network elements, 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 interactive information with the first XRES network element, without the need to re-establish the communication connection in the second XRES network element.

[0111] Through this embodiment, when the XREC needs to switch the XRES network element, there is no need to re-establish the connection relationship, but the interaction process with the original XRES network element can be inherited, thereby improving the implementation efficiency of the XR service.

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

[0113] Figure 4 A schematic diagram schematically illustrates a flow chart of a method for managing an overall XR service in this exemplary embodiment; Figure 4 As shown, taking the target XR service as a VR session as an example, first, in an optional embodiment of the present disclosure, the XREC sends an XREC registration request to the XRES network element in advance, that is, executing step S401 and sending the XREC registration request.

[0114] Exemplarily, the XREC registration request includes the XR user's configuration information (such as software and hardware facility information) and the user's mobility information. When the XREC is registered as a multi-user group, the group, in addition to the above information, also provides synchronization requirement information for multi-user services.

[0115] After receiving the registration request, XRES will execute step S402 to review whether XREC is legal.

[0116] If the XREC is legal, step S403 is executed to allocate user identification information to the XREC and construct a user configuration table corresponding to the user identification information.

[0117] Exemplarily, by allocating user identification information and constructing a user configuration table corresponding to the user identification information, the user identification information is included in the AF analysis request subsequently sent by the XRES network element to the ADAES network element.

[0118] In an optional embodiment of the present disclosure, the XR client executes step S404 to initiate the target XR service. That is, the XR client initiates the VR session service, and 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] When the XRES network element receives a service request for the target XR service from the XREC, it executes step S406 to verify the legitimacy of the service request and the feasibility of the XR client.

[0120] Exemplarily, the legitimacy of the service request is verified, and the feasibility of the XR client executing the target XR service is verified, that is, whether the software configuration and hardware configuration of the XR client meet the service requirements of the target XR service.

[0121] If the service request is legal and the feasibility verification is passed, step S4071 is executed to send a success prompt message. Otherwise, if the service request is illegal or the feasibility verification is not passed, step S4072 is executed to send a failure prompt message.

[0122] After the service request is legal and the feasibility verification is passed, step S408 can be continued to send an AF analysis request to the ADAES network element via the NEF network element.

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

[0124] In an optional embodiment of the present disclosure, the service requirement parameters for meeting the target XR service may be the maximum service bandwidth that the XR client can bear under the current network environment, the corresponding actually allocated bandwidth parameters, and the QoS configuration required for the service.

[0125] Then, the ADAES network element executes step S410 to send the AF analysis result to the XRES network element through the NEF. Exemplarily, the AF analysis result includes the service requirement parameters that need to meet the target XR service.

[0126] After receiving the AF analysis result sent by the ADAES network element, the XRES network element can search for a target AF network element that meets the business requirement parameters from a pre-registered AF list based on the business requirement parameters in the AF analysis result, that is, execute step S411 to search for the target AF network element.

[0127] Before executing step S411, it is necessary to execute step S4110 and pre-register in advance.

[0128] That is, multiple AF network elements need to be pre-registered in 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 search for the target AF network element that meets the service requirement parameters from the pre-registered AF list.

[0129] In an optional embodiment of the present disclosure, after finding the target AF network element, the XRES network element may execute step S412 and send identification information of the target AF network element to the XR client.

[0130] After receiving the identification information of the target AF network element, the XR client builds a data transmission channel with the target AF network element for data communication. That is, execute step S403 to build a data channel. At the same time, the XR client executes step S414 to apply for session resources from the PCF network element. The VR session service is executed based on the applied session resources.

[0131] In addition, based on the above embodiment, when XREC needs to switch the XRES network element, it can obtain the required migration information (ie) from the original XRES network element. If the XREC is a newly registered user, there is no need to obtain the migration information including the user identification information of the XREC, the user configuration table corresponding to the user identification information, and context information, etc., 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, an embodiment of the present disclosure provides a management device based on XR services. Figure 5 A schematic architecture diagram of a management device based on XR services is schematically shown.

[0133] Among them, the XR service-based management device 500 is applied to the first extended reality enabling 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 search module 503.

[0134] The request receiving module 501 is used to receive a service request for a target XR service from an extended reality enabling client XREC, where the target XR service is an XR service that is obtained by the XREC from the XR client and needs to be executed by the XR user; the parameter determination module 502 is used to send 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 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 search module 503 is used to search for a target AF network element that meets the service requirement parameters from a 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 an optional embodiment of the present disclosure, the service demand parameters include one or more of the maximum service bandwidth that the XR client can bear 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 the present disclosure, the device may also include a verification module and an information sending module, the verification module is used to verify the legitimacy of the service request and verify the feasibility of the XR client executing the target XR service; the information sending module is used to send a success prompt message to the XREC when the service request is legal and the feasibility verification passes; and the information sending module is used to send a failure prompt message to the XREC when the service request is illegal or the feasibility verification fails.

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

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

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

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

[0141] The user identification information corresponds to the business synchronization requirement information between XR clients.

[0142] In an optional embodiment of the present disclosure, the device may also include an information migration module; the information migration module is used 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, and the migration information includes user identification information of the XREC, a user configuration table corresponding to the user identification information, and context information.

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

[0144] In an optional embodiment of the present disclosure, the device may also 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 search for other target AF network elements that meet the business requirement parameters to establish data communication between the XR client and the other target AF network elements.

[0145] The XR business-based management device 500 provided in the embodiment of the present disclosure can execute the technical solution of the XR business-based management method in any of the above-mentioned embodiments, and its implementation principle and beneficial effects are similar to the implementation principle and beneficial effects of the XR business-based management method. Please refer to the implementation principle and beneficial effects of the XR business-based management method, and no further details will be given here.

[0146] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present invention may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary embodiments of the present invention described in the above "Exemplary Method" section of the present specification.

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

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

[0149] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program 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 appropriate medium, including but not limited to wireless, wired, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

[0151] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet Service Provider).

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

[0153] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0154] Refer to the following Figure 6 The electronic device 600 according to this embodiment of the present invention is described. Figure 6 The electronic device 600 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0155] like Figure 6 As shown, the electronic device 600 is in the form of a general 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 the storage unit 620 and the processing unit 610), and a display unit 640.

[0156] The storage unit stores program codes, which can be executed by the processing unit 610, so that the processing unit 610 performs the steps according to various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 610 can perform the following steps: Figure 2 Steps S201 to S203 shown in FIG.

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

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

[0159] Bus 630 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

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

[0161] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0162] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0163] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0164] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

[0165] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A management method based on XR services, characterized in that: A first extended reality enabling service XRES network element used to perform extended reality XR service management, the method comprising: Receiving a service request for a target XR service from an extended reality enabling client XREC, where the target XR service is an XR service to be executed and obtained by the XREC from the XR client; 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 determines 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, a target AF network element that meets the service requirement parameters is searched from a pre-registered AF list, so that the XR client establishes 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 maximum service bandwidth that the XR client can bear 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 the extended reality enabling client XREC, the method further includes: Verify the legitimacy of the service request and verify the feasibility of the XR client executing the target XR service; If the service request is legal and the feasibility verification is passed, a success prompt message is sent to the XREC; If the service request is illegal, or the feasibility verification fails, a failure prompt message is sent to the XREC.

4. The method according to claim 1, characterized in that: The method further comprises: In response to receiving the XREC registration request sent by the XREC, determining the legitimacy of the identity information corresponding to the XREC; If the XREC is legal, assign user identification information to the XREC, and construct a user configuration table corresponding to the user identification information, so that the AF analysis request includes the user identification information; The user configuration table includes one or more of the following configuration information: The user identification information corresponds to 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 service synchronization requirement information between XR clients.

5. The method according to claim 4, characterized in that The method further comprises: 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, and 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 searching, based on the service requirement parameters, for a target AF network element that meets 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 a pre-registered AF list, and an AF network element with the smallest 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 comprises: Detect the communication quality parameter between the XR client and the target AF network element, and when the parameter value of the communication quality parameter is less than the parameter threshold, disconnect the data communication between the XR client and the target AF network element, and search for other target AF network elements that meet the business demand parameters 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 enabling service XRES network element used to perform extended reality XR service management, the device comprising: A request receiving module, configured to receive a service request for a target XR service from an extended reality enabling client XREC, wherein the target XR service is an XR service to be executed obtained by the XREC from the XR client; A parameter determination module, configured to send, according to the service request, 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; The AF network element search module is used to search for a target AF network element that meets the business requirement parameters from a pre-registered AF list based on the business requirement parameters, 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 a processor, the XR service-based management method according to any one of claims 1 to 7 is implemented.

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

Images