Communication method, apparatus and system

Abstract

Provided in the present application are a communication method, an apparatus and a system, which are applicable to scenarios of intent-aware communications. The method is applied to a network intelligent agent function network element (NIAF) and comprises: the NIAF receiving first information, the first information being used for describing an intent of a first user; determining a first subnet according to the intent of the first user, the first subnet being determined from at least one subnet, or the first subnet being established by the NIAF; and sending second information, the second information indicating the first subnet. The NIAF selects subnets for users on the basis of users' intents or performs networking on the basis of the users' intents and the users do not need to perform networking by themselves, such that the difficulty of users using devices for networking is reduced, and requirements of users can be satisfied in a timely manner, thus improving user experience.

Description

Communication method, device and system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 29, 2023, with application number 202311869868.0 and application name “Communication Methods, Devices and Systems”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method, device, and system. Background Art

[0003] Dayi communication redefines the protocol interface between devices and networks, shifting from signaling-driven to intent-driven. Leveraging the network's inherent artificial intelligence (AI), it achieves efficient interpretation and delivery of communication intent across a "human-machine-data-spirit" communication framework, driving network functions, intelligent agents, and multimodal devices to achieve user intent. Current technologies require specialized knowledge to set up networking, making them less user-friendly. For example, a user might simply want to control a camera on their phone to monitor their home, but they must first learn how to network between devices. This increases the complexity of device usage and impacts the user experience. Summary of the Invention

[0004] The present application provides a communication method, apparatus, and system that can reduce the difficulty for users to use devices and improve user experience.

[0005] In the first aspect, a communication method is provided, which is applied to a network intelligent agent function network element NIAF. The method can be executed by the NIAF, or by a module in the NIAF (such as a chip or circuit), or by a logical node, logical module or software that can implement all or part of the NIAF functions. This application does not limit this.

[0006] The method includes: receiving first information, where the first information is used to describe the intention of a first user; determining a first subnet based on the intention of the first user, where the first subnet is determined from at least one subnet, or the first subnet is formed by the NIAF; and sending second information, where the second information indicates the first subnet.

[0007] In this method, the user's intention is indirectly expressed by the first device interacting with a device in a subnet, or by a third device accessing a communication network through the first device interacting with a device in a subnet.

[0008] In this method, NIAF connects the first device to the first subnet based on the user's intention or establishes the first subnet for the third device based on the user's intention, which reduces the difficulty of users using device networking, meets user needs in a timely manner, and improves user experience.

[0009] In some implementations, the first subnet is determined from at least one subnet, and determining the first subnet based on the intention of the first user includes: determining a service type of the subnet that the first user requests to access based on the intention of the first user, and the first subnet is a subnet in the at least one subnet with the same service type as the subnet that the first user requests to access.

[0010] In other words, the service type of the subnet that the first user requests to access is determined according to the intention of the first user; and in the at least one subnet, the subnet with the same service type as the subnet that the first user requests to access is used as the first subnet.

[0011] In this method, subnets with the same service type are selected and provided to users, which can meet user needs.

[0012] In some implementations, the method further includes: receiving a first user identifier from the first device, the first user identifier being associated with the first user; and determining the at least one subnet based on the first user identifier, the at least one subnet belonging to a subnet subscribed by the first user.

[0013] In this method, the first user is the user who has signed a contract with the subnet, and can therefore directly obtain the signed subnet.

[0014] In some implementations, the method further includes: receiving a first user identifier, the first user identifier being associated with the first user;

[0015] The at least one subnet is determined according to the first user identifier and the relationship information between the first user and the second user, the at least one subnet belongs to the subnet subscribed by the second user, and the intention of the first user includes the relationship information between the first user and the second user.

[0016] In this method, the first user and the user who signed the contract with the subnet (the second user) are not the same person, but the subnet information signed by the second user can be obtained through the relationship information to avoid being unable to access the subnet.

[0017] In some implementations, the method further includes: determining, based on the verification information of the second user, to allow a first device to access the first subnet, the first device being the device that sends the intention of the first user.

[0018] Optionally, NIAF may contact the second user's digital avatar or user M himself (for example, by sending a confirmation text message) to confirm whether the first user is allowed to access the first subnet.

[0019] This approach can further improve the security of the second user's use of the subnet.

[0020] In some implementations, the method further includes: updating the contract information so that the contract information of the first subnet includes the identifier of the first user, or the contract information of the identifier of the first user includes the identifier of the first subnet.

[0021] In this way, updating the contract information can facilitate subsequent subnet access.

[0022] In some implementations, the second information includes an identifier of the first subnet.

[0023] In some implementations, the identifier of the first subnet is used by a first device to establish a first protocol data unit (PDU) session, where the first device is the device that sends the first user's intention.

[0024] In certain implementations, if the first PDU session and the second PDU session established by the second device in the first subnet are in different management domains, the method further includes: establishing a communication tunnel between a second network element and a third network element, the second network element being the user plane network element of the first PDU session, and the third network element being the user plane network element of the second PDU session.

[0025] This method provides a communication method for scenarios that are not in the same management domain, increasing the compatibility of the solution with multiple communication scenarios.

[0026] In some implementations, the first subnet is formed by the NIAF, and the method includes: according to the intention of the first user, forming at least two devices into the first subnet, the at least two devices include a third device and a fourth device, wherein the third device belongs to the second subnet, the fourth device belongs to the third subnet, and the second subnet is different from the third subnet.

[0027] In this way, NIAF will not establish a new subnet between devices in the same subnet to meet user needs and improve user experience.

[0028] In some implementations, the method further includes: receiving a second user identifier, the second user identifier being associated with the first user; and determining the second subnet and the third subnet to which the first user has subscribed based on the second user identifier.

[0029] In some implementations, the method further includes: receiving a third user identifier and identity information of the first user, the third user identifier being associated with a second user; determining the second subnet to which the second user has subscribed based on the third user identifier; and determining the third subnet to which the first user has subscribed based on the identity information of the first user.

[0030] In some implementations, the method further includes: determining, based on the verification information of the third user, whether to allow the third device to form a network with the fourth device.

[0031] In some implementations, the method further includes: creating contract information for the first subnet, the contract information for the first subnet including the third user identifier of the first device and the fourth user identifier of the fourth device, the fourth user identifier being associated with the first user, or updating the contract information so that the contract information of the first device and the fourth device includes the identifier of the first subnet.

[0032] In this way, creating new contract information or updating contract information can facilitate subsequent subnet access.

[0033] In some implementations, the second information includes an identifier of the first subnet and an identifier of the third device, and the identifier of the first subnet is used to establish a third PDU session. The method also includes: sending third information to a fifth device, and the third information includes an identifier of the first subnet and an identifier of the fourth device, and the identifier of the first subnet is used to establish a fourth PDU session with the fifth device, and the fourth device accesses the communication network through the fifth device.

[0034] In some implementations, sending the second information to the first device includes: sending the second information to the first device via a first application server, where the first application server is an application server registered with the first device; sending the third information to the fifth device includes: sending the third information to the fifth device via a second application server, where the second application server is an application server registered with the fifth device.

[0035] In certain implementations, the third PDU session and the fourth PDU session are in different management domains, and the method further includes: establishing a communication tunnel between a fourth network element and a fifth network element, the fourth network element being the user plane network element of the third PDU session, and the fifth network element being the user plane network element of the fourth PDU session.

[0036] This method provides a communication method after establishing a new subnet in scenarios that are not in the same management domain, increasing the compatibility of the solution with various communication scenarios.

[0037] In a second aspect, a communication method is provided. The method can be executed by a terminal device (such as a first device), or by a module (such as a chip or circuit) in the terminal device, or by a logical node, logical module, or software that can implement all or part of the terminal device functions, which is not limited in this application. The method is applied to the first device.

[0038] The method includes: sending first information, where the first information is used to describe the intention of a first user; receiving second information, where the second information indicates a first subnet, where the first subnet is determined based on the intention of the first user, the first subnet is determined from at least one subnet, or the first subnet is formed by a NIAF; and accessing the first subnet based on the second information.

[0039] In this method, the user's intention is indirectly expressed by the first device interacting with a device in a subnet, or by a third device accessing a communication network through the first device interacting with a device in a subnet.

[0040] In some implementations, the first subnet is determined from at least one subnet, the first subnet is a subnet in the at least one subnet having the same service type as the subnet that the first user requests to access, and the service type of the subnet that the first user requests to access is determined based on the intention of the first user.

[0041] In some implementations, the method further includes: sending a first user identifier, the first user identifier being associated with the first user, the first user identifier being used to determine the at least one subnet, the at least one subnet belonging to a subnet subscribed by the first user.

[0042] In some implementations, a first user identifier is sent, the first user identifier is associated with the first user, the first user identifier and the relationship information between the first user and the second user are used to determine the at least one subnet, the at least one subnet belongs to the subnet signed by the second user, and the first user's intention includes the relationship information between the first user and the second user.

[0043] In some implementations, whether the first device is allowed to access the first subnet is determined based on verification information of the second user.

[0044] In some implementations, the method further includes: updating the contract information so that the contract information of the first subnet includes the identifier of the first user, or the contract information of the identifier of the first user includes the identifier of the first subnet.

[0045] In some implementations, the second information includes an identifier of the first subnet.

[0046] In some implementations, a first PDU session is established based on an identifier of the first subnet.

[0047] In some implementations, the second PDU session established between the first device and the second device in the first subnet is in different management domains, and the first device interacts with the second device through a communication tunnel between the second network element and the third network element. The second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0048] In some implementations, the first subnet is formed by the NIAF, and the first subnet is formed by at least two devices according to the intention of the first user, and the at least two devices include a third device and a fourth device, wherein the third device belongs to the second subnet, the fourth device belongs to the third subnet, and the second subnet is different from the third subnet.

