Business control method, device, equipment, medium and product

Abstract

Provided are a service control method, apparatus, device, medium and product, the method comprising: performing identity registration on a service terminal, and generating context information according to an identity registration message, the context information comprising a network terminal identity and a user identity; determining a plurality of service terminals with an identity association relationship according to the context information, wherein the identity association relationship comprises a relationship with the same user identity or a relationship with the same network terminal identity; generating a service strategy rule for the plurality of service terminals with the identity association relationship; and sending the service to the plurality of service terminals according to the context information so as to realize service linkage among the plurality of service terminals. Through the embodiment of the invention, not only can a plurality of service terminals of the same user be identified, but also different users associated with the same service terminal can be identified, network linkage among the plurality of service terminals is realized, and the reliability and timeliness of network service interaction are improved.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present disclosure is a divisional application of an application with an application date of 2024-07-24, an application number of 2024110014076, and an invention name of “Business Control Method, Device, Equipment, Medium and Product”. The entire contents of the parent case are incorporated herein by reference. Background Art

[0004] At present, with the development of communication technology, a user usually has several devices and needs personal services to be coordinated among several devices. On the one hand, similar service requirements traditionally rely on the application layer to implement multi-service terminal coordination or information synchronization, and lack network linkage solutions to ensure service performance. On the other hand, the next generation network needs to meet the needs of wide-area ubiquitous connectivity. Service terminal cascading is an effective way to extend coverage. Downstream service terminal devices may not have SIM cards, and the service requirements of multiple downstream devices may be the same or different. The current network control mechanism cannot accurately distinguish and control.

[0005] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0006] The purpose of the present disclosure is to provide a service control method, apparatus, device, medium and product, which are used to overcome the problem of lack of network linkage between multiple service terminals of the same user due to limitations and defects of related technologies, at least to a certain extent.

[0007] According to a first aspect of an embodiment of the present disclosure, a service control method is provided, which is applicable to a core network element, and the service control method includes: registering an identity of a service terminal, and generating context information according to a message of the identity registration, wherein the context information includes a network terminal identity and a user identity;

[0008] Determining, according to the context information, a plurality of service terminals having an identity association relationship, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity;

[0009] The service is sent to the multiple service terminals according to the context information, so as to realize the service linkage among the multiple service terminals.

[0010] In an exemplary embodiment of the present disclosure, sending the service to the plurality of service terminals according to the context information to achieve service linkage between the plurality of service terminals includes:

[0011] Generating a service policy rule for a plurality of service terminals having an identity association relationship according to the context information;

[0012] The service is sent to the multiple service terminals according to the service policy rules to achieve service linkage among the multiple service terminals.

[0013] In an exemplary embodiment of the present disclosure, performing identity registration on a service terminal and generating context information according to a message of the identity registration includes:

[0014] Registering a network terminal identity for the first service terminal and establishing a user plane connection;

[0015] Registering a user identity based on a user plane connection corresponding to the first service terminal, and storing context information of the user identity corresponding to the first service terminal;

[0016] Registering the network terminal identity for the second service terminal and establishing a user plane connection;

[0017] triggering the third service terminal to register a user identity based on the user plane connection corresponding to the second service terminal, and storing context information of the user identity corresponding to the third service terminal,

[0018] The first service terminal and the third service terminal are a plurality of service terminals having the user association relationship.

[0019] In an exemplary embodiment of the present disclosure, sending the service to the plurality of service terminals according to the service policy rule includes:

[0020] Identify attribute information of the service corresponding to the service request;

[0021] Determine a service policy rule corresponding to the attribute information, and forward the service to the plurality of service terminals based on the service policy rule.

[0022] In an exemplary embodiment of the present disclosure, generating a service policy rule for a plurality of service terminals having an identity association relationship includes:

[0023] Determining, according to the context information, that the first service terminal and the third service terminal have the identity association relationship;

[0024] aggregating the context information of the first service terminal and the context information of the third service terminal;

[0025] The business policy rule is generated according to the aggregated context information, and the business policy rule includes at least one of a group communication rule, a message synchronization rule, and a task collaboration rule.

[0026] In an exemplary embodiment of the present disclosure, determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule includes:

[0027] receiving a service request from a first service terminal among the plurality of service terminals;

[0028] Determining, according to the attribute information of the service request, that the service requested by the first service terminal is a self-group service;

[0029] Determine a group communication rule in the service policy rule corresponding to the self-group service;

[0030] The data of the self-group service is fed back to the third service terminal according to the group communication rule.

[0031] In an exemplary embodiment of the present disclosure, determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule further includes:

[0032] Responding to traffic sent to a designated user from outside the network;

[0033] Determining, according to the attribute information of the service, that the services of the plurality of service terminals are cross-service terminal synchronization services;

[0034] Determine a message synchronization rule in the service policy rule corresponding to the cross-service terminal synchronization service;

[0035] The service is replicated according to the message synchronization rule and fed back to the multiple service terminals.

[0036] In an exemplary embodiment of the present disclosure, determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule further includes:

[0037] Responding to the collaborative task service issued to the designated user;

[0038] Determining, according to the attribute information of the collaborative task service, a task collaboration rule in the service policy rule corresponding to the collaborative task service;

[0039] The tasks are arranged and processed according to the task cooperation rules, and the multiple tasks after the arrangement and processing are sent to the multiple service terminals respectively.

[0040] According to a second aspect of an embodiment of the present disclosure, a service control method is provided, which is applicable to a core network element. The service control method includes:

[0041] In response to registration information sent by the card-not-present service terminal to the network, generating context information of the card-not-present service terminal according to the registration information, the context information including the identity of the card-not-present service terminal, the network terminal identity associated with the D2D connection peer, the service policy rules and network address of the card-not-present service terminal;

[0042] The control plane network element in the core network network element sends the service policy rule to the card-not-present service terminal and the user plane network element according to the context information, and the network performs service control on the card-not-present service terminal based on the service policy rule;

[0043] The user plane network element in the core network network element receives the traffic data fed back by the cardless service terminal via the D2D connection, and the traffic data meets the constraints of the service policy rules.

[0044] In an exemplary embodiment of the present disclosure, the network address is allocated by a card-carrying network terminal from a network address segment allocated by the network to a communication address of a cardless business terminal with which a network terminal association relationship exists. The business terminals with which the network terminal association relationship exists are multiple business terminals that access the Internet through a D2D connection of the same network terminal.

[0045] In an exemplary embodiment of the present disclosure, it further includes:

