WO2024067421A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2024067421A1
WO2024067421A1 PCT/CN2023/120853 CN2023120853W WO2024067421A1 WO 2024067421 A1 WO2024067421 A1 WO 2024067421A1 CN 2023120853 W CN2023120853 W CN 2023120853W WO 2024067421 A1 WO2024067421 A1 WO 2024067421A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
network device
identifier
core network
service requester
Prior art date
Application number
PCT/CN2023/120853
Other languages
English (en)
French (fr)
Inventor
韩之琳
徐艺珊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024067421A1 publication Critical patent/WO2024067421A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and device.
  • RFID radio frequency identification
  • P-IoT passive IoT
  • ambient IoT ambient IoT
  • A-IoT ambient IoT
  • the present application provides a communication method and device to adapt to the needs of batch operations in a third generation partnership project (3GPP) system, reduce signaling interactions, and improve data processing efficiency.
  • 3GPP third generation partnership project
  • the present application provides a communication method, comprising:
  • the core network device obtains request information from the service requester, where the request information includes an identifier of the service requester; the core network device determines a batch execution operation based on the request information, and performs the operation on the first terminal; after the core network device determines that multiple terminals in the first terminal have completed the operation, the core network device sends operation information of the multiple terminals to the service requester, where the first terminal is the terminal to be operated.
  • the first terminal can be understood as the contracted terminal of the service requester, or a terminal that is accessed to the service requester through a certain access method and managed by the service requester. This application does not specifically limit this.
  • the core network device determines to execute the operation in batches based on the request information, which can be understood as the core network device directly determining whether to execute the operation in batches based on the specific content in the request information, and can also be understood as the core network device presetting a certain judgment strategy, and after receiving the request information, the judgment strategy is retrieved based on the content of the request information to determine whether to execute the operation in batches. This application does not specifically limit this.
  • the request information further includes at least one of the following:
  • the first geographical range where the first terminal is located the identifier of the first terminal, and the operation type indication information.
  • the request information includes the above-mentioned multiple types, so that the core network equipment can better determine whether batch operations need to be performed and how to perform batch operations specifically.
  • the core network device determines to execute the operation in batches, and the first terminal is a contracted terminal of the service requester.
  • the core network device determines to execute the operation in batches, and the first terminal is a contracted terminal of the service requester covered by the first geographical scope.
  • the request information when the request information includes the service requester identifier and the first geographical scope, batch operations are directly performed on the terminal, which can reduce the steps of determining the batch operation and improve data processing efficiency.
  • the request information when the request information includes the first geographical scope, and the second geographical scope queried by the core network device based on the service requester's contract data is different from the first geographical scope, the first terminal is a terminal covered by the intersection of the second geographical scope and the first geographical scope.
  • the core network device determines to execute the operation in batches.
  • the core network device determines to execute the operation in batches.
  • the request information includes the identifier of the service requester, the identifier of the first terminal, and the operation type indication information corresponding to the first terminal, and the same operation type indication information corresponds to the identifiers of multiple terminals in the first terminal
  • batch operations are directly performed on the terminals, which can reduce the steps of judging batch operations and improve data processing efficiency.
  • the core network device determines to execute the operation in batches.
  • the request information includes the identifier of the service requester, the first geographical range of the first terminal and the operation type indication information, batch operations are directly performed on the terminals, which can reduce the steps of determining batch operations and improve data processing efficiency.
  • the request information is the identifier of the service requester
  • the core network device obtains the contract data of the service requester based on the identifier of the service requester
  • the contract data includes: the correspondence between the service requester and the operation type, and the correspondence between the service requester and the second geographical scope; the core network device performs batch operations of the corresponding operation type on multiple terminals covered by the second geographical scope based on the contract data.
  • the data processing efficiency can be improved by obtaining relevant information from the contract data to complete the subsequent batch operation process.
  • the operation type of the batch operation is determined according to the operation type indication information.
  • the core network device when the request information includes a first geographical range, sends a first message to an access network device serving a first terminal, the first message including: an operation instruction and an indication identifier, the operation instruction triggers the access network device to trigger multiple random access processes, the operation instruction is determined according to the operation type, and the indication identifier is associated with the identifier of the service requester; the core network device instructs the access network device to execute the random access process for the terminals under the access network device one by one according to the operation instruction; the core network device receives a second message from the access network device, the second message including: an identifier of the second terminal and an indication identifier; when the operation type is inventory, the core network device determines that the second terminal is one of the first terminals according to the indication identifier, and then caches the identifier of the second terminal; or, when the operation type is read, write or deactivate, the core network device determines that the second terminal is one of the first terminals according to the indication identifier, and then
  • the reported terminal identifier is filtered by the indication identifier to ensure that the operation information of the terminal of the service requester is sent to the service requester, which can ensure the accuracy of data processing.
  • the core network device queries the identification list of the contracted terminals of the service requester in the pre-stored or contracted data of the core network device according to the indication identifier; when the core network device determines that the identification list includes the identification of the second terminal, it determines that the second terminal is one of the first terminals.
  • the core network device when the request information includes the identifier of the first terminal, the core network device sends a first message to the access network device serving the first terminal, the first message includes: an operation instruction, an X-group mask range, X ⁇ 1, the operation instruction triggers the access network device to trigger multiple random access processes, and the operation instruction is determined according to the operation type; the core network device instructs the access network device to perform random access processes for the terminals under the X-group mask range one by one according to the operation instruction; the core network device receives a second message from the access network device, the second message includes: the identifier of the second terminal; when the operation type is inventory, the core network device determines that the second terminal is one of the first terminals, and then caches the identifier of the second terminal; or, when the operation type is read, write or deactivate, the core network device determines that the second terminal is one of the first terminals, and then sends read, write or deactivate instruction information to the second terminal through the access network device to obtain the operation information of the second
  • the core network device determines that multiple terminals in the first terminal have completed the operation, including:
  • the core network device determines that the operation time threshold is reached, and then determines that multiple terminals in the first terminal have completed the operation.
  • This method can be used to know the end time of batch operations, avoid frequent operations, and increase signaling interaction data.
  • the first message further includes: an operation time threshold; and the core network device determines that multiple terminals in the first terminal have completed the operation, including:
  • the core network device receives a third message from the access network device, where the third message is used to indicate that an operation time threshold has been reached; the core network device determines, based on the third message, that multiple terminals in the first terminal have completed the operation.
  • This method can be used to know the end time of batch operations, avoid frequent operations, and increase signaling interaction data.
  • the core network device determines that multiple terminals in the first terminal have completed the operation, including:
  • the core network device determines that the operation life cycle has been reached, and then determines that multiple terminals in the first terminal have completed the operation; the operation life cycle is at least Includes one of the following: operation count threshold, X group mask range.
  • This method can be used to know the end time of batch operations, avoid frequent operations, and increase signaling interaction data.
  • the first message further includes at least one of the following: an operation number threshold, an operation time threshold; and the core network device determines that multiple terminals in the first terminal have completed the operation, including:
  • the core network device receives a third message from the access network device, where the third message is used to indicate that a threshold of the number of operations and/or a threshold of the operation time have been reached; the core network device determines, based on the third message, that multiple terminals in the second terminal have performed batch operations.
  • This method can be used to know the end time of batch operations, avoid frequent operations, and increase signaling interaction data.
  • the core network device determines that multiple terminals in the first terminal have completed the operation, it also includes: the core network device sends a fourth message to the access network device, and the fourth message instructs the access network device to end the random access process.
  • the operation information when the operation type is inventory, includes: an identifier of the first terminal that successfully inventories; or, when the operation type is read, the operation information includes: an identifier of the first terminal that successfully reads and the read data.
  • the core network device can send the operation information of the terminals that have not completed the operation to the service requester in addition to the operation information of the terminals that have completed the operation.
  • the operation information of the terminals that have completed the operation and the operation information of the terminals that have not completed the operation can be sent together or separately, which is not specifically limited in this application.
  • the present application provides a communication method, including:
  • the access network device receives a first message from the core network device.
  • the first message includes an operation instruction and an indication identifier.
  • the operation instruction triggers the access network device to trigger multiple random access processes.
  • the operation instruction is determined according to the operation type, and the indication identifier is associated with the identifier of the service requester.
  • the access network device executes the random access process for the terminals under the access network device one by one according to the operation instruction.
  • the access network device after the access network device reports the terminal operation information to the core network device, it enters the next random access without waiting for the core network device to issue the next random access instruction.
  • This method can improve data efficiency and reduce interactive signaling.
  • the access network device receives an identifier of the second terminal from the second terminal; the access network device sends a second message to the core network device, and the second message further includes: the identifier of the second terminal and an indication identifier.
  • the first message also includes: an operation time threshold, and the access network device sends a third message to the core network device, where the third message is used to indicate that the operation time threshold has been reached.
  • the access network device receives a fourth message from the core network device, and the fourth message instructs the access network device to end the random access process.
  • the present application provides a communication method, comprising:
  • the access network device receives a first message from the core network device, where the first message includes an operation instruction and an X group mask range, where X ⁇ 1.
  • the operation instruction triggers the access network device to trigger multiple random access processes, and the operation instruction is determined according to the operation type; the access network device executes the random access process for each terminal under the X group mask range according to the operation instruction.
  • the access network device after the access network device reports the terminal operation information to the core network device, it enters the next random access without waiting for the core network device to issue the next random access instruction.
  • This method can improve data efficiency and reduce interactive signaling.
  • the access network device receives an identifier of the second terminal from the second terminal; the access network device sends a second message to the core network device, and the second message further includes: the identifier of the second terminal.
  • the first message also includes at least one of the following: an operation time threshold, an operation time threshold, and the access network device sends a third message to the core network device, and the third message is used to indicate that the operation time threshold has been reached.
  • the access network device receives a fourth message from the core network device, and the fourth message instructs the access network device to end the random access process.
  • an embodiment of the present application provides a communication device, which may be an access network device (such as the access network device in the first aspect, the access network device in the second aspect, and the access network device in the third aspect) or a chip disposed inside the access network device, and may also be a core network device (such as the core network device in the first aspect, the core network device in the second aspect, and the core network device in the third aspect) or a chip disposed inside the core network device.
  • an access network device such as the access network device in the first aspect, the access network device in the second aspect, and the access network device in the third aspect
  • a chip disposed inside the core network device such as the core network device in the first aspect, the core network device in the second aspect, and the core network device in the third aspect
  • the communication device has the function of implementing any aspect of the first to third aspects above, for example, the communication device includes a module or unit or means corresponding to the steps involved in any aspect of the first to third aspects above, and the function or unit or means may be implemented by software, or by hardware, or may be implemented by hardware executing the corresponding software.
  • the communication device includes a processing unit and a transceiver unit, wherein the transceiver unit can be used to send and receive signals to achieve communication between the communication device and other devices, for example, the transceiver unit is used to receive request information from a service requester; The unit can be used to perform some internal operations of the communication device.
  • the transceiver unit can be called an input-output unit, a communication unit, etc., and the transceiver unit can be a transceiver; the processing unit can be a processor.
  • the transceiver unit can be an input-output interface, an input-output circuit or an input-output pin, etc., and can also be called an interface, a communication interface or an interface circuit, etc.;
  • the processing unit can be a processor, a processing circuit or a logic circuit, etc.
  • the communication device includes a processor and may also include a transceiver, the transceiver is used to send and receive signals, and the processor executes program instructions to complete the method in any possible design or implementation of the first to third aspects above.
  • the communication device may also include one or more memories, the memory is used to couple with the processor, and the memory can store the necessary computer programs or instructions for implementing the functions involved in any of the first to third aspects above.
  • the processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to third aspects above.
  • the communication device includes a processor, which can be used to couple with a memory.
  • the memory can store necessary computer programs or instructions for implementing the functions involved in any one of the first to third aspects.
  • the processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first to third aspects.
  • the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first to third aspects above.
  • the processor can be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory.
  • the above processors can be one or more, and the memories can be one or more.
  • the memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • the embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.
  • an embodiment of the present application provides a communication system, which includes the access network equipment and core network equipment in the above-mentioned first to third aspects.
  • the present application provides a chip system, which includes a processor and may also include a memory, for implementing the method described in any possible design of the first to third aspects above.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the present application also provides a computer-readable storage medium, which stores computer-readable instructions.
  • the computer-readable instructions When executed on a computer, the computer executes a method in any possible design of the first to third aspects.
  • the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods of the various embodiments of the first to third aspects described above.
  • FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of another network architecture provided in an embodiment of the present application.
  • FIG3 shows a schematic diagram of a passive IoT service
  • FIG4A shows a schematic diagram of the inventory process
  • FIG4B shows a schematic diagram of the read and write process
  • FIG5 is a schematic diagram showing a flow chart of a communication method provided in an embodiment of the present application.
  • FIG6 shows a schematic diagram of a batch operation process provided by an embodiment of the present application.
  • FIG7 shows a schematic diagram of a batch operation process provided by an embodiment of the present application.
  • FIG8 shows a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG9 shows a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG. 10 shows a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • 3GPP standard group has formulated the architecture of next generation mobile communication network system (Next Generation System), which is called the fifth generation (5G) network architecture.
  • Next Generation System Next Generation Mobile communication network system
  • This architecture not only supports the access of wireless access technologies defined by 3GPP standard group (such as long term evolution (LTE) access technology, radio access network (RAN) access technology, etc.) to 5G core network (CN), but also supports the use of non-3GPP (non-3GPP) access technology through non-3GPP interworking function (N3IWF) or next generation access gateway (next generation packet data gateway, ngPDG) to access the core network.
  • 3GPP standard group such as long term evolution (LTE) access technology, radio access network (RAN) access technology, etc.
  • CN 5G core network
  • N3IWF non-3GPP interworking function
  • next generation access gateway next generation packet data gateway
  • Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in Figure 1 may include access network equipment and core network equipment.
  • the terminal accesses the data network (DN) through the access network equipment and the core network equipment.
  • DN data network
  • the core network equipment includes but is not limited to some or all of the following network elements: authentication server function (AUSF) network element (not shown in the figure), unified data management (UDM) network element, unified data repository (UDR) network element, network storage function (NRF) network element (not shown in the figure), network exposure function (NEF) network element (not shown in the figure), application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, binding support function (BSF) network element (not shown in the figure).
  • AUSF authentication server function
  • UDM unified data management
  • UDR unified data repository
  • NEF network storage function
  • NEF network exposure function
  • AF application function
  • PCF policy control function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • BSF binding support function
  • the terminal can be a user equipment (UE), a mobile station, a mobile terminal, etc.
  • the terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • the terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, an urban air vehicle (such as a drone, a helicopter, etc.), a ship, a robot, a robotic arm, a smart home device, etc.
  • Access network equipment can be a base station, a pole station, an indoor base station (such as a lamp site), a home base station (such as a home NB), a micro base station, an integrated access and backhaul (IAB) node, a mobile base station, a radio access network (RAN) device, or a wireline access network (FAN) device.
  • radio access network equipment includes 3GPP access network equipment, untrusted non-3GPP access network equipment, and trusted non-3GPP access network equipment.
  • 3GPP access network equipment includes, but is not limited to: evolved node B (eNode B) in LTE, next generation node B (gNB) in 5G mobile communication systems, base stations in future mobile communication systems, or modules or units that complete some functions of base stations, such as centralized units (CU), distributed units (DU), etc.
  • Untrusted non-3GPP access network equipment includes, but is not limited to: untrusted non-3GPP access gateways or N3IWF devices, untrusted wireless local area network (WLAN) access points (APs), switches, and routers.
  • Trusted non-3GPP access network equipment includes, but is not limited to: trusted non-3GPP access gateways, trusted WLAN APs, switches, and routers.
  • Wired access network equipment includes, but is not limited to: wireline access gateways, fixed-line network equipment, switches, and routers.
  • the access network equipment and terminals can be fixed or movable.
  • the access network equipment and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons, and artificial satellites in the air.
  • the embodiments of the present application do not limit the application scenarios of the access network equipment and terminals.
  • the AMF network element performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transmitting user policies between the terminal and the PCF network element.
  • the SMF network element includes functions such as performing session management, executing control policies issued by PCF, selecting UPF, and allocating Internet protocol (IP) addresses to terminals.
  • functions such as performing session management, executing control policies issued by PCF, selecting UPF, and allocating Internet protocol (IP) addresses to terminals.
  • IP Internet protocol
  • UPF network element including the functions of completing user plane data forwarding, session/flow-level billing statistics, bandwidth limitation, etc.
  • UDM network element includes functions such as executing and managing contract data and user access authorization.
  • the UDR network element includes functions for accessing and storing data such as contract data, policy data, and application data.
  • NEF network element is used to support the opening of capabilities and events.
  • AF network elements transmit the requirements of the application side to the network side, such as quality of service (QoS) requirements or user status event subscriptions.
  • QoS quality of service
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IP Multimedia Subsystem (IMS) voice call service.
  • IMS IP Multimedia Subsystem
  • AF network elements include AF network elements in the core network (i.e., AF network elements of operators) and third-party AF network elements (such as an enterprise's application server).
  • the PCF network element includes policy control functions such as billing for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and terminal policy decision-making.
  • PCF network elements include access and mobility management policy control function (AM PCF) network elements and session management policy control function (SM PCF) network elements.
  • AM PCF access and mobility management policy control function
  • SM PCF session management policy control function
  • the AM PCF network element is used to formulate AM policies for terminals.
  • the AM PCF network element can also be called a policy control network element that provides services for terminals (PCF for a UE).
  • the SM PCF network element is used to formulate session management policies (session management policies, SM policies) for sessions.
  • the SM PCF network element can also be called a policy control network element that provides services for sessions ((PCF for a PDU session)).
  • NRF network elements can be used to provide network element discovery functions and provide network element information corresponding to the network element type based on requests from other network elements.
  • NRF also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push.
  • BSF network element can provide BSF service registration/deregistration/update, NRF connection detection, session binding information creation, UE information acquisition, IP address duplicate session binding information query and other functions.
  • the AUSF network element is responsible for authenticating users to determine whether users or devices are allowed to access the network.
  • DN is a network outside the operator network.
  • the operator network can access multiple DNs. Multiple services can be deployed on DN, which can provide data and/or voice services to terminals.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminals.
  • the control server of the sensors is deployed in DN, and the control server can provide services for the sensors.
  • the sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of the company's employees can be terminals.
  • the employees' mobile phones or computers can access information, data resources, etc. on the company's internal office network.
  • Npcf, Nurf, Nudm, Naf, Namf, and Nsmf are service-oriented interfaces provided by the above PCF, UDR, UDM, AF, AMF, and SMF, respectively, and are used to call corresponding service-oriented operations.
  • N1, N2, N3, N4, and N6 are interface serial numbers, and the meanings of these interface serial numbers are as follows:
  • N1 The interface between AMF and the terminal, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to the terminal.
  • NAS non-access stratum
  • N2 The interface between AMF and access network equipment, which can be used to transmit wireless bearer control information from the core network side to the access network equipment.
  • N3 The interface between the access network equipment and UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and UPF.
  • N4 The interface between SMF and UPF can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.
  • N6 The interface between UPF and DN, used to transmit the uplink and downlink user data flows between UPF and DN.
  • Figure 2 is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • the functions of the network elements therein can be referred to the functions of the corresponding network elements in Figure 2, and will not be repeated here.
  • the main difference between Figure 2 and Figure 1 is that the interface between the control plane network elements in Figure 1 is a service-oriented interface, while the interface between the control plane network elements in Figure 2 is a point-to-point interface.
  • N5 The interface between the AF network element and the PCF network element, which can be used to send application service requests and report network events.
  • N7 The interface between PCF network elements and SMF network elements, which can be used to issue protocol data unit (PDU) session granularity and service data flow granularity control strategy.
  • PDU protocol data unit
  • N8 The interface between the AMF network element and the UDM network element, which can be used by the AMF network element to obtain access and mobility management related contract data and authentication data from the UDM network element, and the AMF network element to register terminal mobility management related information with the UDM network element.
  • N9 User plane interface between UPF network elements, used to transmit uplink and downlink user data flows between UPF network elements.
  • N10 The interface between SMF network element and UDM network element, which can be used by SMF network element to obtain session management related contract data from UDM network element, and SMF network element to register terminal session related information with UDM network element.
  • N11 The interface between SMF network element and AMF network element, which can be used to transmit PDU session tunnel information between access network equipment and UPF, transmit control messages sent to terminals, transmit wireless resource control information sent to access network equipment, etc.
  • N15 The interface between the PCF network element and the AMF network element, which can be used to issue terminal policies and access control related policies.
  • N35 The interface between the UDM network element and the UDR network element, which can be used by the UDM network element to obtain user contract data information from the UDR network element.
  • N36 The interface between the PCF network element and the UDR network element, which can be used by the PCF network element to obtain policy-related contract data and application data-related information from the UDR network element.
  • the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the above network element or function can be implemented by one device, or by multiple devices, or a functional module in one device, which is not specifically limited in the embodiments of the present application.
  • the user plane network element, session management network element, and mobility management network element in this application can be the UPF network element, SMF network element, and AMF network element in the 5G system, respectively, or can be a network element having the functions of the above-mentioned UPF network element, SMF network element, and AMF network element in future communications such as the 6th generation (6G) network, and this application is not limited to this.
  • 6G 6th generation
  • the UPF network element, SMF network element, and AMF network element are respectively the user plane network element, the session management network element, and the mobility management network element is described.
  • the UPF network element, the SMF network element, and the AMF network element are referred to as UPF, SMF, and AMF, respectively.
  • a base station such as the 4th generation (4G) eNB, 5G gNB or base stations in future communications
  • the subsequent "base station” can be replaced by "access network device”.
  • a UE is used as an example of a terminal for explanation, and the subsequent "UE" can be replaced by "terminal”.
  • the core network may also include other network functional entities, which is not limited in this application.
  • the technical solution provided in the embodiment of the present application can be applied to various communication systems. For example, it can be applied to 5G systems, and it can also be applied to other new systems facing the future, such as 6G systems, etc.
  • the embodiment of the present application does not specifically limit this.
  • the term "system” can be interchangeable with "network”.
  • P-IoT that is, some network nodes can be passive, semi-passive, semi-active or active, and obtain energy through solar energy, radio frequency, wind energy, hydropower or tidal energy. Please do not specify the way of obtaining energy here. These nodes themselves may not be equipped with or rely on power devices such as batteries, but obtain energy from the environment to support data perception, transmission and distributed computing. Network nodes can also store the obtained energy.
  • the passive Internet of Things architecture may include terminals, readers (readers, or readers and writers) and servers. Passive terminals can be in the form of tags or any other terminal forms without restriction. Terminals can be passive, semi-passive, semi-active or active.
  • Terminals may not have energy storage capabilities (for example, they do not have capacitors), or they may have energy storage capabilities (for example, they have capacitors to store electrical energy).
  • Readers can be access network devices, such as base stations, pole stations, micro base stations, macro stations, etc.; readers can also be terminals, such as mobile phones, IoT devices, handheld readers and writers, etc.
  • the terminal is used as a tag as an example, but it is not limited to tags.
  • the reader uses wireless radio frequency to perform non-contact two-way data communication, and uses wireless radio frequency to read and write electronic tags or radio frequency cards (Tags), so as to achieve the purpose of identifying targets and exchanging data.
  • Tags radio frequency cards
  • the tag when the tag enters the effective identification range of the reader, it receives the radio frequency signal emitted by the reader, and uses the energy obtained by the induced current to send out the information stored in the chip (corresponding to passive tags); the other is that the tag can store part of the electrical energy through solar energy and other means, so that it can actively send a signal of a certain frequency (this can also be called a semi-passive or semi-active tag). After the reader receives and decodes the information, it sends it to the central information system for relevant data processing.
  • Figure 3 shows a schematic diagram of a passive IoT service.
  • Figure 3 takes the reader as a base station (pole station or macro station) as an example for explanation, but the present application does not limit the device form of the reader.
  • the server When the server operates the tag, it can send an operation instruction to the core network (such as the tag management function TMF, TMF can be integrated with the core network equipment, access network equipment or application function, or it can be an independent core network device).
  • the operation instruction may include an inventory operation (or an inventory operation) (it can also be understood as obtaining the tag identifier, and each tag will have its identifier.
  • the tag identifier can be assigned by the enterprise (that is, written into the tag when the enterprise prints the tag) or by the operator.
  • the tag identifier can be a globally unique code - such as an electronic product code (electronic product code). code, EPC), or it can be a temporary identifier or an identifier that is not globally unique.
  • the server can issue inventory instructions.
  • the inventory instructions will include information such as the tag's identification range, reader identification, and location information.
  • the reader will take inventory of the tag according to the inventory instruction and send the tag's identification to the server.
  • the server sends an instruction, and the reader forwards the instruction to the tag.
  • the tag knows that it is an inventory operation based on the content of the instruction.
  • the tag sends the tag's identification to the reader, and the reader sends the tag's identification to the server; alternatively, the tag sends the tag's identification signal to the core network through the reader, and the core network sends the tag's identification to the server. ), read operation (i.e., performing an inventory on the tag Read data.
  • the tag can have a storage function, and its storage area can store data. If the server wants to read the tag, it will send a read instruction.
  • the reader or core network will read the tag according to the instruction, read the data from the tag storage area, and send the data to the server), write operation (that is, write data to the tag.
  • the server can send a write instruction, and the reader or core network will write to the tag according to the instruction, and write data to the tag storage area), deactivation operation (that is, make the tag invalid or inactivated.
  • the server can send a deactivation instruction, and the deactivation instruction can include a tag identifier (that is, the identifier of the tag that you want to deactivate or invalidate).
  • the reader or core network will invalidate the tag according to the instruction.
  • the tag After the operation is completed, the tag will be invalidated or inactivated, and it will no longer be counted or subjected to other operations), and obtain tag information (it can be processed It is understood as a superordinate description of the above-mentioned operations (for example, a superordinate description of inventory operations and read operations), regardless of whether the server is taking inventory of tags or reading tag data.
  • This operation will obtain tag information, which can be the tag identifier or information stored in the tag storage area), and information interaction operations with tags (which can be understood as a superordinate description of the above-mentioned operations.
  • the reader After the reader receives the instruction sent by the server, it interacts with the tag for information or messages, and sends information from the tag to the server.
  • This operation is mainly for the above-mentioned reader that does not view the content of the instruction, but is only responsible for forwarding messages sent by the server to the tag and messages sent by the tag to the server. Therefore, in this scenario, the operation performed by the reader on the tag can be understood as a message interaction operation with the tag).
  • the instruction may include regional location information, tag identifier, etc.
  • the base station sends an access instruction to the tag. When the tag successfully accesses the random access, the base station sends an instruction to the tag (the base station can forward the instruction sent by the core network to the tag). The tag obtains or sends corresponding information according to the instruction.
  • the tag when the instruction is an inventory instruction or an inventory operation is performed, the tag will send the tag's identification; when the instruction is a read instruction or a read operation is performed, the tag will send the data information stored in the tag storage area; when the instruction is a write instruction or a write operation is performed, the tag will store the data information to be written to the tag included in the instruction in the tag storage area.
  • the base station sends (or forwards) the information sent by the tag to the core network; the core network sends the information to the server.
  • the core network performs access management operations on the tag based on the feedback information from the server.
  • the server sends instructions to the tag management function or the passive IoT function; in this case, the server can be an application function (AF), an application server (AS) or a passive IoT application function (P-IoT AF).
  • the P-IoT AF sends instructions to the tag management function or the passive IoT function.
  • the P-IoT AF sends instructions to the tag management function or the passive IoT function through a control plane device.
  • the control plane device can be NEF, SMF, PCF, UDM, network slice-specific and SNPN authentication and authorization function (NSSAAF), AMF.
  • the server can also send instructions to the reader through the user plane channel.
  • the server sends instructions to the base station through UPF.
  • the server sends instructions to the tag management function or the passive IoT function through the user plane device (UPF) and SMF, and the tag management function or the passive IoT function sends instructions to the tag through the RAN.
  • the server sends instructions to the reader through the user plane device and the access network device, such as RAN (when the reader is a terminal).
  • the tag management function or the passive IoT function can be co-installed or co-deployed with the core network device, the access network device or the application function. When two devices or functions are co-deployed, the interaction between the two functions or devices provided in the embodiment of the present application becomes the internal operation of the co-installed function or device or can be omitted.
  • the tag needs to perform random access (steps 1 to 4) in Figure 4A and send the EPC code to the reader after the random access is successful, so that the reader can know which tags are within its coverage. This information will eventually be reported by the reader to the middleware and server.
  • the reading and writing process is as follows:
  • Step 1 The reader receives the inventory command sent by the server (the inventory command can be sent by the server to the middleware, and then sent by the middleware to the reader), generates a Select command, which carries the tag range (such as certain specific ranges of EPC codes), and sends the Select command.
  • the tag After listening to the Select command, the tag determines whether it belongs to the tag range that needs to be judged in the Select command. If it does, it will feedback information after hearing the Query command. If it does not, it will not take any action later.
  • Step 2 The reader sends a Query command; the Query command may include a value (denoted as Q value), and the tag generates a random number based on the Q value, for example, between 0 and 2 to the power of Q. Subsequently, the tag will reduce the random number by one after the reader sends a Query or QueryRep command. When the random number is reduced to zero, the tag will initiate random access.
  • the Query command may include a value (denoted as Q value)
  • the tag generates a random number based on the Q value, for example, between 0 and 2 to the power of Q.
  • the tag will reduce the random number by one after the reader sends a Query or QueryRep command. When the random number is reduced to zero, the tag will initiate random access.
  • Step 3 When the tag finds that it belongs to the range of tags selected in the Select command, it will feedback a random number RN16 (which can be understood as a random number with a length of 16 bits) to the reader through a competitive manner (for example, by sending a random number RN16 to the reader when the random number is reduced to zero in step 2).
  • a random number RN16 which can be understood as a random number with a length of 16 bits
  • Step 4 When the reader receives the random number sent from the tag, it will send an ACK command, which contains the random number just received (RN16).
  • Step 5 When the tag receives the ACK command sent by the reader and verifies that the random number is correct, it will feedback its EPC code to the reader/writer. device, thereby completing the inventory process.
  • Steps 1 to 5 in Figure 4B are the inventory process, but the inventory process is not an inventory process for a group of tags, but an inventory of a certain tag. Starting from step 6, it is the reading and writing process, which is roughly as follows:
  • Step 6 The reader sends a Req_RN command to the tag, which carries the random number RN16 received previously.
  • Step 7 If the tag verifies that the random number is correct, it sends a handle to the reader. This handle is required in subsequent reading and writing processes.
  • Step 8 The reader sends a read or write command to the tag, which must carry a handle. If it is a write command, it must also carry the data to be written into the tag storage area.
  • Step 9 If step 8 is a read instruction, the tag needs to feedback the data in its own storage area and also carry a handle.
  • the tag deactivation process is similar to this. After receiving the deactivation instruction in step 8, the tag executes the deactivation and then optionally feedbacks the handle in step 9.
  • a tag may not have multiple frequent operations within a period of time. If it waits for multiple statistics, storage or forwarding, it cannot meet the business needs of Passive IoT. This method is not suitable for Passive IoT.
  • the execution subject of the reader becomes a base station, it is necessary to avoid the base station from sensing specific user information, whether it is tag information or tag operation information, to ensure the security of the information. Therefore, a new tag batch operation method is urgently needed to meet the needs of Passive IoT and other 5G IoT technologies, such as Massive IoT, Narrowband IoT, Critical IoT, Industrial IoT, etc.
  • the present application provides a communication method, as shown in FIG5 , which can be executed by an access network device, or by a core network device, or by interaction between an access network device, a core network device, and a service requester.
  • the access network device can be a RAN, a transmission reception point (TRP), a gNB, or a chip, etc.
  • the core network device can be an AMF, an SMF, a TMF, etc.
  • the service requester can be an AF, etc., which is not specifically limited in the present application.
  • the terminals are Tag1, Tag2, and Tag3 (only three terminals are used as an example here, but the number of terminals is not limited in actual application.
  • the tag printer Tag Printer will write Tag identifiers to Tag1, Tag2, and Tag3 in advance
  • the access network device is RAN
  • the core network device is AMF
  • the service requester is AF and NEF.
  • the reader may also be in the form of a terminal. This situation is also applicable to the solution of this application and is not specifically limited here. As described below:
  • AMF obtains the request information of the service requester, and the request information includes the identifier of the service requester (i.e., AF ID).
  • AF can send request information to AMF through NEF, or AMF can obtain request information of the service requester from other core network devices.
  • AMF1 is currently in core network 1, and AMF1 can exchange data with AMF2 in core network 2 to obtain information of a third party.
  • AMF can also query the stored request information from UDM, which is not specifically limited in this application.
  • the service requester can be understood as a user, enterprise, individual, operation requester, etc., which is not specifically limited in this application.
  • Figure 5 takes step 501, where AF sends request information to AMF through NEF so that AMF obtains the request information of the service requester as an example.
  • the request information is used as an example for explanation in this application, but in actual application, it can also be called a service request, operation request information, etc. This application does not limit the message type or message name for sending the request information.
  • the identifier of the service requester is indicated by at least one of the following information:
  • the identifier of the service requester the application function identifier corresponding to the service requester, the address information corresponding to the service requester, and the port information corresponding to the service requester.
  • the identifier of the service requester such as: the globally unique identifier information of the service requester, the globally unique identifier information of the operator, etc., or the application function identifier corresponding to the service requester, such as AF ID.
  • the address information or port information of the request information may be the port information or address information corresponding to the service requester.
  • the address information may include an IP address (such as an IPv4 address, an IPv6 address, or an IPv6 prefix) or a MAC address (media access control address);
  • the port number information may include a transmission control protocol (TCP) port number or a user datagram protocol (UDP) port number.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • Step 503 AMF determines a batch execution operation based on the request information, and performs the operation on the first terminal, where the first terminal is the terminal to be operated.
  • the core network device determines to execute the operation in batches based on the request information, which can be understood as the core network device directly determining whether to execute the operation in batches based on the specific content in the request information, and can also be understood as the core network device presets a certain judgment strategy, and after receiving the request information, retrieves the judgment strategy based on the content of the request information to determine whether to execute the operation in batches, which is not specifically limited in this application.
  • the first terminal can be understood as the contracted terminal of the service requester, for example, the service requester is enterprise A, the first terminal can be the contracted terminal of enterprise A, or the contracted terminal of enterprise A in a certain area, or the contracted terminal of enterprise A in a certain time period, etc., or it is a terminal that is connected to the service requester through a certain access method and managed by the service requester, for example, multiple cars parked in an underground parking lot, or multiple water meters in a community, etc., which are not specifically limited in this application.
  • the request information also includes at least one of the following:
  • the first geographical range where the first terminal is located the identifier of the first terminal, and the operation type indication information.
  • the first geographical range where the first terminal is located can be understood as the address information (longitude information and latitude information, coordinate value information, TAI, Cell ID, etc.) that provides services for the first terminal.
  • the first geographical range is 115 ° east longitude to 20 ° west longitude, 10 ° north latitude to 30 ° north latitude, and the first geographical range is the park of the Shanghai branch of Company A.
  • the service requester is Enterprise A
  • the first geographical range is only exemplified here, and the first geographical range is not specifically limited.
  • the identifier of the first terminal may be understood as the identifier of the terminal (such as a tag) that the service requester wishes to operate, etc., and this application does not specifically limit this.
  • the operation type indication information can be understood as indication information of operations such as inventory (also known as inventory count), reading, writing, and deactivation.
  • the specific operation type can be inventory of the terminal, reading the storage area data of the terminal, writing data to the storage area of the terminal, and deactivating the terminal, which is not specifically limited in this application.
  • the request information includes the above-mentioned multiple types, so that the core network equipment can better determine whether batch operations need to be performed and how to perform batch operations specifically.
  • AMF may determine the batch execution operation based on different situations, as follows:
  • Scenario 1 The request information only contains the ID of the service requester (AF ID)
  • AMF After receiving the request information, AMF finds that it only contains AF ID, and determines the batch execution operation based on AF ID, where the first terminal is the contracted terminal of the service requester.
  • the request information only contains the service requester ID, batch operations are directly performed on the terminals, which can reduce the steps of determining batch operations and improve data processing efficiency.
  • the request information is the identifier of the service requester (AF ID) and the first geographical scope
  • AMF After receiving the request information, AMF finds that it contains AF ID and the first geographical scope. AMF can determine that the batch execution operation is performed, and the first terminal is the contracted terminal of the service requester covered by the first geographical scope. For example, AMF receives AF1+geographical scope A and determines that the batch execution operation needs to be performed on the contracted terminals of the service requester within geographical scope A.
  • the request information includes the service requester identifier and the first geographical range
  • batch operations are directly performed on the terminal, which can reduce the steps of determining the batch operation and improve data processing efficiency.
  • the request information is the ID of the service requester (AF ID) and the ID of the first terminal
  • AMF determines the batch execution operation based on the first terminal identifier. For example, if AMF receives AF1+terminal identifier 1, since there is only one terminal identifier in the request information, the batch execution operation is not performed. If AMF receives AF1+terminal identifier 1, terminal identifier 2, terminal identifier 5, and terminal identifier 9, since there are only multiple terminal identifiers in the request information, the batch execution operation is required.
  • the request information is the business requester's identifier (AF ID) and the operation type indication information
  • the AMF After receiving the AF ID, the AMF determines the batch execution operation based on the AF ID. For example, if the AMF receives AF1 and the operation type indication information and determines that AF1 corresponds to a batch operation, then it determines that the operation corresponding to the operation type indication information needs to be performed on the contracted terminal of the service requester corresponding to AF1. If AF2 does not correspond to a batch operation in the operation rule, then it determines that there is no need to perform the operation on the contracted terminal of the service requester corresponding to AF2.
  • the request information is the identifier of the service requester (AF ID), the first geographical scope, and the identifier of the first terminal
  • the request information is the identifier of the service requester (AF ID)
  • the first geographical scope and the identifier of the first terminal if the number of identifiers of the first terminal is greater than 1, the AMF determines the execution batch operation based on the identifier of the first terminal.
  • the request information is the identifier of the service requester (AF ID), the first geographical scope, and the operation type indication information
  • the AMF can determine the batch execution of the operation of the corresponding operation type indication information according to the first geographical scope.
  • Table 1 takes the address of the access network device RAN that provides services to the first terminal in the first geographical scope as an example to illustrate that the deactivation operation is performed on the contracted terminal whose address is AF1 governed by longitude A1 and latitude B1, and the write operation is performed on the contracted terminal whose address is AF2 governed by longitude A2 and latitude B2.
  • the AMF can also obtain the address of the access network device that provides services to the first terminal through the LMF. This application does not specifically limit how to obtain the address of the access network device that provides services to the first terminal.
  • the request information includes the identifier of the service requester, the first geographical range of the first terminal and the operation type indication information, batch operations are directly performed on the terminals, which can reduce the steps of determining batch operations and improve data processing efficiency.
  • the request information is the identifier of the service requester (AF ID), the identifier of the first terminal, and the operation type indication information corresponding to the first terminal, and the same operation type indication information corresponds to the identifiers of multiple terminals in the first terminal
  • AMF determines to perform the operation in batches. For example, if AMF receives AF1+terminal identifier 1+inventory, terminal identifier 2+read data, terminal identifier 3+write data, terminal identifier 5+deactivate, since the operation types corresponding to the terminal identifiers are different, the operation will not be performed in batches.
  • AMF receives AF1+terminal identifier 1+inventory, terminal identifier 2+inventory, terminal identifier 5+read data, terminal identifier 9+write data, since there are only multiple terminal identifiers in the request information, and there are at least 2 terminal identifiers corresponding to different operation types, the operation needs to be performed in batches.
  • Table 2 takes the first terminal as the contracted terminal of the service requester as an example.
  • An inventory operation is performed on the contracted terminals of AF1 whose terminal identifiers are greater than 100 or less than 200, and a deactivation operation is performed on the contracted terminals of AF1 whose terminal identifiers are less than 50.
  • the terminal identification range in the request information includes the terminal identifications of other enterprises (such as AF2).
  • the core network device queries the identification list of the contracted terminals of the service requester in the pre-stored or contracted data of the core network device according to the identification of the service requester, and selects the intersection of the terminal identification range in the request information and the identification list as the first terminal identification.
  • an inventory operation is performed on the terminals whose terminal identifications are 00000000 and 00000001 which are contracted terminals of AF 1
  • a deactivation operation is performed on the terminal whose terminal identification is 00000010 which is contracted terminals of AF 1
  • a read operation is performed on the terminal whose terminal identification is 00000011 which is contracted terminals of AF1.
  • the request information is the identifier of the service requester (AF ID), the first geographical scope, the identifier of the first terminal, and the operation type indication information
  • the request information includes the identifier of the service requester (AF ID), the second geographical scope, the identifier of the first terminal and the operation type indication information, if the number of identifiers of the first terminal is greater than 1, and the same operation type indication information corresponds to the identifiers of multiple terminals in multiple first terminals, AMF determines to execute the operation in batches.
  • AF ID the identifier of the service requester
  • the second geographical scope the identifier of the first terminal
  • the operation type indication information if the number of identifiers of the first terminal is greater than 1, and the same operation type indication information corresponds to the identifiers of multiple terminals in multiple first terminals, AMF determines to execute the operation in batches.
  • an inventory operation is performed on the terminals identified as 00000000 and 00000001 of the first end governed by longitude A1 and latitude B1.
  • AMF can determine whether it is necessary to perform the same operation on the first terminal based on Tables 1 to 4 above, that is, batch management. As shown in Table 1 above, AMF can batch perform inventory operations on terminals >100& ⁇ 200, and batch perform inactivation operations on terminals ⁇ 50; as shown in Table 3 above, AMF can batch perform inventory operations on terminals corresponding to 0000 0000 and 0000 0001.
  • the request information may be any one of the above 8 situations.
  • the core network equipment can flexibly determine the judgment operation of batch execution operation according to the needs, and this application does not specifically limit it here.
  • All of the above are requests that implicitly include instructions for batch operations, that is, the need for batch operations is determined based on special information content, that is, whether to perform batch operations is directly determined based on the content of the request information.
  • whether to perform batch operations can also be indicated in other ways. For example, when AMF receives the identification information of the service requester, it queries the judgment policy preset by AMF or the contract data in UDM/UDR, and determines that AF1 corresponds to the batch operation based on the judgment policy or the contract data. It is determined that the batch operation needs to be performed on the contracted terminals of the service requester corresponding to AF1. If AF2 does not correspond to the batch operation in the operation rules, it is determined that the batch operation does not need to be performed on the contracted terminals of the service requester corresponding to AF2.
  • AMF obtains the contract data of the service requester according to the identifier of the service requester, and the contract data includes: the correspondence between the service requester and the operation type, and the correspondence between the service requester and the second geographical scope; AMF performs operations of the corresponding operation type on multiple terminals (i.e., the first terminal) covered by the second geographical scope according to the contract data.
  • the contract data includes inventory, longitude A1 to longitude B1, and latitude X1 to latitude Y1. Then AMF can determine the need to perform an inventory operation on multiple terminals under longitude A1 to longitude B1 and latitude X1 to latitude Y1 based on the contract data.
  • the contract data includes read data, longitude A2 to longitude B2, and latitude X2 to latitude Y2. Then AMF can determine the need to perform a read data operation on multiple terminals under longitude A2 to longitude B2 and latitude X2 to latitude Y2 based on the contract data.
  • AMF only needs to query the contract data to obtain the operation type information, and perform operations of the corresponding operation type on multiple terminals covered by the first geographical scope, where the first terminal is the contracted terminal of the service requester covered by the second geographical scope.
  • the request information includes a first geographical scope
  • the second geographical scope queried by the core network device based on the contract data of the service requester is different from the first geographical scope
  • the first terminal is a terminal covered by the intersection of the second geographical scope and the first geographical scope, or a terminal covered by the smaller geographical scope between the first geographical scope and the second geographical scope.
  • the request information includes: operation type indication information
  • the operation type of the batch execution operation is determined according to the operation type indication information without querying the contract data.
  • the request information may also include the device type of the terminal (passive, semi-passive, semi-active, active) so that when different types of first terminals use the same identifier, it can distinguish which first terminal is to be managed, and notify the AMF to take different operations for different types of devices, such as receiving different NAS message types.
  • Step 504 After the AMF determines that multiple terminals in the first terminal have completed the operation, it sends the operation information of the multiple terminals to the service requester.
  • Tag1 and Tag2 have performed operations (that is, they are the first terminals) based on the contract data of the service requester and are the contracted terminals of the service requester, the operation information of Tag1 and Tag2 will be sent to the service requester.
  • Tag3 may also perform operations, but Tag3 is not the first terminal, so there is no need to send the operation information of Tag3 to the service requester.
  • the request information includes the first geographical range but does not include the identifier of the first terminal
  • the terminals are Tag1, Tag2, and Tag3 (only three terminals are used as an example here, but the number of terminals is not limited in actual application.
  • the label printer Tag Printer will write Tag identifiers to Tag1, Tag2, and Tag3 in advance)
  • the access network equipment is RAN
  • the core network equipment is AMF
  • the service requesters are AF and NEF.
  • there may be multiple service requesters, and there may be multiple core network devices serving a certain service requester for example, enterprise A is distributed in different regions, and the core network device serving the terminals in region 1 of enterprise A is AMF1, and the core network device serving the terminals in region 2 of enterprise A is AMF2) and access network devices.
  • AMF1 the core network device serving the terminals in region 1 of enterprise A
  • AMF2 the core network device serving the terminals in region 2 of enterprise A is AMF2
  • Step 601 AF sends a request message to AMF through NEF, where the request message includes the identifier of the service requester and the first geographical scope.
  • Step 602 The AMF determines a batch execution operation based on the request information, and performs the operation on the first terminal.
  • step 503 may be referred to to understand how to determine the batch execution operation, and specifically how to determine the first terminal and the operation type of the batch operation, which will not be described in detail here.
  • the following steps 603 to 608B specifically describe how to perform operations on the first terminal.
  • Step 603 AMF determines a first message, where the first message includes: an operation instruction and an indication identifier.
  • the operation instruction triggers RAN to trigger multiple random access processes.
  • the operation instruction is determined according to the operation type, and the indication identifier is associated with the identifier of the service requester.
  • the operation instruction instructs any terminal to perform random access of the next first terminal after reaching a preset number of transparent transmission times with the access network device. For example, if the operation type is inventory, then the operation instruction instructs the RAN and the terminal to perform a transparent transmission operation once before performing an inventory of the next terminal, wherein one transparent transmission can be understood as step 5 in the above-mentioned FIG4A; if the operation type of batch management is read, write, and deactivate, then the operation instruction instructs the RAN and the terminal to perform three transparent transmission operations before performing reading, writing, and deactivation of the next terminal, wherein three transparent transmissions can be understood as steps 7 to 9 in the above-mentioned FIG4B.
  • the access network device reports the terminal operation information to the core network device, it enters the next random access without waiting for the core network device to perform the next random access instruction. This method can improve data efficiency and reduce interactive signaling.
  • the indication identifier can be understood as an NGAP identifier.
  • the NGAP identifier is different from the existing NGAP identifier.
  • the NGAP identifier is associated with the identifier of the service requester.
  • the indication identifier may be used to filter the terminal identifier reported by the terminal in subsequent steps, so as to report the operation information of the first terminal to the service requester. For a specific description, please refer to the description of 608A and 608B below.
  • the first message may also include operation mode indication information, such as: when the operation mode indication information is 1, the corresponding operation is inventory; when the operation mode indication information is 3, the corresponding operation is read, etc.
  • operation mode indication information such as: when the operation mode indication information is 1, the corresponding operation is inventory; when the operation mode indication information is 3, the corresponding operation is read, etc.
  • Step 604 The AMF sends a first message to the RAN serving the first terminal.
  • the RAN is also the RAN that serves the contracted terminal of the service requester in the first geographical scope.
  • the RAN may serve the terminals of multiple service requesters.
  • Step 605 AMF instructs RAN to perform random access procedures for terminals under RAN one by one according to the operation instruction.
  • Step 606A Tag1 reports the identifier of Tag1 to the RAN.
  • Step 606B Tag2 reports the identifier of Tag2 to the RAN.
  • Step 606C Tag3 reports the identifier of Tag3 to the RAN.
  • each access to the AMF is a re-registration process, so the Tag identifier can be sent via the Registration request message, and the Tag registration message is also required to be carried; when the Tag is a semi-passive device, since some of the previously registered information is retained when accessing the AMF, the Tag identifier can be sent via the NAS transport message.
  • RAN may only perform transparent transmission and forwarding.
  • the Tag performs an inventory operation
  • random access may be performed on the next Tag to receive the identifier reported by the next Tag.
  • the random access process is performed to perform the operation of step 606B.
  • Tag2 performs a transparent transmission
  • random access is performed to perform the operation of step 606C.
  • the random access process is performed to receive the identifier reported by the next Tag. For example, when performing an inventory operation, after determining that Tag1 performs three transparent transmissions in step 606A, the operation of step 606B is performed. After Tag2 performs three transparent transmissions, the operation of step 606C is performed.
  • RAN can also cache the tag identifier, and after determining that all tags have completed access (such as reaching the operation time threshold), report the cached identifier to AMF. It should be noted that RAN does not perceive the specific information of the tag, and the tag identifier information transmitted after the random access process is not fixed in a certain order. This is just an example.
  • Another possible situation is that the operation information of the terminal is temporarily stored on the RAN.
  • the AMF or RAN determines that the operation life cycle of the terminal has ended, the RAN sends the operation information of the terminal to the AMF.
  • Step 607 RAN sends a second message to AMF, where the second message includes the identifier of the second terminal (ie, the identifier of Tag1, the identifier of Tag2, and the identifier of Tag3) and an indication identifier.
  • the second message includes the identifier of the second terminal (ie, the identifier of Tag1, the identifier of Tag2, and the identifier of Tag3) and an indication identifier.
  • the RAN may generate other indication identifiers according to the indication identifier, and the RAN may send a second message to the AMF, wherein the second message also includes other indication identifiers.
  • the AMF may determine the identifier of the service requester according to the association relationship between the other indication identifier and the indication identifier.
  • Step 608A when the operation type is inventory, the AMF determines that the second terminal is one of the first terminals according to the indication identifier, and then caches the identifier of the second terminal (which belongs to the first terminal and is a contracted terminal of the service requester).
  • Step 608B when the operation type is read, write or deactivate, the AMF determines that the second terminal is one of the first terminals based on the indication identifier, and then sends read, write or deactivate instruction information to the second terminal through the access network device to obtain the operation information of the second terminal and cache it.
  • the RAN is instructed to perform random access to the next Tag.
  • the AMF queries the identification list of the contracted terminals of the service requester pre-stored in the core network device according to the indication identifier (or other indication identifier), and when the AMF determines that the identification list includes the identification of the second terminal, it determines that the second terminal is one of the first terminals.
  • the list of identifiers of the contracted terminals corresponding to the indication identifiers is shown in Table 6 below, wherein the terminal identifiers corresponding to NGAP1 include: the identifier of Tag1 of AF1, the identifier of Tag2 of AF1; the terminal identifiers corresponding to NGAP2 include: the identifier of Tag4 of AF2, the identifier of Tag5 of AF2.
  • Table 6 the list of identifiers of the contracted terminals corresponding to the indication identifiers is shown in Table 6 below, wherein the terminal identifiers corresponding to NGAP1 include: the identifier of Tag1 of AF1, the identifier of Tag2 of AF1; the terminal identifiers corresponding to NGAP2 include: the identifier of Tag4 of AF2, the identifier of Tag5 of AF2.
  • Table 6 the terminal identifiers corresponding to NGAP1 include: the identifier of Tag1 of AF1, the identifier of Tag2 of AF
  • step 608A if the indication identifier is NGAP1, by querying Table 6, it can be known that the identifier of the contracted terminal of the service requester is the identifier of Tag1 and the identifier of Tag2. Then when the second terminal is Tag1 and Tag2, AMF caches the identifier of Tag1 and the identifier of Tag2.
  • step 608B if the indication identifier is NGAP1, by querying Table 6, it can be known that the identifier of the contracted terminal of the service requester is the identifier of Tag1 and the identifier of Tag2, and when the second terminal is Tag1 and Tag2, AMF sends read, write or deactivate instruction information to Tag1 and Tag2 to obtain the operation information of Tag1 and Tag2 and cache it.
  • This is only an exemplary description and is not specifically limited.
  • the operation information when the operation type is inventory, the operation information includes: the identifier of the first terminal that successfully inventoried; when the operation type is read, the operation information includes: the identifier of the first terminal that successfully read and the read data.
  • the core network device can also send operation information of terminals that have not completed operations to the service requester.
  • the operation information of the terminal that has completed the operation and the operation information of the terminal that has not completed the operation can be sent together or separately, and this application does not specifically limit this.
  • the operation information includes the identifier of the first terminal that has successfully been inventoried, which is the identifier of Tag1 and the identifier of Tag2, and the identifier of the first terminal that has failed to be inventoried is the identifier of Tag3.
  • the operation information includes the identifier of the first terminal that has successfully been read, which is the identifier of Tag1 and the identifier of Tag2, and the identifier of the first terminal that has failed to be read is the identifier of Tag3.
  • the identifier of the first terminal that failed to write may not feedback information, only the identifier of the first terminal that successfully wrote feedback information, or no feedback on the result of writing.
  • the operation type is deactivation
  • the identifier of the first terminal that successfully deactivated may not be able to interact with AMF, so no feedback is given, and the identifier of the first terminal that failed to deactivate may be able to interact with AMF, so information is fed back.
  • Another possibility is that no feedback on the result of deactivation is given. This application is not specifically limited here.
  • Step 609 AMF determines that multiple terminals in the first terminal have completed the operation.
  • step 609A it can be determined through step 609A.
  • step 609A the AMF determines that the operation time threshold has been reached, and then determines that multiple terminals in the first terminal have completed the operation.
  • the first message also includes: an operation time threshold; it can be determined through steps 609B to 609C.
  • step 609B the AMF receives a third message from the RAN, and the third message is used to indicate that the operation time threshold has been reached; in step 609C, the AMF determines that multiple terminals in the first terminal have completed the operation according to the third message.
  • Step 610 AMF sends a fourth message to RAN, where the fourth message instructs RAN to end the random access procedure.
  • step 610 is an optional step, and in actual application, the AMF may choose to perform it.
  • the RAN may also determine that the operation time threshold has been reached and end the random access process, which is not specifically limited in this application.
  • Step 611 AMF sends operation information of multiple terminals in the first terminal to AF.
  • AMF can execute the operation process for the next batch of terminals.
  • the present application provides a batch operation method in the business scenario of enterprise regional inventory, which includes triggering conditions for batch operation, a method for determining whether a random access tag meets the requirements, a base station transparent transmission method, etc., which saves signaling overhead and terminal response time, and saves terminal energy.
  • Case 2 The request information includes the identifier of the first terminal but does not include the first geographical scope
  • the terminals are Tag1, Tag2, and Tag3 (only three terminals are used as an example here, but the number of terminals is not limited in actual application.
  • the label printer Tag Printer will write Tag identifiers to Tag1, Tag2, and Tag3 in advance)
  • the access network device is RAN
  • the core network device is AMF
  • the service requester is AF and NEF.
  • there may be multiple service requesters, and there may be multiple core network devices serving a service requester for example, enterprise A is distributed in different regions, and the core network device serving the terminals in region 1 of enterprise A is AMF1, and the core network device serving the terminals in region 2 of enterprise A is AMF2) and access network devices.
  • AMF1 the core network device serving the terminals in region 1 of enterprise A
  • AMF2 the core network device serving the terminals in region 2 of enterprise A is AMF2
  • Step 701 AF sends a request message to AMF through NEF, where the request message includes an identifier of the service requester and an identifier of the first terminal.
  • Step 702 The AMF determines a batch execution operation based on the request information, and executes the operation on the first terminal.
  • step 503 may be referred to to understand how to determine the batch execution operation, and specifically how to determine the first terminal and the operation type of the batch operation, which will not be described in detail here.
  • the following steps 703 to 708B specifically describe how to perform operations on the first terminal.
  • Step 703 AMF determines a first message, the first message includes: an operation instruction, an X group mask range, X ⁇ 1, the operation instruction triggers RAN to trigger multiple random access processes, and the operation instruction is determined according to the operation type.
  • the operation instructions may be understood by referring to the above step 603 and will not be described in detail here.
  • Each group of mask ranges corresponds to the identifier of the first terminal that performs the same type of operation.
  • the mask range is mainly to prevent the RAN from directly identifying the identifier of the terminal to ensure the security of information interaction.
  • the RAN can be instructed to perform operations on tags within a certain range in subsequent operations.
  • the mask range is determined according to the identifier of the first terminal. For example, the mask range corresponding to the identifier of the terminal >100& ⁇ 200 in Table 2 is 0000 0XXX, and another group of mask ranges 0000 00XX is constructed for the identifier of the terminal ⁇ 50 in Table 2. This is only for example.
  • the AMF determines the mask range, in subsequent steps, if the identifier of the first terminal currently performing random access is the identifier of the last first terminal corresponding to the mask range of the Xth group, the AMF determines that the first terminals have completed the batch operation.
  • Step 704 The AMF sends a first message to the RAN serving the first terminal.
  • Step 705 AMF instructs RAN to perform random access procedures for terminals within the mask range of group X one by one according to the operation instruction.
  • Step 706A Tag1 reports the identifier of Tag1 to the RAN.
  • Step 706B Tag2 reports the identifier of Tag2 to the RAN.
  • Step 706C Tag3 reports the identifier of Tag3 to the RAN.
  • RAN may only perform transparent transmission and forwarding.
  • the Tag performs an inventory operation
  • random access may be performed on the next Tag to receive the identifier reported by the next Tag.
  • the random access process is performed to perform the operation of step 706B.
  • Tag2 performs a transparent transmission
  • random access is performed to perform the operation of step 706C.
  • a random access process is performed to receive the identifier reported by the next Tag. For example, when performing an inventory operation, after determining that Tag1 performs three transparent transmissions in step 706A, the operation of step 706B is performed. After Tag2 performs three transparent transmissions, the operation of step 706C is performed. RAN can also cache the tag identifier, and after determining that all tags have completed access (such as reaching the operation time threshold), report the cached identifier to AMF. It should be noted that RAN does not perceive the specific information of the tag, and the tag identifier information transmitted after the random access process is not fixed in a certain order. This is just an example.
  • Another possible situation is that the operation information of the terminal is temporarily stored on the RAN.
  • the AMF or RAN determines that the operation life cycle of the terminal has ended, the RAN sends the operation information of the terminal to the AMF.
  • Step 707 RAN sends a second message to AMF, where the second message includes the identifier of the second terminal (ie, the identifier of Tag1, the identifier of Tag2, and the identifier of Tag3).
  • Step 708A When the operation type is inventory, the AMF determines that the second terminal is one of the first terminals, and then caches the identifier of the second terminal.
  • Step 708B when the operation type is read, write or deactivate, the AMF determines that the second terminal is one of the first terminals, and then sends read, write or deactivate instruction information to the second terminal through the access network device to obtain the operation information of the second terminal and cache it.
  • the RAN is instructed to perform random access to the next Tag.
  • steps 708A and 708B can be selected and executed according to the actual operation type, and this application does not specifically limit it here. Specifically, if the identifier of the first terminal includes the identifier of Tag1, the identifier of Tag2, the identifier of Tag4, the identifier of Tag5, and the identifier of Tag6. The identifier of Tag1 and the identifier of Tag2 belong to the identifier of the first terminal, then in step 708A, the identifier of Tag1 and the identifier of Tag2 are cached, and in step 708B, read, write or inactivate instruction information is sent to the identifier of Tag1 and the identifier of Tag2 to obtain the operation information of the second terminal and cache it.
  • operation information may be understood by referring to the description of 608A and 608B above, which will not be repeated here.
  • Step 709 AMF determines that multiple terminals in the second terminal have completed the operation.
  • step 709A it can be determined by step 709A.
  • AMF determines that the operation life cycle has been reached, and then determines that there are multiple terminals in the second terminal that have performed batch operations.
  • the operation life cycle includes at least one of the following: operation number threshold, operation time threshold, and X group mask range.
  • the operation time threshold is T1
  • the batch management operation is performed within T1 time, and the batch management operation is not performed if the time exceeds T1
  • the operation number threshold is Y times (mainly based on the operation number threshold determined by the mask range, such as the label corresponding to the mask range is 10, then the operation number threshold can be set to 10), and the batch management operation is performed within Y times, and the batch management operation is not performed if the number exceeds Y.
  • the identifier of the first terminal currently performing random access is the identifier of the last first terminal corresponding to the mask range of the Xth group, and the AMF determines that the first terminals have completed the operation.
  • the first message further includes at least one of the following: an operation number threshold, an operation time threshold; which can be determined through steps 709B to 709C.
  • the AMF receives a third message from the RAN, and the third message is used to indicate that the operation number threshold and/or the operation time threshold have been reached.
  • the AMF determines, based on the third message, that multiple terminals in the first terminal have completed the operation.
  • Step 710 AMF sends a fourth message to RAN, where the fourth message instructs RAN to end the random access procedure.
  • Step 710 is an optional step.
  • AMF can choose to perform it, or RAN can terminate the random access by itself.
  • the application does not specifically limit the process.
  • Step 711 AMF sends operation information of multiple terminals in the first terminal to AF.
  • AMF can execute the batch operation process for the next batch of terminals.
  • the present application can realize batch operations on multiple terminals instead of performing the same operation on only one terminal, and can realize batch management of terminals. Moreover, the terminal does not report the operation information immediately after completing a random access, but reports the operation information after the terminal corresponding to the service requester completes the random access. In this way, the operation signaling can be reduced and the data processing efficiency can be improved.
  • each device may include a hardware structure and/or software module corresponding to each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application can divide the functional units of the device according to the above method example.
  • each functional unit can be divided according to each function, or two or more functions can be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software functional unit.
  • FIG8 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application.
  • the communication device 800 may include: a processing unit 801 and a transceiver unit 802.
  • the processing unit 801 is used to control and manage the actions of the communication device 800.
  • the transceiver unit 802 is used to support the communication of the communication device 800 with other devices.
  • the transceiver unit 802 may include a receiving unit and/or a sending unit, which are respectively used to perform receiving and sending operations.
  • the communication device 800 may also include a storage unit for storing program code and/or data of the communication device 800.
  • the transceiver unit may be referred to as an input-output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor.
  • the communication device is a module (such as a chip) in a communication device
  • the transceiver unit may be an input-output interface, an input-output circuit or an input-output pin, etc., and may also be referred to as an interface, a communication interface or an interface circuit, etc.
  • the processing unit may be a processor, a processing circuit or a logic circuit, etc.
  • the device may be the above-mentioned access network device, the first core network device, etc.
  • the transceiver unit 802 is used to obtain request information from a service requester, where the request information includes an identifier of the service requester; the processing unit 801 is used to determine a batch execution operation based on the request information, and to perform the operation on a first terminal; after the processing unit 801 determines that multiple terminals in the first terminal have completed the operation, the transceiver unit 802 sends operation information of multiple terminals to the service requester, where the first terminal is the terminal to be operated.
  • the request information further includes at least one of the following:
  • the first geographical range where the first terminal is located the identifier of the first terminal, and the operation type indication information.
  • the processing unit 801 determines a batch execution operation, and the first terminal is a contracted terminal of the service requester.
  • the processing unit 801 determines a batch execution operation, and the first terminal is a contracted terminal of the service requester covered by the first geographical scope.
  • the processing unit 801 determines to execute the operation in batches.
  • the processing unit 801 determines to execute the operation in batches.
  • the request information is an identifier of the service requester
  • the processing unit 801 obtains the contract data of the service requester according to the identifier of the service requester, where the contract data includes: a correspondence between the service requester and the operation type, and a correspondence between the service requester and the second geographical scope; and performs batch operations of the corresponding operation type on multiple terminals covered by the second geographical scope according to the contract data.
  • the request information further includes: operation type indication information
  • the operation type of the batch operation is determined according to the operation type indication information.
  • the transceiver unit 802 is used to send a first message to an access network device serving the first terminal, the first message including: an operation instruction and an indication identifier, the operation instruction triggers the access network device to trigger multiple random access processes, the operation instruction is determined according to the operation type, and the indication identifier is associated with the identifier of the service requester; the processing unit 801 instructs the access network device to perform a random access operation according to the operation instruction.
  • a random access process is performed on the terminals under the access network device one by one; the transceiver unit 802 receives a second message from the access network device, the second message including: an identifier and an indication identifier of the second terminal; when the operation type is inventory, the processing unit 801 determines that the second terminal is one of the first terminals according to the indication identifier, and then caches the identifier of the second terminal; or, when the operation type is read, write or deactivate, the processing unit 801 determines that the second terminal is one of the first terminals according to the indication identifier, and then sends read, write or deactivate instruction information to the second terminal through the access network device to obtain operation information of the second terminal and cache it.
  • the processing unit 801 is used to query the identification list of the subscribed terminals of the service requesting party pre-stored in the core network device according to the first indication identifier; when it is determined that the identification list includes the identification of the second terminal, it is determined that the second terminal is one of the first terminals.
  • a transceiver unit 802 is used to send a first message to an access network device serving a first terminal, the first message including: an operation instruction, an X-group mask range, X ⁇ 1, the operation instruction triggers the access network device to trigger multiple random access processes, and the operation instruction is determined according to the operation type; a processing unit 801 instructs the access network device to execute random access processes for terminals under the X-group mask range one by one according to the operation instruction; the transceiver unit 802 receives a second message from the access network device, the second message including: an identifier of the second terminal; when the operation type is inventory, the processing unit 801 determines that the second terminal is one of the first terminals, and caches the identifier of the second terminal; or, when the operation type is read, write or deactivate, the processing unit 801 determines that the second terminal is one of the first terminals, and sends read, write or deactivate instruction information to the second terminal through the access network device to obtain operation information of the second terminal and
  • the processing unit 801 is configured to determine that when the operation time threshold is reached, it is determined that multiple terminals in the first terminal have completed the operation.
  • the first message also includes: an operation time threshold; a transceiver unit 802, used to receive a third message from an access network device, the third message being used to indicate that the operation time threshold has been reached; and a processing unit 801, used to determine, based on the third message, that multiple terminals in the second terminal have completed the operation.
  • the processing unit 801 is used to determine that the operation life cycle has been reached, and then determine that multiple terminals in the second terminal have completed the operation; the operation life cycle includes at least one of the following: an operation number threshold, and an X-group mask range.
  • the first message also includes at least one of the following: an operation number threshold, an operation time threshold; a transceiver unit 802 is used to receive a third message from an access network device, the third message is used to indicate that the operation number threshold and/or the operation time threshold have been reached; a processing unit 801 is used to determine, based on the third message, that multiple terminals in the second terminal have performed batch operations.
  • the transceiver unit 802 is configured to send a fourth message to the access network device, where the fourth message instructs the access network device to end the random access process.
  • the operation information when the operation type is inventory, includes: an identifier of the first terminal that successfully inventories; or, when the operation type is read, the operation information includes: an identifier of the first terminal that successfully reads and the read data.
  • the transceiver unit 802 is used to receive a first message from a core network device, the first message includes an operation instruction and an indication identifier, the operation instruction triggers the access network device to trigger multiple random access processes, the operation instruction is determined according to the operation type, and the indication identifier is associated with the identifier of the service requester; the processing unit 801 is used to execute the random access process for the terminals under the access network device one by one according to the operation instruction.
  • the transceiver unit 802 is used to receive an identifier of a second terminal from the second terminal; and send a second message to the core network device, where the second message also includes: an identifier of the second terminal and an indication identifier.
  • the first message also includes: an operation time threshold, and the transceiver unit 802 is used to send a third message to the core network device, and the third message is used to indicate that the operation time threshold has been reached.
  • the transceiver unit 802 is used to receive a fourth message from the core network device, where the fourth message instructs the access network device to end the random access process.
  • the transceiver unit 802 is used to receive a first message from a core network device, where the first message includes an operation instruction and an X group mask range, where X ⁇ 1, and the operation instruction triggers the access network device to trigger multiple random access procedures, and the operation instruction is determined according to the operation type; the processing unit 801 is used to execute the random access procedure for the terminals under the X group mask range one by one according to the operation instruction.
  • the transceiver unit 802 is configured to receive an identifier of a second terminal from the second terminal; and send a second message to the core network device, where the second message further includes: the identifier of the second terminal.
  • the first message also includes at least one of the following: an operation time threshold, an operation time threshold, and the transceiver unit 802 is used to send a third message to the core network device, and the third message is used to indicate that the operation time threshold has been reached.
  • the transceiver unit 802 is used to receive a fourth message from the core network device, where the fourth message instructs the access network device to end the random access process.
  • a communication device 900 is also provided in the present application.
  • the communication device 900 may be a chip or a chip system.
  • the communication device may be located in a device involved in any of the above method embodiments, such as an access network device, or a first core network device, etc., to perform actions corresponding to the device.
  • the chip system may consist of the chip, or may include the chip and other discrete devices.
  • the communication device 900 includes a processor 910 .
  • the processor 910 is used to execute the computer program stored in the memory 920 to implement the actions of each device in any of the above method embodiments.
  • the communication device 900 may further include a memory 920 for storing computer programs.
  • the memory 920 is coupled to the processor 910. Coupling is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, for information exchange between devices, units or modules.
  • the memory 920 is integrated with the processor 910.
  • the processor 910 and the memory 920 may be one or more and are not limited.
  • the communication device 900 may include a transceiver 930 or may not include the transceiver 930, which is illustrated by a dotted box in the figure, and the communication device 900 may exchange information with other devices through the transceiver 930.
  • the transceiver 930 may be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.
  • the communication device 900 may be an access network device or a first core network device in the implementation of the above methods.
  • the specific connection medium between the above-mentioned transceiver 930, the processor 910 and the memory 920 is not limited.
  • the memory 920, the processor 910 and the transceiver 930 are connected by a bus in FIG. 9, and the bus is represented by a thick line in FIG. 9.
  • the connection mode between other components is only for schematic illustration and is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present application.
  • the general-purpose processor can be a microprocessor or any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor can be executed.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM).
  • the memory may also be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiments of the present application may also be a circuit or any other device that can implement a storage function, for storing computer programs, program instructions and/or data.
  • the embodiment of the present application also provides another communication device 1000, including: an interface circuit 1010 and a logic circuit 1020; the interface circuit 1010 can be understood as an input-output interface, which can be used to execute the receiving and sending steps of each device in any of the above method embodiments, and the logic circuit 1020 can be used to run codes or instructions to execute the method executed by each device in any of the above embodiments, which will not be repeated.
  • the embodiments of the present application further provide a computer-readable storage medium, which stores instructions.
  • the computer-readable storage medium may include: a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.
  • an embodiment of the present application provides a communication system, which includes the access network equipment (such as RAN) and core network equipment (such as AMF) mentioned in any of the above method embodiments, and can be used to execute the method executed by each device in any of the above method embodiments.
  • access network equipment such as RAN
  • core network equipment such as AMF
  • the above-mentioned communication system may also include a terminal (such as UE), which can execute the relevant method in any of the above-mentioned method embodiments by interacting with the access network device and the core network device.
  • a terminal such as UE
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法及装置，涉及通信技术领域。核心网设备获取业务请求方的请求信息，请求信息包括业务请求方的标识；核心网设备基于请求信息确定批量执行操作，并对第一终端执行操作；核心网设备确定第一终端中已有多个终端完成批量操作后，发送多个终端的操作信息至业务请求方。通过该方法批量执行操作可以减少信令交互，提高处理效率。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年09月27日提交中国专利局、申请号为202211185417.0、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在无线射频识别技术(radio frequency identification，RFID)中，RFID针对单个标签的多次操作统计后，批量存储或转发。但是，这种对单个标签的批量处理并不能满足、无源物联网(passive IoT，P-IoT；或者称为ambient ioT，A-IoT)中的业务需求，该方法不适用于Passive IoT，因此亟需一种新的标签批量操作方法，以适用于Passive IoT的需求。
发明内容
本申请提供一种通信方法及装置，以在第三代合作伙伴计划(third generation partnership project，3GPP)系统中适配批量操作的需求，减少信令交互，提高数据处理效率。
第一方面，本申请提供一种通信方法，包括：
核心网设备获取业务请求方的请求信息，请求信息包括业务请求方的标识；核心网设备基于请求信息确定批量执行操作，并对第一终端执行操作；核心网设备确定第一终端中已有多个终端完成操作后，发送多个终端的操作信息至业务请求方，第一终端为待操作的终端。
本申请，通过核心网设备识别待批量操作的终端，可实现对多个终端的批量操作，而非仅针对一个终端执行同样的操作，通过该方式可以减少操作信令的交互，提高数据处理效率。其中，第一终端的数量以及多个终端的数量根据实际场景而有不同，且在实际应用时，第一终端可以理解为业务请求方的签约终端，或者是通过某种接入方式接入到业务请求方，并通过业务请求方管理的终端，本申请在此不具体限定。此外，核心网设备基于请求信息确定批量执行操作，可以理解为核心网设备直接基于请求信息中的具体内容确定是否批量执行操作，还可以理解为核心网设备预设某种判断策略，在收到请求信息后，基于请求信息的内容检索判断策略，确定是否批量执行操作，本申请在此不具体限定。
在一种可选的方式中，请求信息还包括以下中的至少一种：
第一终端所处的第一地理范围、第一终端的标识、操作类型指示信息。
本申请中，请求信息包括上述的多种类型，便于核心网设备可以更好地确定是否需要批量执行操作以及具体如何批量执行操作。
在一种可选的方式中，请求信息为业务请求方的标识时，核心网设备确定批量执行操作，第一终端为业务请求方的签约终端。
本申请中，在请求信息仅包含业务请求方标识时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
在一种可选的方式中，请求信息为业务请求方的标识及第一地理范围时，核心网设备确定批量执行操作，第一终端为第一地理范围覆盖下的业务请求方的签约终端。
本申请中，在请求信息包含业务请求方标识及第一地理范围时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。此外，请求信息包括第一地理范围时，且核心网设备根据业务请求方的签约数据查询的第二地理范围与第一地理范围不同时，第一终端为第二地理范围与第一地理范围的交集覆盖下的终端。
在一种可选的方式中，请求信息为业务请求方的标识以及第一终端的标识时，若第一终端的标识数量大于1，核心网设备确定批量执行操作。
在一种可选的方式中，请求信息为业务请求方的标识、第一终端的标识以及与第一终端对应的操作类型指示信息，且相同的操作类型指示信息对应第一终端中的多个终端的标识时，核心网设备确定批量执行操作。
本申请中，在请求信息包含业务请求方的标识、第一终端的标识以及与第一终端对应的操作类型指示信息，且相同的操作类型指示信息对应第一终端中的多个终端的标识时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
在一种可选的方式中，请求信息为业务请求方的标识、第一终端所处的第一地理范围及操作类型指示信息时，核心网设备确定批量执行操作。
本申请中，在请求信息包含业务请求方的标识、第一终端所处的第一地理范围及操作类型指示信息时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
在一种可选的方式中，请求信息为业务请求方的标识，核心网设备根据业务请求方的标识获取业务请求方的签约数据，签约数据包括：业务请求方与操作类型的对应关系、业务请求方与第二地理范围的对应关系；核心网设备根据签约数据对第二地理范围覆盖下的多个终端执行相应操作类型的批量操作。
本申请中，在请求信息中没有明确指示地理位置信息和/或操作类型时，从签约数据中获取相关信息以完成后续批量操作的流程，可以提高数据处理效率。
在一种可选的方式中，请求信息包括操作类型指示信息时，批量操作的操作类型是根据操作类型的指示信息确定的。
本申请中，基于请求信息中的操作类型指示信息，可以对不同的终端执行明确的操作，提高数据处理效率。
在一种可选的方式中，请求信息包括第一地理范围时，核心网设备发送第一消息至服务第一终端的接入网设备，第一消息包括：操作指令、指示标识，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的，指示标识与业务请求方的标识存在关联关系；核心网设备指示接入网设备根据操作指令对接入网设备下的终端逐个执行随机接入流程；核心网设备接收来自接入网设备的第二消息，第二消息包括：第二终端的标识和指示标识；操作类型为盘存时，核心网设备根据指示标识确定第二终端为第一终端中的一个，则缓存第二终端的标识；或，操作类型为读、写或灭活时，核心网设备根据指示标识确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
本申请中，在请求信息中包括第一地理位置信息时，通过指示标识筛选上报的终端标识，保证对业务请求方的终端的操作信息发送至业务请求方，可以保证数据处理的准确性。
在一种可选的方式中，核心网设备根据指示标识查询核心网设备预存或签约数据中的业务请求方的签约终端的标识列表；核心网设备在确定标识列表包括第二终端的标识时，则确定第二终端为第一终端中的一个。
在一种可选的方式中，请求信息包括第一终端的标识时，核心网设备发送第一消息至服务第一终端的接入网设备，第一消息包括：操作指令、X组掩码范围，X≥1，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的；核心网设备指示接入网设备根据操作指令对X组掩码范围下的终端逐个执行随机接入流程；核心网设备接收来自接入网设备的第二消息，第二消息包括：第二终端的标识；操作类型为盘存时，核心网设备确定第二终端为第一终端中的一个，则缓存第二终端的标识；或，操作类型为读、写或灭活时，核心网设备确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。本申请中，在请求信息包括第一终端的标识时，通过设置掩码范围防止接入网设备感知终端的具体信息，可以保证数据处理的安全性。
在一种可选的方式中，核心网设备确定第一终端中已有多个终端完成操作，包括：
核心网设备确定到达操作时间阈值，则确定第一终端中已有多个终端完成操作。
通过该方式可以知晓批量操作的结束时机，避免频繁操作，增加信令交互数据。
在一种可选的方式中，第一消息还包括：操作时间阈值；核心网设备确定第一终端中已有多个终端完成操作，包括：
核心网设备接收来自接入网设备的第三消息，第三消息用于指示到达操作时间阈值；核心网设备根据第三消息确定第一终端中已有多个终端完成操作。
通过该方式可以知晓批量操作的结束时机，避免频繁操作，增加信令交互数据。
在一种可选的方式中，核心网设备确定第一终端中已有多个终端完成操作，包括：
核心网设备确定到达操作生命周期，则确定第一终端中已有多个终端完成操作；操作生命周期至少 包括以下中的一种：操作次数阈值、X组掩码范围。
通过该方式可以知晓批量操作的结束时机，避免频繁操作，增加信令交互数据。
在一种可选的方式中，第一消息还至少包括以下中的一种：操作次数阈值、操作时间阈值；核心网设备确定第一终端中已有多个终端完成操作，包括：
核心网设备接收来自接入网设备的第三消息，第三消息用于指示到达操作次数阈值，和/或，操作时间阈值；核心网设备根据第三消息确定第二终端中已有多个终端批量执行操作。
通过该方式可以知晓批量操作的结束时机，避免频繁操作，增加信令交互数据。
在一种可选的方式中，核心网设备确定第一终端中已有多个终端完成操作后，还包括：核心网设备向接入网设备发送第四消息，第四消息指示接入网设备结束执行随机接入流程。
通过该方式可以知晓随机接入的结束时机，避免频繁操作，增加信令交互数据。
在一种可选的方式中，操作类型为盘存时，操作信息包括：盘存成功的第一终端的标识；或，操作类型为读时，操作信息包括：读成功的第一终端的标识、读的数据。
其中，根据实际业务需要，核心网设备除了可发送多个完成操作的终端的操作信息之外，也可以把未完成操作的终端的操作信息发送给业务请求方。此外，完成操作的终端的操作信息与未完成操作的终端的操作信可以一起发送，也可以分开发送，本申请在此不具体限定。
第二方面，本申请提供一种通信方法，包括：
接入网设备接收来自核心网设备的第一消息，第一消息包括操作指令、指示标识，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的，指示标识与业务请求方的标识存在关联关系；接入网设备根据操作指令对接入网设备下的终端逐个执行随机接入流程。
本申请中，接入网设备将终端操作信息上报给核心网设备之后，就进入下一个随机接入，而不需要等待核心网设备进行下一次随机接入的指令，通过该方式可以提高数据效率，减少交互信令。
在一种可选的方式中，接入网设备接收来自第二终端的第二终端的标识；接入网设备向核心网设备发送第二消息，第二消息还包括：第二终端的标识和指示标识。
在一种可选的方式中，第一消息还包括：操作时间阈值，接入网设备向核心网设备发送第三消息，第三消息用于指示到达操作时间阈值。
在一种可选的方式中，接入网设备接收来自核心网设备的第四消息，第四消息指示接入网设备结束执行随机接入流程。
第三方面，本申请提供一种通信方法，包括：
接入网设备接收来自核心网设备的第一消息，第一消息包括操作指令、X组掩码范围，X≥1，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的；接入网设备根据操作指令对X组掩码范围下的终端逐个执行随机接入流程。
本申请中，接入网设备将终端操作信息上报给核心网设备之后，就进入下一个随机接入，而不需要等待核心网设备进行下一次随机接入的指令，通过该方式可以提高数据效率，减少交互信令。
在一种可选的方式中，接入网设备接收来自第二终端的第二终端的标识；接入网设备向核心网设备发送第二消息，第二消息还包括：第二终端的标识。
在一种可选的方式中，第一消息还至少包括以下中的一种：操作时间阈值、操作时间阈值，接入网设备向核心网设备发送第三消息，第三消息用于指示到达操作时间阈值。
在一种可选的方式中，接入网设备接收来自核心网设备的第四消息，第四消息指示接入网设备结束执行随机接入流程。
第四方面，本申请实施例提供一种通信装置，所述通信装置可以为接入网设备(比如第一方面中的接入网设备、第二方面中的接入网设备、第三方面的接入网设备)或者设置在接入网设备内部的芯片，还可以为核心网设备(比如第一方面中的核心网设备、第二方面中的核心网设备、第三方面的核心网设备)或者设置在核心网设备内部的芯片。所述通信装置具备实现上述第一方面至第三方面中任一方面的功能，比如，所述通信装置包括执行上述第一方面至第三方面中任一方面涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述通信装置包括处理单元、收发单元，其中，收发单元可以用于收发信号，以实现该通信装置和其它装置之间的通信，比如，收发单元用于接收来自业务请求方的请求信息；处理 单元可以用于执行该通信装置的一些内部操作。所述收发单元可以称为输入输出单元、通信单元等，所述收发单元可以是收发器；所述处理单元可以是处理器。当通信装置是通信设备中的模块(如，芯片)时，所述收发单元可以是输入输出接口、输入输出电路或输入输出管脚等，也可以称为接口、通信接口或接口电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。
在又一种可能的设计中，所述通信装置包括处理器，还可以包括收发器，所述收发器用于收发信号，所述处理器执行程序指令，以完成上述第一方面至第三方面中任意可能的设计或实现方式中的方法。其中，所述通信装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，所述存储器可以保存实现上述第一方面至第三方面中任一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面至第三方面任意可能的设计或实现方式中的方法。
在又一种可能的设计中，所述通信装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面至第三方面中任一方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述通信装置实现上述第一方面至第三方面任意可能的设计或实现方式中的方法。
在又一种可能的设计中，所述通信装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面至第三方面任意可能的设计或实现方式中的方法。
可以理解地，上述第四方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第五方面，本申请实施例提供一种通信系统，该通信系统包括上述第一方面到第三方面中的接入网设备、核心网设备。
第六方面，本申请提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述第一方面到第三方面中任一种可能的设计中所述的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第七方面，本申请还提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机可读指令，当计算机可读指令在计算机上运行时，以使得计算机执行如第一方面到第三方面中任一种可能的设计中的方法。
第八方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面到第三方面的各实施例的方法。
上述第二方面至第八方面可以达到的技术效果，请参照上述第一方面中相应可能设计方案可以达到的技术效果说明，本申请这里不再重复赘述。
附图说明
图1示出了本申请实施例提供的一种网络架构的示意图；
图2示出了本申请实施例提供的另一种网络架构的示意图；
图3示出了一种无源物联业务的示意图；
图4A示出了盘点流程示意图；
图4B示出了读写流程示意图；
图5示出了本申请实施例提供的一种通信方法的流程示意图；
图6示出了本申请实施例提供的一种批量操作的流程示意图；
图7示出了本申请实施例提供的一种批量操作的流程示意图；
图8示出了本申请实施例提供的通信装置的结构示意图；
图9示出了本申请实施例提供的通信装置的结构示意图；
图10示出了本申请实施例提供的通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。因此装置与方法的实施可以相互参见，重复之处不再赘述。
为了应对无线宽带技术的挑战，保持3GPP网络的领先优势，3GPP标准组制定了下一代移动通信网络系统(Next Generation System)架构，称为第五代(5th generation，5G)网络架构。该架构不但支持3GPP标准组定义的无线接入技术(如长期演进(long term evolution，LTE)接入技术，无线接入网(radio access network，RAN)接入技术等)接入到5G核心网(core network，CN)，而且支持使用非3GPP(non-3GPP)接入技术通过非3GPP转换功能(non-3GPP interworking function，N3IWF)或下一代接入网关(next generation packet data gateway，ngPDG)接入到核心网。
图1为基于服务化架构的5G网络架构示意图。图1所示的5G网络架构中可包括接入网设备以及核心网设备。终端通过接入网设备和核心网设备接入数据网络(data network，DN)。其中，核心网设备包括但不限于以下网元中的部分或者全部：鉴权服务器功能(authentication server function，AUSF)网元(图中未示出)、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR)网元、网络存储功能(network repository function，NRF)网元(图中未示出)、网络开放功能(network exposure function，NEF)网元(图中未示出)、应用功能(application function，AF)网元、策略控制功能(policy control function，PCF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、绑定支持功能(binding support function，BSF)网元(图中未示出)。
终端可以是用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。
接入网设备可以是基站(base station)、杆站、室内基站(例如Lampsite)、家庭基站(例如home NB)、微型基站、接入回传一体化(integrated access and backhaul,IAB)节点、移动基站、无线接入网(RAN)设备或有线接入网(wirelineaccess network，FAN)设备。其中，无线接入网设备包括3GPP接入网设备、非可信非3GPP接入网设备和可信非3GPP接入网设备。3GPP接入网设备包括但不限于：LTE中的演进型基站(evolved nodeB，eNodeB)、5G移动通信系统中的下一代基站(next generation nodeB，gNB)、未来移动通信系统中的基站或完成基站部分功能的模块或单元，如集中式单元(central unit，CU)，分布式单元(distributed unit，DU)等。非可信非3GPP接入网设备包括但不限于：非可信非3GPP接入网关或N3IWF设备、非可信无线局域网(wireless local area network，WLAN)接入点(access point，AP)、交换机、路由器。可信非3GPP接入网设备包括但不限于：可信非3GPP接入网关、可信WLAN AP、交换机、路由器。有线接入网设备包括但不限于：有线接入网关(wireline access gateway)、固定电话网络设备、交换机、路由器。
接入网设备和终端可以是固定位置的，也可以是可移动的。接入网设备和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和终端的应用场景不做限定。
AMF网元，包含执行移动性管理、接入鉴权/授权等功能。此外，还负责在终端与PCF网元间传递用户策略。
SMF网元，包含执行会话管理、执行PCF下发的控制策略、选择UPF、分配终端的互联网协议(internet protocol，IP)地址等功能。
UPF网元，包含完成用户面数据转发、基于会话/流级的计费统计、带宽限制等功能。
UDM网元，包含执行管理签约数据、用户接入授权等功能。
UDR网元，包含执行签约数据、策略数据、应用数据等类型数据的存取功能。
NEF网元，用于支持能力和事件的开放。
AF网元，传递应用侧对网络侧的需求，例如，服务质量(quality of service，QoS)需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。其中，AF网元包括核心网内的AF网元(即运营商的AF网元)和第三方AF网元(如某个企业的应用服务器)。
PCF网元，包含负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、终端策略决策等策略控制功能。PCF网元包括接入与移动性管理策略控制网元(access and mobility management policy control function，AM PCF)网元和会话管理策略控制功能(session management PCF，SM PCF)网元。其中，AM PCF网元用于为终端制定AM策略，AM PCF网元也可以称为为终端提供服务的策略控制网元(PCF for a UE))。SM PCF网元用于为会话制定会话管理策略(session management policy，SM策略)，SM PCF网元也可以称为为会话提供服务的策略控制网元((PCF for a PDU session))。
NRF网元，可用于提供网元发现功能，基于其他网元的请求，提供网元类型对应的网元信息。NRF还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
BSF网元，可提供BSF服务注册/注销/更新，与NRF连接检测，会话绑定信息创建，UE信息的获取，IP地址重复的会话绑定信息查询等功能。
AUSF网元，负责对用户进行鉴权，以确定是否允许用户或设备接入网络。
DN，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1中Npcf、Nurf、Nudm、Naf、Namf、Nsmf分别为上述PCF、UDR、UDM、AF、AMF和SMF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4以及N6为接口序列号，这些接口序列号的含义如下：
1)、N1：AMF与终端之间的接口，可以用于向终端传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
2)、N2：AMF与接入网设备之间的接口，可以用于传递核心网侧至接入网设备的无线承载控制信息等。
3)、N3：接入网设备与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户面数据。
4)、N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
5)、N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
图2为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图2中对应的网元的功能的介绍，不再赘述。图2与图1的主要区别在于：图1中的各个控制面网元之间的接口是服务化的接口，图2中的各个控制面网元之间的接口是点对点的接口。
在图2所示的架构中，各个网元之间的接口名称及功能如下：
1)、N1、N2、N3、N4和N6接口的含义可以参考前述描述。
2)、N5：AF网元与PCF网元之间的接口，可以用于应用业务请求下发以及网络事件上报。
3)、N7：PCF网元与SMF网元之间的接口，可以用于下发协议数据单元(protocol data unit，PDU)会话粒度以及业务数据流粒度控制策略。
4)、N8：AMF网元与UDM网元间的接口，可以用于AMF网元向UDM网元获取接入与移动性管理相关签约数据与鉴权数据，以及AMF网元向UDM网元注册终端移动性管理相关信息等。
5)、N9：UPF网元和UPF网元之间的用户面接口，用于传递UPF网元间的上下行用户数据流。
6)、N10：SMF网元与UDM网元间的接口，可以用于SMF网元向UDM网元获取会话管理相关签约数据，以及SMF网元向UDM网元注册终端会话相关信息等。
7)、N11：SMF网元与AMF网元之间的接口，可以用于传递接入网设备和UPF之间的PDU会话隧道信息、传递发送给终端的控制消息、传递发送给接入网设备的无线资源控制信息等。
8)、N15：PCF网元与AMF网元之间的接口，可以用于下发终端策略及接入控制相关策略。
9)、N35：UDM网元与UDR网元间的接口，可以用于UDM网元从UDR网元中获取用户签约数据信息。
10)、N36：PCF网元与UDR网元间的接口，可以用于PCF网元从UDR网元中获取策略相关签约数据以及应用数据相关信息。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请中的用户面网元、会话管理网元、移动性管理网元分别可以是5G系统中的UPF网元、SMF网元、AMF网元，也可以是未来通信如第6代(the 6th generation，6G)网络中具有上述UPF网元、SMF网元、AMF网元的功能的网元，本申请对此不限定。在本申请的实施例中，以UPF网元、SMF网元、AMF网元分别为用户面网元、会话管理网元、移动性管理网元的一个示例进行描述。并且，将UPF网元、SMF网元、AMF网元分别简称为UPF、SMF、AMF。
为便于说明，本申请实施例中，以基站(如第4代(the 4th generation，4G)的eNB、5G的gNB或未来通信中的基站)作为接入网设备的一个示例进行说明，后续出现的“基站”均可以替换为“接入网设备”。本申请实施例中，以UE作为终端的一个示例进行说明，后续出现的“UE”均可以替换为“终端”。
可以理解的是，核心网还可以包括其他网络功能实体，本申请对此不作限定。
本申请实施例提供的技术方案可以应用于各种通信系统。例如：可以适用于5G系统，也可以适用于其它面向未来的新系统，例如6G系统等。本申请实施例对此不作具体限定。此外，术语“系统”可以和“网络”相互替换。
为便于理解本申请实施例，对本申请实施例中涉及的几个基本概念做简单说明。
1、P-IoT，即有些网络节点可以是无源的、半无源、半有源或者有源的，通过太阳能、射频、风能、水能或者潮汐能等方式获取能量，本身请在此不具体限定获取能量的方式。这些节点自身可以不配备或者不依赖电池等电源设备，而是从环境中获取能量，支撑数据的感知、传输和分布式计算。网络节点还可以将获取的能量进行存储。无源物联网架构中可以包括终端、阅读器(reader，或者可以称为读写器)以及服务器。无源终端可以是标签形态，也可以是其他任意终端形态，不做限制。终端可以是无源的、半无源、半有源或者有源的。终端可以不具有储能能力(例如不具备电容)，或者可以具有储能能力(例如具备电容以存储电能)。阅读器可以是接入网设备，例如基站、杆站、微型基站、宏站等；阅读器还可以是终端，例如手机、IoT设备、手持读写器等设备。在此以终端为标签为例来阐述，但不限于标签。阅读器(Reader)通过无线射频方式进行非接触双向数据通信，利用无线射频方式对电子标签或射频卡(Tag)进行读写，从而达到识别目标和数据交换的目的。一种就是当标签进入阅读器有效识别范围内时，接收阅读器发出的射频信号，凭借感应电流所获得能量发出存储在芯片中的信息(对应于无源标签)；另一种就是标签可以通过太阳能等方式存储部分电能，使得可以主动发送某一频率的信号(这种还可以称为半无源或者半有源标签)，阅读器接收信息并解码后，送至中央信息系统进行有关数据处理。
图3展示了无源物联网业务的示意图。图3中将以阅读器为基站(杆站或者宏站)为例来阐述，但本申请不限制阅读器的设备形态。
当服务器向标签进行操作时，可以向通过核心网(例如标签管理功能TMF，TMF可以与核心网设备、接入网设备或者应用功能合为一体，也可以为独立的核心网设备)发送操作指令，操作指令可以包括盘点操作(或者称为盘存操作)(也可以理解为获取标签的标识，每个标签会有其标识。标签的标识可以由企业分配(即在企业打印标签时写入标签中)，也可以由运营商分配。一种可能的实现方式中，标签的标识可以是一个全球唯一的码——例如电子产品代码(electronic product code，EPC)，也可以是临时的标识或者不为全球唯一的标识。在盘点流程中，服务器可以下发盘点指令。通常，盘点指令会包括标签的标识范围、阅读器标识、位置信息等信息。阅读器接收到盘点指令后，会根据盘点指令向标签进行盘点，并向服务器发送标签的标识。或者，服务器发送指令，阅读器向标签转发该指令。标签根据指令的内容获知为盘点操作，标签向阅读器发送标签的标识，阅读器向服务器发送标签的标识；或者，标签通过阅读器向核心网发送标签的标识信，核心网向服务器发送标签的标识。)、读操作(即对标签进 行数据读取。标签可以有存储功能，其存储区可以存储数据。若服务器欲对标签进行读操作，则会发送读指令，阅读器或者核心网根据指令对标签进行读操作，从标签存储区中读取数据，并向服务器发送该数据)、写操作(即对标签进行数据写入。服务器可以发送写指令，阅读器或者核心网根据指令对标签进行写操作，向标签的存储区写入数据)、灭活操作(即使能标签失效或者灭活。服务器可以发送灭活指令，灭活指令中可以包括标签标识(即希望灭活或者失效的标签的标识)。阅读器或者核心网根据指令对标签进行失效操作，操作完成后，该标签会被失效或者被灭活，而不得再被盘点或被执行其他操作)、获取标签信息(可以理解为是上述各种操作的一个上位描述(例如是盘点操作和读操作的上位描述)，不区分服务器是盘点标签还是读标签数据，该操作会获取标签信息，该标签信息可以是标签的标识或者是标签存储区中存储的信息)、与标签交互信息操作(可以理解为是上述各种操作的一个上位描述。阅读器接收服务器发送的指令后，与标签进行信息或者消息交互，并向服务器发送来自标签的信息。该操作主要是针对上述阅读器不查看指令内容，只负责转发服务器发送给标签的消息和标签发送给服务器的消息。因此在该场景下，阅读器对标签执行的操作可以理解为是与标签的消息交互操作)。指令可以包括区域位置信息、标签的标识等。基站向标签发送接入指令。当标签随机接入成功后，基站会向标签发送指令(基站可以向标签转发核心网发送的指令)。标签根据指令获取或者发送相应的信息。例如，当指令为盘点指令或者为执行盘点操作时，标签会发送标签的标识；当指令为读指令或者为执行读操作时，标签会发送存储在标签存储区中的数据信息；当指令为写指令或者执行写操作时，标签会将指令中包括的待写入标签的数据信息存储至标签的存储区中。基站向核心网发送(或者转发)标签发送的信息；核心网向服务器发送该信息。核心网基于服务器的反馈信息对标签进行接入管理操作。
服务器发送指令的方式可以通过控制面通道发送，如图3所示：服务器向标签管理功能或者无源物联功能发送指令；此时，服务器可以为应用功能(application function，AF)、应用服务器(application server，AS)或者无源物联网应用功能(P-IoT AF)。一种可能的实现方式，P-IoT AF向标签管理功能或者无源物联功能发送指令。另一种可能的实现方式中，P-IoT AF通过控制面设备向标签管理功能或者无源物联功能发送指令。该控制面设备可以是NEF、SMF、PCF、UDM、网络切片和SNPN(独立非公共网络)的鉴权授权功能(network slice-specific and SNPN authentication and authorization function，NSSAAF)、AMF。此外，服务器还可以通过用户面通道向阅读器发送指令。一种可能的实现方式，服务器通过UPF向基站发送指令。一种可能的实现方式，服务器通过用户面设备(UPF)、SMF向标签管理功能或者无源物联功能发送指令，并由标签管理功能或者无源物联功能通过RAN向标签发送指令。另一种可能的实现方式，服务器通过用户面设备和接入网设备，例如RAN向阅读器发送指令(当阅读器为终端时)。一种可能的实现方式中，标签管理功能或者无源物联功能可以与核心网设备、接入网设备或者应用功能合设或者共部署。当两个设备或者功能共部署时，本申请实施例提供的这两个功能或者设备之间的交互就成为该合设功能或者设备的内部操作或者可以省略。
2、标签的随机接入操作流程
针对标签盘点流程，在盘点流程中，标签需要执行图4A中的随机接入(步骤1至步骤4)并在随机接入成功后将该EPC码发送给读写器，以使读写器可获知有哪些标签在其覆盖范围内。该信息会最终由读写器上报给中间件和服务器。读写流程大致如下：
步骤1.读写器收到服务器下发的盘点命令(该盘点命令可由服务器下发给中间件，再由中间件下发给读写器)，生成Select命令，该命令中会携带标签的范围(如某些特定范围的EPC码)，并下发Select命令。标签在监听到Select命令后，判断自己是否属于该Select命令里需要判断的标签范围，若属于，则会在后续听到Query命令后去反馈信息。若不属于，则后续不会做任何动作。
步骤2.读写器发送Query命令；Query命令中可以包括一个数值(记为Q值)，标签会根据Q值生成随机数，例如在0至2的Q次方之间，生成随机数。随后，标签会在读写器每发送一次Query或者QueryRep的指令之后，将该随机数减一。当随机数减至零时，标签会发起随机接入。
步骤3.当标签发现自己属于Select命令中选中的标签范围时，会通过竞争的方式(例如通过步骤2中当随机数减至零时，向读写器发送随机数RN16)向读写器反馈一个随机数RN16(可以理解为一个长度为16比特的随机数)。
步骤4.当读写器收到来自标签发送的随机数后，会发送一个ACK命令，该命令中包含了刚刚收到的随机数(RN16)。
步骤5.当标签收到阅读器发送的ACK命令，并验证该随机数正确后，会反馈其的EPC码给读写 器，从而完成盘点流程。
针对标签读写流程，在读写流程中，读写器会通过将Select命令中的标签范围设置为需读写的标签范围(比如Select命令中的范围为某一EPC码，则会对该EPC码对应的标签进行读写操作)。图4B中的第1步至第5步为盘点流程，只是该盘点流程并非为一个群体标签的盘点流程，而是对某一标签进行盘点。从第6步开始，为读写流程，大致如下：
步骤6.读写器向该标签发送Req_RN命令，其中携带了之前所收到的随机数RN16。
步骤7.标签验证该随机数正确，则向读写器发送句柄。在后续的读写流程中，都需要携带该句柄。
步骤8.读写器向标签发送读或写命令，其中需携带句柄。若为写指令，则还需携带要写进标签存储区的数据。
步骤9.若第8步为读指令，则标签需反馈自己存储区中的数据，且还需携带句柄。
需要注意的是，标签的灭活流程与此类似，在第8步标签收到灭活指令后执行灭活，后在第9步可选地反馈句柄。
如背景技术所述，在Passive IoT中，一个标签在一段时间内可能不会出现多次频繁操作，若等待多次统计后，存储或转发，不能满足Passive IoT中的业务需求，该方法不适用于Passive IoT，此外，当读写器的执行主体变成基站时，需要规避基站感知具体的用户信息，不论是标签信息还是对标签进行的操作信息，以确保信息的安全性，因此亟需一种新的标签批量操作方法，以适用于Passive IoT的需求，以及其他5G IoT技术的需求，如Massive IoT(大规模物联网)、Narrowband IoT(窄带物联网)、Critical IoT(关键任务类物联网)、Industrial IoT(工业物联网)等。
本申请提供一种通信方法，如图5所示，该方法可通过接入网设备来执行，也可通过核心网设备来执行，还可通过接入网设备、核心网设备以及业务请求方的交互来执行。该接入网设备可以为RAN、接收点(transmission reception point，TRP)、gNB，也可以为芯片等，该核心网设备可以为AMF、SMF、TMF等，业务请求方可以为AF等，本申请在此不作具体限定。图5中以终端为Tag1、Tag2、Tag3(在此仅以三个终端为例来说明，但是实际应用时并不限定终端的数量，在执行本申请的方案前，标签打印方Tag Printer会提前向Tag1、Tag2、Tag3写入Tag标识)、接入网设备为RAN、核心网设备为AMF、业务请求方为AF以及NEF为例来说明，当然，在实际应用时，上述的业务请求方可能为多个，服务某个业务请求方的核心网设备(例如企业A分布在不同的地区，服务于企业A的地区1的终端的核心网设备为AMF1，服务于企业A的地区2的终端的核心网设备为AMF2)以及接入网设备可能也存在多个。另外，有部分场景可能可以通过终端对标签执行接入流程，或者执行操作，此时读写器还可能呈现为终端的形态，该情况也适用于本申请的方案，在此不具体限定。如下所述：
步骤502，AMF获取业务请求方的请求信息，请求信息包括业务请求方的标识(也即AF ID)。
可选的，AF可通过NEF向AMF发送请求信息，亦或者AMF从其他核心网设备获取业务请求方的请求信息，如，当前AMF1处于核心网1中，AMF1可以与核心网2中的AMF2进行数据交互获取第三方的信息，当然AMF还可从UDM中查询存储的请求信息，本申请在此不具体限定。其中，业务请求方可以理解为用户、企业、个人、操作请求方等，本申请在此不具体限定。图5中以步骤501，AF通过NEF向AMF发送请求信息，以使AMF获取业务请求方的请求信息为例进行示意。本申请中以请求信息为例来说明，但是实际应用时，还可以称为业务请求，操作请求信息等，本申请对发送请求信息的消息类型或者消息名称不做限定。
可选的，业务请求方的标识通过以下信息中的至少一种指示：
业务请求方的标识、业务请求方对应的应用功能标识、业务请求方对应的地址信息、业务请求方对应的端口信息。
其中，业务请求方的标识，如：业务请求方的全局唯一标识信息、运营商的全局唯一标识信息等，或者业务请求方对应的应用功能标识，如AF ID。一种可能的实现方式，请求信息的地址信息或者端口信息可以是业务请求方对应的端口信息或地址信息。一种可能的实现方式中，地址信息可以包括IP地址(例如IPv4地址、IPv6地址或者IPv6prefix)或者MAC地址(media access control address)；端口号信息可以包括传输控制协议(transmission control protocol，TCP)端口号或者用户数据报协议(user datagram protocol，UDP)端口号，AMF通过解析请求信息的地址可以知晓对应的业务请求方的标识。
步骤503，AMF基于请求信息确定批量执行操作，并对第一终端执行操作，第一终端为待操作的终端。
其中，核心网设备基于请求信息确定批量执行操作，可以理解为核心网设备直接基于请求信息中的具体内容确定是否批量执行操作，还可以理解为核心网设备预设某种判断策略，在收到请求信息后，基于请求信息的内容检索判断策略，确定是否批量执行操作，本申请在此不具体限定。其中，第一终端的数量以及多个终端的数量根据实际场景而有不同，且在实际应用时，第一终端可以理解为业务请求方的签约终端，例如，业务请求方为企业A，第一终端可以为企业A的签约终端，亦或者企业A在某个地区的签约终端，亦或者企业A在某个时间段的签约终端等，或者是通过某种接入方式接入到业务请求方，并通过业务请求方管理的终端，例如，停放在地下停车场中的多辆车，或者某个小区中多个水表等，本申请在此不具体限定。
可选的，请求信息中还包括以下中的至少一种，
第一终端所处的第一地理范围、第一终端的标识、操作类型指示信息。
其中，第一终端所处的第一地理范围可以理解为为第一终端提供服务的地址信息(经度信息和纬度信息、坐标值信息、TAI、Cell ID等)，例如，第一地理范围为东经115°～西经20°，北纬10°～北纬30°，第一地理范围为A公司的上海分公司的园区等。其中，第一地理范围内可能不仅存在业务请求方的签约终端，还可能存在其他的终端，如，业务请求方为企业A，第一地理范围内可能存在企业A的签约终端，还可能存在企业B的签约终端。在此仅示例说明第一地理范围，并不对第一地理范围进行具体限定。
其中，第一终端的标识，可以理解为业务请求方希望操作的终端(如标签)的标识等，本申请在此不具体限定。
其中，操作类型指示信息可以理解为盘存(也可称作盘点)、读、写、灭活等操作的指示信息。具体的操作类型可以为盘存终端、读取终端的存储区数据、向终端的存储区写入数据、灭活终端，本申请在此不具体限定。
本申请中，请求信息包括上述的多种类型，便于核心网设备可以更好地确定是否需要批量执行操作以及具体如何批量执行操作。
在请求信息中包括信息不同时，AMF可基于不同的情形确定批量执行操作，具体如下：
情形1、请求信息仅包含业务请求方的标识(AF ID)
AMF接收到请求信息后发现仅包含AF ID，根据AF ID确定批量执行操作，其中第一终端为业务请求方的签约终端。在请求信息仅包含业务请求方标识时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
情形2、请求信息为业务请求方的标识(AF ID)和第一地理范围
AMF接收到请求信息后发现包含AF ID和第一地理范围，AMF可确定批量执行操作，第一终端为第一地理范围覆盖下的业务请求方的签约终端。如，AMF接收到AF1+地理范围A，确定需要对地理范围A内的业务请求方的签约终端批量执行操作。
本申请中，在请求信息包含业务请求方标识及第一地理范围时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
情形3、请求信息为业务请求方的标识(AF ID)和第一终端的标识
若第一终端的标识的数量大于1，AMF根据第一终端的标识确定批量执行操作。如，AMF接收到AF1+终端的标识1，由于请求信息中仅存在一个终端标识，则不批量执行操作，若AMF接收到AF1+终端的标识1、终端的标识2、终端的标识5、终端的标识9，由于请求信息中仅存在多个终端标识，则需要批量执行操作。
情形4、请求信息为业务请求方的标识(AF ID)和操作类型指示信息
AMF接收到AF ID后，根据AF ID确定批量执行操作，如，AMF接收到AF1，且接收到操作类型指示信息，确定AF1对应批量操作，则确定需对AF1对应的业务请求方的签约终端执行对应操作类型指示信息的操作，若操作规则中AF2未对应批量操作，则确定不需要对AF2对应的业务请求方的签约终端执行操作。
情形5、请求信息为业务请求方的标识(AF ID)、第一地理范围和第一终端的标识
请求信息为业务请求方的标识(AF ID)、第一地理范围和第一终端的标识时，若第一终端的标识的数量大于1，AMF根据第一终端的标识确定执批量行操作。
情形6、请求信息为业务请求方的标识(AF ID)、第一地理范围和操作类型指示信息
请求信息为业务请求方的标识(AF ID)、第一地理范围和操作类型指示信息时，AMF可根据第一地理范围确定批量执行相应操作类型指示信息的操作。示例性地，表1以第一地理范围为第一终端提供服务的接入网设备RAN的地址为例进行示意，对地址为经度A1和纬度B1管辖的AF1的签约终端执行灭活操作，对地址为经度A2和纬度B2管辖的AF2的签约终端执行写操作。此外，AMF还可通过LMF获取为第一终端提供服务的接入网设备的地址，本申请在此不具体限定如何获取为第一终端提供服务的接入网设备的地址。
表1
本申请中，在请求信息包含业务请求方的标识、第一终端所处的第一地理范围及操作类型指示信息时，直接对终端进行批量操作，可减少判断批量操作的步骤，提高数据处理效率。
情形7、请求信息为业务请求方的标识(AF ID)、第一终端的标识以及与第一终端对应的操作类型指示信息，且相同的操作类型指示信息对应第一终端中的多个终端的标识
若第一终端的标识的数量大于1，且相同的操作类型指示信息对应多个不同的第一终端中多个终端的标识时，AMF确定批量执行操作。如，AMF接收到AF1+终端的标识1+盘存、终端的标识2+读数据、终端的标识3+写数据、终端的标识5+灭活，由于各个终端标识对应的操作类型是不同的，则不批量执行操作，若AMF接收到AF1+终端的标识1+盘存、终端的标识2+盘存、终端的标识5+读数据、终端的标识9+写数据，由于请求信息中仅存在多个终端标识，且存在至少2个终端标识对应不同的操作类型，则需要批量执行操作。
示例性地，如下述表2所示，表2中以第一终端为业务请求方的签约终端为例来说明，对于AF1的签约终端中终端的标识大于100或小于200的终端执行盘存操作，对于AF1的签约终端的终端的标识小于50的终端执行灭活操作。
还有一种可能的情况是，请求信息中的终端标识范围包含其余企业(如AF2)的终端标识，这种情况下核心网设备根据业务请求方标识查询核心网设备预存或签约数据中的业务请求方的签约终端的标识列表，选择请求信息中的终端标识范围与标识列表的交集作为第一终端标识。
表2
示例性地，如下述表3所示，对于AF 1的签约终端的终端的标识为00000000和00000001的终端执行盘存操作，对于AF 1的签约终端的终端的标识为00000010的终端执行灭活操作，对于AF1的签约终端的终端的标识为00000011的终端执行读操作。
表3

情形8、请求信息为业务请求方的标识(AF ID)、第一地理范围、第一终端的标识和操作类型指示信息
请求信息为业务请求方的标识(AF ID)、第二地理范围、第一终端的标识和操作类型指示信息时，若第一终端的标识的数量大于1，且相同的操作类型指示信息对应多第一终端中多个终端的标识时，AMF确定批量执行操作。
示例性地，如下述表4所示，对于经度A1和纬度B1管辖的第一端的标识为00000000和00000001的终端执行盘存操作。
表4
在一种可选的方式中，AMF可基于上述表1～表4确定是否需要对第一终端执行相同的操作，也即批量管理，如上述表1，AMF可对>100&<200的终端批量执行盘存的操作，对<50的终端批量执行灭活的操作；如上述的表3，AMF可对0000 0000和0000 0001对应的终端批量执行盘存的操作。
在实际应用时，请求信息可能为上述8种情形中的任意一种，核心网设备可根据需求灵活确定批量执行操作的判断操作，本申请在此不具体限定。
以上均为请求信息中隐式地包含需要进行批量操作的指示，即根据特殊的信息内容判断需要进行批量操作，也即根据请求信息中的内容直接判断是否批量执行操作。此外，还可通过其他方式指示是否批量执行操作，例如，AMF接收到业务请求方的标识信息时，查询AMF预设的判断策略或UDM/UDR中的签约数据，根据判断策略或签约数据确定AF1对应批量操作，则确定需对AF1对应的业务请求方的签约终端批量执行操作，若操作规则中AF2未对应批量操作，则确定不需要对AF2对应的业务请求方的签约终端批量执行操作。
在请求信息为上述几种情形时，对第一终端批量执行操作的具体流程是不同的，具体如下：
在情形1中，AMF根据业务请求方的标识获取业务请求方的签约数据，签约数据包括：业务请求方与操作类型的对应关系、业务请求方与第二地理范围的对应关系；AMF根据签约数据对第二地理范围覆盖下的多个终端(也即第一终端)执行相应操作类型的操作。如下述表5所示，对于AF1的签约数据中包括盘存、经度A1～经度B1，纬度X1～纬度Y1，那么AMF基于该签约数据可确定需要对经度A1～经度B1，纬度X1～纬度Y1下的多个终端执行盘存的操作。对于AF2的签约数据中包括读数据、经度A2～经度B2，纬度X2～纬度Y2，那么AMF基于该签约数据可确定需要对经度A2～经度B2，纬度X2～纬度Y2下的多个终端执行读数据的操作。
表5

在上述的情形中，若请求信息包括第一地理范围，AMF仅需查询签约数据获取操作类型的信息，对第一地理范围覆盖下的多个终端执行相应操作类型的操作，其中，第一终端为第二地理范围覆盖下的业务请求方的签约终端。
此外，请求信息包括第一地理范围时，且核心网设备根据业务请求方的签约数据查询的第二地理范围与第一地理范围不同时，第一终端为第二地理范围与第一地理范围的交集覆盖下的终端，亦或者第一地理范围与第二地理范围中范围较小的地理范围覆盖下的终端。
此外，在上述的情形中，若请求信息包括：操作类型指示信息时，批量执行操作的操作类型是根据操作类型的指示信息确定的，而无需查询签约数据。
此外，请求信息还可包括终端的设备类型(无源、半无源、半有源、有源)，以便在不同类型的第一终端采用相同标识的情况下，区分具体对哪个第一终端执行管理操作，以及通知AMF对不同类型的设备采取不同的操作，如接收不同的NAS消息类型。
步骤504，AMF确定第一终端中已有多个终端完成操作后，发送多个终端的操作信息至业务请求方。
若AMF根据业务请求方的签约数据确定Tag1、Tag2执行了操作(也即为第一终端)且为业务请求方的签约终端，则将Tag1、Tag2的操作信息发送至业务请求方。当然在实际应用时，Tag3可能也执行了操作，但是Tag3并非第一终端，因此无需将Tag3的操作信息发送至业务请求方。
本申请，通过AMF识别待批量操作的终端，可实现对多个终端的批量操作，而非仅针对一个终端执行同样的操作，通过该方式可以减少操作信令的交互，提高数据处理效率。
接下来分情况对请求信息中包括第一地理范围不包括第一终端的标识，以及请求信息中包括第一终端的标识不包括第一地理范围来说明具体如何批量执行操作：
情况一、请求信息包括第一地理范围不包括第一终端的标识
图6中以终端为Tag1、Tag2、Tag3(在此仅以三个终端为例来说明，但是实际应用时并不限定终端的数量，在执行本申请的方案前，标签打印方Tag Printer会提前向Tag1、Tag2、Tag3写入Tag标识)、接入网设备为RAN、核心网设备为AMF、业务请求方为AF以及NEF为例来说明，当然，在实际应用时，上述的业务请求方可能为多个，服务某个业务请求方的核心网设备(例如企业A分布在不同的地区，服务于企业A的地区1的终端的核心网设备为AMF1，服务于企业A的地区2的终端的核心网设备为AMF2)以及接入网设备可能也存在多个。如下所述：
步骤601，AF通过NEF向AMF发送请求信息，请求信息中包括业务请求方的标识以及第一地理范围。
步骤602，AMF基于请求信息确定批量执行操作，并对第一终端执行操作。
可参照上述步骤503的描述来理解如何确定批量执行操作，以及具体如何确定第一终端以及批量操作的操作类型，在此不赘述。
下述步骤603～步骤608B具体介绍如何对第一终端执行操作。
步骤603，AMF确定第一消息，第一消息包括：操作指令、指示标识，操作指令触发RAN触发多次随机接入流程，操作指令是根据操作类型确定的，指示标识与业务请求方的标识存在关联关系。
在一个可能的实施方式中，操作指令指示任一终端与接入网设备之间到达预设透传次数执行下一个第一终端的随机接入。例如，操作类型为盘存，则操作指令指示RAN与终端执行一次透传操作后则可执行对下一个终端的盘存，其中，一次透传可以理解为上述附图4A中的步骤5；批量管理的操作类型为读、写、灭活，则操作指令指示RAN与终端执行三次透传操作后则可执行对下一个终端的读、写、灭活，其中，三次透传可以理解为上述附图4B中的步骤7～9。本申请中，接入网设备将终端操作信息上报给核心网设备之后，就进入下一个随机接入，而不需要等待核心网设备进行下一次随机接入的指令，通过该方式可以提高数据效率，减少交互信令。
其中，指示标识可以理解为NGAP标识，该NGAP标识不同于现有的NGAP标识，该NGAP标识是与业务请求方的标识存在关联关系的，当AMF收到该NGAP标识时可根据关联关系获知业务请求方 的标识信息。该指示标识可用于后续步骤中对终端上报的终端的标识筛选，以便将第一终端的操作信息上报至业务请求方，具体描述可参照后文608A和608B的描述。
此外，第一消息还可包括操作模式指示信息，如：操作模式指示信息为1，对应执行的操作为盘存，操作模式指示信息为3，对应执行的操作为读等，在此仅示例性描述，并不具体限定。
步骤604，AMF发送第一消息至服务第一终端的RAN。
其中，该RAN也即第一地理范围下服务业务请求方的签约终端的RAN，实际应用时，该RAN可能服务多个业务请求方的终端。
步骤605，AMF指示RAN根据操作指令对RAN下的终端逐个执行随机接入流程。
步骤606A，Tag1上报Tag1的标识至RAN。
步骤606B，Tag2上报Tag2的标识至RAN。
步骤606C，Tag3上报Tag3的标识至RAN。
在一种实施例中，Tag为无源设备时，由于每次接入AMF均为重新注册的过程，因此可通过Registration request消息发送Tag的标识，还需要携带Tag注册的消息；Tag为半无源设备时，由于接入AMF时保留之前注册的部分信息，因此可通过NAS transport消息发送Tag的标识。
需要注意的是，上述的步骤606A～步骤606C中，RAN可仅作透传转发，具体地，在Tag执行盘存操作时，可在Tag执行一次透传之后，对下一个Tag进行随机接入，接收下一个Tag上报的标识，例如，在执行盘存操作时，确定步骤606A中Tag1执行一次透传之后，再进行随机接入流程，执行步骤606B的操作，在Tag2执行一次透传之后，再进行随机接入理财，执行步骤606C的操作。在Tag执行读、写、灭活操作时，可在Tag执行三次透传之后，若无来自AMF的其他指示，则进行随机接入流程，接收下一个Tag上报的标识，例如，在执行盘存操作时，确定步骤606A中Tag1执行三次透传之后，再执行步骤606B的操作，在Tag2执行三次透传之后，再执行步骤606C的操作。RAN也可缓存Tag标识后，在自行判断所有的Tag已经完成接入后(如到达操作时间阈值)，在将缓存的标识上报至AMF。需要注意的是，RAN不感知Tag的具体信息，且随机接入流程后透传的Tag标识信息并不按某种顺序固定，此处仅作实例。
另一种可能的情况是，该终端的操作信息暂存在RAN上，当AMF或RAN判断终端的操作生命周期结束后，由RAN统一将终端的操作信息发送给AMF。
步骤607，RAN向AMF发送第二消息，该第二消息包括第二终端的标识(也即Tag1的标识、Tag2的标识、Tag3的标识)和指示标识。
可选的，RAN可根据指示标识生成其他指示标识，RAN可向AMF发送第二消息，第二消息还包括其他指示标识。AMF可根据该其他指示标识与指示标识的关联关系，确定业务请求方的标识。
步骤608A，操作类型为盘存时，AMF根据指示标识确定第二终端为第一终端中的一个，则缓存所第二终端的标识(属于第一终端，且为业务请求方的签约终端)。
步骤608B，操作类型为读、写或灭活时，AMF根据指示标识确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
若不是，则指示RAN对下一个Tag进行随机接入。
上述的步骤608A和608B可根据实际的操作类型选择执行，本申请在此不具体限定。具体地，AMF根据指示标识(或其他指示标识)查询核心网设备预存的业务请求方的签约终端的标识列表，AMF在确定标识列表包括第二终端的标识时，则确定第二终端为第一终端中的一个。
例如，指示标识对应的签约终端的标识列表如下述表6所示，其中NGAP1对应的终端标识包括：AF1的Tag1的标识、AF1的Tag2的标识；NGAP2对应的终端标识包括：AF2的Tag4的标识、AF2的Tag5的标识，在此仅示意性说明，并不具体限定。
表6
在上述步骤608A中，若指示标识为NGAP1，通过查询表6可知业务请求方的签约终端的标识为Tag1的标识、Tag2的标识，那么第二终端为Tag1和Tag2时，AMF则缓存Tag1的标识和Tag2的标识。 在上述步骤608B中，若指示标识为NGAP1，通过查询表6可知业务请求方的签约终端的标识为Tag1的标识、Tag2的标识，第二终端为Tag1和Tag2时，AMF则向Tag1和Tag2发送读、写或灭活的指令信息以获取Tag1和Tag2的操作信息并缓存。在此仅示例性说明，并不具体限定。
另外，操作类型为盘存时，操作信息包括：盘存成功的第一终端的标识，操作类型为读时，操作信息包括：读成功的第一终端的标识、读的数据。
其中，根据实际业务需要，核心网设备除了可发送多个完成操作的终端的操作信息之外，也可以把未完成操作的终端的操作信息发送给业务请求方。此外，完成操作的终端的操作信息与未完成操作的终端的操作信可以一起发送，也可以分开发送，本申请在此不具体限定。例如，上述步骤608A中，操作信息包括盘存成功的第一终端的标识为Tag1的标识、Tag2的标识，盘存失败的第一终端的标识为Tag3的标识。例如，上述步骤608B中，操作信息包括读成功的第一终端的标识为Tag1的标识、Tag2的标识，读失败的第一终端的标识为Tag3的标识。
另外，在操作类型为写时，写失败的第一终端的标识可能不反馈信息，仅写成功的第一终端的标识反馈信息，或者不反馈写的结果信息。在操作类型为灭活时，灭活成功的第一终端的标识可能不能与AMF交互信息，因此不反馈信息，灭活失败的第一终端的标识可能可以与AMF交互信息，因此反馈信息，另一种可能是不反馈灭活的结果信息。本申请在此不具体限定。
步骤609，AMF确定第一终端中已有多个终端完成操作。
在一种可选的实施方式中，可通过步骤609A来确定，步骤609A，AMF确定到达操作时间阈值，则确定第一终端中已有多个终端完成操作。在另一种可选的实施方式中，第一消息还包括：操作时间阈值；可通过步骤609B～步骤609C确定，步骤609B，AMF接收来自RAN的第三消息，第三消息用于指示到达操作时间阈值；步骤609C，AMF根据第三消息确定第一终端中已有多个终端完成操作。
步骤610，AMF向RAN发送第四消息，第四消息指示RAN结束执行随机接入流程。
其中，步骤610为可选的步骤，在实际应用时，AMF可选择执行。也可RAN自行确定到达操作时间阈值，结束执行随机接入流程，本申请在此不具体限定。
步骤611，AMF向AF发送第一终端中多个终端的操作信息。
之后，AMF可执行下一批终端的操作流程。
本申请，在企业对区域盘存的业务场景中提供一种批量操作的方法，其中包括批量操作的触发条件、判断随机接入的标签是否符合要求的方法、基站的透传方法等，节省了信令开销以及终端响应时间，节约终端的能源。
情况二、请求信息包括第一终端的标识不包括第一地理范围
图7中以终端为Tag1、Tag2、Tag3(在此仅以三个终端为例来说明，但是实际应用时并不限定终端的数量，在执行本申请的方案前，标签打印方Tag Printer会提前向Tag1、Tag2、Tag3写入Tag标识)、接入网设备为RAN、核心网设备为AMF、业务请求方为AF以及NEF为例来说明，当然，在实际应用时，上述的业务请求方可能为多个，服务某个业务请求方的核心网设备(例如企业A分布在不同的地区，服务于企业A的地区1的终端的核心网设备为AMF1，服务于企业A的地区2的终端的核心网设备为AMF2)以及接入网设备可能也存在多个。如下所述：
步骤701，AF通过NEF向AMF发送请求信息，请求信息中包括业务请求方的标识以及第一终端的标识。
步骤702，AMF基于请求信息确定批量执行操作，并对第一终端执行操作。
可参照上述步骤503的描述来理解如何确定批量执行操作，以及具体如何确定第一终端以及批量操作的操作类型，在此不赘述。
下述步骤703～步骤708B具体介绍如何对第一终端执行操作。
步骤703，AMF确定第一消息，第一消息包括：操作指令、X组掩码范围，X≥1，操作指令触发RAN触发多次随机接入流程，操作指令是根据操作类型确定的。
其中，操作指令可参照上述步骤603来理解，在此不赘述。
其中，每组掩码范围对应执行相同的操作类型的第一终端的标识。掩码范围主要是为了防止RAN直接识别终端的标识，保证信息交互的安全性，同时可以在后续的操作中指示RAN对一定范围内的标签执行操作。掩码范围根据第一终端的标识确定，如对上述表2中>100&<200的终端的标识对应的掩码范围为0000 0XXX，对上述表2中<50的终端的标识构造另一组掩码范围0000 00XX，在此仅示例性 描述，并不具体限定掩码范围的形式。此外，AMF在确定了掩码范围后，在后续的步骤中，若当前执行随机接入的第一终端的标识为第X组掩码范围对应的最后一个第一终端的标识，则AMF确定第一终端均完成批量操作。
步骤704，AMF发送第一消息至服务第一终端的RAN。
步骤705，AMF指示RAN根据操作指令对X组掩码范围下的终端逐个执行随机接入流程。
步骤706A，Tag1上报Tag1的标识至RAN。
步骤706B，Tag2上报Tag2的标识至RAN。
步骤706C，Tag3上报Tag3的标识至RAN。
需要注意的是，上述的步骤706A～步骤706C中，RAN可仅作透传转发，具体地，在Tag执行盘存操作时，可在Tag执行一次透传之后，对下一个Tag进行随机接入，接收下一个Tag上报的标识，例如，在执行盘存操作时，确定步骤706A中Tag1执行一次透传之后，再进行随机接入流程，执行步骤706B的操作，在Tag2执行一次透传之后，再进行随机接入理财，执行步骤706C的操作。在Tag执行读、写、灭活操作时，可在Tag执行三次透传之后，若无来自AMF的其他指示，则进行随机接入流程，接收下一个Tag上报的标识，例如，在执行盘存操作时，确定步骤706A中Tag1执行三次透传之后，再执行步骤706B的操作，在Tag2执行三次透传之后，再执行步骤706C的操作。RAN也可缓存Tag标识后，在自行判断所有的Tag已经完成接入后(如到达操作时间阈值)，在将缓存的标识上报至AMF。需要注意的是，RAN不感知Tag的具体信息，且随机接入流程后透传的Tag标识信息并不按某种顺序固定，此处仅作实例。
另一种可能的情况是，该终端的操作信息暂存在RAN上，当AMF或RAN判断终端的操作生命周期结束后，由RAN统一将终端的操作信息发送给AMF。
步骤707，RAN向AMF发送第二消息，该第二消息包括第二终端的标识(也即Tag1的标识、Tag2的标识、Tag3的标识)。
步骤708A，操作类型为盘存时，AMF确定第二终端为第一终端中的一个，则缓存所第二终端的标识。
步骤708B，操作类型为读、写或灭活时，AMF确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
若不是，则指示RAN对下一个Tag进行随机接入。
上述的步骤708A和708B可根据实际的操作类型选择执行，本申请在此不具体限定。具体地，若第一终端的标识包括Tag1的标识、Tag2的标识、Tag4的标识、Tag5的标识、Tag6的标识。Tag1的标识、Tag2的标识属于第一终端的标识，则在步骤708A中缓存Tag1的标识、Tag2的标识，在步骤708B中，向Tag1的标识、Tag2的标识发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
此外，可参考上述的608A和608B的描述理解操作信息，在此不赘述。
步骤709，AMF确定第二终端中已有多个终端完成操作。
在一种可选的实施方式中，可通过步骤709A来确定，步骤709A，AMF确定到达操作生命周期，则确定第二终端中已有多个终端批量执行操作，操作生命周期至少包括以下中的一种：操作次数阈值、操作时间阈值、X组掩码范围。例如，操作时间阈值为T1，则在T1时间内执行批量管理操作，时间超过T1则不执行批量管理的操作，或者，操作次数阈值为Y次(主要是基于掩码范围确定的操作次数阈值，如掩码范围对应的标签为10，那么操作次数阈值可以设置为10)，在Y次内执行批量管理操作，次数超过Y则不执行批量管理的操作。需要注意的是，在进行时间或次数的计数时，可以正向计数，如从0时刻计时到T1时刻/从0次计数至Y次，或者反向计数，如从T1时刻倒计时到0时刻/从Y次倒数至0次，本申请在此不具体限定。AMF在确定了掩码范围后，当前执行随机接入的第一终端的标识为第X组掩码范围对应的最后一个第一终端的标识，则AMF确定第一终端均完成操作。
在另一种可选的实施方式中，第一消息还至少包括以下中的一种：操作次数阈值、操作时间阈值；可通过步骤709B～步骤709C确定，步骤709B，AMF接收来自RAN的第三消息，第三消息用于指示到达操作次数阈值，和/或，操作时间阈值，步骤709C，AMF根据第三消息确定第一终端中已有多个终端完成操作。
步骤710，AMF向RAN发送第四消息，第四消息指示RAN结束执行随机接入流程。
其中，步骤710为可选的步骤，在实际应用时，AMF可选择执行，也可RAN自行结束执行随机接 入流程，本申请在此不具体限定。
步骤711，AMF向AF发送第一终端中多个终端的操作信息。
之后，AMF可执行下一批终端的批量操作流程。
本申请可实现对多个终端的批量操作，而非仅针对一个终端执行同样的操作，可实现对终端的批量管理，且并非终端完成一次随机接入立刻上报操作信息，而是在业务请求方对应的终端完成随机接入后，上报操作信息，通过该方式可以减少操作信令，提高数据处理效率。
上述主要从设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，各个设备可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
在采用集成的单元的情况下，图8示出了本申请实施例中所涉及的通信装置的可能的示例性框图。如图8所示，通信装置800可以包括：处理单元801和收发单元802。处理单元801用于对通信装置800的动作进行控制管理。收发单元802用于支持通信装置800与其他设备的通信。可选地，收发单元802可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。可选的，通信装置800还可以包括存储单元，用于存储通信装置800的程序代码和/或数据。所述收发单元可以称为输入输出单元、通信单元等，所述收发单元可以是收发器；所述处理单元可以是处理器。当通信装置是通信设备中的模块(如，芯片)时，所述收发单元可以是输入输出接口、输入输出电路或输入输出管脚等，也可以称为接口、通信接口或接口电路等；所述处理单元可以是处理器、处理电路或逻辑电路等。具体地，该装置可以为上述的接入网设备、第一核心网设备等。
在一种实施例中，收发单元802，用于获取业务请求方的请求信息，请求信息包括业务请求方的标识；处理单元801，用于基于请求信息确定批量执行操作，并对第一终端执行操作；处理单元801，确定第一终端中已有多个终端完成操作后，收发单元802发送多个终端的操作信息至业务请求方，第一终端为待操作的终端。
在一种可选的方式中，请求信息还包括以下中的至少一种：
第一终端所处的第一地理范围、第一终端的标识、操作类型指示信息。
在一种可选的方式中，请求信息为业务请求方的标识时，处理单元801，确定批量执行操作，第一终端为业务请求方的签约终端。
在一种可选的方式中，请求信息包括业务请求方的标识以及第一地理范围时，处理单元801，确定批量执行操作，第一终端为第一地理范围覆盖下的业务请求方的签约终端。
在一种可选的方式中，请求信息为业务请求方的标识、第一终端的标识以及与第一终端对应的操作类型指示信息，且相同的操作类型指示信息对应第一终端中的多个终端的标识时，处理单元801，确定批量执行操作。
在一种可选的方式中，请求信息为业务请求方的标识、第一终端所处的第一地理范围及操作类型指示信息时，处理单元801，确定批量执行操作。
在一种可选的方式中，请求信息为业务请求方的标识，处理单元801，根据业务请求方的标识获取业务请求方的签约数据，签约数据包括：业务请求方与操作类型的对应关系、业务请求方与第二地理范围的对应关系；根据签约数据对第二地理范围覆盖下的多个终端执行相应操作类型的批量操作。
在一种可选的方式中，请求信息还包括：操作类型指示信息时，批量操作的操作类型是根据操作类型的指示信息确定的。
在一种可选的方式中，收发单元802，用于发送第一消息至服务第一终端的接入网设备，第一消息包括：操作指令、指示标识，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的，指示标识与业务请求方的标识存在关联关系；处理单元801，指示接入网设备根据操作指令 对接入网设备下的终端逐个执行随机接入流程；收发单元802，接收来自接入网设备的第二消息，第二消息包括：第二终端的标识和指示标识；操作类型为盘存时，处理单元801，根据指示标识确定第二终端为第一终端中的一个，则缓存第二终端的标识；或，操作类型为读、写或灭活时，处理单元801，根据指示标识确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
在一种可选的方式中，处理单元801，用于根据第一指示标识查询核心网设备预存的业务请求方的签约终端的标识列表；在确定标识列表包括第二终端的标识时，则确定第二终端为第一终端中的一个。
在一种可选的方式中，收发单元802，用于发送第一消息至服务第一终端的接入网设备，第一消息包括：操作指令、X组掩码范围，X≥1，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的；处理单元801，指示接入网设备根据操作指令对X组掩码范围下的终端逐个执行随机接入流程；收发单元802，接收来自接入网设备的第二消息，第二消息包括：第二终端的标识；操作类型为盘存时，处理单元801，确定第二终端为第一终端中的一个，则缓存第二终端的标识；或，操作类型为读、写或灭活时，处理单元801，确定第二终端为第一终端中的一个，则通过接入网设备向第二终端发送读、写或灭活的指令信息以获取第二终端的操作信息并缓存。
在一种可选的方式中，处理单元801，用于确定到达操作时间阈值，则确定第一终端中已有多个终端完成操作。
在一种可选的方式中，第一消息还包括：操作时间阈值；收发单元802，用于接收来自接入网设备的第三消息，第三消息用于指示到达操作时间阈值；处理单元801，用于根据第三消息确定第二终端中已有多个终端完成操作。
在一种可选的方式中，处理单元801，用于确定到达操作生命周期，则确定第二终端中已有多个终端完成操作；操作生命周期至少包括以下中的一种：操作次数阈值、X组掩码范围。
在一种可选的方式中，第一消息还至少包括以下中的一种：操作次数阈值、操作时间阈值；收发单元802，用于接收来自接入网设备的第三消息，第三消息用于指示到达操作次数阈值，和/或，操作时间阈值；处理单元801，用于根据第三消息确定第二终端中已有多个终端批量执行操作。
在一种可选的方式中，收发单元802，用于向接入网设备发送第四消息，第四消息指示接入网设备结束执行随机接入流程。
在一种可选的方式中，操作类型为盘存时，操作信息包括：盘存成功的第一终端的标识；或，操作类型为读时，操作信息包括：读成功的第一终端的标识读的数据。
在又一个实施例中，收发单元802，用于接收来自核心网设备的第一消息，第一消息包括操作指令、指示标识，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的，指示标识与业务请求方的标识存在关联关系；处理单元801，用于根据操作指令对接入网设备下的终端逐个执行随机接入流程。
在一种可选的方式中，收发单元802，用于接收来自第二终端的第二终端的标识；向核心网设备发送第二消息，第二消息还包括：第二终端的标识和指示标识。
在一种可选的方式中，第一消息还包括：操作时间阈值，收发单元802，用于向核心网设备发送第三消息，第三消息用于指示到达操作时间阈值。
在一种可选的方式中，收发单元802，用于接收来自核心网设备的第四消息，第四消息指示接入网设备结束执行随机接入流程。
在还一个实施例中，收发单元802，用于接收来自核心网设备的第一消息，第一消息包括操作指令、X组掩码范围，X≥1，操作指令触发接入网设备触发多次随机接入流程，操作指令是根据操作类型确定的；处理单元801，用于根据操作指令对X组掩码范围下的终端逐个执行随机接入流程。
在一种可选的方式中，收发单元802，用于接收来自第二终端的第二终端的标识；向核心网设备发送第二消息，第二消息还包括：第二终端的标识。
在一种可选的方式中，第一消息还至少包括以下中的一种：操作时间阈值、操作时间阈值，收发单元802，用于向核心网设备发送第三消息，第三消息用于指示到达操作时间阈值。
在一种可选的方式中，收发单元802，用于接收来自核心网设备的第四消息，第四消息指示接入网设备结束执行随机接入流程。
如图9所示，为本申请还提供的一种通信装置900。通信装置900可以是芯片或芯片系统。该通信装置可以位于上述任一方法实施例所涉及的设备中，例如接入网设备，或第一核心网设备等，以执行该设备所对应的动作。
可选的，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
通信装置900包括处理器910。
处理器910，用于执行存储器920中存储的计算机程序，以实现上述任一方法实施例中各个设备的动作。
通信装置900还可以包括存储器920，用于存储计算机程序。
可选地，存储器920和处理器910之间耦合。耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。可选的，存储器920与处理器910集成在一起。
其中，处理器910和存储器920均可以为一个或多个，不予限制。
可选的，在实际应用中，通信装置900中可以包括收发器930，也可不包括收发器930，图中以虚线框来示意，通信装置900可以通过收发器930和其它设备进行信息交互。收发器930可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。
在一种可能的实施方式中，该通信装置900可以为上述各方法实施中的接入网设备，或第一核心网设备。
本申请实施例中不限定上述收发器930、处理器910以及存储器920之间的具体连接介质。本申请实施例在图9中以存储器920、处理器910以及收发器930之间通过总线连接，总线在图9中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实施或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实施存储功能的装置，用于存储计算机程序、程序指令和/或数据。
基于以上实施例，参见图10，本申请实施例还提供另一种通信装置1000，包括：接口电路1010和逻辑电路1020；接口电路1010，可以理解为输入输出接口，可用于执行上述任一方法实施例中各个设备的收发步骤，逻辑电路1020可用于运行代码或指令以执行上述任一实施例中各个设备执行的方法，不再赘述。
基于以上实施例，本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有指令，当所述指令被执行时，使上述任一方法实施例中各个设备执行的方法被实施，例如，使得图5所示实施例中RAN或AMF执行的方法被实施。该计算机可读存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例提供一种通信系统，该通信系统包括上述任一方法实施例中提及的接入网设备(例如RAN)、核心网设备(例如AMF)，可用于执行上述任一方法实施例中各个设备执行的方法。
此外，上述通信系统还可以包括终端(例如UE)，该终端可通过与接入网设备、核心网设备进行数据交互，以执行上述任一方法实施例中的相关方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理装置的处理器以产生一个机器，使得通过计算机或其他可编程数据处理装置的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理装置以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理装置上，使得在计算机或其他可编程装置上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程装置上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。