[0049] In some implementations, the method further includes: sending a second user identifier, where the second user identifier is associated with the first user, and the second user identifier is used to determine the second subnet and the third subnet to which the first user has subscribed.

[0050] In some implementations, the method further includes: sending a third user identifier and identity information of the first user, the third user identifier being associated with a second user, the third user identifier being used to determine the second subnet signed by the second user, and the identity information of the first user being used to determine the third subnet signed by the first user.

[0051] In some implementations, whether the third device and the fourth device are allowed to form a network is determined based on verification information of the second user.

[0052] In some implementations, the contract information of the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device, and the fourth user identifier is associated with the first user, or the contract information of the first device and the fourth device includes the identifier of the first subnet.

[0053] In some implementations, the second information comes from the NIAF and is forwarded via the first application server, where the first application server is the application server registered with the first device.

[0054] In some implementations, the second information includes an identifier of the first subnet and an identifier of the second device.

[0055] In some implementations, a third PDU session is established based on an identifier of the first subnet.

[0056] In certain implementations, the first PDU session and the fourth PDU session established by the fourth device are in different management domains, and the first device communicates with the fourth device through a communication tunnel between a fourth network element and a fifth network element. The fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0057] It should be understood that the second aspect is an implementation method on the terminal device side corresponding to the first aspect. The explanations, supplements and descriptions of the beneficial effects of the first aspect are also applicable to the second aspect and will not be repeated here.

[0058] In a third aspect, a communication device is provided. The device may be a network element (such as a NIAF), a module (such as a chip or circuit) within a network element, or a logical node, logic module, or software that implements all or part of the network element's functions. The device includes: a transceiver unit configured to receive first information from a first device, the first information being used to describe the first user's intention; second information being used to describe the intention; a processing unit configured to determine a first subnet based on the first user's intention, the first subnet being determined from at least one subnet, or the first subnet being established by the NIAF and being accessed by the first device; and the transceiver unit further configured to send second information to the first device, the second information indicating the first subnet.

[0059] In some implementations, the first subnet is determined from at least one subnet, and the processing unit is used to determine the service type of the subnet that the first user requests to access based on the intention of the first user, and the first subnet is a subnet in the at least one subnet with the same service type as the subnet that the first user requests to access.

[0060] In some implementations, the transceiver unit is configured to receive a first user identifier associated with the first user; determine the at least one subnet based on the first user identifier, the at least one subnet belonging to a subnet subscribed by the first user.

[0061] In certain implementations, the transceiver unit is used to receive a first user identifier, where the first user identifier is associated with the first user; the processing unit is used to receive a first user identifier, where the first user identifier is associated with the first user; and the at least one subnet is determined based on the first user identifier and relationship information between the first user and the second user, where the at least one subnet belongs to a subnet signed by the second user, and the first user's intention includes relationship information between the first user and the second user.

[0062] In some implementations, the processing unit is configured to determine, based on the verification information of the second user, whether to allow the first device to access the first subnet.

[0063] In some implementations, the processing unit is configured to update the contract information so that the contract information of the first subnet includes the identifier of the first user, or the contract information of the identifier of the first user includes the identifier of the first subnet.

[0064] In some implementations, the second information includes an identifier of the first subnet.

[0065] In some implementations, the identifier of the first subnet is used by a first device to establish a first protocol data unit (PDU) session, where the first device is the device that sends the first user's intention.

[0066] In some implementations, if the first PDU session and the second PDU session established by the second device in the first subnet are in different management domains, the processing unit is used to establish a communication tunnel between the second network element and the third network element, the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0067] In some implementations, the processing unit is used to organize at least two devices into the first subnet according to the intention of the first user, the at least two devices including a third device and a fourth device, wherein the third device belongs to the second subnet, the fourth device belongs to the third subnet, and the second subnet is different from the third subnet.

[0068] In some implementations, the transceiver unit is used to receive a second user identifier from the first device, where the second user identifier is associated with the first user; and the processing unit is used to determine the second subnet and the third subnet to which the first user has subscribed based on the second user identifier.

[0069] In some implementations, the transceiver unit is used to receive a third user identifier and identity information of the first user from the first device, the third user identifier being associated with a second user; the second subnet to which the third user is contracted is determined based on the second user identifier; and the processing unit is used to determine the third subnet to which the first user is contracted based on the identity information of the first user.

[0070] In some implementations, the processing unit is configured to determine, based on the verification information of the third user, whether to allow the third device to form a network with the fourth device.

[0071] In some implementations, the processing unit is used to create contract information for the first subnet, the contract information for the first subnet including the third user identifier of the first device and the fourth user identifier of the fourth device, the fourth user identifier being associated with the first user, or to update the contract information so that the contract information of the first device and the fourth device includes the identifier of the first subnet.

[0072] In some implementations, the second information includes an identifier of the first subnet and an identifier of the third device, and the identifier of the first subnet is used to establish a third PDU session. The method also includes: sending third information to a fifth device, and the third information includes an identifier of the first subnet and an identifier of the fourth device, and the identifier of the first subnet is used to establish a fourth PDU session with the fifth device, and the fourth device accesses the communication network through the fifth device.

[0073] In some implementations, the transceiver unit is used to send the second information to the first device via a first application server, where the first application server is the application server registered with the first device; sending the third information to the fifth device includes: sending the third information to the fifth device via a second application server, where the second application server is the application server registered with the fifth device.

[0074] In some implementations, the third PDU session and the fourth PDU session are in different management domains, and the processing unit is used to establish a communication tunnel between the fourth network element and the fifth network element, the fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0075] In a fourth aspect, a communication device is provided. The device may be a terminal device (such as a first device), a module (such as a chip or circuit) in the terminal device, or a logical node, logic module, or software that can implement all or part of the terminal device's functions. The device includes: a transceiver unit for sending first information, the first information being used to describe the intention of a first user; the transceiver unit is also used to receive second information, the second information indicating a first subnet, the first subnet being determined based on the intention of the first user, the first subnet being determined from at least one subnet, or the first subnet being formed by a NIAF; and a processing unit for accessing the first subnet based on the second information.

[0076] In some implementations, the first subnet is determined from at least one subnet, the first subnet is a subnet in the at least one subnet having the same service type as the subnet that the first user requests to access, and the service type of the subnet that the first user requests to access is determined based on the intention of the first user.

[0077] In some implementations, the transceiver unit is used to send a first user identifier, the first user identifier is associated with the first user, the first user identifier is used to determine the at least one subnet, and the at least one subnet belongs to the subnet subscribed by the first user.

[0078] In some implementations, the transceiver unit is used to send a first user identifier, the first user identifier is associated with the first user, the first user identifier and the relationship information between the first user and the second user are used to determine the at least one subnet, the at least one subnet belongs to the subnet signed by the second user, and the first user's intention includes the relationship information between the first user and the second user.

[0079] In some implementations, whether the first device is allowed to access the first subnet is determined based on verification information of the second user.

[0080] In some implementations, the processing unit is configured to update the contract information so that the contract information of the first subnet includes the identifier of the first user, or the contract information of the identifier of the first user includes the identifier of the first subnet.

[0081] In some implementations, the second information includes an identifier of the first subnet.

[0082] In some implementations, the processing unit is configured to establish a first PDU session according to an identifier of the first subnet.

[0083] In some implementations, the second PDU session established between the first device and the second device in the first subnet is in different management domains, and the first device interacts with the second device through a communication tunnel between the second network element and the third network element. The second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session.

[0084] In some implementations, the first subnet is formed by the NIAF, and the first subnet is formed by at least two devices according to the intention of the first user, and the at least two devices include a third device and a fourth device, wherein the third device belongs to the second subnet, the fourth device belongs to the third subnet, and the second subnet is different from the third subnet.

[0085] In some implementations, the transceiver unit is used to send a second user identifier, where the second user identifier is associated with the first user, and the second user identifier is used to determine the second subnet and the third subnet to which the first user has subscribed.

[0086] In some implementations, the transceiver unit is used to send a third user identifier and the identity information of the first user, the third user identifier is associated with the second user, the second user identifier is used to determine the second subnet signed by the third user, and the identity information of the first user is used to determine the third subnet signed by the first user.

[0087] In some implementations, whether the third device and the fourth device are allowed to form a network is determined based on verification information of the second user.

[0088] In some implementations, the contract information of the first subnet includes the third user identifier of the first device and the fourth user identifier of the fourth device, and the fourth user identifier is associated with the first user, or the contract information of the first device and the fourth device includes the identifier of the first subnet.

[0089] In some implementations, the second information comes from the NIAF and is forwarded via the first application server, where the first application server is the application server registered with the first device.

[0090] In some implementations, the second information includes an identifier of the first subnet and an identifier of the second device.

[0091] In some implementations, the processing unit is configured to establish a third PDU session according to an identifier of the first subnet.

[0092] In certain implementations, the first PDU session and the fourth PDU session established by the fourth device are in different management domains, and the first device communicates with the fourth device through a communication tunnel between a fourth network element and a fifth network element. The fourth network element is the user plane network element of the third PDU session, and the fifth network element is the user plane network element of the fourth PDU session.

[0093] It should be understood that the third aspect and the fourth aspect are implementation methods on the device side corresponding to the first aspect and the second aspect respectively. The explanations, supplements and descriptions of the beneficial effects of the first aspect and the second aspect are also applicable to the third aspect and the fourth aspect and will not be repeated here.

[0094] In a fifth aspect, a communication device is provided, comprising a processor, wherein the processor is configured to enable the communication device to execute the first aspect and any possible method described in the first aspect by executing a computer program or instruction or through a logic circuit; or to enable the communication device to execute the second aspect and any possible method described in the second aspect.

[0095] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.

[0096] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.