[0046] The control plane network element determines the network terminal association relationship of the card-free service terminal of the sender of the flow data according to the network address;

[0047] The user plane network element performs data exchange with the card-free service terminal according to the service policy rule, and feeds back the flow data to the connection management network element.

[0048] In an exemplary embodiment of the present disclosure, before generating the context information of the card-not-present service terminal according to the registration information of the card-not-present service terminal, the method further includes:

[0049] The card-presence network terminal performs network terminal identity registration and user identity registration;

[0050] In response to a user identity registration request from a card-not-present service terminal, the card-present network terminal establishes a user plane connection as a network terminal;

[0051] Receiving a user identity registration request initiated by the card-not-present service terminal, the registration request including the identity identifier and authentication information;

[0052] Performing an authorization authentication result on the card-not-present service terminal based on the authentication information, and feeding back the authorization authentication result to the card-not-present service terminal as a response of successful registration;

[0053] The discovery management network element in the core network network element determines the connection management network element corresponding to the session according to the network address;

[0054] The discovery management network element is triggered to synchronize the registration information of the card-not-present service terminal to the connection management network element, and the connection management network element generates context information of the card-not-present service terminal.

[0055] In an exemplary embodiment of the present disclosure, the user identity registration request is transmitted to the core network element based on a D2D connection between the card-not-present service terminal and the card-present network terminal.

[0056] In an exemplary embodiment of the present disclosure, the D2D connection is a connection between the card-present network terminal and / or the card-not-present service terminal established in response to a networking request.

[0057] In an exemplary embodiment of the present disclosure, the network address is used to determine a network terminal association relationship between the card-present network terminal and the card-not-present service terminal.

[0058] In an exemplary embodiment of the present disclosure, the networking request is initiated by the card-free service terminal to the network via a card-present network terminal having a network terminal association relationship.

[0059] According to a third aspect of an embodiment of the present disclosure, a service control device is provided, which is applicable to a core network element, and the service control device includes:

[0060] A registration module, configured to register the identity of the service terminal and generate context information according to the identity registration message, wherein the context information includes the network terminal identity and the user identity;

[0061] A determination module, configured to determine a plurality of service terminals having an identity association relationship according to the context information, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity;

[0062] The interaction module is configured to send the service to the plurality of service terminals according to the context information.

[0063] According to a fourth aspect of an embodiment of the present disclosure, a service control device is provided, which is applicable to a core network element, and the service control device includes:

[0064] A determination module, configured to generate context information of the card-free service terminal in response to registration information sent by the card-free service terminal to the network according to the registration information, wherein the context information includes an identity identifier of the card-free service terminal, a network terminal identifier associated with the D2D connection peer, a service policy rule of the card-free service terminal, and a network address;

[0065] A sending module, configured to be a control plane network element in the core network element to send the service policy rules to the user plane network element and the card-free service terminal respectively according to the context information;

[0066] The receiving module is configured to receive, as the user plane network element, the flow data fed back by the card-free service terminal via the D2D connection, wherein the flow data satisfies the constraints of the service policy rules.

[0067] According to a fifth aspect of the present disclosure, an electronic device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor executes any one of the methods described above based on instructions stored in the memory.

[0068] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided, on which a program is stored, and when the program is executed by a processor, the service control method as described in any one of the above items is implemented.

[0069] According to a seventh aspect of the present disclosure, there is provided a computer program product, comprising a computer program, characterized in that when the computer program is executed by a processor, the service control method as described in any one of the above is implemented.

[0070] Based on the embodiment of the present disclosure, by performing identity registration on the service terminal and generating context information based on the identity registration message, and then determining the service policy rules of multiple service terminals based on the context information, based on this, the attribute information of the service corresponding to the service request is identified, and the service is forwarded to multiple service terminals based on the attribute information. Not only can multiple service terminals of the same user be identified, but also different users associated with the same service terminal can be identified. The network can directly perform service control on the cardless service terminal, and expands the functions of group communication, service collaboration and information synchronization between multiple service terminals, realizes network linkage between multiple service terminals, and improves the reliability and timeliness of network service interaction.

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

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

[0073] Figure 1A schematic diagram showing an exemplary system architecture to which the service control solution of an embodiment of the present invention can be applied;

[0074] Figure 2 is a flow chart of a service control method in an exemplary embodiment of the present disclosure;

[0075] Figure 3 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0076] Figure 4 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0077] Figure 5 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0078] Figure 6 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0079] Figure 7 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0080] Figure 8 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0081] Fig. 9 is a flow chart of another service control method in an exemplary embodiment of the present disclosure;

[0082] Fig.10 It is a schematic diagram of the architecture of a service control solution in the prior art;

[0083] Fig.11 It is a schematic diagram of the architecture of another service control solution in the prior art;

[0084] Fig.12 is a schematic diagram of the architecture of a service control solution in an exemplary embodiment of the present disclosure;

[0085] Fig.13 is an interactive schematic diagram of a service control solution in an exemplary embodiment of the present disclosure;

[0086] Fig.14 is an interactive schematic diagram of another service control solution in an exemplary embodiment of the present disclosure;

[0087] Fig.15 is a block diagram of a service control device in an exemplary embodiment of the present disclosure;

[0088] Fig.16 is a block diagram of another service control device in an exemplary embodiment of the present disclosure;

[0089] Fig.17 is a block diagram of an electronic device in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

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

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

[0092] The technical terms involved in the embodiments of the present disclosure are explained as follows:

[0093] Network terminal identity: a type of identity information tightly coupled with a network service terminal, similar to SUPI (User Permanent Identity) or SUCI (User Encrypted Identity) in 5G networks. In this disclosure, a network service terminal has a network terminal identity, but a service terminal does not necessarily have a network terminal identity, such as a cardless service terminal; when a cardless remote service terminal accesses the Internet through a common layer 3 relay, the remote service terminal is a service terminal, but not a network service terminal, and does not have a network terminal identity.

[0094] User identity: Identity information related to a specific business user, with social attributes, such as the identity information of a specific person, also called user individual identity. An entity with a user identity can have multiple network service terminals or business service terminals. The user identity and network terminal identity can be in a 1:n relationship.

[0095] User plane network element: Similar to the user plane function (UPF) of the 5G core network, it executes user plane policies, including traffic identification and forwarding at various levels, as well as various other processing network functions.

[0096] Connection management network element: Similar to the session management function (SMF) network element of the 5G core network control plane, in the present disclosure, this network element not only performs session management (SMF function) of the network terminal identity entity (network service terminal), but is also responsible for the connection management of the user's individual identity entity, and stores the user context to control the forwarding path at the user level (such as the flow level).

[0097] Discovery management network element: In the near-domain discovery scenario, the network element assists in the discovery of neighboring service terminals, similar to the DDNMF (Direct Discovery Name Management Function) in 5G proximity services; in some user authentication scenarios, this network element can perform the function of accessing the security gateway and perform intermediate calculations and verification functions in the user authentication process.

[0098] Contract signing and authentication network element: It stores user contract information and performs server-side functions of user authentication based on the contract information. For network terminal identity authentication, this type of network element performs functions similar to 5G AUSF / UDM; for user identity authentication, this network element is compatible with multiple authentication methods, such as AAA authentication or application layer authentication; this network element can also perform functions similar to 5GPCF, that is, it has policy contract signing functions.

[0099] UE: User Equipment, a terminal for accessing a mobile network. In the present disclosure, it represents a network service terminal, that is, a network terminal identity carrier for accessing a mobile network.

[0100] DN: Data Network, the network behind the mobile network user plane anchor point, usually refers to the application deployment environment.

[0101] Figure 1 A schematic diagram showing an exemplary system architecture to which the service control solution of an embodiment of the present invention can be applied is shown.

[0102] like Figure 1 As shown, the system architecture 100 may include one or more of service terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the service terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0103] It should be understood that Figure 1The number of service terminal devices, networks and servers in the embodiment is only for illustration. Any number of service terminal devices, networks and servers may be provided according to the implementation requirements. For example, the server 105 may be a server cluster composed of multiple servers.

[0104] Users can use service terminal devices 101, 102, 103 to interact with server 105 via network 104 to receive or send messages, etc. Service terminal devices 101, 102, 103 can be various electronic devices with display screens, including but not limited to smartphones, tablet computers, portable computers, desktop computers, etc.

[0105] In some embodiments, the service control method provided in the embodiments of the present invention is generally executed by the server 105. Accordingly, the service control device is generally arranged in the service terminal device 103 (or the service terminal device 101 or 102). In other embodiments, some service terminals may have functions similar to those of the server device to execute the method.

[0106] The exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0107] Figure 2 is a flow chart of a service control method in an exemplary embodiment of the present disclosure.

[0108] refer to Figure 2 , the service control method may include:

[0109] Step S202: register the identity of the service terminal and generate context information according to the identity registration message, wherein the context information includes the network terminal identity and the user identity.

[0110] Step S204: determining a plurality of service terminals having an identity association relationship according to the context information, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity.

[0111] Step S206: sending the service to the plurality of service terminals according to the context information, so as to realize service linkage among the plurality of service terminals.

[0112] Based on the embodiment of the present disclosure, by performing identity registration on the service terminal and generating context information based on the identity registration message, the service policy rules of the multiple service terminals are determined based on the context information. Based on this, the attribute information of the service corresponding to the service request is identified, and the service is forwarded to the multiple service terminals based on the attribute information. This expands the functions of group communication, service collaboration, and information synchronization between the multiple service terminals, realizes network linkage between the multiple service terminals, and improves the reliability and timeliness of network service interaction.

[0113] In an exemplary embodiment of the present disclosure, the service includes service flow data, control signaling, protocol messages, etc., but is not limited thereto.

[0114] The following describes each step of the service control method in detail.

[0115] In an exemplary embodiment of the present disclosure, sending the service to the plurality of service terminals according to the context information to achieve service linkage between the plurality of service terminals includes:

[0116] Generating a service policy rule for a plurality of service terminals having an identity association relationship according to the context information;

[0117] The service is sent to the multiple service terminals according to the service policy rules to achieve service linkage among the multiple service terminals.

[0118] In an exemplary embodiment of the present disclosure, Figure 3 As shown, registering the identity of the service terminal and generating context information according to the identity registration message includes:

[0119] Step S302: register the network terminal identity for the first service terminal and establish a user plane connection.

[0120] Step S304: registering a user identity based on the user plane connection corresponding to the first service terminal, and storing context information of the user identity corresponding to the first service terminal.

[0121] Step S306: register the network terminal identity for the second service terminal and establish a user plane connection.

[0122] Step S308: triggering the third service terminal to register a user identity based on the user plane connection corresponding to the second service terminal, and storing context information of the user identity corresponding to the third service terminal, wherein the first service terminal and the third service terminal are multiple service terminals having the identity association relationship.

[0123] In an exemplary embodiment of the present disclosure, the second service terminal may be used as a network terminal to create a user plane connection, and the third service terminal is equivalent to the second service terminal, or is a subordinate device of the second service terminal, but is not limited thereto.

[0124] In an exemplary embodiment of the present disclosure, context information of multiple service terminals is maintained through a form as shown in Table 1.

[0125] Table 1

[0126]

[0127] In an exemplary embodiment of the present disclosure, the GBR (Guaranteed Bit Rate) in Table 1 refers to a guaranteed bit rate. Even when network resources are tight, the corresponding bit rate can be maintained, that is, the guaranteed minimum bandwidth.

[0128] In an exemplary embodiment of the present disclosure, Figure 4 As shown, sending the service to the plurality of service terminals according to the service policy rule includes:

[0129] Step S402: Identify attribute information of the service corresponding to the service request.

[0130] Step S404: determine the service policy rule corresponding to the attribute information, and forward the service to the multiple service terminals based on the service policy rule.

[0131] In an exemplary embodiment of the present disclosure, Figure 5 As shown, generating a service policy rule for multiple service terminals having identity association relationships includes:

[0132] Step S502: Determine, according to the context information, whether the first service terminal and the third service terminal have the identity association relationship.

[0133] Step S504: Aggregate the context information of the first service terminal and the context information of the third service terminal.

[0134] Step S506: Generate the business policy rule according to the aggregated context information, wherein the business policy rule includes at least one of a group communication rule, a message synchronization rule and a task collaboration rule.

[0135] In an exemplary embodiment of the present disclosure, the self-group service is the interaction of services between multiple service terminals.

[0136] In an exemplary embodiment of the present disclosure, Figure 6 As shown, determining the service policy rule corresponding to the attribute information, and forwarding the service to the multiple service terminals based on the service policy rule includes:

[0137] Step S602: receiving a service request from a first service terminal among the multiple service terminals.

[0138] Step S604: determining, according to the attribute information of the service request, that the service requested by the first service terminal is a self-group service.

[0139] Step S606: Determine the group communication rule in the service policy rule corresponding to the self-group service.

[0140] Step S608: Feedback the data of the self-group service to the third service terminal according to the group communication rule.