Claims (40)

  1. 一种通信方法，其特征在于，包括：
    核心网设备获取业务请求方的请求信息，所述请求信息包括所述业务请求方的标识；
    所述核心网设备基于所述请求信息确定批量执行操作，并对第一终端执行所述操作，所述第一终端为待操作的终端；
    所述核心网设备确定所述第一终端中已有多个终端完成所述操作后，发送所述多个终端的操作信息至所述业务请求方。
  2. 根据权利要求1所述的方法，其特征在于，所述请求信息还包括以下中的至少一种：
    所述第一终端所处的第一地理范围、所述第一终端的标识、操作类型指示信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述核心网设备基于所述请求信息确定批量执行操作，包括：
    所述请求信息为所述业务请求方的标识时，所述核心网设备确定批量执行操作，所述第一终端为所述业务请求方的签约终端。
  4. 根据权利要求2所述的方法，其特征在于，所述核心网设备基于所述请求信息确定批量执行操作，包括：
    所述请求信息为所述业务请求方的标识及所述第一地理范围时，所述核心网设备确定批量执行操作，所述第一终端为所述第一地理范围覆盖下的所述业务请求方的签约终端。
  5. 根据权利要求2所述的方法，其特征在于，所述核心网设备基于所述请求信息确定批量执行操作，包括：
    所述请求信息为所述业务请求方的标识、所述第一终端的标识以及与所述第一终端对应的所述操作类型指示信息，且相同的所述操作类型指示信息对应所述第一终端中的多个终端的标识时，所述核心网设备确定批量执行操作。
  6. 根据权利要求2所述的方法，其特征在于，所述核心网设备基于所述请求信息确定批量执行操作，包括：
    所述请求信息为所述业务请求方的标识、所述第一终端所处的第一地理范围及所述操作类型指示信息时，核心网设备确定批量执行操作。
  7. 根据权利要求1所述的方法，其特征在于，所述对第一终端执行所述操作，包括：
    所述核心网设备根据所述业务请求方的标识获取所述业务请求方的签约数据，所述签约数据包括：所述业务请求方与操作类型的对应关系、所述业务请求方与第二地理范围的对应关系；
    所述核心网设备根据所述签约数据对所述第二地理范围覆盖下的多个终端执行相应所述操作类型的操作。
  8. 根据权利要求5或6所述的方法，其特征在于，所述操作的操作类型是根据所述操作类型的指示信息确定的。
  9. 根据权利要求6或7所述的方法，其特征在于，所述对第一终端执行所述操作，包括：
    所述核心网设备发送第一消息至所述服务所述第一终端的接入网设备，所述第一消息包括：操作指令、指示标识，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的，所述指示标识与所述业务请求方的标识存在关联关系；
    所述核心网设备指示所述接入网设备根据所述操作指令对所述接入网设备下的终端逐个执行随机接入流程；
    所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括：第二终端的标识和所述指示标识；
    所述操作类型为盘存时，所述核心网设备根据所述指示标识确定所述第二终端为所述第一终端中的一个，则缓存所述第二终端的标识；或，
    所述操作类型为读、写或灭活时，所述核心网设备根据所述指示标识确定第二终端为所述第一终端中的一个，则通过所述接入网设备向所述第二终端发送读、写或灭活的指令信息以获取所述第二终端的操作信息并缓存。
  10. 根据权利要求9所述的方法，其特征在于，所述核心网设备根据所述指示标识确定第二终端为 所述第一终端中的一个，包括：
    所述核心网设备根据所述指示标识查询所述核心网设备预存的所述业务请求方的签约终端的标识列表；
    所述核心网设备在确定所述标识列表包括所述第二终端的标识时，则确定所述第二终端为所述第一终端中的一个。
  11. 根据权利要求5所述的方法，其特征在于，所述对第一终端执行所述操作，包括：
    所述核心网设备发送第一消息至服务所述第一终端的接入网设备，所述第一消息包括：操作指令、X组掩码范围，所述X≥1，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的；
    所述核心网设备指示所述接入网设备根据所述操作指令对所述X组掩码范围下的终端执行逐个随机接入流程；
    所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括：第二终端的标识；
    所述操作类型为盘存时，所述核心网设备确定所述第二终端为所述第一终端中的一个，则缓存所述第二终端的标识；或，
    所述操作类型为读、写或灭活时，所述核心网设备确定第二终端为所述第一终端中的一个，则通过所述接入网设备向所述第二终端发送读、写或灭活的指令信息以获取所述第二终端的操作信息并缓存。
  12. 根据权利要求9-11中任意一项所述的方法，其特征在于，所述核心网设备确定所述第一终端中已有多个终端完成所述操作，包括：
    所述核心网设备确定到达操作时间阈值，则确定所述第一终端中已有多个终端完成所述操作。
  13. 根据权利要求12所述的方法，其特征在于，所述核心网设备确定所述第一终端中已有多个终端完成所述操作，包括：
    所述核心网设备确定到达操作生命周期，则确定所述第一终端中已有多个终端完成所述操作；所述操作生命周期至少包括以下中的一种：操作次数阈值、X组掩码范围。
  14. 根据权利要求1-13中任意一项所述的方法，其特征在于，所述操作类型为盘存时，所述操作信息包括：盘存成功的所述第一终端的标识；或，
    所述操作类型为读时，所述操作信息包括：读成功的所述第一终端的标识、读的数据。
  15. 一种通信方法，其特征在于，包括：
    接入网设备接收来自核心网设备的第一消息，所述第一消息包括操作指令、指示标识，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的，所述指示标识与所述业务请求方的标识存在关联关系；
    所述接入网设备根据所述操作指令对所述接入网设备下的终端逐个执行随机接入流程。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自第二终端的第二终端的标识；
    所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括：第二终端的标识和所述指示标识。
  17. 一种通信方法，其特征在于，包括：
    接入网设备接收来自核心网设备的第一消息，所述第一消息包括操作指令、X组掩码范围，所述X≥1；所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的；
    所述接入网设备根据所述操作指令对所述X组掩码范围下的终端逐个执行随机接入流程。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自第二终端的第二终端的标识；
    所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括：所述第二终端的标识。
  19. 一种通信装置，其特征在于，包括：
    收发单元，用于获取业务请求方的请求信息，所述请求信息包括所述业务请求方的标识；
    处理单元，用于基于所述请求信息确定批量执行操作，并对第一终端执行所述操作，所述第一终端为待操作的终端；
    所述收发单元，还用于确定所述第一终端中已有多个终端完成所述操作后，发送所述多个终端的操作信息至所述业务请求方。
  20. 根据权利要求19所述的装置，其特征在于，所述请求信息还包括以下中的至少一种：
    所述第一终端所处的第一地理范围、所述第一终端的标识、操作类型指示信息。
  21. 根据权利要求19或20所述的装置，其特征在于，所述请求信息为所述业务请求方的标识时，所述处理单元，具体用于：确定批量执行操作，所述第一终端为所述业务请求方的签约终端。
  22. 根据权利要求20所述的装置，其特征在于，所述请求信息为所述业务请求方的标识及所述第一地理范围时，所述处理单元，具体用于：确定批量执行操作，所述第一终端为所述第一地理范围覆盖下的所述业务请求方的签约终端。
  23. 根据权利要求20所述的装置，其特征在于，所述请求信息为所述业务请求方的标识、所述第一终端的标识以及与所述第一终端对应的所述操作类型指示信息，且相同的所述操作类型指示信息对应所述第一终端中的多个终端的标识时，所述处理单元，具体用于：确定批量执行操作。
  24. 根据权利要求20所述的装置，其特征在于，所述请求信息为所述业务请求方的标识、所述第一终端所处的第一地理范围及所述操作类型指示信息时，所述处理单元，具体用于：确定批量执行操作。
  25. 根据权利要求19所述的装置，其特征在于，所述处理单元，具体用于：
    根据所述业务请求方的标识获取所述业务请求方的签约数据，所述签约数据包括：所述业务请求方与操作类型的对应关系、所述业务请求方与第二地理范围的对应关系；
    根据所述签约数据对所述第二地理范围覆盖下的多个终端执行相应所述操作类型的操作。
  26. 根据权利要求23或24所述的装置，其特征在于，所述操作的操作类型是根据所述操作类型的指示信息确定的。
  27. 根据权利要求24或25所述的装置，其特征在于，所述收发单元，还用于发送第一消息至所述服务所述第一终端的接入网设备，所述第一消息包括：操作指令、指示标识，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的，所述指示标识与所述业务请求方的标识存在关联关系；
    所述处理单元，还用于：指示所述接入网设备根据所述操作指令对所述接入网设备下的终端逐个执行随机接入流程；
    所述收发单元，还用于接收来自所述接入网设备的第二消息，所述第二消息包括：第二终端的标识和所述指示标识；
    所述操作类型为盘存时，所述处理单元，具体用于：根据所述指示标识确定所述第二终端为所述第一终端中的一个，则缓存所述第二终端的标识；或，
    所述操作类型为读、写或灭活时，所述处理单元，具体用于：根据所述指示标识确定第二终端为所述第一终端中的一个，则通过所述接入网设备向所述第二终端发送读、写或灭活的指令信息以获取所述第二终端的操作信息并缓存。
  28. 根据权利要求27所述的装置，其特征在于，所述处理单元，具体用于：根据所述指示标识查询所述核心网设备预存的所述业务请求方的签约终端的标识列表；在确定所述标识列表包括所述第二终端的标识时，则确定所述第二终端为所述第一终端中的一个。
  29. 根据权利要求23所述的装置，其特征在于，所述收发单元，还用于发送第一消息至服务所述第一终端的接入网设备，所述第一消息包括：操作指令、X组掩码范围，所述X≥1，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的；
    所述处理单元，还用于：指示所述接入网设备根据所述操作指令对所述X组掩码范围下的终端执行逐个随机接入流程；
    所述收发单元，还用于接收来自所述接入网设备的第二消息，所述第二消息包括：第二终端的标识；
    所述操作类型为盘存时，所述处理单元，还用于：确定所述第二终端为所述第一终端中的一个，则缓存所述第二终端的标识；或，
    所述操作类型为读、写或灭活时，所述处理单元，还用于：确定第二终端为所述第一终端中的一个，则通过所述接入网设备向所述第二终端发送读、写或灭活的指令信息以获取所述第二终端的操作信息并缓存。
  30. 根据权利要求27-29中任意一项所述的装置，其特征在于，所述处理单元，还用于：确定到达操作时间阈值，则确定所述第一终端中已有多个终端完成所述操作。
  31. 根据权利要求30所述的装置，其特征在于，所述处理单元，还用于：确定到达操作生命周期， 则确定所述第一终端中已有多个终端完成所述操作；所述操作生命周期至少包括以下中的一种：操作次数阈值、X组掩码范围。
  32. 根据权利要求19-31中任意一项所述的装置，其特征在于，所述操作类型为盘存时，所述操作信息包括：盘存成功的所述第一终端的标识；或，
    所述操作类型为读时，所述操作信息包括：读成功的所述第一终端的标识、读的数据。
  33. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自核心网设备的第一消息，所述第一消息包括操作指令、指示标识，所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的，所述指示标识与所述业务请求方的标识存在关联关系；
    处理单元，用于根据所述操作指令对所述接入网设备下的终端逐个执行随机接入流程。
  34. 根据权利要求33所述的装置，其特征在于，
    所述收发单元，还用于接收来自第二终端的第二终端的标识；
    所述收发单元，还用于向所述核心网设备发送第二消息，所述第二消息包括：第二终端的标识和所述指示标识。
  35. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自核心网设备的第一消息，所述第一消息包括操作指令、X组掩码范围，所述X≥1；所述操作指令触发所述接入网设备触发多次随机接入流程，所述操作指令是根据操作类型确定的；
    处理单元，用于根据所述操作指令对所述X组掩码范围下的终端逐个执行随机接入流程。
  36. 根据权利要求35所述的装置，其特征在于，所述收发单元，还用于接收来自第二终端的第二终端的标识；
    所述收发单元，还用于向所述核心网设备发送第二消息，所述第二消息包括：所述第二终端的标识。
  37. 一种通信装置，其特征在于，包括：至少一个处理器和存储器；
    所述存储器，用于存储计算机程序或指令；
    所述至少一个处理器，用于执行所述计算机程序或指令，以使得如权利要求1-18中任一项的方法被执行。
  38. 一种芯片系统，其特征在于，所述芯片系统包括：处理电路；所述处理电路与存储介质耦合；
    所述处理电路，用于执行所述存储介质中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现如权利要求1-18中任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被计算机执行时，使得如权利要求1-18中任一项所述的方法被执行。
  40. 一种包含计算机程序或指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得上述权利要求1-18中任一项所述的方法被执行。