[0097] In a sixth 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 or any possible embodiment of the first aspect; or, the logic circuit being used to execute the method described in the second aspect and any possible embodiment of the second aspect.

[0098] In a seventh aspect, a communication system is provided, which includes the communication device described in any possible embodiment of the third aspect, and / or the communication device described in the fourth aspect or any possible embodiment of the fourth aspect.

[0099] In an eighth 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 or any possible embodiment of the first aspect is executed; or, the method described in the second aspect or any possible embodiment of the second aspect is executed.

[0100] In the ninth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect or any possible embodiment of the first aspect to be executed; or cause the method described in the second aspect or any possible embodiment of the second aspect to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] FIG1 is a schematic diagram of a communication architecture.

[0102] FIG2 is a schematic diagram of an application scenario applicable to the communication method provided in an embodiment of the present application.

[0103] FIG3 is a schematic diagram of a communication system provided in an embodiment of the present application.

[0104] FIG4 is a schematic flow chart of a communication method provided in an embodiment of the present application.

[0105] (a) in FIG5 is a schematic diagram of a communication system provided in an embodiment of the present application.

[0106] (b) in FIG5 is a schematic diagram of a communication system provided in an embodiment of the present application.

[0107] FIG6 is a schematic flowchart of an implementation of a communication method provided in an embodiment of the present application.

[0108] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0109] FIG8 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0110] FIG9 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0111] FIG10 is a schematic structural block diagram of a communication device provided in an embodiment of the present application.

[0112] FIG11 is a schematic structural block diagram of another communication device provided in an embodiment of the present application.

[0113] FIG12 is a schematic structural block diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0114] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system, sixth generation (6G) system or new radio (NR), as well as future communication systems.

[0115] As an example and not a limitation, in the embodiments of the present application, the terminal device in the embodiments of the present application may refer to user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may also be a subscriber unit, a terminal device station, a terminal device agent, a terminal device device, or a terminal in V2X communication. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network, a terminal in a 6G network, or a terminal in a future evolution network, etc., and the embodiments of the present application are not limited to this.

[0116] The terminal device in the embodiments of the present application may also be a mobile phone, a tablet computer, a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a tactile terminal device, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in transportation safety, a wireless terminal in a smart city, and a wireless terminal in a smart home.

[0117] Among them, wearable devices can also be called wearable smart devices. It is a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as head-mounted extended reality (XR) glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are full-featured, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0118] In addition, in the embodiment of the present application, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0119] In addition, in this application, the terminal device may also include sensors such as smart printers, train detectors, gas stations, etc., and its main functions include collecting data (part of the terminal device), receiving control information and downlink data from the network device, and sending electromagnetic waves to transmit uplink data to the network device.

[0120] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a base transceiver station (BTS) in a global system of mobile communication (GSM) or code division multiple access (CDMA), a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolutionary node base (eNB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G or 6G network and a future communication system, or a network device in a future evolved PLMN network, etc., an access point (AP) in a WLAN, or a gNB in ​​a new radio (NR) system, and the embodiment of the present application is not limited. It can be understood that all or part of the functions of the network device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0121] Among them, the functions and specific implementation methods of the terminal devices and network devices listed above are only exemplary descriptions, and this application is not limited thereto.

[0122] In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in the terminal device or the network device that can call a program and execute the program.

[0123] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or magnetic tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0124] Building on the enhanced connectivity of 5G systems, 6G systems add resources and capabilities in new dimensions, such as computing, intelligence, data, and perception. They are no longer simply pipelines, but instead provide platform-based service capabilities, enabling the intelligent interconnection of all things. However, this enhanced evolution based on the existing mobile network protocol system will lead to the continuous accumulation of complexity in system design and implementation, making it unsustainable. This is primarily due to the fact that the existing network architecture relies on the definition of standardized signaling processes. The complexity of the architecture and signaling process design depends on the number of business scenarios, the number of business processes within each scenario, and the number of network functions involved in each business process.

[0125] Figure 1 shows a schematic diagram of a personal IoT network (PIN) device intercommunication architecture based on a 5G local area network (5G-LAN). In the figure, two PIN elements with gateway capability (PEGC), two PIN elements with management capability (PEMC) and a personal IoT network element (PINE) (also known as a personal IoT member) belong to the same PIN. PEGC is a 3GPP UE with the ability to access a 5G network. PEMC is used to manage the local network and register PEGC and PINE with the PIN agent function (AF). PIN can communicate with other PINEs within the local network or with the 5G network through PEGC. Based on the registration with PEMC, PIN AF requests the creation of a 5G virtual network group (VN Group) from the unified data management (UDM) through the network equipment functions (NEF). The request message includes the UE ID of the registered PEGC. UDM creates a 5G VN Group based on the request and saves the 5G VN Group subscription information, including the 5G VN Group Identifier (External Group ID and Internal Group ID), the members of the 5G VN Group, namely the user identifier of the PEGC (Subscription permanent identifier (SUPI) and generic public subscription identifier (GPSI)), and the data information of the 5G VN Group (protocol data unit session (PDU session) type, data network name (DNN), single network slice selection assistance information (S-NSSAI), etc.).After PEGC registers with the network, PCF will authorize UE policy (Policy) for UE based on the contract parameters of 5G VN Group, which is used to instruct UE to establish PDU session. PEGC establishes PDU session based on UE Policy request (parameters include PDU Session type, DNN, S-NSSAI). When multiple PEGCs belong to the same network management domain, PDU sessions of different PEGCs usually select the same service management function (SMF). SMF selects the same UPF for the PDU session based on the parameters of the PDU session. SMF further configures the user plane function (UPF) to implement local exchange of data between PEGCs in the UPF. This PEGC#2 can communicate with the camera through 5GC.

[0126] Currently, all network elements in a PIN must be registered with the AF, which in turn manages the PIN network. This means that all devices in the PIN network must support the AF's application layer protocol. This prevents devices in different scenarios from interoperating and networking. Furthermore, networking requires specialized knowledge, which is user-unfriendly. For example, if a user simply wants to control a camera at home using their phone, they must first learn how to network the devices, making it difficult for them to use the devices.

[0127] In view of this, the communication system provided in the embodiment of the present application lowers the threshold for user device networking by networking for the user based on the user's intention, and the networking method does not rely on third-party applications.

[0128] Figure 2 is a schematic diagram of an application scenario that can be applied to the communication method of the embodiment of the present application. As shown in Figure 2, the system is a user-centric communication system that drives multimodal information interaction between humans, machines, numbers, and spirits based on the intentions sent by users through terminal devices. It uses the inherent communication, perception, calculation, mathematics, and intelligence capabilities of intelligent agents to translate user intentions into specific business flows, thereby directly invoking or indirectly driving the capabilities of various objects to realize the user's intentions.

[0129] Among them, the "person" mentioned in the above-mentioned express communication scenario may refer to the user's terminal device, such as the mobile phone shown in Figure 2, or other terminal devices that can send user intentions, including but not limited to tablets, computers with wireless transceiver functions, smart watches, etc. This application does not make specific limitations on this.

[0130] The "machine" mentioned in the above-mentioned communication scenario can refer to a machine, that is, a type of terminal device with specific functions or capable of completing specific tasks, such as the XR device or drone shown in Figure 2, or other terminal devices with specific functions or capable of completing specific tasks, including but not limited to vehicle-mounted terminal devices, wireless terminals in smart homes, terminal devices in Internet of Things systems, etc. This application does not make specific limitations on this.

[0131] The "digital" in the aforementioned expressive communication scenario can refer to a digital human or a digitally intelligent human. These are digital virtual images created using computer graphics (CG) and artificial intelligence technologies. They possess human appearance and behavior, and are capable of intelligent voice interaction, visual recognition, and emotional experience. For example, the digitally intelligent avatar shown in Figure 2.

[0132] The "spirit" mentioned in the aforementioned expressive communication scenario can refer to a class of entities with autonomous or semi-autonomous intelligence. These entities can include physical devices, such as the service robot shown in Figure 2, or other autonomous or semi-autonomous intelligent terminal devices, including but not limited to robots or robot dogs. These entities can also include virtual entities, such as intelligent agents in a network. These intelligent agents can recognize and understand the intent and semantics of physical and / or virtual communication partners, enabling efficient interaction and transfer of intent and semantics between communication partners, and assisting in completing task processing.

[0133] An AI agent is an entity based on artificial intelligence (AI) technology, such as the digital human or digital intelligent being referred to in the preceding "number" or the virtual entity referred to in the preceding "spirit." Different types of terminal devices include, but are not limited to, those referred to in the preceding "human," "machine," and "spirit."

[0134] The "intention" mentioned in the embodiments of this application refers to the expected result of the target object. Intent includes but is not limited to the following information: intention expectation, intention object, intention target, intention context, etc. Intent expectation refers to the business scenario targeted by the intention, such as entrusting a digital human to act as an agent for the user to perform tasks, intelligently driving terminal equipment, expanding the computing power of terminal equipment, and establishing a virtual network for a machine group; the intention object refers to the target object targeted by the intention, such as terminal equipment, base stations, virtual private networks, call applications, computing services, third-party applications, etc.; the intention target refers to the target value that the performance indicator needs to achieve, such as throughput, latency, switching success rate, etc.; the intention context refers to the constraints on the intention expressed through relationships such as comparison, inclusion, and association, such as the duration of the intention, the priority of the intention, etc. The description form of the intention includes but is not limited to natural language, formatted intention expression model, etc., and this application does not make specific limitations on this.

[0135] The "business flow" mentioned in the embodiments of this application refers to the specific information interaction process between the intelligent agent and the object and / or multiple objects required to complete a specific business in a specific business scenario, that is, the specific implementation method of the intention. Depending on the type of information recipient and the degree of autonomous intelligence, the interactive information may include specific signaling, task scheduling strategies, and intentions. The "business flow" in this application is also referred to as "business."

[0136] The communication system 300 provided in the embodiment of the present application is described in detail below with reference to Figure 3. As shown in Figure 4, the system 300 includes a network element 310, which can be a network intelligent agent function (NIAF). NIAF is an implementation method of the intelligent agent mentioned above, which is used to receive and identify intentions from terminal devices (such as smart terminal devices) (or, intentions sent by terminal devices through access networks (AN)), and translate the intentions into specific information interaction methods, thereby directly calling or indirectly driving the capabilities of multiple objects to ultimately achieve the intentions sent by users through terminal devices. As mentioned above, these objects include but are not limited to other NFs or MFs, intelligent agents (such as digital smart people), call applications (such as IMS new calls), third-party AFs, and different types of terminal devices.

[0137] Network element 310 can also map intents to information interaction methods based on a local intent knowledge base. Network element 310 can also have an interaction interface, which can be used to receive intents, interact with other types of information, and forward intents or sub-intents of intents to other devices. It should be understood that the above-mentioned structure and workflow of network element 310 are merely examples, and this application does not specifically limit the internal design of network element 310.

[0138] Optionally, the communication system 300 may further include a network element 330, which may be a session management function (SMF). Various terminal devices, including but not limited to mobile phones, XR glasses, IoT terminals, drones, robot dogs, robots, etc., may establish a session with the network element 310 through the network element 330. In an embodiment of the present application, the session established between the NIAF and the terminal device may be referred to as an intelligent session. The intelligent session is used to implement intention interaction between the terminal device and the network element 310, and / or to implement information interaction between the network element 310 and the terminal device required to achieve the intention, including but not limited to semantic information sent by the terminal device to the network element 310 to express the intention, the intention sent by the network element 310 to the intelligent terminal device that can recognize and implement the intention, the specific signaling used by the network element 310 to control the terminal device, and the multimodal data (such as sensor data, image data, audio and video data, etc.) received or collected by the network element 310 from the terminal device. The terminal device can address the network element 330 through other network elements (such as the access and mobility management function (AMF) network element), or can directly connect to the network element 330, which is not specifically limited in this application. The communication system 300 can also include other network elements, such as a policy control function (PCF), UDM, NEF, and UPF.

[0139] The following describes in detail a communication method provided by an embodiment of the present application based on the above communication system. Figure 4 shows a schematic flow chart of a communication method 400 provided by an embodiment of the present application. Optionally, the method shown in Figure 4 can be applied to the communication system 300 shown in Figure 3.

[0140] In this embodiment, the method is illustrated by taking the network element and the terminal device as the execution subjects of the interaction as an example, but this application does not limit the execution subjects of this interaction. For example, the network element in Figure 4 can also be a chip, chip system, or processor that supports the method that can be implemented by the network element, or a logic module or software that can implement all or part of the network element functions; the terminal device in Figure 4 can also be a chip, chip system, or processor that supports the method that can be implemented by the terminal device, or a logic module or software that can implement all or part of the terminal device functions.

[0141] The following description is made by taking NIAF as an example of a network element and the first device as an example of a terminal device.

[0142] It should be understood that the specific type of terminal device is not limited in the embodiments of the present application. For example, the terminal device can be a UE or other types of terminal devices, and the present application does not make specific limitations on this.

[0143] As shown in FIG4 , the method includes the following steps.

[0144] S410, device #A sends first information to NIAF, and correspondingly, NIAF receives the first information.

[0145] Device #A is an example of a first device.

[0146] The first information is used to describe the first user's intention. Therefore, the first information can also be called an intent description. The intent description can be a natural language description, such as natural language text, voice, or image, or it can be a formatted intent expression model, such as the intent expression model defined by the intent driven management service (IDMS) of the 3rd Generation Partnership Project (3GPP) Management Standards Working Group SA5.

[0147] The first information may be included in an intent request message sent by device #A to the NIAF. The intent request message is used to request the implementation of the intent described in the first information. Optionally, the intent request message may also include other information, such as SUPI, to enable the NIAF or other entities in the system to determine the identity of device #A sending the information.

[0148] Optionally, the intent request message may also carry attachments, including but not limited to pictures, text, voice, video, binary code files, application (APP) installation packages, etc., to expand or supplement the content described in the intent.

[0149] Optionally, NIAF and device #A may interact multiple times to confirm the specific intention of device #A. For example, NIAF may request device #A to supplement the details of the intent description, or NIAF may send the identified intent to device #A to confirm whether the identification is correct, etc. The above attachments may also be provided during multiple confirmation interactions of the intent. The user's intention is to indirectly express that the first device is to interact with a device in a subnet or to interact with a device in a subnet using other devices accessed through the first device. For example, "I want to see family photos stored on the NAS at home"; "I want to use the PAD in the back seat to watch movies stored on the NAS at home", etc. The user does not need to send explicit instructions through the first device to connect the first device to the home network.

[0150] S420: The NIAF determines a first subnet according to the intention of the first user.

[0151] This step includes two ways of determining the first subnet, which are described below respectively.

[0152] Mode 1: The NIAF determines a first subnet from at least one subnet according to the intention of the first user.

[0153] In other words, the NIAF selects a first subnet from at least one subnet.

[0154] In an embodiment of the present application, different subnets may undertake different types of services. For example, the service types can be divided into entertainment services and work services. For example, subnet A is used for work (i.e., the service type corresponding to subnet A is work), and subnet B is used for entertainment (i.e., the service type corresponding to subnet B is entertainment). The network assigns different identifiers to subnets corresponding to different service types. For example, the network assigns identifier 1 to subnet A, and the network assigns identifier 2 to subnet B. It should be understood that users need to sign a contract with the operator's subnet service (such as PIN service) before using the subnet. Specifically, the subnet identifier can be represented by DNN, S-NSSAI.

[0155] Based on the first user's intent, NIAF determines the service type of the subnet the first user requests to access, and further identifies the first subnet within at least one subnet based on the service type. For example, within at least one subnet, NIAF selects the subnet with the same service type as the subnet the first user requested to access as the first subnet. For example, suppose there are three subnets: subnet 1 corresponds to work, subnet 2 corresponds to entertainment, and subnet 3 corresponds to study. Since the first user's intent is work, that is, the service type of the subnet the first user requested to access is work, and subnet 1 is further identified as the first subnet.

[0156] In one possible scenario 1, the at least one subnet belongs to a subnet subscribed by the first user. Device #A sends a first user identifier associated with the first user to the NIAF. The NIAF can then determine the subnet subscribed by the first user based on the first user identifier and further determine the at least one subnet. Specifically, the NIAF determines at least one subnet based on the first user and then determines the first subnet within these subnets.

[0157] In another possible scenario 2, the at least one subnet belongs to a subnet subscribed to by the second user. Device #A sends a first user identifier to the NIAF, which is associated with the first user. The first user's intent includes relationship information between the first and second users. Based on the first user identifier and this relationship information, the NIAF determines the subnet subscribed to by the second user to determine the at least one subnet. For example, this relationship information can be a family relationship, such as if the first and second users belong to the same family. That is, the NIAF determines at least one subnet based on the second user associated with the first user, and further determines the first subnet within these subnets.

[0158] The at least one subnet may be a subnet subscribed by the first user or the second user, or may be a part of a subnet subscribed by the first user or the second user, which is not limited in the embodiment of the present application.

[0159] Furthermore, in scenario 2, one possible implementation is for NIAF to determine whether to allow device #A to access the first subnet based on the second user's verification information. Alternatively, NIAF determines whether to allow device #A to access the first subnet based on the second user's verification information. For example, NIAF can contact the second user's digital avatar or the second user themselves (e.g., by sending a confirmation text message) to confirm whether the first user is allowed to access the first subnet.

[0160] NIAF can also update subscription information. For example, NIAF can update the subscription information of the first subnet, such as by including the first user's identifier in the subscription information of the first subnet. Alternatively, NIAF can update the subscription information of the first user's identifier, such as by including the first subnet's identifier in the subscription information of the first user's identifier. This allows the first user to successfully access the first subnet.

[0161] The identifier of the first subnet can be used to establish a first PDU session. For example, device #A establishes the first PDU session based on the identifier of the first subnet. Specifically, the DNN, S-NSSAI of the first PDU session is the identifier of the first subnet. If the first PDU session and the second PDU session are in different management domains, NIAF can establish a communication tunnel between the second network element and the third network element, the second network element is the user plane network element of the first PDU session, and the third network element is the user plane network element of the second PDU session. Among them, device #B (an example of the second device) is a device belonging to the first subnet. In this way, device #A and device #B in different management domains can establish communication through the communication tunnel.

[0162] Method 2: NIAF establishes the first subnet according to the intention of the first user.

[0163] For example, NIAF forms a first subnet with at least two devices according to the intention of the first user. The at least two devices include device #C (an example of the third device) and device #E (an example of the fourth device).

[0164] Optionally, device #A and device #C belong to the second subnet, and device #D (an example of a fifth device) and device #E belong to the third subnet. Device #C accesses the communication network through device #A, and device #E accesses the communication network through device #D. That is, NIAF, based on the first user's intent, combines devices in two different subnets into a new subnet.

[0165] In one possible implementation 1, NIAF receives a second user identifier from device #A, where the second user identifier is associated with the first user. NIAF determines, based on the second user identifier, the subnets to which the first user has subscribed, such as the second subnet and the third subnet. Specifically, the second subnet and the third subnet are both subnets to which the first user has subscribed.

[0166] In another possible implementation 2, NIAF receives a third user identifier and the identity information of the first user from device #A. The third user identifier is associated with the second user. NIAF determines the second subnet subscribed to by the second user based on the third user identifier, and determines the third subnet subscribed to by the first user based on the identity information of the first user. That is, the second subnet and the third subnet are subnets subscribed to by different users.