[0141] In an exemplary embodiment of the present disclosure, Figure 7 As shown, determining the service policy rule corresponding to the attribute information, and forwarding the service to the multiple service terminals based on the service policy rule also includes:

[0142] Step S702, responding to a service sent to a designated user from outside the network.

[0143] Step S704: determining, according to the attribute information of the service, that the services of the plurality of service terminals are cross-service terminal synchronization services.

[0144] Step S706: determine a message synchronization rule in the service policy rule corresponding to the cross-service terminal synchronization service.

[0145] Step S708: copy the service according to the message synchronization rule and feed back to the multiple service terminals.

[0146] In an exemplary embodiment of the present disclosure, the identity of a specified user can determine the corresponding user identity based on context information, and further determine a service terminal having the same user identity, that is, a service terminal having an identity association relationship.

[0147] In an exemplary embodiment of the present disclosure, Figure 8 As shown, determining the service policy rule corresponding to the attribute information, and forwarding the service to the multiple service terminals based on the service policy rule also includes:

[0148] Step S802, responding to the collaborative task service sent to the designated user.

[0149] In an exemplary embodiment of the present disclosure, the identity of a specified user can determine the corresponding user identity based on context information, and further determine a service terminal having the same user identity, that is, a service terminal having an identity association relationship.

[0150] Step S804: determining the task collaboration rule in the service policy rule corresponding to the collaborative task service according to the attribute information of the collaborative task service.

[0151] Step S806: orchestrate the tasks according to the task collaboration rule, and send the multiple tasks after the orchestration to the multiple terminals respectively.

[0152] In an exemplary embodiment of the present disclosure, a cross-service terminal synchronization service is a service that synchronizes data sent by other users to at least one service terminal among multiple service terminals in real time to other service terminals among the multiple service terminals.

[0153] Fig. 9 is a flow chart of a service control method in an exemplary embodiment of the present disclosure.

[0154] refer to Fig. 9 , the service control method includes:

[0155] Step S902, in response to the registration information sent by the cardless service terminal to the network, generate the context information of the cardless service terminal according to the registration information, the context information including the identity of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the cardless service terminal business policy rules and network address.

[0156] Step S904: The control plane network element in the core network network element sends the service policy rules to the user plane network element and the card-not-present service terminal respectively according to the context information, and the network performs service control on the card-not-present service terminal based on the service policy rules.

[0157] Step S906: The user plane network element in the core network network element receives the traffic data fed back by the cardless service terminal via the D2D connection, and the traffic data meets the constraints of the service policy rules.

[0158] In an exemplary embodiment of the present disclosure, the network address is a network address in a terminal address segment assigned by the card-carrying network terminal to a communication address of a card-free service terminal with a network terminal association relationship, and the service terminals with the network terminal association relationship are multiple service terminals connected to the Internet through a D2D connection of the same network terminal.

[0159] In an exemplary embodiment of the present disclosure, the control plane network element includes a discovery management network element, a connection management network element, a subscription and authentication network element, etc., but is not limited thereto.

[0160] In an exemplary embodiment of the present disclosure, based on the technical solution defined in the above steps S902 to S906, in a scenario where multiple cardless business terminal devices are hung under a network business terminal, specific end users can also be distinguished and precisely controlled based on the match with the user context, that is, by introducing the user identity and the network terminal identity, the network user group can be expanded, which is in line with the development trend of ubiquitous connectivity in mobile networks. At the same time, the network's inherent user identification capabilities can be used to provide users with value-added services across business terminals, thereby achieving maximum added value for the communication network.

[0161] In an exemplary embodiment of the present disclosure, it further includes:

[0162] The control plane network element (i.e., connection management network element) determines the network terminal association relationship of the card-free service terminal of the sender of the flow data according to the network address;

[0163] The user plane network element performs data exchange with the card-free service terminal according to the service policy rule, and feeds back the flow data to the connection management network element.

[0164] In an exemplary embodiment of the present disclosure, before generating the context information of the card-not-present service terminal according to the registration information of the card-not-present service terminal, the method further includes:

[0165] The card-presence network terminal performs network terminal identity registration and user identity registration;

[0166] In response to a user identity registration request from a card-not-present service terminal, the card-present network terminal establishes a user plane connection as a network terminal;

[0167] Performing an authorization authentication result on the card-not-present service terminal based on the authentication information, and feeding back the authorization authentication result to the card-not-present service terminal as a response of successful registration;

[0168] The discovery management network element in the core network network element determines the discovery connection management network element corresponding to the session according to the network address;

[0169] The discovery management network element is triggered to synchronize the registration information of the card-not-present service terminal to the connection management network element, and the connection management network element generates context information of the card-not-present service terminal.

[0170] In an exemplary embodiment of the present disclosure, the user identity registration request is transmitted to the core network element based on a D2D connection between the card-not-present service terminal and the card-present network terminal.

[0171] In an exemplary embodiment of the present disclosure, the D2D connection is a connection between the card-present network terminal and / or the card-not-present service terminal established in response to a networking request.

[0172] In an exemplary embodiment of the present disclosure, the network address is used to determine a network terminal association relationship between the card-present network terminal and the card-not-present service terminal.

[0173] In an exemplary embodiment of the present disclosure, the networking request is initiated by the card-free service terminal to the network via a card-present network terminal having a network terminal association relationship.

[0174] Combine the following Fig.10 and Fig.11 The description architecture of multiple terminals of the same user in the prior art is described.

[0175] like Fig.10 As shown, in an architecture 1000 of a service control solution in the prior art, when user 1 has terminals UE-A and UE-B at the same time, UE-A and UE-B are regarded as two different users, and terminal UE3 is a terminal of other users. Even if the same user logs in to two terminals, the service synchronization and coordination between them can only rely on the service platform outside the 5G5 network for control.

[0176] like Fig.11 As shown, in the architecture 1100 of a service control solution in the prior art, the cardless service terminal D (user 3) is connected to the Internet through the terminal C (user 2) and UE-A (user 1) in the form of a layer 3 relay connection, and the terminal E (user 5) is connected to the Internet through the terminal B (user 4). The network cannot perceive the users downstream of the terminal UE-A and the users downstream of the terminal UE-B, that is, the 5G5 network performs service control in the identity of the terminal UE-A (that is, user 1) and the identity of the terminal UE-B.

[0177] Based on the existing technology, it is known that a terminal identifier is equivalent to a user identity, and it is impossible to realize the linkage of services of the same individual user using different terminals, and it is impossible to distinguish and independently control different service devices connected to the terminal, that is, it is impossible to identify the end user.

