Service control methods and apparatuses, device, medium and product

Abstract

Provided in the present disclosure are service control methods and apparatuses, a device, a medium and a product. A method comprises: performing identity registration on service terminals, and generating context information on the basis of messages of the identity registration, the context information comprising network terminal identities and user identities; on the basis of the context information, determining a plurality of service terminals having an identity association relationship, the identity association relationship comprising a relationship of having the same user identity or a relationship of having the same network terminal identity; generating a service policy rule for the plurality of service terminals having the identity association relationship; and sending services to the plurality of service terminals according to the service policy rule, so as to implement service linkage among the plurality of service terminals. The embodiments of the present disclosure not only can identify a plurality of service terminals of the same user, but also can identify different users associated with the same service terminal, thereby implementing network linkage among the plurality of service terminals, and improving the reliability and timeliness of network service interaction.

Description

Business control methods, devices, equipment, media and products

[0001] This application claims priority to a prior Chinese application with application number "202411001407.6", filing date "2024.7.24", and title "Business Control Method, Apparatus, Equipment, Medium, and Product", which is the first application and has not exceeded the 12-month priority period. Technical Field

[0002] This disclosure relates to the field of communication technology, and more specifically, to a service control method, apparatus, device, medium, and product. Background Technology

[0003] Currently, with the development of communication technology, a user typically owns several devices and needs personal services to coordinate across these devices. On the one hand, traditionally, similar service requirements rely on application-layer implementation of inter-service terminal collaboration or information synchronization, lacking network linkage solutions to guarantee service performance. On the other hand, next-generation networks need to meet the demand for wide-area ubiquitous connectivity, and 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, which current network control mechanisms cannot accurately distinguish and control.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The purpose of this disclosure is to provide a business control method, apparatus, device, medium, and product to overcome, at least to some extent, the problem of lack of network linkage between multiple business terminals of the same user due to limitations and defects in related technologies.

[0006] According to a first aspect of the present disclosure, a service control method is provided, applicable to core network elements. The service control method includes: registering the identity of a service terminal and generating context information based on the identity registration message, wherein the context information includes network terminal identity and user identity.

[0007] Based on the context information, multiple business terminals with identity association relationships are determined, including relationships with the same user identity or the same network terminal identity.

[0008] Generate business policy rules for multiple business terminals with identity association relationships;

[0009] According to the business strategy rules, the service is sent to multiple business terminals to achieve business linkage between multiple business terminals.

[0010] In one exemplary embodiment of this disclosure, registering the identity of a service terminal and generating context information based on the identity registration message includes:

[0011] Register the network terminal identity of the first service terminal and establish a user plane connection;

[0012] User identity registration is performed based on the user plane connection corresponding to the first service terminal, and the context information of the user identity corresponding to the first service terminal is stored.

[0013] Register the network terminal identity of the second service terminal and establish a user plane connection;

[0014] The third service terminal is triggered to register the user identity based on the user plane connection corresponding to the second service terminal, and the context information of the user identity corresponding to the third service terminal is stored.

[0015] The first service terminal and the third service terminal are multiple service terminals that have the aforementioned user association relationship.

[0016] In one exemplary embodiment of this disclosure, sending services to multiple service terminals according to the service policy rules includes:

[0017] Identify the attribute information of the business corresponding to the business request;

[0018] The business policy rules corresponding to the attribute information are determined, and the business is forwarded to multiple business terminals based on the business policy rules.

[0019] In one exemplary embodiment of this disclosure, generating service policy rules for multiple service terminals with identity association relationships includes:

[0020] Based on the context information, it is determined that the first service terminal and the third service terminal have the identity association relationship;

[0021] The context information of the first service terminal and the context information of the third service terminal are aggregated;

[0022] The business strategy rules are generated based on the aggregated context information, and the business strategy rules include at least one of group communication rules, message synchronization rules, and task collaboration rules.

[0023] In one exemplary embodiment of this disclosure, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule includes:

[0024] Receive a service request from the first service terminal among the multiple service terminals;

[0025] Based on the attribute information of the service request, it is determined that the service requested by the first service terminal is a self-group service;

[0026] Determine the group communication rules in the service policy rules corresponding to the self-group service;

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

[0028] In one exemplary embodiment of this disclosure, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule further includes:

[0029] Responding to services sent from outside the network to a specified user;

[0030] Based on the attribute information of the service, the services of multiple service terminals are determined to be cross-service terminal synchronization services;

[0031] Determine the message synchronization rule in the business strategy rule corresponding to the cross-service terminal synchronization service;

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

[0033] In one exemplary embodiment of this disclosure, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule further includes:

[0034] Responding to collaborative task requests sent to designated users;

[0035] The task collaboration rules in the business strategy rules corresponding to the collaborative task service are determined based on the attribute information of the collaborative task service.

[0036] The tasks are orchestrated according to the task collaboration rules, and the orchestrated tasks are sent to the various service terminals respectively.

[0037] According to a second aspect of the present disclosure, a service control method is provided, applicable to core network elements, the service control method comprising:

[0038] In response to the registration information sent to the network by the cardless service terminal, context information of the cardless service terminal is generated based on the registration information. The context information includes the identity identifier of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the service policy rules of the cardless service terminal, and the network address. The network address is the communication address of the cardless service terminal that is assigned from the network address range allocated by the network terminal to the cardless service terminal with network terminal association relationship. The service terminals with network terminal association relationship are multiple service terminals that access the Internet through D2D connection of the same network terminal.

[0039] The control plane network element in the core network element sends the service policy rules to the cardless service terminal and the user plane network element according to the context information, and the network performs service control on the cardless service terminal based on the service policy rules;

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

[0041] In one exemplary embodiment of this disclosure, it further includes:

[0042] The control plane network element determines the network terminal association relationship of the cardless service terminal of the sender of the traffic data based on the network address;

