WO2021159891A1 - Procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, dispositifs, appareil et support - Google Patents

Procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, dispositifs, appareil et support Download PDF

Info

Publication number
WO2021159891A1
WO2021159891A1 PCT/CN2021/070468 CN2021070468W WO2021159891A1 WO 2021159891 A1 WO2021159891 A1 WO 2021159891A1 CN 2021070468 W CN2021070468 W CN 2021070468W WO 2021159891 A1 WO2021159891 A1 WO 2021159891A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
user
authorization
nef
information
Prior art date
Application number
PCT/CN2021/070468
Other languages
English (en)
Chinese (zh)
Inventor
毕晓宇
张玲
侯云静
陶源
Original Assignee
大唐移动通信设备有限公司
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 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2021159891A1 publication Critical patent/WO2021159891A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular to a method, equipment, device, and medium for calling request, query, and authorization processing.
  • Edge computing is an important technology that meets the key performance indicators of 5G networks.
  • Operators can provide computing capabilities and services for vertical industries through the deployment of MEC (Multi-access Edge Computing), and open network capabilities to third-party applications .
  • MEC Multi-access Edge Computing
  • vertical industries can deploy various applications to the edge of the operator's network with the help of MEC, and invoke the capabilities of network openness.
  • FIG. 1 is a schematic diagram of the network architecture of the MEC with offloaded UPF (User Plane Function) defined by SA2
  • Figure 2 is a schematic diagram of the network architecture of the MEC without offloaded UPF defined by SA2.
  • the edge computing defined by SA2 The two architectures are shown in Figures 1 and 2, where the local UPF (PSA (PDU Session Anchor, PDU Session Anchor; PDU: Protocol Data Unit)/BP (Branching Point)) performs local Offloading, the remote UPF serves as the remote anchor point of the edge computing service, and the local UPF (User Plane Function) and the remote UPF access the same DN (Data Network).
  • the offloading strategy is in charge of the SMF (Session Management Function), and the SMF can formulate offloading strategies based on the operating status, application location, or UE (User Equipment) location.
  • SMF Session Management Function
  • FIG. 3 is a schematic diagram of the network structure of the edge data network providing services to the UE.
  • the current application layer of edge computing is divided into a three-layer structure, the edge application server (Edge Application Server) and the edge computing enable server (Edge Enabler). Server), and Edge Computing Network Configuration Server (Edge Data Network Configuration Server).
  • the UE acts as an edge computing application client (Application Client) to make an application request between the edge computing application server. Before the request, the UE needs to obtain information from the edge computing enabling server to the edge computing application server in order to establish interaction with the edge application server.
  • the edge data network configuration server is used to send the edge application server address to the Edge Enabler Client of the UE.
  • the edge computing network and the 3GPP network interact with corresponding network elements through edge application servers and edge computing enabling servers.
  • the disadvantage of the related technology is that in the existing edge computing process, user information will be leaked.
  • the embodiment of the present disclosure provides a method for processing request invocation, including:
  • the edge computing application server As an AF requests a call to the 3GPP network NEF, it queries the UE's permission or authorization for the call;
  • the UE When it is determined that the UE has permitted or authorized the call, it requests the call to the 3GPP network NEF.
  • the edge computing application server when the edge computing application server queries the UE's permission or authorization for the call, it queries the user configuration information server at the application layer;
  • the method further includes:
  • the user information server in the UDM and the application layer shares the UE's permission or authorization information for the call
  • the user permission information and the user who uses the UDM and the application layer are carried.
  • the verification code calculated by the security key shared by the information server.
  • the embodiment of the present disclosure provides a method for processing request invocation, including:
  • NEF queries the UE's permission or authorization for the call
  • NEF allows the edge computing application server to be called when it determines that the UE has approved or authorized the call.
  • the NEF when receiving the call requested by the edge computing application server from the 3GPP network NEF as the AF, the NEF queries the UDM or UDR for the UE's permission or authorization for the call; or,
  • NEF When receiving a call with user permission information requested by the edge computing application server from the 3GPP network NEF, NEF queries UDM for the UE's permission or authorization for the call; or,
  • NEF Receiving the call with user permission information and verification code requested by the edge computing application server from the 3GPP network NEF, NEF queries the local database for the UE’s permission or authorization for the call according to the user’s authorization configuration, or queries the UDM for the UE’s permission for the call or Authorization.
  • the embodiment of the present disclosure provides a query and call method, including:
  • the UDM or UDR receives NEF's query on the call, and the query is to query whether the call is a call permitted or authorized by the UE;
  • the UDM or UDR determines whether the call is a call authorized or authorized by the UE according to the user authorization configuration, and feeds the determination result back to the NEF.
  • the user authorization configuration is pre-configured or configured according to user authorization configuration information sent by the edge computing enabling server.
  • the embodiment of the present disclosure provides a method for invoking authorization, which includes:
  • the UE determines the APP call permitted or authorized by the user
  • the UE determines the user authorization configuration information according to the APP call information permitted or authorized by the user;
  • the UE sends the user authorization configuration information to the edge computing enabling server.
  • the method further includes:
  • the UE saves the user authorization configuration information.
  • the method further includes:
  • the user authorization configuration information is updated according to the instruction of the edge computing enabling server.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the embodiment of the present disclosure provides a processing method for invoking authorization, which includes:
  • the edge computing enabling server receives the user authorization configuration information sent by the UE, where the user authorization configuration information contains APP invocation information permitted or authorized by the user;
  • the edge computing enabling server sends the user authorization configuration information to the network side device for the NEF to query and call the license or authorization.
  • the network side device is one or a combination of the following devices: UDM, UDR, user information server at the application layer, NEF.
  • the method further includes:
  • the edge computing enabling server instructs the UE to update the user authorization configuration information on the UE.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the embodiment of the present disclosure provides a processing method for invoking authorization, which includes:
  • the network-side device receives the user authorization configuration information sent by the edge computing enabling server, where the user authorization configuration information includes the APP invocation information permitted or authorized by the user;
  • the network side device receives the query for the call sent by the NEF, where the query is to query whether the call is a call permitted or authorized by the UE;
  • the network side device determines whether the call is a call approved or authorized by the UE according to the user authorization configuration.
  • the network side device is one or a combination of the following devices: UDM, UDR, user information server at the application layer, NEF.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • An embodiment of the present disclosure provides an edge computing application server, including:
  • the processor is used to read the program in the memory and execute the following process:
  • the edge computing application server As an AF requests a call to the 3GPP network NEF, it queries the UE's permission or authorization for the call;
  • the UE When it is determined that the UE has permitted or authorized the call, it requests the call to the 3GPP network NEF;
  • Transceiver used to receive and send data under the control of the processor.
  • the edge computing application server when the edge computing application server queries the UE's permission or authorization for the call, it queries the user configuration information server at the application layer;
  • the processor is further used for:
  • the user information server in the UDM and the application layer shares the UE's permission or authorization information for the call
  • the user permission information and the user who uses the UDM and the application layer are carried.
  • the verification code calculated by the security key shared by the information server.
  • An embodiment of the present disclosure provides a processing device for request invocation, including:
  • the first query module is used to query the UE's permission or authorization for the call when the edge computing application server as an AF requests a call to the 3GPP network NEF;
  • the request module is used to request the call from the 3GPP network NEF when it is determined that the UE has permitted or authorized the call.
  • NEF is provided in the embodiments of the present disclosure, including:
  • the processor is used to read the program in the memory and execute the following process:
  • the call to the edge computing application server is allowed
  • Transceiver used to receive and send data under the control of the processor.
  • the edge computing application server when receiving the call requested by the edge computing application server from the 3GPP network NEF as the AF, query the UDM or UDR for the UE's permission or authorization for the call; or,
  • An embodiment of the present disclosure provides a processing device for request invocation, including:
  • the first receiving module is used to receive the call requested by the edge computing application server from the 3GPP network NEF as the AF, or receive the call carrying user permission information requested by the edge computing application server from the 3GPP network NEF, or receive the call from the edge computing application server to the 3GPP network NEF.
  • 3GPP network NEF requests to carry user permission information and verification code calls, where the verification code is to use UDM and application layer user information when UDM and application layer user information server share UE’s permission or authorization information for the call The verification code calculated from the security key shared by the server;
  • the second query module is used to query the UE's permission or authorization for the call
  • the calling module is used to allow the edge computing application server to be called when it is determined that the UE has approved or authorized the calling.
  • An embodiment of the present disclosure provides a communication device located in UDM or UDR, including:
  • the processor is used to read the program in the memory and execute the following process:
  • the UDM or UDR receives NEF's query on the call, and the query is to query whether the call is a call permitted or authorized by the UE;
  • UDM or UDR determines whether the call is authorized or authorized by the UE according to the user authorization configuration, and feeds the determination result back to NEF;
  • Transceiver used to receive and send data under the control of the processor.
  • the user authorization configuration is pre-configured or configured according to user authorization configuration information sent by the edge computing enabling server.
  • An embodiment of the present disclosure provides a communication device located in UDM or UDR, including:
  • the second receiving module is configured to receive a query from NEF to a call, and the query is to query whether the call is a call permitted or authorized by the UE;
  • the authorization confirmation module is used to determine whether the call is a call authorized or authorized by the UE according to the user authorization configuration, and feed the determination result back to the NEF.
  • An embodiment of the present disclosure provides a terminal device, including:
  • the processor is used to read the program in the memory and execute the following process:
  • Transceiver used to receive and send data under the control of the processor.
  • the processor is further configured to:
  • the processor is further configured to:
  • the user authorization configuration information is updated according to the instruction of the edge computing enabling server.
  • the user permits or authorizes APP invocation based on the granularity of the application or the granularity of the invocation event.
  • An embodiment of the present disclosure provides a calling authorization device, including:
  • the first determining module is used to determine the APP call permitted or authorized by the user
  • the configuration module is used to determine the user authorization configuration information according to the APP call information permitted or authorized by the user;
  • the first sending module is configured to send the user authorization configuration information to the edge computing enabling server.
  • the embodiment of the present disclosure provides an edge computing enabling server, including:
  • the processor is used to read the program in the memory and execute the following process:
  • Transceiver used to receive and send data under the control of the processor.
  • the network side device is one or a combination of the following devices: UDM, UDR, user information server at the application layer, NEF.
  • the processor is further configured to:
  • the UE According to the user's instruction in the process of requesting the edge computing application, instruct the UE to update the user authorization configuration information on the UE.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • An embodiment of the present disclosure provides a processing device for invoking authorization, including:
  • the third receiving module is configured to receive user authorization configuration information sent by the UE, where the user authorization configuration information contains APP invocation information permitted or authorized by the user;
  • the second sending module is used to send the user authorization configuration information to the network side device for NEF to query and call the permission or authorization.
  • the embodiments of the present disclosure provide a communication device, which is located in the following devices UDM, UDR, user information server or NEF at the application layer, including:
  • the processor is used to read the program in the memory and execute the following process:
  • Transceiver used to receive and send data under the control of the processor.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • An embodiment of the present disclosure provides a processing device for invoking authorization, including:
  • the fourth receiving module is configured to receive user authorization configuration information sent by the edge computing enabling server, where the user authorization configuration information includes APP invocation information permitted or authorized by the user;
  • the fifth receiving module is configured to receive a query for a call sent by NEF, where the query is to query whether the call is a call permitted or authorized by the UE;
  • the second determining module is configured to determine whether the call is a call permitted or authorized by the UE according to the user authorization configuration.
  • An embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores a program for executing the above method.
  • the UE determines the user authorization configuration information according to the APP call information permitted or authorized by the user, and sends it to the edge computing enabling server;
  • the edge computing enabling server receives the user authorization configuration information sent by the UE and sends it to the network side device for NEF to query and call the license or authorization;
  • the network side device can be UDM, UDR, application layer user information server, NEF, etc.
  • the edge computing application server When the edge computing application server as an AF requests a call to the 3GPP network NEF, it queries the UE for permission or authorization for the call; when it is determined that the UE has permission or authorization for the call, it requests the call to the 3GPP network NEF;
  • NEF allows the edge computing application server to be called when it determines that the UE has approved or authorized the call.
  • the edge computing application server when the edge computing application server makes a call, it will query whether the call is permitted or authorized; on the other hand, because UDM, UDR, the user information server at the application layer, NEF, etc. already know the user’s call to the application
  • the permission or authorization can confirm the called query. Therefore, it can verify the user's authorization or permission query for the edge computing application to call the network capability, so as to avoid the leakage of user information when the edge computing application calls the network capability.
  • FIG. 1 is a schematic diagram of the network architecture of the MEC with offloaded UPF defined by SA2 in the background art
  • FIG. 2 is a schematic diagram of the network architecture of the MEC without the offloaded UPF defined by SA2 in the background art
  • FIG. 3 is a schematic diagram of a network structure in which an edge data network provides services to UEs in the background art
  • FIG. 4 is a schematic diagram of the relationship between the authorization processing stage and the call processing stage in the embodiments of the disclosure.
  • FIG. 5 is a schematic diagram of the implementation process of the method for invoking authorization on the UE side in an embodiment of the disclosure
  • FIG. 6 is a schematic diagram of an implementation process of a processing method for invoking authorization on the edge computing enable server side in an embodiment of the disclosure
  • FIG. 7 is a schematic diagram of an implementation process of a processing method for invoking authorization on a network side device in an embodiment of the disclosure
  • FIG. 8 is a schematic diagram of an implementation flow of authorization processing in Embodiment 1 of the present disclosure.
  • FIG. 9 is a schematic diagram of an implementation flow of authorization processing in Embodiment 2 of the disclosure.
  • FIG. 10 is a schematic diagram of the implementation process of the processing method for request invocation on the side of the edge computing application server of the present disclosure
  • FIG. 11 is a schematic diagram of the implementation flow of the processing method for request invocation on the NEF side of the present disclosure
  • FIG. 12 is a schematic diagram of the implementation process of the query and invocation method on the UDM side of the present disclosure
  • FIG. 13 is a schematic diagram of the implementation flow of the call processing in the third embodiment of the disclosure.
  • FIG. 14 is a schematic diagram of the implementation flow of calling processing in the fourth embodiment of the disclosure.
  • FIG. 15 is a schematic diagram of the implementation flow of calling processing in Embodiment 5 of the present disclosure.
  • FIG. 16 is a schematic diagram of the implementation flow of the call processing in the sixth embodiment of the disclosure.
  • FIG. 17 is a schematic diagram of structure 1 of an edge computing application server in an embodiment of the disclosure.
  • FIG. 18 is a schematic diagram of the NEF structure in an embodiment of the disclosure.
  • FIG. 19 is a schematic diagram of structure 1 of a communication device in an embodiment of the disclosure.
  • FIG. 20 is a schematic diagram of a UE structure in an embodiment of the disclosure.
  • FIG. 21 is a schematic diagram of structure 2 of an edge computing enabled server in an embodiment of the disclosure.
  • FIG. 22 is a schematic diagram of structure 2 of a communication device in an embodiment of the disclosure.
  • the network function needs to be opened to the edge application server, and some sensitive information may be involved in this process, especially the sensitive information of some users (such as location information). Therefore, the UE needs to know which network capabilities the network will open to which edge computing applications, and whether the user allows these edge computing applications to call the network capabilities to obtain user information.
  • the embodiment of the present disclosure provides a processing solution in the process of the edge computing application server requesting the NEF call to solve how the user agrees or authorizes the edge computing service to call the open network API to access the user's information, especially the private information.
  • the implementation stage is divided into two parts for description, one part is called the authorization processing stage in the embodiment, and the other part is called the call processing stage in the embodiment. Obviously, the two parts are both independent and interrelated.
  • the application authorization allowed by the user can be determined through the authorization processing stage, and the application can be invoked according to the user's authorization through the invocation processing stage to achieve the purpose of protecting user information.
  • the user's permission information for using the network capability of a certain service is synchronized at the application layer and the core network, and the configuration update of the user's application attribute is also applied
  • the layer and core network are changed synchronously; when the edge computing application service calls the network capability, NEF (Network Exposure Function) will save the user configuration authorization sent by the received AS (Access Stratum) with the core network Match.
  • NEF Network Exposure Function
  • Figure 4 is a schematic diagram of the relationship between the authorization processing stage and the call processing stage, as shown in the figure, including:
  • step 401 the user's permission configuration for the APP to call the network capability
  • Step 402 authorization verification of the user APP invoking the network capability.
  • the user's update of the application configuration can be uploaded to the database of the application layer (the information server of the UE) through the edge computing enable server. That is, the application layer and the core network recognize the UE's permission to call the API according to the authorization configuration of the UE.
  • Authorization configuration defines which API calls are allowed or not allowed to call network capabilities.
  • Figure 5 is a schematic diagram of the implementation process of the UE side invoking the authorization method. As shown in the figure, it can include:
  • Step 501 The UE determines the APP call permitted or authorized by the user
  • Step 502 The UE determines user authorization configuration information according to the APP call information permitted or authorized by the user;
  • Step 503 The UE sends the user authorization configuration information to the edge computing enabling server.
  • the method may further include:
  • the UE saves the user authorization configuration information.
  • the method may further include:
  • the user authorization configuration information is updated according to the instruction of the edge computing enabling server.
  • Figure 6 is a schematic diagram of the implementation process of the processing method of invoking authorization on the edge computing enable server side. As shown in the figure, it can include:
  • Step 601 The edge computing enabling server receives user authorization configuration information sent by the UE, where the user authorization configuration information includes APP invocation information permitted or authorized by the user;
  • Step 602 The edge computing enabling server sends the user authorization configuration information to the network side device for the NEF to query and call the license or authorization.
  • the network-side device may be one of the following devices or a combination of them: UDM (Unified Data Management), UDR (Unified Data Repository), application layer users Information server, NEF.
  • UDM Unified Data Management
  • UDR Unified Data Repository
  • NEF application layer users Information server
  • the method may further include:
  • the edge computing enabling server instructs the UE to update the user authorization configuration information on the UE.
  • Figure 7 is a schematic diagram of the implementation process of the processing method for invoking authorization on the network side device, as shown in the figure, which may include:
  • Step 701 The network side device receives user authorization configuration information sent by the edge computing enablement server, where the user authorization configuration information includes APP invocation information permitted or authorized by the user;
  • Step 702 The network side device receives the query for the call sent by the NEF, where the query is to query whether the call is a call permitted or authorized by the UE;
  • Step 703 The network side device determines whether the call is a call permitted or authorized by the UE according to the user authorization configuration.
  • the network-side device may be one or a combination of the following devices: UDM, UDR, user information server at the application layer, NEF.
  • the user's authorization for APP authorization can be pre-configured in the core network element UDM, or pre-configured in the server responsible for user subscription information management at the application layer.
  • the user's license information can also be stored on the terminal side.
  • the invocation permission configuration can be based on the application as the granularity or based on the invocation event as the granularity.
  • the configuration information contains the APP ID (application identification) information, and the APP can call all the capabilities supported by the core network capability opening; if the granularity is based on the call event, the configuration information contains It is event ID (event identification) information, which only supports the ability of the APP to call a certain event. That is, in some optional embodiments described above, the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the user can update the UE configuration information through the edge computing enablement server to update the UE whether the APP is authorized to call the network capability identifier for the APP.
  • the request to enable the server is processed by UDM or UDR.
  • FIG. 8 is a schematic diagram of the authorization processing implementation flow of Embodiment 1. As shown in the figure, it may include:
  • Step 801 Request the edge computing application server information to carry information about whether the APP is allowed to call network capabilities.
  • the user requests the edge computing server information, and the request carries the capability information whether the user is allowed to call the network.
  • Step 802 Update request (query the UE's permission status for each APP, and update the settings if they are inconsistent).
  • the edge computing application server interacts with the 3GPP network element to request to query and update the user's ability to call permission for a certain APP.
  • the network element used for illustration in the figure is UDM or UDR.
  • Step 803 The UE privacy permission flag is 1, and the call is allowed. Otherwise, it is 0, and the UE privacy permission flag information is bound to the UE identity and the APP identity.
  • the 3GPP network entity verifies the request message. After the verification is passed, the permission identifier is updated according to the user ID, APP identifier/APP event ID.
  • Step 804 Update the response, notifying that it has been updated according to the user's wishes.
  • the 3GPP network entity returns update response information.
  • Step 805 APP information and the APP call network capability update notification identifier.
  • the enabling server notifies the user to update the license identifier while responding to the APP information.
  • it is the user configuration server at the application layer that processes the request to enable the server.
  • Fig. 9 is a schematic diagram of the authorization processing implementation flow of the second embodiment. As shown in the figure, it may include:
  • Step 901 Request the edge computing application server information to carry information about whether the APP is allowed to call network capabilities.
  • the user requests the edge computing server information, and the request carries the capability information whether the user is allowed to call the network.
  • Step 902 Update request (query the UE's permission status for each APP, and update the settings if they are inconsistent).
  • the edge computing application server interacts with the user configuration server at the application layer, requesting to query and update the user's ability to call permission for a certain APP.
  • Step 903 The UE privacy permission flag is 1, and the call is allowed. Otherwise, it is 0, and the UE privacy permission flag information is bound to the UE ID and APP ID.
  • the user at the application layer configures the server body verification request message, and after the verification is passed, the license identification is updated according to the user's ID and APP identification.
  • the network element used for illustration in the figure is the user profile server in the application layer (UE profile server in Application layer).
  • Step 904 Update the response, notifying that it has been updated according to the user's wishes.
  • the user configuration server of the application layer returns the update response information.
  • Step 905 APP information and APP call network capability update notification identifier.
  • the enabling server notifies the user to update the license identifier while responding to the APP information.
  • the user information server is actually a proxy entity of the core network UDM, which stores configuration information of edge computing nodes.
  • the data in the proxy entity is the mirror image of the core network UDM.
  • the server can delete the user's subscription configuration information. That is, through the configuration at the application layer, users can quickly query the application network capability opening authorization.
  • the first embodiment and the second embodiment can be independent or related.
  • the core network and the application layer fully trust each other, they can be used independently, otherwise the enabler server needs to synchronize the UE configuration information in the application layer and UDM at the same time.
  • FIG. 10 is a schematic diagram of the implementation process of the processing method of request invocation on the edge computing application server side. As shown in the figure, it may include:
  • Step 1001 When the edge computing application server as an AF requests a call to the 3GPP network NEF, query the UE's permission or authorization for the call;
  • Step 1002 when it is determined that the UE has granted or authorized the call, request the call to the 3GPP network NEF.
  • the edge computing application server when the edge computing application server queries the UE's permission or authorization for the call, it queries the user configuration information server at the application layer;
  • the method may further include:
  • the user information server in the UDM and the application layer shares the UE's permission or authorization information for the call
  • the user permission information and the user who uses the UDM and the application layer are carried.
  • the verification code calculated by the security key shared by the information server.
  • Figure 11 is a schematic diagram of the implementation process of the processing method for request invocation on the NEF side. As shown in the figure, it can include:
  • Step 1101 Receive the call requested by the edge computing application server from the 3GPP network NEF as the AF, or receive the call carrying user license information requested by the edge computing application server from the 3GPP network NEF, or receive the request from the edge computing application server to the 3GPP network NEF Carrying user permission information and verification code calls, where the verification code is the security shared by the UDM and the user information server of the application layer when the UDM and the user information server of the application layer share the UE’s permission or authorization information for the call The verification code calculated by the key;
  • Step 1102 NEF queries the UE's permission or authorization for the call
  • Step 1103 When the NEF determines that the UE has approved or authorized the call, it allows the edge computing application server to call.
  • the NEF when receiving the call requested by the edge computing application server from the 3GPP network NEF as the AF, the NEF queries the UDM or UDR for the UE's permission or authorization for the call; or,
  • NEF When receiving a call with user permission information requested by the edge computing application server from the 3GPP network NEF, NEF queries UDM for the UE's permission or authorization for the call; or,
  • NEF Receiving the call with user permission information and verification code requested by the edge computing application server from the 3GPP network NEF, NEF queries the local database for the UE’s permission or authorization for the call according to the user’s authorization configuration, or queries the UDM for the UE’s permission for the call or Authorization.
  • Figure 12 is a schematic diagram of the implementation process of the query invocation method on the UDM side. As shown in the figure, it can include:
  • Step 1201 The UDM or UDR receives the NEF query on the call, where the query is to query whether the call is a UE permitted or authorized call;
  • Step 1202 the UDM or UDR determines whether the call is a call permitted or authorized by the UE according to the user authorization configuration, and feeds the determination result back to the NEF.
  • the user authorization configuration is pre-configured or configured according to user authorization configuration information sent by the edge computing enabling server.
  • the edge computing application server (enable server, at this time, the enable server is the proxy of the edge application server) as an AF (Application Function) to the 3GPP network
  • NEF Network Exposure Function
  • an AF When an AF initiates a request, it needs to carry the edge computing service type, or the network recognizes that the AF is an application instance of edge computing through an IP address.
  • NEF When NEF receives this type of request, it needs to query the user configuration information to confirm whether the UE allows the call or authorizes the call.
  • the user configuration information can be a 3GPP network entity UDM or UDR, or an independent user configuration information server at the application layer.
  • Figure 13 is a schematic diagram of the implementation flow of the call processing in the third embodiment. As shown in the figure, it may include:
  • Step 1301 Invoke the capability request, which carries the identifier of the UE and the edge computing service type.
  • the edge computing application server requests the NEF to verify whether the UE allows the APP to call network capabilities.
  • Step 1302 Invoke the capability verification request.
  • NEF initiates a request to UDM/UDR to query whether UR is allowed to call the APP or the event ID of the APP.
  • Step 1303 Confirm whether the service is allowed to be invoked through the UE identification, the calling ID, the APP identification, and the privacy permission identification of the UE.
  • Step 1304 If allowed, return related call information.
  • UDM/UDR returns the user authorization identification information corresponding to NEF. If the call is allowed, the UDM/UDR returns the license identifier as 1. Otherwise, the UDM/UDR returns the license ID as 0.
  • Step 1305 Return the calling information to the APP.
  • NEF returns the corresponding event information if the permission result of the query is 1. Otherwise, the return event information is empty.
  • NEF calls the user license information through the enabling server.
  • Figure 14 is a schematic diagram of the implementation flow of the call processing in the fourth embodiment. As shown in the figure, it may include:
  • Step 1401 Invoke the permission request, which carries the identifier of the UE and the edge computing service type.
  • the edge computing application server queries the user configuration information server of the application layer for the user's authorization information for invoking network capabilities.
  • Step 1402 through the UE/user identification, the calling ID, the APP identification, and the privacy permission identification of the UE to confirm whether the calling is allowed.
  • the application layer user information configuration server queries the user's authorization for the microservice based on the user ID, event ID, and APP ID.
  • Step 1403 If allowed, return the related call information, carrying the permission information identifier.
  • the application layer user information configuration server returns the configuration information to the application server.
  • the license ID is 1. Otherwise, the return permission ID is 0.
  • Step 1404 Invoke the capability request, which carries the permission information identifier.
  • the edge computing application server carries user permission information when requesting a service call from the NEF.
  • Step 1405 Invoke the capability request, which carries the license information identifier.
  • NEF forwards to UDM.
  • Step 1406 Verification of the license information identification.
  • UDM verifies whether the license identifier is consistent with the locally stored one.
  • Step 1407 Return the calling information to the APP.
  • UDM If they agree that the user is allowed to call, UDM returns the result to NEF.
  • Step 1408 Return the calling information to the APP.
  • NEF returns the user information event information that needs to be called to the APP. Otherwise, the return event information is empty.
  • both the application layer user information database and NEF save the user's permission to call the service, and are protected by MAC (Message Authentication Code).
  • MAC is a verification code calculated by the security key shared by the UDM and the user information server at the application layer to ensure that the authorization information will not be tampered with.
  • Figure 15 is a schematic diagram of the implementation flow of the call processing in the fifth embodiment. As shown in the figure, it may include:
  • Step 1501 Query the application invocation capability, which carries the identifier of the UE or the user, and the edge computing service type.
  • the APP server When the APP server requests a 3GPP network service call, it first initiates a query request to the user information server.
  • Step 1502 using the UE or user identification, the calling ID, the APP identification, and the privacy permission identification of the UE to confirm whether the calling is allowed.
  • the application layer user configuration information server queries the user's authorization for the microservice.
  • Step 1503 If allowed, return the related call information, which carries the permission information identifier and the MAC.
  • the edge computing application layer configuration server returns configuration information to the application server.
  • Step 1504 Invoke the capability request, which carries the permission information identifier and MAC.
  • the edge computing application server (enable server) carries user permission information and MAC when requesting service invocation from NEF.
  • Step 1505 Verification of the license information identification.
  • NEF verifies whether the MAC value is consistent with the local MAC. If they are consistent, the user permits the call and returns the result to NEF.
  • Step 1506 Return the calling information to the APP.
  • NEF returns to the APP the information that needs to call the user. If they are inconsistent, an empty message is returned, and the microservice call of the APP is prohibited.
  • both the application layer user information database and UDM store the user's permission to call the service and are protected by MAC.
  • Figure 16 is a schematic diagram of the implementation flow of the call processing in the sixth embodiment. As shown in the figure, it may include:
  • Step 1601 Query the application invocation capability, which carries the identifier of the UE or the user, and the edge computing service type).
  • the APP server (enable server) requests a 3GPP network service call, it first initiates a query request to the user information server.
  • Step 1602 using the UE or user identification, the calling ID, the APP identification, and the privacy permission identification of the UE to confirm whether the calling is allowed.
  • the application layer user configuration information server queries the user's permission for the microservice.
  • Step 1603 If allowed, return the related call information, which carries the permission information identifier and the MAC.
  • the edge computing application layer configuration server returns configuration information to the application server.
  • Step 1604 Invoke the capability request, which carries the permission information identifier and MAC.
  • the edge computing application server carries user permission information and MAC when requesting service invocation from NEF.
  • Step 1605 Invoke the capability request, which carries the permission information identifier and MAC.
  • NEF forwards to UDM.
  • Step 1606 MAC verification.
  • UDM verifies whether the MAC value is consistent with the local MAC.
  • Step 1607 The user permits the call.
  • UDM If they agree that the user is allowed to call, UDM returns the result to NEF.
  • Step 1608 Return the calling information to the APP.
  • NEF returns to the APP the information that needs to call the user.
  • the embodiments of the present disclosure also provide a base station-side device, user equipment, and system. Since these devices have similar principles and methods for solving problems, the implementation of these devices can refer to the implementation of the method. For repetitions No longer.
  • FIG 17 is a schematic diagram of edge computing application server structure 1. As shown in the figure, the server includes:
  • the processor 1700 is configured to read a program in the memory 1720 and execute the following process:
  • the edge computing application server As an AF requests a call to the 3GPP network NEF, it queries the UE's permission or authorization for the call;
  • the UE When it is determined that the UE has permitted or authorized the call, it requests the call to the 3GPP network NEF;
  • the transceiver 1710 is used to receive and send data under the control of the processor 1700.
  • the edge computing application server when the edge computing application server queries the UE's permission or authorization for the call, it queries the user configuration information server at the application layer;
  • the processor 1700 is further used to:
  • the user information server in the UDM and the application layer shares the UE's permission or authorization information for the call
  • the user permission information and the user who uses the UDM and the application layer are carried.
  • the verification code calculated by the security key shared by the information server.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1700 and various circuits of the memory represented by the memory 1720 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1710 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the processor 1700 is responsible for managing the bus architecture and general processing, and the memory 1720 can store data used by the processor 1700 when performing operations.
  • An embodiment of the present disclosure provides a processing device for request invocation, including:
  • the first query module is used to query the UE's permission or authorization for the call when the edge computing application server as an AF requests a call to the 3GPP network NEF;
  • the request module is used to request the call from the 3GPP network NEF when it is determined that the UE has permitted or authorized the call.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • NEF includes:
  • the processor 1800 is configured to read a program in the memory 1820 and execute the following process:
  • the call to the edge computing application server is allowed
  • the transceiver 1810 is used to receive and send data under the control of the processor 1800.
  • the edge computing application server when receiving the call requested by the edge computing application server from the 3GPP network NEF as the AF, query the UDM or UDR for the UE's permission or authorization for the call; or,
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1800 and various circuits of the memory represented by the memory 1820 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1810 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the processor 1800 is responsible for managing the bus architecture and general processing, and the memory 1820 can store data used by the processor 1800 when performing operations.
  • An embodiment of the present disclosure provides a processing device for request invocation, including:
  • the first receiving module is used to receive the call requested by the edge computing application server from the 3GPP network NEF as the AF, or receive the call carrying user permission information requested by the edge computing application server from the 3GPP network NEF, or receive the call from the edge computing application server to the 3GPP network NEF.
  • 3GPP network NEF requests to carry user permission information and verification code calls, where the verification code is to use UDM and application layer user information when UDM and application layer user information server share UE’s permission or authorization information for the call The verification code calculated from the security key shared by the server;
  • the second query module is used to query the UE's permission or authorization for the call
  • the calling module is used to allow the edge computing application server to be called when it is determined that the UE has approved or authorized the calling.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • FIG 19 is a schematic diagram of communication equipment structure 1, located in UDM or UDR. As shown in the figure, the equipment includes:
  • the processor 1900 is configured to read the program in the memory 1920 and execute the following process:
  • the UDM or UDR receives NEF's query on the call, and the query is to query whether the call is a call permitted or authorized by the UE;
  • UDM or UDR determines whether the call is authorized or authorized by the UE according to the user authorization configuration, and feeds the determination result back to NEF;
  • the transceiver 1910 is used to receive and send data under the control of the processor 1900.
  • the user authorization configuration is pre-configured or configured according to user authorization configuration information sent by the edge computing enabling server.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1900 and various circuits of the memory represented by the memory 1920 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1910 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the processor 1900 is responsible for managing the bus architecture and general processing, and the memory 1920 can store data used by the processor 1900 when performing operations.
  • An embodiment of the present disclosure provides a communication device located in UDM or UDR, including:
  • the second receiving module is configured to receive a query from NEF to a call, and the query is to query whether the call is a call permitted or authorized by the UE;
  • the authorization confirmation module is used to determine whether the call is a call authorized or authorized by the UE according to the user authorization configuration, and feed the determination result back to the NEF.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • Figure 20 is a schematic diagram of the UE structure. As shown in the figure, the user equipment includes:
  • the processor 2000 is configured to read the program in the memory 2020 and execute the following process:
  • the transceiver 2010 is used to receive and send data under the control of the processor 2000.
  • the processor 2000 is further configured to:
  • the processor 2000 is further configured to:
  • the user authorization configuration information is updated according to the instruction of the edge computing enabling server.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 2000 and various circuits of the memory represented by the memory 2020 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 2010 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the user interface 2030 may also be an interface capable of connecting externally and internally with required equipment, and the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 2000 is responsible for managing the bus architecture and general processing, and the memory 2020 can store data used by the processor 2000 when performing operations.
  • An embodiment of the present disclosure provides a calling authorization device, including:
  • the first determining module is used to determine the APP call permitted or authorized by the user
  • the configuration module is used to determine the user authorization configuration information according to the APP call information permitted or authorized by the user;
  • the first sending module is configured to send the user authorization configuration information to the edge computing enabling server.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • FIG. 21 is a schematic diagram of edge computing enabled server structure 2. As shown in the figure, the server includes:
  • the processor 2100 is configured to read a program in the memory 2120, and execute the following process:
  • the transceiver 2110 is used to receive and send data under the control of the processor 2100.
  • the network side device is one or a combination of the following devices: UDM, UDR, user information server at the application layer, NEF.
  • the processor 2100 is further configured to:
  • the UE According to the user's instruction in the process of requesting the edge computing application, instruct the UE to update the user authorization configuration information on the UE.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 2100 and various circuits of the memory represented by the memory 2120 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 2110 may be a plurality of elements, that is, including a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium.
  • the processor 2100 is responsible for managing the bus architecture and general processing, and the memory 2120 can store data used by the processor 2100 when performing operations.
  • An embodiment of the present disclosure provides a processing device for invoking authorization, including:
  • the third receiving module is configured to receive user authorization configuration information sent by the UE, where the user authorization configuration information contains APP invocation information permitted or authorized by the user;
  • the second sending module is used to send the user authorization configuration information to the network side device for NEF to query and call the permission or authorization.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • FIG 22 is a schematic diagram of the structure 2 of the communication device.
  • the user information server or NEF located in the following devices UDM, UDR, and application layer, as shown in the figure, includes:
  • the processor 2200 is configured to read a program in the memory 2220 and execute the following process:
  • the transceiver 2210 is configured to receive and send data under the control of the processor 2200.
  • the user's permission or authorization for APP invocation is based on the granularity of the application or the granularity of the invocation event.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 2200 and various circuits of the memory represented by the memory 2220 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 2210 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the processor 2200 is responsible for managing the bus architecture and general processing, and the memory 2220 can store data used by the processor 2200 when performing operations.
  • An embodiment of the present disclosure provides a processing device for invoking authorization, including:
  • the fourth receiving module is configured to receive user authorization configuration information sent by the edge computing enabling server, where the user authorization configuration information includes APP invocation information permitted or authorized by the user;
  • the fifth receiving module is configured to receive a query for a call sent by NEF, where the query is to query whether the call is a call permitted or authorized by the UE;
  • the second determining module is configured to determine whether the call is a call permitted or authorized by the UE according to the user authorization configuration.
  • each part of the above-mentioned device is divided into various modules or units by function and described separately.
  • the functions of each module or unit can be implemented in the same one or more software or hardware.
  • An embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores a program that executes one or a combination of the following methods:
  • the processing method of request calling the method of query calling, the method of calling authorization, the processing method of calling authorization.
  • the user updates or configures the authorization of a certain edge computing application for invoking network capabilities through the edge computing enabling server; when the edge computing application invokes the network capabilities, the user needs to query the user first. Permission to call network capabilities for this application.
  • the embodiments of the present disclosure can be provided as methods, systems, or program products. Therefore, the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram. It can be understood that the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, each module, unit, sub-unit or sub-module, etc.
  • ASIC application specific integrated circuits
  • DSP digital signal processors
  • DSP Device digital signal processing equipment
  • DSP Device digital signal processing equipment
  • PLD Programmable Logic Device
  • PLD Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, des dispositifs, un appareil et un support. Le procédé comprend les étapes suivantes : un équipement d'utilisateur détermine des informations de configuration d'autorisation d'utilisateur selon des informations d'appel d'application permises ou autorisées par un utilisateur et les envoie à un dispositif côté réseau au moyen d'un serveur d'activation de calcul en périphérie pour une fonction d'exposition de réseau afin d'interroger une permission ou une autorisation pour un appel ; lorsqu'un serveur d'activation de calcul en périphérie agit en tant que fonction d'application pour demander un appel à la fonction d'exposition de réseau d'un réseau 3GPP, la permission ou l'autorisation de l'équipement d'utilisateur pour l'appel est interrogée ; et la fonction d'exposition de réseau permet l'appel du serveur d'activation de calcul en périphérie lorsqu'il est déterminé que l'équipement d'utilisateur a permis ou autorisé l'appel.
PCT/CN2021/070468 2020-02-10 2021-01-06 Procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, dispositifs, appareil et support WO2021159891A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010084031.5A CN113259930A (zh) 2020-02-10 2020-02-10 调用的请求、查询、授权处理方法、设备及装置、介质
CN202010084031.5 2020-02-10

Publications (1)

Publication Number Publication Date
WO2021159891A1 true WO2021159891A1 (fr) 2021-08-19

Family

ID=77219344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070468 WO2021159891A1 (fr) 2020-02-10 2021-01-06 Procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, dispositifs, appareil et support

Country Status (2)

Country Link
CN (1) CN113259930A (fr)
WO (1) WO2021159891A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113783882A (zh) * 2021-09-16 2021-12-10 恒安嘉新（北京）科技股份公司 一种边缘应用的信息获取方法、装置、电子设备及介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113791792B (zh) * 2021-09-03 2023-09-12 北京百度网讯科技有限公司 应用调用信息的获取方法、设备以及存储介质
CN117062052A (zh) * 2022-05-07 2023-11-14 维沃移动通信有限公司 数据处理方法、装置、核心网节点、电子设备和存储介质
WO2024031731A1 (fr) * 2022-08-12 2024-02-15 北京小米移动软件有限公司 Procédé et appareil d'appel d'interface de programmation d'application (api), et support de stockage
WO2024031722A1 (fr) * 2022-08-12 2024-02-15 北京小米移动软件有限公司 Procédé et appareil d'invocation d'interface de programmation d'application (api) ascendante
WO2024164356A1 (fr) * 2023-02-10 2024-08-15 北京小米移动软件有限公司 Procédé et appareil d'autorisation de ressources

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408197A (zh) * 2018-09-29 2019-03-01 上海理想信息产业（集团）有限公司 一种边缘计算引擎的实现方法及装置
CN110169089A (zh) * 2017-01-05 2019-08-23 华为技术有限公司 用于应用友好型协议数据单元会话管理的系统和方法
WO2019194954A1 (fr) * 2018-04-06 2019-10-10 Convida Wireless, Llc Procédés de gestion de connexions à un réseau de données local (ladn) dans un réseau 5g

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428866A (zh) * 2017-08-30 2019-03-05 中兴通讯股份有限公司 提供用户身份信息的方法、系统及计算机可读存储介质
CN109511115B (zh) * 2017-09-14 2020-09-29 华为技术有限公司 一种授权方法和网元
CN109587187B (zh) * 2017-09-28 2024-08-02 华为技术有限公司 用于调用网络功能服务的方法、装置和系统
CN109818868B (zh) * 2017-11-20 2021-06-22 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
CN110753335B (zh) * 2018-07-24 2023-04-07 中兴通讯股份有限公司 信息传输方法、设备及计算机可读存储介质
CN110545307B (zh) * 2019-07-19 2022-09-27 中移（杭州）信息技术有限公司 边缘计算平台、调用方法及计算机可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110169089A (zh) * 2017-01-05 2019-08-23 华为技术有限公司 用于应用友好型协议数据单元会话管理的系统和方法
WO2019194954A1 (fr) * 2018-04-06 2019-10-10 Convida Wireless, Llc Procédés de gestion de connexions à un réseau de données local (ladn) dans un réseau 5g
CN109408197A (zh) * 2018-09-29 2019-03-01 上海理想信息产业（集团）有限公司 一种边缘计算引擎的实现方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System (5GS) Location Services (LCS); Stage 2 (Release 16)", 3GPP TS 23.273 V16.2.0, 22 December 2019 (2019-12-22), XP051840918 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113783882A (zh) * 2021-09-16 2021-12-10 恒安嘉新（北京）科技股份公司 一种边缘应用的信息获取方法、装置、电子设备及介质
CN113783882B (zh) * 2021-09-16 2023-07-07 恒安嘉新（北京）科技股份公司 一种边缘应用的信息获取方法、装置、电子设备及介质

Also Published As

Publication number Publication date
CN113259930A (zh) 2021-08-13

Similar Documents

Publication Publication Date Title
WO2021159891A1 (fr) Procédé de traitement de demande, d'interrogation et d'autorisation pour un appel, dispositifs, appareil et support
WO2020220865A1 (fr) Procédé de vérification d'identité pour service de fonction de réseau, et dispositif associé
US11997491B2 (en) Data transmission system and method, and apparatus thereof
WO2019196813A1 (fr) Procédé et dispositif d'abonnement à un service
JP2023162188A (ja) ブルートゥーススキャン方法および電子デバイス
CN107784221B (zh) 权限控制方法、服务提供方法、装置、系统及电子设备
CN113746777B (zh) 安全访问数据的方法及电子设备
TWI700957B (zh) 一種確定建立原因的方法和終端
US10798570B2 (en) Terminal authentication method and device
WO2009092315A1 (fr) Procédé d'accès à un réseau personnel sans fil
JP2020506629A (ja) ルーティング方法および装置
WO2019024744A1 (fr) Procédé et dispositif d'acquisition d'identifiant de dispositif terminal
US20200367054A1 (en) Systems and methods for remote device security attestation and manipulation detection
US20230232228A1 (en) Method and apparatus for establishing secure communication
WO2022027528A1 (fr) Procédé d'appel d'interface de programmation d'application, ainsi que dispositif et système associés
US20230300622A1 (en) Communication system, communication method, and communication apparatus
WO2020201051A1 (fr) Procédés et appareil permettant une protection de données de bout en bout
WO2016131250A1 (fr) Procédé, appareil et système de partage de ressources
US12047780B2 (en) Authorization in cellular communication systems
US20210385088A1 (en) Network access method, user equipment, network entity, and storage medium
US20230319907A1 (en) Device with Two Communication Devices
WO2020220937A1 (fr) Procédé et dispositif de gestion de politique de sécurité
WO2023143554A1 (fr) Procédé et dispositif d'établissement de pin
WO2023184548A1 (fr) Procédé et appareil de traitement d'informations, dispositif de communication et support de stockage
WO2024031399A1 (fr) Procédé et appareil permettant à un ue de rejoindre un pin, et dispositif de communication et support de stockage

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: 21753105

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21753105

Country of ref document: EP

Kind code of ref document: A1