[0167] In implementation 2, NIAF can determine whether to allow device #C and device #E to form a network based on the third user's verification information. In other words, NIAF determines whether to allow device #C and device #E to form a network based on the third user's verification information. For example, device #C is a vehicle-mounted device, and device #E is a home device of the third user. NIAF contacts the third user's digital avatar or the third user himself (for example, by sending a confirmation SMS) to confirm whether the first user is allowed to form a network with the third user's home device. The vehicle-mounted device can be the vehicle-mounted device of the third user or the vehicle-mounted device of another person, without limitation.

[0168] Furthermore, NIAF can create subscription information for the first subnet, such that the subscription information for the first subnet includes the third user identifier and the fourth user identifier, and the fourth user identifier is associated with the first user. Alternatively, NIAF can update the subscription information such that the subscription information for device #A and device #D includes the identifier of the first subnet, so that the first user can successfully access the newly established first subnet.

[0169] The identifier of the first subnet can be used by device #A to establish a third PDU session, and can also be used by device #D to establish a fourth PDU session. When the third and fourth PDU sessions are in different administrative domains, NIAF can establish a communication tunnel between the fourth network element (NE) and the fifth network element (NE). The fourth NE is the user plane NE for the third PDU session, and the fifth NE is the user plane NE for the fourth PDU session. In this way, device #A and device #D can establish communication through this communication tunnel.

[0170] S430, NIAF sends the second information to device #A, and correspondingly, device #A receives the second information.

[0171] The second information indicates the first subnet.

[0172] Corresponding to the method 1 in S420, the second information may include the identifier of the first subnet.

[0173] Corresponding to the method 2 in S420, the second information may include the identifier of the first subnet and the identifier of the device #C. That is, the second information includes the identifier of the first subnet and the identifier of the device joining the first subnet.

[0174] Optionally, NIAF may also send third information to device #D, where the third information includes the identifier of the first subnet and the identifier of device #E.

[0175] In one possible implementation, NIAF can send information to device #A or device #D via another server. For example, NIAF sends the second information to device #A via a first application server, with which device #A is registered. NIAF then sends the third information to device #D via a second application server, with which device #D is registered.

[0176] S440, device #A accesses the first subnet according to the second information.

[0177] For example, the second information is a DNN, S-NSSAI combination. Device #A establishes a PDU session corresponding to the (DNN, S-NSSAI) combination and accesses the 5G network. The 5G network connects device #A to the first subnet. Device #A and device #C can then communicate with other devices in the first subnet.

[0178] In this method, NIAF recognizes user intent and determines whether the user is requesting to connect a terminal device to a subnet or to establish a new subnet for devices in two subnets. This allows the network to establish a network based on the user's intent, simplifying the networking process and improving the user experience.

[0179] The above describes the communication method provided in the embodiment of the present application. The embodiment of the present application is further described below with reference to specific implementation examples.