[0043] The user plane network element interacts with the cardless service terminal according to the service policy rules and feeds back the traffic data to the connection management network element.

[0044] In one exemplary embodiment of this disclosure, before generating the context information of the cardless service terminal based on the registration information of the cardless service terminal, the method further includes:

[0045] The card-enabled network terminal performs network terminal identity registration and user identity registration;

[0046] In response to a user identity registration request from a cardless service terminal, the card-enabled network terminal establishes a user plane connection using its network terminal identity.

[0047] Receive a user identity registration request initiated by the cardless service terminal, the registration request including the identity identifier and authentication information;

[0048] Based on the authentication information, the cardless service terminal is authenticated, and the authentication result is fed back to the cardless service terminal as a successful registration response.

[0049] The discovery management element in the core network element determines the connection management element corresponding to the session based on the network address;

[0050] The discovery management network element is triggered to synchronize the registration information of the cardless service terminal to the connection management network element, and the connection management network element generates the context information of the cardless service terminal.

[0051] In one exemplary embodiment of this disclosure, the user identity registration request is transmitted to the core network element based on the D2D connection between the cardless service terminal and the card-equipped network terminal.

[0052] In one exemplary embodiment of this disclosure, the D2D connection is a connection established in response to a network connection request between the card-enabled network terminal and / or the cardless service terminal.

[0053] In one exemplary embodiment of this disclosure, the network address is used to determine the network terminal association relationship between the card-enabled network terminal and the cardless service terminal.

[0054] In one exemplary embodiment of this disclosure, the network connection request is initiated by the cardless service terminal to the network via a SIM card network terminal with which it has a network terminal association.

[0055] According to a third aspect of the present disclosure, a service control device is provided, applicable to a core network element, the service control device comprising:

[0056] The registration module is configured to register the identity of a business terminal and generate context information based on the identity registration message. The context information includes the network terminal identity and the user identity.

[0057] The determination module is configured to determine multiple business terminals with identity association relationships based on the context information, wherein the identity association relationships include relationships with the same user identity or relationships with the same network terminal identity.

[0058] The module is configured to generate business policy rules for multiple business terminals with identity association relationships.

[0059] The interaction module is configured to send services to multiple service terminals according to the business strategy rules.

[0060] According to a fourth aspect of the present disclosure, a service control device is provided, applicable to a core network element, the service control device comprising:

[0061] The determination module is configured to respond to the registration information sent by the cardless service terminal to the network, and generate the context information of the cardless service terminal based on the registration information. The context information includes the identity identifier of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the service policy rules of the cardless service terminal, and the network address. The network address is the communication address of the cardless service terminal that is assigned from the network address range allocated by the SIM card network terminal to the cardless service terminal with the network terminal association relationship. The service terminals with the network terminal association relationship are multiple service terminals that access the Internet through D2D connection of the same network terminal.

[0062] The sending module is configured to send the service policy rules to the user plane network element and the cardless service terminal respectively according to the context information;

[0063] The receiving module is configured to receive traffic data fed back by the cardless service terminal via the D2D connection from the user plane network element, wherein the traffic data satisfies the constraints of the service policy rules.

[0064] According to a fifth aspect of this disclosure, an electronic device is provided, comprising: a memory; and a processor coupled to the memory, the processor performing the method as described in any one of the preceding methods based on instructions stored in the memory.

[0065] According to a sixth aspect of this disclosure, a computer-readable storage medium is provided having a program stored thereon that, when executed by a processor, implements the business control method as described in any of the preceding claims.

[0066] According to a seventh aspect of this disclosure, a computer program product is provided, comprising a computer program, characterized in that, when executed by a processor, the computer program implements the business control method as described in any of the preceding claims.

[0067] Based on the embodiments of this disclosure, by registering the identity of 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, the attribute information of the service corresponding to the service request is identified, and the service is forwarded to multiple service terminals according to the attribute information. This not only identifies multiple service terminals of the same user, but also identifies different users associated with the same service terminal. The network can directly control the service of cardless service terminals, expand the functions of group communication, service collaboration and information synchronization between multiple service terminals, realize network linkage between multiple service terminals, and improve the reliability and timeliness of network service interaction.

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

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

[0070] Figure 1 shows a schematic diagram of an exemplary system architecture for which the business control scheme of the present invention can be applied;

[0071] Figure 2 is a flowchart of a business control method in an exemplary embodiment of this disclosure;

[0072] Figure 3 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0073] Figure 4 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0074] Figure 5 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0075] Figure 6 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0076] Figure 7 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0077] Figure 8 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0078] Figure 9 is a flowchart of another business control method in an exemplary embodiment of this disclosure;

[0079] Figure 10 is a schematic diagram of the architecture of a business control scheme in the prior art;

[0080] Figure 11 is a schematic diagram of the architecture of another business control scheme in the prior art;

[0081] Figure 12 is a schematic diagram of the architecture of a business control scheme in an exemplary embodiment of this disclosure;

[0082] Figure 13 is an interactive schematic diagram of a business control scheme in an exemplary embodiment of this disclosure;

[0083] Figure 14 is an interactive schematic diagram of another business control scheme in an exemplary embodiment of this disclosure;

[0084] Figure 15 is a block diagram of a service control device according to an exemplary embodiment of the present disclosure;

[0085] Figure 16 is a block diagram of another service control device in an exemplary embodiment of this disclosure;

[0086] Figure 17 is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

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

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

[0089] The technical terms used in the embodiments of this disclosure are explained as follows:

[0090] Network terminal identity: An identity information tightly coupled with the network service terminal, similar to SUPI (User Permanent Identifier) ​​or SUCI (User Encrypted Identifier) ​​in 5G networks. In this disclosure, the network service terminal possesses a network terminal identity, but a service terminal does not necessarily possess a network terminal identity, such as a cardless service terminal; when a cardless remote service terminal accesses the Internet through a regular Layer 3 relay, the remote service terminal is a service terminal, but not a network service terminal, and therefore does not have a network terminal identity.