[0178] In view of the defects in the above-mentioned prior art, Fig.12 As shown, the present disclosure proposes a new service control framework 1200, which aims to solve the control and service shortcomings caused by the above user identity being equal to the network terminal identity.

[0179] In the service control framework 1200, firstly, a user identity is introduced and used as a user access parameter. The user identity corresponds to an individual user with a social identity.

[0180] Secondly, after the terminal with the network terminal identity (SIM card) performs network registration, it performs registration at the user identity level (if acting as a relay, it and each downstream terminal perform registration separately).

[0181] like Fig.12 As shown, after UE-A performs network registration of the network terminal identity, user 2 (the service terminal is terminal C) and user 1 (the service terminal is UE-A) respectively perform user identity registration, user 3 (the service terminal is terminal B) and user 4 (the service terminal is terminal E) respectively perform user identity registration, and establish user context in the network. In the subsequent business process, user 2 (UE-C) interacts with the mobile network as an independent terminal.

[0182] In an exemplary embodiment of the present disclosure, the user context includes a user identity associated with a specific user, a network address assigned to its service terminal by a network or upstream device, a service control policy related to the user, and an associated network terminal identity, but is not limited thereto.

[0183] In an exemplary embodiment of the present disclosure, no matter the service terminal used by the user is the network terminal for this connection or a downstream terminal of the locally connected network terminal, the associated network terminal identity is the network identity of the network terminal for this connection.

[0184] Fig.12 An example of a corresponding user context is shown in Table 2, where the service control policy of user 2 is consistent when using different service terminals. Based on the user context, the network can identify the services of the same user from different terminals, or different or the same users under one terminal, so that the services of the same user from different service terminals can be associated for processing, such as data synchronization, service collaboration, distributed processing and aggregation of data, etc., but not limited to this. For scenarios where multiple cardless service terminal devices are connected to a network terminal, specific end users can also be distinguished and precisely controlled based on the match with the user context.

[0185] Table 2

[0186]

[0187] As shown in Table 2, the mobile network analyzes the traffic from IP2 and IP3 based on the context and finds that both traffic from IP2 and IP3 are from user 2. The mobile network can further identify the traffic from the same application from these traffic. The mobile network can also accurately identify the traffic from IP5 as from user 4 based on the context to distinguish it from the traffic from user 3 from the UE-B session.

[0188] In an exemplary embodiment of the present disclosure, the user identity identification code and the authentication method of the user identity registration process are not limited by the present disclosure. Under the security mechanism of network terminal identity authentication, the authentication of user identity can be compatible with multiple authentication methods, such as AAA authentication, or even any authentication method at the application layer. In addition, in order to support control based on user identity, it is necessary to sign a service policy for user identity in the network and retain it in the signing and authentication network element. The authentication of user identity is associated with the service terminal, so there can be multiple registrations in the case of multiple terminals, and the registration information does not conflict, that is, multiple registration information can be saved.

[0189] In an exemplary embodiment of the present disclosure, Fig.13As shown, a service control solution is provided, and the process of implementing network control multi-terminal linkage service based on user plane network element 1302, connection management network element 1304, contract and authentication network element 1306, UE1 1308 (user 1), UE2 1310 (user 1) and DN 1312 includes:

[0190] 1a. UE1 1308 completes the registration of the traditional network terminal identity and establishes a user plane connection (ie, session) under the control of the network. The network terminal identity is such as IMSI for 4G, SUPI or SUCI for 5G, etc.

[0191] 2a. UE1 1308 is the service terminal of user 1. Therefore, after UE1 1308 completes the network terminal identity registration, user 1 performs user identity registration, and the connection management network element 1304 saves the user identity context, which includes the identity of user 1, the network address of UE1 1308, the network terminal identity of UE1 1308, etc.

[0192] 1b. Similar to 1a, UE2 1310 completes the registration of the traditional network terminal identity and establishes a user plane connection (ie, session) under the control of the network.

[0193] 2b. UE2 1310 is also the service terminal of user 1. Therefore, after UE2 1310 completes the network terminal identity registration, user 1 performs user identity registration again on the connection of UE2 1310. The connection management network element 1304 adds new information to the original user context of user 1.

[0194] 3. The connection management network element 1304 determines that user 1 uses terminals UE1 1308 and UE2 1310 at the same time based on context matching, so it aggregates the two contexts of user 1 and generates service policy rules for the user identity of user 1 (such as execution rules related to group communication, message synchronization, task collaboration, etc.).

[0195] 4. The connection management network element 1304 sends corresponding service policy rules to each service terminal and related user plane network element 1302 respectively.

[0196] 5a to 7a are the processes of implementing self-group services between different service terminals of the same user.

[0197] 5a. User 1 uses UE2 1310 to initiate a self-group service, the target of which is other service terminals of the user.

[0198] 6a. The user plane network element 1302 executes the service policy rule, identifies that the message is a user group service, and determines that it needs to be forwarded to UE1 1308.

[0199] 7a. The user plane network element 1302 forwards the group service to UE1 1308.

[0200] 5b to 8b are the processes of implementing message synchronization services between different service terminals of the same user.

[0201] 5b. The mobile network receives a message sent to UE1 1308 from the outside (DN 1312).

[0202] 6b. The user-plane network element 1302 executes the service policy rules, identifies that the message is a cross-terminal synchronization service, determines that it needs to be forwarded to other terminals of user 1, and therefore copies the message.

[0203] 7b. The user plane network element 1302 forwards a message to UE1 1308.

[0204] 8b. The user plane network element 1302 forwards another message to UE2 1310.

[0205] like Fig.14 As shown, the present disclosure provides a service control solution in a three-layer relay networking scenario, based on a cardless service terminal 1402 (user 2), UE1 1404 (user 1), a user plane network element 1406, a connection management network element 1408, a discovery management network element 1410, and a contract and authentication network element 1414, wherein UE1 1404 is a service terminal of user 1, and at the same time, as a layer 3 relay, provides a relay Internet access service for the cardless service terminal 1402, and the cardless service terminal 1402 is a service terminal of user 2. The process of realizing network control of multi-terminal linkage services includes:

[0206] 1. UE1 1404 completes network terminal identity registration, establishes UE1 1404 initial session, and then completes user identity registration as user 1.

[0207] 2. The cardless service terminal 1402 initiates a discovery request, indicating the need for Internet connection, and discovers and selects UE1 1404 as the third Internet layer relay.

