Communication method, system and apparatus
Through information interaction and processing between the first network element and the second network element, the problem of intelligent proxy service providers sharing mobile network services of physical terminal devices is solved, the collaborative management and privacy protection of terminal devices and virtual terminal services are realized, and the flexibility and efficiency of services are improved.
Patent Information
- Application Number
- PCT/CN2025/082029
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-03-30
- Filing Date
- 2025-03-12
- Publication Date
- 2025-10-09
AI Technical Summary
How to support intelligent proxy service providers to share mobile network services on physical terminal devices, especially how to open network services under different implementation methods and business use cases.
Through information interaction and processing between the first network element and the second network element, including authentication, security processing, state synchronization, etc., collaborative management and control of terminal devices and virtual terminal services are achieved, supporting the flexibility and privacy protection of virtual terminal services.
It enables intelligent proxy service providers to share or use mobile network services of terminal devices, reduces power consumption and signaling interaction overhead, and enhances the flexibility and privacy protection of virtual terminal services.
Smart Images

Figure CN2025082029_09102025_PF_FP_ABST
Abstract
Description
Communication method, system and device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 30, 2024, with application number 202410385650.6 and application name “Communication Methods, Systems and Devices”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and more specifically, to a communication method, system, and device. Background Art
[0003] In recent years, artificial intelligence (AI) technology has begun to demonstrate remarkable operational assistance capabilities across various industries, including intelligent agents, digital humans, and AI robots. The integration of mobile network and AI technologies has also been a hot topic in recent years. In addition to providing connectivity for devices, mobile networks can also offer applications built-in intelligent services, such as exposing user route prediction information to third-party application service providers and providing applications with wireless network resource quality of service (QoS) prediction information.
[0004] With the rise of intelligent agent services, mobile networks can further open up user services within the mobile network to applications that support intelligent agents. Depending on the intelligent agent implementation method and service use case, the mobile network can open different network services for it. For example, if the intelligent agent is implemented on a cloud phone, the mobile network can simultaneously open traditional mobile voice and SMS services to the cloud phone with user authorization, and the intelligent agent can handle user-related services (such as automatic answering, etc.). If the intelligent agent is an application on the terminal, the mobile network can open some user information to the application service provider based on the user's authorization, for example, to manage communications between multiple devices for the terminal user, offload the application's computing power to be executed within the mobile network, and so on.
[0005] Therefore, how to support intelligent proxy service providers to share mobile network services of physical terminal devices is a technical problem that needs to be solved urgently. Summary of the Invention
[0006] The present application provides a communication method, system and apparatus that can support intelligent proxy service providers to share mobile network services of physical terminal devices.
[0007] In a first aspect, a communication method is provided, which is applied to a first network element, including: receiving first information, the first information including a first parameter, the first parameter being a parameter configured by a second network element for a terminal device, the second network element being a network element providing a virtual terminal service, and the first information being information related to the virtual terminal service; and sending second information, the second information indicating a response result to the first information, the response result to the first information being related to the first parameter.
[0008] The execution entity of the solution described in the first aspect may be the first network element, a module within the first network element (such as a chip system), or a logical node, logic module, or software that implements all or part of the functions of the first network element, without limitation. For ease of description, the following description uses the first network element as an example.
[0009] In the above solution, the first information is information related to the virtual terminal service. For example, the first information is information for requesting the virtual terminal service. For another example, the first information is information for requesting the second network element to activate or provide the virtual terminal service.
[0010] When the terminal device or the second network element sends information including parameters configured by the second network element for the terminal device to the first network element, the first network element can perform authentication or security processing on the information based on the parameters, and then determine whether to agree or allow the content requested by the information. In this way, the embodiment of the present application can support the second network element to share or use the mobile network service of the terminal device.
[0011] One possible implementation method is sending the second information, including: sending third information to the second network element, the third information requesting the second network element to respond to the first information, the third information including the first parameter; receiving fourth information from the second network element, the fourth information indicating the response result to the first information; and sending the second information.
[0012] In this way, the first network element can request the second network element to perform response processing on the first information, which can reduce the power consumption of the first network element.
[0013] In one possible implementation, sending the second information includes: receiving a first parameter from a second network element; determining the second information based on the first parameter; and sending the second information.
[0014] In this way, the first network element can complete the authentication response processing of the first information by itself, which can reduce the signaling interaction overhead between the first network element and the second network element.
[0015] In a possible implementation, before receiving the first information, the method further includes: sending capability information, where the capability information indicates that the first network element can support the virtual terminal service.
[0016] In this way, when the terminal device determines that the first network element supports the virtual terminal service based on the capability information, the terminal device sends the first information to the first network element, thereby supporting the second network element to share the mobile network service of the terminal device.
[0017] In a possible implementation, the capability information includes a first identifier, where the first identifier is an identifier used by the terminal device in the virtual terminal service.
[0018] In this way, the terminal device can use the identifier to interact with other network elements regarding the virtual terminal service, which can protect the privacy information of the terminal device.
[0019] In one possible implementation, the method further includes: receiving fifth information, the fifth information indicating an association between the terminal device and the second network element; and determining the association between the terminal device and the second network element based on the fifth information.
[0020] When the first network element determines the association between the terminal device and the second network element, the first network element may establish a context for the second network element to process data or signaling for the terminal device.
[0021] In one possible implementation, the method further includes: sending sixth information to the third network element, where the sixth information indicates an information processing rule, and the information processing rule is used by the third network element to send information related to the terminal device to the second network element.
[0022] In this way, the third network element can send information related to the terminal device to the second network element according to the information processing rule, which can support the second network element to process information related to the terminal device, thereby reducing the processing power consumption of the terminal device.
[0023] In one possible implementation, the method further includes: receiving seventh information from the terminal device, the seventh information indicating information on the status operation of the second network element; and sending eighth information to the second network element, the eighth information indicating information on the status operation of the second network element.
[0024] Through the above solution, the terminal device can operate or manage the state of the second network element, thereby supporting the synchronization between the state of the terminal device and the state of the second network element.
[0025] In one possible implementation, the method further includes: determining status information of the terminal device; sending ninth information to the second network element, the ninth information indicating information on status operation of the second network element, the information on status operation of the second network element being related to the status information of the terminal device.
[0026] Through the above solution, the first network element can operate or manage the state of the second network element, thereby supporting the synchronization between the state of the terminal device and the state of the second network element.
[0027] In one possible implementation, the method further includes: receiving tenth information from the second network element, the tenth information requesting the virtual terminal service, the tenth information including a second parameter, and the second parameter being a parameter configured by the terminal device for the second network element; sending eleventh information to the terminal device, the eleventh information requesting the terminal device to respond to the tenth information, the eleventh information including the second parameter; receiving twelfth information from the terminal device, the twelfth information indicating a response result to the tenth information; and sending thirteenth information to the second network element, the thirteenth information indicating a response result to the tenth information.
[0028] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0029] In one possible implementation, the method further includes: receiving fourteenth information from the second network element, the fourteenth information requesting the virtual terminal service; sending fifteenth information to the terminal device, the fifteenth information requesting the terminal device to respond to the fourteenth information, the fifteenth information including a third parameter, the third parameter being a parameter configured by the first network element for the second network element; receiving sixteenth information from the second network element, the sixteenth information including the third parameter; and sending seventeenth information to the second network element, the seventeenth information indicating a response result to the fourteenth information.
[0030] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0031] In one possible implementation, the method further includes: receiving eighteenth information from the terminal device, the eighteenth information requesting the virtual terminal service; sending nineteenth information to the terminal device, the nineteenth information including a fourth parameter, which is a parameter configured by the first network element for the terminal device; receiving twentieth information from the second network element, the twentieth information including the fourth parameter; and sending twenty-first information to the terminal device, the twenty-first information indicating a response result to the eighteenth information.
[0032] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0033] In a second aspect, a communication method is provided, which is applied to a terminal device, including: sending first information to a first network element, the first information including a first parameter, the first parameter being a parameter configured for the terminal device by a second network element, the second network element being a network element providing a virtual terminal service, and the first information being information related to the virtual terminal service; receiving second information from the second network element, the second information indicating a response result to the first information, the response result to the first information being related to the first parameter.
[0034] The execution entity of the solution described in the second aspect can be a terminal device, a module in the terminal device (such as a chip system, etc.), or a logical node, logic module, or software that can implement all or part of the terminal device functions, without limitation. For ease of description, the following description uses a terminal device as an example.
[0035] In the above solution, the first information is information related to the virtual terminal service. For example, the first information is information for requesting the virtual terminal service. For another example, the first information is information for requesting the second network element to activate or provide the virtual terminal service.
[0036] When the terminal device sends information including parameters configured by the second network element for the terminal device to the first network element, the first network element can perform authentication or security processing on the information based on the parameters, and then determine whether to agree or allow the content requested by the information. In this way, the embodiment of the present application can support the second network element to share or use the mobile network service of the terminal device.
[0037] In a possible implementation, the method further includes: sending a request message to the second network element, the request message requesting the virtual terminal service; and receiving a response message from the second network element, the response message including the first parameter.
[0038] When the second network element supports providing virtual terminal services, the second network element configures the first parameter for the terminal device, and the first network element responds to the first information according to the first parameter, thereby supporting the second network element to share or use the mobile network service of the terminal device.
[0039] In a possible implementation, before sending the first information to the first network element, the method further includes: receiving capability information from the first network element, where the capability information indicates that the first network element can support the virtual terminal service.
[0040] In this way, when the terminal device determines that the first network element supports the virtual terminal service based on the capability information, the terminal device sends the first information to the first network element, thereby supporting the second network element to share the mobile network service of the terminal device.
[0041] In a possible implementation, the capability information includes a first identifier, where the first identifier is an identifier used by the terminal device in the virtual terminal service.
[0042] In this way, the terminal device can use the identifier to interact with other network elements regarding the virtual terminal service, which can protect the privacy information of the terminal device.
[0043] In one possible implementation, the method further includes: sending third information to the second network element, where the third information indicates an association between the terminal device and the second network element.
[0044] When the first network element determines the association between the terminal device and the second network element, the first network element may establish a context for the second network element to process data or signaling for the terminal device.
[0045] In one possible implementation, the method further includes: sending fourth information to the first network element, where the fourth information indicates information on a status operation of the second network element.
[0046] Through the above solution, the terminal device can operate or manage the status of the second network element or the virtual terminal in the second network element, thereby supporting the synchronization between the status of the terminal device and the status of the second network element or the virtual terminal in the second network element.
[0047] In one possible implementation, the method further includes: receiving fifth information from the first network element, where the fifth information indicates an updated state of the second network element.
[0048] In this way, the terminal device can obtain the updated status of the second network element.
[0049] In one possible implementation, the method further includes: receiving sixth information from the first network element, the sixth information requesting a response to seventh information, the seventh information being used by the second network element to request the virtual terminal service, the seventh information including a second parameter, the second parameter being a parameter configured by the terminal device for the second network element, the sixth information including the second parameter; and sending eighth information to the first network element, the eighth information indicating a response result to the seventh information.
[0050] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0051] In one possible implementation, the method further includes receiving ninth information from the first network element, the ninth information requesting a response to the tenth information, the tenth information being used by the second network element to request the virtual terminal service, the ninth information including a third parameter, the third parameter being a parameter configured by the first network element for the second network element; and sending the third parameter to the second network element.
[0052] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0053] In one possible implementation, the method further includes: sending tenth information to the first network element, the tenth information requesting the virtual terminal service; receiving eleventh information from the first network element, the eleventh information including a fourth parameter, the fourth parameter being a parameter configured by the first network element for the terminal device; sending the fourth parameter to the second network element; and receiving twelfth information from the first network element, the twelfth information indicating a response result to the tenth information.
[0054] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0055] According to a third aspect, a communication method is provided, which is applied to a second network element, and includes: receiving first information from a first network element, the first information requesting a response to second information from a terminal device, the first information including a first parameter, the first parameter being a parameter configured by the second network element for the terminal device, the second network element being a network element providing a virtual terminal service, the second information including the first parameter, the second information being information related to the virtual terminal service; and sending third information to the first network element, the third information indicating a response result to the second information, the third information being used by the first network element to determine fourth information, the fourth information indicating a response result to the second information.
[0056] The execution entity of the solution described in the first aspect can be the second network element, or a module in the second network element (such as a chip system, etc.), or a logical node, logical module, or software that can implement all or part of the functions of the second network element, without limitation. For ease of description, the following description uses the second network element as an example.
[0057] In the above solution, the first information is information related to the virtual terminal service. For example, the first information is information for requesting the virtual terminal service. For another example, the first information is information for requesting the second network element to activate or provide the virtual terminal service.
[0058] When the first network element sends information including parameters configured by the second network element for the terminal device to the second network element, the second network element can perform authentication or security processing on the information based on the parameters, and then determine whether to agree or allow the content requested by the information. In this way, the embodiment of the present application can support the second network element to share or use the mobile network service of the terminal device.
[0059] In one possible implementation, before receiving the first information from the first network element, the method further includes: receiving request information from a terminal device, the request information requesting a virtual terminal service; and sending response information to the terminal device, the response information including the first parameter.
[0060] When the second network element supports providing virtual terminal services, the second network element configures the first parameter for the terminal device, and the first network element responds to the first information according to the first parameter, thereby supporting the second network element to share or use the mobile network service of the terminal device.
[0061] In one possible implementation, the method further includes: receiving fifth information from the first network element, the fifth information indicating information on the status operation of the second network element; and sending sixth information to the first network element, the sixth information indicating a response result to the fifth information.
[0062] Through the above scheme, the embodiment of the present application can support the synchronization between the status of the terminal device and the status of the second network element.
[0063] In one possible implementation, the method further includes: receiving seventh information from the first network element, the seventh information indicating information on status operation of the second network element, the information on status operation of the second network element being related to the status of the terminal device; and sending eighth information to the first network element, the eighth information indicating the updated status of the second network element.
[0064] Through the above solution, the embodiment of the present application can support synchronization between the state of the terminal device and the state of the second network element. In one possible implementation, the method further includes: sending ninth information to the first network element, the ninth information indicating the updated state of the second network element.
[0065] In one possible implementation, the method further includes: sending a tenth message to a third network element, the tenth message requesting the virtual terminal service, the tenth message including a second parameter, the second parameter being a parameter configured by the terminal device for the first network element; and receiving an eleventh message sent from the third network element, the eleventh message indicating a response result to the tenth message.
[0066] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0067] In one possible implementation, the method further includes: sending twelfth information to a third network element, the twelfth information requesting the virtual terminal service; receiving a third parameter from the terminal device, the third parameter being a parameter configured by the third network element for the first network element; sending thirteenth information to the third network element, the third information including the third parameter; and receiving fourteenth information from the third network element, the fourteenth information indicating a response result to the twelfth information.
[0068] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0069] In one possible implementation, the method further includes: receiving a fourth parameter from the terminal device, the fourth parameter being a parameter configured by the third network element for the terminal device; and sending fifteenth information to the third network element, the fifteenth information including the fourth parameter, the fourth parameter being used to respond to sixteenth information from the terminal device, the sixteenth information requesting the virtual terminal service.
[0070] Through the above solution, the second network element can actively request to provide the virtual terminal service, thereby enhancing the flexibility of the virtual terminal service.
[0071] In a fourth aspect, a communication device is provided. The communication device may be a first network element, or may be a device or module for performing the function of the first network element.
[0072] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0073] In a fifth aspect, a communication device is provided, which may be a terminal device, or a device or module for executing the functions of a terminal device.
[0074] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0075] In a sixth aspect, a communication device is provided. The communication device may be a second network element, or may be a device or module for performing the function of the second network element.
[0076] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.
[0077] In the seventh aspect, a communication device is provided, comprising a processor, wherein the processor is used to, by executing a computer program or instruction, or by a logic circuit, enable the communication device to execute the method described in the first aspect and any possible manner of the first aspect; or, enable the communication device to execute the method described in the second aspect and any possible manner of the second aspect; or, enable the communication device to execute the method described in the third aspect and any possible manner of the third aspect.
[0078] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.
[0079] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.
[0080] In an eighth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any possible manner of the first aspect; or, the logic circuit being used to execute the method described in the second aspect and any possible manner of the second aspect; or, the logic circuit being used to execute the method described in the third aspect and any possible manner of the third aspect.
[0081] In the ninth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any possible embodiment of the first aspect is executed; or, the method described in the second aspect and any possible manner of the second aspect is executed; or, the method described in the third aspect and any possible manner of the third aspect is executed.
[0082] In the tenth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible manner of the first aspect to be executed; or, cause the method described in the second aspect and any possible manner of the second aspect to be executed, or, cause the method described in the third aspect and any possible manner of the third aspect to be executed.
[0083] In the eleventh aspect, a chip system is provided, comprising: a processor, which is used to execute the computer program or instructions in the memory, so that the chip system implements the method in the first aspect and any possible implementation of the first aspect; or, enables the chip system to implement the method in the second aspect and any possible implementation of the second aspect; or, enables the chip system to implement the method in the third aspect and any possible implementation of the third aspect.
[0084] For the description of the beneficial effects of any of the fourth to eleventh aspects, reference can be made to the description of the beneficial effects of the first to third aspects, and no further details will be given. BRIEF DESCRIPTION OF THE DRAWINGS
[0085] FIG1 is a schematic diagram of the architecture of a communication system 100 applicable to an embodiment of the present application.
[0086] FIG2 is a schematic diagram of a network architecture 200 applicable to an embodiment of the present application.
[0087] FIG3 is a schematic diagram of an interaction flow of a communication method 300 according to an embodiment of the present application.
[0088] FIG4 is a schematic diagram of an interaction flow of a communication method 400 according to an embodiment of the present application.
[0089] FIG5 is a schematic diagram of an interaction flow of a communication method 500 according to an embodiment of the present application.
[0090] FIG6 is a schematic diagram of an interaction flow of a communication method 600 according to an embodiment of the present application.
[0091] FIG7 is a schematic diagram of an interaction flow of a communication method 700 according to an embodiment of the present application.
[0092] FIG8 is a schematic diagram of an interaction flow of a communication method 800 according to an embodiment of the present application.
[0093] FIG9 is a schematic diagram of an interaction flow of a communication method 900 according to an embodiment of the present application.
[0094] FIG10 is a schematic diagram of the interaction flow of a communication method 1000 according to an embodiment of the present application.
[0095] FIG11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application.
[0096] FIG12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. DETAILED DESCRIPTION
[0097] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.
[0098] 1. Unless otherwise specified, “a plurality of or at least two” means two or more.
[0099] 2. Unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.
[0100] 3. The various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of protection of the present application. The size of the serial numbers involved in the present application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of the present application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.
[0101] At the same time, any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.
[0102] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.
[0103] In the embodiments of the present application, "used to indicate" can be understood as "enabling," and "enabling" can include both direct and indirect enabling. When describing that certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and does not necessarily mean that the information contains A.
[0104] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the enabled information, such as but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, it is also possible to enable specific information with the help of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.
[0105] 6. "Storage" or "saving" as used in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated into a decoder, a processor, or a communication device. The type of memory may be any form of storage medium and is not limited thereto.
[0106] 7. The “protocol” involved in the embodiments of the present application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, the sixth generation (6 th generation, 6G) network protocols and related protocols used in future communication systems, which are not limited in this application.
[0107] 8. The dotted arrows or boxes in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.
[0108] 9. In the embodiments of the present application, unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. “And / or” in the present application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. Among them, A and B can be singular or plural.
[0109] 10. In the embodiments of the present application, indications include direct indications (also called explicit indications) and implicit indications. Direct indication of information A refers to including information A. Implicit indication of information A refers to indicating information A through the correspondence between information A and information B and the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.
[0110] 11. In the embodiments of the present application, information C is used to determine information D, which includes information D being determined solely based on information C, as well as information D being determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, where information D is determined based on information E, and information E is determined based on information C.
[0111] 12. In the embodiment of the present application, "device A sends information A to device B" can be understood as the destination end of the information A or the intermediate network element in the transmission path between the destination end and the device B, which may include sending information to device B directly or indirectly.
[0112] 13. In the embodiments of this application, the phrase "Device B receives information A from Device A" can be understood to mean that the source of information A or an intermediate network element in the transmission path between the source and the device A is Device A, and may include directly or indirectly receiving the information from Device A. Information may undergo necessary processing between the source and destination, such as formatting changes, but the destination can still understand the valid information from the source. Similar expressions in this application should be understood similarly and are not elaborated on here.
[0113] For ease of description and understanding, the following description is made from the aspects of communication system, method and device.
[0114] 1. Communication system
[0115] In order to solve the problem described in the background technology section, the present application provides a communication system that can support intelligent proxy service providers to share mobile network services of physical terminal devices.
[0116] Figure 1 is a schematic diagram of the architecture of a communication system 100 applicable to an embodiment of the present application. As shown in Figure 1, the communication system 100 includes: a terminal device, a first network element, and a second network element. The terminal device, the first network element, and the second network element are located in a mobile network, such as a cellular network.
[0117] In communication system 100, the second network element is a network element that provides or supports the provision of a virtual terminal service. For example, the virtual terminal service can be replaced by an intelligent proxy service, providing a virtual terminal or intelligent proxy, or other intelligent services. Therefore, the virtual terminal service described in the embodiments of the present application can be an intelligent proxy service provided or supported by an intelligent proxy service provider, but this is only an example and not a final definition. For ease of description, the following description uses the virtual terminal service as an example, but other terminology is not limited. Accordingly, the second network element can be an intelligent proxy service provider or an entity with similar functions to an intelligent proxy service provider.
[0118] In the communication system 100, the first network element controls or manages the mobile network service of the terminal device shared or used or applied by the second network element, or the first network element manages the mobile network connection or mobile network service between the terminal device and the second network element, for example, service authorization, maintenance of the binding relationship between the terminal device and the second network element, receiving and processing service requests from the terminal device and / or the second network element, etc.
[0119] In the communication system 100, the second network element can configure parameters for security processing (including but not limited to authentication, certification, or authorization) for the terminal device. When the terminal device or the second network element sends information carrying these parameters to the first network element, the first network element can respond to the information based on these parameters. For example, if the information is used to request the provision of a virtual terminal service, the first network element can determine whether to allow the second network element to provide the virtual terminal service based on these parameters. In this way, based on the above mechanism, embodiments of the present application can support the second network element sharing the mobile network service of the terminal device.
[0120] For ease of description, the following description uses an example where the first network element is a virtual terminal controller (e.g., a virtual user equipment controller, VUEC) and the second network element is a virtual terminal agent (e.g., a virtual user equipment agent, VUE Agent) or a virtual terminal service. Other terminology is not limited. The first network element manages and controls the virtual terminal service, while the second network element provides the virtual terminal service.
[0121] Optionally, the VUEC may be a virtual agent that can be used to control the virtual terminal service. The virtual agent may be a component in an application function (AF), which is not limited to this.
[0122] Optionally, the VUE Agent may be a controller, such as a virtual terminal controller, etc., which is not limited to this.
[0123] In an embodiment of the present application, a terminal device is a device with wireless transceiver capabilities, which may refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal device may also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a wireless modem, a machine type communication device, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), customer-premises equipment (CPE), a smart point of sale (POS) machine, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a terminal in device-to-device (D2D) communication, a terminal in vehicle-to-everything (V2X), a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a telemedicine or telehealth There are no restrictions on wireless terminals in wireless services, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, or terminal devices in communication networks evolved after 5G.
[0124] The communication device used to implement the functions of the terminal device can be the terminal device; it can also be a device that can support the terminal device to implement the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In this application, the chip system can be composed of a chip or include a chip and other discrete devices.
[0125] The communication system 100 can be applied to the following systems or scenarios: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, universal mobile telecommunication system (UMTS), 5G system or NR system, 6G system and other systems evolved after 5G, inter-satellite communication and satellite communication and other non-terrestrial network (NTN) systems. Among them, the satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services for the terminal equipment. The satellite base station can also communicate with the ground base station. The satellite can be used as a base station or as a terminal device. Among them, the satellite can refer to non-ground base stations or non-ground equipment such as drones, hot air balloons, low-orbit satellites, medium-orbit satellites, and high-orbit satellites.
[0126] The technical solution disclosed by communication system 100 is applicable to both homogeneous and heterogeneous network scenarios. There are no restrictions on the transmission points. It can be multi-point coordinated transmission between macro base stations, micro base stations, and macro base stations. It is applicable to both FDD and TDD systems. The technical solution disclosed by the communication system shown in Figure 1 is applicable not only to low-frequency scenarios (sub 6G), but also to high-frequency scenarios (above 6GHz), terahertz, optical communications, etc.
[0127] The technical solution disclosed in communication system 100 can also be applied to scenarios where a terminal device is connected to a single base station, where the base station to which the terminal device 130 is connected and the core network (CN) to which the base station is connected are of the same standard. For example, if the CN is 5G Core, the corresponding base station is a 5G base station, and the 5G base station is directly connected to the 5G Core; or if the CN is 6G Core, the base station is a 6G base station, and the 6G base station is directly connected to the 6G Core.
[0128] The technical solution disclosed by the communication system 100 can also be applied to macro and micro scenarios composed of base stations of different forms in the communication network. For example, the base station can be a satellite, an aerial balloon station, a drone station, etc.
[0129] The technical solution disclosed by the communication system 100 is also suitable for scenarios where wide-coverage base stations and small-coverage base stations coexist.
[0130] The technical solution disclosed by the communication system 100 can be applied to scenarios with high reliability business requirements, such as ports, industrial manufacturing, transportation, and coal mines.
[0131] The technical solution disclosed by the communication system 100 can also be applied to 5.5G, 6G and later wireless communication systems, and applicable scenarios include but are not limited to terrestrial cellular communications, NTN, satellite communications, high altitude platform station (HAPS) communications, V2X, integrated access and backhaul (IAB) and reconfigurable intelligent surface (RIS) communications.
[0132] The following description takes the application of the communication system 100 to a 5G network architecture as an example.
[0133] FIG2 is a schematic diagram of a network architecture 200 applicable to an embodiment of the present application. As shown in FIG2 , the network architecture 200 may include:
[0134] 1. Access and mobility management function (AMF)
[0135] The AMF mainly performs functions such as mobility management or access authentication / authorization. The AMF is also responsible for transmitting user policies between the terminal device and the policy control function (PCF). The AMF can receive the non-access stratum (NAS) signaling of the terminal device (including mobility management (MM) signaling and session management (SM) signaling) and related signaling of the access network device (for example, the base station-level next generation (NG) 2 interface signaling that interacts with the AMF), complete the user registration process and forwarding of SM signaling as well as mobility management.
[0136] 2. Session management function (SMF)
[0137] SMF is primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, and charging interfaces, and downlink data notification. SMF can also be used to complete processes related to the establishment, release, and update of protocol data unit (PDU) sessions.
[0138] 3. PCF
[0139] PCF can be responsible for user policy management, including both mobility-related policies and PDU session-related policies, such as QoS policies and billing policies.
[0140] 4. Unified data repository (UDR)
[0141] UDR mainly includes the following functions:
[0142] 1) Unified data management (UDM) function stores or reads subscription data;
[0143] 2) PCF stores policy data or reads policy data;
[0144] 3) Store or read the exposed data.
[0145] The UDR and the network function (NF) accessing it have the same public land mobile network (PLMN), that is, they are in the same network, that is, the Nudr interface is a PLMN internal interface.
[0146] 5. UDM
[0147] UDM mainly includes the following functions: unified data management, support for authentication credentials processing in 3GPP authentication and key negotiation mechanism, user identity processing, access authorization, registration and mobility management, contract management and short message management.
[0148] 6. Application function (AF)
[0149] AF mainly includes the following functions: interacting with the 3GPP core network to provide business or services, including: interacting with the network element function (NEF) and policy architecture interaction.
[0150] 7. User plane function (UPF)
[0151] As the interface with the data network, the UPF performs functions such as user plane data forwarding, session / flow-level billing and statistics, and bandwidth limiting. This includes packet routing and forwarding, as well as QoS processing for user plane data.
[0152] 8. Radio access network (RAN)
[0153] RAN can manage wireless resources, provide access services for terminal devices, and complete the forwarding of terminal device data between the terminal device and the core network. RAN can also be understood as a base station. Please refer to the previous description for details.
[0154] 9. Data network (DN)
[0155] DN is used to provide, for example, operator services, Internet access, or third-party services, and includes a server that implements video source encoding and rendering.
[0156] In the above description, the network element can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). The functional network element can be divided into one or more services, and further, there may be services that exist independently of the network function. An instance of the functional network element, an instance of a service included in the functional network element, or an instance of a service that exists independently of the network function can be referred to as a service instance.
[0157] As can be seen from Figure 2, the terminal device accesses the network through the RAN, the terminal device communicates with the AMF through the NG1 interface (N1 for short), the access network device communicates with the AMF through the NG2 interface (N2 for short), the access network device communicates with the UPF through the NG3 interface (N3 for short), the AMF communicates with the SMF through the NG11 interface (N11 for short), the AMF communicates with the UDM through the NG8 interface (N8 for short), the AMF communicates with the PCF through the NG15 interface (N15 for short), the SMF communicates with the PCF through the NG7 interface (N7 for short), the SMF communicates with the UPF through the NG4 interface (N4 for short), the UPF accesses the DN through the NG6 interface (N6 for short), the UDM communicates with the UDR through the NG35 interface (N35 for short), the PCF communicates with the UDR through the NG36 interface (N36 for short), etc.
[0158] The names of the network elements shown in Figure 2 are just names and do not limit the functions of the network elements themselves. In 5G networks and other future networks, the above network elements may also have other names, and this embodiment of the application does not specifically limit this. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may have other names, etc.
[0159] The network architecture 200 is only described as an example. The network architecture 200 may also include other network elements, such as an authentication server function (AUSF) and NEF.
[0160] The VUEC in the communication system 100 can be deployed in the network architecture 200. It can be deployed independently or integrated with other NFs, for example, the VUEC can be integrated with the SMF, which is not limited to this. In addition, the VUE Agent can be an AF or a component of an AF.
[0161] It should be noted that when VUEC and VUE Agent are applied to the core network architecture, the embodiments of the present application do not limit the deployment form and deployment location of VUEC and VUE Agent.
[0162] In addition, the "network element" in this article may also be referred to as a network function instance, NF, equipment, device or module, etc., which is not specifically limited in this application. In addition, the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation. This application does not exclude the possibility of adopting other naming in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above-mentioned networks may continue to use the terminology in 5G, or may adopt other names, etc. The interface name between the above-mentioned network elements is only an example. The name of the interface in the specific implementation may be other names, and there is no specific limitation on this. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.
[0163] 2. Communication method
[0164] For ease of understanding and explanation, the following describes the communication method of the embodiment of the present application using the first network element as a VUEC, the second network element as a VUE Agent, and the interaction between the first network element, the second network element, and the terminal device as an example. However, this does not limit the execution subject of the communication method of the embodiment of the present application. For example, the method executed by a network element (such as a VUEC or a VUE Agent) may also be executed by a module (such as a circuit, a chip, or a chip system) of the network element, and may also be implemented by a logical node, a logical module, or software that can implement all or part of the functions of the network element. The method executed by a terminal device may be executed by a module (such as a circuit, a chip, or a chip system) of the terminal device, and may also be implemented by a logical node, a logical module, or software that can implement all or part of the functions of the terminal device.
[0165] FIG3 is a schematic diagram of an interaction flow of a communication method 300 according to an embodiment of the present application. As shown in FIG3 , the communication method 300 includes:
[0166] S301. VUEC receives first information.
[0167] The first information is information related to the virtual terminal service, or the content requested, carried or indicated by the first information is related to the virtual terminal service.
[0168] In a possible embodiment, the VUEC receives the first information from the terminal device, or the VUEC receives the first information from the terminal device via another AF, such as a RAN.
[0169] Optionally, the first information is information for requesting the VUE Agent to activate or provide a virtual terminal service.
[0170] Optionally, the first information includes a first parameter related to the terminal device sending the first information. The first parameter is pre-configured by the VUE Agent for the terminal device. In some embodiments, the first parameter can be a token, a key, or a verification code. The first parameter can be used for security-related processing. For example, the VUEC can perform security or authentication processing on the first information based on the first parameter.
[0171] In a possible example, the first information is used by the terminal device to request the VUE Agent to provide a virtual terminal service. The first information includes a first parameter. The VUEC performs authentication and / or authorization processing on whether to approve the VUE Agent to provide the virtual terminal service based on the first parameter.
[0172] In another possible embodiment, the VUEC receives the first information from the VUE Agent, or the VUEC receives the first information from the VUE Agent via another AF (not limited). Optionally, the first information is information for requesting provision of a virtual terminal service.
[0173] Optionally, the first information includes a first parameter configured by the VUE Agent for the terminal device. For example, the first parameter may be a token, a key, or a verification code. The first parameter may be used for security-related processing. For example, the VUEC may perform security or authentication processing on the first information based on the first parameter, which is not limited to this. For example, the VUEC interacts with the terminal device (e.g., the terminal device has stored the first parameter) regarding the first parameter based on the first parameter to facilitate authentication and other processing of the first information. For another example, before the VUE Agent sends the first information to the VUEC, the VUE Agent has already sent or configured the first parameter to the VUEC. When the VUE Agent sends the first information including the first parameter to the VUEC, the VUEC may verify the first parameter included in the first information based on the configured first parameter, thereby completing authentication and other processing of the first information.
[0174] S302: The VUEC sends second information, where the second information is used to respond to the first information.
[0175] When the VUEC receives the first information from the terminal device, the VUEC sends second information to the terminal device, where the second information indicates a response result to the first information.
[0176] When the VUEC receives the first information from the VUE Agent, the VUEC sends the second information to the VUE Agent, where the second information indicates a response result to the first information.
[0177] The above-mentioned response result to the first information is related to the first parameter, or the above-mentioned response result to the first information is determined according to the first parameter.
[0178] When the first information comes from the terminal device, the VUEC determines the second information according to any of the following methods:
[0179] Method #1:
[0180] The VUEC sends a third message to the VUE Agent, where the third message requests the VUE Agent to respond to the first message, and the third message includes the first parameter;
[0181] The VUE Agent sends fourth information to the VUEC, where the fourth information indicates a response result to the first information.
[0182] In the embodiment of the present application, the third information is information determined by the VUEC based on the first information. For example, the third information is the same as the first information. For another example, the third information is different from the first information. For example, the third information includes all or part of the content of the first information and request information for requesting the VUE Agent to respond to the first information, etc., which is not limited to this.
[0183] In a possible example, the first information includes the identification information and the first parameter of the virtual terminal service. The third information includes the identification information, the first parameter of the virtual terminal service, and information for requesting the VUE Agent to authenticate the virtual terminal service.
[0184] When the VUE Agent receives the third message sent by the VUEC, the VUE Agent can determine whether the terminal device is an authorized device based on the first parameter included in the third message. If so, the VUE Agent sends a fourth message to the VUEC, indicating that the terminal device is an authorized device. The VUEC determines that it approves the request in the first message and indicates the result of its response to the first message (e.g., approving the terminal device's request for the VUE Agent to provide virtual terminal services) in a second message sent to the terminal device. If the VUE Agent determines that the terminal device is not an authorized device based on the first parameter included in the third message, the VUE Agent sends a fourth message to the VUEC indicating that the terminal device is not authorized. The VUEC determines that it disapproves the request in the first message and indicates the result of its response to the first message (e.g., rejecting the terminal device's request for the VUE Agent to provide virtual terminal services) in a second message sent to the terminal device. In this embodiment, the VUEC can request the VUE Agent to process the first message (e.g., perform authentication or authorization) to reduce VUEC power consumption.
[0185] In some embodiments, the VUE Agent pre-configures parameters for the terminal device used to authenticate whether the terminal device is a VUE Agent-authorized device. When the terminal device sends a first message to the VUEC to initiate a virtual terminal service request, the first message carries the configured parameters. Upon receiving the first message forwarded by the VUEC and sent by the terminal device, or upon receiving a third message containing the configured parameters, the VUE Agent compares the parameters carried in the first message or the third message with the parameters of the VUE Agent. If the two are identical or meet a predetermined correspondence or predetermined requirements, the terminal device is deemed to be a device authorized by the VUE Agent; otherwise, the terminal device is deemed not to be a device authorized by the VUE Agent.
[0186] In some embodiments, the VUE Agent pre-sends information about the terminal device authorized by the VUE Agent, such as parameters configured by the VUE Agent for the terminal device, and / or parameters that have a corresponding relationship or a specific matching relationship with the parameters configured by the VUE Agent for the terminal device, and such corresponding relationship or matching relationship, to the VUEC, or configures such information locally on the VUEC. In this way, the VUEC can determine whether the terminal device is a device authorized by the VUE Agent based on this information and the parameters in the first information sent by the terminal device. If so, the response result to the first information is indicated in the second information (for example, approving the request of the terminal device to request the VUE Agent to provide a virtual terminal service); if not, the response result to the first information is indicated in the second information (for example, rejecting the request of the terminal device to request the VUE Agent to provide a virtual terminal service).
[0187] Method #2:
[0188] VUE Agent sends the first parameter to VUEC;
[0189] The VUEC determines the second information according to the first parameter.
[0190] After the VUE Agent configures the first parameter for the terminal device, it sends the first parameter to the terminal device and the VUEC. When the terminal device sends a first message including the first parameter to the VUEC, the VUEC can determine whether to approve or allow the request for the first message based on whether the first parameter from the VUE Agent is consistent with the first parameter in the first message. In this way, the VUEC can independently complete the response processing (such as authentication or authorization) for the first message, which can reduce the signaling interaction overhead between the VUEC and the VUE Agent.
[0191] When the first information comes from the VUE Agent, the VUEC can complete its response to the first information based on the first parameter. For example, the VUE Agent has sent the first parameter to the terminal device; when the VUE Agent sends the first information including the first parameter to the VUEC, the VUEC exchanges the first parameter with the terminal device and obtains a verification result of the first parameter from the terminal device. Based on the verification result, the VUEC determines whether to approve the VUE Agent to provide the virtual terminal service. For another example, the VUE Agent exchanges the first parameter with the VUEC. When the VUE Agent sends the first information including the first parameter to the VUEC, the VUEC can verify the first parameter carried in the first information based on the first parameter obtained from the aforementioned interaction and determine whether to approve the VUE Agent to provide the virtual terminal service based on the verification result.
[0192] Through the above process, when the terminal device or VUE Agent sends information including parameters configured by the VUE Agent for the terminal device to the VUEC, the VUEC can authenticate or perform security processing on the information based on the parameters, and then determine whether to agree or allow the content requested by the information. In this way, the embodiment of the present application can support the VUE Agent to share or use the mobile network services of the terminal device.
[0193] For further description of the above mechanism, please refer to FIG4 .
[0194] For ease of description, information is numbered with Arabic numerals below, but the numbers of the information appearing in Figures 4 to 10 are associated with the numbers of the information appearing in the aforementioned summary of the invention.
[0195] FIG4 is a schematic diagram of an interaction flow of a communication method 400 according to an embodiment of the present application. As shown in FIG4 , the communication method 400 includes:
[0196] Optionally, in S401 , the VUEC sends capability information to the terminal device.
[0197] Accordingly, the terminal device receives capability information indicating that the VUEC can support virtual terminal services. Thus, when the terminal device determines that the VUEC supports virtual terminal services based on the capability information, it sends the first information to the VUEC, thereby enabling the VUE Agent to share the mobile network service of the terminal device.
[0198] In one possible example, before receiving the capability information, the terminal device sends a service request message to the VUEC (for example, the terminal device sends the service request message because an APP on the terminal device needs to use the virtual terminal service). The service request message is used to request the VUEC to provide the virtual terminal service.
[0199] The above service request message may include at least one of the following: terminal identification of the terminal device, APP (entity for providing virtual terminal services or the aforementioned intelligent agent service provider) information, user identification in the APP (such as WeChat account, QQ number, etc.), etc.
[0200] The terminal device may send service request information to the VUEC through a RAN node or other NFs, such as AMF or SMF. When the terminal device sends the service request information to the VUEC through other NFs, the service request message may be carried in a message processed by the NF, such as a registration request message sent to the AMF, a PDU session establishment or change request message sent to the SMF, and so on.
[0201] In one possible example, the VUEC can proactively send capability information to the terminal device. For example, the terminal device may have a virtual terminal service subscription within its network. When the terminal device registers, it may include a capability indication for the virtual terminal service in its registration request information. The VUEC issues a virtual terminal service authorization indication (an example of capability information) to the terminal device based on the terminal device's subscription information, or based on the terminal device's subscription information and the capability indication for the virtual terminal service reported by the terminal device. This authorization indication may be included in registration completion information or user policies, without limitation.
[0202] In one possible implementation, the capability information includes a first identifier, which is an identifier used by the terminal device in the virtual terminal service. For example, the first identifier may be a UE temporary ID. In this way, the terminal device can use the first identifier to interact with other network elements regarding the virtual terminal service, which can protect the privacy information of the terminal device.
[0203] S402: The terminal device sends a request message to the VUE Agent.
[0204] Correspondingly, the VUE Agent receives the request information, wherein the request information is used to request the virtual terminal service, or the request information is used to request the VUE Agent to provide the virtual terminal service.
[0205] When the terminal device needs to use the virtual terminal service provided by the VUE Agent, the terminal device may send request information to the VUE Agent, and the request information may include the first identifier of the terminal device.
[0206] S403. VUE Agent sends response information to the terminal device.
[0207] Correspondingly, the terminal device receives the response information, which includes the first parameter.
[0208] When the VUE Agent supports providing virtual terminal services, the VUE Agent configures a first parameter for the terminal device, and the VUEC responds to the first information according to the first parameter, thereby enabling the VUE Agent to share or use the mobile network service of the terminal device.
[0209] In an embodiment of the present application, the VUE Agent can also provide the terminal device with an identity identifier (such as an APP UE ID) for identifying the terminal device within the VUE Agent. In this way, the terminal device can use the identity identifier to interact with the VUE Agent regarding the virtual terminal service, which can protect the privacy of the terminal device.
[0210] Optionally, after receiving the request message, the VUE Agent may send an authentication request message to the VUEC. The authentication request message is used to obtain the virtual terminal service authentication information of the terminal device. The virtual terminal service authentication information of the terminal device can be used to verify whether the terminal device can use the virtual terminal service through the operator network. The authentication request message carries the VUE Agent's identifier or a first identifier (e.g., a UE temporary ID).
[0211] If the VUE Agent does not obtain the first identifier of the terminal device, the VUE Agent may carry the international interconnection protocol (IP) address of the terminal device in the authentication request message, or other information used to identify the identity of the terminal device (such as a user permanent identifier (SUPI), a subscription concealed identifier (SUCI), a generic public subscription identifier (GPSI), etc., which may also be provided to the VUE Agent by the terminal device).
[0212] Optionally, if the authentication verification is passed, the VUE Agent may also provide security-related parameters to the VUEC. The security-related parameters may be used to perform security verification on subsequent service requests of the terminal device.
[0213] The interaction between VUE Agent and VUEC may vary depending on the deployment form of VUEC. For example, when VUEC is deployed as a standalone NF, VUE Agent can interact with VUEC through NEF. If VUEC is integrated into other NFs, such as AMF, SMF, UDM, or UPF, VUE Agent can interact with the VUEC-integrated NF through NEF.
[0214] If the VUE Agent cannot find the corresponding VUEC through the identification or address information provided by the terminal device, the VUE Agent can also first select the VUEC function or obtain the UE identification (such as UE temp ID, SUPI, etc.) through NEF or other network elements, and then interact with the VUEC.
[0215] S404: The terminal device sends information 1 (which may be the first information in FIG3 ) to the VUEC. The VUEC receives information 1.
[0216] In one possible example, information 1 includes identification information of the terminal device (such as a first identification), identification information of the VUE Agent, and a first parameter. Information 1 may also include related application information (i.e., application information corresponding to the virtual terminal service, such as an APP ID) and a user identification (such as a SUPI or APP UE ID, etc.).
[0217] S405 : The VUEC sends information 2 (which may be the second information in FIG. 3 ) to the terminal device.
[0218] Correspondingly, the terminal device receives information 2. Information 2 indicates the response result to information 1.
[0219] The VUEC can determine the response to message 1 through interaction with the VUE Agent. For example, the VUEC sends an authentication request message (which can be the third message in Figure 3 ) to the VUE Agent, and the VUE Agent sends an authentication feedback message (which can be the fourth message in Figure 3 ) to the VUEC. If authentication is successful, the VUE Agent can provide the VUEC with the terminal device's identity within the VUE Agent, such as a virtual UE agent ID (VUE Agent ID), smart agent ID, or digital human ID, for use in identifying the terminal device during interaction between the VUEC and the VUE Agent.
[0220] The VUEC can create a service context for the virtual terminal service, which includes at least one of the following: application information corresponding to the virtual terminal service (such as VUE Agent information) (such as APP ID or AF ID), identification information assigned by the VUEC to the terminal device (such as UE temp ID), permanent identification information of the terminal device (such as SUPI), or identity information of the UE in the APP (such as VUE Agent ID).
[0221] The terminal device can create and maintain the service context of the virtual terminal service corresponding to the VUE Agent based on information 2. The context includes at least one of the following: application information corresponding to the virtual terminal service (such as VUE Agent information) (APP ID or AF ID), identification information assigned by VUEC to the terminal device (such as UE temp ID), permanent identification information of the terminal device (such as SUPI), and identity information of the UE in the APP (such as APP UE ID or VUE Agent ID).
[0222] Through the interaction process shown in FIG4 , the embodiment of the present application can support VUE Agent to share or use the mobile network service of the terminal device.
[0223] When the VUEC allows or agrees to the content requested in message 1, a service connection for the virtual terminal service can be established between the terminal device and the VUE Agent, and the VUE Agent can process data or signaling for the terminal device.
[0224] FIG5 is a schematic diagram of an interaction flow of a communication method 500 according to an embodiment of the present application. As shown in FIG5 , the communication method 500 includes:
[0225] S501. VUEC receives information 3.
[0226] Information 3 is used to indicate the association between the terminal device and the VUE Agent.
[0227] For example, the information 3 includes identification information of the terminal device and identification information of the VUE Agent. The VUEC can determine the association between the terminal device and the VUE Agent according to the identification information of the terminal device and the identification information of the VUE Agent.
[0228] For another example, information 3 includes IP address information of the terminal device and IP address information of the VUE Agent. The VUEC can determine the association between the terminal device and the VUE Agent based on the IP address of the terminal device and the IP address information of the VUE Agent.
[0229] In the embodiment of the present application, the VUEC may receive the information 3 from one or both of the terminal device and the VUE Agent, which is not limited.
[0230] S502 : The VUEC determines the association between the terminal device and the VUE Agent according to information 3 .
[0231] When the VUEC determines the association between the terminal device and the VUE Agent, the VUEC may establish a context for the VUE Agent to process data or signaling for the terminal device.
[0232] S503: The VUEC sends information 4 to the third network element. The third network element receives information 4.
[0233] Information 4 indicates an information processing rule for the third network element to send information related to the terminal device to the VUE Agent. In this way, the third network element can send information related to the terminal device to the VUE Agent according to the information processing rule. This can support the VUE Agent in processing the information related to the terminal device, thereby reducing the processing power consumption of the terminal device.
[0234] For example, taking the information related to the terminal device as session data, VUEC adopts independent deployment. After the terminal device sends the session data that needs to be processed to VUEC, VUEC sends the session data to SMF. SMF determines that there is an association between the terminal device and VUE Agent based on information 3 (from VUEC). SMF configures information processing rules to UPF, and UPF sends the session data to VUE Agent according to the information processing rules.
[0235] For another example, taking the information related to the terminal device as perception data, VUEC configures information processing rules to the perception service network element (such as the third network element), which is used by the perception service network element to send the perception data that originally needs to be processed by the terminal device to the VUE Agent, and the VUE Agent processes the perception data.
[0236] When the VUEC is deployed independently, the VUEC can directly send information 4 to the third network element, or can indirectly send information 4 to the third network element. For example, taking the third network element as the UPF, the VUEC sends information 3 to the SMF, and the SMF determines information 4 based on information 3 and sends information 4 to the UPF.
[0237] When VUEC is integrated into other NFs, VUEC can directly send information 4 to the third network element. Taking the third network element as UPF, VUECSMF as an example, SMF receives information 3, determines information 4 based on information 3, and sends information 4 to UPF.
[0238] In the embodiments of the present application, the information related to the terminal device may include data and / or signaling. For example, the third network element sends data related to the terminal device to the VUE Agent, and the VUE Agent processes the data related to the terminal device; for another example, the third network element sends signaling related to the terminal device to the VUE Agent, and the VUE Agent processes the signaling related to the terminal device.
[0239] For further description, the following describes the data and signaling levels respectively.
[0240] Information related to terminal devices is data:
[0241] For example, VUEC is integrated into SMF, and the third network element is UPF.
[0242] Information 3 includes information used to identify the terminal device session (such as session identifier, UE address information (such as IP address), etc.) and VUE Agent information (such as ID information, address information, etc.). The terminal device sends information 3 to the SMF through a PDU session establishment or change request message.
[0243] Optionally, the SMF configures the VUE Agent information (such as identification information or IP address information) to the UPF. For example, the SMF configures the VUE Agent information as a packet detection rule (PDR) to the UPF for data flow identification and subsequent flow processing.
[0244] When a terminal device needs to send a service data flow (SDF) to a VUE Agent, the terminal device sends a data processing request message to the VUEC. The data processing request message includes the data to be processed (such as a triplet, a quintuple, an APP ID, the network element address or identifier where the data is stored, etc.) and the corresponding processing method (such as forwarding to the VUE Agent, data copy forwarding, data diversion processing, etc.). For example, the data processing request message carries a PDU session ID. The VUEC can send a session change request to the SMF based on the data processing request message.
[0245] The terminal device can also send a data processing request message to the SMF, such as using a PDU session change request message to carry the above-mentioned data to be processed and the corresponding processing method. Based on the PDU session change request information, the SMF obtains the corresponding session execution policy from the PCF, or executes the data to be processed based on the local policy, and generates the corresponding information processing rules. The SMF configures the generated information processing rules to the UPF. If the SMF does not provide the PDR corresponding to the VUE Agent to the UPF, it can be configured to the UPF together with the information processing rules. Otherwise, the identification information corresponding to the PDR can be used to bind to the corresponding information processing rules. The information processing rules can be: data flow forwarding processing method (such as forwarding to the VUE Agent, data copy forwarding, data diversion processing, etc.), QoS execution method, etc.
[0246] After the SMF completes processing the data processing request information, the SMF may send feedback corresponding to the data processing request information to the terminal device or send feedback to the terminal device through the VUEC.
[0247] Furthermore, the UPF processes the uplink and downlink data packets of the terminal device based on the PDR and the corresponding information processing rules. For example, if the data packet that needs to be sent to the terminal device needs to be forwarded to the VUE Agent (or the address provided by the VUE Agent), the UPF can change the destination address of the data from the address information of the terminal device to the address information of the VUE Agent (or provided by the VUE Agent), thereby realizing the forwarding processing of the data packet. If the uplink or downlink data packet of the terminal device needs to be copied and forwarded (such as the uplink data needs to be sent to the APP and the VUE Agent simultaneously), after receiving the data packet, the UPF will copy the data packet and send one copy to the network element or device corresponding to the original destination address, and one copy to the VUE Agent (or the address provided by the VUE Agent). Correspondingly, if it is a data packet from the VUE Agent (or the address provided by the VUE Agent), the UPF can also process it based on the corresponding processing method and information processing rules.
[0248] The above content takes session data as an example, but it can also be other service data, such as terminal data generated within the network, data that the network can open to the terminal for use, etc. (such as analysis data generated by the network's data analysis function, AI service data provided by the network to the terminal, perception data, etc.). For example, for perception data, the VUEC sends a diversion instruction to the perception service network element, so that the perception service network element sends the generated perception data to the VUE Agent.
[0249] Information related to terminal devices is signaling:
[0250] For example, VUEC is deployed independently, and the third network element is AMF.
[0251] After VUEC receives information 3, VUEC determines information 4 based on information 3 and sends information 4 to AMF. AMF sends the signaling related to the terminal device to VUE Agent according to the information processing rules.
[0252] Exemplarily, after the terminal device sends information 3 to the VUEC, the terminal device sends a signaling processing request message to the VUEC, which includes the signaling to be processed (such as positioning signaling, SMS or voice service signaling, IoT data signaling, perception service signaling, AI signaling, etc.) and the corresponding processing method. If multiple signaling processing methods are defined, the signaling processing request message carries one or more processing methods. If there is no direct communication path between the AMF and the VUE Agent, the information 4 can be forwarded through other network elements. For example, the AMF forwards the information 4 to the VUE Agent through the NEF, or forwards the information 4 to the VUE Agent through the user plane path of the SMF and UPF, etc.
[0253] The above content is based on the example of AMF being a signaling processing and forwarding node. In future communication systems, the signaling processing node can also be other network elements, or the network element providing the service can directly send signaling, such as session data sent by SMF (that is, there is no signaling forwarding network element).
[0254] After completing the processing of the signaling processing request information, the third network element may send feedback information to the VUEC. Correspondingly, the VUEC sends feedback information to the terminal device.
[0255] After a connection or service for a virtual terminal service is established between a terminal device and a VUE Agent, the terminal device's status must be synchronized with the status of the VUE Agent (or the virtual terminal within the VUE Agent). For example, when a terminal device is in arrears, the VUE Agent must stop providing virtual terminal services; when the terminal device is in a normal payment state, the VUE Agent must resume or continue providing virtual terminal services. Therefore, the present application provides a communication method that synchronizes the status of a terminal device with that of the VUE Agent. This is described below with reference to Figures 6 and 7 for an exemplary embodiment.
[0256] In the embodiments of the present application, the status of the terminal device includes, but is not limited to, arrears, normal payment, or disconnected status. The status of the VUE Agent includes, but is not limited to, activation, suspension, or deletion. The activation state may include: the VUE Agent initiating services to the core network, using the core network's network services, or receiving data / signaling sent by the core network to the VUE Agent. The suspension state may include: the connection between the core network and the VUE Agent is suspended, and the core network only exchanges service data / signaling with the terminal device. The deletion state may include: the service related to the virtual terminal service is terminated, and the VUEC deletes the VUE Agent context.
[0257] FIG6 is a schematic diagram of an interaction flow of a communication method 600 according to an embodiment of the present application. As shown in FIG6 , the communication method 600 includes:
[0258] S601: The terminal device sends information 5 to the VUEC. The VUEC receives information 5.
[0259] Information 5 indicates information on status operation of the VUE Agent or a virtual terminal in the VUE Agent.
[0260] Information 5 includes the identification information of the terminal device (such as UE temple ID) or the identification information of the VUE Agent (such as AF ID or APP ID, etc.). After a connection relationship is established between the terminal device and the VUE Agent (connection or binding is performed using an IP address or identifier), the VUEC can determine the VUE Agent based on the identification information of the terminal device or the identification information of the VUE Agent. For example, the VUEC can determine the VUE Agent based on the connection relationship between the terminal device and the VUE Agent and the identification information of the terminal device; for another example, the VUEC can determine the VUE Agent based on the identification information of the VUE Agent. In this way, the VUEC can determine that the information indicated by information 5 regarding the status operation of the VUE Agent or the virtual terminal in the VUE Agent is about the VUE Agent or the virtual terminal in the VUE Agent.
[0261] S602: VUEC sends information 6 to VUE Agent. VUE Agent receives information 6.
[0262] Information 6 is used to indicate information on the status operation of the VUE Agent or the virtual terminal in the VUE Agent.
[0263] When information 6 is the same as information 5, the VUEC forwards information 5 to the VUE Agent. When information 6 is different from information 5, the VUEC can determine information 6 based on information 5 and send information 6 to the VUE Agent. In this way, the VUE Agent determines information related to the state of the VUE Agent or the virtual terminal in the VUE Agent and updates the state of the VUE Agent or the virtual terminal in the VUE Agent based on the information.
[0264] S603: VUE Agent sends information 7 to VUEC. VUEC receives information 7.
[0265] Information 7 is used to respond to information 6, or information 7 indicates the response result to information 6.
[0266] For example, after the VUE Agent performs an operation to update the status of the VUE Agent or the virtual terminal in the VUE Agent based on the information on the status operation of the VUE Agent or the virtual terminal in the VUE Agent, the VUE Agent indicates to the VUEC the updated status of the VUE Agent or the virtual terminal in the VUE Agent (consistent with the information on the status operation of the VUE Agent or the virtual terminal in the VUE Agent), or the VUE Agent indicates to the VUEC that the VUE Agent or the virtual terminal in the VUE Agent has performed the status update operation, which is not limited to this.
[0267] S604: The VUEC sends information 8 to the terminal device. The terminal device receives information 8.
[0268] Message 8 is used to respond to message 5, or message 8 indicates the response result to message 5.
[0269] For example, the information 8 includes information for indicating the updated state of the VUE Agent or the virtual terminal in the VUE Agent. In this way, the terminal device can determine that the VUE Agent or the virtual terminal in the VUE Agent has performed a state update operation.
[0270] Through the above solution, the terminal device can operate or manage the status of the VUE Agent or the virtual terminal in the VUE Agent, thereby supporting synchronization between the status of the terminal device and the status of the VUE Agent or the virtual terminal in the VUE Agent.
[0271] Method 600 is described by taking the example of a terminal device controlling or managing the status of a VUE Agent or a virtual terminal in the VUE Agent, but is not limited thereto. For example, a VUEC may control or manage the status of a VUE Agent or a virtual terminal in the VUE Agent, as shown in FIG. 7 .
[0272] FIG7 is a schematic diagram of an interaction flow of a communication method 700 according to an embodiment of the present application. As shown in FIG7 , the communication method 700 includes:
[0273] S701. The VUEC determines status information of a terminal device.
[0274] For example, the VUEC may send a request message to the NF (such as the AMF) or the RAN node to request subscription to the terminal device's status information. The request message may carry the terminal device's identification information, the triggering condition for reporting the terminal device's status information (for example, when the terminal device is in arrears or when the terminal device has completed payment), etc. The subscription to the terminal device's status information may be initiated by the VUEC itself or by the VUE Agent requesting subscription from the VUEC, which is not limited to this.
[0275] When the terminal device meets the triggering condition for reporting the terminal device's status information, the RAN or NF sends the terminal device's status information to the VUEC.
[0276] When the VUE Agent sends a request to the VUEC to subscribe to the terminal device's status information, the VUEC returns a subscription trigger message to the VUE Agent. In certain scenarios, if the VUEC needs to change the status of the VUE Agent or the virtual terminal within the VUE Agent, the VUEC sends a status update message to the VUE Agent. For example, if the terminal device is in arrears, the VUEC learns from the charge function (CHF) or PCF that it can no longer provide virtual terminal services to the terminal device. The VUEC then sends a service suspension or release message to the VUE Agent.
[0277] S702: VUEC sends information 9 to VUE Agent. VUE Agent receives information 9.
[0278] Information 9 indicates information on the state operation of the VUE Agent or the virtual terminal in the VUE Agent, wherein the information on the state operation of the VUE Agent or the virtual terminal in the VUE Agent is related to the state information of the terminal device.
[0279] For example, if the terminal device is in arrears, the VUEC learns from the CHF or PCF that it is currently unable to continue providing virtual terminal services to the terminal device. The VUEC may send a service suspension or release message to the VUE Agent (such as message 9).
[0280] S703: VUE Agent sends information 10 to VUEC. VUEC receives information 10.
[0281] Information 10 is used to respond to information 9, or information 10 indicates the response result to information 9.
[0282] For example, after the VUE Agent performs an operation to update the status of the VUE Agent or the virtual terminal in the VUE Agent based on the information of the status operation on the VUE Agent or the virtual terminal in the VUE Agent, the VUE Agent indicates to the VUEC the updated status of the VUE Agent or the virtual terminal in the VUE Agent (consistent with the information of the status operation on the VUE Agent or the virtual terminal in the VUE Agent), or the VUE Agent indicates to the VUEC that the VUE Agent or the virtual terminal in the VUE Agent has performed the status update operation, which is not limited to this.
[0283] S704: The VUEC sends information 11 to the terminal device. Correspondingly, the terminal device receives the information 11.
[0284] Information 11 indicates the updated status of the VUE Agent or the virtual terminal in the VUE Agent.
[0285] For example, the information 11 includes information for indicating the updated state of the VUE Agent or the virtual terminal in the VUE Agent. In this way, the terminal device can determine that the VUE Agent or the virtual terminal in the VUE Agent has performed a state update operation.
[0286] Through the above solution, VUEC can operate or manage the status of VUE Agent or the virtual terminal in VUE Agent, thereby supporting the synchronization between the status of the terminal device and the status of VUE Agent or the virtual terminal in VUE Agent.
[0287] Figures 6 and 7 illustrate an example in which the state of a VUE Agent or a virtual terminal within the VUE Agent is controlled by a terminal device or a VUEC. The VUE Agent can manage its own state. For example, when the state of the VUE Agent or the virtual terminal within the VUE Agent changes (e.g., the virtual terminal service between the VUE Agent and the terminal device is terminated, or the user proactively changes the state of the VUE Agent's virtual terminal), the VUE Agent notifies the VUEC of the state change of the VUE Agent or the virtual terminal within the VUE Agent. For example, the virtual terminal service of the VUE Agent or the virtual terminal within the VUE Agent is terminated. Accordingly, the VUEC notifies the terminal device of the state change of the VUE Agent or the virtual terminal within the VUE Agent.
[0288] After a connection or service for a virtual terminal service is established between a terminal device and a VUE Agent, the terminal device can request the VUE Agent to provide the virtual terminal service, and the VUE Agent can provide the virtual terminal service in response to the terminal device's request. However, enhancing the flexibility of virtual terminal services is a technical issue that needs to be addressed. In view of this, the present application provides a communication method that can support requests for virtual terminal services from a VUE Agent, thereby enhancing the flexibility of virtual terminal services. This is described below with reference to Figures 8 to 10 as an example.
[0289] It should be noted that the virtual terminal service described in Figures 8 to 10 refers to the VUE Agent requesting the VUEC for services of the terminal device within the mobile network, such as the location information of the terminal device, the data stored by the terminal device in the mobile network, the session establishment or change of the terminal device in the mobile network, etc.
[0290] FIG8 is a schematic diagram of an interaction flow of a communication method 800 according to an embodiment of the present application. As shown in FIG8 , the communication method 800 includes:
[0291] S801: The terminal device sends information 12 to the VUE Agent. The VUE Agent receives the information 12.
[0292] Information 12 is used to request the virtual terminal service 1. Information 12 includes a second parameter. The second parameter is a parameter configured by the terminal device for the VUE Agent. For example, the second parameter may be a service token for security authentication, etc., which is not limited to this.
[0293] In one possible example, the information 12 includes identification information of the virtual terminal service 1. The VUE Agent determines that the terminal device requests the virtual terminal service 1 according to the identification information of the virtual terminal service 1.
[0294] S802: VUE Agent sends information 13 to VUEC. VUEC receives information 13.
[0295] The information 13 is used to request the virtual terminal service 1, and the information 13 includes a second parameter.
[0296] In a possible example, the VUE Agent sends information 13 to the VUEC in response to information 12 , where the information 13 includes identification information of the virtual terminal service 1 and a second parameter.
[0297] S803: The VUEC sends information 14 to the terminal device. The terminal device receives information 14.
[0298] The information 14 is used to request a response to the information 13, and the information 14 includes a second parameter.
[0299] For example, the information 14 includes the identification information of the virtual terminal service 1 and the second parameter. Optionally, the information 14 may also include the identification information of the VUE Agent. The identification information of the VUE Agent may be used to indicate that the information 13 is sent by the VUE Agent.
[0300] S804: The terminal device sends information 15 to the VUEC. The VUEC receives information 15.
[0301] Information 15 is used to indicate the response result to information 13.
[0302] For example, the terminal device confirms that the second parameter in the information 14 is the parameter configured by the terminal device for the VUE Agent, the terminal device determines that the VUE Agent is a network element authorized by the terminal device, and the terminal device sends information 15 to the VUEC.
[0303] S805 : VUEC sends information 16 to VUE Agent, and VUE Agent receives information 16 .
[0304] Information 16 is used to indicate the response result to information 13.
[0305] For example, when the information 15 indicates that the second parameter is a correct parameter, the VUEC determines that the VUE Agent is allowed to provide the virtual terminal service 1 .
[0306] Through the above solution, the VUE Agent can actively request the provision of virtual terminal services, thereby enhancing the flexibility of the virtual terminal services.
[0307] FIG9 is a schematic diagram of an interaction flow of a communication method 900 according to an embodiment of the present application. As shown in FIG9 , the communication method 900 includes:
[0308] S901. VUE Agent sends information 17 to VUEC. VUEC receives information 17.
[0309] In one possible example, the information 17 includes identification information of the virtual terminal service 2 .
[0310] Optionally, the information 17 may also include identification information of the VUE Agent. In this way, the VUEC can determine that the information 17 is sent by the VUE Agent.
[0311] S902: The VUEC sends information 18 to the terminal device. The terminal device receives information 18.
[0312] Information 18 is used to request a response to information 17. Information 18 includes a third parameter. The third parameter is a parameter configured by VUEC for VUE Agent. For example, the third parameter can be a service token used for security authentication, etc., which is not limited to this.
[0313] In one possible example, the information 18 includes identification information of the virtual terminal service 2 .
[0314] S903: The terminal device sends information 19 to the VUE Agent. The VUE Agent receives information 19.
[0315] In one possible example, the information 19 includes identification information of the virtual terminal service 2 and a third parameter.
[0316] S904: VUE Agent sends information 20 to VUEC. VUEC receives information 20.
[0317] In one possible example, the information 20 includes the third parameter and identification information of the virtual terminal service 2 .
[0318] S905: VUEC sends information 21 to VUE Agent. VUE Agent receives information 21. Information 21 indicates the response result to information 17.
[0319] For example, when the VUEC determines that the third parameter in the information 20 is a correct parameter, the VUEC determines that the VUE Agent is allowed to provide the virtual terminal service 2 .
[0320] Through the above solution, the VUE Agent can actively request the provision of virtual terminal services, thereby enhancing the flexibility of the virtual terminal services.
[0321] FIG10 is a schematic diagram of an interaction flow of a communication method 1000 according to an embodiment of the present application. As shown in FIG10 , the communication method 1000 includes:
[0322] S1001: The terminal device sends information 22 to the VUEC. The VUEC receives the information 22.
[0323] The information 22 is used to request the virtual terminal service 3 .
[0324] In one possible example, the information 22 includes the identification information of the virtual terminal service 3
[0325] Optionally, the information 22 may further include identification information of the VUE Agent, wherein the identification information of the VUE Agent may indicate that the virtual terminal service 3 is provided by the VUE Agent.
[0326] S1002: VUEC sends information 23 to the terminal device. The terminal device receives information 23.
[0327] In one possible example, the information 23 includes identification information of the virtual terminal service 3 and a fourth parameter. The fourth parameter is a parameter configured by the VUEC for the terminal device. For example, the fourth parameter may be a service token for security authentication, etc., which is not limited to this.
[0328] Optionally, the information 23 may also include identification information of the VUE Agent.
[0329] S1003: The terminal device sends information 24 to the VUE Agent. The VUE Agent receives the information 24.
[0330] The information 24 is used to request the virtual terminal service 3 .
[0331] In one possible example, the information 24 includes identification information of the virtual terminal service 3 and the fourth parameter.
[0332] S1004 : VUE Agent sends information 25 to VUEC. VUEC receives information 25 .
[0333] Information 25 is used to request virtual terminal service 3
[0334] In one possible example, the information 25 includes identification information of the virtual terminal service 3 and the fourth parameter.
[0335] S1005 : VUEC sends information 26 to VUE Agent, and VUE Agent receives information 26 .
[0336] Here, information 26 indicates the response result to information 25 .
[0337] For example, when the VUEC determines that the fourth parameter in the information 25 is a correct parameter, the VUEC determines that provision of the virtual terminal service 3 is permitted.
[0338] Through the above solution, the VUE Agent can actively request the provision of virtual terminal services, thereby enhancing the flexibility of the virtual terminal services.
[0339] It should be noted that the methods described in Figures 4 to 10 can be combined with each other or can be independent of each other. For example, the method shown in Figure 4 can be combined with the method shown in Figure 5 to form a new technical solution, or the method shown in Figure 4 can be combined with the method shown in Figure 6 to form a new technical solution, and so on, without limitation.
[0340] 3. Communication Device
[0341] Finally, the device embodiment of the embodiment of the present application is introduced.
[0342] To implement the various functions of the methods provided herein, the terminal device, VUEC, and VUE Agent may include hardware structures and / or software modules, with the aforementioned functions implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0343] FIG11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device 1100 includes a processing circuit 1110 and a transceiver circuit 1120. The processing circuit 1110 and the transceiver circuit 1120 may be interconnected or coupled, for example, via a bus 1130. The communication device 1100 may be a terminal device, a VUEC, or a VUE Agent.
[0344] Optionally, the communication device 1100 may further include a memory 1140. The memory 1140 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), and is used for related instructions and data.
[0345] The processing circuit 1110 may be all or part of the processing circuit in one or more processors, or one or more processors. The processor may be a central processing unit (CPU). When the processing circuit 1110 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processing circuit 1110 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuit for processing functions in the aforementioned processor, chip or integrated circuit. In addition, the transceiver circuit 1120 may also be a transceiver, or an input / output interface, which is used for input or output of signals or data, and may also be referred to as an input / output circuit.
[0346] When the communication apparatus 1100 is a terminal device, illustratively, the processing circuit 1110 is configured to perform the following operations: sending request information; receiving response information, and the like.
[0347] When the communication device 1100 is a VUEC, illustratively, the processing circuit 1110 is configured to perform the following operations: receive first information; send second information, etc.
[0348] When the communication device 1100 is a VUE Agent, illustratively, the processing circuit 1110 is configured to perform the following operations: receive third information; send fourth information, etc.
[0349] The above contents are merely exemplary descriptions. When the communication device 1100 is a terminal device, a VUEC, or a VUE Agent, it will be responsible for executing the methods or steps related to the terminal device, the VUEC, or the VUE Agent in the aforementioned method embodiments.
[0350] When the communication device 1100 is a terminal device, a VUEC, or a VUE Agent, the transceiver circuit 1120 may be a transceiver. When the communication device 1100 is a chip for a terminal device, a VUEC, or a VUE Agent, the transceiver circuit 1120 may be an input / output circuit. The above description is merely exemplary.
[0351] For details, please refer to the contents of the above method embodiment. The implementation of each operation in Figure 11 can also correspond to the corresponding description of the method embodiment shown in Figures 3 to 10.
[0352] 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 may be a terminal device, a VUEC, or a VUE Agent, and is configured to implement the method described in the above embodiment.
[0353] The communication device 1200 includes a transceiver unit 1210. The transceiver unit 1210 is exemplarily introduced below.
[0354] The transceiver unit 1210 may include a transmitting unit and a receiving unit. The transmitting unit is configured to execute a transmitting operation of the communication device, and the receiving unit is configured to execute a receiving operation of the communication device. For ease of description, this embodiment of the application combines the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later.
[0355] When the communication apparatus 1200 is a terminal device, illustratively, the transceiver unit 1210 is used to send request information and receive response information, etc.
[0356] Optionally, the communication device 1200 may further include a processing unit 1220, which is used to execute the content of the terminal device involving processing, control and other steps.
[0357] When the communication device 1200 is a VUEC, illustratively, the transceiver unit 1210 is configured to receive first information and send second information, etc.
[0358] Optionally, the communication device 1200 may further include a processing unit 1220, which is configured to execute steps such as processing and control related to the VUEC.
[0359] When the communication device 1200 is a VUE Agent, illustratively, the transceiver unit 1210 is configured to receive the third information and send the fourth information, etc.
[0360] Optionally, the communication device 1200 may further include a processing unit 1220, which is configured to execute the contents of the VUE Agent involving processing, control and other steps.
[0361] When the communication device 1200 is a terminal device, a VUEC, or a VUE Agent, it will be responsible for executing one or more of the methods or steps related to the terminal device, the VUEC, or the VUE Agent in the aforementioned method embodiments.
[0362] Optionally, the communication device 1200 further includes a storage unit 1230, which is used to store a program or code for executing the aforementioned method.
[0363] It should be noted that the transceiver unit in FIG12 may correspond to the transceiver circuit in FIG11 , and the processing unit in FIG12 may correspond to the processing circuit in FIG11 .
[0364] The device embodiments shown in Figures 11 and 12 are used to implement the contents described in Figures 3 to 10. The specific execution steps and methods of the devices shown in Figures 11 and 12 can refer to the contents described in the above method embodiments.
[0365] The present application also provides a chip including a processor configured to retrieve and execute instructions stored in a memory, so that a communication device equipped with the chip executes the methods described in the above examples. The memory may be integrated within the chip or located outside the chip.
[0366] The present application also provides another chip, comprising: an input interface, an output interface, and a processing circuit, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processing circuit is used to execute the code in the memory. When the code is executed, the processing circuit is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, which is used to store computer programs or code. The input interface and the output interface can be independent of each other, or can be integrated into an input and output interface.
[0367] The processing circuit may be all or part of the processing circuits in one or more processors, or one or more processors.
[0368] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving a network device or a terminal device in any of the above embodiments.
[0369] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.
[0370] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.
[0371] In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.
[0372] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0373] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0374] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.
[0375] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0376] Those skilled in the art will appreciate that the various exemplary units and algorithmic steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented using hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for ease of description and brevity, the specific operating processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is merely a logical functional division. In actual implementation, other divisions may be used, such as multiple units or components can be combined or integrated into another system, or some features can be omitted or not implemented. Furthermore, the coupling or direct coupling or communication connection shown or discussed between each other can be through some interface, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.
[0377] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. If the above functions are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the portion that contributes to the prior art, or the portion of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk.
[0378] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
Claims
1. A communication method, characterized in that: Applied to the first network element, including: receiving first information, the first information including a first parameter, the first parameter being a parameter configured by a second network element for a terminal device, the second network element being a network element providing a virtual terminal service, and the first information being information related to the virtual terminal service; Second information is sent, where the second information indicates a response result to the first information, and the response result to the first information is related to the first parameter.
2. The method according to claim 1, characterized in that The sending of the second information includes: Sending third information to the second network element, where the third information requests the second network element to respond to the first information, and the third information includes the first parameter; receiving fourth information from the second network element, where the fourth information indicates a response result to the first information; The second information is sent.
3. The method according to claim 1, characterized in that The sending of the second information includes: receiving the first parameter from the second network element; determining the second information according to the first parameter; The second information is sent.
4. The method according to any one of claims 1 to 3, characterized in that Before receiving the first information, the method further includes: Capability information is sent, where the capability information indicates that the first network element can support the virtual terminal service.
5. The method according to claim 4, characterized in that The capability information includes a first identifier, which is an identifier used by the terminal device in the virtual terminal service.
6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: receiving fifth information, where the fifth information indicates an association between the terminal device and the second network element; Based on the fifth information, determine the association between the terminal device and the second network element.
7. The method according to claim 6, characterized in that The method further comprises: Send sixth information to the third network element, where the sixth information indicates an information processing rule, and the information processing rule is used by the third network element to send information related to the terminal device to the second network element.
8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: receiving seventh information from the terminal device, the seventh information indicating information about a status operation on the second network element; Eighth information is sent to the second network element, where the eighth information indicates information about the status operation on the second network element.
9. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Determining status information of the terminal device; Ninth information is sent to the second network element, where the ninth information indicates information on status operations on the second network element, and the information on status operations on the second network element is related to the status information of the terminal device.
10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: receiving tenth information from the second network element, the tenth information requesting the virtual terminal service, the tenth information including a second parameter, the second parameter being a parameter configured by the terminal device for the second network element; sending eleventh information to the terminal device, where the eleventh information requests the terminal device to respond to the tenth information, and the eleventh information includes the second parameter; receiving twelfth information from the terminal device, the twelfth information indicating a response result to the tenth information; Thirteenth information is sent to the second network element, where the thirteenth information indicates a response result to the tenth information.
11. The method according to any one of claims 1 to 9, characterized in that The method further comprises: receiving fourteenth information from the second network element, the fourteenth information requesting the virtual terminal service; Sending fifteenth information to the terminal device, the fifteenth information requesting the terminal device to respond to the fourteenth information, the fifteenth information including a third parameter, the third parameter being a parameter configured by the first network element for the second network element; receiving sixteenth information from the second network element, where the sixteenth information includes the third parameter; Seventeenth information is sent to the second network element, where the seventeenth information indicates a response result to the fourteenth information.
12. The method according to any one of claims 1 to 9, characterized in that The method further comprises: receiving an eighteenth message from the terminal device, the eighteenth message requesting the virtual terminal service; Sending nineteenth information to the terminal device, where the nineteenth information includes a fourth parameter, where the fourth parameter is a parameter configured by the first network element for the terminal device; receiving twentieth information from the second network element, where the twentieth information includes the fourth parameter; Twenty-first information is sent to the terminal device, where the twenty-first information indicates a response result to the eighteenth information.
13. A communication method, characterized in that: Applied to terminal equipment, including: Sending first information to a first network element, where the first information includes a first parameter, where the first parameter is a parameter configured by a second network element for the terminal device, where the second network element is a network element providing a virtual terminal service, and the first information is information related to the virtual terminal service; Second information is received from the second network element, where the second information indicates a response result to the first information, and the response result to the first information is related to the first parameter.
14. The method according to claim 13, characterized in that The method further comprises: Sending a request message to the second network element, wherein the request message requests the virtual terminal service; Receive response information from the second network element, where the response information includes the first parameter.
15. The method according to claim 13 or 14, characterized in that Before sending the first information to the first network element, the method further includes: Capability information is received from the first network element, where the capability information indicates that the first network element can support the virtual terminal service.
16. The method according to claim 15, characterized in that The capability information includes a first identifier, which is an identifier used by the terminal device in the virtual terminal service.
17. The method according to any one of claims 13 to 16, characterized in that The method further comprises: Send third information to the second network element, where the third information indicates the association between the terminal device and the second network element.
18. The method according to any one of claims 13 to 17, characterized in that The method further comprises: Fourth information is sent to the first network element, where the fourth information indicates information about a status operation on the second network element.
19. The method according to any one of claims 13 to 18, characterized in that The method further comprises: Fifth information is received from the first network element, where the fifth information indicates an updated state of the second network element.
20. The method according to any one of claims 13 to 19, characterized in that The method further comprises: receiving sixth information from the first network element, the sixth information requesting a response to seventh information, the seventh information being used by the second network element to request the virtual terminal service, the seventh information including a second parameter, the second parameter being a parameter configured by the terminal device for the second network element, and the sixth information including the second parameter; Sending eighth information to the first network element, where the eighth information indicates a response result to the seventh information.
21. The method according to any one of claims 13 to 20, characterized in that The method further comprises: receiving ninth information from the first network element, the ninth information requesting a response to tenth information, the tenth information being used by the second network element to request the virtual terminal service, the ninth information including a third parameter, the third parameter being a parameter configured by the first network element for the second network element; Send the third parameter to the second network element.
22. The method according to any one of claims 13 to 21, characterized in that The method further comprises: sending a tenth message to the first network element, wherein the tenth message requests the virtual terminal service; receiving eleventh information from the first network element, where the eleventh information includes a fourth parameter, where the fourth parameter is a parameter configured by the first network element for the terminal device; sending the fourth parameter to the second network element; Twelfth information is received from the first network element, where the twelfth information indicates a response result to the tenth information.
23. A communication method, characterized in that: Applied to a second network element, the second network element provides a virtual terminal service, including: receiving first information from a first network element, the first information requesting a response to second information from a terminal device, the first information including a first parameter, the first parameter being a parameter configured by the second network element for the terminal device, the second information including the first parameter, the second information being information related to the virtual terminal service; Send third information to the first network element, where the third information indicates a response result to the second information, and the third information is used by the first network element to determine fourth information, where the fourth information indicates a response result to the second information.
24. The method according to claim 23, wherein The method further comprises: receiving a request message from the terminal device, the request message requesting the virtual terminal service; Send response information to the terminal device, where the response information includes the first parameter.
25. The method according to claim 23 or 24, characterized in that The method further comprises: receiving fifth information from the first network element, where the fifth information indicates information about a status operation on the second network element; Send sixth information to the first network element, where the sixth information indicates a response result to the fifth information.
26. The method according to any one of claims 23 to 25, characterized in that The method further comprises: receiving seventh information from the first network element, the seventh information indicating information about a status operation on the second network element, the information about the status operation on the second network element being related to a status of the terminal device; Eighth information is sent to the first network element, where the eighth information indicates an updated state of the second network element.
27. The method according to any one of claims 23 to 26, characterized in that The method further comprises: Sending tenth information to a third network element, the tenth information requesting the virtual terminal service, the tenth information including a second parameter, where the second parameter is a parameter configured by the terminal device for the first network element; Receive eleventh information sent from the third network element, where the eleventh information indicates a response result to the tenth information.
28. The method according to any one of claims 23 to 27, characterized in that The method further comprises: sending twelfth information to a third network element, wherein the twelfth information requests the virtual terminal service; receiving a third parameter from the terminal device, where the third parameter is a parameter configured by the third network element for the first network element; Sending thirteenth information to the third network element, where the third information includes the third parameter; Fourteenth information is received from the third network element, where the fourteenth information indicates a response result to the twelfth information.
29. The method according to any one of claims 23 to 28, characterized in that The method further comprises: receiving a fourth parameter from the terminal device, where the fourth parameter is a parameter configured by a third network element for the terminal device; A fifteenth message is sent to the third network element, where the fifteenth message includes a fourth parameter, and the fourth parameter is used to respond to a sixteenth message from the terminal device, where the sixteenth message requests the virtual terminal service.
30. A communication device, characterized in that: comprising a processor configured to, by executing computer programs or instructions, or by executing logic circuits, causing the communication device to perform the method according to any one of claims 1 to 12; or, causing the communication device to perform the method according to any one of claims 13 to 22; or, The communication device is caused to perform the method according to any one of claims 23 to 29.
31. The communication device according to claim 30, characterized in that The communication device further comprises a memory for storing the computer program or instructions.
32. The communication device according to claim 30 or 31, characterized in that The communication device further includes a communication interface, which is used to input and / or output signals.
33. A communication device, characterized in that: It includes a logic circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals. The logic circuit is configured to execute the method according to any one of claims 1 to 12; or The logic circuit is configured to execute the method according to any one of claims 13 to 22; or The logic circuit is configured to execute the method according to any one of claims 23 to 29.
34. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a computer, causing the method of any one of claims 1 to 12 to be performed; or, causing the method of any one of claims 13 to 22 to be performed; or, Such that the method of any one of claims 23 to 29 is performed.
35. A computer program product, characterized in that Contains instructions that, when executed on a computer, causing the method of any one of claims 1 to 12 to be performed; or, causing the method of any one of claims 13 to 22 to be performed; or, Such that the method of any one of claims 23 to 29 is performed.
Citation Information
Patent Citations
Authentication method, device and system of cloud mobile phone application, authentication module and terminal
CN114268445A
Biological characteristic authentication method and device based on cloud mobile phone, cloud mobile phone platform and storage medium
CN114297603A
Method for improving 5G MAAP message fallback experience
CN116367097A
Service reachability detection
US20240031447A1
Network function creation method and communication device
WO2023125259A1