[0091] User identity: Identification information related to specific business users, possessing social attributes, such as the identity information of a specific person, also called individual user identity. An entity with user identity can own multiple network business terminals or business business terminals. The relationship between user identity and network terminal identity can be 1:n.

[0092] User plane network elements: Similar to the user plane function (UPF) of the 5G core network, they execute user plane policies, including network functions such as traffic identification, forwarding, and other processing at various levels.

[0093] Connection Management Network Element: Similar to the Session Management Function (SMF) network element in the control plane of the 5G core network, in this disclosure, this network element not only performs session management (SMF function) for network terminal identity entities (network service terminals), but is also responsible for connection management of individual user identity entities, and stores user context to control the forwarding path at the user level (such as the flow level).

[0094] Discovery Management Network Element: In near-field discovery scenarios, this network element assists in the discovery of nearby service terminals, similar to DDNMF (Direct Discovery Name Management Function) in 5G proximity services; in some user authentication scenarios, this network element can perform the functions of an access security gateway, performing intermediate calculations and verification functions in the user authentication process.

[0095] Subscription and authentication network elements: These elements store user subscription information and perform server-side functions for user authentication based on that information. For network terminal authentication, these elements perform functions similar to 5G AUSF / UDM; for user authentication, they are compatible with multiple authentication methods, such as AAA authentication or application-layer authentication; these elements can also perform functions similar to 5G PCF, thus providing policy-based subscription capabilities.

[0096] UE: User Equipment, is an access service terminal for a mobile network. In this disclosure, it represents a network service terminal, that is, a network terminal identity carrier that accesses the mobile network.

[0097] DN: Data Network, the network behind the user plane anchor point of a mobile network, usually referring to the deployment environment of applications.

[0098] Figure 1 shows a schematic diagram of an exemplary system architecture for which the business control scheme of the present invention can be applied.

[0099] As shown in Figure 1, the system architecture 100 may include one or more of service terminal devices 101, 102, and 103, a network 104, and a server 105. The network 104 serves as the medium for providing communication links between the service terminal devices 101, 102, and 103 and the server 105. The network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0100] It should be understood that the number of business terminal devices, networks, and servers shown in Figure 1 is merely illustrative. Depending on implementation needs, any number of business terminal devices, networks, and servers can be used. For example, server 105 could be a server cluster composed of multiple servers.

[0101] Users can use service terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Service terminal devices 101, 102, and 103 can be various electronic devices with displays, including but not limited to smartphones, tablets, laptops, and desktop computers, etc.

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

[0103] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0104] Figure 2 is a flowchart of the business control method in an exemplary embodiment of this disclosure.

[0105] Referring to Figure 2, business control methods may include:

[0106] Step S202: Register the identity of the service terminal and generate context information based on the identity registration message. The context information includes the network terminal identity and the user identity.

[0107] Step S204: Determine multiple service terminals with identity association relationships based on the context information. The identity association relationships include relationships with the same user identity or relationships with the same network terminal identity.

[0108] Step S206: Generate business policy rules for multiple business terminals with identity association relationships.

[0109] Step S208: Send the service to multiple service terminals according to the service policy rules to realize service linkage between multiple service terminals.

[0110] Based on the embodiments of this disclosure, by registering the identity of the service terminals 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, the attribute information of the service corresponding to the service request is identified, and the service is forwarded to multiple service terminals according to the attribute information. This 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.

[0111] In one exemplary embodiment of this disclosure, the service includes, but is not limited to, service traffic data, control signaling, and protocol messages.

[0112] The following section provides a detailed explanation of each step in the business control method.

[0113] In one exemplary embodiment of this disclosure, as shown in FIG3, registering the identity of the service terminal and generating context information based on the identity registration message includes:

[0114] Step S302: Register the network terminal identity of the first service terminal and establish a user plane connection.

[0115] Step S304: Register user identity based on the user plane connection corresponding to the first service terminal, and store the context information of the user identity corresponding to the first service terminal.

[0116] Step S306: Register the network terminal identity of the second service terminal and establish a user plane connection.

[0117] Step S308: Trigger the third service terminal to register user identity based on the user plane connection corresponding to the second service terminal, and store the context information of the user identity corresponding to the third service terminal. The first service terminal and the third service terminal are multiple service terminals with the identity association relationship.

[0118] In one exemplary embodiment of this disclosure, the second service terminal can create a user plane connection as a network terminal, and the third service terminal is equivalent to the second service terminal or a subordinate device of the second service terminal, but is not limited thereto.

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

[0120] Table 1

[0121] In one exemplary embodiment of this disclosure, GBR (Guaranteed Bit Rate) in Table 1 refers to the guaranteed bit rate, which can be maintained even when network resources are scarce, i.e., the guaranteed minimum bandwidth.

[0122] In one exemplary embodiment of this disclosure, as shown in FIG4, sending services to multiple service terminals according to the service policy rules includes:

[0123] Step S402: Identify the attribute information of the business corresponding to the business request.

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

[0125] In one exemplary embodiment of this disclosure, as shown in FIG5, generating business policy rules for multiple business terminals with identity association relationships includes:

[0126] Step S502: Determine that the first service terminal and the third service terminal have the identity association relationship based on the context information.

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

[0128] Step S506: Generate the business strategy rules based on the aggregated context information. The business strategy rules include at least one of group communication rules, message synchronization rules, and task collaboration rules.

[0129] In one exemplary embodiment of this disclosure, a self-group service refers to the interaction of services between multiple service terminals.

[0130] In one exemplary embodiment of this disclosure, as shown in FIG6, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule includes:

[0131] Step S602: Receive a service request from the first service terminal among the plurality of service terminals.

[0132] Step S604: Determine that the service requested by the first service terminal is a self-group service based on the attribute information of the service request.

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

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

[0135] In one exemplary embodiment of this disclosure, as shown in FIG7, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule further includes:

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

[0137] Step S704: Determine that the services of multiple service terminals are cross-service terminal synchronization services based on the attribute information of the services.

[0138] Step S706: Determine the message synchronization rule in the business strategy rule corresponding to the cross-service terminal synchronization service.

[0139] Step S708: The service is copied and fed back to multiple service terminals according to the message synchronization rules.

[0140] In one exemplary embodiment of this disclosure, the identity of the specified user can be determined based on context information, and further, business terminals with the same user identity can be determined, i.e., business terminals with an identity association relationship.

[0141] In one exemplary embodiment of this disclosure, as shown in FIG8, determining the service policy rule corresponding to the attribute information and forwarding the service to multiple service terminals based on the service policy rule further includes:

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

[0143] In one exemplary embodiment of this disclosure, the identity of the specified user can be determined based on context information, and further, business terminals with the same user identity can be determined, i.e., business terminals with an identity association relationship.

[0144] Step S804: Determine the task collaboration rules in the business strategy rules corresponding to the collaborative task service based on the attribute information of the collaborative task service.

[0145] Step S806: Arrange the tasks according to the task collaboration rules, and send the arranged tasks to the multiple terminals respectively.

[0146] In one exemplary embodiment of this disclosure, cross-service terminal synchronization service refers to the service of synchronizing data in real time to other service terminals when other users send data to at least one of the multiple service terminals.

[0147] Figure 9 is a flowchart of the business control method in an exemplary embodiment of this disclosure.

[0148] Referring to Figure 9, the business control methods include:

[0149] 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 based on the registration information. The context information includes the identity identifier of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the service policy rules of the cardless service terminal, and the network address. The network address is the communication address of the cardless service terminal that has a network terminal association relationship with the network terminal, which is assigned from the network address range allocated by the SIM card network terminal. The service terminals with the network terminal association relationship are multiple service terminals that access the Internet through D2D connection of the same network terminal.

[0150] In step S904, the control plane network element in the core network element sends the service policy rules to the user plane network element and the cardless service terminal respectively according to the context information, and the network performs service control on the cardless service terminal based on the service policy rules.

[0151] In step S906, the user plane network element in the core network element receives traffic data fed back by the cardless service terminal through the D2D connection, and the traffic data satisfies the constraints of the service policy rules.

[0152] In one exemplary embodiment of this disclosure, the control plane network elements include discovery management network elements, connection management network elements, subscription and authentication network elements, etc., but are not limited thereto.

[0153] In an exemplary embodiment of this disclosure, based on the technical solution defined in steps S902-S906 above, in a scenario where multiple cardless service terminal devices are attached to a network service terminal, specific end users can be distinguished and precisely controlled based on the matching with the user context. That is, by introducing user identity in conjunction with network terminal identity, the network user group can be expanded, which is in line with the development trend of ubiquitous mobile network connectivity. At the same time, the network-native user identification capability provides users with value-added services across service terminals, thereby maximizing the value-added of the communication network.

[0154] In one exemplary embodiment of this disclosure, it further includes:

[0155] The control plane network element (i.e., the connection management network element) determines the network terminal association relationship of the cardless service terminal of the sender of the traffic data based on the network address;

[0156] The user plane network element interacts with the cardless service terminal according to the service policy rules and feeds back the traffic data to the connection management network element.

[0157] In one exemplary embodiment of this disclosure, before generating the context information of the cardless service terminal based on the registration information of the cardless service terminal, the method further includes:

[0158] The card-enabled network terminal performs network terminal identity registration and user identity registration;

[0159] In response to a user identity registration request from a cardless service terminal, the card-enabled network terminal establishes a user plane connection using its network terminal identity.

[0160] Based on the authentication information, the cardless service terminal is authenticated, and the authentication result is fed back to the cardless service terminal as a successful registration response.

[0161] The discovery management network element in the core network element determines the discovery connection management network element corresponding to the session based on the network address;

[0162] The discovery management network element is triggered to synchronize the registration information of the cardless service terminal to the connection management network element, and the connection management network element generates the context information of the cardless service terminal.

[0163] In one exemplary embodiment of this disclosure, the user identity registration request is transmitted to the core network element based on the D2D connection between the cardless service terminal and the card-equipped network terminal.

[0164] In one exemplary embodiment of this disclosure, the D2D connection is a connection established in response to a network connection request between the card-enabled network terminal and / or the cardless service terminal.

[0165] In one exemplary embodiment of this disclosure, the network address is used to determine the network terminal association relationship between the card-enabled network terminal and the cardless service terminal.

[0166] In one exemplary embodiment of this disclosure, the network connection request is initiated by the cardless service terminal to the network via a SIM card network terminal with which it has a network terminal association.

[0167] The following description of the architecture of multiple terminals for the same user in the prior art is illustrated with reference to Figures 10 and 11.

[0168] As shown in Figure 10, in the architecture 1000 of a service control scheme in the prior art, when user 1 has both UE-A and UE-B, UE-A and UE-B are regarded as two different users, and UE3 is the terminal of other users. Even if the same user logs in on two terminals, the service synchronization and coordination between them can only be controlled by the service platform outside the 5G network.

[0169] As shown in Figure 11, in the architecture 1100 of a service control scheme in the prior art, the cardless service terminal D (user 3) connects to the Internet through terminal C (user 2) and UE-A (user 1) in a Layer 3 relay connection manner, and terminal E (user 5) connects to the Internet through terminal B (user 4). The network cannot perceive the users downstream of terminal UE-A and the users downstream of terminal UE-B. That is, the 5G5 network performs service control based on the identity of terminal UE-A (i.e., user 1) and the identity of terminal UE-B.

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

[0171] To address the shortcomings in the existing technology, as shown in Figure 12, this disclosure proposes a new business control framework 1200, which aims to solve the control and business shortcomings caused by the equivalence of user identity to network terminal identity.

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

[0173] Secondly, after the terminal with network terminal identity (SIM card) performs network registration, user identity-level registration is performed (if it is a relay, it and each downstream terminal are registered separately).

[0174] As shown in Figure 12, after UE-A performs network terminal identity registration, User 2 (service terminal is terminal C) and User 1 (service terminal is UE-A) perform user identity registration respectively, and User 3 (service terminal is terminal B) and User 4 (service terminal is terminal E) perform user identity registration respectively, establishing a user context in the network. In subsequent service processes, User 2 (UE-C) interacts with the mobile network as an independent terminal.

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

[0176] In one exemplary embodiment of this disclosure, regardless of whether the service terminal used by the user is the network terminal of this connection or the downstream terminal of the locally connected network terminal, the associated network terminal identity identifier is the network identity identifier of the network terminal of this connection.

[0177] As shown in Table 2, an example of a user context corresponding to Figure 12 illustrates this. In this example, user 2 maintains a consistent service control strategy even when using different service terminals. Based on the user context, the network can identify services from the same user across different terminals, or different or identical users connected to a single terminal. This allows the network to associate and process services from the same user across different service terminals, such as data synchronization, service collaboration, distributed data processing and aggregation, but is not limited to these. In scenarios where multiple cardless service terminal devices are connected to a network terminal, the network can also distinguish specific end users based on the matching of user contexts and perform precise control.

[0178] Table 2

[0179] As shown in Table 2, the mobile network analyzes the context and determines that traffic from IP2 and IP3 belongs to User 2. Furthermore, it can identify traffic from the same application within this traffic. The mobile network can also accurately identify traffic from IP5 as User 4's traffic based on the context, thus differentiating it from User 3's traffic from the UE-B session.

[0180] In one exemplary embodiment of this disclosure, the user identity encoding and the authentication method of the user identity registration process are not limited. Under the security mechanism of network terminal identity authentication, user identity authentication can be compatible with multiple authentication methods, such as AAA authentication, or even any authentication method at the application layer. Furthermore, to support user identity-based control, a service policy for user identity needs to be signed up in the network and stored in the signing and authentication network elements. Since user identity authentication is associated with the service terminal, multiple registrations are possible in the case of multiple terminals without conflicting registration information; that is, multiple registration records can be stored.

[0181] In an exemplary embodiment of this disclosure, as shown in FIG13, a service control scheme is provided. The process of implementing network control for multi-terminal linkage services based on user plane network element 1302, connection management network element 1304, subscription and authentication network element 1306, UE1 1308 (user 1), UE2 1310 (user 1), and DN 1312 includes:

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

[0183] 2a. UE1 1308 is the service terminal of user 1. After UE1 1308 completes network terminal identity registration, user 1 performs user identity registration. The connection management network element 1304 saves the context of the user identity, including the identity identifier of user 1, the network address of UE1 1308, and the network terminal identity identifier of UE1 1308.

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

[0185] 2b. UE2 1310 is also a 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.

[0186] 3. The connection management network element 1304 determines, based on context matching, that user 1 is using both UE1 1308 and UE2 1310. Therefore, it aggregates the two contexts of user 1 and generates service policy rules (such as execution rules related to group communication, message synchronization, task collaboration, etc.) for user 1's identity.

[0187] 4. The connection management network element 1304 sends the corresponding service policy rules to each service terminal and the relevant user plane network element 1302.

[0188] 5a to 7a represent the process of implementing self-group services between different service terminals of the same user.

[0189] 5a. User 1 initiates a group service using UE2 1310, with the target being other service terminals of the user.

[0190] 6a. User plane network element 1302 executes the service policy rules, identifies the message as a user self-group service, and determines that it needs to be forwarded to UE1 1308.

[0191] 7a. User plane network element 1302 forwards group services to UE1 1308.

[0192] Sections 5b to 8b describe the process of implementing message synchronization services between different service terminals of the same user.

[0193] 5b. The mobile network receives a message addressed to UE1 1308 from an external source (DN 1312).

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

[0195] 7b. User plane network element 1302 forwards a message to UE1 1308.

[0196] 8b. User plane network element 1302 forwards another message to UE2 1310.

[0197] As shown in Figure 14, this disclosure provides a service control scheme for a three-layer relay network scenario. Based on a cardless service terminal 1402 (user 2), UE1 1404 (user 1), user plane network element 1406, connection management network element 1408, discovery management network element 1410, and subscription and authentication network element 1414, UE1 1404 is the service terminal for user 1 and also acts as a layer 3 relay to provide relay internet access service to the cardless service terminal 1402. The cardless service terminal 1402 is the service terminal for user 2. The process of network control for multi-terminal linkage services includes:

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

[0199] 2. The cardless service terminal 1402 initiates a discovery request, indicating that it needs to connect to the Internet, and discovers and selects UE1 1404 as the Internet Layer 3 relay.

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

[0201] 4. Cardless service terminal 1402 initiates a user identity registration request through the dedicated channel of UE1 1404. This request is sent to discovery and management network element 1410.

[0202] 5. Discover that the management network element 1410 acts as the access security gateway network element of the cardless service terminal 1402, assists the signing and authentication network element 1414 in authenticating the user, and obtains the user's identity signing information from the signing and authentication network element 1414.

[0203] 6. The management network element 1410 sends a registration success message to the cardless service terminal 1402.

[0204] 7. The management network element 1410 discovers the connection management network element 1408 corresponding to the session with UE1 1404 based on the IP network address in the registration request message of the cardless service terminal 1402.

[0205] 8. The management network element 1410 synchronizes the information of user 2 to the connected management network element 1408, including the network address of the cardless service terminal 1402, the user identity and subscription information in step 5, etc.

[0206] 9. The connection management network element 1408 generates user context information for user 2, which includes the user identity identifier of the cardless service terminal 1402 (i.e., user 2), the network terminal identity identifier of UE1 1404, the terminal address of user 2, and the service policy rules for user 2's user identity.

[0207] 10. Connect management network element 1408 to send service policy rules to cardless service terminal 1402.

[0208] 11. The connection management network element 1408 sends service policy rules to the relevant user plane network element 1406. This step is not in any particular order from step 10.

[0209] 12. User 2's traffic is transmitted to user plane network element 1406 through the D2D connection of UE1 1404.

[0210] 13. User plane network element 1406 identifies user 2's traffic based on the terminal network address and executes the corresponding service policy rules.

[0211] 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.

[0212] In one exemplary embodiment of this disclosure, certain details and technical extensions of the technical solution are also provided:

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

[0214] (2) User identity authentication is associated with business terminals, so multiple registrations are possible in the case of multiple terminals, and the registration information does not conflict, that is, multiple registration information can be saved.

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

[0216] (4) The network element that acts as the intermediary for user identity registration is not necessarily DDNMF, but since 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.

[0217] (5) In actual design or deployment, the signed and certified network elements can be multiple network elements.

[0218] In one exemplary embodiment of this disclosure, to address the lack of control mechanisms and service flexibility caused by the tight coupling between existing network user identities and terminal devices, this disclosure also proposes a user identity-based mobile network service control method, which includes:

[0219] (1) Introduce user identity and use the user identity identifier as the user access parameter. The user identity corresponds to an individual user with a social identity.

[0220] (2) After the terminal with network terminal identity (SIM card) performs network registration, it performs user identity level registration (if it is a relay, it and each downstream terminal are registered separately) and establishes user context.

[0221] In one exemplary embodiment of this disclosure, the user context includes, but is not limited to, the user identity identifier associated with the user, the network address assigned to the service terminal by the network or upstream device, the service control policy related to the user, and the associated network terminal identity identifier.

[0222] (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 connected to a terminal, so that the services of the same user on different service terminals can be associated and processed (such as data synchronization, service collaboration, distributed processing and aggregation of data, etc.).

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

[0224] The above embodiments expand the network user group by introducing user identity combined with network terminal identity, which is in line with the development trend of ubiquitous mobile network connectivity. At the same time, it enables users to provide cross-terminal value-added services through the network's inherent user identification capabilities, thereby maximizing the value-added of the network.

[0225] Corresponding to the above method embodiments, this disclosure also provides a business control device that can be used to execute the above method embodiments.

[0226] Figure 15 is a block diagram of a service control device according to an exemplary embodiment of the present disclosure.

[0227] Referring to Figure 15, the service control device 1500 may include:

[0228] The registration module 1502 is configured to register the identity of a business terminal and generate context information based on the identity registration message. The context information includes the network terminal identity and the user identity.

[0229] The determination module 1504 is configured to determine multiple business terminals with identity association relationships based on the context information, wherein the identity association relationships include relationships with the same user identity or relationships with the same network terminal identity.

[0230] Module 1504 is configured to generate business policy rules for multiple business terminals with identity association relationships.

[0231] The interaction module 1506 is configured to send services to multiple service terminals according to the service policy rules.

[0232] In one exemplary embodiment of this disclosure, the registration module 1502 is further configured to:

[0233] Register the network terminal identity of the first service terminal and establish a user plane connection;

[0234] User identity registration is performed based on the user plane connection corresponding to the first service terminal, and the context information of the user identity corresponding to the first service terminal is stored.

[0235] Register the network terminal identity of the second service terminal and establish a user plane connection;

[0236] The third service terminal is triggered to register the user identity based on the user plane connection corresponding to the second service terminal, and the context information of the user identity corresponding to the third service terminal is stored.

[0237] The first service terminal and the third service terminal are multiple service terminals with the aforementioned identity association relationship.

[0238] In one exemplary embodiment of this disclosure, the interaction module 1506 is further configured as follows:

[0239] Identify the attribute information of the business corresponding to the business request;

[0240] The business policy rules corresponding to the attribute information are determined, and the business is forwarded to multiple business terminals based on the business policy rules.

[0241] In one exemplary embodiment of this disclosure, the determining module 1504 is further configured to:

[0242] Based on the context information, it is determined that the first service terminal and the third service terminal have the identity association relationship;

[0243] The context information of the first service terminal and the context information of the third service terminal are aggregated;

[0244] The business strategy rules are generated based on the aggregated context information, and the business strategy rules include at least one of group communication rules, message synchronization rules, and task collaboration rules.

[0245] In one exemplary embodiment of this disclosure, the determining module 1504 is further configured to:

[0246] Receive a service request from the first service terminal among the multiple service terminals;

[0247] Based on the attribute information of the service request, it is determined that the service requested by the first service terminal is a self-group service;

[0248] Determine the group communication rules in the service policy rules corresponding to the self-group service;

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

[0250] In one exemplary embodiment of this disclosure, the determining module 1504 is further configured to:

[0251] Responding to services sent from outside the network to a specified user;

[0252] Based on the attribute information of the service, the services of multiple service terminals are determined to be cross-service terminal synchronization services;

[0253] Determine the message synchronization rule in the business strategy rule corresponding to the cross-service terminal synchronization service;

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

[0255] In one exemplary embodiment of this disclosure, the determining module 1504 is further configured to:

[0256] Responding to collaborative task requests sent to designated users;

[0257] The task collaboration rules in the business strategy rules corresponding to the collaborative task service are determined based on the attribute information of the collaborative task service.

[0258] The tasks are orchestrated according to the task collaboration rules, and the orchestrated tasks are sent to the terminals respectively.

[0259] Figure 16 is a block diagram of another service control device in an exemplary embodiment of this disclosure.

[0260] Referring to Figure 16, the business control device 1600 includes:

[0261] The 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 based on the registration information. The context information includes the identity identifier of the cardless service terminal, the network terminal identifier associated with the D2D connection peer, the service policy rules of the cardless service terminal, and the network address. The network address is the communication address of the cardless service terminal that is assigned from the network address range allocated by the SIM card network terminal to the cardless service terminal with the network terminal association relationship. The service terminals with the network terminal association relationship are multiple service terminals that access the Internet through D2D connection of the same network terminal.

[0262] The sending module 1604 is configured to send the service policy rules to the cardless service terminal and the user plane network element in the core network element according to the context information, and the network performs service control on the cardless service terminal based on the service policy rules.

[0263] The receiving module 1606 is configured to receive traffic data fed back by the cardless service terminal through the D2D connection from the user plane network element, wherein the traffic data satisfies the constraints of the service policy rules.

[0264] In one exemplary embodiment of this disclosure, the determining module 1602 is further configured to:

[0265] The user plane network element determines the network terminal association relationship of the cardless service terminal of the sender of the traffic data based on the network address;

[0266] The user plane network element interacts with the cardless service terminal according to the service policy rules and feeds back the traffic data to the connection management network element.

[0267] In one exemplary embodiment of this disclosure, the receiving module 1606 is further configured to:

[0268] The card-enabled network terminal performs network terminal identity registration and user identity registration;

[0269] In response to a user identity registration request from a cardless service terminal, the card-enabled network terminal establishes a user plane connection using its network terminal identity.

[0270] Receive a user identity registration request initiated by the cardless service terminal, the registration request including the identity identifier and authentication information;

[0271] Based on the authentication information, the cardless service terminal is authenticated, and the authentication result is fed back to the cardless service terminal as a successful registration response.

[0272] The discovery management network element in the core network element determines the discovery connection management network element corresponding to the session based on the network address;

[0273] The discovery management network element is triggered to synchronize the registration information of the cardless service terminal to the connection management network element, and the connection management network element generates the context information of the cardless service terminal.

[0274] In one exemplary embodiment of this disclosure, the user identity registration request is transmitted to the core network element based on the D2D connection between the cardless service terminal and the card-equipped network terminal.

[0275] In one exemplary embodiment of this disclosure, the D2D connection is a connection established in response to a network connection request between the card-enabled network terminal and / or the cardless service terminal.

[0276] In one exemplary embodiment of this disclosure, the network address is used to determine the network terminal association relationship between the card-enabled network terminal and the cardless service terminal.

[0277] In one exemplary embodiment of this disclosure, the network connection request is initiated by the cardless service terminal to the network via a SIM card network terminal with which it has a network terminal association.

[0278] Since the functions of the service control device 1500 and the service control device 1600 have been described in detail in their respective method embodiments, they will not be repeated here.

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

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

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

[0282] The electronic device 1700 according to this embodiment of the present invention will now be described with reference to FIG17. The electronic device 1700 shown in FIG17 is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0283] As shown in Figure 17, the electronic device 1700 is presented in the form of a general-purpose 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 storage unit 1720 and processing unit 1710).