[0208] 3. UE1 1404 allocates a network address to the cardless service terminal 1402, and the cardless service terminal 1402 establishes an end-to-end communication connection with UE1 1404. If UE1 1404 has not established a relay-dedicated session before, UE1 1404 establishes a dedicated bearer channel for all downstream users.

[0209] 4. The cardless service terminal 1402 initiates a user identity registration request through the dedicated channel of UE1 1404 , and this request is sent to the discovery management network element 1410 .

[0210] 5. The discovery management network element 1410 serves as the access security gateway network element of the cardless service terminal 1402 , assists the contract signing and authentication network element 1414 in completing the authentication of the user, and obtains the contract signing information of the user identity from the contract signing and authentication network element 1414 .

[0211] 6. The discovery management network element 1410 replies a registration success message to the card-free service terminal 1402.

[0212] 7. The discovery management network element 1410 discovers the connection management network element 1408 corresponding to the session with UE1 1404 according to the IP network address in the registration request message of the card-free service terminal 1402 .

[0213] 8. The discovery management network element 1410 synchronizes the information of user 2 to the connection management network element 1408, including the network address of the cardless service terminal 1402, the user identity contract information in step 5, etc.

[0214] 9. The connection management network element 1408 generates user context information of user 2, which includes the user identity of the cardless service terminal 1402 (ie user 2), the network terminal identity of UE1 1404, the terminal address of user 2, the service policy rules of the user identity of user 2, etc.

[0215] 10. The connection management network element 1408 sends service policy rules to the card-free service terminal 1402.

[0216] 11. The connection management network element 1408 sends service policy rules to the relevant user plane network elements 1406. This step and step 10 are performed in no particular order.

[0217] 12. The traffic of user 2 is transmitted to the user plane network element 1406 through the D2D connection of UE1 1404.

[0218] 13. The user plane network element 1406 identifies the traffic of user 2 according to the terminal network address and executes the corresponding service policy rules.

[0219] 14. When the conditions are met, the user plane network element 1406 reports the traffic status of user 2 to the connection management network element 1408.

[0220] In an exemplary embodiment of the present disclosure, some details and technical extensions of the technical solution are also provided:

[0221] (1) To support user identity-based control, it is necessary to sign up for user identity-based service policies in the network and keep them in the signing and authentication network elements;

[0222] (2) User identity authentication is associated with the service terminal, so multiple registrations can be made in the case of multiple terminals, and the registration information does not conflict, that is, multiple registration information can be saved;

[0223] (3) User identity authentication can be compatible with multiple authentication methods, such as AAA authentication, or even any authentication method at the application layer.

[0224] (4) The network element that acts as a user identity registration intermediary is not necessarily the DDNMF, but because the DDNMF can participate in the discovery between terminals and can perceive the access topology to a certain extent, it is more suitable to assume this responsibility.

[0225] (5) The signing and authentication network elements may be multiple network elements during actual design or deployment.

[0226] In an exemplary embodiment of the present disclosure, in view of the lack of control mechanism and service flexibility caused by the tight coupling of existing network user identities and terminal devices, the present disclosure also proposes a mobile network service control method based on user identities, the method comprising:

[0227] (1) Introduce user identity and use user identity as a user access parameter. User identity corresponds to an individual user with a social identity.

[0228] (2) After the terminal with the network terminal identity (SIM card) performs network registration, it performs registration at the user identity level (if acting as a relay, it and each downstream terminal register separately) and establishes a user context.

[0229] In an exemplary embodiment of the present disclosure, the user context includes, but is not limited to, a user identity associated with the user, a network address assigned by a network or upstream device to its service terminal, a service control policy related to the user, and an associated network terminal identity.

[0230] (3) Based on the user context, the network can identify the services of the same user from different terminals, or different or the same users under one terminal, so that the services of the same user from different service terminals can be associated for processing (such as data synchronization, service collaboration, distributed processing and aggregation of data, etc.).

[0231] (4) In the scenario where a network terminal is connected to multiple cardless service terminal devices, the specific end user can be distinguished and precisely controlled based on the matching with the user context.

[0232] The above embodiment expands the network user group by introducing user identity and network terminal identity, which is in line with the development trend of ubiquitous connection of mobile networks. At the same time, it provides users with cross-terminal value-added services through the network's inherent user identification capabilities, thereby achieving maximum value-added of the network.

[0233] Corresponding to the above method embodiments, the present disclosure also provides a service control device, which can be used to execute the above method embodiments.

[0234] Fig.15 It is a block diagram of a service control device in an exemplary embodiment of the present disclosure.

[0235] refer to Fig.15 , the service control device 1500 may include:

[0236] The registration module 1502 is configured to register the identity of the service terminal and generate context information according to the identity registration message, wherein the context information includes the network terminal identity and the user identity.

[0237] The determination module 1504 is configured to determine a plurality of service terminals having an identity association relationship according to the context information, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity.

[0238] The interaction module 1504 is configured to send the service to the plurality of service terminals according to the context information.

[0239] In an exemplary embodiment of the present disclosure, sending the service to the plurality of service terminals according to the context information to achieve service linkage between the plurality of service terminals includes:

[0240] Generating a service policy rule for a plurality of service terminals having an identity association relationship according to the context information;

[0241] The service is sent to the multiple service terminals according to the service policy rules to achieve service linkage among the multiple service terminals.

[0242] In an exemplary embodiment of the present disclosure, the registration module 1502 is further configured to:

[0243] Registering a network terminal identity for the first service terminal and establishing a user plane connection;

[0244] Registering a user identity based on a user plane connection corresponding to the first service terminal, and storing context information of the user identity corresponding to the first service terminal;

[0245] Registering the network terminal identity for the second service terminal and establishing a user plane connection;

[0246] triggering the third service terminal to register a user identity based on the user plane connection corresponding to the second service terminal, and storing context information of the user identity corresponding to the third service terminal,

[0247] The first service terminal and the third service terminal are a plurality of service terminals having the identity association relationship.

[0248] In an exemplary embodiment of the present disclosure, the interaction module 1504 is further configured to:

[0249] Identify attribute information of the service corresponding to the service request;

[0250] Determine a service policy rule corresponding to the attribute information, and forward the service to the plurality of service terminals based on the service policy rule.

[0251] In an exemplary embodiment of the present disclosure, the interaction module 1504 is further configured to:

[0252] Determining, according to the context information, that the first service terminal and the third service terminal have the identity association relationship;

[0253] aggregating the context information of the first service terminal and the context information of the third service terminal;

[0254] The business policy rule is generated according to the aggregated context information, and the business policy rule includes at least one of a group communication rule, a message synchronization rule, and a task collaboration rule.

