Patent Application
20240163670
This application relates to the communication field, and in particular, to a wireless communication method and apparatus.
With the development of a 5th-generation (5 Generation, 5G) industrial internet technology, especially the rapid development of in-depth integration of informatization and industrialization, an increasing number of industrial control system products are connected to public networks, such as the internet, by using general-purpose protocols, general-purpose hardware, and general-purpose software in various manners. In particular, a 5G local area network may provide wireless data access and a high-quality information transmission service that complies with industry standards for an industrial device in an industrial automatic control system (Industrial automatic control system, IACS). For example, an industrial terminal device in an industrial field network implements wireless network access by using customer premise equipment (Customer Premise Equipment, CPE).
An industrial field network service has high requirements on real-time information transmission and network information security. However, an industrial field network based on a 5G wireless communication system has complex application environments, and has many network communication modes and distributed devices. There is a possibility of attacks. An open network environment, an industrial terminal with limited security mechanisms, and message transmission pose many information security risks to industrial field networks.
How to ensure secure transmission of a service packet of the industrial terminal device in the industrial field network becomes an urgent problem to be resolved in the industry.
This application provides a wireless communication method and apparatus, to ensure secure transmission of a service packet of an industrial terminal in an industrial field network.
According to a first aspect, a wireless communication method is provided, including: A first device obtains first information, where the first information includes a correspondence between first customer premise equipment and at least one first terminal device, and a correspondence between the first terminal device and at least one second terminal device. The first device configures the first information on a second device, where the first information is used by the second device to verify that a received service packet is a service packet sent by the first terminal device to the second terminal device by using the first customer premise equipment.
According to the wireless communication method provided in this application, the first device obtains the correspondence between the first customer premise equipment and the at least one first terminal device, and the correspondence between the first terminal device and the at least one second terminal device, and configures the correspondences for the second device. The second device verifies that a terminal device corresponding to a source address of the received service packet is a terminal device corresponding to the first customer premise equipment, and terminal devices corresponding to the source address and a destination address respectively correspond to a control end terminal device and an execution end terminal device, to authorize forwarding the service packet. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network is improved.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first device generates a token of the first customer premise equipment based on the first information, and signs the token. The first device sends the token to the second device.
According to the technical solution, the first device configures the first information for the second device in a form of a token, and signs the token, to ensure that the second device may determine validity of the token after receiving the token. The validity may be understood as integrity and accuracy of content of the token, or may be understood as security of the token. In this way, security of the service packet is subsequently verified by using the token.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first device generates a configuration message of the first customer premise equipment based on the first information. The first device sends the configuration message to the second device.
According to the technical solution, the first device may directly configure a packet message for the second device, which increases flexibility of processing the first information by the first device. The configuration message may be directly verified and used by the second device. It should be understood that, in this case, the first device and the second device are in a same security domain, and a secure channel is established between the first device and the second device. Therefore, the configuration message may be directly used to verify the packet, and security of the configuration message does not need to be additionally verified, thereby reducing signaling and improving efficiency.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first information further includes a security certificate of the first terminal device, the security certificate is used by the second device to verify an identifier signature of the first terminal device based on a public key of the first terminal device, and the security certificate is delivered or pre-configured by the first device.
According to the technical solution, the first terminal device has a security capability, and verifies the identifier signature of the first terminal device based on the public key of the first terminal device included in the security certificate of the first terminal device, to ensure validity of the first terminal device and prevent the first terminal device from being attacked, thereby ensuring security of the service packet transmitted by the first terminal device.
In a possible implementation, the security certificate is delivered by the IFES, or is pre-configured.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: That the first device configures the first information on a second device includes: The first device sends the first information to the second device by using a user plane function UPF network element. According to the technical solution, the first device may include the first information in a user plane, and a carrying manner may be flexibly selected when the first information is configured.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first device sends the first information to a network exposure function NEF network element, so that the NEF network element sends a configuration request message to the second device by using a unified data management UDM network element. The configuration request message is used to request the second device to configure the first information, and the configuration request message includes a subscription permanent identifier of the second device.
Alternatively, the first device sends a policy request message to a policy control function PCF network element, where the policy request message includes the first information, and the policy request message is used by the PCF network element to send a packet detection rule PDR and a QoS enforcement rule QER to a UPF network element by using a session management function SMF network element.
According to the technical solution, the first device may include the first information in a control plane, and a carrying manner may be flexibly selected when the first information is configured.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first information further includes that the first terminal device is a control end device and/or the second terminal device is an execution end device.
According to this technical solution, the first information includes role information of the terminal device, so that the second device further determines, when verifying the service packet, whether a role of the first terminal device matches a role of the second terminal device, thereby ensuring validity of packet information.
With reference to the first aspect, in some implementations of the first aspect, the method further includes: The first device is an AF, the second device is one of the UPF, the first customer premise equipment, or second customer premise equipment, and the second customer premise equipment is customer premise equipment corresponding to the at least one second terminal device.
According to a second aspect, a wireless communication method is provided, including: A second device obtains first information, where the first information includes a correspondence between first customer premise equipment and at least one first terminal device, and a correspondence between the first terminal device and at least one second terminal device. The second device verifies, based on the first information, that a received service packet is a service packet sent by the first terminal device to the second terminal device by using the first customer premise equipment. The second device sends the service packet to second customer premise equipment.
According to the wireless communication method provided in this application, the second device obtains the correspondence between the first customer premise equipment and the at least one first terminal device, and the correspondence between the first terminal device and the at least one second terminal device. The second device verifies that a terminal device corresponding to a source address of a received service packet is a terminal device corresponding to the first customer premise equipment, and terminal devices corresponding to the source address and a destination address respectively correspond to a control end terminal device and an execution end terminal device, to authorize forwarding the service packet. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network is improved.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The second device receives a token, and determines, with reference to a signature of the token, that the token is a token corresponding to the first customer premise equipment. The token is generated by a first device for the first customer premise equipment based on the first information.
According to the technical solution, the second device may determine validity of the token. In this way, security of the service packet is subsequently verified by using the token.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The second device receives a configuration message, where the configuration message is generated by the first device for the first customer premise equipment based on the first information.
According to this technical solution, the second device may directly verify the service packet based on the configuration message. It should be understood that, in this case, the first device and the second device are in a same security domain, and a secure channel is established between the first device and the second device. Therefore, the configuration message may be directly used to verify the packet, and authenticity and security do not need to be verified, thereby saving signaling and improving efficiency.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The second device verifies, based on the correspondence between the first customer premise equipment and the at least one first terminal device in the first information, that a control end device corresponding to a source address of the service packet is one of first terminal devices corresponding to the first customer premise equipment. The second device verifies, based on the correspondence between the first terminal device and the at least one second terminal device in the first information, that the control end device and an execution end device that correspond to the source address and a destination address of the service packet are respectively one of the first terminal devices and one of the second terminal devices.
According to the technical solution, the second device may verify, based on the first information, that a sending end device in the service packet corresponds to the first customer premise equipment, and the sending end and a receiving end in the service packet respectively correspond to the first terminal device and the second terminal device, to verify that the sending end device of the service packet is a terminal device connected to the first customer premise equipment, and a communication path is a preset valid path. In this way, validity of the first terminal device, validity of the communication path, and secure transmission of the service packet are ensured.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The second device verifies an identifier signature of the first customer premise equipment based on a pre-configured public key of the first customer premise equipment.
According to the technical solution, the second device may verify an identity of the first customer premise equipment, that is, ensure the security of the first customer premise equipment itself, and prevent the first customer premise equipment from being attacked.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The first information further includes a security certificate of the first terminal device. The method further includes: The second device verifies an identifier signature of the first terminal device based on a pre-configured public key of the first terminal device.
According to the technical solution, the first terminal device has a security capability, and verifies the identifier signature of the first terminal device based on the public key of the first terminal device included in the security certificate of the first terminal device, to ensure validity of the first terminal device and prevent the first terminal device from being attacked, thereby ensuring security of a service packet transmitted by the first terminal device.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The second device obtains and includes the first information in a user plane, or the second device obtains and carries the first information by using a control plane.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The first information further includes that the first terminal device is a control end device and/or the second terminal device is an execution end device.
According to this technical solution, the first information includes role information of the terminal device, so that the second device further determines, when verifying the service packet, whether a role of the first terminal device matches a role of the second terminal device, thereby ensuring validity of packet information.
With reference to the second aspect, in some implementations of the second aspect, the method further includes: The first device is an AF, the second device is one of a UPF, the first customer premise equipment, or the second customer premise equipment, and the second customer premise equipment is customer premise equipment corresponding to the at least one second terminal device.
According to a third aspect, a wireless communication apparatus is provided, and the wireless communication apparatus executes units of the method according to the first aspect or the implementations of the first aspect.
Based on the foregoing technical solution, the packet processing apparatus performs the method according to the first aspect or the implementations of the first aspect. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network and an entire industrial field network is improved.
According to a fourth aspect, a wireless communication apparatus is provided, and the wireless communication apparatus executes units of the method according to the second aspect or the implementations of the second aspect.
Based on the foregoing technical solution, the wireless communication apparatus performs the method according to the second aspect or the implementations of the second aspect. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network and an entire industrial field network is improved.
According to a fifth aspect, a wireless communication apparatus is provided, including a memory and a processor. The memory is configured to store computer instructions, and the processor is configured to execute the computer instructions stored in the memory, so that the wireless communication apparatus performs the wireless communication method according to the first aspect or the second aspect and the possible implementations of the first aspect or the second aspect.
Based on the foregoing technical solution, the wireless communication apparatus performs the method according to the foregoing implementations. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network and an entire industrial field network is improved.
Optionally, there are one or more processors, and there are one or more memories.
Optionally, the memory may be integrated with the processor, or the memory and the processor are separately disposed.
According to a sixth aspect, a wireless communication apparatus is provided, including one of the foregoing first device and second device.
According to a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (which may also be referred to as code or instructions), and when the computer program is run on a computer, the computer is enabled to perform the method according to any one of the possible implementations of the first aspect and the second aspect.
According to an eighth aspect, a chip system is provided, including a processor and a memory, so that a communication apparatus installed with the chip system enabled to perform the method according to any one of the possible implementations of the first aspect and the second aspect.
The following describes technical solutions of this application with reference to accompanying drawings.
A wireless communication system mentioned in embodiments of this application includes but is not limited to a long term evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD) system, a universal mobile telecommunication system (Universal Mobile Telecommunication System, UMTS), a worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, WiMAX) communication system, a 5th-generation (5th Generation, 5G) system, a future 6th-generation (6th Generation, 6G), or a new radio (New Radio, NR) system.
The following clearly and completely describes the technical solutions in embodiments of this application with reference to the accompanying drawings in embodiments of this application. It is clear that the described embodiments are some but not all of embodiments of this application. All other embodiments obtained by a person of ordinary skill in the art based on embodiments of this application without creative efforts shall fall within the protection scope of this application.
For ease of understanding embodiments of this application, a schematic diagram of an architecture of a wireless communication system 100 according to an embodiment of this application is first briefly described with reference to
The communication system 100 shown in
As shown in
It should be understood that, in this embodiment of this application, the industrial terminal 111 may specifically include a plurality of industrial controllers and industrial devices. Real-time service communication is implemented between the industrial controllers and the industrial devices by using customer premise equipment and a network device. In addition, a communication path relationship between each industrial controller and each industrial device has been configured during configuration.
When user equipment 111 is located outside network coverage or a communication signal between the user equipment 111 and the access network device 121 is poor, the user equipment 111 may communicate with user equipment 112, and the user equipment 112 communicates with the access network device 121, so that the user equipment 111 can communicate with the access network device 121, and the access network device 121 forwards the data packet to the data network by using the UPF.
As shown in
1. User equipment (UE): The terminal device in embodiments of this application may also be referred to as user equipment (user equipment, UE), a mobile station (mobile station, MS), a mobile terminal (mobile terminal, MT), an access terminal, a user unit, a user station, a mobile base station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, a user apparatus, or the like.
In embodiments of this application, the user equipment is, in particular, an industrial terminal device in an industrial scenario, for example, an industrial controller and an industrial device, for example, a programmable logic controller (Programmable Logic Controller, PLC), a distributed control system (Distributed Control System, DCS), or a supervisory control and data acquisition (Supervisory Control And Data Acquisition, SCADA) system. The user equipment may be any device that can detect and control an electromechanical device, a process device, or the like in a production process. This is not limited in embodiments of this application.
In addition, in embodiments of this application, the user equipment may alternatively be user equipment in an internet of things (internet of things, IoT) system. An IoT is an important part in future development of information technologies. A main technical feature of the IoT is to connect things to a network by using a communication technology, to implement an intelligent network for human-machine interconnection and thing-thing interconnection.
In embodiments of this application, the IoT technology may implement massive connections, in-depth coverage, and terminal power saving by using, for example, a narrow band (narrow band) NB technology. For example, an NB may include only one resource block (resource block, RB). In other words, a bandwidth of the NB is only 180 KB. To implement massive access, terminals need to be discrete in access. According to the communication method in embodiments of this application, a congestion problem that occurs in the IoT technology when massive terminals access a network through the NB may be effectively resolved.
In addition, an access device in embodiments of this application may be a device configured to communicate with user equipment, and the access device may also be referred to as an access network device or a radio access network device. For example, the access device may be an evolved NodeB (evolved NodeB, eNB or eNodeB) in an LTE system, or may be a radio controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or may be a relay station, an access point, a vehicle-mounted device, a wearable device, an access device in a future 5G network, or an access device in a future evolved PLMN network, or may be an access point (access point, AP) in a WLAN, or may be a gNB in a new radio (new radio, NR) system. This is not limited in embodiments of this application.
In addition, in embodiments of this application, the user equipment may further perform communication, for example, inter-device communication, with user equipment in another communication system. For example, the user equipment may further transmit (for example, send and/or receive) a time synchronization packet with user equipment in another communication system.
2. Access device (AN/RAN): The access device in embodiments of this application may be a device configured to communicate with user equipment, and the access device may also be referred to as an access network device or a radio access network device. For example, the access device may be an evolved NodeB (evolved NodeB, eNB or eNodeB) in an LTE system, or may be a radio controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or may be a relay station, an access point, a vehicle-mounted device, a wearable device, an access device in a 5G network, or an access device in a future evolved PLMN network, or may be an access point (access point, AP) in a WLAN, or may be a gNB in an NR system. This is not limited in embodiments of this application.
In addition, in embodiments of this application, the access device is a device in a RAN. In other words, the access device is a RAN node that enables the user equipment to access a wireless network. For example, by way of example and not limitation, the access device may be a gNB, a transmission reception point (transmission reception point, TRP), an evolved NodeB (evolved NodeB, eNB), a radio network controller (radio network controller, RNC), a NodeB (NodeB, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home evolved NodeB (for example, a home evolved NodeB or a home NodeB, HNB), a baseband unit (base band unit, BBU), or a wireless fidelity (wireless fidelity, Wi-Fi) access point (access point, AP). In a network structure, the network device may include a central unit (central unit, CU) node, a distributed unit (distributed unit, DU) node, a RAN device including a CU node and a DU node, or a RAN device including a control plane CU node (CU-CP node), a user plane CU node (CU-UP node), and a DU node.
The access device serves a cell. The user equipment communicates with the access device on a transmission resource (for example, a frequency domain resource, or in other words, a frequency spectrum resource) used for the cell. The cell may be a cell corresponding to the access device (for example, a base station). The cell may belong to a macro base station, or a base station corresponding to a small cell (small cell). The small cell herein may include a metro cell (metro cell), a micro cell (micro cell), a pico cell (pico cell), a femto cell (femto cell), or the like. These small cells have features of small coverage and low transmit power, and are applicable to providing a high-speed data transmission service.
In addition, a plurality of cells may simultaneously operate in a same frequency band on a carrier in the LTE system or the 5G system. In some special scenarios, it may also be considered that a concept of the carrier is equivalent to that of the cell. For example, in a carrier aggregation (carrier aggregation, CA) scenario, both a carrier index of a secondary carrier and a cell identifier (cell identification, Cell ID) of a secondary cell that works on the secondary carrier are carried when the secondary carrier is configured for UE. In this case, it may be considered that the concept of the carrier is equivalent to that of the cell. For example, that the user equipment accesses a carrier is equivalent to that the user equipment accesses a cell.
3. Access and mobility management function (Access and Mobility Management Function, AMF) network element: The access and mobility management function network element is mainly used for mobility management, access management, and the like, and may be configured to implement another function other than session management in a mobility management entity (mobility management entity, MME) function in an LTE system, for example, functions such as lawful interception and access authorization/authentication. When the AMF network element provides a service for a session in user equipment, the AMF network element provides a control plane storage resource for the session, to store a session identifier, an SMF network element identifier associated with the session identifier, and the like. In embodiments of this application, the AMF network element may be configured to implement functions of an access and mobility management network element.
4. Session management function (Session Management Function, SMF) network element: The session management function network element is mainly used for session management, internet protocol (internet protocol, IP) address allocation and management of user equipment, selection and management of a user plane function, policy control, or an end point of a charging function interface, and downlink data notification. In embodiments of this application, the session management function network element may be used to implement a function of a session management network element.
5. Policy control (Policy Control Function, PCF) network element: The policy control network element is a unified policy framework used to guide network behavior, and provides policy rule information, a traffic-based charging control function, and the like for a control plane function network element (such as an AMF or an SMF network element).
6. Unified data management (unified data management, UDM) network element: The unified data management network element is mainly responsible for processing subscription data of the UE, including storage and management of a user identifier, user subscription data, authentication data, and the like.
7. User plane function (User Plane Function, UPF) network element: The user plane function network element is used for packet routing and forwarding, quality of service (Quality of Service, QoS) processing of user plane data, or the like. User data may be accessed to a data network (data network, DN) by using the network element, and the user data may further be received from the data network, and then transmitted to the user equipment by using an access network device. In the UPF network element, a transmission resource and a scheduling function that provide a service for the user equipment are managed and controlled by the SMF network element. In embodiments of this application, the user plane function network element may be configured to implement a function of a user plane network element.
8. Network exposure function (Network Exposure Function, NEF) network element: The network exposure function network element is configured to securely expose services, capabilities, and the like provided by a 3GPP network function to the outside, and mainly supports secure interaction between a 3GPP network and a third-party application.
9. Application function (Application Function, AF) network element: The application function network element is configured to perform application-affected data routing, access a network exposure function network element, or interact with a policy framework to perform policy control, for example, affect data routing decision or a policy control function, or provide some third-party services for a network side.
10. Network slice selection function (Network Slice Selection Function, NSSF) network element: The network slice selection function network element is mainly responsible for network slice selection, and determines, based on slice selection assistance information and subscription information of the UE, a network slice instance that the UE is allowed to access.
11. Authentication server function (Authentication Server Function, AUSF) network element: The authentication server function network element supports 3GPP and non-3GPP access authentication.
12. Network repository function (Network Repository Function, NRF) network element: The network repository function network element supports registration and discovery of network functions.
13. Unified data repository (Unified Data Repository, UDR) function network element: The unified data repository function network element stores and obtains subscription data used by the UDM and the PCF.
In the network architecture, an N2 interface is a reference point between a RAN and an AMF entity, and is used to send a NAS (Non-Access Stratum, non-access stratum) message and the like. An N3 interface is a reference point between the RAN and the UPF network element, and is used to transmit user plane data and the like. An N4 interface is a reference point between the SMF network element and the UPF network element, and is used to transmit information such as tunnel identifier information connected by N3, data buffer indication information, and a downlink data notification message.
It should be understood that the UE, the (R)AN, the UPF, and the DN in
It should be understood that the foregoing network architecture applied to embodiments of this application is merely an example of a network architecture described from the perspective of a conventional point-to-point architecture and a service architecture, and a network architecture applicable to embodiments of this application is not limited thereto. Any network architecture that can implement functions of the foregoing network elements is applicable to embodiments of this application.
It should be understood that names of interfaces between the network elements in
It should be noted that the “network element” may also be referred to as an entity, a device, an apparatus, a module, or the like. This is not particularly limited in this application. In addition, in this application, for ease of understanding and description, the description “network element” is omitted in some descriptions. For example, the SMF network element is referred to as an SMF for short. In this case, the “SMF” should be understood as an SMF network element or an SMF entity. Descriptions of same or similar cases are omitted below.
It may be understood that the entities or the functions may be network elements in a hardware device, may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform).
Specific embodiments are used below to describe in detail the technical solutions of this application. The following several specific embodiments may be combined with each other, and a same or similar concept or process may not be described repeatedly in some embodiments.
S301: A first device obtains first information of an industrial field network.
Specifically, the first device obtains the first information of the industrial field network, where the first information may be configuration information, and the configuration information includes a binding relationship between first customer premise equipment CPE 1 and at least one first terminal device, and a communication relationship between the first terminal device and at least one second terminal device. The binding relationship may be understood as that one CPE may serve at least one industrial terminal device in a directional manner. For example, an industrial terminal device A and an industrial terminal device B are connected to the CPE 1, and both the industrial terminal device A and the industrial terminal device B may be connected to an access network device by using the CPE 1. The communication relationship refers to a direction of a communication path between industrial terminal devices. For example, data sent by an industrial terminal device C is received by an industrial terminal device D. The binding relationship and the communication relationship may alternatively be referred to as an association relationship, a correspondence, a correlation relationship, or the like. This is not limited in this embodiment of this application.
Optionally, the configuration information may further include a valid role of the industrial terminal device, that is, a preset functional role of the industrial terminal device, for example, whether the industrial terminal device is a controller (a sending end device) or an industrial device (a receiving end device).
It should be understood that the first device may be an AF device, for example, an industrial field enable service (Industrial Field Enable Service, IFES) device, or may be another device having a function of configuring configuration information. This is not limited in this embodiment of this application.
In a possible implementation, the first device may further configure a public key certificate of the first device on a second device. The public key certificate of the first device is used by the second device to verify security of the first information configured by the first device for the second device. For details, refer to the description in step S302.
S302: The first device configures the first information on the second device.
Specifically, the first device generates verification information based on the stored first information, and sends the verification information to the second device.
The verification information may be classified into two cases:
Case 1:
In this embodiment of this application, the verification information may be configured as a token form of the CPE 1, and the token may be understood as a token (token) used by the CPE 1 to prove an identity and obtain a permission. The token specifically includes: an identifier of the CPE 1, for example, an IMSI, a GPSI, or an MEI; a binding relationship between the CPE 1 and an industrial terminal device connected to the CPE 1, for example, CPE 1-C; and a communication relationship between the CPE 1 and the industrial terminal device connected to the CPE 1, for example, C-D. Optionally, the token may further include role type information of the industrial terminal device connected to the CPE 1. For example, C is a controller.
The first device may further perform digital signature on the token by using a private key of the first device, to ensure integrity and authenticity of the token. Specifically, it may be understood that the second device may verify validity of the signature by using a pre-configured IFES certificate. For example, content of the token is not tampered with by an attacker, to ensure authenticity of the token.
In this case, the first device configures the token to the CPE 1. The CPE 1 may use the token to verify an identity and permission of the CPE 1.
The second device may be the CPE 1, or may be CPE 2. The CPE 2 may be understood as customer premise equipment bound to a receiving end terminal industrial device.
Case 2:
In this embodiment of this application, the verification information may alternatively be a configuration message. The first device obtains, based on the configuration information, configuration information corresponding to the CPE 1 and directly organizes a configuration message. The configuration message includes a certificate of the CPE 1, the binding relationship between the CPE 1 and the industrial terminal device connected to the CPE 1, for example, CPE 1-C, and the communication relationship between the CPE 1 and the industrial terminal device connected to the CPE 1, for example, C-D. Optionally, the configuration message may further include the role type information of the industrial terminal device connected to the CPE 1. For example, C is a controller.
In this case, the first device may directly send the verification packet information to the second device for subsequent packet verification. It should be understood that the configuration message is sent in a form of a packet, not in a form of a token.
It should be understood that content of the verification information is the same as that of the first information, and the verification information is another form of the first information. The verification information may also be referred to as validation information, check information, or a similar description. This is not limited in this embodiment of this application.
The second device may be a UPF.
In a possible implementation, the first device may include the first information in a user plane, and send the first information to the second device.
In a possible implementation, the first device may alternatively include the first information in a control plane, and send the first information to the second device.
S303: The second device obtains the service packet from the first terminal device, and verifies the service packet based on the first information.
Specifically, the first terminal device sends the service packet to the second device, and the second device performs a verification operation based on specific verification information.
In this embodiment of this application, the second device may be CPE, or may be a UPF.
When the second device is a UPF, the second device obtains the service packet by using the CPE 1. The UPF verifies packets in two manners based on the verification information:
Manner 1:
The verification information is configured as a token. Specifically, after receiving the service packet from the first terminal device, the CPE 1 sends service packet information, identifier information of the CPE 1, and a pre-configured token to the UPF, and the UPF performs verification based on a received identifier of the CPE 1 and a token, to verify that the received service packet is a service packet sent by the first terminal device to a second terminal device by using the CPE 1. A verification procedure is as follows:
a: The UPF verifies validity of an identifier signature of the CPE 1 based on a public key of the CPE 1, to determine identity validity of the CPE 1. The validity refers to preset customer premise equipment of the CPE 1 in the industrial field network. It should be understood that, before the identifier of the CPE 1 is verified, a certificate of a pre-configured CPE 1 needs to be searched for in the UPF based on the identifier, to determine that the CPE 1 is a network device known to the UPF, and the certificate of the CPE 1 includes the public key of the CPE 1.
b: That the UPF verifies validity of the token based on the identifier of the CPE 1 specifically means that the token includes a sub field that corresponds to the identifier of the CPE 1, and the UPF may correspond to the identifier of the CPE 1 based on the sub field in the token, to determine that the token is a token corresponding to the CPE 1. It should be understood that before verifying validity of the token, the UPF first verifies validity of a token signature based on a configured IFES certificate, to ensure that content of the token is complete and correct. It should be understood that validity of the token means that the token is complete and accurate, and the token is a token corresponding to the CPE 1.
c: The UPF verifies, based on a binding relationship in the token, the industrial terminal device corresponding to a source address in the service packet, to determine that the industrial terminal device corresponding to the source address in the packet is a device connected to the CPE 1. Specifically, the UPF verifies, based on a correspondence between the first customer premise equipment and the at least one first terminal device in the token, that a sending end device corresponding to the source address of the service packet is one of the first terminal devices corresponding to the first customer premise equipment.
d: The UPF verifies, based on the communication relationship in the token, an industrial terminal device corresponding to a destination address in the service packet, to determine that the industrial terminal device corresponding to the destination address in the packet has a communication relationship with the industrial terminal device in step c. Specifically, the UPF verifies, based on a correspondence between the first terminal device and the at least one second terminal device in the token, that the sending end device and a receiving end device that are corresponding to the source address and the destination address of the service packet are respectively one of the first terminal devices and one of the second terminal devices, to determine that the communication relationship in the packet is authorized.
f: Optionally, whether the roles of the first terminal device and the second terminal device match may be further verified based on the valid role of the industrial terminal device in the token. The matching means that the first terminal device is a controller, and the second terminal device is an industrial device.
Manner 2:
The verification information is configured as a verification packet, and is directly sent to the UPF. Specifically, after receiving the service packet from the first terminal device, the CPE 1 sends the service packet information and the identifier information of the CPE 1 to the UPF, and the UPF performs verification based on the received identifier of the CPE 1 and the verification packet. It should be understood that the verification packet is basically the same as content of the token configured for the CPE 1, and specific verification steps are similar. Details are not described herein again.
When the second device is the CPE, in a possible implementation, the CPE 1 may verify the received service packet based on the identifier of the CPE 1 and the token.
Preferably, the CPE 1 may also send the service packet received from the first terminal device, the identifier of the CPE 1, and the token together to the CPE 2, and the CPE 2 performs verification based on the received identifier of the CPE 1 and the token. A specific verification step is similar to the foregoing, and details are not described herein again.
It should be noted that the binding relationship between the CPE 1 and the first terminal device still needs to be verified. However, in the complex industrial internet, the CPE 1 itself may be attacked. Therefore, the CPE 2 needs to determine, based on a received token, that the CPE 1 itself is valid, to further verify the binding relationship and the communication relationship.
S304: The second device sends the service packet that passes the verification to the second terminal device.
Specifically, the UPF forwards the service packet that passes the verification to the CPE 2, and the CPE 2 further forwards the service packet to the second terminal device.
In a possible implementation, the CPE 2 performs verification, and directly forwards the service packet that passes the verification to the second terminal device.
In this embodiment of this application, the first terminal device may be a controller in the industrial terminal device, and the second terminal device may be an industrial device in the industrial terminal device.
S401: An IFES obtains configuration information in an industrial field network, where the configuration information refers to information pre-configured or set in the industrial field network.
Specifically, a first correspondence between a first terminal device and CPE 1 and a second correspondence between the first terminal device and a second terminal device are included.
It should be understood that the first correspondence may include a correspondence between a plurality of terminal devices and the CPE 1, and the second correspondence may include a correspondence between the first terminal device and the plurality of terminal devices.
Optionally, the configuration information may further include role type information of the terminal device. For example, the first terminal device is a controller, or the second terminal device is an industrial device, or the first terminal device is a controller, and the second terminal device is an industrial device. It should be understood that the controller may also be referred to as a sending end device, and the industrial device may also be understood as a receiving end device. This is not limited in this embodiment of this application.
The IFES may further pre-configure an IFES certificate on a UPF, the CPE 1, and CPE 2, and pre-configure a certificate of the CPE 1 on the UPF.
S402: The IFES generates a token based on the configuration information.
Specifically, the IFES generates configuration information in a token form for the CPE 1 based on stored configuration information. That is, the IFES may configure the configuration information as a token form of the CPE 1.
The token specifically includes: the first correspondence between the CPE 1 and the first terminal device, the second correspondence between the first terminal device and the second terminal device, and the identifier of the CPE 1, for example, an IMSI or a GPSI. The first correspondence may be understood as that the first terminal device communicates with the network device by using the CPE 1, and the second correspondence may be understood as that there is a valid communication path between the first terminal device and the second terminal device. Optionally, the token may further include role type information of the industrial terminal device. For example, the first terminal device is a controller, and/or the second terminal device is an industrial device.
The IFES may further sign the token by using a private key, to verify integrity and authenticity of the token.
S403: The IFES authorizes the CPE 1 to configure the token.
Specifically, the IFES may include information about the token in a 5G user plane, to send the information about the token to the CPE 1.
In a possible implementation, the IFES may alternatively include the information about the token in a 5GC control plane. For a specific method, refer to
S404: The CPE 1 verifies and saves the token.
Optionally, the CPE 1 may verify and store the token. Specifically, the IFES certificate is pre-configured on the CPE 1, and the token signature is verified based on the IFES certificate, to ensure that content of the token is complete and correct.
S405: The CPE 1 sends a configuration response message to the IFES.
S406: The CPE 1 receives a service packet.
Specifically, the service packet includes sending end address information and receiving end address information.
S407: The CPE 1 sends the service packet, the identifier of the CPE 1, and the token to the UPF.
S408: The UPF verifies the service packet based on the identifier of the CPE 1 and the token.
The verification procedure is as follows:
S409: The UPF sends the service packet that passes the verification to the CPE 2.
S410: The CPE 2 forwards the service packet that passes the verification to the second terminal device.
According to the wireless communication method provided in this embodiment of this application, the IFES generates verification information in a token form for the first customer premise equipment based on an obtained correspondence between the first customer premise equipment and the sending end terminal device and an obtained correspondence between the sending end terminal device and the receiving end terminal device, and authorizes and configures the token to the first customer premise equipment. When receiving the service packet, the UPF verifies the service packet based on a first customer premise equipment identifier and the token, to ensure a valid identity of the first client and a valid identity of the token. In addition, the terminal device corresponding to the source address in the service packet is the terminal device corresponding to the first customer premise equipment, and the terminal device corresponding to the source address and the terminal device corresponding to the destination address respectively correspond to the sending end terminal device and the receiving end terminal device, thereby authorizing the forwarding of the service packet. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network is improved.
Steps S501 to S506 are similar to steps S401 to S406 in the method 400. Details are not described herein in this application.
S507: CPE 1 verifies a service packet based on a token.
Specifically, after receiving the service packet, the CPE 1 may verify content of the service packet based on a stored token, and verify, based on a first correspondence in the token, that a terminal device corresponding to a source address in the service packet is a terminal device corresponding to first customer premise equipment. The CPE 1 may verify, based on a second correspondence in the token, that the terminal devices corresponding to the source address and a destination address in the service packet are a first terminal device and a second terminal device respectively.
Optionally, the CPE 1 may alternatively verify, based on the token, that the first terminal device is a sending end device (controller), or verify that the second terminal device is a receiving end device (industrial device).
It should be understood that this step is an optional step. After the CPE 1 performs this step, if the content of the service packet does not pass the verification, a subsequent step does not need to be performed. If the CPE 1 does not perform this step, subsequent service packet verification may also be completely performed by CPE 2. Alternatively, the CPE 1 and the CPE 2 may perform verification at the same time, to improve verification accuracy.
S508: The CPE 1 sends the service packet, an identifier of the CPE 1, and the token to the CPE 2.
S509: The CPE 2 verifies the service packet based on the identifier of the CPE 1 and the token.
The verification procedure is as follows:
It should be noted that the CPE 2 determines, based on the received token, that the CPE 1 is valid, and may further verify the service packet content only after the CPE 1 is excluded from being attacked.
S510: The CPE 2 sends the service packet to the second terminal device.
Based on this embodiment of this application, the IFES generates verification information in a token form for the first customer premise equipment based on an obtained correspondence between the first customer premise equipment and the sending end terminal device and an obtained correspondence between the sending end terminal device and the receiving end terminal device, and authorizes and configures the token to the first customer premise equipment. The first customer premise equipment forwards the token, the first customer premise equipment identifier, and the service packet to the second customer premise equipment, and the second customer premise equipment verifies the service packet based on the first customer premise equipment identifier and the token, to ensure a valid identity of the first customer premise and a valid identity of the token. In addition, the terminal device corresponding to the source address in the service packet is the terminal device corresponding to the first customer premise equipment, and the terminal device corresponding to the source address and the terminal device corresponding to the destination address respectively correspond to the sending end terminal device and the receiving end terminal device, thereby authorizing the forwarding of the service packet. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network is improved.
S601 is basically the same as step S401 in the method 400. To avoid repetition, no repeated description is provided.
S602: An IFES generates a configuration message based on configuration information.
Specifically, the IFES generates the configuration information in a configuration message form for CPE 1 based on saved configuration information. That is, the IFES may configure the configuration information as the configuration message of the CPE 1.
The configuration message specifically includes: a first correspondence between the CPE 1 and a first terminal device, a second correspondence between the first terminal device and a second terminal device, and an identifier of the CPE 1, for example, an IMSI or a GPSI. The first correspondence may be understood as that the first terminal device communicates with a network device by using the CPE 1, and the second correspondence may be understood as that there is a valid communication path between the first terminal device and the second terminal device. Optionally, the token may further include role type information of the industrial terminal device. For example, the first terminal device is a controller, and/or the second terminal device is an industrial device.
It should be understood that specific content of the configuration message is the same as specific content of the token, and is only in different information forms.
S603: The IFES authorizes the UPF to configure the token.
Specifically, the IFES may include the configuration message in the 5G user plane, to send the configuration message to the CPE 1.
In a possible implementation, the IFES may alternatively include the configuration message in the 5GC control plane. For a specific method, refer to
S604: The UPF sends the configuration response message to the IFES.
S605: The CPE 1 receives a service packet.
Specifically, the service packet includes the sending end address and the receiving end address information.
S606: The CPE 1 sends the service packet, the identifier of the CPE 1, and the configuration message to the UPF.
S607: The UPF verifies the service packet based on the identifier of the CPE 1 and the configuration message.
A specific verification step is similar to step S408 in the method 400, and only the token identity does not need to be verified. Other steps are the same. Details are not described herein again.
S608: The UPF sends the service packet that passes the verification to the CPE 2.
S609: The CPE 2 forwards the service packet that passes the verification to the second terminal device.
According to the wireless communication method provided in this embodiment of this application, the IFES generates the verification information in a form of the configuration message for the first customer premise equipment based on the obtained correspondence between the first customer premise equipment and the sending end terminal device and the obtained correspondence between the sending end terminal device and the receiving end terminal device, and authorizes and configures the configuration message to the UPF. When receiving the service packet, the UPF verifies the service packet based on the first customer premise equipment identifier and the configuration message, to ensure the valid identity of the first client and to ensure that the terminal device corresponding to the source address in the service packet is the terminal device corresponding to the first customer premise equipment, and the terminal devices corresponding to the source address and the destination address respectively correspond to the sending end terminal device and the receiving end terminal device, thereby authorizing the forwarding of the service packet. In this solution, the configuration message is used to avoid a complex token verification process, the process is more flexible and simplified, and accuracy of service packet transmission of the industrial terminal device is ensured. To some extent, the industrial terminal or the customer premise equipment may be prevented from being attacked, the loss caused by attack on the device is reduced, and information security of the industrial terminal device in the industrial field network is improved.
The first information is configured in a token form.
S701: An IFES sends the token to an NEF.
S702: The NEF obtains a CPE subscription permanent identifier SUPI based on an address of CPE.
S703: The NEF sends configuration request information to a UDM, where the configuration request information includes the token and the CPE SUPI.
S704: The UDM sends the configuration request information to the CPE.
S705: The CPE sends a configuration response to the IFES by using the UDM and the NEF.
The first information is configured as the configuration message.
S801: The IFES directly or indirectly (through an NEF) sends a policy authorization request message to the PCF. The policy authorization request message includes address information of the first terminal device, service flows of the first terminal device and the second terminal device, and corresponding flow control information, that is, communication path information. The policy authorization request message is used by the PCF to indicate the SMF or the UPF to release the service flows. Optionally, the policy authorization request message further includes functional role information of the terminal device.
S802: The PCF generates a PCC policy based on the policy authorization request message and sends the PCC policy to the SMF. Service flow information and gate control information are used to generate a packet detection rule (Packet Detection Rule, PDR), and a QoS enforcement rule (QoS Enforcement Rule, QER). The SMF may further determine additional flow description information based on a mapping relationship between role information and a service flow characteristic. For example, the terminal device C serves as a controller, and a message sent by the terminal device C has the following characteristics: a-c. The SMF may perform extended description on the PDR based on the information.
S803: The SMF sends the PCC policy to the UPF.
S804: The UPF performs packet monitoring and gate control based on the PDR/QER. Optionally, the PDR may further include a flow characteristic of the role information corresponding to the controller C, and the UPF also needs to perform flow matching based on the characteristic information.
It should be understood that, in a specific implementation, identity authentication of the CPE 1 still needs to be performed based on the method in the method 400. Only the content of the service packet is checked. The UPF performs gate control policy on related service flows based on the PDR and the QER. Other steps are basically the same.
S805: The UPF sends the configuration response to the IFES by using the UDM and the NEF.
In this embodiment of this application, in this solution, it is considered that the industrial terminal device has a security capability after evolution. In other words, the industrial terminal device may support certificate signature, and sign the identifier of the industrial terminal device by using the private key of the industrial terminal device, to indicate the valid identity of the industrial terminal device.
The method 600 is used as an example. If the first terminal device has a security capability, the UPF may determine the valid identity of the first terminal device based on the security capability of the first terminal device.
Specifically, in S601, the IFES obtains the configuration information. The configuration information further includes the security certificate of the first terminal device. In S603, the IFES configures the configuration information on the UPF. That is, the security certificate of the first terminal device is configured on the UPF.
In S607, after the UPF receives the service packet and the identifier signature of the first terminal device from the first terminal device, the UPF searches, based on the received identifier, for a corresponding security certificate configured on the UPF, and verifies validity of the first terminal device identifier based on the public key included in the security certificate of the first terminal device, to determine authenticity of the first terminal device. A subsequent verification step is the same as step S607, and details are not described herein again.
According to the wireless communication method provided in this embodiment of this application, the IFE may configure, on a verification subject, a first correspondence between the first customer premise equipment and the sending end terminal device, and a second correspondence between the sending end terminal device and the receiving end terminal device. The verification subject may verify security of the CPE or the industrial terminal by using a public key signature identifier of the verification subject based on a certificate of a pre-configured CPE or industrial terminal certificate, and further verify security of the service packet based on the first correspondence and the second correspondence. Therefore, accuracy of service packet transmission of an industrial terminal device can be ensured, an industrial terminal or customer premise equipment can be prevented from being attacked to some extent, a loss caused by an attack on the device is reduced, and information security of an industrial terminal device in an industrial field network is improved.
Embodiments described in this specification may be independent solutions, or may be combined based on internal logic. All these solutions fall within the protection scope of this application.
It should be understood that the steps in the foregoing embodiments are merely possible implementations, and this is not limited in this embodiment of this application.
It may be understood that in the foregoing method embodiments, the methods and operations that are implemented by the user equipment may alternatively be implemented by a component (for example, a chip or a circuit) that may be used in the user equipment, and the methods and the operations that are implemented by the access network device (for example, a RAN node) may alternatively be implemented by a component (for example, a chip or a circuit) that may be used in the access network device.
The foregoing mainly describes the solutions provided in embodiments of this application from a perspective of interactions. It may be understood that, to implement the foregoing functions, each network element such as a sending end device or a receiving end device includes a corresponding hardware structure and/or software module for performing each function. A person skilled in the art may be aware that, with reference to the various example units and algorithm steps described in embodiments disclosed in this specification, this application may be implemented by hardware or a combination of computer software and hardware. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.
In embodiments of this application, functional modules of a sending end device or a receiving end device may be divided based on the foregoing method examples. For example, functional modules may be divided based on functions, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. It should be noted that, in embodiments of this application, division of the modules is an example, and is merely logical function division. During actual implementation, another division manner may be used. Descriptions are provided below by using an example in which each functional module is obtained through division corresponding to each function.
The foregoing has described the methods provided in embodiments of this application in detail with reference to
Optionally, the wireless communication apparatus 900 may further include a storage unit 930. The storage unit may be configured to store instructions and/or data. The processing unit 920 may read the instructions and/or the data in the storage unit, so that the communication apparatus is enabled to implement the foregoing method embodiments.
The wireless communication apparatus 900 may be configured to perform an action performed by the first device in the foregoing method embodiment. In this case, the wireless communication apparatus 900 may be the first device or a component that may be configured for the first device. The transceiver unit 910 is configured to perform a receiving and sending related operation on the first device side in the foregoing method embodiments. The storage unit 930 is configured to perform a data or instruction storage related operation on the first device side in the foregoing method embodiments. The processing unit 920 is configured to perform a processing related operation on the first device side in the foregoing method embodiments. The first device may be an AF network element.
Alternatively, the wireless communication apparatus 900 may be configured to perform an action performed by the second device in the foregoing method embodiments. In this case, the wireless communication apparatus 900 may be the second device or a component that may be configured for the second device. The transceiver unit 910 is configured to perform a receiving and sending related operation on the second device side in the foregoing method embodiments. The storage unit 930 is configured to perform a data or instruction storage related operation on the second device side in the foregoing method embodiments. The processing unit 920 is configured to perform a processing related operation on the second device side in the foregoing method embodiments. The second device may be a UPF network element or customer premise equipment.
In a design, the wireless communication apparatus 900 is configured to perform an action performed by the first device in the embodiment shown in
The wireless communication apparatus 900 may implement steps or procedures performed by the first device (IFES) in the method 400 to the method 600 according to embodiments of this application. The wireless communication apparatus 900 may include units configured to perform the methods performed by the first device in the method 400 in
When the communication apparatus 900 is configured to perform the method 400 in
The method 500 and the method 600 are similar to the method 400, and details are not described herein again.
It should be understood that a specific process in which the units perform the foregoing corresponding steps is described in detail in the foregoing method embodiments. For brevity, details are not described herein again.
In another design, the wireless communication apparatus 900 is configured to perform an action performed by the second device in the embodiment shown in
The wireless communication apparatus 900 may implement steps or procedures performed by the second device in the method 400 to the method 600 according to embodiments of this application. The wireless communication apparatus 900 may include units configured to perform the method performed by the second device in the method 400 in
When the communication apparatus 900 is configured to perform the method 400 in
When the wireless communication apparatus 900 is configured to perform the method 500 in
When the wireless communication apparatus 900 is configured to perform the method 600 in
The processing unit 920 in the foregoing embodiments may be implemented by at least one processor or a processor-related circuit. The transceiver unit 910 may be implemented by using a transceiver or a transceiver-related circuit. The transceiver unit 910 may also be referred to as a communication unit or a communication interface. The storage unit may be implemented by using at least one memory.
As shown in
Optionally, the wireless communication apparatus 1000 includes one or more processors 1010.
Optionally, as shown in
Optionally, the wireless communication apparatus 1000 may include one or more memories 1020.
Optionally, the memory 1020 may be integrated with the processor 1010, or separately disposed.
In a solution, the wireless communication apparatus 1000 is configured to implement operations performed by the first device in the foregoing method embodiments.
For example, the processor 1010 is configured to implement a processing-related operation performed by the first device in the foregoing method embodiments.
In another solution, the wireless communication apparatus 1000 is configured to implement operations performed by the second device in the foregoing method embodiments.
For example, the processor 1010 is configured to implement a processing-related operation performed by the second device in the foregoing method embodiments.
It should be noted that the foregoing method embodiments of this application may be applied to a processor, or implemented by a processor. The processor may be an integrated circuit chip with a signal processing capability. In an implementation process, the steps in the foregoing method embodiments may be completed by an integrated logic circuit in a form of hardware or instructions in a form of software in the processor. The processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component. The processor may implement or perform the methods, steps, and logical block diagrams that are disclosed in embodiments of this application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. Steps of the methods disclosed with reference to embodiments of this application may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware and software modules in a decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable read-only memory, or a register. The storage medium is located in the memory. The processor reads information in the memory and completes the steps of the foregoing methods in combination with hardware of the processor.
It may be understood that, in embodiments of this application, the memory may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), and is used as an external cache. By way of example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described in this specification includes but is not limited to these and any other proper types of memories.
It should be understood that the term “and/or” in this specification describes only an association relationship between associated objects and indicates that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character “/” in this specification generally indicates an “or” relationship between the associated objects.
It should be understood that, in embodiments of this application, sequence numbers of the foregoing processes do not mean execution sequences. The execution sequences of the processes should be determined based on functions and internal logic of the processes, and should not constitute any limitation on implementation processes of embodiments of this application.
A person of ordinary skill in the art may be aware that, in combination with the examples described in embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.
It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again.
In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, division of the units is merely logical function division. During actual implementation, another division manner may be used. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not be performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be in electrical, mechanical, or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of embodiments.
In addition, functional units in embodiments of this application may be integrated into one processing unit, each of the units may exist alone physically, or two or more units are integrated into one unit.
When the function is implemented in a form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions in this application essentially, or the part contributing to the conventional technology, or some of the technical solutions may be implemented in a form of a software product. A computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in embodiments of this application. The storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disc.
The foregoing descriptions are merely specific implementations of this application, but the protection scope of this application is not limited thereto. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202110870734.5 | Jul 2021 | CN | national |
This application is a continuation of International Application No. PCT/CN2022/106284, filed on Jul. 18, 2022, which claims priority to Chinese Patent Application No. 202110870734.5, filed on Jul. 30, 2021. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2022/106284 | Jul 2022 | US |
| Child | 18424458 | US |