[0284] The storage unit stores program code that can be executed by the processing unit 1710, causing the processing unit 1710 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 1710 can perform the method shown in the embodiments of this disclosure.

[0285] Storage unit 1720 may include readable media in the form of volatile storage units, such as random access memory (RAM) 17201 and / or cache memory 17202, and may further include read-only memory (ROM) 17203.

[0286] 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: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

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

[0288] Electronic device 1700 can also communicate with one or more external devices 1740 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 1700, and / or with any device that enables electronic device 1700 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1750. Furthermore, electronic device 1700 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1760. As shown, network adapter 1760 communicates with other modules of electronic device 1700 via bus 1730. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 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.

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

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

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

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

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

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

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

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

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

Claims

1. A service control method characterized by, The service control method suitable for a core network element comprises: Identity registration of service terminals, and generation of context information according to the identity registration message, wherein the context information comprises network terminal identity and user identity; Determination of a plurality of service terminals having an identity association relationship according to the context information, wherein the identity association relationship comprises a relationship having the same user identity or the same network terminal identity; Generation of service policy rules for the plurality of service terminals having the identity association relationship; Sending of services to the plurality of service terminals according to the service policy rules, so as to realize service linkage among the plurality of service terminals.

2. The service control method of claim 1, wherein, Identity registration of service terminals, and generation of context information according to the identity registration message, comprises: Network terminal identity registration of a first service terminal, and establishment of a user plane connection; User identity registration based on the user plane connection corresponding to the first service terminal, and storage of context information of the user identity corresponding to the first service terminal; Network terminal identity registration of a second service terminal, and establishment of a user plane connection; Triggering of user identity registration of a third service terminal based on the user plane connection corresponding to the second service terminal, and storage of context information of the user identity corresponding to the third service terminal, The first service terminal and the third service terminal are the plurality of service terminals having the identity association relationship.

3. The service control method of claim 2, wherein, Sending of services to the plurality of service terminals according to the service policy rules comprises: Identification of attribute information of a service corresponding to a service request; Determination of service policy rules corresponding to the attribute information, and forwarding of the service to the plurality of service terminals based on the service policy rules.

4. The service control method of claim 3, wherein, Generation of service policy rules for the plurality of service terminals having the identity association relationship comprises: Determination that the first service terminal and the third service terminal have the identity association relationship according to the context information; Aggregation of context information of the first service terminal and context information of the third service terminal; Generation of the service policy rules according to the aggregated context information, wherein the service policy rules comprise at least one of group communication rules, message synchronization rules and task cooperation rules.