[0180] First, we introduce two communication architectures. One communication architecture is shown in Figure 5 (a). Two subnets (Subnet #1 and Subnet #2) are preconfigured in the user's home network. Subnet #1 is used for work and includes terminal devices such as network attached storage (NAS), printers, and laptops. Subnet #2 is used for entertainment and includes terminal devices such as smart speakers, NAS 1, and smart screens. User Xiao A (the first user in this example) requests access to the home network.

[0181] Another communication architecture is shown in (b) of Figure 5. One subnet (Subnet#1) is preconfigured in the user's home network, and one subnet (Subnet#2) is preconfigured in the car network. User Xiao A requests that the NAS and smart screen in Subnet#1 be combined with the car camera and car pad in Subnet#2 to form a new subnet.

[0182] A possible implementation 1: Xiao A sends an intent to NIAF through the user interface of the mobile phone: I want to view the family photos saved on the NAS at home. This intent indicates that Xiao A is a family member of this "home" and the family photos are saved in the subnet used for entertainment. Xiao A's mobile phone and home network are in the same management domain (that is, the PDU session established by PEGC1 accessing the 5G network and the PDU session established by the UE accessing the 5G network are managed by the same SMF or the same SMF set). In this implementation, NIAF can help Xiao A's UE access the corresponding subnet based on Xiao A's intent request. Since the UE and the subnet are in the same management domain, the same SMF is responsible for managing the establishment of the PDU session for the PEGC of the UE and the subnet. It should be understood that this implementation is an example of method 1 in S420. For details, please refer to the description in S420 and will not be repeated here. This implementation is applicable to the communication architecture shown in (a) in Figure 5.

[0183] Specifically, referring to FIG6 , the implementation includes the following steps:

[0184] S610 , user M (an example of a first user or a second user) requests to establish a PDU session corresponding to Subnet# 1 and Subnet# 2 .

[0185] Subnet#1 and Subnet#2 are examples of at least one subnet. User M subscribes to two subnet services of the operator (such as PIN services). Subnet#1 is used for work and Subnet#2 is used for entertainment. The network assigns an identifier (S-NSSAI1, DNN1) to Subnet#1 and an identifier (S-NSSAI2, DNN2) to Subnet#2. The user identifier of PEGC1 is SUPI1. When the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#1 and Subnet#2. Specifically, PEGC1 sends a PDU session establishment request message to the network, which carries (S-NSSAI1, DNN1) and S-NSSAI2, DNN2 respectively. SMF selects UPF based on (S-NSSAI1, DNN1) and S-NSSAI2, DNN2).

[0186] S620, PEGC1 and UPF establish a tunnel for Subnet#1.

[0187] S630, PEGC1 and UPF establish a tunnel for Subnet#2.

[0188] S640, add NAS1 to Subnet#2.

[0189] For example, after NAS1, where the user saves family photos, is started, NAS1 is added to Subnet#2 according to the configuration of PEMC1.

[0190] S650: The UE registers with the network.

[0191] Optionally, the UE can also establish a PDU session. This PDU session is used for interaction between the UE and the NIAF.

[0192] S660, Xiao A sends an intent request to NIAF through UE (PEGC2).

[0193] The UE's user ID is SUPI2. User A and User M may or may not be the same person. The UE can send an intent to the NIAF via a control plane message or via the user plane. For details, please refer to the description in S410 and will not be repeated here. For example, User A's intent is to view a family photo.

[0194] S670, NIAF Executive Intent Decision.

[0195] That is, NIAF determines that Xiao A wants to request access to the home network based on Xiao A's intended request.

[0196] S680, NIAF identifies and authenticates users based on digital identities.

[0197] For example, NIAF performs identification and authentication based on SUPI2 and received images (such as obtained through a mobile phone camera) or sounds (such as obtained through a mobile phone microphone), as well as Xiao A's digital identity in the network.

[0198] S690: NIAF performs identity confirmation and confirms access to Subnet#2.

[0199] One possible way is that if Xiao A and user M are the same person, when identification and authentication are passed, NIAF requests the UDM for the contract information of the subnet service signed by Xiao A.

[0200] Another possible approach is that if Xiao A and User M are not the same person, NIAF queries Xiao A's digital avatar on the network to determine Xiao A's family members (including User M), and then uses M's identity to sign up for the UDM subnet. In other words, the relationship between Xiao A and User M is considered a family relationship. NIAF then contacts User M's digital avatar or User M himself (for example, by sending a confirmation text message) to confirm whether Xiao A is allowed to access the home network.

[0201] After NIAF obtains the subnet contract from UDM, since Xiao A's intention is to view the family photo, NIAF determines that Xiao A is requesting access to Subnet #2.

[0202] S6100, NIAF returns an intent response message to the UE.

[0203] The intent response message includes an indication to trigger the establishment of a PDU session and the Subnet#2 identifier (S-NSSAI2, DNN2).

[0204] S6110, NIAF updates the contract in UDM.

[0205] That is, the contract information of Subnet#2 includes SUPI2 or the contract information in SUP2 includes S-NSSAI2, DNN2.

[0206] S6120, UE sends a message to SMF requesting to establish a PDU session, and correspondingly, SMF receives the message requesting to establish a PDU session.

[0207] This message includes S-NSSAI2 and DNN2. The SMF can obtain the subscription information from the UDM, accept the UE's request, and select the UPF for the PDU session.

[0208] S6130, UE and UPF establish a PDU session for Subnet#2.

[0209] S6140, SMF sends N4 rule to UPF to configure local switching.

[0210] Data packets between UE and NAS1 will be locally switched at UPF.

[0211] S6150, application layer interaction.

[0212] That is, Xiao A searches for NAS1 through UE and views the family photos saved on NAS1.

[0213] A possible implementation 2: Xiao A sends an intent to NIAF through the user interface of the mobile phone: I want to view the family photos saved on the NAS at grandma's house. Grandma's house and Xiao A's UE are not in the same management domain. Xiao A's mobile phone and grandma's home network are not in the same management domain. (That is, the PDU session established by PEGC1 accessing the 5G network and the PDU session established by UE accessing the 5G network are managed by different SMFs or by different sets of SMFs). In this implementation, NIAF can help Xiao A's UE access the subnet corresponding to grandma according to Xiao A's intention request. It should be understood that this implementation is an example of the first PDU session and the second PDU session in mode 1 in S420 being in different management domains. For details, please refer to the description in S420 and will not be repeated here. This implementation is applicable to the communication architecture shown in (a) in Figure 5.

[0214] Specifically, referring to FIG. 7 , the implementation includes the following steps:

[0215] S710 , user M requests to establish a PDU session corresponding to Subnet# 1 and Subnet# 2.

[0216] User M (Xiao A's grandmother, i.e., the second user example) has signed up for two subnet services (such as PIN services) of the operator, Subnet#1 for work and Subnet#2 for entertainment. The network assigns an identifier (S-NSSAI1, DNN1) to Subnet#1 and an identifier (S-NSSAI2, DNN2) to Subnet#2. The user identifier of PEGC1 is SUPI1. When the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#1 and Subnet#2. Specifically, PEGC1 sends a PDU session establishment request message to the network, which carries (S-NSSAI1, DNN1) and S-NSSAI2, DNN2 respectively. SMF1 selects UPF1 based on (S-NSSAI1, DNN1) and S-NSSAI2, DNN2).

[0217] S720, PEGC1 and UPF establish a tunnel for Subnet#1.

[0218] S730, PEGC1 and UPF establish a tunnel for Subnet#2.

[0219] S740, add NAS1 (ie, device #B in the example) to Subnet #2.

[0220] For example, after NAS1, where the user stores family photos, is started, NAS1 is added to Subnet#2 according to the configuration of PEMC1.

[0221] S750: The UE registers with the network.

[0222] Optionally, the UE can also establish a PDU session. This PDU session is used for interaction between the UE and the NIAF.

[0223] S760, Xiao A sends an intent to NIAF through UE (PEGC2).

[0224] The UE's user ID is SUPI2. User A and user M (grandmother) are not the same person. The UE can send an intent to the NIAF via a control plane message or via the user plane. For details, please refer to the description in S410 and will not be repeated here. For example, User A's intent is to view the family photo.

[0225] S770, NIAF Executive Intent Decision.

[0226] That is, NIAF determines that Xiao A wants to request access to the grandmother's home subnet based on Xiao A's intention request.

[0227] S780, NIAF identifies and authenticates users based on digital identities.

[0228] For example, NIAF performs identification and authentication based on SUPI2 and received images (such as obtained through a mobile phone camera) or sounds (such as obtained through a mobile phone microphone), as well as Xiao A's digital identity in the network.

[0229] S790: NAIF performs identity confirmation and confirms access to Subnet#2.

[0230] One possible approach is that if identification and authentication succeed, NIAF determines Xiao A's grandmother's identity based on Xiao A's digital avatar on the network. NIAF then contacts Xiao A's grandmother's digital avatar or Xiao A's grandmother herself (for example, by sending a confirmation text message) to confirm whether Xiao A is allowed to access the home network. If so, NIAF obtains the grandmother's subnet subscription information from the UDM.

[0231] After NIAF obtains the subnet contract from UDM, based on Xiao A's intention to view the family photo, NIAF determines that Xiao A is requesting access to Subnet #2.

[0232] S7100, NIAF returns an intent response message to the UE.

[0233] The message includes an indication of triggering the establishment of a PDU session and the Subnet#2 identifier (S-NSSAI2, DNN2).

[0234] S7110, NIAF updates the contract in UDM.

[0235] That is, the contract information of Subnet#2 includes SUPI2 or the contract information in SUP2 includes S-NSSAI2, DNN2.

[0236] S7120, UE sends a message to SMF2 requesting to establish a PDU session.

[0237] This message includes S-NSSAI2 and DNN2. SMF2 can obtain subscription information from UDM, accept the UE's request, and select UPF2 for the PDU session.

[0238] S7130, UE and UPF2 establish a PDU session for Subnet#2.

[0239] At S7140, NIAF initiates N9 tunnel establishment requests to SMF1 and SMF2 respectively.

[0240] For example, NIAF interacts with SMF1 and SMF2 respectively to establish an N9 tunnel between UPF1 and UPF2. Data packets between the UE and NAS1 can be exchanged through the N9 tunnel between UPF1 and UPF2.

[0241] On the S7150, an N9 tunnel is established between UPF1 and UPF2.

[0242] S7160, application layer interaction.

[0243] That is, Xiao A searches for NAS1 through UE and views the family photos saved on NAS1.

[0244] In a possible implementation 3, Xiao A sends an intention to NIAF through the user interface of the vehicle terminal: (1) Let the family watch the images captured by the vehicle camera on the smart screen; (2) Play movie #1 on the NAS on the back seat PAD. The vehicle terminal and the home network are in the same management domain. In this implementation, NIAF can help the vehicle camera, PAD in the vehicle network and the smart screen and NAS in the home network form the same subnet according to Xiao A's intention request. Since the vehicle subnet and the home subnet are in the same management domain, the same SMF is responsible for managing the establishment of PDU sessions for the PEGC of the vehicle subnet and the PEGC of the home subnet. In addition, the devices of the home network and the vehicle network are all registered with the application functions provided by the operator. It should be understood that this implementation is an example of method 2 in S420. For details, please refer to the description in S420 and will not be repeated here. This implementation is applicable to the communication architecture shown in (b) in Figure 5.

[0245] Specifically, referring to FIG8 , the implementation includes the following steps:

[0246] S810: Establish a PDU session corresponding to Subnet#1.

[0247] For example, PEMC1 in Xiao A's home network registers PEGC1 and home network devices to AF. AF requests UDM to create subnet Subnet#1 through NEF. The identifier assigned by UDM to Subnet#1 is (S-NSSAI1, DNN1). The user identifier of PEGC1 is SUPI1. PEMC1 configures PEGC1. When the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#1. Specifically, PEGC1 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI1, DNN1). SMF selects UPF based on (S-NSSAI1, DNN1).

[0248] S820, device 1 starts and connects to PEGC1.

[0249] The device 1 is a device in the home network of user A.

[0250] S830: Establish a PDU session corresponding to Subnet#2.

[0251] For example, PEMC2 in the vehicle network of user M registers PEGC2 and the vehicle network equipment to AF. AF requests UDM to create subnet Subnet#2 through NEF. The identifier assigned by UDM to Subnet#2 is (S-NSSAI2, DNN2). The user identifier of PEGC2 is SUPI2. PEMC2 configures PEGC2. When the gateway PEGC2 is started, PEGC2 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#2. Specifically, PEGC2 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI2, DNN2). SMF selects UPF based on (S-NSSAI2, DNN2).

[0252] S840: Device 2 starts and connects to PEGC2.

[0253] The device 2 is a device in the vehicle network.

[0254] At S850, Xiao A sends an intent request to NIAF via the vehicle terminal (PEGC2).

[0255] Xiao A and user M can be the same person (Xiao A purchased the car) or different people (Xiao A's car belongs to a friend or Xiao A rents it). PEGC2 can send the intent to NIAF via a control plane message or via the user plane. For details, please refer to the description in S410 and will not be repeated here.

[0256] S860, NIAF Executive Intent Decision.

[0257] That is, NIAF determines, based on Xiao A's intention request, that Xiao A wants to network the devices in the vehicle network and the devices in the home network.

[0258] S870, NIAF identifies and authenticates users based on digital identities.

[0259] For example, NIAF performs identification and authentication based on SUPI2, received images (captured via the phone's camera) or audio (captured via the phone's microphone), and user A's digital identity on the network. Based on SUPI2 and user A's digital identity, NIAF can determine whether SUPI2 is the terminal device that user A has subscribed to. If not, NIAF can determine the subscribed user, M, based on SUPI2.

[0260] S880: NAIF performs identity confirmation and determines to form Subnet #3.

[0261] Subnet#3 is an example of the first subnet in S420.

[0262] In one possible approach, if Xiao A and user M are the same person, after identification and authentication, NIAF requests UDM to sign up for the subnet service that Xiao A has signed up for. NIAF then obtains the contract description information in steps S810 and S830.

[0263] Another possible method is that if Xiao A and user M are not the same person, NIAF contacts user M's digital avatar or user M himself (for example, by sending a confirmation text message) to confirm whether Xiao A is allowed to connect the in-vehicle network to other networks. Usually, when Xiao A rents a vehicle from user M, user M updates his digital avatar to authorize Xiao A to connect to the network. After NIAF obtains the subnet contract of Xiao A and user M from UDM, it interacts with AF to obtain the devices in Subnet#1 and Subnet#2. According to Xiao A's intention, the in-vehicle camera and PAD in the in-vehicle network and the smart screen and NAS in the home network are combined into the same subnet.

[0264] S890: NIAF sends a networking policy provision message to PEGC1 / PEMC1.

[0265] The message includes instructions for forming Subnet#3, as well as the identifier of Subnet3 (S-NSSAI3, DNN3) and the identifier of the device added to Subnet3 (i.e., device #C) (smart screen, NAS).

[0266] S8100, NIAF sends a networking policy provision message to PEGC2 / PEMC2.

[0267] This message includes an instruction to form Subnet#3, as well as the identifier of Subnet3 (S-NSSAI3, DNN3) and the identifier of the device (i.e., device #E) added to Subnet3 (onboard camera, PAD).

[0268] S8110, NIAF updates the contract in UDM.

[0269] That is, the contract information of Subnet#3 is added, including the identifiers of SUPI1, SUPI2, and Subnet#3 (S-NSSAI3, DNN3), or the contract information in SUPI1 and SUPI2 includes S-NSSAI3, DNN3.

[0270] S8120, PEGC1 sends a message to SMF requesting to establish a PDU session.

[0271] This message includes S-NSSAI3 and DNN3. SMF obtains the subscription information from UDM, accepts the request of PEGC1, and selects UPF for the PDU session.

[0272] S8130, PEGC2 sends a message to SMF requesting to establish a PDU session.

[0273] This message includes S-NSSAI3 and DNN3. SMF obtains the subscription information from UDM, accepts the PEGC2 request, and selects UPF for the PDU session.

[0274] S8140, SMF sends N4 rule to UPF to configure local switching.

[0275] For example, data packets from smart screens, NAS, cameras, and PADs will be locally exchanged in UPF.

[0276] S8150, application layer interaction.

[0277] For example, Xiao A uses the PAD to search for the NAS and view the videos saved on it. The smart screen searches for the car camera and views the captured images.

[0278] For scenarios where Xiao A's home network and car network are not in the same management domain, the implementation process is similar to the above process. The difference is that in S8120 and S8130, the PDU sessions established by PEGC1 and PEGC2 will select different UPFs. In this case, NIAF will be responsible for establishing a tunnel between the two different UPFs for communication.

[0279] In a possible implementation 4, Xiao A sends an intent to NIAF through the in-vehicle terminal user interface: (1) Let family members watch the images captured by the in-vehicle camera on the smart screen; (2) Play movie #1 on the NAS on the back seat PAD. The in-vehicle terminal and the home network are in the same management domain. In this implementation, NIAF can help the in-vehicle camera, PAD in the in-vehicle network and the smart screen and NAS in the home network form the same subnet based on Xiao A's intent request. Since the in-vehicle subnet and the home subnet are in the same management domain, the same SMF or the same SMF set is responsible for managing the establishment of PDU sessions for the PEGC of the in-vehicle subnet and the PEGC of the home subnet. In addition, the devices of the home network and the in-vehicle network are all registered with the application server provided by a third party. This implementation is applicable to the communication architecture shown in (b) in Figure 5.

[0280] S910: Establish a PDU session corresponding to Subnet#1.

[0281] For example, PEMC1 in Xiao A's home network registers PEGC1 and home network devices to the third-party AS1. AS1 requests UDM to create subnet Subnet#1 through NEF. The identifier assigned by UDM to Subnet#1 is (S-NSSAI1, DNN1). The user identifier of PEGC1 is SUPI1. PEMC1 configures PEGC1. When the gateway PEGC1 is started, PEGC1 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#1. Specifically, PEGC1 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI1, DNN1). SMF selects UPF based on (S-NSSAI1, DNN1).

[0282] S920: Device 1 starts and connects to PEGC1.

[0283] The device 1 is a device in the home network of user A.

[0284] S930: Establish a PDU session corresponding to Subnet#2.

[0285] For example, PEMC2 in the in-vehicle network of user M registers PEGC2 and home network devices to the third-party AS2. AS2 requests UDM to create subnet Subnet#2 through NEF. The identifier assigned by UDM to Subnet#2 is (S-NSSAI2, DNN2). The user identifier of PEGC2 is SUPI2. PEMC2 configures PEGC2. When the gateway PEGC2 is started, PEGC2 can interact with the network according to the configuration and request to establish a PDU session corresponding to Subnet#2. Specifically, PEGC2 sends a PDU session establishment request message to the network, and the message carries (S-NSSAI2, DNN2). SMF selects UPF based on (S-NSSAI2, DNN2).

[0286] S940: Device 2 starts and connects to PEGC2.

[0287] The device 2 is a device in the vehicle network.

[0288] At S950, Xiao A sends an intent request to NIAF via the vehicle terminal (PEGC2).

[0289] Xiao A and user M can be the same person (Xiao A purchased the car) or different people (Xiao A's car belongs to a friend or Xiao A rents it). PEGC2 can send the intent to NIAF via a control plane message or via the user plane. For details, please refer to the description in S410 and will not be repeated here.

[0290] S960, NIAF Executive Intent Decision.

[0291] That is, NIAF determines, based on Xiao A's intention request, that Xiao A wants to network the devices in the vehicle network and the devices in the home network.

[0292] S970, NIAF identifies and authenticates users based on digital identities.

[0293] For example, NIAF performs identification and authentication based on SUPI2, received images (captured via the phone's camera) or audio (captured via the phone's microphone), and user A's digital identity on the network. Based on SUPI2 and user A's digital identity, NIAF can determine whether SUPI2 is the terminal device that user A has subscribed to. If not, NIAF can determine the subscribed user, M, based on SUPI2.

[0294] S980: NAIF performs identity confirmation and determines to form Subnet #3.

[0295] Subnet#3 is an example of the first subnet in S420.

[0296] In one possible approach, if user A and user M are the same person, after identification and authentication are successful, NIAF requests the UDM to subscribe to the subnet service that user A has subscribed to. NIAF obtains the subscription description information in steps S910 and S930.

[0297] Another possible way is that Xiao A and user M are not the same person. NIAF contacts user M's digital avatar or user M himself (for example, sending a confirmation text message) to confirm whether Xiao A is allowed to network the in-vehicle network with other networks. If allowed, NIAF requests UDM to sign a contract for the subnet service of Xiao A and user M. Usually when Xiao A rents a vehicle from user M, user M updates his digital avatar to authorize Xiao A to network. After NIAF obtains the subnet contract from UDM, it interacts with AF to obtain the devices in Subnet#1 and Subnet#2, and according to Xiao A's intention, the in-vehicle camera, PAD in the in-vehicle network and the smart screen and NAS in the home network are combined into the same subnet.

[0298] S990: NIAF requests AS1 (an example of the first application server) to obtain information about Subnet#1.

[0299] The information of Subnet#1 includes PEGC1 (SUP1) (an example of device #A), PEMC1, and other devices in the subnet.

[0300] S9100, NIAF requests AS2 (an example of the second application server) to obtain information about Subnet#2.

[0301] The information of Subnet#2 includes PEGC2 (SUP2) (an example of device #D), PEMC2, and other devices in the subnet.

[0302] S9110, NIAF sends a networking policy provision message to PEMC1 / PEGC1 via AS1.

[0303] This message includes an instruction to establish Subnet #3, as well as the identifiers of Subnet 3 (S-NSSAI3, DNN3) and the identifiers of the devices (i.e., device #C) (smart screen, NAS) added to Subnet 3. AS1 further sends the network strategy provision message to PEMC1 / PEGC1.

[0304] S9120, NIAF sends a networking policy provision message to PEMC2 / PEGC2 via AS2.

[0305] This message includes an instruction to establish Subnet#3, as well as the identifiers of Subnet3 (S-NSSAI3, DNN3) and the identifiers of the devices (i.e., device #E) (onboard camera, PAD) added to Subnet3. AS1 further sends a network strategy provision message to PEMC2 / PEGC2.

[0306] S9130, NIAF updates contracting in UDM.

[0307] That is, the contract information of Subnet#3 is added, including the identifiers of SUPI1, SUPI2, and Subnet#3 (S-NSSAI3, DNN3), or the contract information in SUPI1 and SUPI2 includes S-NSSAI3, DNN3.

[0308] S9140, PEGC1 sends a message to SMF requesting to establish a PDU session.

[0309] This message includes S-NSSAI3 and DNN3. SMF obtains the subscription information from UDM, accepts the request of PEGC1, and selects UPF for the PDU session.

[0310] S9150, PEGC2 sends a message to SMF requesting to establish a PDU session.

[0311] This message includes S-NSSAI3 and DNN3. SMF obtains the subscription information from UDM, accepts the PEGC2 request, and selects UPF for the PDU session.

[0312] S9160, SMF sends N4 rule to UPF to configure local switching.

[0313] For example, data packets from smart screens, NAS, cameras, and PADs will be locally exchanged in UPF.

[0314] S9170, application layer interaction.

[0315] For example, Xiao A uses the PAD to search for the NAS and view the videos saved on it. The smart screen searches for the car camera and views the captured images.

[0316] For scenarios where Xiao A's home network and in-vehicle network are not in the same management domain, the implementation process is similar to the above process. The difference is that in S9140 and S9150, the PDU sessions established by PEGC1 and PEGC2 will select different UPFs. In this case, NIAF will be responsible for establishing a tunnel between the two different UPFs for communication.

[0317] Finally, the device embodiment of the embodiment of the present application is introduced.

[0318] To implement the various functions of the methods provided herein, each communication device, such as a network element or terminal device, may include hardware structures and / or software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions 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.

[0319] Figure 10 is a schematic block diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010 and a communication interface 1020, which may be interconnected via a bus 1030. The communication device 1000 may be at least one of the aforementioned network elements, such as a NIAF.

[0320] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 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 to store relevant instructions and data.

[0321] The processor 1010 may be one or more central processing units (CPUs). In the case where the processor 1010 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0322] When the communication device 1000 is a NIAF network element, illustratively, the communication device 1000 is used to perform the following operations: selecting a first subnet, or establishing a first subnet, etc.

[0323] When the communication device 1000 is an SMF network element, illustratively, the communication device 1000 is used to perform the following operations: establishing a PDU session, etc.

[0324] When the communication device 1000 is a UPF network element, illustratively, the communication device 1000 is used to perform the following operations: processing contract information, etc.

[0325] When the communication apparatus 1000 is a terminal device, such as a first device, illustratively, the communication apparatus 1000 is configured to perform the following operations: sending first information; receiving second information; accessing a first subnet, and the like.

[0326] The above contents are merely exemplary descriptions. When the communication device 1000 is at least one of the aforementioned network elements, it will be responsible for executing at least one method or step related to each network element in the aforementioned method embodiment.

[0327] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG10 may also correspond to the corresponding description of the method embodiments shown in FIG4 to FIG9.

[0328] Figure 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. Communication device 1100 may be at least one of the aforementioned communication devices, or a chip or module within any of these communication devices, configured to implement the methods described in the aforementioned embodiments. Communication device 1100 includes a transceiver unit 1110 and a processing unit 1120. The following provides an exemplary description of transceiver unit 1110 and processing unit 1120.

[0329] The transceiver unit 1110 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting operation of the communication device 1100, and the receiving unit is used to perform the receiving operation of the communication device 1100. 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.

[0330] When the communication device 1100 is a NIAF, illustratively, the transceiver unit 1110 is used to receive first information from a first device, and the processing unit 1120 is used to determine a first subnet in at least one subnet according to the intention of the first user, or to establish a first subnet according to the intention of the first user.

[0331] When the communication apparatus 1100 is a terminal device, such as a first device, illustratively, the transceiver unit 1110 is configured to receive the second information.

[0332] The above contents are merely exemplary descriptions. When the communication device 1100 is at least one of the aforementioned communication devices, it will be responsible for executing the methods or steps related to at least one of the communication devices in the aforementioned method embodiments.

[0333] Optionally, the communication device 1100 further includes a storage unit 1130, which is used to store a program or code for executing the aforementioned method.

[0334] The device embodiments shown in Figures 10 and 11 are used to implement the contents described in Figures 4 to 9. The specific execution steps and methods of the devices shown in Figures 10 and 11 can refer to the contents described in the above method embodiments.

[0335] Figure 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 is configured to implement the functions of at least one of the aforementioned communication devices. The communication device 1200 may be a chip in at least one of the aforementioned communication devices.

[0336] Communication device 1200 includes an input / output interface 1220 and a processor 1210. Input / output interface 1220 may be an input / output circuit. Processor 1210 may be a signal processor, a chip, or other integrated circuit capable of implementing the method of the present application. Input / output interface 1220 is used for inputting or outputting signals or data.

[0337] For example, when the communication device 1200 is a first network element, the input and output interface 1220 is used to receive first information from a terminal device, and the processor 1210 is used to determine a first subnet in at least one subnet according to the intention of the first user, or to establish a first subnet according to the intention of the first user.

[0338] In one possible implementation, the processor 1210 implements the functions implemented by at least one of the aforementioned first network element, second network element, third network element, or fourth network element by executing instructions stored in the memory.

[0339] Optionally, the communication device 1200 further includes a memory.

[0340] Optionally, the processor and memory are integrated together.

[0341] Optionally, the memory is outside the communication device 1200 .

[0342] In one possible implementation, the processor 1210 may be a logic circuit, which inputs / outputs messages or signals through the input / output interface 1220. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.

[0343] The above description of the communication device 1200 is only an exemplary description. The communication device 1200 can be used to execute the method described in the above embodiments. For specific content, please refer to the description of the above method embodiments, which will not be repeated here.

[0344] It should also be understood that the above-mentioned communication device is also applicable to various devices, such as the first device, the second device, the third device, the fourth device, the Xth device, and the application server, etc.

[0345] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0346] The present application also provides a chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0347] The present application also provides a processor, which is coupled to a memory and is used to execute the method and function of at least one of the aforementioned communication devices in any of the aforementioned embodiments.

[0348] The present application provides a computer program product comprising instructions. When the computer program product is run on a computer, the method of the aforementioned embodiment is implemented.

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

[0350] The present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

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

[0352] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working 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.

[0353] In the several embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0354] The units described as separate components may or may not be physically separate, and the components shown 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 technical solutions of the embodiments of the present application.

[0355] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0356] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of each method embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0357] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that, The method includes: Receiving first information, where the first information is used to describe the intention of a first user; Determining a first subnet from at least one subnet according to the intention of the first user, or forming the first subnet according to the intention of the first user; Sending second information, where the second information indicates the first subnet.