[0255] In an exemplary embodiment of the present disclosure, the interaction module 1504 is further configured to:

[0256] receiving a service request from a first service terminal among the plurality of service terminals;

[0257] Determining, according to the attribute information of the service request, that the service requested by the first service terminal is a self-group service;

[0258] Determine a group communication rule in the service policy rule corresponding to the self-group service;

[0259] The data of the self-group service is fed back to the third service terminal according to the group communication rule.

[0260] In an exemplary embodiment of the present disclosure, the interaction module 1504 is further configured to:

[0261] Responding to traffic sent to a designated user from outside the network;

[0262] Determining, according to the attribute information of the service, that the services of the plurality of service terminals are cross-service terminal synchronization services;

[0263] Determine a message synchronization rule in the service policy rule corresponding to the cross-service terminal synchronization service;

[0264] The service is replicated according to the message synchronization rule and fed back to the multiple service terminals.

[0265] In an exemplary embodiment of the present disclosure, the interaction module 1504 is further configured to:

[0266] Responding to the collaborative task service issued to the designated user;

[0267] Determining, according to the attribute information of the collaborative task service, a task collaboration rule in the service policy rule corresponding to the collaborative task service;

[0268] The tasks are arranged and processed according to the task cooperation rules, and the multiple tasks after the arrangement are sent to the multiple terminals respectively.

[0269] Fig.16 It is a block diagram of another service control device in an exemplary embodiment of the present disclosure.

[0270] refer to Fig.16 , the service control device 1600 includes:

[0271] Determination module 1602 is configured to respond to registration information sent by the cardless service terminal to the network, and generate context information of the cardless service terminal according to the registration information, wherein the context information includes the identity of the cardless service terminal, the network terminal identifier associated with the D2D connection counterpart, the business policy rules and network address of the cardless service terminal.

[0272] The sending module 1604 is configured such that the control plane network element in the core network network element sends the service policy rule to the card-not-present service terminal and the user plane network element according to the context information, and the network performs service control on the card-not-present service terminal based on the service policy rule.

[0273] The receiving module 1606 is configured to receive, as the user plane network element, the flow data fed back by the card-free service terminal via the D2D connection, where the flow data meets the constraints of the service policy rules.

[0274] In an exemplary embodiment of the present disclosure, the network address is allocated by the card-carrying network terminal from a network address segment allocated by the network to a communication address of a cardless business terminal with which a network terminal association relationship exists. The business terminals with which the network terminal association relationship exists are multiple business terminals that access the Internet through a D2D connection of the same network terminal.

[0275] In an exemplary embodiment of the present disclosure, the determination module 1602 is further configured to:

[0276] The user plane network element determines the network terminal association relationship of the card-free service terminal of the sender of the flow data according to the network address;

[0277] The user plane network element performs data exchange with the card-free service terminal according to the service policy rule, and feeds back the flow data to the connection management network element.

[0278] In an exemplary embodiment of the present disclosure, the receiving module 1606 is further configured to:

[0279] The card-presence network terminal performs network terminal identity registration and user identity registration;

[0280] In response to a user identity registration request from a card-not-present service terminal, the card-present network terminal establishes a user plane connection as a network terminal;

[0281] Receiving a user identity registration request initiated by the card-not-present service terminal, the registration request including the identity identifier and authentication information;

[0282] Performing an authorization authentication result on the card-not-present service terminal based on the authentication information, and feeding back the authorization authentication result to the card-not-present service terminal as a response of successful registration;

[0283] The discovery management network element in the core network network element determines the discovery connection management network element corresponding to the session according to the network address;

[0284] The discovery management network element is triggered to synchronize the registration information of the card-not-present service terminal to the connection management network element, and the connection management network element generates context information of the card-not-present service terminal.

[0285] In an exemplary embodiment of the present disclosure, the user identity registration request is transmitted to the core network element based on a D2D connection between the card-not-present service terminal and the card-present network terminal.

[0286] In an exemplary embodiment of the present disclosure, the D2D connection is a connection between the card-present network terminal and / or the card-not-present service terminal established in response to a networking request.

[0287] In an exemplary embodiment of the present disclosure, the network address is used to determine a network terminal association relationship between the card-present network terminal and the card-not-present service terminal.

[0288] In an exemplary embodiment of the present disclosure, the networking request is initiated by the card-free service terminal to the network via a card-present network terminal having a network terminal association relationship.

[0289] Since the functions of the service control apparatus 1500 and the service control apparatus 1600 have been described in detail in the corresponding method embodiments, the present disclosure will not elaborate on them here.

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

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

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

[0293] Refer to the following Fig.17 1700 according to this embodiment of the present invention will be described. Fig.17 The electronic device 1700 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0294] like Fig.17 As shown, the electronic device 1700 is in the form of a general computing device. The components of the electronic device 1700 may include but are not limited to: at least one processing unit 1710, at least one storage unit 1720, and a bus 1730 connecting different system components (including the storage unit 1720 and the processing unit 1710).

[0295] The storage unit stores program codes, which can be executed by the processing unit 1710, so that the processing unit 1710 performs the steps according to various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 1710 can perform the method shown in the embodiment of the present disclosure.

[0296] The storage unit 1720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 17201 and / or a cache storage unit 17202 , and may further include a read-only storage unit (ROM) 17203 .

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

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

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

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

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

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

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

[0304] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0305] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0306] In an exemplary embodiment of the present disclosure, a computer program product is also provided, which can be loaded or stored in any combination of one or more readable media, and can be written in any combination of one or more programming languages ​​to perform the program code of the present invention, including object-oriented programming languages ​​such as Java, C++, etc., and also conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, as an independent software package, partially on the user computing device and partially on a remote computing device, or completely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

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

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

Claims

1. A service control method, characterized in that: Applicable to a core network element, the service control method includes: Registering the identity of the service terminal and generating context information according to the identity registration message, wherein the context information includes the network terminal identity and the user identity; Determine, according to the context information, a plurality of service terminals having an identity association relationship, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity; The service is sent to the multiple service terminals according to the context information, so as to realize the service linkage among the multiple service terminals.

2. The service control method according to claim 1, characterized in that: Sending the service to the plurality of service terminals according to the context information to achieve service linkage between the plurality of service terminals includes: Generating service policy rules for multiple service terminals having identity association relationships according to the context information; The service is sent to the multiple service terminals according to the service policy rules to achieve service linkage between the multiple service terminals.