5. The service control method of claim 4, wherein, Determination of service policy rules corresponding to the attribute information, and forwarding of the service to the plurality of service terminals based on the service policy rules comprises: Receiving of a service request of a first service terminal in the plurality of service terminals; Determination that a service requested by the first service terminal is a self-group service according to attribute information of the service request; Determination of group communication rules in the service policy rules corresponding to the self-group service; Feedback of data of the self-group service to the third service terminal according to the group communication rules.

6. The service control method of claim 4, wherein, Determination of service policy rules corresponding to the attribute information, and forwarding of the service to the plurality of service terminals based on the service policy rules further comprises: Response to a service sent to a specified user from outside a network; Determination that services of the plurality of service terminals are cross-service-terminal synchronization services according to attribute information of the service; Determination of message synchronization rules in the service policy rules corresponding to the cross-service-terminal synchronization services; According to the message synchronization rule, the service is replicated and fed back to the service terminal.

7. The service control method of claim 4, wherein, The service policy rule corresponding to the attribute information is determined, and the service is forwarded to the service terminal based on the service policy rule, and the method further comprises: in response to the collaborative task service issued to the specified user; According to the attribute information of the collaborative task service, the task cooperation rule in the service policy rule corresponding to the collaborative task service is determined; According to the task cooperation rule, the task is arranged and processed, and the arranged and processed tasks are sent to the terminal respectively.

8. A service control method characterized by, The service control method suitable for core network element, the service control method comprises: In response to the user identity registration information sent by the cardless service terminal to the network, the context information of the cardless service terminal is generated according to the user identity registration information, the context information includes the identity of the cardless service terminal, the network terminal identifier associated with the opposite end of D2D connection, the service policy rule of the cardless service terminal and the network address, the network address is the communication address of the cardless service terminal to which the network address in the terminal address segment allocated by the network is allocated by the card network terminal, and the service terminal with the network terminal association relationship is a plurality of service terminals connected to the network through the same network terminal D2D connection; The control plane element in the core network element sends the service policy rule to the cardless service terminal and the user plane element according to the context information, and the network controls the cardless service terminal based on the service policy rule; The user plane element in the core network element receives the traffic data fed back by the cardless service terminal through the D2D connection, and the traffic data meets the constraint of the service policy rule.

9. The service control method of claim 8, wherein, Further comprising: The control plane element determines the network terminal association relationship of the cardless service terminal of the traffic data according to the network address; The user plane element interacts with the cardless service terminal according to the service policy rule, and feeds back the traffic data to the connection management element.

10. The service control method according to claim 8 or 9, characterized by, Before generating the context information of the cardless service terminal according to the registration information of the cardless service terminal, further comprising: The card network terminal carries out network terminal identity registration and user identity registration; In response to the user identity registration request of the cardless service terminal, the card network terminal establishes the user plane connection with the network terminal identity; Receive the registration request of the user identity initiated by the cardless service terminal, the registration request includes the identity and authentication information; Based on the authentication information, the permission authentication result of the cardless service terminal is carried out, and the permission authentication result is fed back to the cardless service terminal as the response of registration success; The discovery management element in the core network element determines the connection management element corresponding to the session according to the source network address of the registration request; Trigger the discovery management element to synchronize the registration information of the cardless service terminal to the connection management element, and the connection management element generates the context information of the cardless service terminal.

11. The service control method of claim 10, wherein, The user identity registration request is transmitted to the core network element based on a D2D connection between the cardless service terminal or the card network terminal.

12. The service control method of claim 11, wherein, The D2D connection is a connection between the card network terminal and / or the cardless service terminal established in response to a networking request.

13. The service control method of claim 10, wherein, The network address is used to determine a network terminal association relationship between the card network terminal and the cardless service terminal.

14. The service control method of claim 12, wherein, The networking request is initiated by the cardless service terminal to the network via the card network terminal with which the network terminal association relationship exists.

15. A service control apparatus characterized by comprising: The service control device is suitable for a core network element, and comprises: A registration module configured to perform identity registration on the service terminal and generate context information according to a message of the identity registration, the context information comprising a network terminal identity and a user identity; A determination module configured to determine a plurality of service terminals with an identity association relationship according to the context information, the identity association relationship comprising a relationship with the same user identity or a relationship with the same network terminal identity; The determination module is configured to generate a service policy rule for the plurality of service terminals with the identity association relationship; An interaction module configured to send a service to the plurality of service terminals according to the service policy rule.

16. A service control apparatus characterized by comprising: The service control device is suitable for a core network element, and comprises: A determination module configured to generate context information of the cardless service terminal according to registration information of the cardless service terminal sent to the network in response to the registration information, the context information comprising an identity of the cardless service terminal, a network terminal identity associated with a D2D connection opposite end, a service policy rule of the cardless service terminal, and a network address, the network address being a network address in a terminal address segment allocated by a network to a communication address of the cardless service terminal with which a network terminal association relationship exists, the service terminal with which the network terminal association relationship exists being a plurality of service terminals ultimately accessing the network through the same network terminal via a D2D connection; A sending module configured to send the service policy rule to the cardless service terminal and a user plane network element according to the context information by a control plane network element in the core network element; The receiving module is further configured to receive traffic data fed back by the cardless service terminal via the D2D connection by the user plane network element, the traffic data satisfying a constraint of the service policy rule.

17. An electronic device, comprising: comprises: a memory; and a processor coupled to the memory, the processor being based on instructions stored in the memory to perform the service control method of any one of claims 1-14.

18. A computer readable storage medium having stored thereon a program which, when executed by a processor, implements the service control method of any one of claims 1-14.

19. A computer program product comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the service control method of any one of claims 1-14.

Images