PCT/CN2023/120853 2022-09-27 2023-09-22 一种通信方法及装置 WO2024067421A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211185417.0 2022-09-27
CN202211185417.0A CN117793733A (zh) 2022-09-27 2022-09-27 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2024067421A1 true WO2024067421A1 (zh) 2024-04-04

Family

ID=90400541

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/120853 WO2024067421A1 (zh) 2022-09-27 2023-09-22 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN117793733A (zh)
WO (1) WO2024067421A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112567684A (zh) * 2018-08-13 2021-03-26 瑞典爱立信有限公司 支持核心网络中订阅事件的方法、设备和计算机可读介质
CN113923800A (zh) * 2020-07-08 2022-01-11 华为技术有限公司 一种通信方法及装置
CN114007192A (zh) * 2021-02-26 2022-02-01 中国移动通信有限公司研究院 一种终端接入处理方法、设备及存储介质
CN114095987A (zh) * 2021-11-22 2022-02-25 中国联合网络通信集团有限公司 一种业务处理方法、装置及存储介质
US20220232504A1 (en) * 2021-01-19 2022-07-21 Samsung Electronics Co., Ltd. Uplink transmission timing in non-terrestrial networks
CN116567780A (zh) * 2022-01-30 2023-08-08 华为技术有限公司 终端管理方法和核心网设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112567684A (zh) * 2018-08-13 2021-03-26 瑞典爱立信有限公司 支持核心网络中订阅事件的方法、设备和计算机可读介质
CN113923800A (zh) * 2020-07-08 2022-01-11 华为技术有限公司 一种通信方法及装置
US20220232504A1 (en) * 2021-01-19 2022-07-21 Samsung Electronics Co., Ltd. Uplink transmission timing in non-terrestrial networks
CN114007192A (zh) * 2021-02-26 2022-02-01 中国移动通信有限公司研究院 一种终端接入处理方法、设备及存储介质
CN114095987A (zh) * 2021-11-22 2022-02-25 中国联合网络通信集团有限公司 一种业务处理方法、装置及存储介质
CN116567780A (zh) * 2022-01-30 2023-08-08 华为技术有限公司 终端管理方法和核心网设备

