WO2025246166A1 - 业务使能方法、业务处理方法、装置和通信设备 - Google Patents

业务使能方法、业务处理方法、装置和通信设备

Info

Publication number
WO2025246166A1
WO2025246166A1 PCT/CN2024/127769 CN2024127769W WO2025246166A1 WO 2025246166 A1 WO2025246166 A1 WO 2025246166A1 CN 2024127769 W CN2024127769 W CN 2024127769W WO 2025246166 A1 WO2025246166 A1 WO 2025246166A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
iusu
nscdf
download
software data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/127769
Other languages
English (en)
French (fr)
Inventor
马金兰
王庆扬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd Technology Innovation Center
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd Technology Innovation Center
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd Technology Innovation Center, China Telecom Corp Ltd filed Critical China Telecom Corp Ltd Technology Innovation Center
Publication of WO2025246166A1 publication Critical patent/WO2025246166A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring

Definitions

  • This application relates to the field of communication technology, and in particular to a service enabling method, service processing method, apparatus, communication equipment, computer-readable storage medium, and computer program product.
  • 6G (6th Generation Mobile Networks)
  • 6G network architecture based on an integrated user service unit, which can provide terminals with network functions and service support defined by users according to their own needs.
  • This application provides a service enabling method, apparatus, communication device, computer-readable storage medium, and computer program product that can enable services in a 6G network architecture.
  • this application provides a method for integrating a User Service Unit (IUSU), the method comprising:
  • downloading the software data of the service corresponding to the service download notification from the NSCDF includes:
  • the service resources corresponding to the service resource requirements are reserved.
  • downloading the software data from the NSCDF includes:
  • the method further includes:
  • the service identifier corresponding to the service software data is recorded to indicate that the IUSU supports the service corresponding to the service identifier.
  • the method further includes:
  • a service launch success notification is sent to the NSCDF.
  • the service launch success notification includes the service identifier.
  • the service launch success notification is used to notify the NSCDF to record that the IUSU supports the service corresponding to the service identifier.
  • the method includes:
  • the service software download notification being used to instruct the IUSU to download the software data of the service corresponding to the service download notification from the NSCDF.
  • the method before sending the service download notification to the IUSU, the method further includes:
  • the software data is downloaded from the SMG.
  • downloading the software data from the SMG according to the service release notification includes:
  • the NSCDF When the NSCDF meets the storage space requirement, it sends a second service software data download request to the SMG; the second service software data download request includes a service identifier.
  • the method further includes:
  • the software data is sent to the IUSU based on the service identifier included in the first service software data download request.
  • the method further includes:
  • the method includes:
  • a service release notification is sent to the NSCDF, which is used to instruct the NSCDF to download the software data of the service corresponding to the service release notification from the SMG.
  • the method further includes:
  • the software data is sent to the NSCDF based on the service identifier carried in the second service software data download request.
  • this application also provides a service processing method for a first IUSU, wherein the first IUSU enables services using the service enabling method described in any one of the first aspects above, the method comprising:
  • a failure response is returned to the terminal.
  • the failure response is used to instruct the terminal to register with a second IUSU that supports the service.
  • the method further includes:
  • returning a failure response to the terminal includes:
  • the failure response is generated, and the failure response includes a list of service support IUSUs;
  • the method further includes:
  • the service capability query response includes the service support IUSU list.
  • a service processing method for a terminal includes:
  • a failure response is received from the first IUSU
  • a second IUSU is selected based on the failure response, and a user registration request is initiated to the second IUSU.
  • this application also provides an apparatus for an IUSU, the apparatus comprising:
  • the first receiving module is used to receive service software download notifications sent by the Network and Service Capability Storage Function (NSCDF).
  • NSCF Network and Service Capability Storage Function
  • the download module is used to download the software data of the service corresponding to the service download notification from the NSCDF according to the service download notification;
  • the startup module is used to load and start the software corresponding to the software data.
  • this application also provides an apparatus for NSCDF, the apparatus comprising:
  • the second sending module is used to send a service software download notification to the IUSU.
  • the service software download notification is used to instruct the IUSU to download the software data of the service corresponding to the service download notification from the NSCDF.
  • the fourth sending module is used to send a service release notification to the NSCDF.
  • the service release notification is used to instruct the NSCDF to download the software data of the service corresponding to the service release notification from the SMG.
  • the fourth receiving module is used to receive service requests sent by the terminal
  • the sixth sending module is used to return a failure response to the terminal if the service corresponding to the service request is not supported.
  • the failure response is used to instruct the terminal to register with the second IUSU that supports the service.
  • this application also provides a service processing apparatus for NSCDF, the apparatus comprising:
  • the eighth sending module is used to return a service capability query response to the first IUSU, the service capability query response being used to indicate at least one second IUSU that supports the service.
  • this application also provides a service processing apparatus for a terminal, the apparatus comprising:
  • the tenth sending module is used to, when receiving a failure response returned by the first IUSU, initiate a user registration request to at least one second IUSU that supports the service corresponding to the service request, as included in the failure response.
  • the receiver is used to receive service download notifications sent by the Network and Service Capability Storage Function (NSCDF).
  • NSCF Network and Service Capability Storage Function
  • the receiver is also configured to download the software data of the service corresponding to the service download notification from the NSCDF according to the service download notification;
  • the processor is used to load and start the software corresponding to the software data.
  • this application also provides a communication device.
  • the communication device includes: a transmitter;
  • the transmitter is used to send a service software download notification to the IUSU, which is used to instruct the IUSU to download the software data of the service corresponding to the service download notification from the NSCDF.
  • the communication device includes: a transmitter;
  • the receiver is used to receive service requests sent by the terminal;
  • the transmitter is used to return a failure response to the terminal if it does not support the service corresponding to the service request.
  • the failure response is used to instruct the terminal to register with a second IUSU that supports the service.
  • this application also provides a communication device.
  • the communication device includes: a receiver and a transmitter;
  • the receiver is used to receive a service capability query request sent by the first IUSU, which is sent by the first IUSU when it does not support the service corresponding to the service request sent by the terminal.
  • the transmitter is used to return a service capability query response to the first IUSU, and the service capability query response is used to indicate at least one second IUSU that supports the service.
  • this application also provides a communication device.
  • the communication device includes: a transmitter;
  • the transmitter is used to send a service request to the first IUSU
  • the transmitter is further configured to, upon receiving a failure response returned by the first IUSU, initiate a user registration request to at least one second IUSU included in the failure response that supports the service corresponding to the service request.
  • this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the service enabling method described in any of the first aspects and the service processing method described in any of the second aspects.
  • this application also provides a computer program product, including a computer program that, when executed by a processor, implements the business enabling method described in any of the first aspects and the business processing method described in any of the second aspects.
  • the aforementioned service enabling method, service processing method, apparatus, communication equipment, computer-readable storage medium, and computer program product wherein the IUSU receives a service software download notification sent by the NSCDF, downloads the software data corresponding to the service download notification from the NSCDF, and then enables the service corresponding to the software by loading the software data.
  • the IUSU can pre-download the software data of the corresponding service based on the received service software download notification, thereby enabling the loading of the software corresponding to the software data.
  • IUSU When IUSU receives a user's service request, it can provide the service to the user through pre-installed software. This avoids the problem that the IUSU cannot provide the corresponding service to the user because the software for the service download notification is not available. In this way, the software-related service can be enabled, realizing service enablement in the 6G network architecture.
  • Figure 1 is an application environment diagram of a service enablement method in one embodiment
  • Figure 2 is a flowchart illustrating a service enablement method in one embodiment
  • FIG. 3 is a flowchart of step 202 in one embodiment
  • Figure 4 is a flowchart of step 303 in one embodiment
  • Figure 5 is a flowchart illustrating the service enablement method in another embodiment
  • FIG. 6 is a flowchart of step 502 in one embodiment
  • Figure 7 is a flowchart illustrating the service enablement method in another embodiment
  • Figure 8 is a flowchart illustrating the service enablement method in another embodiment
  • Figure 9 is a flowchart illustrating the service enablement method in another embodiment
  • Figure 10 is a schematic diagram of signaling interaction for a service enablement method in one embodiment
  • Figure 11 is an application environment diagram of a business processing method in one embodiment
  • Figure 12 is a flowchart illustrating a business processing method in one embodiment
  • Figure 13 is a flowchart illustrating the business processing method in another embodiment
  • FIG 14 is a flowchart of step 1002 in one embodiment
  • Figure 15 is a flowchart illustrating the business processing method in another embodiment
  • Figure 16 is a flowchart illustrating the business processing method in another embodiment
  • Figure 17 is a flowchart illustrating the business processing method in another embodiment
  • Figure 18 is a schematic diagram of signaling interaction of a service processing method in one embodiment
  • Figure 19 is a structural block diagram of a service enabling device in one embodiment
  • Figure 20 is a structural block diagram of a service enabling device in another embodiment
  • Figure 21 is a structural block diagram of a service enabling device in another embodiment
  • Figure 22 is a structural block diagram of a service processing device in one embodiment
  • Figure 23 is a structural block diagram of the service processing device in another embodiment.
  • Figure 24 is a structural block diagram of the service processing device in another embodiment
  • Figure 25 is an internal structure diagram of a communication device in one embodiment
  • Figure 26 is an internal structure diagram of the communication device in another embodiment
  • Figure 27 is an internal structural diagram of the communication device in another embodiment
  • Figure 28 is an internal structural diagram of the communication device in another embodiment
  • Figure 29 is an internal structural diagram of the communication device in another embodiment
  • Figure 30 is an internal structural diagram of a communication device in another embodiment.
  • FIG. 1 is a schematic diagram of an application scenario for a service enabling method provided in an embodiment of this application.
  • this scenario includes an Integrated User-Centric Service Unit (IUSU) 100, Network and Service Capabilities Depository Functions (NSCDF) 200, and a Session Management Function (SMG) 300.
  • IUSU 100 and NSCDF 200 are conducted via a network
  • NSCDF 200 and SMG 300 are also conducted via a network.
  • the SMG300 sends a service release notification to the NSCDF200.
  • the NSCDF200 downloads the corresponding software data from the SMG300 and then sends a service software download notification to the IUSU100.
  • the IUSU Upon receiving the service software download notification, the IUSU, provided that the service resource requirements are met and it is configured to support autonomous service enablement, reserves the service resources corresponding to the service resource requirements, downloads the software data from the NSCDF, loads the software corresponding to the software data, and enables the service corresponding to the software, thereby realizing service enablement in the 6G network architecture.
  • the operator's service platform After receiving a service request from a service terminal, the operator's service platform needs to determine whether it can support the service request. If it can, it downloads the corresponding software and responds to the request, providing the user with the relevant service. If it cannot support the service, it returns a response failure message to the service terminal.
  • ISP integrated service unit
  • the IUSU receives a service software download notification sent by the NSCDF, downloads the software data corresponding to the service from the NSCDF, and then enables the corresponding service by loading the software corresponding to the software data. Because the IUSU can pre-download the corresponding service software data according to the received service software download notification, and thus load the corresponding software, the IUSU can provide services to the user through the pre-loaded software when it receives a user's service request. This avoids the problem of being unable to provide the corresponding service to the user due to the absence of the software corresponding to the service download notification in the IUSU, thereby enabling the service corresponding to the software and realizing service enabling in the 6G network architecture.
  • the IUSU By receiving service software download notifications from the NSCDF, the IUSU downloads the software data corresponding to the service from the NSCDF. Then, by loading the software corresponding to the software data, the corresponding service can be enabled. In this service enabling method, the IUSU can pre-download the software data of the corresponding service based on the received service software download notification, and thus load the corresponding software. This allows the IUSU to provide services to users when it receives service requests from users through the pre-loaded software. This avoids the problem of not being able to provide services to users because the software corresponding to the service download notification is not in the IUSU, thereby enabling the corresponding service in the 6G network architecture.
  • Step 201 Receive the service software download notification sent by the Network and Service Capability Storage Function (NSCDF).
  • NSCF Network and Service Capability Storage Function
  • an IUSU is a user-centric integrated service unit network element that can provide selected network functions and service capabilities to specific users of fixed, mobile, and satellite convergence within the network.
  • the IUSU can be a private IUSU created and managed by a user, capable of providing network and services to the user who created it; alternatively, the IUSU can be a public IUSU created and managed by an operator, capable of providing network and services to all users.
  • the access network can include one or more IUSUs.
  • a public IUSU can be used as an example to describe the interaction process of the service enabling method.
  • NSCDF is a network element that supports the storage and download functions of the network and services required by IUSU.
  • the service software download notification is a signaling message sent by NSCDF to IUSU, instructing IUSU to download software data related to a specific user service.
  • This notification may include the service name, service description, service type, service identifier, and service resource requirements.
  • the resource requirements may include information such as bandwidth, storage resources, and computing resources corresponding to the service.
  • the notification may include information related to one or multiple services.
  • the IUSU can receive service software download notifications sent by the NSCDF through the access network.
  • the IUSU's identifier can be pre-stored in the NSCDF for use when the NSCDF sends service software download notifications to designated IUSUs.
  • Step 202 Download the software data corresponding to the service download notification from NSCDF.
  • the "service download notification” refers to the service whose identifier and description are included in the download notification. Different services provide different services to users. Each service corresponds to a set of software data, which may include the software package corresponding to that service, installation instructions, and other information. In some embodiments, the software data may include the software data for one service, or it may include the software data for multiple services, with different service identifiers for different software data sets.
  • the IUSU can determine the service corresponding to the service software download notification based on the service identifier and service description in the service software download notification, and then download the software data of the service from the NSCDF.
  • Step 203 Load the software corresponding to the software data and enable the corresponding services.
  • the software corresponding to the software data can receive users' software usage requests and provide corresponding services to users through the software, thus enabling the business corresponding to the software.
  • the IUSU after downloading software data, the IUSU can load the software corresponding to the software data into the IUSU. After the software is successfully loaded, when the user initiates a usage request, it can provide the service corresponding to the software, thereby enabling the business corresponding to the software.
  • the IUSU does not pre-download the software data corresponding to a service, it cannot load the corresponding software.
  • the IUSU receives a service request from a user, it cannot provide the service corresponding to that service.
  • the IUSU receives a service request from a user, it needs to obtain and load the corresponding service software before it can provide the service to the user. Therefore, pre-downloading the software data corresponding to a service and loading the corresponding software in the IUSU enables the service to be enabled and provides services to users, while also achieving autonomous enabling of the corresponding service.
  • the IUSU receives a service software download notification sent by the NSCDF, downloads the software data corresponding to the service from the NSCDF, and then enables the corresponding service by loading the software corresponding to the software data. Because the IUSU can pre-download the software data of the corresponding service based on the received service software download notification, and thus load the corresponding software, the IUSU can provide services to the user through the pre-loaded software when it receives a user's service request. This avoids the problem of being unable to provide the corresponding service to the user due to the absence of the software corresponding to the service download notification in the IUSU, thereby enabling the corresponding service in the 6G network architecture.
  • step 202 may include:
  • Step 301 Determine whether the IUSU meets the business resource requirements included in the business download notification.
  • the business resource requirements refer to the bandwidth needed for downloading the software corresponding to the service within the IUSU, as well as the storage and computing resources required for loading the software. It's understandable that if the IUSU needs to download software data corresponding to a service, its own business resources must be able to meet the software data's resource requests. Therefore, before downloading software data, the IUSU needs to determine whether it meets the business resource requirements.
  • IUSU can obtain the service resource requirements from the received service download notification, and then determine whether its own bandwidth meets the bandwidth requirement, its own storage resources meet the storage requirement, and its own computing resources meet the computing requirement, thereby determining whether it meets the service resource requirements included in the service download notification.
  • Step 302 If the IUSU meets the business resource requirements and is configured to support business self-enabling, reserve the business resources corresponding to the business resource requirements.
  • IUSU needs to be configured to support business autonomy so that when a business request is received from a user, the installed software can provide the corresponding service to the user.
  • business resources refer to the bandwidth, computing resources and storage resources corresponding to IUSU.
  • IUSU needs to ensure that its own bandwidth can meet the bandwidth requirements of business resources, its own computing resources can meet the computing resources requirements of business resources, and its own storage resources can meet the storage resources requirements of business resources.
  • IUSU determines that it meets the business resource requirements and supports business self-enabling, it can reserve the business resources that meet the business resource requirements to avoid the problem of the business resources being occupied, which would lead to the failure of downloading software data.
  • Step 303 Download software data from NSCDF.
  • the IUSU may also send an instruction message to the NSCD to instruct the NCDF to send software data to the IUSU, thereby downloading the software data from the NCDF; or, after a preset time period following receiving the business software download notification, the IUSU may receive a business resource query message sent by the NCDF and send a message to the NCDF containing the business resource information corresponding to the reserved business resource requirements, so that the NCDF can send software data to the IUSU after receiving the message, thereby downloading the software data from the NCDF.
  • the IUSU determines whether it meets the service resource requirements included in the service download notification. If it meets the service resource requirements and is configured to support service autonomy, it reserves the corresponding service resources before downloading the software data from the NSCDF. Because the IUSU ensures that it meets the service resource requirements and reserves the corresponding resources before downloading the software data, it avoids situations where it cannot meet the service resource requirements and downloads the software data from the NSCDF but fails to install, resulting in wasted computing resources and improving the reliability of successful software data download. Furthermore, since the IUSU reserves service resources and downloads the software data while configured to support service autonomy, it ensures that after the software data download, when a user request is received... When sending a business request, the corresponding business can be enabled.
  • step 303 may include:
  • Step 401 Send a first service software data download request to NSCDF.
  • the first service software data download request includes a service identifier.
  • the first service software download request refers to the signaling from an IUSU requesting to download the software data corresponding to a service software notification from the NSCDF. It is understandable that, since the access network includes multiple IUSUs, when the NSCDF receives a software download request, it cannot determine which software data the request corresponds to. Therefore, the first service software download request may include a service identifier to represent the service corresponding to the first service software download request, allowing the NSCDF to determine the corresponding software data based on the represented service.
  • the IUSU can generate a first service software data download request carrying a service identifier based on the received service software download notification.
  • Step 402 Receive software data sent by NSCDF in response to the first service software data download request.
  • the IUSU can wait for the NSCDF to respond to the first service software data download request and send a response message, thereby obtaining the software data corresponding to the first service software data download request from the received response message.
  • the IUSU sends a first service software data download request including a service identifier to the NSCDF, enabling the NSCDF to determine the service corresponding to the download request based on the service identifier, determine the corresponding software data based on the service, and send it to the IUSU.
  • the IUSU can receive the software data sent by the NSCDF in response to the first service software data download request.
  • the IUSU can avoid the problem of the NSCDF sending incorrect software data, thereby improving the accuracy of the software data received by the IUSU.
  • an IUSU can support multiple services. After the IUSU loads the software corresponding to a service, it can record the service identifier of the supported service. This allows for quick determination of whether a service request is supported when a user's service request is received. In one embodiment, the method further includes recording the service identifier corresponding to the service software data in the list of services supported by the IUSU, indicating that the IUSU supports the service corresponding to the service identifier.
  • the service list may include service identifiers corresponding to the software installed in IUSU, which represent the services that IUSU can provide to users.
  • the service identifier may include one service identifier, or it may include multiple service identifiers.
  • the service identifier corresponding to the software can be added to the service list.
  • IUSU records the service identifiers corresponding to the service software data in the service list supported by IUSU. Since the service list can indicate whether IUSU supports the service corresponding to the service identifier, IUSU can quickly determine whether to support the service request when it receives a user's service request by judging whether the service identifier corresponding to the service request exists in the service list, thereby improving the response efficiency to service requests.
  • the NSCDF can provide storage functionality for the required network and services for the IUSU.
  • the above method further includes: sending a service launch success notification to the NSCDF, the service launch success notification including a service identifier, the service launch success notification being used to notify the NSCDF to record the service corresponding to the service identifier supported by the IUSU.
  • the successful service launch notification refers to the notification information generated by IUSU when IUSU has loaded the software corresponding to the software data and the software can run successfully. It is used to indicate that IUSU supports the software and can provide the software service to the user, and instructs NSCDF to record the service corresponding to the software.
  • IUSU can generate a successful service launch notification, including a service identifier, and send the successful service launch notification to NSCDF when the software corresponding to the software data is loaded and the software can run successfully.
  • the IUSU can instruct the NSCDF to record the services supported by the service identifier, thereby improving the effectiveness of storing the services supported by the service identifier of the IUSU. Then, when a user's service request is received, the IUSU can obtain the services supported by the IUSU from the NSCDF and quickly determine whether the IUSU supports the service request.
  • the method includes: sending a service software download notification to the IUSU, which instructs the IUSU to download the software data of the corresponding service from NSCDF.
  • the business software download notification is a signaling method used by NSCDF to notify IUSU to download the corresponding software data.
  • the NSCDF can send a service software download notification to the IUSU through the access network, enabling the IUSU to send a software download request to the NSCDF based on the service software download notification, thereby downloading the software data of the service corresponding to the service download notification from the NSCDF.
  • the NSCDF can store a list of multiple IUSUs.
  • the NSCDF can send different service software download notifications to different IUSUs, or the NSCDF can send the same service software download notification to multiple IUSUs simultaneously.
  • NSCDF sends a service software download notification to IUSU, which instructs IUSU to download the software data corresponding to the service download notification from NSCDF.
  • IUSU instructs IUSU to download the software data corresponding to the service download notification from NSCDF.
  • NSCDF sends the service software download notification to IUSU, it needs to receive the service release notification from SMG, and then generate the service software download notification based on the service release notification.
  • the above method further includes:
  • Step 501 Receive the service release notification sent by the Service Management Gateway (SMG).
  • SMG Service Management Gateway
  • the SMG is responsible for approving the software data submitted by the business software service provider. Upon approval, it assigns a business identifier and notifies the NSCDF via a message publishing mechanism.
  • the business publishing notification may include the business name, description, type, identifier, and resource requirements. Resource requirements may include information such as bandwidth, storage, and computing resources.
  • the notification may include information for one or more businesses.
  • a mapping relationship between NSCDF and SMG can be established in advance. After SMG approves the software data, a notification message including the business identifier of the corresponding business of the software data can be sent to the NSCDF that has established the mapping relationship.
  • the NSCDF can receive service publication notifications sent by the SMG through the access network. It is understood that the NSCDF can parse the service publication notifications to obtain relevant information about the corresponding service, such as service identifiers and service resource requirements.
  • Step 502 Download software data from SMG according to the business release notification.
  • the software data includes the software package corresponding to the service release notification, installation instructions for the software package, and other data.
  • NSCDF can parse the received service release notification, obtain the identifier of the software data from the parsing result, and then download the corresponding software data from the SMG based on the identifier.
  • the NSCDF can download software data from the SMG based on the service release notification sent by the SMG. Since the service release notification is used to release approved software data, the NSCDF can determine the existence of approved software data after receiving the service release notification, and thus download the software data from the SMG. This allows the NSCDF to quickly download software data from the SMG based on the received service release notification, thereby improving the efficiency of the NSCDF in downloading software data from the SMG.
  • step 502 may include:
  • Step 601 Determine whether NSCDF meets the storage space requirements for the software data included in the business release notification.
  • Storage space requirements refer to the amount of memory that the software data needs to occupy. The larger the memory required, the larger the storage space requirement, and the smaller the memory required, the smaller the storage space requirement.
  • NSCDF only needs to download software data and does not need to load the corresponding software.
  • NSCDF only needs to meet the storage space requirements of the software data to download software data from SMG. Therefore, when NSCDF downloads software data from SMG, it can first determine whether its own storage space meets the storage space requirements of the software data.
  • NSCDF can parse the received service release notification, determine the storage space requirement of the software data included in the service release notification based on the parsing result, compare its own storage space size with the storage space requirement, and determine whether the storage space requirement of the software data included in the service release notification is met based on the comparison result.
  • Step 602 When the NSCDF meets the storage space requirements, it sends a second service software data download request to the SMG; the second service software data download request includes the service identifier.
  • the second software data download request refers to the signaling from which the NSCDF requests the download of software data included in the service release notification issued by the SMG. It is understood that the service release notification issued by the SMG may contain software data corresponding to multiple services. When the SMG receives a software download request, it cannot determine which software the request corresponds to. Therefore, the second service software data download request may include... This includes a service identifier, which is used to characterize the service corresponding to the second service software download request, so that SMG can determine the software data corresponding to the service based on the characterized service.
  • the NSCDF if it meets the storage space requirements, it can generate a second service software data download request including the service identifier corresponding to the storage space requirements, and send the second service software data download request to the SMG.
  • Step 603 Receive the software data sent by SMG according to the second service software data download request, and store the software data.
  • the NSCDF determines whether it meets the storage space requirements of the software data included in the service release notification. If the NSCDF meets the storage space requirements, it sends a second service software data download request, including the service identifier, to the SMG. Then, it receives the software data sent by the SMG according to the second service software data download request and stores the software data. This avoids the problem of downloading software data from the SMG when the NSCDF's storage space is insufficient, which would lead to download failure and waste of computing resources. This improves the reliability of the NSCDF downloading software data from the SMG.
  • the following describes the process of NSCDF sending software data to IUSU, using NSCDF as the executing entity.
  • the above method is used for NSCDF, as shown in Figure 7.
  • the method further includes:
  • Step 701 Receive the first service software data download request sent by IUSU.
  • IUSU when IUSU receives a business software download notification, if its own business origin meets the business resource requirements, it can generate a first business software data download request carrying a business identifier.
  • the NSCDF can receive the first service software data download request sent by the IUSU through the access network.
  • NSCDF can identify a service using a service identifier, thereby determining the corresponding software data.
  • NSCDF can identify the service corresponding to the first service software data download request using the service identifier included in the first service software data download request, thereby enabling it to determine the corresponding software data based on the service and send it to IUSU.
  • the NSCDF receives a first service software data download request sent by the IUSU. Since the first service software data download request includes a service identifier, the NSCDF can determine the service corresponding to the first service software data download request based on the service identifier. This allows the NSCDF to accurately determine the software data corresponding to the service and send the software data to the IUSU, thus improving the accuracy of the sent software data.
  • NSCDF can provide IUSU with the necessary storage functionality for networking and services.
  • the above method further includes:
  • Step 801 Receive the service startup success notification sent by IUSU.
  • Step 802 Record the service corresponding to the service identifier included in the IUSU support service startup success notification.
  • NSCDF can parse the notification, determine the service identifier included in the notification based on the parsing result, and then record the service corresponding to the service identifier.
  • NSCDF can record the service corresponding to the service identifier included in the successful service launch notification supported by IUSU, thereby improving the effectiveness of storing the services supported by IUSU. Then, when a user's service request is received, the service supported by IUSU can be obtained from NSCDF and the service supported by IUSU can be quickly determined whether IUSU supports the service request.
  • the above method is used by SMG, and the method further includes: sending a service release notification to NSCDF, wherein the service release notification is used to instruct NSCDF to download the software data of the service corresponding to the service release notification from SMG.
  • SMG needs to approve the software data submitted by the software provider. If the software data matches IUSU, the approval is granted; if the software data does not match IUSU, the approval is denied.
  • This approval process may include reviewing the code and data format of the software packages within the software data.
  • the SMG can generate a service request after approving the software data submitted by the software provider.
  • the system issues a notification and sends a service release notification to the NSCDF, enabling the NSCDF to download the software data for the service corresponding to the service release notification from the SMG.
  • the SMG sends a service release notification to the NSCDF. Since the service release notification is used to instruct the NSCDF to download the software data of the service corresponding to the service release notification from the SMG, the NSCDF can quickly determine that the SMG contains approved software data through the service release notification, and thus download the approved software data from the SMG, thereby improving the efficiency of the NSCDF in downloading software data from the SMG.
  • the SMG can send the requested software data to the NSCDF upon receiving a second service software data download request from the NSCDF.
  • the method further includes:
  • Step 901 Receive the second service software data download request sent by NSCDF.
  • the NSCDF can determine whether its own storage space meets the storage space requirements of the software data based on the service release notification. If it does, the NSCDF generates a second service software data download request and sends it to the SMG, so that the SMG can receive the second software data download request sent by the NSCDF.
  • Step 902 Send software data to NSCDF according to the service identifier carried in the second service software data download request.
  • SMG since SMG may contain multiple approved software data, when SMG receives a software data download request, it cannot determine the corresponding software data. Therefore, it can determine the business based on the business identifier, and then determine the corresponding software data based on the business.
  • the SMG can parse the second service software data download request, determine the service identifier based on the parsing result, then determine the corresponding service based on the service identifier, and then determine the software data corresponding to the service as the software data corresponding to the second service software data download request and send it to the NSCDF.
  • the SMG receives a second service software data download request sent by the NSCDF and can send software data to the NSCDF according to the service identifier carried in the second service software data download request. Since the SMG can quickly and accurately determine the service corresponding to the service identifier, it can determine the software data corresponding to the service as the software data corresponding to the second service software data download request, and then send the determined software data to the NSCDF, thereby improving the efficiency and accuracy of the software data sent to the NSCDF.
  • Figure 10 provides a signaling interaction flowchart for a service enablement method. As shown in Figure 10, the method includes the following steps:
  • SMG upon receiving and approving the software data, SMG generates and sends a notification to NSCDF for service publication.
  • NSCDF determines whether it meets the storage space requirements of the software data included in the business release notification, and if the storage space requirements are met, NSCDF sends a second business software data download request to SMG.
  • S3 SMG sends software data to NSCDF based on the service identifier carried in the second service software data download request.
  • NSCDF sends a business software download notification to IUSU.
  • IUSU determines whether it meets the business resource requirements included in the business download notification, and if it meets the business resource requirements and is configured to support business self-enablement, it reserves the business resources corresponding to the business resource requirements and sends the first business software data download request to NSCDF.
  • NSCDF sends software data to IUSU based on the service identifier included in the first service software data download request.
  • IUSU loads the software corresponding to the software data and enables the corresponding services.
  • IUSU records the service identifier corresponding to the service software data in the list of services supported by IUSU.
  • S9 sends a service startup success notification to NSCDF.
  • NSCDF records IUSU support services corresponding to service identifiers.
  • Figure 11 is a schematic diagram of an application scenario of a service processing method provided in an embodiment of this application.
  • the scenario includes NSCDF200, a first IUSU400, a second IUSU500, and a terminal 600.
  • the first IUSU400 transmits data with NSCDF200, the second IUSU500, and the terminal 600 via the network.
  • the terminal 600 also transmits data with the second IUSU500 via the network.
  • the terminal 600 can send a service request to the first IUSU400.
  • the first IUSU can send a service capability query request to NSCDF200, generate a failure response based on the service capability query response returned by NSCDF200, and send the failure response to the terminal 600.
  • the terminal 600 can select a second IUSU500 based on the failure response and initiate a user registration request to the second IUSU500.
  • a business processing method is provided, which is applied to the first IUSU400 in FIG12. Taking this as an example, the first IUSU can perform business processing after enabling services using the above-mentioned business enabling method.
  • This business processing method includes the following steps:
  • Step 1201 Receive the service request sent by the terminal.
  • the first IUSU refers to a private IUSU, which is a network element created and managed by the user.
  • the first IUSU can only provide services to registered users and provided that the software corresponding to the service request exists.
  • the service request is a request generated by the terminal based on the user's software usage request, used to apply to the first IUSU for the corresponding service.
  • the first IUSU can receive service requests sent by the terminal.
  • the service request received by the first IUSU may be responsive, or the service request received by the first IUSU may be unresponsive.
  • Step 1202 If the service corresponding to the service request is not supported, a failure response is returned to the terminal.
  • the failure response is used to instruct the terminal to register with the second IUSU that supports the service.
  • the second IUSU refers to the public IUSU, which is a network element created and managed by the operator.
  • the second IUSU can provide services to all users. It should be noted that different service requests may correspond to different software. If the first IUSU includes the software corresponding to the service request, then the service request will be responded to; if the first IUSU does not include the software corresponding to the service request, then the service request will not be responded to.
  • the first IUSU can return a failure response to the terminal, and the failure response may include a second IUSU that supports the service corresponding to the service request, thereby instructing the terminal to register with the second IUSU.
  • the terminal After registering with the second IUSU, the terminal can initiate a service request to the second IUSU to realize the response to the terminal's service request.
  • the terminal corresponding to the user can register with a public IUSU to apply for services, for example, by initiating service registration with the second IUSU that supports the service corresponding to the service request.
  • the first IUSU by receiving the business request sent by the terminal, can return a failure response to the terminal if it does not support the business corresponding to the business request. Since the failure response can instruct the terminal to register with the second IUSU that supports the business, the terminal can be instructed to register with the second IUSU if the first IUSU cannot respond to the business request, thus avoiding the problem of the business request initiated by the terminal being unresponsive, thereby improving the reliability of providing services to users.
  • the first IUSU can determine whether to support the service request based on the service identifier of the service request itself.
  • the method further includes:
  • Step 1301 Determine whether the service is supported based on the service identifier included in the service request and the list of services supported by the first IUSU.
  • the business identifier is used to represent the business information corresponding to the business request. Different business identifiers correspond to different business requests.
  • the first IUSU is based on
  • the first IUSU can parse the service request, determine the service identifier corresponding to the service request based on the parsing result, and then query whether the first IUSU exists in the service list supported by the first IUSU. Based on the query result, it can determine whether the first IUSU supports the service corresponding to the service request.
  • Step 1302 If the service identifier is not in the service list, determine that the service is not supported.
  • a service identifier exists in the service list, it means that the first IUSU includes the software for the service corresponding to that service identifier, and the first IUSU can provide the service for that service; if a service identifier does not exist in the service list, it means that the first IUSU does not include the software for the service corresponding to that service identifier, and the first IUSU cannot provide the service for that service.
  • the first IUSU determines that the service identifier is not in the service list, it means that the first IUSU does not include the software of the service corresponding to the service identifier. That is, the first IUSU cannot provide the service corresponding to the service to the terminal, and it can be determined that the first IUSU does not support the service.
  • the first IUSU can quickly determine whether a service identifier exists in the service list based on the service identifier included in the service request and the service list supported by the first IUSU. This allows it to quickly determine whether the first IUSU supports the service. Furthermore, if the service identifier is not in the service list, it can quickly determine that the first IUSU does not support the service, thus improving the response speed of the first IUSU to service requests.
  • step 1202 above may include:
  • Step 1401 Generate a failure response based on the service capability query response sent by NSCDF.
  • the failure response includes a list of service support IUSUs.
  • the service capability query response refers to the response message that NSCDF sends after receiving a service capability query from the first IUSU. It can be understood that NSCDF can record the services corresponding to the software that is installed and successfully running in the first IUSU. Therefore, after receiving the service capability query from the first IUSU, it can combine the recorded information to determine which services the public IUSUs included in the service capability query support, thereby generating a list of service-supported IUSUs. This list includes the identifiers of the public IUSUs that support the requested service.
  • the first IUSU when it cannot support the service corresponding to the service request, it can send query information including its own pre-configured list of public IUSUs to the NSCDF, thereby receiving the service capability query response generated by the NSCDF based on the query information and pre-stored records. Then, by parsing the service capability query response, it can obtain the list of service-supporting IUSUs and generate a failure response based on the IUSUs that support the service corresponding to the service request.
  • the service-supported IUSU list includes the identifiers of one or more second IUSUs that support the service in the public IUSU list.
  • the second IUSU is a pre-configured public IUSU within the first IUSU that can provide services to all users.
  • the public IUSU list may include identifiers of one or more second IUSUs. It should be noted that for different service requests, some second IUSUs support the corresponding service, while others do not. Therefore, for a given service request, it is necessary to determine the second IUSU supporting the service from the public IUSU list and generate a service-supported IUSU list based on all supporting second IUSUs.
  • the service-supported IUSU list may include the identifier of one second IUSU supporting the service request, or it may include the identifiers of multiple second IUSUs supporting the service request.
  • Step 1402 Send a failure response to the terminal.
  • the first IUSU can send the generated failure response to the terminal via the network.
  • the first IUSU generates a failure response based on the list of service-supporting IUSUs in the service capability query response sent by NSCDF.
  • This failure response includes the identifier of the public IUSU that supports the service request.
  • the terminal then sends the failure response to the terminal, enabling the terminal to determine the public IUSU that can support the service request based on the failure response.
  • the terminal can then re-register with the public IUSU and send the service request, thereby obtaining the service provided by the public IUSU.
  • the first IUSU can send a service capability query request to NSCDF and receive the service capability query response returned by NSCDF.
  • the method further includes:
  • Step 1501 Send a service capability query request to NSCDF; the service capability query request includes a list of public IUSUs configured in the first IUSU.
  • the service capability query request is a request used by the first IUSU to obtain information from the NSCDF about the public IUSUs configured to provide services to all users. It should be noted that different public IUSUs can be configured for different first IUSUs. When the first IUSU cannot support the service corresponding to the service request, it can instruct the terminal to register with its own configured public IUSUs and resend the service request.
  • the public IUSU list is a list of pre-configured public IUSUs in the first IUSU.
  • the first IUSU can generate a service capability management query request based on its own pre-configured list of public IUSUs and send the service capability query request to NSCDF.
  • Step 1502 Receive the business capability query response sent by NSCDF in response to the business capability query request; the business capability query response includes a list of business support IUSUs.
  • the first IUSU can receive a service capability query response generated by NSCDF based on the service capability query request via the network, and then determine the public IUSU that supports a certain service request through the service support IUSU list in the service capability query response.
  • the first IUSU sends a service capability query request, which includes a list of public IUSUs configured by the first IUSU, to the NSCDF.
  • a service capability query request which includes a list of public IUSUs configured by the first IUSU
  • the first IUSU can determine the public IUSUs that support the service corresponding to the service request.
  • the first IUSU can return a failure response, which includes a list of service-supporting IUSUs, to the terminal. This instructs the terminal to re-register with the IUSUs in the list of service-supporting IUSUs and resend the service request, thereby improving the reliability of providing services to users.
  • the following describes the interaction process of the business processing method using NSCDF as the execution entity.
  • the above method is used in NSCDF, as shown in Figure 16.
  • the method further includes:
  • Step 1601 Receive the service capability query request sent by the first IUSU.
  • the service capability query request is generated by the first IUSU when it cannot support the service corresponding to the service request sent by the terminal. And sent.
  • the business capability query request may include a list of pre-configured public IUSUs in the first IUSU.
  • NSCDF can receive a service capability query request sent by the first IUSU via the network.
  • Step 1602 Return a business capability query response to the first IUSU.
  • the business capability query response contains the identifiers of one or more second IUSUs that support the business corresponding to the business capability query request.
  • the business capability query response is generated by NSCDF based on the business capability query request and after checking whether the public IUSUs in the public IUSU list in the business capability query request support the business request corresponding to the business request. If the public IUSU in the public IUSU list supports the business request corresponding to the business request, then the public IUSU is determined as the second IUSU, and a business capability query response is generated based on all the second IUSUs and returned to the first IUSU.
  • NSCDF receives a service capability query request sent by a first IUSU. It can determine a second IUSU that supports the service request corresponding to the service capability query request based on the list of common IUSUs in the service capability query request. It can then generate a service capability query response based on the second IUSU and return the service capability query response to the first IUSU. This enables the first IUSU to generate a failure response based on the service capability query response, ensuring that the terminal can re-determine a second IUSU that can support the service request based on the failure response, thereby improving the reliability of providing services for the service requests sent by the terminal.
  • the following describes the interaction process of the business processing method, using the terminal as the execution subject.
  • the above method is used on a terminal, as shown in Figure 17.
  • the method further includes:
  • Step 1701 Send a service request to the first IUSU.
  • a service request refers to a user's request to use a specific software.
  • the terminal when the terminal receives a user's request to use the software, it can generate a service request based on the software usage request and send the generated service request to the first IUSU via the network.
  • the first IUSU can be an IUSU that the user corresponding to the business request has pre-registered.
  • Step 1702 When a failure response is received from the first IUSU, a second IUSU is selected based on the failure response, and a user registration request is sent to the second IUSU.
  • the failure response may include a public IUSU that can provide the service corresponding to the software to the user, namely the second IUSU.
  • the terminal will receive a failure response returned by the first IUSU.
  • a failure response returned by the first IUSU.
  • a second IUSU that supports the service corresponding to the service request can be obtained.
  • a second IUSU can be determined from the parsing result, and a user registration request can be initiated to the second IUSU.
  • the failure response may include multiple second IUSUs, from which the terminal can select any one of the second IUSUs and initiate a user registration request to the selected second IUSU.
  • the terminal can, upon receiving a failure response from the first IUSU, select one of the multiple second IUSUs included in the failure response and initiate a user registration request to the second IUSU.
  • This allows the terminal to send a service request to the second IUSU if the registration request is successful. Since the second IUSU supports the service corresponding to the service request, after the terminal sends the service request to the second IUSU, the second IUSU can support the service corresponding to the service request and thus respond to the service request, improving the reliability of providing services to the user.
  • Figure 18 provides a signaling interaction flowchart of a service processing method. As shown in Figure 18, the method includes the following steps.
  • the first IUSU receives the service request sent by the terminal.
  • the service corresponding to the service request is not supported, determine whether the service is supported based on the service identifier included in the service request of the first IUSU and the list of services supported by the first IUSU. If the service identifier is not in the list of services, the first IUSU determines that the service is not supported.
  • the first IUSU sends a service capability query request to NSCDF.
  • NSCDF returns a business capability query response to the first IUSU.
  • the first IUSU generates a failure response based on the service capability query response sent by NSCDF and sends the failure response to the terminal.
  • the terminal selects a second IUSU and initiates a user registration request to the second IUSU.
  • steps in the flowchart above are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart above may include multiple steps or multiple stages, and these steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of segments is not necessarily sequential; rather, they can be executed alternately or in turn with other steps or at least a portion of steps or stages within other steps.
  • a service enabling device including: a first receiving module 1901, a downloading module 1902, and a startup module 1903, wherein:
  • the first receiving module 1901 is used to receive service software download notifications sent by the Network and Service Capability Storage Function (NSCDF).
  • NSCF Network and Service Capability Storage Function
  • the download module 1902 is used to download the software data of the corresponding business from the NSCDF according to the business download notification.
  • the startup module 1903 is used to load and start the software corresponding to the software data.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the download module 1901 includes: a determining unit, a processing unit, and a first download unit, wherein:
  • the determination unit is used to determine whether the IUSU meets the business resource requirements included in the business download notification.
  • the processing unit is used to reserve the business resources corresponding to the business resource requirements when the IUSU meets the business resource requirements and is configured to support business self-enablement.
  • the first download unit is used to download software data from NSCDF.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the download unit is specifically configured to: send a first service software data download request to the NSCDF, the first service software data download request including a service identifier; and receive software data sent by the NSCDF in response to the first service software data download request.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes a first recording module, wherein:
  • the first recording module is used to record the service identifier corresponding to the service software data in the list of services supported by IUSU, which indicates the service corresponding to the service identifier supported by IUSU.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes a first transmitting module, wherein:
  • the first sending module is used to send a service launch success notification to NSCDF.
  • the service launch success notification includes a service identifier and is used to notify NSCDF to record the IUSU that supports the service corresponding to the service identifier.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • a service enabling device comprising: a second transmitting module 2001, wherein:
  • the second sending module 2001 is used to send a service software download notification to the IUSU.
  • the service software download notification is used to instruct the IUSU to download the software data of the corresponding service from the NSCDF.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the second sending module 2001 includes: a receiving unit and a second downloading unit, wherein:
  • the receiving unit is used to receive service release notifications sent by the Service Management Gateway (SMG).
  • SMG Service Management Gateway
  • the second download unit is used to download software data from SMG based on business release notifications.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the second download unit is specifically used to: determine whether the NSCDF meets the storage space requirements of the software data included in the service release notification; if the NSCDF meets the storage space requirements, send a second service software data download request to the SMG; the second service software data download request includes a service identifier; receive the software data sent by the SMG according to the second service software data download request, and store the software data.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes a first receiving module and a third transmitting module, wherein:
  • the first receiving module is used to receive the first service software data download request sent by IUSU.
  • the third sending module is used to send software data to IUSU based on the service identifier included in the first service software data download request.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes: a second receiving module and a second recording module, wherein:
  • the second receiving module is used to receive the service startup success notification sent by IUSU.
  • the second recording module is used to record the service corresponding to the service identifier included in the IUSU support service startup success notification.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • a service enabling device including: a fourth transmitting module 2101, wherein:
  • the fourth sending module 2101 is used to send a service release notification to the NSCDF.
  • the service release notification is used to instruct the NSCDF to download the software data of the service corresponding to the service release notification from the SMG.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes: a third receiving module and a fifth transmitting module, wherein:
  • the third receiving module is used to receive the second service software data download request sent by NSCDF.
  • the fifth sending module is used to send software data to NSCDF based on the service identifier carried in the second service software data download request.
  • the service enabling device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • a service processing apparatus including: a fourth receiving module 2201 and a sixth transmitting module 2202, wherein:
  • the fourth receiving module 2201 is used to receive service requests sent by the terminal;
  • the sixth sending module 2202 is used to return a failure response to the terminal when the service corresponding to the service request is not supported.
  • the failure response is used to instruct the terminal to register with the second IUSU that supports the service.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-mentioned apparatus includes: a first determining module and a second determining module, wherein:
  • the first determination module is used to determine whether a service is supported based on the service identifier included in the service request and the list of services supported by the first IUSU;
  • the second determination module is used to determine that the service is not supported if the service identifier is not in the service list.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the sixth transmitting module 2202 includes: a generating unit and a transmitting unit, wherein:
  • the generation unit is used to generate a failure response based on the service capability query response sent by NSCDF.
  • the failure response includes a list of service-supporting IUSUs.
  • the list of service-supporting IUSUs includes the identifiers of one or more second IUSUs that support the service in the public IUSU list.
  • the sending unit is used to send a failure response to the terminal.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • the above-described apparatus further includes: a seventh transmitting module and a fifth receiving module, wherein:
  • the seventh sending module is used to send a service capability query request to the NSCDF; the service capability query request includes a list of public IUSUs configured in the first IUSU.
  • the fifth receiving module is used to receive the service capability query response sent by NSCDF in response to the service capability query request; the service capability query response includes a list of service support IUSUs.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • a service processing apparatus including: a sixth receiving module 2301 and an eighth transmitting module 2302, wherein:
  • the sixth receiving module 2301 is used to receive the service capability query request sent by the first IUSU.
  • the service capability query request is sent by the first IUSU when it does not support the service corresponding to the service request sent by the terminal.
  • the eighth sending module 2302 is used to return a service capability query response to the first IUSU, and the service capability query response is used to indicate at least one second IUSU that supports the service.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • a service processing apparatus including: a ninth sending module 2401 and a tenth sending module 2402, wherein:
  • the ninth sending module 2401 is used to send a service request to the first IUSU.
  • the tenth sending module 2402 is used to, if it receives a failure response returned by the first IUSU, initiate a user registration request to the second IUSU, which includes at least one service supporting the service request, in the failure response.
  • the business processing device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
  • Each module in the aforementioned business processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.
  • FIG25 is a schematic diagram of the structure of the access network device provided in this embodiment.
  • the access network device may include a receiver 251, a memory 252, a processor 253, at least one communication bus 254, and a transmitter 255.
  • the communication bus 254 is used to realize communication connections between components.
  • the memory 252 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage.
  • the memory 252 can store various programs for performing various processing functions and implementing the method steps of this embodiment.
  • the transmitter 255 may be a radio frequency processing module or a baseband processing module in the access network device
  • the receiver 251 may also be a radio frequency processing module or a baseband processing module in the access network device.
  • the transmitter 255 and the receiver 251 may be integrated together to form a transceiver. Both the transmitter 255 and the receiver 251 may be coupled to the processor 253, and can perform receiving or transmitting actions under the instruction or control of the processor 253.
  • the receiver is used to receive the service software download notification sent by the Network and Service Capability Storage Function (NSCDF); the processor is used to download the software data of the service corresponding to the service download notification from the NSCDF; the processor is also used as a transmitter to load the software corresponding to the software data and enable the service corresponding to the software.
  • NSCDF Network and Service Capability Storage Function
  • the processor is used to determine whether the IUSU meets the service resource requirements included in the service download notification; if the IUSU meets the service resource requirements and is configured to support service self-enablement, it reserves the service resources corresponding to the service resource requirements; and downloads software data from the NSCDF.
  • the transmitter is used to send a first service software data download request to the NSCDF, the first service software data download request including a service identifier; the receiver is used to receive software data sent by the NSCDF in response to the first service software data download request.
  • the processor is used to record the service identifier corresponding to the service software data in the list of services supported by IUSU, so as to indicate the service corresponding to the service identifier supported by IUSU.
  • the transmitter is used to send a service launch success notification to the NSCDF.
  • the service launch success notification includes a service identifier and is used to notify the NSCDF to record the IUSU that it supports the service corresponding to the service identifier.
  • FIG26 is a schematic diagram of the structure of an access network device provided in an embodiment of this application.
  • the access network device may include a receiver 261, a memory 262, a processor 263, at least one communication bus 264, and a transmitter 265.
  • the communication bus 264 is used to realize communication connections between components.
  • the memory 262 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage.
  • NVM non-volatile memory
  • the memory 262 can store various programs for performing various processing functions and implementing the method steps of this embodiment.
  • the transmitter 265 may be a radio frequency processing module or a baseband processing module in the access network device
  • the receiver 261 may also be a radio frequency processing module or a baseband processing module in the access network device.
  • the transmitter 265 and receiver 261 can be integrated together to form a transceiver. Both the transmitter 265 and receiver 261 can be coupled to the processor 263, and can perform the actions of receiving or transmitting under the instruction or control of the processor 263.
  • the transmitter is used to send a service software download notification to the IUSU.
  • the service software download notification is used to instruct the IUSU to download the software data of the service corresponding to the service download notification from the NSCDF.
  • the receiver is used to receive a service release notification sent by the Service Management Gateway (SMG); the processor is used to download software data from the SMG according to the service release notification.
  • SMG Service Management Gateway
  • the processor determines whether the NSCDF meets the storage space requirements of the software data included in the service release notification; if the NSCDF meets the storage space requirements, it sends a second service software data download request to the SMG; the second service software data download request includes a service identifier; it receives the software data sent by the SMG according to the second service software data download request and stores the software data.
  • the receiver is configured to receive a first service software data download request sent by the IUSU; the transmitter is configured to send software data to the IUSU according to the service identifier included in the first service software data download request.
  • the receiver is used to receive a service launch success notification sent by the IUSU; the processor is used to record the service corresponding to the service identifier included in the IUSU support service launch success notification.
  • FIG27 is a schematic diagram of the structure of the access network device provided in this embodiment.
  • the access network device may include a receiver 2671, a memory 272, a processor 273, at least one communication bus 274, and a transmitter 275.
  • the communication bus 274 is used to realize communication connections between components.
  • the memory 272 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage.
  • the memory 272 can store various programs for performing various processing functions and implementing the method steps of this embodiment.
  • the transmitter 275 may be a radio frequency processing module or a baseband processing module in the access network device
  • the receiver 271 may also be a radio frequency processing module or a baseband processing module in the access network device.
  • the transmitter 275 and the receiver 271 may be integrated together to form a transceiver. Both the transmitter 275 and the receiver 271 may be coupled to the processor 273, and can perform receiving or transmitting actions under the instruction or control of the processor 273.
  • the transmitter is used to send a service release notification to the NSCDF, which instructs the NSCDF to download the software data of the service corresponding to the service release notification from the SMG.
  • the receiver is used to receive a second service software data download request sent by the NSCDF; the transmitter is used to send software data to the NSCDF according to the service identifier carried in the second service software data download request.
  • FIG28 is a schematic diagram of the structure of the access network device provided in this embodiment.
  • the access network device may include a receiver 281, a memory 282, a processor 283, at least one communication bus 284, and a transmitter 285.
  • the communication bus 284 is used to realize communication connections between components.
  • the memory 282 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage.
  • the memory 282 can store various programs for performing various processing functions and implementing the method steps of this embodiment.
  • the transmitter 285 may be a radio frequency processing module or a baseband processing module in the access network device
  • the receiver 281 may also be a radio frequency processing module or a baseband processing module in the access network device.
  • the transmitter 285 and the receiver 281 may be integrated together to form a transceiver. Both the transmitter 285 and the receiver 281 may be coupled to the processor 283, and can perform receiving or transmitting actions under the instruction or control of the processor 283.
  • the receiver is used to receive service requests sent by the terminal; the transmitter is used to return a failure response to the terminal if the service corresponding to the service request is not supported, and the failure response is used to instruct the terminal to register with the second IUSU that supports the service.
  • the processor is configured to determine whether a service is supported based on the service identifier included in the service request and the list of services supported by the first IUSU; if the service identifier is not in the service list, it is determined that the service is not supported.
  • the processor is used to generate a failure response based on the service capability query response sent by NSCDF, the failure response including a list of service-supported IUSUs; the transmitter is used to send the failure response to the terminal.
  • the transmitter is used to send a service capability query request to the NSCDF;
  • the service capability query request includes a list of public IUSUs configured for the first IUSU;
  • the receiver is used to receive a service capability query response sent by the NSCDF in response to the service capability query request;
  • the service capability query response includes a list of service-supporting IUSUs.
  • FIG29 is a schematic diagram of the structure of an access network device provided in this embodiment.
  • the access network device may include a receiver 291, a memory 292, a processor 293, at least one communication bus 294, and a transmitter 295.
  • the communication bus 294 is used to realize communication connections between components.
  • the memory 292 may include a high-speed RAM memory, and may also include non-volatile memory (NVM), such as at least one disk storage.
  • the memory 292 can store various programs for performing various processing functions and implementing the method steps of this embodiment.
  • the transmitter 295 may be a radio frequency processing module or a baseband processing module in the access network device
  • the receiver 291 may also be a radio frequency processing module or a baseband processing module in the access network device.
  • the transmitter 295 and receiver 291 can be integrated together to form a transceiver. Both the transmitter 295 and receiver 291 can be coupled to the processor 293, and can perform the actions of receiving or transmitting under the instruction or control of the processor 293.
  • the receiver is used to receive a service capability query request sent by the first IUSU; the transmitter is used to return a service capability query response to the first IUSU, and the service capability query response contains the identifiers of one or more second IUSUs that support the service corresponding to the service capability query request.
  • FIG30 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention.
  • the terminal device 3000 shown in FIG30 includes: at least one processor 3001, a memory 3002, at least one network interface 3004, and a user interface 3003.
  • the various components in the terminal device 3000 are coupled together through a bus system 3005.
  • the bus system 3005 is used to realize the connection and communication between these components.
  • the bus system 3005 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 3005 in FIG1.
  • the embodiment of the present invention also includes a transceiver 3006, which may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.
  • the user interface 3003 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).
  • clicking device e.g., mouse, trackball, touchpad, or touchscreen.
  • the memory 3002 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory.
  • the volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous DRAM
  • DDRSDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous DRAM
  • SLDRAM Synchronous Link DRAM
  • DRRAM Direct Rambus RAM
  • memory 3002 stores elements, executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 30021 and application programs 30022.
  • the operating system 30021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks.
  • the application program 30022 includes various applications, such as a media player and a browser, used to implement various application functions.
  • the program implementing the method of this embodiment can be included in the application program 30022.
  • the transmitter is used to send a service request to the first IUSU; the processor is used to... If a failure response is received from the first IUSU, a second IUSU is selected based on the failure response, and a user registration request is initiated to the second IUSU. It is understood that the embodiments described in this invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field-programmable gate arrays
  • general-purpose processors controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.
  • the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention.
  • the software code can be stored in memory and executed by processor 3001.
  • the memory can be implemented in processor 3001 or external to processor 3001.
  • a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.
  • a computer program product including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
  • Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM may take many forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请涉及一种业务使能方法、业务处理方法、装置、通信设备、计算机可读存储介质和计算机程序产品。所述方法用于综合用户服务单元IUSU,所述方法包括:接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;从所述NSCDF中下载所述业务下载通知对应业务的软件数据;装载所述软件数据对应的软件,并使能所述软件对应的业务。采用本方法能够实现6G网络架构中的业务使能。