2. The method according to claim 1, wherein The determining a first subnet from at least one subnet according to the intention of the first user includes: Determining the service type of the subnet to which the first user requests access according to the intention of the first user; Determining the subnet in the at least one subnet that has the same service type as the subnet to which the first user requests access as the first subnet.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receiving a first user identifier, where the first user identifier is associated with the first user; Determining the at least one subnet according to the first user identifier, where the at least one subnet belongs to the subnets subscribed by the first user.

4. The method according to claim 1 or 2, characterized in that The method further includes: Receiving a first user identifier, where the first user identifier is associated with the first user; Determining the at least one subnet according to the first user identifier and the relationship information between the first user and a second user, where the at least one subnet belongs to the subnets subscribed by the second user, and the intention of the first user includes the relationship information between the first user and the second user.

5. The method according to claim 4, wherein The method further includes: Determining to allow a first device to access the first subnet according to the verification information of the second user, where the first device is the device that sends the intention of the first user.

6. The method according to any one of claims 2 to 5, characterized in that The second information includes the identifier of the first subnet.

7. The method according to claim 6, wherein The identifier of the first subnet is used for the first device to establish a first session, where the first device is the device that sends the intention of the first user.

8. The method according to claim 7, characterized in that, If the first session and a second session established with a second device in the first subnet are in different management domains, the method further includes: Establishing a communication tunnel between a second network element and a third network element, where the second network element is the user plane network element of the first session, and the third network element is the user plane network element of the second session.