3. The service control method according to claim 2, characterized in that: Registering the identity of the service terminal and generating context information according to the identity registration message includes: Registering a network terminal identity for the first service terminal and establishing a user plane connection; Registering a user identity based on a user plane connection corresponding to the first service terminal, and storing context information of the user identity corresponding to the first service terminal; Registering the network terminal identity for the second service terminal and establishing a user plane connection; triggering the third service terminal to register a user identity based on the user plane connection corresponding to the second service terminal, and storing context information of the user identity corresponding to the third service terminal, The first service terminal and the third service terminal are a plurality of service terminals having the identity association relationship.

4. The service control method according to claim 3, characterized in that: Sending the service to the plurality of service terminals according to the service policy rule comprises: Identify attribute information of the service corresponding to the service request; Determine a service policy rule corresponding to the attribute information, and forward the service to the plurality of service terminals based on the service policy rule.

5. The service control method according to claim 4, characterized in that: Generating business policy rules for multiple business terminals with identity association relationships includes: Determining, according to the context information, that the first service terminal and the third service terminal have the identity association relationship; aggregating the context information of the first service terminal and the context information of the third service terminal; The business policy rule is generated according to the aggregated context information, and the business policy rule includes at least one of a group communication rule, a message synchronization rule, and a task collaboration rule.

6. The service control method according to claim 5, characterized in that: Determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule includes: receiving a service request from a first service terminal among the plurality of service terminals; Determining, according to the attribute information of the service request, that the service requested by the first service terminal is a self-group service; Determine a group communication rule in the service policy rule corresponding to the self-group service; The data of the self-group service is fed back to the third service terminal according to the group communication rule.

7. The service control method according to claim 5, characterized in that: Determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule further includes: Responding to traffic sent to a designated user from outside the network; Determining, according to the attribute information of the service, that the services of the plurality of service terminals are cross-service terminal synchronization services; Determine a message synchronization rule in the service policy rule corresponding to the cross-service terminal synchronization service; The service is replicated according to the message synchronization rule and fed back to the multiple service terminals.

8. The service control method according to claim 5, characterized in that: Determining a service policy rule corresponding to the attribute information, and forwarding the service to the plurality of service terminals based on the service policy rule further includes: Responding to the collaborative task service issued to the designated user; Determining, according to the attribute information of the collaborative task service, a task collaboration rule in the service policy rule corresponding to the collaborative task service; The tasks are arranged and processed according to the task cooperation rules, and the multiple tasks after the arrangement are sent to the multiple terminals respectively.

9. A service control method, characterized in that: Applicable to a core network element, the service control method includes: In response to user identity registration information sent by the cardless service terminal to the network, generate context information of the cardless service terminal according to the user identity registration information, the context information including the identity identifier of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the cardless service terminal service policy rules and the network address; The control plane network element in the core network network element sends the service policy rule to the card-not-present service terminal and the user plane network element according to the context information, and the network performs service control on the card-not-present service terminal based on the service policy rule; The user plane network element in the core network network element receives the traffic data fed back by the cardless service terminal via the D2D connection, and the traffic data meets the constraints of the service policy rules.

10. The service control method according to claim 9, characterized in that: The network address is allocated by the card-carrying network terminal from the network address segment allocated by the network to the communication address of the card-free service terminal with which the network terminal is associated. The service terminals with which the network terminal is associated are multiple service terminals that access the Internet through the D2D connection of the same network terminal.

11. The service control method according to claim 9, characterized in that: Also includes: The control plane network element determines the network terminal association relationship of the cardless service terminal of the flow data according to the network address; The user plane network element performs data exchange with the card-free service terminal according to the service policy rule, and feeds back the flow data to the connection management network element.

12. The service control method according to any one of claims 9 to 10, characterized in that: Before generating the context information of the card-not-present service terminal according to the registration information of the card-not-present service terminal, the method further includes: The card-presence network terminal performs network terminal identity registration and user identity registration; In response to a user identity registration request from a card-not-present service terminal, the card-present network terminal establishes a user plane connection as a network terminal; Receiving a user identity registration request initiated by the card-not-present service terminal, the registration request including the identity identifier and authentication information; Performing an authorization authentication result on the card-not-present service terminal based on the authentication information, and feeding back the authorization authentication result to the card-not-present service terminal as a response of successful registration; The discovery management network element in the core network network element determines the connection management network element corresponding to the session according to the source network address of the registration request; The discovery management network element is triggered to synchronize the registration information of the card-not-present service terminal to the connection management network element, and the connection management network element generates context information of the card-not-present service terminal.

13. The service control method according to claim 12, characterized in that: The user identity registration request is transmitted to the core network element based on the D2D connection between the card-free service terminal or the card-present network terminal.

14. The service control method according to claim 13, characterized in that: The D2D connection is a connection between the card-present network terminal and / or the card-not-present service terminal established in response to a networking request.

15. The service control method according to claim 12, characterized in that: The network address is used to determine the network terminal association relationship between the card-present network terminal and the card-not-present service terminal.

16. The service control method according to claim 14, characterized in that: The network connection request is initiated by the card-free service terminal to the network via the card-present network terminal with which the network terminal is associated.

17. A service control device, characterized in that: Applicable to a core network element, the service control device comprises: A registration module, configured to register the identity of the service terminal and generate context information according to the identity registration message, wherein the context information includes the network terminal identity and the user identity; A determination module, configured to determine a plurality of service terminals having an identity association relationship according to the context information, wherein the identity association relationship includes a relationship having the same user identity or a relationship having the same network terminal identity; The interaction module is configured to send the service to the plurality of service terminals according to the context information.

18. A service control device, characterized in that: Applicable to a core network element, the service control device comprises: A determination module, configured to generate context information of the card-free service terminal in response to registration information sent by the card-free service terminal to the network according to the registration information, wherein the context information includes an identity identifier of the card-free service terminal, a network terminal identifier associated with the D2D connection peer, a service policy rule of the card-free service terminal, and a network address; A sending module, configured to be a control plane network element in the core network network element to send the service policy rule to the card-free service terminal and the user plane network element according to the context information; The receiving module is further configured such that the user plane network element receives the flow data fed back by the card-free service terminal via the D2D connection, and the flow data satisfies the constraints of the service policy rules.

19. An electronic device, characterized in that: include: Memory; as well as A processor coupled to the memory, wherein the processor executes the service control method according to any one of claims 1 to 16 based on instructions stored in the memory.

20. A computer-readable storage medium having a program stored thereon, wherein when the program is executed by a processor, the service control method according to any one of claims 1 to 16 is implemented.

21. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the service control method according to any one of claims 1 to 16 is implemented.

Images