Description

业务使能方法、业务处理方法、装置和通信设备
本申请要求于2024年5月29日提交中国专利局,申请号为2024106824121,申请名称为“业务使能方法、业务处理方法、装置和通信设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,特别是涉及一种业务使能方法、业务处理方法、装置、通信设备、计算机可读存储介质和计算机程序产品。
背景技术
关于6G(6th Generation Mobile Networks,第六代移动通信系统)的研究正在积极开展,关于6G网络架构的猜想很多,例如,相关项目中提出了一种基于综合用户服务单元的6G网络架构,综合用户服务单元可以向终端提供用户根据自身需求所定义的网络功能和业务支持。
但是,基于该网络架构,如何实现业务使能目前还未解决。
发明内容
本申请实施例提供一种业务使能方法、装置、通信设备、计算机可读存储介质和计算机程序产品,可以实现6G网络架构中的业务使能。
第一方面,本申请提供了一种方法,用于综合用户服务单元IUSU,所述方法包括:
接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;
从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
装载所述软件数据对应的软件,并使能所述软件对应的业务。
在其中一个实施例中,所述从所述NSCDF中下载所述业务下载通知对应业务的软件数据,包括:
确定所述IUSU是否满足所述业务下载通知中包括的业务资源需求;
在所述IUSU满足所述业务资源需求,且配置为支持业务自主使能的情况下,预留所述业务资源需求对应的业务资源;
从所述NSCDF下载所述软件数据。
在其中一个实施例中,所述从所述NSCDF中下载所述软件数据,包括:
向所述NSCDF发送第一业务软件数据下载请求,所述第一业务软件数据下载请求中包括所述业务标识;
接收所述NSCDF针对所述第一业务软件数据下载请求发送的所述软件数据。
在其中一个实施例中,所述方法还包括:
在所述IUSU支持的业务列表中,记录所述业务软件数据对应的业务标识,用于表明所述IUSU支持所述业务标识对应的业务。
在其中一个实施例中,所述方法还包括:
向所述NSCDF发送业务启动成功通知,所述业务启动成功通知中包括所述业务标识,所述业务启动成功通知用于通知所述NSCDF记录所述IUSU支持所述业务标识对应的业务。
在其中一个实施例中,用于NSCDF,所述方法包括:
向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
在其中一个实施例中,所述向IUSU发送业务下载通知之前,所述方法还包括:
接收业务管理网关SMG发送的业务发布通知;
根据所述业务发布通知,从所述SMG中下载所述软件数据。
在其中一个实施例中,所述根据所述业务发布通知,从所述SMG中下载所述软件数据,包括:
确定所述NSCDF是否满足所述业务发布通知中包括的软件数据的存储空间需求;
当所述NSCDF满足所述存储空间需求时,向所述SMG发送第二业务软件数据下载请求;所述第二业务软件数据下载请求中包括业务标识;
接收所述SMG根据所述第二业务软件数据下载请求发送的所述软件数据,并存储所述软件数据。
在其中一个实施例中,所述方法还包括:
接收所述IUSU发送的第一业务软件数据下载请求;
根据所述第一业务软件数据下载请求中包括的业务标识,向所述IUSU发送所述软件数据。
在其中一个实施例中,所述方法还包括:
接收所述IUSU发送的业务启动成功通知;
记录所述IUSU支持所述业务启动成功通知中包括的所述业务标识对应的业务。
在其中一个实施例中,用于SMG,所述方法包括:
向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF从所述SMG中下载所述业务发布通知对应业务的软件数据。
在其中一个实施例中,所述方法还包括:
接收所述NSCDF发送的第二业务软件数据下载请求;
根据所述第二业务软件数据下载请求携带的业务标识,向所述NSCDF发送所述软件数据。
第二方面,本申请还提供了一种业务处理方法,用于第一IUSU,所述第一IUSU利用上述第一方面任一项所述的业务使能方法进行业务使能,所述方法包括:
接收终端发送的业务请求;
在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
在其中一个实施例中,所述方法还包括:
根据所述业务请求中包括的业务标识和所述第一IUSU支持的业务列表,确定是否支持所述业务;
当所述业务标识未在所述业务列表中时,确定不支持所述业务。
在其中一个实施例中,所述向所述终端返回失败响应,包括:
根据NSCDF发送的业务能力查询响应,生成所述失败响应,所述失败响应中包括业务支持IUSU列表;
向所述终端发送所述失败响应。
在其中一个实施例中,所述方法还包括:
向所述NSCDF发送业务能力查询请求;所述业务能力查询请求中包括所述第一IUSU配置的公共IUSU列表;
接收所述NSCDF针对所述业务能力查询请求发送的所述业务能力查询响应;所述业务能力查询响应中包括所述业务支持IUSU列表。
在其中一个实施例中,所述业务支持IUSU列表中包括所述公共IUSU列表中支持所述业务的一个或多个所述第二IUSU的标识。
在其中一个实施例中,用于NSCDF,所述方法包括:
接收第一IUSU发送的业务能力查询请求;
向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应中包含一个或多个支持所述业务能力查询请求对应业务的第二IUSU的标识。
在其中一个实施例中,一种业务处理方法,用于终端,所述方法包括:
向第一IUSU发送业务请求;
当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,选择一个第二IUSU,并向所述第二IUSU发起用户注册请求。
第三方面,本申请还提供了一种装置,用于IUSU,所述装置包括:
第一接收模块,用于接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;
下载模块,用于根据所述业务下载通知,从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
启动模块,用于装载并启动所述软件数据对应的软件。
第四方面,本申请还提供了一种装置,用于NSCDF,所述装置包括:
第二发送模块,用于向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
第五方面,本申请还提供了一种装置,用于SMG,所述装置包括:
第四发送模块,用于向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF根据所述业务发布通知从所述SMG中下载所述业务发布通知对应业务的软件数据。
第六方面,本申请还提供了一种业务处理装置,用于第一IUSU,所述装置包括:
第四接收模块,用于接收终端发送的业务请求;
第六发送模块,用于在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
第七方面,本申请还提供了一种业务处理装置,用于NSCDF,所述装置包括:
第六接收模块,用于接收第一IUSU发送的业务能力查询请求,所述业务能力查询请求为所述第一IUSU在不支持终端发送的业务请求对应的业务的情况下发送的;
第八发送模块,用于向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应用于指示至少一个支持所述业务的第二IUSU。
第八方面,本申请还提供了一种业务处理装置,用于终端,所述装置包括:
第九发送模块,用于向第一IUSU发送业务请求;
第十发送模块,用于当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,向所述失败响应中包括的至少一个支持所述业务请求对应的业务的第二IUSU发起用户注册请求。
第九方面,本申请还提供了一种通信设备。所述通信设备包括:接收器和处理器;
所述接收器用于接收网络和业务能力存储功能NSCDF发送的业务下载通知;
所述接收器还用于根据所述业务下载通知,从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
所述处理器用于装载并启动所述软件数据对应的软件。
第十方面,本申请还提供了一种通信设备。所述通信设备包括:发送器;
所述发送器,用于向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
第十一方面,本申请还提供了一种通信设备。所述通信设备包括:发送器;
所述发送器用于向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF根据所述业务发布通知从所述SMG中下载所述业务发布通知对应业务的软件数据。
第十二方面,本申请还提供了一种通信设备。所述通信设备包括:接收器和发送器;
所述接收器用于接收终端发送的业务请求;
所述发送器用于在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
第十三方面,本申请还提供了一种通信设备。所述通信设备包括:接收器和发送器;
所述接收器用于接收第一IUSU发送的业务能力查询请求,所述业务能力查询请求为所述第一IUSU在不支持终端发送的业务请求对应的业务的情况下发送的;
所述发送器用于向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应用于指示至少一个支持所述业务的第二IUSU。
第十四方面,本申请还提供了一种通信设备。所述通信设备包括:发送器;
所述发送器用于向第一IUSU发送业务请求;
所述发送器还用于当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,向所述失败响应中包括的至少一个支持所述业务请求对应的业务的第二IUSU发起用户注册请求。
第十五方面,本申请还提供了一种计算机可读存储介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现上述第一方面任一项所述的业务使能方法和第二方面任一项所述的业务处理方法。
第十六方面,本申请还提供了一种计算机程序产品,包括计算机程序,该计算机程序被处理器执行时实现上述第一方面任一项所述的业务使能方法和第二方面任一项所述的业务处理方法。
上述业务使能方法、业务处理方法、装置、通信设备、计算机可读存储介质和计算机程序产品,IUSU通过接收NSCDF发送的业务软件下载通知,从NSCDF中下载业务下载通知对应业务的软件数据,接着,通过装载软件数据对应的软件,就能够使能软件对应的业务,由于该业务使能方法中,IUSU根据接收的业务软件下载通知能够预先下载对应业务的软件数据,从而能装载该软件数据对应的软件,使得 IUSU在接收到用户的业务请求时,能够通过预先装载的软件向用户提供服务,避免了由于IUSU中不存在业务下载通知对应的业务的软件,而无法向用户提供对应的业务的服务的问题,进而能够使能软件对应的业务,实现6G网络架构中的业务使能。
附图说明
图1为一个实施例中业务使能方法的应用环境图;
图2为一个实施例中业务使能方法的流程示意图;
图3为一个实施例中步骤202的流程示意图;
图4为一个实施例中步骤303的流程示意图;
图5为另一个实施例中业务使能方法的流程示意图;
图6为一个实施例中步骤502的流程示意图;
图7为另一个实施例中业务使能方法的流程示意图;
图8为另一个实施例中业务使能方法的流程示意图;
图9为另一个实施例中业务使能方法的流程示意图;
图10为一个实施例中业务使能方法的信令交互示意图;
图11为一个实施例中业务处理方法的应用环境图;
图12为一个实施例中业务处理方法的流程示意图;
图13为另一个实施例中业务处理方法的流程示意图;
图14为一个实施例中步骤1002的流程示意图;
图15为另一个实施例中业务处理方法的流程示意图;
图16为另一个实施例中业务处理方法的流程示意图;
图17为另一个实施例中业务处理方法的流程示意图;
图18为一个实施例中业务处理方法的信令交互示意图;
图19为一个实施例中业务使能装置的结构框图;
图20为另一个实施例中业务使能装置的结构框图;
图21为另一个实施例中业务使能装置的结构框图;
图22为一个实施例中业务处理装置的结构框图;
图23为另一个实施例中业务处理装置的结构框图;
图24为另一个实施例中业务处理装置的结构框图;
图25为一个实施例中通信设备的内部结构图;
图26为另一个实施例中通信设备的内部结构图;
图27为另一个实施例中通信设备的内部结构图;
图28为另一个实施例中通信设备的内部结构图;
图29为另一个实施例中通信设备的内部结构图;
图30为另一个实施例中通信设备的内部结构图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
图1为本申请实施例提供的一种业务使能方法的应用场景示意图。如图1所示,该场景中包括综合用户服务单元(Integrated user-centric service unit,IUSU)100、网络和业务能力存储功能(Network and Service Capabilities Depository Functions,NSCDF)200、业务管理网关(Session Management Function,SMG)300。其中,IUSU100与NSCDF200之间通过网络进行数据传输,NSCDF200与SMG300之间通过网络进行数据传输。其中,SMG300向NSCDF200发送业务发布通知,NSCDF200在接收到业务发布通知,并从SMG300中下载业务发布通知对应的软件数据,,然后向IUSU100发送业务软件下载通知,IUSU在接收到业务软件下载通知,在满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源,从NSCDF中下载该软件数据,并装载软件数据对应的软件,使能软件对应的业务,从而实现6G网络架构中的业务使能。
相关技术中,运营商部署业务平台在接收到业务终端发送的业务请求之后,业务平台需要判断是否能够支持该业务请求,若可以支持,则下载该业务请求对应的软件,并响应该业务请求,为用户提供相应的业务,若无法支持,则向业务终端返回响应失败的消息。随着无线通信技术的发展,在6G网络架构中,提出了一种以支持用户为中心的综合服务单元为用户提供业务的模式,然而,传统技术中没有对在6G网络架构中,如何利用以支持用户为中心的综合服务单元实现业务使能进行规定和说明。因此,传统技术中存在无法实现6G网络架构中业务使能的问题。基于上述传统技术,本申请实施例提供业务使能方法,IUSU通过接收NSCDF发送的业务软件下载通知,从NSCDF中下载业务下载通知对应业务的软件数据,接着,通过装载软件数据对应的软件,就能够使能软件对应的业务,由于该业务使能方法中,IUSU根据接收的业务软件下载通知能够预先下载对应业务的软件数据,从而能装载该软件数据对应的软件,使得IUSU在接收到用户的业务请求时,能够通过预先装载的软件向用户提供服务,避免了由于IUSU中不存在业务下载通知对应的业务的软件,而无法向用户提供对应的业务的服务的问题,进而能够使能软件对应的业务,实现6G网络架构中的业务使能。通过IUSU通过接收NSCDF发送的业务软件下载通知,从NSCDF中下载业务下载通知对应业务的软件数据,接着,通过装载软件数据对应的软件,就能够使能软件对应的业务,由于该业务使能方法中,IUSU根据接收的业务软件下载通知能够预先下载对应业务的软件数据,从而能装载该软件数据对应的软件,使得IUSU在接收到用户的业务请求时,能够通过预先装载的软件向用户提供服务,避免了由于IUSU中不存在业务下载通知对应的业务的软件,而无法向用户提供对应的业务的服务的问题,进而能够使能软件对应的业务,实现6G网络架构中的业务使能。
需要说明的是,本申请实施例所带来的有益效果或者所解决的技术问题并不限定于这一个,还可以是其它隐含或者关联的问题,具体可以参见下述实施例的描述。
下面以具体地实施例对本申请的技术方案以及本申请的技术方案如何解决上述技术问题进行详细说明。下面这几个具体的实施例可以相互结合,对于相同或相似的概念或过程可能在某些实施例中不再赘述。下面将结合附图,对本申请的实施例进行描述。
在一个实施例中,如图2所示,提供了一种业务使能方法,以该方法应用于图1中的IUSU100为例进行说明,包括以下步骤:
步骤201,接收网络和业务能力存储功能NSCDF发送的业务软件下载通知。
需要说明的是,本申请的实施例是网络架构中接入网中的不同网元之间的交互过程。其中,IUSU是一个以用户为中心的综合服务单元的网元,可以为网络中固定、移动和卫星融合的特定用户提供选定的网络功能和服务能力,在一些实施例中,IUSU可以是由用户创建和管理的私人IUSU,能够为创建用户提供网络和服务;或者,IUSU也可以是由运营商创建和管理的公共IUSU,能够为所有用户提供网络和服务。可以理解的是,在接入网中,可以包括一个或多个IUSU。在本实施例中,可以以公共IUSU为例,对业务使能方法的交互过程进行介绍。
其中,NSCDF是支持IUSU所需的网络和服务的存储功能和下载功能的网元,业务软件下载通知是NSCDF发送给IUSU,用于指示IUSU需要下载某个用户业务相关的软件数据的信令,其中,业务软件下载通知中可以包括业务名称、业务描述、业务类型、业务标识、业务资源需求,业务资源需求在可以包括该业务对应的带宽、存储资源和计算资源等信息。可选的,业务软件下载通知中可以包括一个业务相关的信息,也可以包括多个业务相关的信息。
在本实施例中,IUSU可以通过接入网网络接收NSCDF发送的业务软件下载通知。作为一种可能的实施方式,可以在NSCDF中预先存储IUSU的标识,以用于NSCDF向指定的IUSU发送业务软件下载通知。
步骤202,从NSCDF中下载业务下载通知对应业务的软件数据。
其中,业务下载通知对应业务指的是业务下载通知中的业务标识和业务描述对应的业务,不同业务可以为用户提供不同的服务,每个业务对应有一个软件数据,其中,软件数据中可以包括该业务对应的软件包、软件包的安装说明等信息。在一些实施例中,软件数据中可以包括一个业务的软件数据,或者,也可以包括多个业务的软件数据,不同软件数据对应的业务标识不同。
在本实施例中,IUSU接收到业务软件下载通知之后,可以根据业务软件下载通知中的业务标识和业务描述确定业务软件下载通知对应的业务,然后从NSCDF中下载该业务的软件数据。
步骤203,装载软件数据对应的软件,并使能软件对应的业务。
可以理解的是,当IUSU中装载软件数据对应的软件之后,可以接收用户的软件使用请求,并通过该软件向用户提供相应的服务,即使能软件对应的业务。
在本实施例中,IUSU在下载软件数据之后,可以在IUSU中装载该软件数据对应的软件,在软件装载成功之后,可以在用户发起使用请求的时候,向用于提供该软件对应的服务,从而实现软件对应的业务的使能。
可以理解的是,若IUSU中没有预先下载业务对应的软件数据,则无法装载软件数据对应的软件,当IUSU接收到用户发起的业务请求时,就无法向用户提供该业务对应的服务,或者,当IUSU接收到用户发起的业务请求时,需要根据业务请求获取并装载对应业务的软件之后,才能够向用户提供该业务对应的服务。因此,IUSU预先下载业务对应的软件数据,并装载软件数据对应的软件,能够在实现业务使能,向用户提供服务的同时,实现软件对应业务的自主使能。
上述业务使能方法中,IUSU通过接收NSCDF发送的业务软件下载通知,从NSCDF中下载业务下载通知对应业务的软件数据,接着,通过装载软件数据对应的软件,就能够使能软件对应的业务,由于该业务使能方法中,IUSU根据接收的业务软件下载通知能够预先下载对应业务的软件数据,从而能装载该软件数据对应的软件,使得IUSU在接收到用户的业务请求时,能够通过预先装载的软件向用户提供服务,避免了由于IUSU中不存在业务下载通知对应的业务的软件,而无法向用户提供对应的业务的服务的问题,进而能够使能软件对应的业务,实现6G网络架构中的业务使能。
在上述所述从NSCDF中下载业务下载通知对应业务的软件数据的场景中,IUSU可以在确定自身满足软件数据的下载需求的情况下,从NSCDF下载该软件数据。在一个实施例中,如图3所示,上述步骤202可以包括:
步骤301,确定IUSU是否满足业务下载通知中包括的业务资源需求。
其中,业务资源需求指的是IUSU中下载业务对应的软件所需要的带宽,以及装载业务对应的软件所需要的存储资源和计算资源。可以理解的是,若IUSU需要下载业务对应的软件数据,则需要自身的业务资源能够满足软件数据的业务资源请求的,因此,IUSU在下载软件数据之前,需要确定自身是否满足业务资源需求。
在本实施例中,IUSU可以从接收的业务下载通知中获取业务资源需求,然后分别确定自身的带宽是否满足业务资源需求中的带宽,自身的存储资源是否满足业务资源需求中的存储资源,以及自身的计算资源是否满足业务资源需求中计算资源,从而确定是否满足业务下载通知中包括的业务资源需求。
步骤302,在IUSU满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源。
需要说明的是,在通过IUSU向用户提供服务之前,需要将IUSU配置为支持业务自主使能,才能在接收到用户发送的业务请求时,允许装载好的软件向用户提供相应的服务。
其中,业务资源指的是IUSU对应的带宽、计算资源和存储资源,IUSU需要确保自身的带宽能够满足业务资源需求中的带宽、自身的计算资源满足业务资源需求中的计算资源、自身的存储资源满足业务资源需求中的存储资源。
在本实施例中,IUSU可以在确定自身满足业务资源需求的情况,且支持业务自主使能的情况下,将满足业务资源需求的业务资源预留出来,以避免该部分业务资源被占用,导致下载软件数据失败的问题。
步骤303,从NSCDF下载软件数据。
在一些实施例中,IUSU也可以向NSCD发送指示信息,以指示NSCDF向IUSU发送软件数据,从而从NSCDF下载软件数据;或者,IUSU也可以在接收到业务软件下载通知的预设时长之后,接收到NSCDF发送的业务资源查询消息,并向NSCDF发送已预留业务资源需求对应的业务资源信息的消息,使得NSCDF在接收到该消息之后,可以向IUSU发送软件数据,从而从NSCDF下载软件数据。
本实施例中,IUSU通过确定自身是否满足业务下载通知中包括的业务资源需求,能够在自身满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源,然后从NSCDF下载软件数据,由于IUSU下载软件数据之前先确保了自身能够满足业务资源需求,并预留对应的业务资源,从而能够避免自身无法满足业务资源需求的情况下,从NSCDF中下载软件数据却无法安装,造成计算资源的浪费,提高了软件数据下载成功的可靠性;另外,由于IUSU是在配置为支持业务自主使能的情况下,预留业务资源并下载软件数据的,能够确保在软件数据下载之后,当接收到用户 发送的业务请求时,能够实现对应业务的使能。
在上述从NSCDF中下载软件数据的场景中,IUSU还可以向NSCD发送软件数据下载请求,从而下载软件数据。在一个实施例中,如图4所示,上述步骤303可以包括:
步骤401,向NSCDF发送第一业务软件数据下载请求,第一业务软件数据下载请求中包括业务标识。
其中,第一业务软件下载请求指的是IUSU请求从NSCDF下载业务软件通知对应的软件数据的信令。可以理解的是,由于接入网中包括多个IUSU,在NSCDF接收到软件下载请求时,无法确定该软件下载请求对应哪个软件的软件数据,因此,第一业务软件下载请求中可以包括业务标识,用于表征第一业务软件下载请求对应的业务,从而使得NSCDF可以根据表征的业务,确定该业务对应的软件数据。
在本实施例中,IUSU可以根据接收的业务软件下载通知中,生成携带有业务标识的第一业务软件数据下载请求。
步骤402,接收NSCDF针对第一业务软件数据下载请求发送的软件数据。
在本实施例中,IUSU可以在发送了第一业务软件数据下载请求之后,等待NSCDF对第一业务软件数据下载请求进行响应并发送的响应消息,从而从接收的响应消息中获取第一业务软件数据下载请求对应的软件数据。
本实施例中,IUSU通过向NSCDF发送包括业务标识的第一业务软件数据下载请求,使得NSCDF能够根据业务标识确定该业务软件数据下载请求对应的业务,并根据该业务确定对应软件数据,并发送给IUSU,从而IUSU能够接收NSCDF针对第一业务软件数据下载请求发送的软件数据,IUSU通过发送包括业务标识的第一业务软件数据下载请求,能够避免NSCDF发送错误的软件数据的问题,进而能够提高IUSU接收的软件数据的准确性。
需要说明的是,一个IUSU可以支持多个业务,在IUSU装载业务对应的软件之后,可以将所支持业务的业务标识进行记录,从而在接收到用户的业务请求时,能够快速确定是否支持该业务请求。在一个实施例中,上述方法还包括:在IUSU支持的业务列表中,记录业务软件数据对应的业务标识,用于表明IUSU支持业务标识对应的业务。
其中,业务列表中可以包括IUSU中装载的软件对应的业务标识,用于表征IUSU能够为用户提供服务的业务。可选的,业务标识可以包括一个业务标识,或者,也可以包括多个业务标识。
在本实施例中,可以在IUSU中装载软件数据对应的软件,且该软件能够成功运行的情况下,将该软件对应的业务标识添加至业务列表中。
本实施例中,IUSU通过在IUSU支持的业务列表中,记录业务软件数据对应的业务标识,由于该业务列表能够表明IUSU支持业务标识对应的业务,使得IUSU在接收到用户的业务请求的情况下,能够通过判断业务列表中是否存在该业务请求对应的业务标识,快速地确定是否支持该业务请求,从而提高对业务请求的响应效率。
可以理解的是,NSCDF中可以为IUSU提供所需网络和服务的存储功能。在一个实施例中,上述方法还包括:向NSCDF发送业务启动成功通知,业务启动成功通知中包括业务标识,业务启动成功通知用于通知NSCDF记录IUSU支持业务标识对应的业务。
其中,业务启动成功通知指的是在IUSU装载了软件数据对应的软件,且该软件能够成功运行的情况下,IUSU生成的通知信息,用于表明IUSU支持该软件,且可以向用户提供该软件的服务,并指示NSCDF记录该软件对应的业务。
在本实施例中,IUSU可以在装载了软件数据对应的软件,且该软件能够成功运行的情况下,生成包括业务标识业务的启动成功通知,并向NSCDF发送该业务启动成功通知。
本实施例中,IUSU通过向NSCDF发送包括业务标识的业务启动成功通知,能够指示NSCDF记录IUSU支持业务标识对应的业务,从而提高保存IUSU支持业务标识的业务的有效性,进而在在接收到用户的业务请求时,能够从NSCDF中获取IUSU所支持的业务,并快速确定IUSU是否支持该业务请求。
下面以NSCDF为执行主体,对业务使能方法的交互过程进行介绍。在一个实施例中,以该方法应用于图1中的NSCDF200为例进行说明,该方法包括:向IUSU发送业务软件下载通知,业务软件下载通知用于通知IUSU从NSCDF中下载业务下载通知对应业务的软件数据。
其中,业务软件下载通知是NSCDF用于通知IUSU下载对应软件数据的信令。在本实施例中, NSCDF可以通过接入网网络向IUSU发送业务软件下载通知,以使得IUSU能够根据业务软件下载通知向NSCDF发送软件下载请求,从而从NSCDF中下载业务下载通知对应业务的软件数据。
作为一种可能的实施方式,NSCDF中可以保存包括多个IUSU的列表,在一些实施例中,NSCDF可以向不同的IUSU发送不同的业务软件下载通知,或者,NSCDF可以同时向多个IUSU发送相同的业务软件下载通知。
本实施例中,NSCDF通过向IUSU发送用于通知IUSU从NSCDF中下载业务下载通知对应业务的软件数据的业务软件下载通知,能够使得IUSU根据业务软件下载通知下载对应的软件数据,从而通过装载软件数据对应的软件,能够向用户提供该软件对应的服务,从而实现业务使能。
可以理解的是,NSCDF向IUSU发送的业务软件下载通知之前,需要先接收来自SMG发送的业务发布通知,从而根据业务发布通知生成业务软件下载通知。在一个实施例中,如图5所示,上述方法还包括:
步骤501,接收业务管理网关SMG发送的业务发布通知。
其中,SMG是负责审批业务软件服务提供商提交的业务的软件数据,并在软件数据审批通过的情况下,为其分配业务标识,并通过消息发布模式通知NSCDF。其中,业务发布通知中可以包括业务名称、业务描述、业务类型、业务标识、业务资源需求,业务资源需求在可以包括该业务对应的带宽、存储资源和计算资源等信息。可选的,业务发布通知中可以包括一个业务对应的信息,或者,业务发布通知中也可以包括多个业务对应的信息。
作为一种可能的实施方式,可以预先建立NSCDF与SMG之间的映射关系,在SMG对软件数据审批通过之后,能够将包括该软件数据对应业务的业务标识的通知信息发送给建立了映射关系的NSCDF。
在本实施例中,NSCDF可以通过接入网网络接收SMG发送的业务发布通知。可以理解的是,NSCDF可以通过对业务发布通知进行解析,得到业务发布通知对应业务的相关信息,例如业务标识、业务资源需求。
步骤502,根据业务发布通知,从SMG中下载软件数据。
其中,软件数据中包括该业务发布通知对应业务的软件包、软件包的安装说明等数据。在本实施例中,NSCDF可以对接收的业务发布通知进行解析,从解析结果中获取软件数据的标识,从而根据标识从SMG中下载该表示对应的软件数据。
本实施例中,NSCDF通过SMG发送的业务发布通知,能够根据业务发布通知,从SMG中下载软件数据,由于业务发布通知是用于发布审批通过的软件数据,NSCDF在接收到业务发布通之后,就能够确定存在审批通过的软件数据,从而可以从SMG中下载该软件数据,进而使得NSCDF根据接收到的业务发布通知快速地从SMG下载软件数据,提高NSCDF从SMG下载软件数据的效率。
在上述根据业务发布通知,从SMG中下载软件数据的场景中,NSCDF可以在确定自身的存储空间满足软件数据的存储空间需求的情况下,从SMG下载软件数据。在一个实施例中,如图6所示,上述步骤502可以包括:
步骤601,确定NSCDF是否满足业务发布通知中包括的软件数据的存储空间需求。
其中,存储空间需求指的是软件数据需要占用的内存大小,需要占用的内存越大,存储空间需求越大,需要占用的内存越小,存储空间需求越小。
需要说明的是,NSCDF只需要下载软件数据,不需要装载软件数据对应的软件,即NSCDF只需要满足软件数据的存储空间就可以从SMG中下载软件数据,因此,NSCDF从SMG中下载软件数据的时候,可以先确定自身的存储空间否满足软件数据的存储空间需求。
在本实施例中,NSCDF可以对接收到的业务发布通知进行解析,根据解析结果确定该业务发布通知中包括的软件数据的存储空间需求,从而将自身的存储空间大小与存储空间需求进行比较,根据比较结果确定是否满足业务发布通知中包括的软件数据的存储空间需求。
步骤602,当NSCDF满足存储空间需求时,向SMG发送第二业务软件数据下载请求;第二业务软件数据下载请求中包括业务标识。
其中,第二软件数据下载请求指的是NSCDF请求从SMG下载业务发布通知中包括的软件数据的信令。可以理解的是,SMG发布的业务发布通知中可能包含多个业务对应的软件数据,当SMG接收到软件下载请求时,无法确定该软件下载请求对应哪个软件,因此,第二业务软件数据下载请求中可以 包括业务标识,用于表征第二业务软件下载请求对应的业务,从而使得SMG可以根据表征的业务,确定该业务对应的软件数据。
在本实施例中,NSCDF可以在NSCDF满足存储空间需求的情况下,生成包括该存储空间需求对应的业务标识的第二业务软件数据下载请求,并向SMG发送第二业务软件数据下载请求。
步骤603,接收SMG根据第二业务软件数据下载请求发送的软件数据,并存储软件数据。
在本实施例中,由于NSCDF已将向SMG发送了第二业务软件数据下载请求,在SMG对该第二业务软件数据下载请求进行响应之后,会将第二业务软件数据下载请求中包括的业务标识对应的软件数据发送给NSCDF,从而,NSCDF能够接收到SMG根据第二业务软件数据下载请求发送的软件数据,并存储软件数据,以向IUSU发送业务下载通知,并向IUSU发送该软件数据。
本实施例中,NSCDF通过确定自身是否满足业务发布通知中包括的软件数据的存储空间需求,并在NSCDF满足存储空间需求的情况下,向SMG发送包括业务标识第二业务软件数据下载请求,然后接收SMG根据第二业务软件数据下载请求发送的软件数据,并存储软件数据,能够避免在NSCDF存储空间不足的情况下,从SMG中下载软件数据,导致下载失败且浪费计算资源的问题,从而提高NSCDF从SMG中下载软件数据的可靠性。
下面以执行主体为NSCDF,对NSCDF向IUSU发送软件数据的过程进行介绍。在一个实施例中,上述方法用于NSCDF,如图7所示,上述方法还包括:
步骤701,接收IUSU发送的第一业务软件数据下载请求。
可以理解的是,IUSU在接收到业务软件下载通知时,若自身的业务起源满足业务资源需求,可以生成携带有业务标识的第一业务软件数据下载请求。
在本实施例中,NSCDF可以通过接入网接收IUSU发送的第一业务软件数据下载请求。
步骤702,根据第一业务软件数据下载请求中包括的业务标识,向IUSU发送软件数据。
可以理解的是,NSCDF可以业务标识确定业务,从而确定业务对应的软件数据。在本实施例中,NSCDF可以第一业务软件数据下载请求中包括的业务标识确定该第一业务软件数据下载请求对应的业务,从而能够根据该业务确定对应的软件数据并发送给IUSU。
本实施例中,NSCDF通过接收IUSU发送的第一业务软件数据下载请求,由于第一业务软件数据下载请求中包括业务标识,使得NSCDF能够根据业务标识确定第一业务软件数据下载请求对应的业务,从而能够准确的确定业务对应的软件数据,并向IUSU发送软件数据,提高了发送的软件数据的准确性。
可以理解的是,NSCDF中可以为IUSU提供所需网络和服务的存储功能。在一个实施例中,如图8所示,上述方法还包括:
步骤801,接收IUSU发送的业务启动成功通知。
在本实施例中,NSCDF可以在IUSU装载了软件数据对应的软件,且该软件能够成功运行的情况下,生成包括业务标识业务的启动成功通知,并向NSCDF发送该业务启动成功通知,然后接收到IUSU发送的业务启动成功通知。
步骤802,记录IUSU支持业务启动成功通知中包括的业务标识对应的业务。
在本实施例中,NSCDF在接收到业务启动成功通知之后,可以对该业务启动成功通知进行解析,然后根据解析结果确定该业务启动成功通知包括的业务标识,从而将业务标识对应的业务进行记录。
本实施例中,NSCDF通过接收IUSU发送的业务启动成功通知,能够记录IUSU支持业务启动成功通知中包括的业务标识对应的业务,从而能够提高保存IUSU所支持的业务的有效性,进而在接收到用户的业务请求时,能够从NSCDF中获取IUSU所支持的业务,并快速确定IUSU是否支持该业务请求。
下面以SMG为执行主体,对业务使能方法的交互过程进行介绍。在一个实施例中,上述方法用于SMG,上述方法还包括:向NSCDF发送业务发布通知,业务发布通知用于通知NSCDF从SMG中下载业务发布通知对应业务的软件数据。
可以理解的是,为了保证IUSU能够根据下载的软件数据成功地装载软件数据对应的软件,SMG在接收软件提供商提交的软件数据之后,需要对软件数据进行审批,若软件数据与IUSU相匹配,则审批通过,若软件数据与IUSU不匹配,则审批未通过。其中,对软件数据进行审批可以包括对软件数据中的软件包的编写代码、数据格式进行审批。
在本实施例中,SMG可以在对接收的软件提供商提交的软件数据审批通过的情况下,生成业务发 布通知,并向NSCDF发送业务发布通知,从而使得NSCDF能够从SMG中下载业务发布通知对应业务的软件数据。
本实施例中,SMG通过向NSCDF发送业务发布通知,由于业务发布通知用于通知NSCDF从SMG中下载业务发布通知对应业务的软件数据,能够使得NSCDF通过业务发布通知,快速地确定SMG中包括审批通过的软件数据,从而从SMG中下载该审批通过的软件数据,提高了NSCDF从SMG中下载软件上数据的效率。
在上述SMG向NSCDF发送业务发布通知的场景中,SMG可以在接收到NSCDF发送的第二业务软件数据下载请求的情况下,向NSCDF发哦是那个软件数据。在一个实施例中,如图9所示,上述方法还包括:
步骤901,接收NSCDF发送的第二业务软件数据下载请求。
在本实施例中,SMG向NSCDF发送业务发布通知之后,NSCDF可以根据业务发布通知中确定自身的存储空间是否满足软件数据的存储空间需求,并在满足的情况,生成第二业务软件数据下载请求,并发送给SMG,从而SMG能够接收NSCDF发送的第二软件数据下载请求。
步骤902,根据第二业务软件数据下载请求携带的业务标识,向NSCDF发送软件数据。
可以理解的是,由于SMG中可能包括多个审批通过的软件数据,当SMG接收到软件数据下载请求时,无法确定对应的软件数据,因此,可以根据业务标识确定业务,然后根据业务确定对应的软件数据。
在本实施例中,SMG可以对第二业务软件数据下载请求进行解析,根据解析结果确定业务标识,接着,根据业务标识确定对应的业务,而后,将该业务对应的软件数据确定为第二业务软件数据下载请求对应的软件数据,并发送给NSCDF。
本实施例中,SMG通过接收NSCDF发送的第二业务软件数据下载请求,能够根据第二业务软件数据下载请求携带的业务标识,向NSCDF发送软件数据,由于SMG根据业务标识能够快速准确度地确定与业务标识对应的业务,从而能够将与该业务对应的软件数据确定为第二业务软件数据下载请求对应的软件数据,进而能够将确定的软件数据发送给NSCDF,提高了发送给NSCDF的软件数据的效率和准确性。
在一个实施例中,图10提供一种业务使能方法的信令交互流程图。如图10所示,该方法包括如下步骤:
S1,SMG在接收的软件数据审批通过的情况下,生成并发送向NSCDF业务发布通知。
S2,NSCDF确定自身是否满足业务发布通知中包括的软件数据的存储空间需求,并在满足存储空间需求的情况下,NSCDF向SMG发送第二业务软件数据下载请求。
S3,SMG根据第二业务软件数据下载请求携带的业务标识,向NSCDF发送软件数据。
S4,NSCDF向IUSU发送业务软件下载通知。
S5,IUSU确定自身是否满足业务下载通知中包括的业务资源需求,并在满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源,向NSCDF发送第一业务软件数据下载请求。
S6,NSCDF根据第一业务软件数据下载请求中包括的业务标识,向IUSU发送软件数据。
S7,IUSU装载软件数据对应的软件,并使能软件对应的业务。
S8,IUSU在IUSU支持的业务列表中,记录业务软件数据对应的业务标识。
S9,向NSCDF发送业务启动成功通知。
S10,NSCDF记录IUSU支持业务标识对应的业务。
图11为本申请实施例提供的一种业务处理方法的应用场景示意图。如图11所示,该场景中包括NSCDF200、第一IUSU400、第二IUSU500、终端600。其中,第一IUSU400通过网络分别与NSCDF200、第二IUSU500、终端600进行数据传输,终端600还通过网络与第二IUSU500进行数据传输。其中,终端600可以向第一IUSU400发送业务请求,第一IUSU可以向NSCDF200发送业务能力查询请求,并根据NSCDF200返回的业务能力查询响应生成失败响应,并向终端600发送失败响应,终端600在接收到失败响应的情况下,可以根据失败响应选择一个第二IUSU500,并向第二IUSU500发起用户注册请求。
在一个实施例中,如图12所示,提供了一种业务处理方法,以该方法应用于图12中的第一IUSU400 为例进行说明,第一IUSU可以在利用上述业务使能方法进行业务使能的情况下,进行业务处理。该业务处理方法包括以下步骤:
步骤1201,接收终端发送的业务请求。
其中,第一IUSU指的是私人IUSU,是由用户创建和管理的网元,第一IUSU只能向已注册的用户,且存在业务请求对应的软件的情况下,为用户提供服务。业务请求是终端根据用户的软件使用请求生成的请求,用于向第一IUSU申请对应业务的服务。
在本实施例中,第一IUSU可以接收终端发送的业务请求。可选的,业务请求可以为一个,或者,业务请求也可以为多个。可选的,第一IUSU接收的业务请求可能是可以响应的,或者,第一IUSU接收的业务请求可能是无法响应的。
步骤1202,在不支持业务请求对应的业务的情况下,向终端返回失败响应,失败响应用于指示终端注册至支持业务的第二IUSU。
其中,第二IUSU指的是公共IUSU,是由运营商创建和管理的网元,第二IUSU可以向所有用户提供服务。需要说明的是,不同业务请求可能会对应不同的软件,若第一IUSU中包括该业务请求对应的软件,则响应该业务请求,若第一IUSU中不包括该业务请求对应的软件,则不响应该业务请求。
在本实施例中,若第一IUSU中不存在该业务请求对应的软件,则可以确定第一IUSU不支持该业务请求对应的业务,在该情况下,第一IUSU可以向终端返回失败响应,且失败响应中可以包括支持业务请求对应的业务的第二IUSU,从而指示终端注册至第二IUSU,进而能够使得终端在注册制第二IUSU之后,向第二IUSU发起业务请求,实现对终端的业务请求的响应。
可以理解的是,由于第一IUSU无法响应该业务请求,则说明第一IUSU不支持该用户,因此,该用户对应的终端可以向公共的IUSU进行注册以申请服务,例如,向支持该也业务请求对应业务的第二IUSU发起业务注册。
上述业务处理方法中,第一IUSU通过接收终端发送的业务请求,能够在不支持业务请求对应的业务的情况下,向终端返回失败响应,由于失败响应可以指示终端注册至支持业务的第二IUSU,从而能够在第一IUSU无法响应业务请求的情况下,指示终端向第二IUSU进行注册,避免终端发起的业务请求无法响应的问题,进而能够提高为用户提供服务的可靠性。
在上述第一IUSU接收终端发送的业务请求的场景中,第一IUSU可以根据业务请求的业务标识自身确定是否支该持业务请求。在一个实施例中,如图13所示,上述方法还包括:
步骤1301,根据业务请求中包括的业务标识和第一IUSU支持的业务列表,确定是否支持业务。
其中,业务标识用于表征业务请求对应的业务信息,不同业务标识对应不同的业务请求,第一IUSU根据
在本实施例中,第一IUSU可以对业务请求进行解析,根据解析结果确定该业务请求对应的业务标识,然后从第一IUSU支持的业务列表中查询是否存在该第一IUSU,根据查询结果确定第一IUSU是否支持该业务请求对应的业务。
步骤1302,当业务标识未在业务列表中时,确定不支持业务。
可以理解的是,若业务列表存在业务标识,则说明第一IUSU中包括该业务标识对应业务的软件,那么第一IUSU可以提供该业务的服务;若业务列表中不存在业务标识,则说明第一IUSU中不包括该业务标识对应业务的软件,那么第一IUSU无法提供该业务对应的服务。
在本实施例中,若第一IUSU确定业务标识未在业务列表中,则说明第一IUSU中不包括该业务标识对应业务的软件,即第一IUSU无法向终端提供该业务对应的服务,就可以确定第一IUSU不支持该业务。
本实施例中,第一IUSU通过根据业务请求中包括的业务标识和第一IUSU支持的业务列表,能够快速确定业务列表中是否存在业务标识,从而能够快速地确定第一IUSU是否支持业务,进而能够在业务标识未在业务列表中的情况下,快速地确定第一IUSU不支持业务,提高了第一IUSU对业务请求的响应速度。
在上述向终端返回失败响应的场景中,第一IUSU可以通过NSCDF发送的业务能力查询响应生成失败响应。在一个实施例中,如图14所示,上述步骤1202可以包括:
步骤1401,根据NSCDF发送的业务能力查询响应,生成失败响应,失败响应中包括业务支持IUSU列表。
其中,业务能力查询响应指的是NSCDF在接收到第一IUSU发送的业务能力查询的信息之后,对该信息做出的响应消息。可以理解的是,NSCDF作能够对第一IUSU中已装载且成功运行的软件对应的业务进行记录,因此,在接收到第一IUSU发送的业务能力查询的信息之后,可以结合记录的信息,确定业务能力查询信息中包括的公共IUSU支持什么业务,从而生成业务支持IUSU列表。其中,业务支持IUSU列表中包括支持该业务请求的公共IUSU的标识。
在本实施例中,第一IUSU可以在无法支持业务请求对应的业务的情况下,将包括有自身预配置的公共IUSU列表的查询信息发送给NSCDF,从而能够接收NSCDF根据查询信息和预先存储的记录生成的业务能力查询响应,进而通过对业务能力查询响应进行解析,能够得到业务支持IUSU列表,并根据支持业务请求对应业务的IUSU生成失败响应。
在一些实施例中,业务支持IUSU列表中包括公共IUSU列表中支持业务的一个或多个第二IUSU的标识。
其中,第二IUSU为第一IUSU中预配置的能够向所有用户提供服务的公共IUSU,在公共IUSU列表中可以包括一个或多个第二IUSU的标识。需要说明的是,对于不同的业务请求,部分第二IUSU支持业务请求对应的业务,部分第二IUSU不支持业务请求对应的业务,因此,针对某个业务请求,需要从公共IUSU列表中确定支持该业务请求对应业务的第二IUSU,并根据所有支持该业务请求对应业务的第二IUSU生成业务支持IUSU列表。可选的,业务支持IUSU列表可以包括一个支持该业务请求的第二IUSU的标识,或者,也可以包括多个支持该业务请求的第二IUSU的标识。
步骤1402,向终端发送失败响应。
在本实施例中,第一IUSU可以将生成的失败响应通过网络发送给终端。
本实施例中,第一IUSU通过根据NSCDF发送的业务能力查询响应中的业务支持IUSU列表生成失败响应,使得失败响应中能够包括支持业务请求的公共IUSU的标识,从而向终端发送失败响应,使得终端能够根据失败响应,确定可以支持业务请求的公共IUSU,然后能够向该公共IUSU重新发起注册并发送业务请求,进而能够得到公共IUSU提供的服务。
在上述根据NSCDF发送的业务能力查询响应,生成失败响应的场景中,第一IUSU可以通过向NSCDF发送业务能力查询请求,接收NSCDF返回的业务能力查询响应。在一个实施例中,如图15所示,上述方法还包括:
步骤1501,向NSCDF发送业务能力查询请求;业务能力查询请求中包括第一IUSU配置的公共IUSU列表。
其中,业务能力查询请求是第一IUSU用于向NSCDF获取自身配置的用于向所有用户提供服务的公共IUSU信息的请求。需要说明的是,对于不同的第一IUSU,可以配置不同的公共IUSU,当第一IUSU无法为业务请求对应的业务提供支持时,可以指示终端向自身所配置的公共IUSU发起注册并重新发送业务请求。其中,公共IUSU列表为第一IUSU中预先配置的公共IUSU的列表。
在本实施例中,第一IUSU可以根据自身预配置的公共IUSU列表生成业务能管理查询请求,并向NSCDF发送业务能力查询请求。
步骤1502,接收NSCDF针对业务能力查询请求发送的业务能力查询响应;业务能力查询响应中包括业务支持IUSU列表。
在本实施例中,第一IUSU能够通过网络接收NSCDF根据业务能力查询请求生成的业务能力查询响应,然后通过该业务能力查询响应中的业务支持IUSU列表,第一IUSU能够确定支持某个业务请求的公共IUSU。
本实施例中,第一IUSU通过向NSCDF发送包括第一IUSU配置的公共IUSU列表业务能力查询请求,能够到接收NSCDF针对业务能力查询请求发送的业务能力查询响应,从而根据业务能力查询响应中包括的业务支持IUSU列表,能够确定支持业务请求对应业务的公共IUSU,进而能够在无法支持业务请求的情况下,向终端返回包括业务支持IUSU列表的失败响应,以指示终端向业务支持IUSU列表中的IUSU重新发起注册并发送业务请求,提高了为用户提供服务的可靠性。
下面以NSCDF为执行主体,对业务处理方法的交互过程进行介绍。在一个实施例中,上述方法用于NSCDF,如图16所示,上述方法还包括:
步骤1601,接收第一IUSU发送的业务能力查询请求。
其中,业务能力查询请求是第一IUSU在无法支持终端发送的业务请求对应的业务的情况下,生成 并发送的。业务能力查询请求中可以包括第一IUSU中预先配置的公共IUSU列表。
在本实施例中,NSCDF可以通过网络接收第一IUSU发送的业务能力查询请求。
步骤1602,向第一IUSU返回业务能力查询响应,业务能力查询响应中包含一个或多个支持业务能力查询请求对应业务的第二IUSU的标识。
其中,业务能力查询响应是NSCDF根据业务能力查询请求,对业务能力查询请求中的公共IUSU列表中的公共IUSU是否支持业务能力查询请求对应的业务请求之后生成的,若公共IUSU列表中的公共IUSU支持业务能力查询请求对应的业务请求,则将该公共IUSU确定为第二IUSU,并根据所有第二IUSU生成业务能力查询响应,并向第一IUSU返回业务能力查询响应。
本实施例中,NSCDF通过接收第一IUSU发送的业务能力查询请求,能够根据业务能力查询请求中的公共IUSU列表确定支持业务能力查询请求对应的业务请求的第二IUSU,从而能够根据第二IUSU生成业务能力查询响应,并向第一IUSU返回业务能力查询响应,进而能够使得第一IUSU根据业务能力查询响应生成失败响应,确保终端能够根据失败响应重新确定能够支持业务请求的第二IUSU,提高为终端发送的业务请求提供服务的可靠性。
下面以终端为执行主体,对业务处理方法的交互过程进行介绍。在一个实施例中,上述方法用于终端,如图17所示,上述方法还包括:
步骤1701,向第一IUSU发送业务请求。
其中,业务请求指的是用户针对某个软件的使用请求。在本实施例中,终端在接收到用户发起软件使用请求时,可以根据软件使用请求生成业务请求,并通过网络将生成的业务请求发送给第一IUSU。
可以理解的是,第一IUSU可以为业务请求对应用户预先注册过的IUSU。
步骤1702,当接收到第一IUSU返回的失败响应时,根据失败响应,选择一个第二IUSU,并向第二IUSU发起用户注册请求。
需要说明的是,若第一IUSU中不存在业务请求对应的软件,则无法向用户提供该软件对应的服务,那么就会生成失败响应,且在失败响应中,可以包括能够向用户提供该软件对应的服务的公共IUSU,即第二IUSU。
在本实施例中,若第一IUSU无法支持终端发送的业务请求对应的业务时,终端就会收到第一IUSU返回的失败响应,通过对失败响应进行解析,能够得到支持业务请求对应业务的第二IUSU,从而可以从解析结果中确定一个第二IUSU,并向第二IUSU发起用户注册请求。
可以理解的是,失败响应中可能包括多个第二IUSU,终端可以从中选在任一个第二IUSU,并向该选择的第二IUSU发起用户注册请求。
本实施例中,终端通过向第一IUSU发送业务请求,能够在接收到第一IUSU返回的失败响应的情况下,根据失败响应中包括的多个第二IUSU,选择一个第二IUSU,并向第二IUSU发起用户注册请求,从而能够在注册请求成功的情况下,向该第二IUSU发送业务请求,由于该第二IUSU为支持该业务请求对应业务的IUSU,当终端向该第二IUSU发送业务请求之后,第二IUSU能够支持该业务请求对应的业务,从而能够响应该业务请求,提高了为用户提供服务的可靠性。
在一个实施例中,图18提供一种业务处理方法的信令交互流程图。如图18所示,该方法包括如下步骤。
S1,第一IUSU接收终端发送的业务请求。
S2,在不支持业务请求对应的业务的情况下,根据第一IUSU业务请求中包括的业务标识和第一IUSU支持的业务列表,确定是否支持业务,若业务标识未在业务列表中,则第一IUSU确定不支持业务。
S3,第一IUSU向NSCDF发送业务能力查询请求。
S4,NSCDF向第一IUSU返回业务能力查询响应。
S5,第一IUSU根据NSCDF发送的业务能力查询响应,生成失败响应,并向终端发送失败响应。
S6,终端根据失败响应,选择一个第二IUSU,并向第二IUSU发起用户注册请求。
应该理解的是,虽然上述流程图中的各个步骤按照箭头的指示依次显示,但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明,这些步骤的执行并没有严格的顺序限制,这些步骤可以以其它的顺序执行。而且,上述流程图中的至少一部分步骤可以包括多个步骤或者多个阶段,这些步骤或者阶段并不必然是在同一时刻执行完成,而是可以在不同的时刻执行,这些步骤或者阶 段的执行顺序也不必然是依次进行,而是可以与其它步骤或者其它步骤中的步骤或者阶段的至少一部分轮流或者交替地执行。
在一个实施例中,如图19所示,提供了一种业务使能装置,包括:第一接收模块1901、下载模块1902和启动模块1903,其中:
第一接收模块1901用于接收网络和业务能力存储功能NSCDF发送的业务软件下载通知。
下载模块1902用于根据业务下载通知,从NSCDF中下载业务下载通知对应业务的软件数据。
启动模块1903用于装载并启动软件数据对应的软件。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述下载模块1901包括:确定单元、处理单元和第一下载单元,其中:
确定单元用于确定IUSU是否满足业务下载通知中包括的业务资源需求。
处理单元用于在IUSU满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源。
第一下载单元用于从NSCDF下载软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述下载单元具体用于:向NSCDF发送第一业务软件数据下载请求,第一业务软件数据下载请求中包括业务标识;接收NSCDF针对第一业务软件数据下载请求发送的软件数据
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置还包括第一记录模块,其中:
第一记录模块用于在IUSU支持的业务列表中,记录业务软件数据对应的业务标识,用于表明IUSU支持业务标识对应的业务。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置还包括第一发送模块,其中:
第一发送模块用于向NSCDF发送业务启动成功通知,业务启动成功通知中包括业务标识,业务启动成功通知用于通知NSCDF记录IUSU支持业务标识对应的业务。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,如图20所示,提供了一种业务使能装置包括:第二发送模块2001,其中:
第二发送模块2001用于向IUSU发送业务软件下载通知,业务软件下载通知用于通知IUSU从NSCDF中下载业务下载通知对应业务的软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述第二发送模块2001包括:接收单元和第二下载单元,其中:
接收单元用于接收业务管理网关SMG发送的业务发布通知。
第二下载单元用于根据业务发布通知,从SMG中下载软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述第二下载单元具体用于:确定NSCDF是否满足业务发布通知中包括的软件数据的存储空间需求;若NSCDF满足存储空间需求,则向SMG发送第二业务软件数据下载请求;第二业务软件数据下载请求中包括业务标识;接收SMG根据第二业务软件数据下载请求发送的软件数据,并存储软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置还包括第一接收模块和第三发送模块,其中:
第一接收模块用于接收IUSU发送的第一业务软件数据下载请求。
第三发送模块用于根据第一业务软件数据下载请求中包括的业务标识,向IUSU发送软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
一个实施例中,上述装置还包括:第二接收模块和第二记录模块,其中:
第二接收模块用于接收IUSU发送的业务启动成功通知。
第二记录模块用于记录IUSU支持业务启动成功通知中包括的业务标识对应的业务。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,如图21所示,提供了一种业务使能装置,包括:第四发送模块2101,其中:
第四发送模块2101用于向NSCDF发送业务发布通知,业务发布通知用于通知NSCDF根据业务发布通知从SMG中下载业务发布通知对应业务的软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置还包括:第三接收模块和第五发送模块,其中:
第三接收模块用于接收NSCDF发送的第二业务软件数据下载请求。
第五发送模块用于根据第二业务软件数据下载请求携带的业务标识,向NSCDF发送软件数据。
本实施例提供的业务使能装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
关于业务使能装置的具体限定可以参见上文中对于业务使能方法的限定,在此不再赘述。上述业务使能装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中,也可以以软件形式存储于计算机设备中的存储器中,以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中,如图22所示,提供了一种业务处理装置,包括:第四接收模块2201和第六发送模块2202,其中:
第四接收模块2201用于接收终端发送的业务请求;
第六发送模块2202用于在不支持业务请求对应的业务的情况下,向终端返回失败响应,失败响应用于指示终端注册至支持业务的第二IUSU。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置包括:第一确定模块和第二确定模块,其中:
第一确定模块用于根据业务请求中包括的业务标识和第一IUSU支持的业务列表,确定是否支持业务;
第二确定模块用于若业务标识未在业务列表中,则确定不支持业务。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述第六发送模块2202,包括:生成单元和发送单元,其中:
生成单元用于根据NSCDF发送的业务能力查询响应,生成失败响应,失败响应中包括业务支持IUSU列表;可选的,业务支持IUSU列表中包括公共IUSU列表中支持业务的一个或多个第二IUSU的标识。
发送单元用于向终端发送失败响应。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,上述装置还包括:第七发送模块和第五接收模块,其中:
第七发送模块用于向NSCDF发送业务能力查询请求;业务能力查询请求中包括第一IUSU配置的公共IUSU列表。
第五接收模块用于接收NSCDF针对业务能力查询请求发送的业务能力查询响应;业务能力查询响应中包括业务支持IUSU列表。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,如图23所示,提供了一种业务处理装置,包括:第六接收模块2301和第八发送模块2302,其中:
第六接收模块2301用于接收第一IUSU发送的业务能力查询请求,业务能力查询请求为第一IUSU在不支持终端发送的业务请求对应的业务的情况下发送的。
第八发送模块2302用于向第一IUSU返回业务能力查询响应,业务能力查询响应用于指示至少一个支持业务的第二IUSU。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
在一个实施例中,如图24所示,提供了一种业务处理装置,包括:第九发送模块2401和第十发送模块2402,其中:
第九发送模块2401用于向第一IUSU发送业务请求。
第十发送模块2402用于若接收到第一IUSU返回的失败响应,则根据失败响应,向失败响应中包括的至少一个支持业务请求对应的业务的第二IUSU发起用户注册请求。
本实施例提供的业务处理装置,可以执行上述方法实施例,其实现原理和技术效果类似,在此不再赘述。
关于业务处理装置的具体限定可以参见上文中对于业务处理方法的限定,在此不再赘述。上述业务处理装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中,也可以以软件形式存储于计算机设备中的存储器中,以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中,如图25所示,提供了一种通信设备,图25为本申请实施例提供的接入网设备的结构示意图。该接入网设备可以包括接收器251、存储器252、处理器253、至少一个通信总线254和发送器255。通信总线254用于实现元件之间的通信连接。存储器252可能包含高速RAM存储器,也可能还包括非易失性存储NVM,例如至少一个磁盘存储器,存储器252中可以存储各种程序,用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中,发送器255可以为接入网设备中的射频处理模块或者基带处理模块,接收器251也可以为接入网设备中的射频处理模块或者基带处理模块,该发送器255和接收器251可以集成在一起实现成为收发器,该发送器255和接收器251均可以耦合至所述处理器253,其可以在处理器253的指示或者控制作用下实现收或者发的动作。
本实施例中,接收器用于接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;处理器用于从NSCDF中下载业务下载通知对应业务的软件数据;处理器还用于发送器,用于装载软件数据对应的软件,并使能软件对应的业务。
在一个实施例中,处理器用于确定IUSU是否满足业务下载通知中包括的业务资源需求;在IUSU满足业务资源需求,且配置为支持业务自主使能的情况下,预留业务资源需求对应的业务资源;从NSCDF下载软件数据。
在一个实施例中,发送器用于向NSCDF发送第一业务软件数据下载请求,第一业务软件数据下载请求中包括业务标识;接收器用于接收NSCDF针对第一业务软件数据下载请求发送的软件数据。
在一个实施例中,处理器用于在IUSU支持的业务列表中,记录业务软件数据对应的业务标识,用于表明IUSU支持业务标识对应的业务。
在一个实施例中,发送器用于向NSCDF发送业务启动成功通知,业务启动成功通知中包括业务标识,业务启动成功通知用于通知NSCDF记录IUSU支持业务标识对应的业务。
在一个实施例中,如图26所示,提供了一种通信设备,图26为本申请实施例提供的接入网设备的结构示意图。该接入网设备可以包括接收器261、存储器262、处理器263、至少一个通信总线264和发送器265。通信总线264用于实现元件之间的通信连接。存储器262可能包含高速RAM存储器,也可能还包括非易失性存储NVM,例如至少一个磁盘存储器,存储器262中可以存储各种程序,用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中,发送器265可以为接入网设备中的射频处理模块或者基带处理模块,接收器261也可以为接入网设备中的射频处理模块或者基带处理模块,该发 送器265和接收器261可以集成在一起实现成为收发器,该发送器265和接收器261均可以耦合至所述处理器263,其可以在处理器263的指示或者控制作用下实现收或者发的动作。
本实施例中,发送器用于向IUSU发送业务软件下载通知,业务软件下载通知用于通知IUSU从NSCDF中下载业务下载通知对应业务的软件数据。
在一个实施例中,接收器用于接收业务管理网关SMG发送的业务发布通知;处理器用于根据业务发布通知,从SMG中下载软件数据。
在一个实施例中,处理器用于确定NSCDF是否满足业务发布通知中包括的软件数据的存储空间需求;若NSCDF满足存储空间需求,则向SMG发送第二业务软件数据下载请求;第二业务软件数据下载请求中包括业务标识;接收SMG根据第二业务软件数据下载请求发送的软件数据,并存储软件数据。
在一个实施例中,接收器用于接收IUSU发送的第一业务软件数据下载请求;发送器用于根据第一业务软件数据下载请求中包括的业务标识,向IUSU发送软件数据。
在一个实施例中,接收器用于接收IUSU发送的业务启动成功通知;处理器用于记录IUSU支持业务启动成功通知中包括的业务标识对应的业务。
在一个实施例中,如图27所示,提供了一种通信设备,图27为本申请实施例提供的接入网设备的结构示意图。该接入网设备可以包括接收器2671、存储器272、处理器273、至少一个通信总线274和发送器275。通信总线274用于实现元件之间的通信连接。存储器272可能包含高速RAM存储器,也可能还包括非易失性存储NVM,例如至少一个磁盘存储器,存储器272中可以存储各种程序,用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中,发送器275可以为接入网设备中的射频处理模块或者基带处理模块,接收器271也可以为接入网设备中的射频处理模块或者基带处理模块,该发送器275和接收器271可以集成在一起实现成为收发器,该发送器275和接收器271均可以耦合至所述处理器273,其可以在处理器273的指示或者控制作用下实现收或者发的动作。
在本实施例中,发送器用于向NSCDF发送业务发布通知,业务发布通知用于通知NSCDF从SMG中下载业务发布通知对应业务的软件数据。
在一个实施例中,接收器用于接收NSCDF发送的第二业务软件数据下载请求;发送器,用于根据第二业务软件数据下载请求携带的业务标识,向NSCDF发送软件数据。
在一个实施例中,如图28所示,提供了一种通信设备,图28为本申请实施例提供的接入网设备的结构示意图。该接入网设备可以包括接收器281、存储器282、处理器283、至少一个通信总线284和发送器285。通信总线284用于实现元件之间的通信连接。存储器282可能包含高速RAM存储器,也可能还包括非易失性存储NVM,例如至少一个磁盘存储器,存储器282中可以存储各种程序,用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中,发送器285可以为接入网设备中的射频处理模块或者基带处理模块,接收器281也可以为接入网设备中的射频处理模块或者基带处理模块,该发送器285和接收器281可以集成在一起实现成为收发器,该发送器285和接收器281均可以耦合至所述处理器283,其可以在处理器283的指示或者控制作用下实现收或者发的动作。
在本实施例中,接收器用于接收终端发送的业务请求;发送器,用于在不支持业务请求对应的业务的情况下,向终端返回失败响应,失败响应用于指示终端注册至支持业务的第二IUSU。
在一个实施例中,处理器用于根据业务请求中包括的业务标识和第一IUSU支持的业务列表,确定是否支持业务;若业务标识未在业务列表中,则确定不支持业务。
在一个实施例中,处理器用于根据NSCDF发送的业务能力查询响应,生成失败响应,失败响应中包括业务支持IUSU列表;发送器用于向终端发送失败响应。
在一个实施例中,发送器用于向NSCDF发送业务能力查询请求;业务能力查询请求中包括第一IUSU配置的公共IUSU列表;接收器,用于接收NSCDF针对业务能力查询请求发送的业务能力查询响应;业务能力查询响应中包括业务支持IUSU列表。
在一个实施例中,如图29所示,提供了一种通信设备,图29为本申请实施例提供的接入网设备的结构示意图。该接入网设备可以包括接收器291、存储器292、处理器293、至少一个通信总线294和发送器295。通信总线294用于实现元件之间的通信连接。存储器292可能包含高速RAM存储器,也可能还包括非易失性存储NVM,例如至少一个磁盘存储器,存储器292中可以存储各种程序,用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中,发送器295可以为接入网设备中的射频处理模块或者基带处理模块,接收器291也可以为接入网设备中的射频处理模块或者基带处理模块,该发 送器295和接收器291可以集成在一起实现成为收发器,该发送器295和接收器291均可以耦合至所述处理器293,其可以在处理器293的指示或者控制作用下实现收或者发的动作。
在本实施例中,接收器用于接收第一IUSU发送的业务能力查询请求;发送器用于向第一IUSU返回业务能力查询响应,业务能力查询响应中包含一个或多个支持业务能力查询请求对应业务的第二IUSU的标识。
在一个实施例中,如图30所示,提供了一种通信设备,图30是本发明实施例提供的终端设备的结构示意图。图30所示的终端设备3000包括:至少一个处理器3001、存储器3002、至少一个网络接口3004和用户接口3003。终端设备3000中的各个组件通过总线系统3005耦合在一起。可理解,总线系统3005用于实现这些组件之间的连接通信。总线系统3005除包括数据总线之外,还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见,在图1中将各种总线都标为总线系统3005。另外,本发明实施例中,还包括收发器3006,收发器可以是多个元件,即包括发送器和接收器,提供用于在传输介质上与各种其他装置通信的单元。
其中,用户接口3003可以包括显示器、键盘或者点击设备(例如,鼠标,轨迹球(trackball)、触感板或者触摸屏等。
可以理解,本发明实施例中的存储器3002可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DRRAM)。本发明实施例描述的系统和方法的存储器3002旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中,存储器3002存储了如下的元素,可执行模块或者数据结构,或者他们的子集,或者他们的扩展集:操作系统30021和应用程序30022。
其中,操作系统30021,包含各种系统程序,例如框架层、核心库层、驱动层等,用于实现各种基础业务以及处理基于硬件的任务。应用程序30022,包含各种应用程序,例如媒体播放器(Media Player)、浏览器(Browser)等,用于实现各种应用业务。实现本发明实施例方法的程序可以包含在应用程序30022中。
在本发明实施例中,通过调用存储器3002存储的程序或指令,具体的,可以是应用程序30022中存储的程序或指令,其中,发送器,用于向第一IUSU发送业务请求;处理器,用于。若接收到第一IUSU返回的失败响应,则根据失败响应,选择一个第二IUSU,并向第二IUSU发起用户注册请求。可以理解的是,本发明实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现,处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits,ASIC)、数字信号处理器(Digital Signal Processing,DSP)、数字信号处理设备(DSP Device,DSPD)、可编程逻辑设备(Programmable Logic Device,PLD)、现场可编程门阵列(Field-Programmable Gate Array,FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请功能的其它电子单元或其组合中。
对于软件实现,可通过执行本发明实施例功能的模块(例如过程、函数等)来实现本发明实施例的技术。软件代码可存储在存储器中并通过处理器3001执行。存储器可以在处理器3001中或在处理器3001外部实现。
在一个实施例中,提供了一种计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现上述各方法实施例中的步骤。
在一个实施例中,提供了一种计算机程序产品,包括计算机程序,该计算机程序被处理器执行时实现上述各方法实施例中的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,的计算机程序可存储于一非易失性计算机可读取存储介质中,该计算机程序 在执行时,可包括如上述各方法的实施例的流程。其中,本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用,均可包括非易失性和易失性存储器中的至少一种。非易失性存储器可包括只读存储器(Read-Only Memory,ROM)、磁带、软盘、闪存或光存储器等。易失性存储器可包括随机存取存储器(Random Access Memory,RAM)或外部高速缓冲存储器。作为说明而非局限,RAM可以是多种形式,比如静态随机存取存储器(Static Random Access Memory,SRAM)或动态随机存取存储器(Dynamic Random Access Memory,DRAM)等。
以上实施例的各技术特征可以进行任意的组合,为使描述简洁,未对上述实施例中的各个技术特征所有可能的组合都进行描述,然而,只要这些技术特征的组合不存在矛盾,都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式,其描述较为具体和详细,但并不能因此而理解为对发明专利范围的限制。应当指出的是,对于本领域的普通技术人员来说,在不脱离本申请构思的前提下,还可以做出若干变形和改进,这些都属于本申请的保护范围。因此,本申请专利的保护范围应以所附权利要求为准。

Claims (34)

  1. 一种业务使能方法,用于综合用户服务单元IUSU,所述方法包括:
    接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;
    从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
    装载所述软件数据对应的软件,并使能所述软件对应的业务。
  2. 根据权利要求1所述的方法,其中,所述从所述NSCDF中下载所述业务下载通知对应业务的软件数据,包括:
    确定所述IUSU是否满足所述业务下载通知中包括的业务资源需求;
    在所述IUSU满足所述业务资源需求,且配置为支持业务自主使能的情况下,预留所述业务资源需求对应的业务资源;
    从所述NSCDF下载所述软件数据。
  3. 根据权利要求2所述的方法,其中,所述从所述NSCDF中下载所述软件数据,包括:
    向所述NSCDF发送第一业务软件数据下载请求,所述第一业务软件数据下载请求中包括所述业务标识;
    接收所述NSCDF针对所述第一业务软件数据下载请求发送的所述软件数据。
  4. 根据权利要求3所述的方法,还包括:
    在所述IUSU支持的业务列表中,记录所述业务软件数据对应的业务标识,用于表明所述IUSU支持所述业务标识对应的业务。
  5. 根据权利要求4所述的方法,还包括:
    向所述NSCDF发送业务启动成功通知,所述业务启动成功通知中包括所述业务标识,所述业务启动成功通知用于通知所述NSCDF记录所述IUSU支持所述业务标识对应的业务。
  6. 根据权利要求1所述的方法,其中,所述装载所述软件数据对应的软件,并使能所述软件对应的业务,包括:
    接收用户的业务使用请求;
    运行所述软件向用户提供相应的业务,以使能软件对应的业务。
  7. 一种业务使能方法,用于NSCDF,所述方法包括:
    向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
  8. 根据权利要求7所述的方法,还包括:在所述向IUSU发送业务下载通知之前,
    接收业务管理网关SMG发送的业务发布通知;
    根据所述业务发布通知,从所述SMG中下载所述软件数据。
  9. 根据权利要求8所述的方法,其中,所述根据所述业务发布通知,从所述SMG中下载所述软件数据,包括:
    确定所述NSCDF是否满足所述业务发布通知中包括的软件数据的存储空间需求;
    当所述NSCDF满足所述存储空间需求时,向所述SMG发送第二业务软件数据下载请求;所述第二业务软件数据下载请求中包括业务标识;
    接收所述SMG根据所述第二业务软件数据下载请求发送的所述软件数据,并存储所述软件数据。
  10. 根据权利要求7-9任一项所述的方法,还包括:
    接收所述IUSU发送的第一业务软件数据下载请求;
    根据所述第一业务软件数据下载请求中包括的业务标识,向所述IUSU发送所述软件数据。
  11. 根据权利要求10所述的方法,还包括:
    接收所述IUSU发送的业务启动成功通知;
    记录所述IUSU支持所述业务启动成功通知中包括的所述业务标识对应的业务。
  12. 一种业务使能方法,用于SMG,所述方法包括:
    向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF从所述SMG中下载所述业务发布通知对应业务的软件数据。
  13. 根据权利要求12所述的方法,还包括:
    接收所述NSCDF发送的第二业务软件数据下载请求;
    根据所述第二业务软件数据下载请求携带的业务标识,向所述NSCDF发送所述软件数据。
  14. 一种业务处理方法,用于第一IUSU,所述第一IUSU利用权利要求1-6任一项所述的业务使能方法进行业务使能,所述方法包括:
    接收终端发送的业务请求;
    在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
  15. 根据权利要求14所述的方法,还包括:
    根据所述业务请求中包括的业务标识和所述第一IUSU支持的业务列表,确定是否支持所述业务;
    当所述业务标识未在所述业务列表中时,确定不支持所述业务。
  16. 根据权利要求14所述的方法,其中,所述向所述终端返回失败响应,包括:
    根据NSCDF发送的业务能力查询响应,生成所述失败响应,所述失败响应中包括业务支持IUSU列表;
    向所述终端发送所述失败响应。
  17. 根据权利要求16所述的方法,还包括:
    向所述NSCDF发送业务能力查询请求;所述业务能力查询请求中包括所述第一IUSU配置的公共IUSU列表;
    接收所述NSCDF针对所述业务能力查询请求发送的所述业务能力查询响应;所述业务能力查询响应中包括所述业务支持IUSU列表。
  18. 根据权利要求17所述的方法,其中,所述业务支持IUSU列表中包括所述公共IUSU列表中支持所述业务的一个或多个所述第二IUSU的标识。
  19. 一种业务处理方法,用于NSCDF,所述方法包括:
    接收第一IUSU发送的业务能力查询请求;
    向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应中包含一个或多个支持所述业务能力查询请求对应业务的第二IUSU的标识。
  20. 一种业务处理方法,用于终端,所述方法包括:
    向第一IUSU发送业务请求;
    当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,选择一个第二IUSU,并向所述第二IUSU发起用户注册请求。
  21. 一种业务使能装置,用于IUSU,所述装置包括:
    第一接收模块,用于接收网络和业务能力存储功能NSCDF发送的业务软件下载通知;
    下载模块,用于根据所述业务下载通知,从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
    启动模块,用于装载并启动所述软件数据对应的软件。
  22. 一种业务使能装置,用于NSCDF,所述装置包括:
    第二发送模块,用于向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
  23. 一种业务使能装置,用于SMG,所述装置包括:
    第四发送模块,用于向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF根据所述业务发布通知从所述SMG中下载所述业务发布通知对应业务的软件数据。
  24. 一种业务处理装置,用于第一IUSU,所述装置包括:
    第四接收模块,用于接收终端发送的业务请求;
    第六发送模块,用于在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
  25. 一种业务处理装置,用于NSCDF,所述装置包括:
    第六接收模块,用于接收第一IUSU发送的业务能力查询请求,所述业务能力查询请求为所述第一IUSU在不支持终端发送的业务请求对应的业务的情况下发送的;
    第八发送模块,用于向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应用于指示至少一个支持所述业务的第二IUSU。
  26. 一种业务处理装置,用于终端,所述装置包括:
    第九发送模块,用于向第一IUSU发送业务请求;
    第十发送模块,用于当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,向所述失败响应中包括的至少一个支持所述业务请求对应的业务的第二IUSU发起用户注册请求。
  27. 一种通信设备,包括:接收器和处理器;
    所述接收器用于接收网络和业务能力存储功能NSCDF发送的业务下载通知;
    所述接收器还用于根据所述业务下载通知,从所述NSCDF中下载所述业务下载通知对应业务的软件数据;
    所述处理器用于装载并启动所述软件数据对应的软件。
  28. 一种通信设备,包括:发送器;
    所述发送器用于向IUSU发送业务软件下载通知,所述业务软件下载通知用于通知所述IUSU从所述NSCDF中下载所述业务下载通知对应业务的软件数据。
  29. 一种通信设备,包括:发送器;
    所述发送器,用于向NSCDF发送业务发布通知,所述业务发布通知用于通知所述NSCDF根据所述业务发布通知从所述SMG中下载所述业务发布通知对应业务的软件数据。
  30. 一种通信设备,包括:接收器和发送器;
    所述接收器用于接收终端发送的业务请求;
    所述发送器用于在不支持所述业务请求对应的业务的情况下,向所述终端返回失败响应,所述失败响应用于指示所述终端注册至支持所述业务的第二IUSU。
  31. 一种通信设备,包括:接收器和发送器;
    所述接收器用于接收第一IUSU发送的业务能力查询请求,所述业务能力查询请求为所述第一IUSU在不支持终端发送的业务请求对应的业务的情况下发送的;
    所述发送器用于向所述第一IUSU返回业务能力查询响应,所述业务能力查询响应用于指示至少一个支持所述业务的第二IUSU。
  32. 一种通信设备,包括:发送器;
    所述发送器用于向第一IUSU发送业务请求;
    所述发送器还用于当接收到所述第一IUSU返回的失败响应时,根据所述失败响应,向所述失败响应中包括的至少一个支持所述业务请求对应的业务的第二IUSU发起用户注册请求。
  33. 一种计算机可读存储介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1至20中任一项所述的方法的步骤。
  34. 一种计算机程序产品,包括计算机程序,该计算机程序被处理器执行时实现权利要求1至20中任一项所述的方法的步骤。
PCT/CN2024/127769 2024-05-29 2024-10-28 业务使能方法、业务处理方法、装置和通信设备 Pending WO2025246166A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410682412.1A CN121056827A (zh) 2024-05-29 2024-05-29 业务使能方法、业务处理方法、装置和通信设备
CN202410682412.1 2024-05-29

Publications (1)

Publication Number Publication Date
WO2025246166A1 true WO2025246166A1 (zh) 2025-12-04

Family

ID=97811732

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/127769 Pending WO2025246166A1 (zh) 2024-05-29 2024-10-28 业务使能方法、业务处理方法、装置和通信设备

Country Status (2)

Country Link
CN (1) CN121056827A (zh)
WO (1) WO2025246166A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200252849A1 (en) * 2017-10-20 2020-08-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method, device for service bearer network handover and computer storage medium
CN116527759A (zh) * 2023-05-05 2023-08-01 中国建设银行股份有限公司 银企互联方法、装置、代理服务器、介质及产品
CN116827937A (zh) * 2023-07-17 2023-09-29 中国电信股份有限公司技术创新中心 应用列表下发方法、装置、计算机设备和存储介质
CN118474168A (zh) * 2024-05-08 2024-08-09 中国电信股份有限公司技术创新中心 业务能力调用方法、装置、计算机设备、可读存储介质和程序产品

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200252849A1 (en) * 2017-10-20 2020-08-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method, device for service bearer network handover and computer storage medium
CN116527759A (zh) * 2023-05-05 2023-08-01 中国建设银行股份有限公司 银企互联方法、装置、代理服务器、介质及产品
CN116827937A (zh) * 2023-07-17 2023-09-29 中国电信股份有限公司技术创新中心 应用列表下发方法、装置、计算机设备和存储介质
CN118474168A (zh) * 2024-05-08 2024-08-09 中国电信股份有限公司技术创新中心 业务能力调用方法、装置、计算机设备、可读存储介质和程序产品

Also Published As

Publication number Publication date
CN121056827A (zh) 2025-12-02

Similar Documents

Publication Publication Date Title
WO2019047821A1 (zh) 业务路由的方法、装置及存储介质
CN112350978A (zh) 一种业务处理方法、系统、设备及存储介质
CN110162345A (zh) 一种应用程序访问方法、装置和存储介质
CN107635027B (zh) 一种域名解析方法、介质、装置和计算设备
US12106253B2 (en) Container management method, apparatus, and device
US10162952B2 (en) Security model for network information service
CN114625479A (zh) 边缘计算中云边协同应用管理方法及对应的装置
CN114281263A (zh) 容器集群管理系统的存储资源处理方法、系统和设备
CN115048642A (zh) 多可信执行环境下可信应用间的通信方法及电子设备
CN112073448A (zh) 一种双系统终端的服务隔离方法和装置
WO2026016770A1 (zh) 云网络系统、通信方法、设备、存储介质及程序产品
CN113973126A (zh) 车端子系统间的通信方法、装置、电子设备及介质
CN115604333B (zh) 基于dubbo的分布式大数据分析服务调度方法及系统
CN111694639A (zh) 进程容器地址的更新方法、装置和电子设备
CN112688811B (zh) 无线局域网络管理方法、装置、设备和存储介质
WO2025246166A1 (zh) 业务使能方法、业务处理方法、装置和通信设备
CN112910673B (zh) 一种确定网元部署信息的方法、装置、设备及存储介质
US11811878B1 (en) Session manager providing bidirectional data transport
CN117762564A (zh) 函数处理方法及装置、电子设备和计算机可读存储介质
CN112559213B (zh) 应用通信方法、装置、计算机设备和存储介质
CN115580614A (zh) 一种数据下载方法、装置、设备及计算机可读存储介质
CN111506320B (zh) 装机方法、装机配置方法、装置及设备
US20220376992A1 (en) Network Function Management
KR102086088B1 (ko) 접속점 이름을 변경하는 단말 장치, 디바이스 매니저 어플리케이션 및 서비스 어플리케이션
CN119496815B (zh) 基于AutosarAP平台动态加载服务的通道和实例的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24941438

Country of ref document: EP

Kind code of ref document: A1