9. The method according to claim 1, characterized in that, The forming the first subnet according to the intention of the first user includes: Forming the first subnet by at least two devices according to the intention of the first user, where the at least two devices include a third device and a fourth device, where the third device belongs to a second subnet, and the fourth device belongs to a third subnet, and the second subnet is different from the third subnet.

10. The method according to claim 9, characterized in that, The method further includes: Receiving a second user identifier, where the second user identifier is associated with the first user; Determining the second subnet and the third subnet subscribed by the first user according to the second user identifier.

11. The method according to claim 9, wherein The method further includes: Receiving a third user identifier and the identity information of the first user, where the third user identifier is associated with a second user; Determining the second subnet subscribed by the second user according to the third user identifier; Determining the third subnet subscribed by the first user according to the identity information of the first user.

12. The method according to claim 11, wherein The method further includes: Determining to allow the third device to form a network with the fourth device according to the verification information of the third user.

13. The method according to any one of claims 9 to 12, characterized in that, The second information includes the identifier of the first subnet and the identifier of the third device. The identifier of the first subnet is used by the first device to establish a third session. The third device accesses the communication network through the first device. The method further includes: Sending third information to a fifth device, where the third information includes the identifier of the first subnet and the identifier of the fourth device. The identifier of the first subnet is used by the fifth device to establish a fourth session. The fourth device accesses the communication network through the fifth device.

14. A communication method, characterized in that, Applied to a communication device, the method includes: Sending first information, where the first information is used to describe the intention of a first user; Receiving second information, where the second information indicates a first subnet. The first subnet is determined from at least one subnet according to the intention of the first user, or the first subnet is formed according to the intention of the first user; Accessing the first subnet according to the second information.

15. The method according to claim 14, wherein The first subnet is determined from at least one subnet. The first subnet is a subnet among the at least one subnet that has the same service type as the subnet that the first user requests to access. The service type of the subnet that the first user requests to access is determined according to the intention of the first user.

16. The method according to claim 14 or 15, characterized in that, The method further includes: Sending a first user identifier, where the first user identifier is associated with the first user. The first user identifier is used to determine the at least one subnet, and the at least one subnet belongs to the subnets subscribed by the first user.

17. The method according to claim 14 or 15, characterized in that, The method further includes: Sending a first user identifier, where the first user identifier is associated with the first user. The first user identifier and the relationship information between the first user and the second user are used to determine the at least one subnet, and the at least one subnet belongs to the subnets subscribed by the second user. The intention of the first user includes the relationship information between the first user and the second user.

18. The method according to claim 17, wherein The communication device is allowed to access the first subnet according to the verification information of the second user.

19. The method according to any one of claims 14 to 18, characterized in that, The second information includes the identifier of the first subnet.

20. The method according to claim 19, characterized in that, The method further includes: Establishing a first session according to the identifier of the first subnet.

21. The method according to claim 20, characterized in that, If the first session and the second session established with a second device in the first subnet are in different management domains, the method further includes: Establishing a communication tunnel between a second network element and a third network element. The second network element is the user plane network element of the first session, and the third network element is the user plane network element of the second session.

22. The method according to claim 14, wherein The first subnet is formed according to the intention of the first user. The first subnet includes a third device and a fourth device, where the third device belongs to a second subnet and the fourth device belongs to a third subnet. The second subnet is different from the third subnet.

23. The method according to claim 22, wherein The method further includes: Sending a second user identifier, where the second user identifier is associated with the first user. The second user identifier is used to determine the second subnet and the third subnet subscribed by the first user.

24. The method according to claim 22, wherein The method further includes: Send the third user identifier and the identity information of the first user, where the third user identifier is associated with a second user, the third user identifier is used to determine the second subnet subscribed by the second user, and the identity information of the first user is used to determine the third subnet subscribed by the first user.

25. The method according to claim 24, wherein The authentication information of the second user is used to determine that the third device and the fourth device are allowed to form a network.

26. The method according to any one of claims 22 to 25, characterized in that, The second information includes the identifier of the first subnet and the identifier of the third device. The identifier of the first subnet is used to establish a third session, and the third device accesses the communication network through the communication device.

27. The method according to claim 26, wherein The method further includes: Establish a third session according to the identifier of the first subnet.

28. The method according to any one of claims 14 to 27, characterized in that The communication device is a terminal device or a chip in the terminal device.

29. A communication device, characterized in that, It includes a unit for executing the method according to any one of claims 1 to 13 or claims 14 to 28.

30. A communication device, characterized in that, It includes: A processor for executing computer instructions stored in a memory, so that the communication device executes the method according to any one of claims 1 to 13, or so that the communication device executes the method according to any one of claims 14 to 28.

31. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 13; or, the computer is caused to execute the method according to any one of claims 14 to 28.

32. A computer program product, characterized in that, The computer program product includes a computer program or instruction. When the computer program or the instruction runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 13; or, the computer is caused to execute the method according to any one of claims 14 to 28.

33. A communication system, characterized in that, It includes a communication device for executing the method according to any one of claims 1 to 13; and a communication device for executing the method according to any one of claims 14 to 28.

34. A communication method, characterized in that, The method includes: Send a first message, the first message is used to describe the intention of the first user; Determine a first subnet from at least one subnet according to the intention of the first user, or form the first subnet according to the intention of the first user; Send a second message, the second message indicates the first subnet; Access the first subnet according to the second message.

Images