Also Published As

Publication number Publication date
CN117793733A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
US11297660B2 (en) Session management with relaying and charging for indirect connection for internet of things applications in 3GPP network
EP3993347A1 (en) Method and device for application migration
US20210044454A1 (en) Communication Method and Device
JP6275768B2 (ja) マシンタイプ通信事前登録
JP5827359B2 (ja) マシンツーマシン通信登録のための方法および装置
US11706321B2 (en) System and method for using T8 API to deliver data over an IP path
US20220103990A1 (en) Communication Method, Apparatus, and System
WO2022017285A1 (zh) 报文转发方法、装置及系统
CN113260014B (zh) 一种物联网iot设备自动接入无线局域网wlan的方法以及装置
EP2884779A1 (en) Message processing method in coexistence of multiple external identifiers of terminal and network side device
US20220210702A1 (en) Communication Method and Apparatus
CN114424634A (zh) 使用多个sim的服务提供方法和设备
CN102057719B (zh) 通信系统
US20240072882A1 (en) Information transmission method and system, and apparatus
WO2024067421A1 (zh) 一种通信方法及装置
WO2023071770A1 (zh) 获取数据分析结果的方法及通信装置
WO2024067706A1 (zh) 一种通信方法及通信装置
WO2019136695A1 (zh) 一种数据传输方法及装置、计算机存储介质
WO2021081712A1 (zh) 一种dns查询方法及装置
WO2024078305A1 (zh) 通信方法、通信装置及通信系统
WO2024067046A1 (zh) 一种通信方法及装置
WO2024021935A1 (zh) 一种通信方法及装置
WO2023246431A1 (zh) 一种通信方法和装置
WO2023071979A1 (zh) 一种寻呼方法及装置
WO2024066417A1 (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: 23870652

Country of ref document: EP

Kind code of ref document: A1