WO2023280000A1 - 一种通信方法、系统和装置 - Google Patents
一种通信方法、系统和装置 Download PDFInfo
- Publication number
- WO2023280000A1 WO2023280000A1 PCT/CN2022/101555 CN2022101555W WO2023280000A1 WO 2023280000 A1 WO2023280000 A1 WO 2023280000A1 CN 2022101555 W CN2022101555 W CN 2022101555W WO 2023280000 A1 WO2023280000 A1 WO 2023280000A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- identifier
- terminal
- network
- network element
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 94
- 238000000034 method Methods 0.000 title claims abstract description 85
- 238000004590 computer program Methods 0.000 claims description 19
- 238000003860 storage Methods 0.000 claims description 12
- 229920006235 chlorinated polyethylene elastomer Polymers 0.000 description 87
- 238000007726 management method Methods 0.000 description 58
- 230000006870 function Effects 0.000 description 50
- 230000008569 process Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000013523 data management Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 238000000136 cloud-point extraction Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/002—Transmission of channel access control information
- H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/002—Transmission of channel access control information
- H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Definitions
- the present application relates to the communication field, and more specifically, to a communication method, system and device.
- the field bus is the underlying communication network used in the production and manufacturing sites. It realizes the bidirectional serial multi-node digital communication between computerized on-site measurement and control instruments or equipment, and has the characteristics of real-time and high stability. Since the International Electrotechnical Commission (IEC) announced and passed the IEC61158 fieldbus standard in 2000, there are now more than ten fieldbus standards.
- Ethernet is a local area network commonly used in the commercial field. Combining transmission control protocol/internet protocol (transmission control protocol/internet protocol, TCP/IP) protocol constitutes the basis of Ethernet and becomes the de facto standard in network applications. It has become the general trend to realize the integration of factory monitoring through the integration of fieldbus control system and enterprise information network through Ethernet.
- the device communication in the industrial field network is currently changing from wired-based communication to wireless-based communication.
- some protocols for discovering devices based on wired communication systems are no longer suitable for the industrial Internet after 5G.
- the link layer discovery protocol (LLDP) running in the PROFINET IO system cannot discover the 5G core network.
- Functional network elements in the network such as user plane function (user plane function, UPF), (wireless) access network (radio access network, (R)AN), etc., and LLDP protocol packets cannot be used by industrial
- the client equipment customer premise equipment, CPE (also called terminal equipment (userequipment, UE)
- CPE customer premise equipment
- UE terminal equipment
- the present application provides a communication method, system, and device, which enable the network side or the network management server side to obtain the topology structure of the 5G industrial Internet, grasp the topological connection relationship between industrial terminals, network terminals, and wireless networks, and realize the control of industrial terminals. management to meet the individual needs of industrial terminals.
- a communication method includes: a first network element receives first information, where the first information includes a first identifier of a first terminal; the first network element sends second information, The second information includes the first identifier, and the second information is used to request a second identifier of a first network, where the first network is a network accessed by the first terminal; the first network element receiving third information, where the third information includes the second identifier; the first network element sends fourth information to the first server, where the fourth information is used to indicate that the first identifier and the second An association relationship identified, the first server is used to manage the first terminal.
- the first terminal may be a terminal device that integrates an industrial terminal device and a network terminal device
- the first server may be a device management server or a management and monitoring software server.
- the first server grasps the connection relationship between the first terminal and the first network, so as to provide personalized service to the first terminal, and realizes the management of the first terminal by the first server.
- the method includes: the first network element sending fifth information, where the fifth information includes the first identifier, and the fifth information is used to request the second terminal's Three identification, the second terminal is a device connected to the first terminal and the first network, the first terminal is an industrial terminal device; the first network element receives sixth information, the sixth information The third identifier is included; the first network element sends seventh information to the first server, where the seventh information is used to indicate an association relationship between the first identifier and the third identifier.
- the second terminal is a network terminal, and the first terminal accesses the first network through the second terminal.
- the first server can provide personalized service to the first terminal by grasping the connection relationship between the first terminal and the second terminal, so that the first server can accurately manage the first terminal.
- the fifth information includes a first event identifier, and the first event identifier is used to indicate that a third identifier of the second terminal is requested.
- the seventh information is further used to indicate an association relationship between the first identifier, the second identifier, and the third identifier.
- the first server can grasp the topological relationship between the first terminal, the second terminal and the first network through the connection relationship between the first terminal and the second terminal and the connection relationship between the first terminal and the first network, thereby Subsequent operations can be performed by using the topology relationship, such as calculating network load, etc., and the first server can accurately manage the first terminal.
- the third identifier includes an International Mobile Subscriber Identity IMSI and/or an International Mobile Equipment Identity IMEI and/or a Permanent Subscriber Identity SUPI and/or a General Public Subscription Identifier GPSI.
- the first identifier includes a media access control layer MAC address and/or an Internet Protocol IP address and/or a device name and/or a device role and/or a device identifier.
- the first identifier may further include a device manufacturer and/or a device instance (instance) of the first terminal and/or a subnet (subnet) accessed by the first terminal and/or a gateway ( gateway).
- the second identifier includes a first cell identifier and/or a first access point name (APN).
- APN access point name
- a communication system which is characterized by including a first terminal, a first network element, and a first server; the first terminal is used to send first information, and the first information includes the first The first identifier of a terminal, the first terminal accesses the first network; the first network element is used to receive the first information; the first network element is also used to send the first information to the first server Two information, the second information includes the first identifier, and the second information is used to request the second identifier of the first network; the first network element is also used to receive the third information, so The third information includes the second identifier; the first network element is further configured to send fourth information to the first server, where the fourth information is used to indicate the association between the first identifier and the second identifier relationship; the first server is used to receive the fourth information, and the first server is also used to manage the first terminal.
- the first terminal may be a terminal device that integrates an industrial terminal device and a network terminal device
- the first server may be a device management server or a management and monitoring software server.
- the first server grasps the connection relationship between the first terminal and the first network, so as to provide personalized service to the first terminal, and realizes the management of the first terminal by the first server.
- the communication system further includes a second terminal; the first network element is configured to send fifth information, the fifth information includes the first identifier, and the fifth information uses In order to request the third identifier of the second terminal, the second terminal is a device connected to the first terminal and the first network, and the first terminal is an industrial terminal device; the first network element also is used to receive sixth information, where the sixth information includes the third identifier; the first network element is also used to send seventh information to the first server, where the seventh information is used to indicate that the first An association relationship between an identifier and the third identifier.
- the second terminal is a network terminal, and the first terminal accesses the first network through the second terminal.
- the first server can provide personalized service to the first terminal by grasping the connection relationship between the first terminal and the second terminal, so that the first server can accurately manage the first terminal.
- the fifth information includes a first event identifier, and the first event identifier is used to indicate that a third identifier of the second terminal is requested.
- the seventh information is further used to indicate an association relationship between the first identifier, the second identifier, and the third identifier.
- the first server can grasp the topological relationship between the first terminal, the second terminal and the first network through the connection relationship between the first terminal and the second terminal and the connection relationship between the first terminal and the first network, thereby Subsequent operations can be performed by using the topology relationship, such as calculating network load, etc., and the first server can accurately manage the first terminal.
- the third identifier includes an International Mobile Subscriber Identity IMSI and/or an International Mobile Equipment Identity IMEI and/or a Permanent Subscriber Identity SUPI and/or a General Public Subscription Identifier GPSI.
- the first identifier includes a media access control layer MAC address and/or an Internet Protocol IP address and/or a device name and/or a device role and/or a device identifier.
- the first identifier may further include a device manufacturer of the first terminal, a device instance (instance), a subnet (subnet) accessed by the first terminal, and a gateway (gateway) accessed by the first terminal.
- the second identifier includes a first cell identifier and/or a first access point name (APN).
- APN access point name
- a communication device in a third aspect, includes: a transceiver module, configured to receive first information, where the first information includes a first identifier of a first terminal; and the transceiver module is also configured to send a second information, the second information includes the first identifier, and the second information is used to request a second identifier of the first network, where the first network is a network accessed by the first terminal; the transceiver module It is also used to receive third information, the third information includes the second identification; the transceiver module is also used to send fourth information to the first server, the fourth information is used to indicate that the first identification and In the association relationship of the second identifier, the first server is used to manage the first terminal.
- the first terminal may be a terminal device that integrates an industrial terminal device and a network terminal device
- the first server may be a device management server or a management and monitoring software server.
- the first server grasps the connection relationship between the first terminal and the first network, so as to provide personalized service to the first terminal, and realizes the management of the first terminal by the first server.
- the device includes: the transceiver module is further configured to send fifth information, the fifth information includes the first identifier, and the fifth information is used to request the second terminal's The third identification, the second terminal is a device connected to the first terminal and the first network, the first terminal is an industrial terminal device; the transceiver module is also used to receive sixth information, the first terminal The sixth information includes the third identifier; the transceiver module is further configured to send seventh information to the first server, and the seventh information is used to indicate an association relationship between the first identifier and the third identifier.
- the second terminal is a network terminal, and the first terminal accesses the first network through the second terminal.
- the first server can provide personalized service to the first terminal by grasping the connection relationship between the first terminal and the second terminal, so that the first server can accurately manage the first terminal.
- the fifth information includes a first event identifier, and the first event identifier is used to indicate that a third identifier of the second terminal is requested.
- the seventh information is further used to indicate an association relationship between the first identifier, the second identifier, and the third identifier.
- the first server can grasp the topological relationship between the first terminal, the second terminal and the first network through the connection relationship between the first terminal and the second terminal and the connection relationship between the first terminal and the first network, thereby Subsequent operations can be performed by using the topology relationship, such as calculating network load, etc., and the first server can accurately manage the first terminal.
- the third identifier includes an International Mobile Subscriber Identity IMSI and/or an International Mobile Equipment Identity IMEI and/or a Permanent Subscriber Identity SUPI and/or a General Public Subscription Identifier GPSI.
- the first identifier includes a medium access control layer MAC address and/or an Internet Protocol IP address and/or a device name and/or a device role and/or a device identifier.
- the first identifier may further include a device manufacturer and/or a device instance (instance) of the first terminal and/or a subnet (subnet) accessed by the first terminal and/or a gateway ( gateway).
- the second identifier includes a first cell identifier and/or a first access point name (APN).
- APN access point name
- a communication device is provided, and the communication device may be the communication device in the foregoing method embodiments, or a chip provided in the communication device.
- the communication device includes a communication interface, a processor, and optionally, a memory.
- the memory is used to store computer programs or instructions
- the processor is coupled to the memory and the communication interface.
- the communication device executes the methods performed by the communication device in the above method embodiments.
- the memory and the processor may be integrated together, or may be independent devices.
- a computer program product includes: computer program code, when the computer program code is executed, the method performed by the above communication device in the above aspects is executed.
- the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to implement the functions of the communication device in the methods of the above aspects.
- the chip system further includes a memory, configured to store program instructions and/or data.
- the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
- the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the methods performed by the above-mentioned communication device in the above-mentioned aspects are implemented.
- Fig. 1 is a diagram of an application scenario applicable to the embodiment of the present application.
- Fig. 2 is a diagram of another application scenario applicable to the embodiment of the present application.
- Fig. 3 is a schematic flowchart of an example of the embodiment of the present application.
- Fig. 4 is a schematic flowchart of another example of the embodiment of the present application.
- Fig. 5 is another schematic flowchart of the embodiment of the present application.
- Fig. 6 is another schematic flowchart of the embodiment of the present application.
- Fig. 7 is another schematic flowchart of the embodiment of the present application.
- Fig. 8 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
- Fig. 9 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
- NB-IoT narrow band-internet of things
- GSM global system of mobile communication
- CDMA code division Multiple access
- WCDMA wideband code division multiple access
- general packet radio service general packet radio service, GPRS
- long term evolution long term evolution, LTE
- LTE frequency division duplex FDD
- LTE time division duplex TDD
- UMTS universal mobile telecommunications system
- WiMAX global interconnection microwave access
- the terminal equipment in the embodiment of the present application may also be referred to as user equipment (user equipment, UE), access terminal, terminal equipment unit (subscriber unit), terminal equipment station, mobile station, mobile station (mobile station, MS), Remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, terminal agent, or terminal device.
- the terminal device may include various handheld devices with wireless communication functions, vehicle-mounted devices, Internet of things (internet of things, IoT) devices, wearable devices, computing devices, or other processing devices connected to a wireless modem.
- IoT Internet of things
- cellular phone cellular phone
- smart phone smart phone
- wireless data card personal digital assistant (personal digital assistant, PDA) computer
- tablet computer wireless modem (modem)
- handheld device handset
- laptop computer laptop computer
- machine type communication machine type communication
- MTC machine type communication terminal
- station station, ST
- wireless local area network wireless local area networks, WLAN
- SIP session initiation protocol
- WLL wireless local loop
- next-generation communication systems such as terminal equipment in 5G networks or future evolved Terminal equipment in the PLMN network, etc.
- the terminal device in the embodiment of the present application may also be an industrial terminal device, which may include a controller device (for example, a programmable logic controller (programmable logic controller, PLC)), an industrial input/output (input/output, IO ) equipment and other equipment used for industrial operations in industrial scenarios, the industrial terminal equipment can be connected to the 5G network through the 5G terminal equipment, so as to be managed and monitored by the server; the terminal equipment in the embodiment of this application can also be equipped with 5G Industrial terminals with communication capabilities, for example, industrial terminal equipment with built-in 5G communication modules.
- a controller device for example, a programmable logic controller (programmable logic controller, PLC)
- an industrial input/output (input/output, IO ) equipment and other equipment used for industrial operations in industrial scenarios
- the industrial terminal equipment can be connected to the 5G network through the 5G terminal equipment, so as to be managed and monitored by the server
- the terminal equipment in the embodiment of this application can also be equipped with 5G Industrial terminals with communication capabilities,
- 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 global system of mobile communication (GSM) system or a code division multiple access (code division multiple access, CDMA) base transceiver station (BTS), or a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved base station (evolutional nodeB) in an LTE system , eNB or eNodeB), can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or a satellite base station in a satellite communication system, or a network device can be a relay station, an access point , in-vehicle devices, wearable devices, and network devices in a 5G network or network devices in a future evolved PLMN network, etc., are not limited in this embodiment of the present application.
- GSM global system of mobile communication
- CDMA code division multiple access
- BTS base transce
- Protocol data unit (protocol data unit, PDU) session A session service for realizing PDU connectivity between UE and data network, identified by PDU session ID (Session ID).
- 5G local area network (local area network, LAN) is a LAN created by using 5G new air interface. Using 5G LAN can realize reliable and efficient transmission in the industrial Internet and keep the business in LAN isolated from the public network.
- CPE It is a UE device defined in the 3rd Generation Partnership Project (3GPP).
- 3GPP 3rd Generation Partnership Project
- the current industrial input and output devices are connected to the 5G-LAN network through the CPE.
- Programmable logic controller (programmable logic controller, PLC) is an electronic device specially designed for digital operation in industrial environments.
- Human machine interface human machine interface, HMI: also known as touch screen monitor, is an intelligent operation control and display device.
- FIG. 1 is a diagram of an application scenario applicable to the embodiment of the present application.
- FIG. 1 is a diagram of an application scenario applicable to the embodiment of the present application.
- Each network element that may be involved in the network architecture 100 shown in FIG. 1 will be described respectively below.
- UE110 refer to the description above, and will not go into details here.
- network element may also be referred to as an entity, device, device, or module, etc., which are not specifically limited in this application.
- description of “network element” is omitted in some descriptions, for example, (R)AN network element is referred to as (R)AN, in this case, the “(R) ”) AN network element” should be understood as (R)AN network element or (R)AN entity, and the description of the same or similar situations will be omitted below.
- User plane network element 130 used for packet routing and forwarding, and user plane data quality of service (quality of service, QoS) processing, etc.
- the user plane network element may be a user plane function (user plane function, UPF) network element.
- UPF user plane function
- the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
- Data network 140 used to provide a network for transmitting data.
- the data network may be a data network (data network, DN).
- the data network may still be a DN, or may have other names, which are not limited in this application.
- Access management network element 150 mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in mobility management entity (mobility management entity, MME) functions, for example, legal functions such as monitoring and access authorization/authentication.
- mobility management entity mobility management entity, MME
- the access management network element may be an access and mobility management function (access and mobility management function, AMF) network element.
- AMF access and mobility management function
- the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
- Session management network element 160 mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, selection of manageable user plane functions, termination points of policy control and charging function interfaces, and downlink Data Notification etc.
- IP network interconnection protocol
- the session management network element may be a session management function (session management function, SMF) network element.
- SMF session management function
- the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
- Policy control network element 170 a unified policy framework for guiding network behavior, providing policy rule information and the like for control plane functional network elements (such as AMF, SMF network elements, etc.).
- the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element.
- policy control network element may be a policy control function (policy control function, PCF) network element.
- policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
- Unified data repository function (unified data repository, UDR) network element 180: used to provide contract data to UDM network elements or obtain contract data from UDM network elements; and provide policy data to PCF network elements, or obtain contract data from PCF network elements Get policy data, etc. in the meta.
- Data management network element 190 used for processing terminal equipment identification, access authentication, registration and mobility management, etc.
- the data management network element may be a unified data management (unified data management, UDM) network element.
- UDM unified data management
- the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
- Network opening function network element 1100 mainly used for services and capabilities provided by the secure open 3GPP network function, which may be opened internally or to third parties.
- the network exposure function network element may be a network exposure function network element (network exposure function, NEF).
- NEF network exposure function
- the network element with the network opening function may still be an NEF network element, or may have other names, which are not limited in this application.
- an application function network element used to implement information exchange between an external server and a 3GPP network.
- the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
- N7 The interface between PCF and SMF, which is used to deliver PDU session granularity and service data flow granularity control policies.
- N15 the interface between the PCF and the AMF, used to issue UE policies and access control-related policies.
- N5 the interface between the AF and the PCF, used for sending application service requests and reporting network events.
- N4 The interface between SMF and UPF, which is used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules for the user plane, QoS control rules, traffic statistics rules, etc., and reporting of user plane information .
- N11 The interface between SMF and AMF, used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, transfer radio resource control information sent to RAN, etc.
- N2 the interface between the AMF and the RAN, used to transmit radio bearer control information from the core network side to the RAN.
- N1 The interface between the AMF and the UE, which has nothing to do with access, and is used to transfer QoS control rules to the UE.
- N8 The interface between AMF and UDM, which is used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register UE current mobility management related information with UDM.
- N10 the interface between the SMF and the UDM, used for the SMF to obtain session management-related subscription data from the UDM, and for the SMF to register UE current session-related information with the UDM.
- N35 interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.
- N36 the interface between the PCF and the UDR, used for the PCF to obtain policy-related subscription data and application data-related information from the UDR.
- N52 The interface between UDM and NEF, which is used for NEF to open network capabilities to third-party application functions, such as third-party application functions subscribe to UDM through NEF to reachability events of all users in a specific group.
- NEF also has direct interfaces with AMF and SMF, corresponding to N29 interface and N51 interface respectively (to simplify the illustration, not shown in the above figure), which is used to open the operator's network capabilities to third-party application function entities, the former can be used
- the NEF directly subscribes to the corresponding network events and updates the user configuration information to the AMF, which can be used to update the application configuration data on the SMF/UPF, such as the PFD (Packet Flow Description) packet flow description information corresponding to the Application ID.
- AMF Packet Flow Description
- the general user registration process can be simply described as: UE sends a registration request to AMF through AN, AMF obtains subscription data from a specific UDM according to the user ID, and UDM can obtain actual subscription data from UDR after receiving the request.
- the AMF can also initiate a user policy control creation request (UEPolicyControl_Create) and an access management policy control creation request (AMPolicyControl_Create) to the PCF, which are used to obtain UE policies and access control policies respectively.
- UEPolicyControl_Create user policy control creation request
- APolicyControl_Create access management policy control creation request
- the PCF returns the access control policy to the AMF, and provides the UE policy to the UE via the AMF.
- the general session establishment process can be simply described as: UE sends a session establishment request to AMF through RAN, AMF selects SMF to provide services for the session, saves the corresponding relationship between SMF and PDU session, and sends the session establishment request to SMF, SMF Select the corresponding UPF for the UE, establish a user plane transmission path, and assign an IP address to it.
- the SMF will also initiate a policy control session establishment request to the PCF for establishing a policy control session between the SMF and the PCF.
- the SMF will save the correspondence between the policy control session and the PDU session .
- the AF can also establish an AF session with the PCF, and the PCF binds the AF session and the policy control session.
- network architecture applied to the embodiment of the present application is only an example network architecture described from the perspective of the 5G networking architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto.
- the network architecture of the functions of the elements are applicable to the embodiment of the present application.
- network functional entities such as AMF, SMF, PCF, and UDM are called network function (Network Function, NF) network elements; or, in other network architectures, AMF, SMF, PCF, and UDM
- AMF, SMF, PCF, and UDM A collection of such network elements can be called a control plane function (Control Plane Function, CPF) network element.
- CPF Control Plane Function
- the embodiments of the present application describe various embodiments in conjunction with core network equipment, wherein the functions of the core network are mainly to provide user connections, manage users, and carry out services, and provide interfaces to external networks as the bearer network.
- the establishment of a user connection includes functions such as mobility management (MM), call management (Connection Management, CM), switching/routing, and recording notification.
- MM mobility management
- CM Call Management
- CM Connection Management
- switching/routing switching/routing
- Record notification includes user description, quality of service (Quality of Service, QoS), user communication records (accounting), virtual home environment (virtual home environment, VHE) and security (corresponding security measures provided by the authentication center include Security management of mobile services and security processing of external network access).
- QoS Quality of Service
- VHE virtual home environment
- security corresponding security measures provided by the authentication center include Security management of mobile services and security processing of external network access.
- Bearer connections include to the external public switched telephone network (public switched telephone network, PSTN), external circuit data network and packet data network, the Internet and the intranet (intranets), and mobile phone text messages of the mobile network itself Service (short message service, SMS) server and so on.
- PSTN public switched telephone network
- intranets the Internet and the intranet (intranets)
- SMS short message service
- the basic services that the core network can provide include mobile office, e-commerce, communication, entertainment services, travel and location-based services, remote sensing services (telemetry), simple message delivery services (monitoring and control), and so on.
- FIG. 2 is another application scenario diagram applicable to the embodiment of the present application.
- the industrial input and output (Input/Output, IO) equipment is connected to the 5G-LAN through the CPE, and through the RAN, UPF, switch (switch) is connected with monitoring and diagnosis software/HMI, PLC.
- the present application provides a method 200, as shown in FIG. 3 , which is a schematic flowchart of an example of an embodiment of the present application.
- the first terminal sends the first information, and the first network element receives the first information.
- the first information includes a first identifier of the first terminal.
- the first terminal may be a terminal device integrating an industrial terminal device and a network terminal device.
- the first identifier includes a media access control layer MAC address and/or an Internet Protocol IP address and/or a device name and/or a device role and/or a device identifier.
- the first identifier may further include a device manufacturer and/or a device instance (instance) of the first terminal and/or a subnet (subnet) accessed by the first terminal and/or a gateway ( gateway).
- the first network element sends the fifth information to the third network element, and receives sixth information from the third network element.
- the fifth information includes the first identification
- the fifth information is used to request the third identification of the second terminal
- the second terminal is a device connected to the first terminal and the first network
- the first terminal is an industrial terminal device.
- the sixth information includes the third identification.
- the second terminal is a network terminal, and the first terminal accesses the first network through the second terminal.
- the fifth information includes a first event identifier, and the first event identifier is used to indicate the request for the third identifier of the second terminal.
- the third identifier includes an International Mobile Subscriber Identity IMSI and/or an International Mobile Equipment Identity IMEI and/or a Permanent Subscriber Identity SUPI and/or a General Public Subscription Identifier GPSI.
- the first network element sends the second information, and the second network element receives the second information.
- the second information includes the first identifier, and the second information is used to request the second identifier of the first network, and the first network is a network accessed by the first terminal.
- the second identifier includes the first cell identifier and/or the first access point name APN.
- the second network element sends the third information, and the first network element receives the third information.
- the third information includes the second identification.
- the first network element sends fourth information to the first server, and the first server receives the fourth information.
- the fourth information is used to indicate the association relationship between the first identifier and the second identifier, and the first server is used to manage the first terminal.
- the first server may be a device management server or a management and monitoring software server.
- the first network element sends seventh information to the first server, where the seventh information is used to indicate an association relationship between the first identifier and the third identifier.
- the seventh information is also used to indicate an association relationship between the first identifier, the second identifier, and the third identifier.
- the first server can grasp the topological relationship between the first terminal, the second terminal and the first network through the connection relationship between the first terminal and the second terminal and the connection relationship between the first terminal and the first network, thereby Subsequent operations can be performed by using the topology relationship, such as calculating network load, etc., and the first server can accurately manage the first terminal.
- FIG. 4 is another schematic flowchart of an embodiment of the present application.
- CPE#1 and UPF#1 have set up Ethernet (ethernet, ETH) PDU session and IP PDU session, and the agent (agent) software on CPE#1 has completed in equipment management server# 1 on the registration.
- Ethernet ethernet, ETH
- agent agent
- this application proposes an industrial field enable service (industrial field enable service, IFES) application/service, which is responsible for extracting the information of the industrial terminal, the connection relationship between the industrial terminal and the CPE, the CPE and the connection between the CPE and the CPE.
- the association relationship of the network for example, the association relationship between the identification code information of the CPE and the information of the network that the CPE accesses, the identification code information of the CPE can be: international mobile subscriber identification number (international mobile subscriber identification number, IMSI), international mobile equipment The identification code (international mobile equipment identity, IMEI); the information of the network that the CPE accesses may be associated information such as the access point name (Access Point Name, APN) and the cell identity.
- IFES can be used as an application/service to access the network (such as 5G core network) accessed by CPE. Therefore, IFES can be considered as a type of AF, which is not limited in this application.
- IFES#1 sends information #A through UPF#1, RAN#1 and CPE#1, and industrial terminal #1 receives information #A through CPE#1.
- the IFES sends information #A through a discovery and basic configuration protocol (discovery and basic configuration protocol, DCP).
- DCP discovery and basic configuration protocol
- IFES#1 sends information #A in a multicast manner, and one or more industrial terminals send response information to IFES#1 after receiving information #A, and one of the industrial terminals is as follows, That is, industrial terminal #1 is taken as an example for description.
- the information #A is used to request the equipment information of the industrial terminal #1 from the industrial terminal #1.
- the device information includes at least one of the following information:
- Equipment manufacturer the name or logo of the manufacturer that produced the equipment
- Device name the name of the device
- ID the identification of the device
- Device role that is, whether the device is a controller (responsible for managing other devices, that is, responsible for issuing control commands to other devices) or a device (not responsible for managing other devices, that is, accepting control commands issued by the controller);
- Device instance the virtual generation of a copy of the device entity that is actually used and loaded into memory
- Media access control layer (media access control, MAC) address: the address used to confirm the location of the device;
- IP address the logical address of the device that conforms to the IP protocol
- Subnet the subnet to which the device is connected
- Gateway the gateway connected to the device.
- the industrial terminal #1 determines the information #B.
- industrial terminal #1 determines information #B, and information #B is used for industrial terminal #1 to respond to information #A.
- the information #B includes the equipment information of the industrial terminal #1, and for the equipment information, please refer to the above description, which will not be repeated here.
- the industrial terminal #1 if the industrial terminal #1 operates normally, the industrial terminal #1 sends an identity confirmation (identity OK) message to the IFES #1, and the message is used to indicate that the query is successful.
- identity OK identity confirmation
- Industrial terminal #1 sends information #B, and IFES #1 receives information #B.
- industrial terminal #1 sends information #B through CPE#1, RAN#1, and UPF#1, and IFES#1 receives information #B through UPF#1.
- UPF #1 has acquired MAC address #1 of industrial terminal #1.
- the industrial terminal #1 sends the information #B through the DCP protocol.
- industrial terminal #1 periodically sends information #B, at this time, the IFES does not need to send information #A, and industrial terminal #1 does not need to receive information #A.
- association relationship #1 is used to associate various equipment information of industrial terminals, such as Table 1.
- the device information in Table 1 may also include other device information, such as device manufacturer, subnet and so on.
- the MAC address #1, device name #1, IP address #1, device ID #1, and device role #1 in Table 1 are the device information of the industrial terminal #1, then these device information are associated Corresponds to the same industrial terminal.
- IFES#1 can grasp the equipment information of industrial terminal #1 through information #B.
- IFES#1 determines the identity of CPE#1.
- FIG. 5 is another example of a schematic flowchart of the embodiment of the present application, used to represent the specific process of IFES obtaining the CPE identification:
- Step a CPE#1 initiates an Ethernet type PDU session establishment request.
- connection between the CPE#1 and the industrial terminal #1 is taken as an example for description.
- Step b SMF#1 and PCF#1 update the session management policy.
- SMF#1 and PCF#1 update the session management policy
- SMF#1 sends MAC address #1 to PCF#1.
- PCF#1 has MAC address #1 and CPE Correspondence of #1.
- SMF#1 sends the MAC address #1 through a session management policy association update request (session management policy association update request) message.
- session management policy association update request session management policy association update request
- UPF#1 sends MAC address #1 of industrial terminal #1, SMF#1 receives MAC address #1, SMF#1 sends MAC address #1, PCF#1 receives MAC address #1.
- UPF#1 judges whether MAC address #1 is a new MAC address, and if it is a new MAC address, sends the MAC address #1, if it is not a new MAC address, it means that MAC address #1 has been sent, and MAC address #1 will not be sent this time.
- Step c PCF#1 initiates a binding information registration/update process to BSF#1 based on the received MAC address #1 (that is, the MAC address of industrial terminal #1), which carries information #C, and information #C includes At least one of the following information:
- Subscriber permanent identifier for example, subscriber permanent identifier information of CPE#1;
- GSM Generic public subscription identifier
- MAC address for example, MAC address information of industrial terminal #1
- Data network name for example, information about the name of the 5G core network accessed by CPE#1;
- Single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), for example, single network slice selection assistance information accessed by CPE#1;
- PCF ID/address for example, ID/address information of PCF#1.
- Step d IFES#1 obtains the identification information of CPE#1 in the following two ways:
- IFES#1 sends information #D to PCF#1, wherein information #D is used to request to query user identification information.
- PCF#1 can determine the identifier (for example, SUPI, GSPI) of CPE#1 corresponding to MAC address #1 according to information #D and send it to IFES#1,
- the information #D includes the MAC address information of the industrial terminal, for example, the MAC address #1 of the industrial terminal #1.
- IFES#1 requests the identification information of the connected CPE#1 from the NEF by sending the MAC address #1 of the industrial terminal #1.
- information #D may also include DNN.
- the information #D may also include an event ID (event ID), which is used to indicate that the event type initiated by the information #D is the query user ID.
- event ID an event ID
- IFES#1 determines and transmits information #D, and NEF#1 receives information #D.
- Step d1 NEF#1 executes PCF query to BSF#1 according to MAC address #1, and obtains the identifier/address of PCF#1.
- Step d2 NEF#1 determines and sends information #E, PCF#1 receives information #E.
- NEF#1 sends information #E to PCF#1 according to the identifier/address of PCF#1, and information #E is used to request to query the identifier information of CPE#1 connected to industrial terminal #1.
- the information #E includes the MAC address #1 of the industrial terminal #1, and may also include a DNN, and/or an event identifier.
- Step d3 PCF#1 determines and sends message #F, and NEF#1 receives message #F.
- PCF#1 determines the identity of CPE#1 connected to industrial terminal #1 according to information #E, and information #F includes the identity of CPE#1.
- information #F includes at least one of the following information:
- SUPI such as SUPI#1 of CPE#1;
- GPSI such as GPSI#1 of CPE#1;
- IMSI such as IMSI#1 of CPE#1.
- Step d4 NEF#1 determines and sends information #G, and IFES#1 receives information #G.
- NEF#1 determines the identity of CPE#1 according to information #F, and information #G includes the identity of CPE#1.
- information #G refer to the content of information #F, which will not be repeated here.
- PCF#1 determines and sends information #G, and PCF#1 receives information #G.
- association relationship #2 is used to associate the industrial terminal with the CPE.
- IFES determines association relationship #2 according to information #G, such as Table 2.
- information #H is used to request to query the equipment information and access network information of CPE#1.
- the information #H includes IMSI#1 of CPE#1, and may also include an event ID (event ID), which is used to indicate that the initiated event is to query the device information and access network information of the CPE corresponding to the IMSI.
- event ID event ID
- the device management server #1 sends the information #I, and the IFES #1 receives the information #I.
- the device management server #1 determines the information #I according to the information #H, and the information #I includes the IMEI #1 corresponding to the CPE #1 and/or the APN #1 corresponding to the CPE #1 and/or the cell corresponding to the CPE #1 Identification #1 and other information.
- association relationship #3 determines association relationship #3 according to information #1, and association relationship #3 is used to associate the device information of the CPE with the network information accessed by the CPE. For example Table 3.
- IMSI Community ID IMEI APNs ... IMSI#1 Cell ID #1 IMEI#1 APN#1 ... ... ... ... ... ... ... ...
- the device information used to associate the CPE and the network information accessed by the CPE may be IMSI and cell ID, or IMSI, IMEI and cell ID, or IMSI and APN, or IMSI, cell ID and APN, etc. , that is, the content in Table 3 is only used as an example of the device information associated with the CPE and the network information accessed by the CPE, and does not constitute a limitation to this application.
- IMSI#1 and IMEI#1 are used as the equipment information of CPE#1.
- 1 is used as the network information accessed by CPE#1, and the two are associated together.
- the information #J includes the association relationship #4, and the association relationship #4 is used to associate the industrial terminal, the CPE, and the network information corresponding to the CPE.
- IFES#1 determines association relationship #4 according to association relationship #1, association relationship #2 and association relationship #3. For example as shown in Table 4.
- the network information used to associate industrial terminals, CPE and CPE access can be MAC address, IP address, IMSI, APN, or MAC address, device name, IP address, IMSI, APN, cell identity, or It is a combination of MAC address, device ID, IP address, IMSI, APN, cell identifier, IMEI, etc., and is not limited to the combinations in Table 4, and will not be described here in this application.
- MAC address #1, device name #1, IP address #1, device ID #1 and Device role #1 is the device information corresponding to industrial terminal #1
- IMSI#1 and IMEI#1 are the device information corresponding to CPE#1
- APN#1 and cell ID #1 are the network information corresponding to CPE#1 access
- three are associated together
- IFES#1 grasps the topological relationship of the entire network through association relationship #4.
- IFES#1 sends information #J through a simple network management protocol (simple network management protocol, SNMP).
- simple network management protocol simple network management protocol, SNMP
- the method 300 uses the industrial terminal #1 as an example to describe how the IFES#1 obtains the entire network topology structure.
- the method 300 is also applicable to the IFES#1 obtaining the entire network topology structure including multiple industrial terminals.
- IFES can obtain the association relationship between industrial terminals and CPE, and the association relationship between CPE and the network connected to CPE, so as to grasp the topology structure of the entire network and enable the core network to realize Customized bandwidth or services are provided.
- the relationship between industrial terminals and CPE is obtained through the above method, which makes it easier to replace the binding relationship between industrial terminals and CPE.
- the association relationship between the CPE and the network accessed by the CPE it can ensure that subsequent operations such as network load calculation can be accurately performed.
- the application provides method 400 to update the topology of the entire network, as shown in Figure 6, which is an embodiment of the application Another example schematic flow chart of .
- IFES#1 periodically updates the topology of the entire network.
- IFES#1 has a "topology update timer" inside, and when the timer expires, IFES#1 is triggered to update the topology of the entire network.
- IFES#1 deletes the original topology information after reacquiring the topology information of the whole network according to the methods S310-S3110, and retains the latest topology information.
- the present application also provides a method 500 for updating the topology of the entire network, as shown in FIG. 7 , which is another schematic flowchart of an embodiment of the present application.
- the industrial terminal #2 determines the information #B1.
- the industrial terminal #2 sends the information #B1, and the IFES#1 receives the information #B1.
- IFES#1 judges whether the industrial terminal #2 is a new device according to information #B1 and Table 1 (or association relationship #1).
- MAC address #2, device name #2, IP address #2, device ID #2, and device role #2 are the device information of industrial terminal #2.
- the equipment information in the information #B1 is exactly the same as the equipment information of the industrial terminal in Table 1, it is judged that the industrial terminal #2 is an old equipment, and the equipment information of the information #B1 is not stored in the Table 1.
- IFES#1 receives identification information of CPE#2 corresponding to industrial terminal #2.
- IFES#1 stores MAC address #2 and IMSI#2 corresponding to CPE#2 in Table 2, and the updated Table 2 is as follows:
- the message #H1 is for requesting to query the equipment information and access network information of CPE#2.
- the message #H1 is for requesting to query the equipment information and access network information of CPE#2.
- method S380 which will not be repeated here.
- the device management server #1 sends the information #I1, and the IFES #1 receives the information #I1.
- the device management server #1 determines the information #I1 according to the information #H1, and the information #I1 includes the IMEI#2 corresponding to the CPE#2 and/or the APN#2 corresponding to the CPE#2 and/or the cell corresponding to the CPE#2 Identification #2 and other information.
- IFES#1 maintains or updates association relationship #3.
- IFES#1 updates association relationship #3 according to information #I1, such as the following updated Table 3:
- IMSI Community ID IMEI APNs ... IMSI#1 Cell ID #1 IMEI#1 APN#1 ... IMSI#2 Cell ID #2 IMEI#2 APN#2 ... ... ... ... ... ... ... ... ... ...
- IFES#1 determines the updated table 4 according to the updated table 1, the updated table 2, and the updated table 3, and the updated table 4 is as follows:
- information #J1 includes the newly added association relationship between industrial terminal #2, CPE#2 and the network information accessed by CPE#2 in Table 4, for example, information #J1 includes MAC address #2, device name #2 , IP address #2, device ID #2, device role #2, IMSI #2, IMEI #2, APN #2, cell ID #2 and other information, so that the management and monitoring software server #1 can grasp the latest network topology structure.
- the IFES is enabled to regularly update the network-wide topology relationship, and regularly report the updated network-wide topology relationship to the management and monitoring software.
- FIG. 8 and FIG. 9 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication apparatuses can realize the functions of the terminal equipment or the network equipment in the above method embodiments, and therefore can also realize the beneficial effects of the above method embodiments.
- the communication device may be the first communication device (corresponding to the first network element) in the method 200, or may be a module (such as a chip) applied to the first communication device.
- a communication device 600 includes a transceiver module 601 and a processing module 602 .
- the communication device 600 may be used to implement the functions of the first communication device in the method embodiment shown in FIG. 3 above.
- the transceiver module 601 is used to receive first information, the first information includes a first identifier of a first terminal; the The transceiver module 601 is further configured to send second information, where the second information includes the first identifier, and the second information is used to request a second identifier of a first network, where the first network is the first terminal access network; the transceiving module 601 is further configured to receive third information, the third information includes the second identifier; the transceiving module 601 is further configured to send fourth information to the first server, the first Four information is used to indicate the association relationship between the first identifier and the second identifier, and the first server is used to manage the first terminal.
- the processing module 602 is configured to determine the above-mentioned second information and the above-mentioned fourth information.
- transceiver module 601 For a more detailed description of the foregoing transceiver module 601 and processing module 602, reference may be made to relevant descriptions in the foregoing method embodiments, and no further description is given here.
- the communication device 700 includes a processor 710 and an interface circuit 720 .
- the processor 710 and the interface circuit 720 are coupled to each other.
- the interface circuit 720 may be a transceiver or an input-output interface.
- the communication device 700 may further include a memory 730 for storing instructions executed by the processor 710, or storing input data required by the processor 710 to execute the instructions, or storing data generated by the processor 710 after executing the instructions.
- the memory 730 and the processor 710 may be integrated together, or may be independent devices.
- the processor 710 is used to execute the functions of the above-mentioned processing module 602
- the interface circuit 720 is used to execute the functions of the above-mentioned transceiver module 601 .
- the chip of the first communication device implements the functions of the first communication device in the above method embodiment.
- the first communication device chip receives information from other modules (such as radio frequency modules or antennas) in the first communication device; or, the first communication device chip sends information to other modules (such as radio frequency modules or antennas) in the first communication device information.
- processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
- CPU central processing unit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- a general-purpose processor can be a microprocessor, or any conventional processor.
- each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. place.
- the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.
- the systems and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.
- the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
- Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (random access memory, RAM), flash memory, read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or known in the art any other form of storage medium.
- An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
- the storage medium may also be a component of the processor.
- the processor and storage medium can be located in the ASIC.
- the ASIC may be located in the access network device or the terminal device.
- the processor and the storage medium may also exist in the access network device or the terminal device as discrete components.
- all or part of them may be implemented by software, hardware, firmware or any combination thereof.
- software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
- the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
- the computer program or instructions may be stored in or transmitted via a computer-readable storage medium.
- the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
- the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (solid state disk, SSD).
- a magnetic medium such as a floppy disk, a hard disk, or a magnetic tape
- an optical medium such as a DVD
- it may also be a semiconductor medium such as a solid state disk (solid state disk, SSD).
- “at least one” means one or more, and “multiple” means two or more.
- “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
- the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a "division” Relationship.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种通信方法,使能网络侧或者网络管理服务器侧能够获取5G工业互联网的拓扑结构,掌握工业终端、网络终端、无线网络的拓扑连接关系,实现对工业终端的管理,所述方法包括:第一网元接收第一信息,所述第一信息包括第一终端的第一标识;所述第一网元发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述第一网元接收第三信息,所述第三信息包括所述第二标识;所述第一网元向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。
Description
本申请要求于2021年7月6日提交中国专利局、申请号为202110760280.6、申请名称为“一种通信方法、系统和装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信领域,并且更具体地,涉及一种通信方法、系统和装置。
现场总线是用于生产制造现场的底层通信网络,它实现了微机化的现场测量控制仪器或设备之间的双向串行多节点数字通信,具有实时性、稳定性高的特点。自从2000年国际电工委员会(IEC)公布通过了IEC61158现场总线标准,现在已有十多种现场总线标准。以太网是商业领域里普遍采用的局域网络,结合传输控制协议/网际协议(transmission control protocol/internet protocol,TCP/IP)协议构成了以太网的基础,成为网络应用中事实上的标准,这也使得现场总线控制系统通过以太网与企业信息网集成实现工厂监控一体化成为大势所趋。
随着第五代(5th generation,5G)工业互联网技术的不断发展,目前工业现场网络中的设备通信正在从基于有线的通信向基于无线的通信方式转换。然而,基于有线的通信系统的一些发现设备的协议不再适用5G化后的工业互联网,例如,PROFINET IO系统中运行的链路层发现协议(link layer discovery protocol,LLDP)则无法发现5G核心网中的功能网元,例如用户面功能(user plane function,UPF)、(无线)接入网络(radio access network,(R)AN)等,并且,LLDP协议的报文不能被5G化后的工业互联网中的客户端设备(customer premise equipment,CPE)(也可称为终端设备(userequipment,UE)识别而被丢弃,因此,继续使用LLDP协议则无法获取5G化后的工业互联网的拓扑结构,会造成管理软件无法获知工业终端的信息,不能够精确的管理工业终端等问题。因此,如何能够获取5G工业互联网的拓扑结构成为亟待解决的问题。
发明内容
本申请提供了一种通信方法、系统和装置,使能网络侧或者网络管理服务器侧能够获取5G工业互联网的拓扑结构,掌握工业终端、网络终端、无线网络的拓扑连接关系,实现对工业终端的管理,满足工业终端个性化的需求。
第一方面,提供了一种通信方法,所述方法包括:第一网元接收第一信息,所述第一信息包括第一终端的第一标识;所述第一网元发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述第一网元接收第三信息,所述第三信息包括所述第二标识;所述第一网元向第 一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。
上述方式中,第一终端可以是集成了工业终端设备和网络终端设备的终端设备,第一服务器可以是设备管理服务器或者是管理和监控软件服务器。
采用上述方式,第一服务器通过掌握第一终端和第一网络的连接关系,以便于个性化地对第一终端提供服务,实现了第一服务器对第一终端的管理。
在一种可能的实施方式中,所述方法包括:所述第一网元发送第五信息,所述第五信息包括所述第一标识,所述第五信息用于请求第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述第一网元接收第六信息,所述第六信息包括所述第三标识;所述第一网元向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
上述方式中,第二终端为网络终端,第一终端通过所述第二终端接入第一网络。
采用上述方式,第一服务器通过掌握第一终端和第二终端的连接关系,能够个性化地对第一终端提供服务,实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
在一种可能的实施方式中,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
采用上述方式,第一服务器通过第一终端和第二终端的连接关系以及第一终端和第一网络的连接关系,能够掌握第一终端、第二终端和第一网络之间的拓扑关系,从而能够利用该拓扑关系进行后续的操作,例如计算网络负载等,并且实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
在一种可能的实施方式中,所述第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
示例性地,第一标识还可以包括第一终端的设备生产厂家和/或设备实例(instance)和/或第一终端接入的子网(subnet)和/或第一终端接入的网关(gateway)。
在一种可能的实施方式中,所述第二标识包括第一小区标识和/或第一接入点名称APN。
第二方面,提供了一种通信系统,其特征在于,包括第一终端、第一网元、第一服务器;所述第一终端用于发送第一信息,所述第一信息包括所述第一终端的第一标识,所述第一终端接入第一网络;所述第一网元用于接收所述第一信息;所述第一网元还用于向所述第一服务器发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求所述第一网络的第二标识;所述第一网元还用于接收所述第三信息,所述第三信息包括所述第二标识;所述第一网元还用于向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系;所述第一服务器用于接收所述第四信息,所述第一服务器还用于管理所述第一终端。
上述方式中,第一终端可以是集成了工业终端设备和网络终端设备的终端设备,第一 服务器可以是设备管理服务器或者是管理和监控软件服务器。
采用上述方式,第一服务器通过掌握第一终端和第一网络的连接关系,以便于个性化地对第一终端提供服务,实现了第一服务器对第一终端的管理。
在一种可能的实施方式中,所述通信系统还包括第二终端;所述第一网元用于发送第五信息,所述第五信息包括所述第一标识,所述第五信息用于请求所述第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述第一网元还用于接收第六信息,所述第六信息包括所述第三标识;所述第一网元还用于向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
上述方式中,第二终端为网络终端,第一终端通过所述第二终端接入第一网络。
采用上述方式,第一服务器通过掌握第一终端和第二终端的连接关系,能够个性化地对第一终端提供服务,实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
在一种可能的实施方式中,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
采用上述方式,第一服务器通过第一终端和第二终端的连接关系以及第一终端和第一网络的连接关系,能够掌握第一终端、第二终端和第一网络之间的拓扑关系,从而能够利用该拓扑关系进行后续的操作,例如计算网络负载等,并且实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
在一种可能的实施方式中,所述第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
示例性地,第一标识还可以包括第一终端的设备生产厂家、设备实例(instance)、第一终端接入的子网(subnet)、第一终端接入的网关(gateway)。
在一种可能的实施方式中,所述第二标识包括第一小区标识和/或第一接入点名称APN。
第三方面,提供了一种通信装置,所述装置包括:收发模块,用于接收第一信息,所述第一信息包括第一终端的第一标识;所述收发模块还用于发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述收发模块还用于接收第三信息,所述第三信息包括所述第二标识;所述收发模块还用于向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。
上述方式中,第一终端可以是集成了工业终端设备和网络终端设备的终端设备,第一服务器可以是设备管理服务器或者是管理和监控软件服务器。
采用上述方式,第一服务器通过掌握第一终端和第一网络的连接关系,以便于个性化地对第一终端提供服务,实现了第一服务器对第一终端的管理。
在一种可能的实施方式中,所述装置包括:所述收发模块还用于发送第五信息,所述 第五信息包括所述第一标识,所述第五信息用于请求第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述收发模块还用于接收第六信息,所述第六信息包括所述第三标识;所述收发模块还用于向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
上述方式中,第二终端为网络终端,第一终端通过所述第二终端接入第一网络。
采用上述方式,第一服务器通过掌握第一终端和第二终端的连接关系,能够个性化地对第一终端提供服务,实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
在一种可能的实施方式中,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
采用上述方式,第一服务器通过第一终端和第二终端的连接关系以及第一终端和第一网络的连接关系,能够掌握第一终端、第二终端和第一网络之间的拓扑关系,从而能够利用该拓扑关系进行后续的操作,例如计算网络负载等,并且实现了第一服务器精确地对第一终端进行管理。
在一种可能的实施方式中,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
在一种可能的实施方式中,其特征在于,所述第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
示例性地,第一标识还可以包括第一终端的设备生产厂家和/或设备实例(instance)和/或第一终端接入的子网(subnet)和/或第一终端接入的网关(gateway)。
在一种可能的实施方式中,所述第二标识包括第一小区标识和/或第一接入点名称APN。
第四方面,提供了一种通信装置,该通信装置可以为上述方法实施例中的通信装置,或者为设置在通信装置中的芯片。该通信装置包括通信接口以及处理器,可选的,还包括存储器。其中,该存储器用于存储计算机程序或指令,处理器与存储器、通信接口耦合,当处理器执行所述计算机程序或指令时,使通信装置执行上述方法实施例中由通信装置所执行的方法。
示例性地,存储器和处理器可以集成在一起,也可以为独立的器件。
第五方面,提供了一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码被运行时,使得上述各方面中由上述通信装置执行的方法被执行。
第六方面,本申请提供了一种芯片系统,该芯片系统包括处理器,用于实现上述各方面的方法中通信装置的功能。在一种可能的设计中,所述芯片系统还包括存储器,用于保存程序指令和/或数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
第七方面,本申请提供了一种计算机可读存储介质,该计算机可读存储介质存储有计算机程序,当该计算机程序被运行时,实现上述各方面中由上述通信装置执行的方法。
图1是适用于本申请实施例的一例应用场景图。
图2是适用于本申请实施例的又一例应用场景图。
图3是本申请实施例的一例示意性流程图。
图4是本申请实施例的再一例示意性流程图。
图5是本申请实施例的又一例示意性流程图。
图6是本申请实施例的又一例示意性流程图。
图7是本申请实施例的又一例示意性流程图。
图8是本申请的实施例提供的可能的通信装置的结构示意图。
图9是本申请的实施例提供的可能的通信装置的结构示意图。
下面将结合附图,对本申请中的技术方案进行描述。显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统,例如:窄带物联网系统(narrow band-internet of things,NB-IoT)、全球移动通讯(global system of mobile communication,GSM)系统、码分多址(code division multiple access,CDMA)系统、宽带码分多址(wideband code division multiple access,WCDMA)系统、通用分组无线业务(general packet radio service,GPRS)、长期演进(long term evolution,LTE)系统、LTE频分双工(frequency division duplex,FDD)系统、LTE时分双工(time division duplex,TDD)、通用移动通信系统(universal mobile telecommunication system,UMTS)、全球互联微波接入(worldwide interoperability for microwave access,WiMAX)通信系统、第五代(5th generation,5G)系统或新无线(new radio,NR)、卫星通信系统、未来的第六代(6th generation,6G)系统等。
本申请实施例中的终端设备,也可以称为用户设备(user equipment,UE)、接入终端、终端设备单元(subscriber unit)、终端设备站、移动站、移动台(mobile station,MS)、远方站、远程终端、移动设备、用户终端、终端(terminal)、无线通信设备、终端设备代理或终端设备装置。终端设备可以包括各种具有无线通信功能的手持设备、车载设备、物联网(internet of things,IoT)设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。还可以包括用户单元、蜂窝电话(cellular phone)、智能手机(smart phone)、无线数据卡、个人数字助理(personal digital assistant,PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handset)、膝上型电脑(laptop computer)、机器类型通信(machine type communication,MTC)终端、无线局域网(wireless local area networks,WLAN)中的站点(station,ST)。可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站以及下一代通信系统,例如,5G网络中的终端设备或者未来演进的PLMN网络中的终端设备等。
本申请实施例中的终端设备还可以是工业终端设备,该工业终端设备可以包括控制器设备(例如,可编程逻辑控制器(programmable logic controller,PLC))、工业输入输出(input/output,IO)设备等其它用作工业场景中负责工业操作的设备,该工业终端设备可以通过5G终端设备接入到5G网络,从而被服务器管理和监控;本申请实施例中的终端 设备还可以是具备5G通信能力的工业终端,例如,工业终端设备内置了5G通信模块。
本申请实施例中的网络设备可以是用于与终端设备通信的设备,网络设备可以是全球移动通讯(global system of mobile communication,GSM)系统或码分多址(code division multiple access,CDMA)中的基站(base transceiver station,BTS),也可以是宽带码分多址(wideband code division multiple access,WCDMA)系统中的基站(nodeB,NB),还可以是LTE系统中的演进型基站(evolutional nodeB,eNB或eNodeB),还可以是云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器,还可以是卫星通信系统中的卫星基站,或者网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等,本申请实施例并不限定。
需要说明的是,本申请实施例的技术方案可以适用于集中单元(central unit,CU)和分布式单元(distributed unit,DU)架构,也可以适用于控制面(control plane,CP)和(user plane,UP)分离的架构,本申请对此不做限定。
为了便于理解,以下将对本申请实施例所涉及的基本概念作简单介绍。
协议数据单元(protocol data unit,PDU)会话:UE与数据网络间实现PDU连通性的会话服务,由PDU会话标识(Session ID)来作为标识。
5G局域网(local area network,LAN)是利用5G新空口创建的LAN,利用5G LAN能够实现工业互联网中可靠高效的传输并且保持LAN中业务与公众网络的隔离。
CPE:为第三代合作伙伴项目(3rd Generation Partnership Project,3GPP)中定义的UE设备,当前工业输入输出设备(工业终端设备)通过CPE接入5G-LAN网络中。
可编程逻辑控制器(programmable logic controller,PLC),是一种专门为在工业环境下应用而设计的数字运算操作的电子装置。
人机界面(human machine interface,HMI):又称为触摸屏监控器,是一种智能化操作控制、显示装置。
下面对本申请实施例可以应用的系统架构或者场景进行说明,如图1所示,其中,图1是适用于本申请实施例的一例应用场景图。下面对图1所示的网络架构100中可能涉及的各个网元分别进行说明。
1、UE110:参见上述说明,在此不再赘述。
2、(无线)接入网络(radio access network,(R)AN)网元120:参见上述说明,在此不再赘述。
需要说明的是,上述“网元”也可以称为实体、设备、装置或模块等,本申请并未特别限定。并且,在本申请中,为了便于理解和说明,在对部分描述中省略“网元”这一描述,例如,将(R)AN网元简称(R)AN,此情况下,该“(R)AN网元”应理解为(R)AN网元或(R)AN实体,以下,省略对相同或相似情况的说明。
3、用户面网元130:用于分组路由和转发以及用户面数据的服务质量(quality of service,QoS)处理等。
在5G通信系统中,该用户面网元可以是用户面功能(user plane function,UPF)网元。在未来通信系统中,用户面网元仍可以是UPF网元,或者,还可以有其它的名称,本申请不做限定。
4、数据网络140:用于提供传输数据的网络。
在5G通信系统中,该数据网络可以是数据网络(data network,DN)。在未来通信系统中,数据网络仍可以是DN,或者,还可以有其它的名称,本申请不做限定。
5、接入管理网元150:主要用于移动性管理和接入管理等,可以用于实现移动性管理实体(mobility management entity,MME)功能中除会话管理之外的其它功能,例如,合法监听以及接入授权/鉴权等功能。
在5G通信系统中,该接入管理网元可以是接入管理功能(access and mobility management function,AMF)网元。在未来通信系统中,接入管理网元仍可以是AMF网元,或者,还可以有其它的名称,本申请不做限定。
6、会话管理网元160:主要用于会话管理、终端设备的网络互连协议(internet protocol,IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中,该会话管理网元可以是会话管理功能(session management function,SMF)网元。在未来通信系统中,会话管理网元仍可以是SMF网元,或者,还可以有其它的名称,本申请不做限定。
7、策略控制网元170:用于指导网络行为的统一策略框架,为控制面功能网元(例如AMF,SMF网元等)提供策略规则信息等。
在4G通信系统中,该策略控制网元可以是策略和计费规则功能(policy and charging rules function,PCRF)网元。在5G通信系统中,该策略控制网元可以是策略控制功能(policy control function,PCF)网元。在未来通信系统中,策略控制网元仍可以是PCF网元,或者,还可以有其它的名称,本申请不做限定。
8、统一数据仓储功能(unified data repository,UDR)网元180:用于向UDM网元提供签约数据或者从UDM网元中获取签约数据;以及,向PCF网元提供策略数据,或者从PCF网元中获取策略数据等。
9、数据管理网元190:用于处理终端设备标识,接入鉴权,注册以及移动性管理等。
在5G通信系统中,该数据管理网元可以是统一数据管理(unified data management,UDM)网元。在未来通信系统中,统一数据管理仍可以是UDM网元,或者,还可以有其它的名称,本申请不做限定。
10、网络开放功能网元1100:主要用于安全的开放3GPP网络功能提供的业务和能力,有内部开放,或者开放给第三方等。
在5G通信系统中,该网络开放功能网元可以是网络开放功能网元(network exposure function,NEF)。在未来通信系统中,网络开放功能网元仍可以是NEF网元,或者,还可以有其它的名称,本申请不做限定。
或者,应用功能网元(application function,AF)1100:用于实现外部服务器与3GPP网络的信息交互。
可以理解的是,上述网元或者功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。
其中各接口功能描述如下:
1、N7:PCF与SMF之间的接口,用于下发PDU会话粒度以及业务数据流粒度控制 策略。
2、N15:PCF与AMF之间的接口,用于下发UE策略及接入控制相关策略。
3、N5:AF与PCF之间的接口,用于应用业务请求下发以及网络事件上报。
4、N4:SMF与UPF之间的接口,用于控制面与用户面之间传递信息,包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5、N11:SMF与AMF之间的接口,用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。
6、N2:AMF与RAN之间的接口,用于传递核心网侧至RAN的无线承载控制信息等。
7、N1:AMF与UE之间的接口,接入无关,用于向UE传递QoS控制规则等。
8、N8:AMF与UDM间的接口,用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据,以及AMF向UDM注册UE当前移动性管理相关信息等。
9、N10:SMF与UDM间的接口,用于SMF向UDM获取会话管理相关签约数据,以及SMF向UDM注册UE当前会话相关信息等。
10、N35:UDM与UDR间的接口,用于UDM从UDR中获取用户签约数据信息。
11、N36:PCF与UDR间的接口,用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
12、N52:UDM和NEF间的接口,用于NEF向第三方应用功能开放网络能力,如第三方应用功能通过NEF向UDM订阅特定群组中所有用户的可达性事件。
此外,NEF还与AMF、SMF均有直接接口,分别对应N29接口和N51接口(为简化图示,上图中并未展示),用于开放运营商网络能力至第三方应用功能实体,前者可用于NEF直接向AMF订阅相应网络事件、更新用户配置信息,后者可用于更新SMF/UPF上的应用配置数据,如Application ID所对应的PFD(Packet Flow Description)分组流描述信息。
通用的用户注册流程可简单描述为:UE通过AN发送注册请求至AMF,AMF根据用户标识向特定UDM获取签约数据,UDM收到该请求后可向UDR获取实际签约数据。此外,AMF还可向PCF发起用户策略控制建立请求(UEPolicyControl_Create)及接入管理策略控制建立请求(AMPolicyControl_Create),分别用于获取UE策略及接入控制策略。PCF在该过程中返回接入控制策略至AMF,并经由AMF向UE提供UE策略。
通用的会话建立流程可简单描述为:UE通过RAN发送会话建立请求到AMF,AMF为该会话选择SMF为其提供服务,保存SMF与PDU会话的对应关系,并将会话建立请求发送至SMF,SMF为UE选择相应UPF并建立用户面传输路径,并为其分配IP地址。在此过程中,SMF还将向PCF发起策略控制会话建立请求,用于在SMF和PCF间建立策略控制会话,在策略控制会话建立过程中,SMF将保存策略控制会话与PDU会话间的对应关系。此外,AF还可与PCF间建立AF会话,由PCF对AF会话与策略控制会话进行绑定。
应理解,上述应用于本申请实施例的网络架构仅是举例说明的从5G组网架构的角度描述的网络架构,适用本申请实施例的网络架构并不局限于此,任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如,在某些网络架构中,AMF、SMF、PCF以及UDM等网络功能实体都称为网络功能(Network Function,NF)网元;或者,在另一些网络架构中,AMF、SMF、PCF及UDM等网元的集合都可以称为控制面功能(Control Plane Function,CPF)网元。
本申请实施例结合核心网设备描述了各个实施例,其中,核心网的功能主要是提供用户连接、对用户的管理以及对业务完成承载,作为承载网络提供到外部网络的接口。用户连接的建立包括移动性管理(mobile management,MM)、呼叫管理(connection management,CM)、交换/路由、录音通知等功能。用户管理包括用户的描述、服务质量(Quality of Service,QoS)、用户通信记录(accounting)、虚拟归属环境(virtual home environment,VHE)和安全性(由鉴权中心提供相应的安全性措施包含了对移动业务的安全性管理和对外部网络访问的安全性处理)。承载连接(access)包括到外部的公共交换电话网络(public switched telephone network,PSTN)、外部电路数据网和分组数据网、互联网络(internet)和内联网(intranets)、以及移动网络自身的手机短信服务(short message service,SMS)服务器等等。
核心网可以提供的基本业务包括移动办公、电子商务、通信、娱乐性业务、旅行和基于位置的服务、遥感业务(telemetry)、简单消息传递业务(监视控制)等等。
图2是适用于本申请实施例的又一例应用场景图,如图2所示,工业输入输出(Input/Output,IO)设备通过CPE接入到5G-LAN中,并通过RAN、UPF、交换机(switch)和监控诊断软件/HMI、PLC相连接。
在上述场景中,当5G应用到工业互联网中时,目前工业总线协议的设备发现机制无法应用到5G工业互联网的拓扑结构获取。为解决上述问题,本申请提供了方法200,如图3所示,图3是本申请实施例的一例示意性流程图。
S210,第一终端发送第一信息,第一网元接收第一信息。
其中,第一信息包括第一终端的第一标识。
示例性地,第一终端可以是集成了工业终端设备和网络终端设备的终端设备。
在一种可能的实施方式中,第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
示例性地,第一标识还可以包括第一终端的设备生产厂家和/或设备实例(instance)和/或第一终端接入的子网(subnet)和/或第一终端接入的网关(gateway)。
在一种可能的实施方式中,第一网元向第三网元发送第五信息,并接收来自第三网元的第六信息。
其中,第五信息包括第一标识,第五信息用于请求第二终端的第三标识,第二终端是连接第一终端和第一网络的设备,第一终端为工业终端设备。第六信息包括第三标识。
上述方式中,第二终端为网络终端,第一终端通过第二终端接入第一网络。
在一种可能的实施方式中,第五信息包括第一事件标识,第一事件标识用于指示请求第二终端的第三标识。
在一种可能的实施方式中,第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
S220,第一网元发送第二信息,第二网元接收第二信息。
其中,第二信息包括第一标识,第二信息用于请求第一网络的第二标识,第一网络是 第一终端接入的网络。
在一种可能的实施方式中,第二标识包括第一小区标识和/或第一接入点名称APN。
S230,第二网元发送第三信息,第一网元接收第三信息。
其中,第三信息包括第二标识。
S240,第一网元向第一服务器发送第四信息,第一服务器接收第四信息。
其中,第四信息用于指示第一标识与第二标识的关联关系,第一服务器用于管理第一终端。
示例性地,第一服务器可以是设备管理服务器或者是管理和监控软件服务器。
在一种可能的实施方式中,第一网元向第一服务器发送第七信息,第七信息用于指示第一标识与第三标识的关联关系。
在一种可能的实施方式中,第七信息还用于指示第一标识、第二标识与第三标识的关联关系。
采用上述方式,第一服务器通过第一终端和第二终端的连接关系以及第一终端和第一网络的连接关系,能够掌握第一终端、第二终端和第一网络之间的拓扑关系,从而能够利用该拓扑关系进行后续的操作,例如计算网络负载等,并且实现了第一服务器精确地对第一终端进行管理。
下面结合附图对本申请实施例提供的通信方法进行详细说明。
本申请提供了方法300,如图4所示,图4是本申请实施例的再一例示意性流程图。
如方法300所示,S310中,CPE#1与UPF#1建立了以太网(ethernet,ETH)PDU会话和IP PDU会话,并且CPE#1上的代理(agent)软件完成了在设备管理服务器#1上的注册。
S320,IFES#1发送信息#A,工业终端#1接收信息#A。
需要说明的是,本申请提出了工业现场使能服务(industrial field enable service,IFES)应用/服务,该应用负责提取工业终端的信息、工业终端和CPE的连接关系、CPE和与CPE接入的网络的关联关系,例如,CPE的识别码信息和CPE接入的网络的信息的关联关系,CPE的识别码信息可以是:国际移动用户识别码(international mobile subscriber identification number,IMSI)、国际移动设备识别码(international mobile equipment identity,IMEI);CPE接入的网络的信息可以是接入点名称(Access Point Name,APN)、小区标识等信息的关联信息。IFES可以作为一种应用/服务访问CPE接入的网络(例如5G核心网),因此,IFES可以认为是AF的一种,本申请对此不作限定。
在一种可能的实施方式中,IFES#1通过UPF#1、RAN#1和CPE#1发送信息#A,工业终端#1通过CPE#1接收信息#A。
在一种可能的实施方式中,IFES通过发现与基本配置协议(discovery and basic configuration protocol,DCP)发送信息#A。
在一种可能的实施方式中,IFES#1以组播的方式发送信息#A,1个或多个工业终端接收信息#A后向IFES#1发送响应信息,下面以其中的一个工业终端,即工业终端#1为例进行说明。
其中,信息#A用于向工业终端#1请求工业终端#1的设备信息。
示例性地,设备信息包括以下信息的至少一种:
设备生产厂家:即生产该设备的厂家名称或标识;
设备名称:即该设备的名称;
设备标识(identity,ID):即该设备的标识;
设备角色:即该设备的是控制者(controller)(负责管理其他设备,即负责向其他设备发出控制命令)还是设备(device)(不负责管理其他设备,即接受控制者发出的控制命令);
设备实例(instance):即实际的使用以及装载进存储器的该设备实体的拷贝的虚拟生成;
介质访问控制层(media access control,MAC)地址:即用来确认该设备位置的地址;
IP地址:即该设备的符合IP协议的逻辑地址;
子网(subnet):即该设备接入的子网;
网关(gateway):即与该设备连接的网关。
S330,工业终端#1确定信息#B。
具体地,工业终端#1接收到信息#A后,确定信息#B,信息#B用于工业终端#1针对信息#A作出响应。
其中,信息#B包括工业终端#1的设备信息,设备信息参见上述说明,在此不再赘述。
在一种可能的实施方式中,如果工业终端#1运行正常,则工业终端#1向IFES#1发送身份确认(identity OK)消息,该消息用于指示查询成功。
S340,工业终端#1发送信息#B,IFES#1接收信息#B。
在一种可能的实施方式中,工业终端#1通过CPE#1、RAN#1、UPF#1发送信息#B,IFES#1通过UPF#1接收信息#B。在此情况下,UPF#1获取了工业终端#1的MAC地址#1。
在一种可能的实施方式中,工业终端#1通过DCP协议发送该信息#B。
在一种可能的实施方式中,工业终端#1周期性地发送信息#B,此时IFES无需发送信息#A,工业终端#1也无需接收信息#A。
S350,IFES#1确定关联关系#1。
具体地,IFES#1根据信息#B生成关联关系#1,其中,关联关系#1用于关联工业终端的各项设备信息,例如表一。
表一
MAC地址 | 设备名称 | IP地址 | 设备ID | 设备角色 | … |
MAC地址#1 | 设备名称#1 | IP地址#1 | 设备ID#1 | 设备角色#1 | … |
… | … | … | … | … | … |
应理解,表一中的设备信息除了MAC地址、设备名称、IP地址、设备ID、设备角色等信息外,还可以包括其他的设备信息,例如设备生产厂家、子网等。
假设表一中的MAC地址#1,设备名称#1,IP地址#1,设备ID#1,设备角色#1这几项设备信息为工业终端#1的设备信息,那么这些设备信息被关联起来与同一个工业终端对应。
IFES#1通过信息#B能够掌握工业终端#1的设备信息。
S360,IFES#1确定CPE#1的标识。
具体地,可分为以下步骤(可参见图5,图5是本申请实施例的又一例示意性流程图, 用于表示IFES获取CPE标识的具体过程):
步骤a:CPE#1发起以太网类型的PDU会话建立请求。
下面以该CPE#1与工业终端#1连接为例进行说明。
步骤b:SMF#1与PCF#1进行会话管理策略的更新。
在一种可能的实施方式中,SMF#1与PCF#1进行会话管理策略的更新的同时SMF#1向PCF#1发送MAC地址#1,此时,PCF#1具有MAC地址#1和CPE#1的对应关系。
具体地,SMF#1通过会话管理策略关联更新请求(session management policy association update request)消息发送MAC地址#1。
UPF#1发送工业终端#1的MAC地址#1,SMF#1接收MAC地址#1,SMF#1发送MAC地址#1,PCF#1接收MAC地址#1。
在一种可能的实施方式中,在UPF#1发送工业终端#1的MAC地址#1之前,UPF#1判断MAC地址#1是否是新的MAC地址,如果是新的MAC地址则发送MAC地址#1,如果不是新的MAC地址,则意味着已经发送过MAC地址#1,本次则不再发送MAC地址#1。
步骤c:PCF#1基于所收到的MAC地址#1(即工业终端#1的MAC地址)信息,向BSF#1发起绑定信息注册/更新流程,其中携带信息#C,信息#C包括以下信息的至少一种:
用户永久标识符(subscriber permanent identifier,SUPI),例如,CPE#1的用户永久标识符信息;
一般公共订阅标识符(generic public subscription identifier,GPSI),例如,CPE#1的一般公共订阅标识符信息;
MAC地址,例如,工业终端#1的MAC地址信息;
数据网络名称(data network name,DNN),例如,CPE#1接入的5G核心网的名称的信息;
单网络切片选择辅助信息(single network slice selection assistance information,S-NSSAI),例如,CPE#1接入的单网络切片选择辅助信息;
PCF标识/地址,例如,PCF#1的标识/地址信息。
步骤d:IFES#1获取CPE#1的标识信息,可以有以下两种方式:
方式一
IFES#1向PCF#1发送信息#D,其中,信息#D用于请求查询用户标识信息。PCF#1可以根据信息#D确定MAC地址#1对应的CPE#1的标识(例如,SUPI、GSPI)并发送给IFES#1,
示例性地,信息#D包括工业终端的MAC地址信息,例如,工业终端#1的MAC地址#1。
IFES#1通过发送工业终端#1的MAC地址#1来向NEF请求其所连接的CPE#1的标识信息。
示例性地,信息#D还可以包括DNN。
在一种可能的实施方式中,信息#D还可以包括事件标识(event ID),用于指示信息#D发起的事件类型为查询用户标识。
方式二
IFES#1确定并发送信息#D,NEF#1接收信息#D。
步骤d1:NEF#1根据MAC地址#1向BSF#1执行PCF查询,并获取PCF#1的标识/地址。
步骤d2:NEF#1确定并发送信息#E,PCF#1接收信息#E。
具体地,NEF#1根据PCF#1标识/地址向PCF#1发送信息#E,信息#E用于请求查询工业终端#1所连接的CPE#1的标识信息。
示例性地,信息#E包括工业终端#1的MAC地址#1,还可以包括DNN,和/或事件标识。
步骤d3:PCF#1确定并发送信息#F,NEF#1接收信息#F。
具体地,PCF#1根据信息#E确定工业终端#1连接的CPE#1的标识,信息#F包括该CPE#1的标识。
示例性地,信息#F包括以下信息的至少一种:
SUPI,例如CPE#1的SUPI#1;
GPSI,例如CPE#1的GPSI#1;
IMSI,例如CPE#1的IMSI#1。
步骤d4:NEF#1确定并发送信息#G,IFES#1接收信息#G。
NEF#1根据信息#F确定CPE#1的标识,信息#G包括CPE#1的标识,信息#G的内容参见信息#F的内容,在此不再赘述。
在一种可能的实施方式中,PCF#1确定并发送信息#G,PCF#1接收信息#G。
S370,IFES#1确定关联关系#2,关联关系#2用于关联工业终端和CPE。
具体地,IFES根据信息#G确定关联关系#2,例如表二。
表二
MAC地址 | IMSI | … |
MAC地址#1 | IMSI#1 | … |
… | … | … |
需要说明的是,表二除了使用MAC地址和IMSI来关联工业终端和CPE外,还可以使用MAC地址和SUPI来关联工业终端和CPE,或者使用MAC地址、SUPI和IMSI来关联工业终端和CPE,即将工业终端的设备信息和CPE的标识信息关联即可,本申请对此不做限定。
如表二所示,以关联工业终端#1和CPE#1为例,工业终端#1的MAC地址#1和CPE#1的IMSI#1被关联在一起,即表示工业终端#1和CPE#1为相互连接的关系。
S380,IFES#1发送信息#H,设备管理服务器#1接收信息#H。
其中,信息#H用于请求查询CPE#1的设备信息和接入的网络信息。
示例性地,信息#H包括CPE#1的IMSI#1,还可以包括事件标识(event ID),用于指示发起的事件为查询IMSI对应的CPE的设备信息和接入的网络信息。
S390,设备管理服务器#1发送信息#I,IFES#1接收信息#I。
具体地,设备管理服务器#1根据信息#H,确定信息#I,信息#I包括CPE#1对应的IMEI#1和/或CPE#1对应的APN#1和/或CPE#1对应的小区标识#1等信息。
S3100,IFES#1确定关联关系#3。
具体地,IFES#1根据信息#I确定关联关系#3,关联关系#3用于关联CPE的设备信息和CPE接入的网络信息。例如表三。
表三
IMSI | 小区标识 | IMEI | APN | … |
IMSI#1 | 小区标识#1 | IMEI#1 | APN#1 | … |
… | … | … | … | … |
需要说明的是,用于关联CPE的设备信息和CPE接入的网络信息可以是IMSI和小区标识,或者是IMSI、IMEI和小区标识,或者是IMSI和APN,或者是IMSI、小区标识和APN等,即表三的内容仅作为关联CPE的设备信息和CPE接入的网络信息的实例,不构成对本申请的限定。
如表三所示,以关联CPE#1的设备信息和CPE#1接入的网络信息为例进行说明,IMSI#1、IMEI#1作为CPE#1的设备信息,小区标识#1、APN#1作为CPE#1接入的网络信息,两者被关联在一起。
S3110,IFES#1发送信息#J,管理和监控软件服务器#1接收信息#J。
其中,信息#J包括关联关系#4,关联关系#4用于关联工业终端、CPE、以及CPE对应的网络信息。
具体地,IFES#1根据关联关系#1、关联关系#2和关联关系#3确定关联关系#4。例如表四所示。
表四
需要说明的是,用于关联工业终端、CPE和CPE接入的网络信息可以是MAC地址、IP地址、IMSI、APN,或者是MAC地址、设备名称、IP地址、IMSI、APN、小区标识,或者是MAC地址、设备ID、IP地址、IMSI、APN、小区标识、IMEI等多种组合,并不限于表四中的组合,本申请在此不再赘述。
如表四所示,以关联工业终端#1、CPE#1和CPE#1接入的网络信息为例进行说明,MAC地址#1、设备名称#1、IP地址#1、设备ID#1和设备角色#1作为对应工业终端#1的设备信息,IMSI#1和IMEI#1作为对应CPE#1的设备信息,APN#1、小区标识#1作为对应CPE#1接入的网络信息,三者被关联在一起,IFES#1通过关联关系#4掌握全网拓扑关系。
在一种可能的实施方式中,IFES#1通过简单网络管理协议(simple network management protocol,SNMP)发送信息#J。
需要说明的是,方法300以工业终端#1为例,进行了IFES#1获取全网拓扑结构的说明,对于IFES#1获取包括多个工业终端的全网拓扑结构,方法300同样适用。
通过方法300,IFES能够获取工业终端与CPE之间的关联关系、CPE与CPE接入的网络之间的关联关系,从而掌握全网的拓扑结构,使能核心网根据不同的工业终端的需求来提供定制化的带宽或业务,另外,工业终端与CPE的关系通过上述方式获取使能更换工业终端与CPE的绑定关系更加容易。另一方面,通过CPE与CPE接入的网络之间的关联关系,能够保证后续的网络负载计算等操作能够精确进行。
在IFES通过方法300获取全网拓扑结构后,还面临着拓扑结构更新的问题,对此,本申请提供了方法400来更新全网拓扑结构,如图6所示,图6是本申请实施例的又一例示意性流程图。
S410,IFES#1启动拓扑更新。
具体地,IFES#1周期性地对全网的拓扑进行更新。
在一种可能的实施方式中,IFES#1内部具有“拓扑更新定时器”,当定时器超时后,触发IFES#1更新全网拓扑。
S420,IFES#1按照方法S310~S3110重新获取全网的拓扑信息后,删除原来的拓扑信息,保留最新的拓扑信息。
本申请还提供了方法500来更新全网拓扑结构,参见图7,图7为本申请实施例的又一例示意性流程图。
S510,IFES#1启动拓扑更新。
具体内容可参见方法S410,在此不再赘述。
S520,IFES#1发送信息#A,工业终端#2接收信息#A。
具体内容参见方法S320,在此不再赘述。
S530,工业终端#2确定信息#B1。
具体内容参见方法S330,在此不再赘述。其中,信息#B1的内容参见信息#B,在此不再赘述。
S540,工业终端#2发送信息#B1,IFES#1接收信息#B1。
S550,IFES#1进行关联关系#1的维护或更新。
具体地,IFES#1根据信息#B1以及表一(或者关联关系#1)来判断工业终端#2是否为新设备。
如果,信息#B1中的设备信息在表一中没有工业终端的设备信息与之完全相同,则判断工业终端#2为新设备,并将信息#B1中的内容添加到表一中,则更新后的表一如下所示:
表一
MAC地址 | 设备名称 | IP地址 | 设备ID | 设备角色 | … |
MAC地址#1 | 设备名称#1 | IP地址#1 | 设备ID#1 | 设备角色#1 | … |
MAC地址#2 | 设备名称#2 | IP地址#2 | 设备ID#2 | 设备角色#2 | … |
… | … | … | … | … | … |
其中,MAC地址#2,设备名称#2,IP地址#2,设备ID#2,设备角色#2这几项设备信息为工业终端#2的设备信息。
如果,信息#B1中的设备信息在表一中有工业终端的设备信息与之完全相同,则判断工业终端#2为老设备,则不将信息#B1的设备信息存入表一中。
在一种可能的实施方式中,如果IFES#1没有收到MAC地址#1对应的工业终端#1响 应的设备信息,则删除表一中有关工业终端#1的设备信息;或者,
虽然收到了与MAC地址#1相同的MAC地址#2,但是其他的设备信息例如IP地址#1和IP地址#2不同,则删除表一中的工业终端#1对应的“MAC地址#1,设备名称#1,IP地址#1,设备ID#1,设备角色#1等”记录,保存工业终端#2对应的“MAC地址#2,设备名称#2,IP地址#2,设备ID#2,设备角色#2等”记录,此种场景可以是,工业终端#1更换了连接的CPE,而IFES#1将更换CPE后的工业终端#1(即工业终端#2)认为是新设备。
下面以工业终端#2是新设备为例进行后面方法的说明。
S560,IFES#1接收工业终端#2对应的CPE#2的标识信息。
具体内容可参见方法S360,在此不再赘述。
S570,IFES#1进行关联关系#2的维护或更新。
示例性地,IFES#1将MAC地址#2和CPE#2对应的IMSI#2存入表二中,更新后的表二如下所示:
表二
MAC地址 | IMSI | … |
MAC地址#1 | IMSI#1 | … |
MAC地址#2 | IMSI#2 | … |
… | … | … |
具体内容参见方法S370,在此不再赘述。
S580,IFES#1发送信息#H1,设备管理服务器#1接收信息#H1。
其中,信息#H1于请求查询CPE#2的设备信息和接入的网络信息。具体内容参见方法S380,在此不再赘述。
S590,设备管理服务器#1发送信息#I1,IFES#1接收信息#I1。
具体地,设备管理服务器#1根据信息#H1,确定信息#I1,信息#I1包括CPE#2对应的IMEI#2和/或CPE#2对应的APN#2和/或CPE#2对应的小区标识#2等信息。
S5100,IFES#1维护或更新关联关系#3。
示例性地,IFES#1根据信息#I1更新关联关系#3,例如以下更新后的表三:
表三
IMSI | 小区标识 | IMEI | APN | … |
IMSI#1 | 小区标识#1 | IMEI#1 | APN#1 | … |
IMSI#2 | 小区标识#2 | IMEI#2 | APN#2 | … |
… | … | … | … | … |
具体内容参见方法S3100,在此不再赘述。
S5110,IFES#1发送信息#J1,管理和监控软件服务器接收信息#J1。
具体地,IFES#1根据更新后的表一、更新后的表二、更新后的表三确定更新后的表四,更新后的表四如下所示:
表四
示例性地,信息#J1包括表四中新增加的工业终端#2、CPE#2和CPE#2接入的网络信息的关联关系,例如,信息#J1包括MAC地址#2、设备名称#2、IP地址#2、设备ID#2、设备角色#2、IMSI#2、IMEI#2、APN#2、小区标识#2等信息,以便于管理和监控软件服务器#1掌握最新的全网拓扑结构。
其他具体内容参见方法S3110,在此不再赘述。
通过方法400和方法500,使能IFES定期更新全网拓扑关系,并定期上报给管理和监控软件更新后的全网拓扑关系。
图8和图9是本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以实现上述方法实施例中终端设备或网络设备的功能,因此也能实现上述方法实施例所具备的有益效果。在本申请实施例中,该通信装置可以是方法200中的第一通信装置(对应第一网元),还可以是应用于第一通信装置的模块(如芯片)。
如图8所示,通信装置600包括收发模块601和处理模块602。通信装置600可用于实现上述图3所示的方法实施例中第一通信装置的功能。
当通信装置600用于实现图3所述方法实施例中第一通信装置的功能时:收发模块601,用于接收第一信息,所述第一信息包括第一终端的第一标识;所述收发模块601还用于发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述收发模块601还用于接收第三信息,所述第三信息包括所述第二标识;所述收发模块601还用于向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。处理模块602,用于确定上述第二信息和上述第四信息。
关于上述收发模块601和处理模块602更详细的描述,可参考上述方法实施例中的相关描述,在此不再说明。
如图9所示,通信装置700包括处理器710和接口电路720。处理器710和接口电路720之间相互耦合。可以理解的是,接口电路720可以为收发器或输入输出接口。可选的,通信装置700还可以包括存储器730,用于存储处理器710执行的指令或存储处理器710运行指令所需要的输入数据或存储处理器710运行指令后产生的数据。
示例性地,存储器730和处理器710可以集成在一起,也可以为独立的器件。
当通信装置700用于实现上述方法实施例中的方法时,处理器710用于执行上述处理模块602的功能,接口电路720用于执行上述收发模块601的功能。
当上述通信装置为应用于第一通信装置的芯片时,该第一通信装置芯片实现上述方法实施例中第一通信装置的功能。该第一通信装置芯片从第一通信装置中的其它模块(如射频模块或天线)接收信息;或者,该第一通信装置芯片向第一通信装置中的其它模块(如 射频模块或天线)发送信息。
可以理解的是,本申请的实施例中的处理器可以是中央处理单元(central processing unit,CPU),还可以是其它通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其它可编程逻辑器件、晶体管逻辑器件,硬件部件或者其任意组合。通用处理器可以是微处理器,也可以是任何常规的处理器。
需要说明的是,本说明书中的各个实施例均采用递进的方式描述,各个实施例之间相同相似的部分互相参见即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于系统或系统实施例而言,由于其基本相似于方法实施例,所以描述得比较简单,相关之处参见方法实施例的部分说明即可。以上所描述的系统及系统实施例仅仅是示意性的,其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下,即可以理解并实施。
还需要说明的是,在本文中,诸如第一、第二、“#1”、“#2”之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本申请的实施例中的方法步骤可以通过硬件的方式来实现,也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于随机存取存储器(random access memory,RAM)、闪存、只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性地存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于接入网设备或终端设备中。当然,处理器和存储介质也可以作为分立组件存在于接入网设备或终端设备中。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时,全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中,或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存 储设备。所述可用介质可以是磁性介质,例如,软盘、硬盘、磁带;也可以是光介质,例如,DVD;还可以是半导体介质,例如,固态硬盘(solid state disk,SSD)。
本申请中,“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单数或者复数。在本申请的文字描述中,字符“/”,一般表示前后关联对象是一种“或”的关系;在本申请的公式中,字符“/”,表示前后关联对象是一种“相除”的关系。
可以理解的是,在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分,并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定。需要说明的是,本申请实施例中的步骤不一定全部都必须执行,有些是可省略的,并且也能达到类似的效果。
Claims (24)
- 一种通信方法,其特征在于,所述方法包括:第一网元接收第一信息,所述第一信息包括第一终端的第一标识;所述第一网元发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述第一网元接收第三信息,所述第三信息包括所述第二标识;所述第一网元向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。
- 根据权利要求1所述的方法,其特征在于,所述方法包括:所述第一网元发送第五信息,所述第五信息包括所述第一标识,所述第五信息用于请求第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述第一网元接收第六信息,所述第六信息包括所述第三标识;所述第一网元向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
- 根据权利要求2所述的方法,其特征在于,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
- 根据权利要求2或3所述的方法,其特征在于,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
- 根据权利要求2-4中任一项所述的方法,其特征在于,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
- 根据权利要求1-5中任一项所述的方法,其特征在于,所述第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
- 根据权利要求1-6中任一项所述的方法,其特征在于,所述第二标识包括第一小区标识和/或第一接入点名称APN。
- 一种通信系统,其特征在于,包括第一终端、第一网元、第一服务器;所述第一终端用于发送第一信息,所述第一信息包括所述第一终端的第一标识,所述第一终端接入第一网络;所述第一网元用于接收所述第一信息;所述第一网元还用于向所述第一服务器发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求所述第一网络的第二标识;所述第一网元还用于接收所述第三信息,所述第三信息包括所述第二标识;所述第一网元还用于向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系;所述第一服务器用于接收所述第四信息,所述第一服务器还用于管理所述第一终端。
- 根据权利要求8所述的系统,其特征在于,所述通信系统还包括第二终端;所述第一网元用于发送第五信息,所述第五信息包括所述第一标识,所述第五信息用于请求所述第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述第一网元还用于接收第六信息,所述第六信息包括所述第三标识;所述第一网元还用于向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
- 根据权利要求9所述的系统,其特征在于,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
- 根据权利要求9或10所述的系统,其特征在于,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
- 根据权利要求9-11中任一项所述的系统,其特征在于,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
- 根据权利要求8-12中任一项所述的系统,其特征在于,所述第一标识包括介质访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
- 根据权利要求8-13中任一项所述的系统,其特征在于,所述第二标识包括第一小区标识和/或第一接入点名称APN。
- 一种通信装置,其特征在于,所述装置包括:收发模块,用于接收第一信息,所述第一信息包括第一终端的第一标识;所述收发模块还用于发送第二信息,所述第二信息包括所述第一标识,所述第二信息用于请求第一网络的第二标识,所述第一网络是所述第一终端接入的网络;所述收发模块还用于接收第三信息,所述第三信息包括所述第二标识;所述收发模块还用于向第一服务器发送第四信息,所述第四信息用于指示所述第一标识与所述第二标识的关联关系,所述第一服务器用于管理所述第一终端。
- 根据权利要求15所述的装置,其特征在于,所述装置包括:所述收发模块还用于发送第五信息,所述第五信息包括所述第一标识,所述第五信息用于请求第二终端的第三标识,所述第二终端是连接所述第一终端和所述第一网络的设备,所述第一终端为工业终端设备;所述收发模块还用于接收第六信息,所述第六信息包括所述第三标识;所述收发模块还用于向所述第一服务器发送第七信息,所述第七信息用于指示所述第一标识与所述第三标识的关联关系。
- 根据权利要求16所述的装置,其特征在于,所述第五信息包括第一事件标识,所述第一事件标识用于指示请求所述第二终端的第三标识。
- 根据权利要求16或17所述的装置,其特征在于,所述第七信息还用于指示所述第一标识、所述第二标识与所述第三标识的关联关系。
- 根据权利要求16-18中任一项所述的装置,其特征在于,所述第三标识包括国际移动用户识别码IMSI和/或国际移动设备识别码IMEI和/或用户永久标识SUPI和/或一般公共订阅标识符GPSI。
- 根据权利要求15-19中任一项所述的装置,其特征在于,所述第一标识包括介质 访问控制层MAC地址和/或网际协议IP地址和/或设备名称和/或设备角色和/或设备标识。
- 根据权利要求15-20中任一项所述的装置,其特征在于,所述第二标识包括第一小区标识和/或第一接入点名称APN。
- 一种用于通信的通信装置,其特征在于,包括处理器和通信接口,所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号传输给所述通信装置之外的其它通信装置,所述处理器用于实现如权利要求1至7中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机程序,当所述计算机程序被运行时,实现如权利要求1至7中任一项所述的方法。
- 一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码被通信装置运行时,使得所述通信装置执行如权利要求1至7中任一项所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22836754.6A EP4333538A4 (en) | 2021-07-06 | 2022-06-27 | COMMUNICATION METHOD, SYSTEM AND DEVICE |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110760280.6 | 2021-07-06 | ||
CN202110760280.6A CN115589364A (zh) | 2021-07-06 | 2021-07-06 | 一种通信方法、系统和装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023280000A1 true WO2023280000A1 (zh) | 2023-01-12 |
Family
ID=84772068
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/101555 WO2023280000A1 (zh) | 2021-07-06 | 2022-06-27 | 一种通信方法、系统和装置 |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP4333538A4 (zh) |
CN (1) | CN115589364A (zh) |
WO (1) | WO2023280000A1 (zh) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102356668A (zh) * | 2009-03-18 | 2012-02-15 | 诺基亚西门子通信公司 | 用于通信网络中的拓扑信息的分发的方法和设备 |
CN105323780A (zh) * | 2014-07-18 | 2016-02-10 | 中兴通讯股份有限公司 | 物联网的终端拓扑管理服务方法、装置及系统 |
CN108880899A (zh) * | 2018-06-30 | 2018-11-23 | 华为技术有限公司 | 一种网络拓扑图生成方法及服务器 |
CN109831334A (zh) * | 2019-02-20 | 2019-05-31 | 普联技术有限公司 | 网络拓扑构建方法、装置及终端设备 |
CN110913473A (zh) * | 2018-09-18 | 2020-03-24 | 电信科学技术研究院有限公司 | 选择方法、装置、管理功能实体、接入网节点、gmlc及nrf |
WO2020232667A1 (en) * | 2019-05-22 | 2020-11-26 | Abb Schweiz Ag | Network topology discovery in substation |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102323235B1 (ko) * | 2019-05-03 | 2021-11-08 | 주식회사 케이티 | 스마트팩토리의 산업 장치 원격 제어 방법 및 장치 |
-
2021
- 2021-07-06 CN CN202110760280.6A patent/CN115589364A/zh active Pending
-
2022
- 2022-06-27 EP EP22836754.6A patent/EP4333538A4/en active Pending
- 2022-06-27 WO PCT/CN2022/101555 patent/WO2023280000A1/zh active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102356668A (zh) * | 2009-03-18 | 2012-02-15 | 诺基亚西门子通信公司 | 用于通信网络中的拓扑信息的分发的方法和设备 |
CN105323780A (zh) * | 2014-07-18 | 2016-02-10 | 中兴通讯股份有限公司 | 物联网的终端拓扑管理服务方法、装置及系统 |
CN108880899A (zh) * | 2018-06-30 | 2018-11-23 | 华为技术有限公司 | 一种网络拓扑图生成方法及服务器 |
CN110913473A (zh) * | 2018-09-18 | 2020-03-24 | 电信科学技术研究院有限公司 | 选择方法、装置、管理功能实体、接入网节点、gmlc及nrf |
CN109831334A (zh) * | 2019-02-20 | 2019-05-31 | 普联技术有限公司 | 网络拓扑构建方法、装置及终端设备 |
WO2020232667A1 (en) * | 2019-05-22 | 2020-11-26 | Abb Schweiz Ag | Network topology discovery in substation |
Also Published As
Publication number | Publication date |
---|---|
CN115589364A (zh) | 2023-01-10 |
EP4333538A1 (en) | 2024-03-06 |
EP4333538A4 (en) | 2024-10-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE49729E1 (en) | Session information management method and apparatus | |
JP7485793B2 (ja) | スライスアクセス方法、装置、及びシステム | |
EP3869855A1 (en) | Information transmission method and apparatus thereof | |
WO2020108002A1 (zh) | 一种传输策略确定方法、策略控制方法及装置 | |
WO2021135187A1 (zh) | 一种切片控制方法及装置 | |
WO2021197185A1 (zh) | 一种通信方法和通信装置 | |
EP4192184A1 (en) | Pdu session establishment method, terminal device, and chip system | |
WO2020151584A1 (zh) | 网络配置的方法和通信装置 | |
WO2022052875A1 (zh) | 终端跨区域通信方法、网元设备及存储介质 | |
US20230379806A1 (en) | Method and apparatus for supporting information acquisition, device, and readable storage medium | |
WO2020024865A1 (zh) | 一种会话对应关系的管理方法和终端设备 | |
WO2021227600A1 (zh) | 一种网络切片控制方法及通信装置 | |
WO2021115429A1 (zh) | 一种通信方法及装置 | |
WO2024051313A1 (zh) | 通信资源管理方法、装置、系统及存储介质 | |
WO2023280093A1 (zh) | 执行在线签约的方法和装置 | |
WO2023280000A1 (zh) | 一种通信方法、系统和装置 | |
WO2022141528A1 (zh) | 一种确定mec接入点的方法及装置 | |
CN116746207A (zh) | 应用相关功能的资源分配状态订阅 | |
CN117596583A (zh) | 动态发现核心网络中服务网络节点的方法、网络节点和介质 | |
WO2020088626A1 (zh) | 一种pdu会话的动态调整方法、装置 | |
WO2023280114A1 (zh) | 基于介质冗余协议进行组网的方法和装置 | |
WO2024164640A1 (zh) | 一种通信方法、通信装置及通信系统 | |
WO2023061207A1 (zh) | 一种通信方法、通信装置及通信系统 | |
WO2024164905A1 (zh) | 一种边缘应用服务器选择方法和装置 | |
WO2023015973A1 (zh) | 一种网络切片准入控制方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22836754 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022836754 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022836754 Country of ref document: EP Effective date: 20231201 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |