WO2022222674A1 - 消息处理方法和装置、电子设备、计算机可读存储介质 - Google Patents

消息处理方法和装置、电子设备、计算机可读存储介质 Download PDF

Info

Publication number
WO2022222674A1
WO2022222674A1 PCT/CN2022/082427 CN2022082427W WO2022222674A1 WO 2022222674 A1 WO2022222674 A1 WO 2022222674A1 CN 2022082427 W CN2022082427 W CN 2022082427W WO 2022222674 A1 WO2022222674 A1 WO 2022222674A1
Authority
WO
WIPO (PCT)
Prior art keywords
registration request
entity
equal
message
messages
Prior art date
Application number
PCT/CN2022/082427
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 WO2022222674A1 publication Critical patent/WO2022222674A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present application relates to the field of communications, and in particular, to a message processing method and apparatus, an electronic device, and a computer-readable storage medium.
  • the fifth-generation mobile communication technology (5G, 5th Generation) core network ( 5GC , 5G Core Network) adopts a service-based architecture (SBA, Service Based Architecture), and all network function (NF, Network Function) entities in 5GC can be It is divided into two categories: service producers and service consumers.
  • the service producer needs to register with the Network Repository Function (NRF, Network Repository Function) entity.
  • the current registration method makes the NF entity as the service producer occupy too much network bandwidth resources during the registration process, which affects the sending and receiving of ordinary messages, resulting in chain links. Road congestion, and even network paralysis.
  • the present application provides a message processing method and apparatus, an electronic device, and a computer-readable storage medium.
  • An embodiment of the present application provides a message processing method, including: sending N first registration request messages to an NRF entity, where N is an integer greater than or equal to 1, and for a second registration request message that needs to be sent to the NRF entity Splitting to obtain the N first registration request messages, and the information amount of each of the first registration request messages is less than or equal to the first preset threshold, and the first registration request messages sent twice adjacently The time interval between them is greater than or equal to the second preset threshold.
  • An embodiment of the present application further provides a message processing apparatus, including: a sending module, configured to send N first registration request messages to an NRF entity, where N is an integer greater than or equal to 1, and a message that needs to be sent to the NRF entity
  • the second registration request message is split to obtain the N first registration request messages, and the information amount of each of the first registration request messages is less than or equal to the first preset threshold, and the number of the two consecutively sent
  • the time interval between the first registration request messages is greater than or equal to the second preset threshold.
  • Embodiments of the present application further provide an electronic device, including: at least one processor; and a memory, where at least one program is stored, and when the at least one program is executed by the at least one processor, the at least one program according to the present application is implemented. message handling method.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the message processing method according to the present application is implemented.
  • FIG. 1 is a schematic diagram of a communication system interaction in the related art
  • FIG. 2 is a schematic diagram of registration interaction in the related art
  • Fig. 3 is the service discovery interaction schematic diagram of the related art
  • FIG. 5 is an interactive schematic diagram of a message processing method provided by the present application.
  • FIG. 6 is a schematic diagram of service discovery interaction provided by the present application.
  • FIG. 9 is another schematic diagram of interaction of the message processing method provided by the present application.
  • FIG. 10 is a block diagram of the composition of the message processing apparatus provided by the present application.
  • FIG. 1 is a schematic diagram of interaction of a communication system in the related art.
  • the communication system includes: a first NF entity, an NRF entity and a second NF entity.
  • the first NF entity acts as a service producer, and the second NF entity acts as a service consumer.
  • the role of a single NF entity can be switched back and forth between service producers and service consumers.
  • the process of registering with the NRF entity by the first NF entity as a service producer generally includes: the first NF entity sends a registration request message to the NRF entity; and the first NF entity receives a registration response message sent by the NRF entity.
  • the registration request message carries the NF profile (NFProfile) parameter in the JS object notation (JSON, JavaScript Object Notation) format of the first NF entity.
  • NFProfile NF profile
  • JSON JavaScript Object Notation
  • the configuration parameter may carry at least one of the following range lists of services provided by the first NF entity: User Permanent Identifier (SUPI, Subscription Permanent Identifier) Range List (SUPIRanges); Generic Public User Identifier (GPSI, Generic Public Subscription Identifier) Range List (GPSIRanges); User Internet Protocol Version 4 (IPv4, Internet Protocol Version 4) Address Range List (IPv4AddressRanges); User Internet Protocol Version 6 (IPv6, Internet Protocol Version 6) Prefix Range List (IPv6PrefixRanges); and Tracking Area Identification (TAI, Tracking Area Identity) range list.
  • SUPI User Permanent Identifier
  • GPSI Generic Public User Identifier
  • GPSIRanges Generic Public Subscription Identifier
  • Range List GPSIRanges
  • IPv4AddressRanges User Internet Protocol Version 6
  • IPv6PrefixRanges Prefix Range List
  • TAI Tracking Area Identification
  • SUPI range list is in JSON array format and includes two SUPI ranges, that is, the SUPI range list size is 2, and each SUPI range contains a start ( start) field and an end (end) field.
  • the formats of the GPSI range list, the user IPv4 address range list, the user IPv6 prefix range list, and the TAI range list are similar, except that the value formats of the list name, start field, and end field are different.
  • the specific scope list carried in the registration request message is related to the type of the first NF entity.
  • PCF Policy Control Function
  • BSF Binding Support Function
  • FIG. 2 is a schematic diagram of registration interaction in the related art.
  • the registration request message only carries the SUPI range list, and other types of range lists may also be carried in actual situations. It is assumed that the first NF entity corresponds to 10,000 SUPI ranges, so the NFProfile parameter in the registration request message sent by the first NF entity will carry the 10,000 SUPI ranges and other configuration parameters. According to estimation, the entire registration request message is a super-long message with a length of about 700KB.
  • each independently deployed NF entity only sends a registration request message to the NRF entity. Since the current operator implements the regional system, the number of mobile users served by a single NF entity is huge. For appropriate reasons (for example, the number segment is too scattered, etc.), the number of range lists of the NFProfile parameters in the registration request message may be very large, for example, thousands or even tens of thousands of range lists, and the NFProfile parameters are in plain text format. , so that the registration request message may become a super-long message of several hundreds of kilobytes (KB, Kilobyte) or even several megabytes (MB, Megabyte).
  • HTTP/2 Hypertext Transfer Protocol 2
  • SBI Service Based Interface
  • TCP transport layer control protocol
  • TCP Transmission Control Protocol
  • the registration response message returned by the first NRF entity also needs to carry the NFProfile parameter in the registration request message. All in all, the current registration method causes the first NF entity to occupy too much network bandwidth resources during the registration process, which affects the sending and receiving of ordinary messages, leads to link congestion, and even network paralysis.
  • the first NF entity needs to process the super-long message, it will also occupy more central processing unit (CPU, Center Processing Unit) resources, resulting in a decrease in the processing efficiency of the first NF entity.
  • CPU Central Processing Unit
  • the second NF entity when the second NF entity as a service consumer needs to invoke services provided by other NF entities, it needs to perform service discovery to the NRF entity, that is, the second NF entity sends a discovery request message to the NRF entity; and the second NF entity receives the NRF entity
  • the discovery response message sent by the entity, the discovery response message carries the NFProfile parameter of the NF entity of the qualified service producer.
  • the discovery request message sent by the second NF entity to the NRF entity for the first time carries SUPI A
  • the discovery request message sent to the NRF entity for the second time carries SUPI B
  • SUPI A falls in the first Within the first SUPI range corresponding to the NF entity
  • SUPI B falling within the 10,000th SUPI range corresponding to the first NF entity
  • the discovery response message returned by the NRF entity twice will carry the complete NFProfile parameter, which includes The range of 10,000 SUPIs corresponding to the first NF entity, that is to say, if any SUPI that falls within the range of 10,000 SUPIs is used for service discovery, the returned discovery response message will be a super-long message with a length of about 700KB .
  • an NF entity refers to an NF instance of a service function provided to a user.
  • the registration request message, registration response message, discovery request message, and discovery response message in the embodiments of the present application are all transmitted in the network in the form of messages, and messages whose total length exceeds 64 KB are generally considered to be super-long messages.
  • the message processing method of the present application can be applied to any network including the first NF entity, the NRF entity and the second NF entity, for example, can be applied to the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) protocol, using The 5GC control plane network implemented by the SBA architecture can also be applied to future networks.
  • 3GPP 3rd Generation Partnership Project
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • FIG. 4 is a flowchart of a message processing method provided by the present application.
  • the present application provides a message processing method, which is applied to a first NF entity, and the method includes steps 400 to 401 .
  • N first registration request messages are sent to the NRF entity, where N is an integer greater than or equal to 1.
  • N first registration request messages are obtained by splitting the second registration request message to be sent to the NRF entity.
  • the amount of information of each first registration request message is less than or equal to the first preset threshold, and the time interval between the first registration request messages sent twice in succession is greater than or equal to the second preset threshold.
  • the second registration request message that needs to be sent to the NRF entity is the registration request message in the related art described above. It can be seen from the preceding description that the second registration request message is an over-long message.
  • the processing of over-long messages requires too much network bandwidth resources, which affects the sending and receiving of ordinary messages, resulting in link congestion and even network congestion.
  • the processing efficiency of the first NF entity is reduced due to the need to process the super-long message, which also occupies more CPU resources.
  • the registration request message may be first determined whether the second registration request message to be sent to the NRF entity is an oversized message, and if the second registration request message to be sent to the NRF entity is an oversized message, the second registration request message to be sent to the NRF entity is an oversized message.
  • the registration request message is divided into N first registration request messages, so that the information amount of each first registration request message is less than or equal to the first preset threshold, and then N first registration request messages are sent to the NRF entity.
  • the second registration request message is not a super-long message
  • a time interval may be preset, and N first registration request messages are sequentially sent to the NRF entity according to the preset time interval.
  • the time interval can be configured between 10 milliseconds and 10,000 milliseconds, which can be determined according to the total duration of the registration process and anti-shock requirements. Determine the specific value, for example, you can configure the time interval to 100 milliseconds.
  • the information amount of each first registration request message is less than or equal to the first preset threshold may include the following situations: the number of ranges included in the configuration parameters carried in each first registration request message is less than or equal to the third preset threshold ; Or each range quantity contained in the configuration parameter carried in each first registration request message is less than or equal to the fourth preset threshold; or the length of the configuration parameter carried in each first registration request message is less than or equal to is equal to the fifth preset threshold; or the length of each first registration request message is less than or equal to the sixth preset threshold.
  • the information amount of each first registration request message described above is less than or equal to the first preset threshold may mean: the number of ranges included in the configuration parameters carried in each first registration request message is less than or equal to is equal to the third preset threshold, thereby indirectly reflecting that the information amount of each first registration request message is less than or equal to the first preset threshold; or each of the configuration parameters carried in each first registration request message contains The number of ranges is less than or equal to the fourth preset threshold, thereby indirectly reflecting that the information amount of each first registration request message is less than or equal to the first preset threshold; or the configuration parameters carried in each first registration request message The lengths are all less than or equal to the fifth preset threshold, thereby indirectly reflecting that the information amount of each first registration request message is less than or equal to the first preset threshold; or the length of each first registration request message is less than or equal to the first Six preset thresholds, thereby indirectly reflecting that the information amount of each first registration request message is less than or equal to the first preset threshold.
  • the configuration parameters carried in the first registration request message may include the aforementioned NFProfile parameters.
  • the third preset threshold does not limit the specific value of the third preset threshold.
  • the number of ranges included in the configuration parameters carried in each first registration request message is between 100 and 5000.
  • the third preset threshold can be set to Configured to 500.
  • the SUPI range list including 10,000 SUPI ranges can be split into 20 SUPI range lists, each of which is a SUPI range list Including 500 SUPI ranges, and then including 500 SUPI ranges in the NFProfile parameter carried in each first registration request message, so that each first registration request message and registration response message becomes a short message of about 35KB, The size is 1/20 of the original.
  • Each first registration request message sent by the first NF entity can be regarded as a registration request message sent by a virtual NF entity, that is, a first NF entity externally appears as multiple virtual NF entities.
  • a first NF entity is represented as 20 virtual NF entities.
  • the second NF entity uses the user-related parameters (that is, the SUPI of the terminal) to perform service discovery to the NRF entity, still taking the above discovery conditions SUPI A and SUPI B as examples, as shown in Figure 6, the second NF The entity sends a discovery request message 1 to the NRF entity, and the discovery request message 1 carries SUPI A; the discovery response message 1 returned by the NRF to the second NF entity carries the NFProfile parameter including the SUPI range where SUPI A is located, and the NFProfile parameter only includes 500 Similarly, the second NF entity sends a discovery request message 2 to the NRF entity, and the discovery request message 2 carries SUPI B; the discovery response message 2 returned by the NRF to the second NF entity carries the SUPI range that includes SUPI B.
  • the NFProfile parameter which also includes only 500 SUPI ranges. In this way, each discovery response message is a message of about 35KB, and the length is only 1/20 of the original.
  • the length of the configuration parameter carried in each first registration request message is between 16KB and 128KB.
  • the fifth preset threshold can be configured as 32KB. .
  • the length of the NFProfile parameter carried in the second registration request message is less than or equal to 32KB. If the total length of the NFProfile parameter is greater than 32KB, it is necessary to Split multiple first registration request messages with NFProfile parameters less than or equal to 32KB. In the splitting process, the integrity of the grammar must be guaranteed, and the parameters cannot be missing. That is to say, the NFProfile should be guaranteed during the splitting process.
  • the parameter contains an integer number of SUPI ranges. For example, to register by setting the maximum length of the NFProfile parameter to 32KB, the process is shown in Figure 7. The original super-long packet of about 750KB is split into multiple short packets carrying the NFProfile parameter less than or equal to 32KB. And after each sending a first registration request message, wait according to the configured time interval, and then send the next first registration request message.
  • the sixth preset threshold does not limit the specific value of the sixth preset threshold.
  • the length of each first registration request message is between 16KB and 128KB.
  • the sixth preset threshold can be configured as 32KB.
  • the scope included in the configuration parameter carried in the first registration request message may include at least one of the following: SUPI scope; GPSI scope; user IPv4 address scope; user IPv6 prefix scope; and TAI scope.
  • the configuration parameters carried in the first registration request message may only include any one of the above ranges, or may include two or more of the above ranges, and which parameters and NF types are specifically carried related.
  • the NFProfile parameter carried in the first registration request message includes both the SUPI range and the GPSI range.
  • the maximum number of each range can be reasonably configured to control the total number of ranges included in the NFProfile parameter. For example, if the maximum number of SUPI ranges and GPSI ranges contained in the NFProfile parameter carried in each first registration request message is configured to be 250, then when the SUPI range or GPSI range contained in the NFProfile parameter carried in the second registration request message is configured The number exceeds 250, or when the number of the SUPI range and the GPSI range contained in the NFProfile parameter carried in the second registration request message exceeds 250 at the same time, each first registration request message is split.
  • the NFProfile parameter carried in the original second registration request message includes 10,000 SUPI ranges and 10,000 GPSI ranges
  • each NFProfile parameter carried in the second registration request message contains both 10,000 user IPv4 address ranges and 1 10,000 user IPv6 prefix ranges can be divided into 34 first registration request messages.
  • the NFProfile parameters carried in the first 33 first registration request messages include 300 IPv4 address ranges and 300 IPv6 prefix ranges.
  • the NFProfile parameter carried in the registration request message includes 100 IPv4 address ranges and 100 IPv6 prefix ranges, as shown in Figure 9.
  • the ranges included in the configuration parameters carried in the first registration request message are all ranges corresponding to the services provided by the first NF entity, and the services here refer to services for terminals.
  • the configuration parameters carried in the first registration request message may include virtual NF entity identifiers, and the virtual NF entity identifiers included in configuration parameters carried in different first registration request messages sent by the same first NF entity are different.
  • a virtual NF entity identifier pool may be pre-configured for the first NF entity, including M virtual NF entity identifiers, and each time the first NF entity sends a first registration request message, it applies for a virtual NF entity from the virtual NF entity identifier pool logo.
  • the specific value of M can be determined according to the specific situation, and it is necessary to ensure that the virtual NF entity identifier is globally unique.
  • the ranges of virtual NF entity identifier pools configured for different first NF entities cannot overlap each other. That is, each virtual NF entity identifier pool configured for the first NF instance must NF entity identifiers are globally unique.
  • each first registration request message sent by the first NF entity can be regarded as a registration request message sent by a virtual NF entity, that is, a first registration request message sent by a virtual NF entity
  • the NF entity is externally represented as multiple virtual NF entities, and the registration process of each virtual NF entity is the same as the registration process of the first NF entity in the related art, except that the length of the sent registration request message is different.
  • the length of the first registration request message sent by the virtual NF entity of the present application is short, does not occupy too much network bandwidth resources, reduces the impact on the sending and receiving of ordinary messages, ensures smooth links, saves CPU resources, and improves processing efficiency.
  • step 401 receiving N registration response messages returned by the NRF entity, wherein the N first registration request messages are the same as the The N registration response messages are in one-to-one correspondence.
  • the corresponding first registration request message and the configuration parameter carried in the registration response message contain the same number of ranges.
  • the first registration request message corresponds to the registration response message means that the registration response message is a reply message for the first registration request message.
  • N first registration request messages are obtained by splitting the second registration request message that needs to be sent to the NRF entity, the second registration request message is a super-long message, and each obtained by splitting The lengths of the first registration request messages are all less than or equal to the first preset threshold, and the time interval between the first registration request messages sent twice adjacently is greater than or equal to the second preset threshold, that is, the second
  • the registration request message is split into N short messages, and the N short messages are sent discretely in time, so that the network bandwidth resources occupied by sending the N first registration request messages are more than those occupied by sending the second registration request message.
  • the network bandwidth resource occupied is much less, which reduces the impact on the sending and receiving of ordinary messages, ensures smooth links, saves CPU resources, and improves processing efficiency.
  • the discovery response message returned by the NRF entity to the second NF entity also becomes a short ordinary message, so that the The network bandwidth resources occupied in the service discovery process are also relatively reduced, which reduces the impact on the sending and receiving of ordinary messages, ensures smooth links, saves CPU resources, and improves processing efficiency.
  • the present application also provides an electronic device, including: at least one processor; and a memory, where at least one program is stored, and when the at least one program is executed by the at least one processor, the message processing method according to each embodiment of the present application is implemented .
  • a processor is a device with data processing capability, including but not limited to a central processing unit (CPU), etc.; a memory is a device with data storage capability, including but not limited to random access memory (RAM, more specifically such as SDRAM, DDR, etc.) etc.), read-only memory (ROM), electrified erasable programmable read-only memory (EEPROM), flash memory (FLASH).
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrified erasable programmable read-only memory
  • FLASH flash memory
  • the processor and memory may be connected to each other through the bus and, in turn, to other components of the computing device.
  • the present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the message processing method according to each embodiment of the present application is implemented.
  • FIG. 10 is a block diagram of the composition of the message processing apparatus provided by the present application.
  • the present application provides a message processing apparatus, including a sending module 1001 and a receiving module 1002 .
  • the sending module 1001 is configured to send N first registration request messages to the NRF entity, where N is an integer greater than or equal to 1, and split the second registration request messages to be sent to the NRF entity to obtain the N first registration request messages
  • the first registration request message, and the information amount of each of the first registration request messages is less than or equal to the first preset threshold, and the time interval between the first registration request messages sent twice adjacently is greater than or equal to the second preset threshold.
  • the information amount of each first registration request message is less than or equal to the first preset threshold may include the following situations: the number of ranges included in the configuration parameters carried in each first registration request message is less than or equal to the third preset threshold ; Or each range quantity contained in the configuration parameter carried in each first registration request message is less than or equal to the fourth preset threshold; or the length of the configuration parameter carried in each first registration request message is less than or equal to is equal to the fifth preset threshold; or the length of each first registration request message is less than or equal to the sixth preset threshold.
  • the scope included in the configuration parameter carried in the first registration request message may include at least one of the following: SUPI scope; GPSI scope; user IPv4 address scope; user IPv6 prefix scope; and TAI scope.
  • the configuration parameters carried in the first registration request message may include virtual NF entity identifiers, and the virtual NF entity identifiers included in configuration parameters carried in different first registration request messages sent by the same first NF entity are different.
  • the receiving module 1002 is configured to receive N registration response messages returned by the NRF entity, wherein the N first registration request messages correspond to the N registration response messages one-to-one.
  • the corresponding first registration request message and the configuration parameter carried in the registration response message contain the same number of ranges.
  • Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes both volatile and nonvolatile implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data flexible, removable and non-removable media.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage, or may Any other medium that stores the desired information and can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

Landscapes

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

Abstract

本申请提供了一种消息处理方法和装置、电子设备和计算机可读存储介质。消息处理方法包括：向网络存储功能实体发送N个第一注册请求消息，其中，N为大于或等于1的整数，对需要向所述网络存储功能实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。

Description

消息处理方法和装置、电子设备、计算机可读存储介质 技术领域
本申请涉及通信领域，特别涉及消息处理方法和装置、电子设备、计算机可读存储介质。
背景技术
第五代移动通信技术(5G，5 th Generation)核心网(5GC，5G Core Network)采用了基于服务的架构(SBA，Service Based Architecture)，5GC中所有的网络功能(NF，Network Function)实体可以分为服务生产者和服务消费者两类。服务生产者需要向网络存储功能(NRF，Network Repository Function)实体注册，目前的注册方法使得作为服务生产者的NF实体在注册过程中占用过多的网络带宽资源，影响普通消息的收发，导致链路拥塞，甚至网络瘫痪。
发明内容
本申请提供一种消息处理方法和装置、电子设备、计算机可读存储介质。
本申请实施例提供一种消息处理方法，包括：向NRF实体发送N个第一注册请求消息，其中，N为大于或等于1的整数，对需要向所述NRF实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
本申请实施例还提供一种消息处理装置，包括：发送模块，用于向NRF实体发送N个第一注册请求消息，其中，N为大于或等于1的整数，对需要向所述NRF实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
本申请实施例还提供一种电子设备，包括：至少一个处理器；以及存储器，存储器上存储有至少一个程序，当所述至少一个程序被所述至少一个处理器执行时，实现根据本申请的消息处理方法。
本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现根据本申请的消息处理方法。
附图说明
图1为相关技术的通信系统交互示意图；
图2为相关技术的注册交互示意图；
图3为相关技术的服务发现交互示意图；
图4为本申请提供的消息处理方法的流程图；
图5为本申请提供的消息处理方法的交互示意图；
图6为本申请提供的服务发现交互示意图；
图7为本申请提供的消息处理方法的又一交互示意图；
图8为本申请提供的消息处理方法的又一交互示意图；
图9为本申请提供的消息处理方法的又一交互示意图；以及
图10为本申请提供的消息处理装置的组成框图。
具体实施方式
为使本领域的技术人员更好地理解本申请的技术方案，下面结合附图对本申请提供的消息处理方法和装置、电子设备、计算机可读存储介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本申请透彻和完整，并将使本领域技术人员充分理解本申请的范围。
在不冲突的情况下，本申请各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括至少一个相关列举条目的 任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本申请。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加至少一个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本申请的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
图1为相关技术的通信系统交互示意图。
如图1所示，通信系统包括：第一NF实体、NRF实体和第二NF实体。
第一NF实体作为服务生产者，第二NF实体作为服务消费者。在不同的业务场景，单个NF实体的角色可以在服务生产者和服务消费者之间来回切换。
目前，作为服务生产者的第一NF实体向NRF实体注册的过程大致包括：第一NF实体向NRF实体发送注册请求消息；以及第一NF实体接收NRF实体发送的注册响应消息。
注册请求消息携带第一NF实体的JS对象简谱(JSON，JavaScript Object Notation)格式的NF配置(NFProfile)参数，NFProfile参数包含了第一NF实体及其所能提供的服务的一系列配置参数，这些配置参数可能会携带第一NF实体所提供的服务的以下至少一个范围列表：用户永久标识符(SUPI，Subscription Permanent Identifier)范围列表(SUPIRanges)；通用公共用户标识符(GPSI，Generic Public Subscription Identifier)范围列表(GPSIRanges)；用户互联网协议版本4(IPv4，Internet Protocol Version 4)地址范围列表(IPv4AddressRanges)；用户互联网协议版本6(IPv6， Internet Protocol Version 6)前缀范围列表(IPv6PrefixRanges)；以及跟踪区域标识(TAI，Tracking Area Identity)范围列表。
SUPI范围列表(SUPIRanges)的一个例子如下所示，在该示例中，SUPI范围列表为JSON数组格式，包括了两个SUPI范围，即，SUPI范围列表大小为2，每个SUPI范围包含一个开始(start)字段和一个结束(end)字段。GPSI范围列表、用户IPv4地址范围列表、用户IPv6前缀范围列表、TAI范围列表的格式与之类似，只有列表名称、start字段和end字段的取值格式不同。
Figure PCTCN2022082427-appb-000001
注册请求消息中具体携带哪些范围列表与第一NF实体的类型有关，例如，策略控制功能(PCF，Policy Control Function)实体只支持SUPI和GPSI这两种范围列表，而绑定支持功能(BSF，Binding Support Function)实体只支持用户IPv4地址范围列表和用户IPv6前缀范围列表。
图2为相关技术的注册交互示意图。
如图2所示，为了简化描述，注册请求消息中只携带了SUPI范围列表，实际情况下也可以携带其他类型的范围列表。假设第一NF实体对应1万个SUPI范围，因此第一NF实体发送的注册请求消息中的NFProfile参数将携带该1万个SUPI范围以及其他配置参数。根据估算，整个注册请求消息是长度约700KB的超长报文。
目前的注册过程中，每一个独立部署的NF实体只向NRF实体发送一个注册请求消息，由于目前运营商实行大区制，因此单个NF实 体提供服务的移动用户数量庞大，加之运维人员配置不恰当等原因(例如，号段过于分散等)，可能会导致注册请求消息中的NFProfile参数的范围列表数量非常庞大，例如，达到数千个甚至上万个范围列表，而NFProfile参数采用纯文本格式，这样导致注册请求消息可能成为几百千字节(KB，Kilobyte)甚至几兆字节(MB，Megabyte)的超长报文。尽管5GC的控制面的基于服务的接口(SBI，Service Based Interface)所使用的超文本传输协议第2版(HTTP/2，Hypertext Transfer Protocol 2)协议栈有分帧机制，可以将一个比较长的消息体拆分为多个较小的数据(DATA)帧，底层传输层控制协议(TCP，Transmission Control Protocol)协议栈也有分片机制，但是，不管是拆分成多个DATA帧还是进行TCP分片，都需要在极短时间内全部发送完成，这是因为底层无法感知业务逻辑，也就无法做到离散控制。
另外，如图2所示，第一NRF实体返回的注册响应消息也需要携带注册请求消息中的NFProfile参数。总而言之，目前的注册方法使得第一NF实体在注册过程中占用过多的网络带宽资源，影响普通消息的收发，导致链路拥塞，甚至网络瘫痪。
另外，在注册过程中，由于第一NF实体需要处理超长报文也会占用较多的中央处理单元(CPU，Center Processing Unit)资源，导致第一NF实体处理效率降低。
另外，作为服务消费者的第二NF实体需要调用其他NF实体提供的服务时，需要向NRF实体进行服务发现，即，第二NF实体向NRF实体发送发现请求消息；并且第二NF实体接收NRF实体发送的发现响应消息，发现响应消息中携带符合条件的服务生产者的NF实体的NFProfile参数。
如图3所示，假设第二NF实体第一次向NRF实体发送的发现请求消息中携带SUPI A，第二次向NRF实体发送的发现请求消息中携带SUPI B，并且SUPI A落在第一NF实体对应的第1个SUPI范围内，SUPI B落在第一NF实体对应的第1万个SUPI范围内，那么NRF实体两次返回的发现响应消息中都会携带完整的NFProfile参数，其中 包含了第一NF实体对应的1万个SUPI范围，也就是说，用落在这1万个SUPI范围内的任何SUPI去进行服务发现，返回的发现响应消息都将是长度约700KB的超长报文。这使得第二NF实体在服务发现过程中也会占用过多的网络带宽资源，影响普通消息的收发，导致链路拥塞，甚至网络瘫痪；并且在服务发现过程中，由于第二NF实体需要处理超长报文也会占用较多的CPU资源，导致第二NF实体处理效率降低。
技术术语说明
在本申请中，如无特殊说明，以下技术术语按照以下解释理解，即，NF实体是指为用户提供的服务功能的NF实例。
本申请实施例中的注册请求消息、注册响应消息、发现请求消息、发现响应消息均以报文的形式在网络中传输，一般认为总长度超过64KB的报文为超长报文。
本申请的消息处理方法可以应用于任何一个包括第一NF实体、NRF实体和第二NF实体的网络，例如，可以应用于第三代合作伙伴计划(3GPP，3 rd Generation Partnership Project)协议、采用SBA架构实现的5GC控制面网络，也可以应用于未来的网络。
图4为本申请提供的消息处理方法的流程图。
参照图4，本申请提供一种消息处理方法，应用于第一NF实体，该方法包括步骤400至401。
在步骤400，向NRF实体发送N个第一注册请求消息，N为大于或等于1的整数。
在本申请中，对需要向NRF实体发送的第二注册请求消息进行拆分得到N个第一注册请求消息。
在本申请中，每一个第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
在本申请中，需要向NRF实体发送的第二注册请求消息即为前面描述的相关技术中的注册请求消息。由前面的描述可知，第二注册请求消息为超长报文，在注册过程中，由于处理超长报文需要占用过 多的网络带宽资源，影响普通消息的收发，导致链路拥塞，甚至网络瘫痪；并且，在注册过程中，由于需要处理超长报文也会占用较多的CPU资源，导致第一NF实体处理效率降低。
在实现过程中，可以先判断需要向NRF实体发送的第二注册请求消息是否为超长报文，在需要向NRF实体发送的第二注册请求消息为超长报文的情况下，将第二注册请求消息拆分成N个第一注册请求消息，使得每一个第一注册请求消息的信息量均小于或等于第一预设阈值，然后向NRF实体发送N个第一注册请求消息。
在第二注册请求消息不是超长报文的情况下，不需要将第二注册请求消息拆分成N个第一注册请求消息，可以直接将第二注册请求消息作为第一注册请求消息发送给NRF实体。
可以预先设置时间间隔，按照预先设置的时间间隔依次向NRF实体发送N个第一注册请求消息。
本申请对第二预设阈值(即，预设的时间间隔)的具体取值不作限定，例如，时间间隔可以配置在10毫秒到10000毫秒之间，可以根据注册过程总时长和防冲击需求来决定具体取值，例如，可以将时间间隔配置成100毫秒。
每一个第一注册请求消息的信息量均小于或等于第一预设阈值可以包括以下情况：每一个第一注册请求消息中携带的配置参数中包含的范围数量均小于或等于第三预设阈值；或者每一个第一注册请求消息中携带的配置参数中包含的每一种范围数量均小于或等于第四预设阈值；或者每一个第一注册请求消息中携带的配置参数的长度均小于或等于第五预设阈值；或者每一个第一注册请求消息的长度均小于或等于第六预设阈值。
也就是说，前面描述的每一个第一注册请求消息的信息量均小于或等于第一预设阈值可以是指：每一个第一注册请求消息中携带的配置参数中包含的范围数量均小于或等于第三预设阈值，从而间接反映出每一个第一注册请求消息的信息量均小于或等于第一预设阈值；或者每一个第一注册请求消息中携带的配置参数中包含的每一种范围数量均小于或等于第四预设阈值，从而间接反映出每一个第一注册 请求消息的信息量均小于或等于第一预设阈值；或者每一个第一注册请求消息中携带的配置参数的长度均小于或等于第五预设阈值，从而间接反映出每一个第一注册请求消息的信息量均小于或等于第一预设阈值；或者每一个第一注册请求消息的长度均小于或等于第六预设阈值，从而间接反映出每一个第一注册请求消息的信息量均小于或等于第一预设阈值。
不管采用哪种方式实现，最终的目的都是使得每一个第一注册请求消息的信息量均小于或等于第一预设阈值，而为达到这一目的所采用的各种方式均在本申请实施例的保护范围内，这里不再赘述。
第一注册请求消息中携带的配置参数可以包括前面所描述的NFProfile参数。
本申请对第三预设阈值的具体取值不作限定，例如，每一个第一注册请求消息中携带的配置参数中包含的范围数量在100到5000之间，例如，可以将第三预设阈值配置成500。
仍然以图2中的例子进行说明，在第一NF实体向NRF实体注册时，判断第一NF实体所提供服务的SUPI范围数量是否小于或等于500，在第一NF实体所提供服务的SUPI范围数量(这个例子中为1万个)大于500的情况下，如图5所示，可以将包括1万个SUPI范围的SUPI范围列表拆分成20个SUPI范围列表，其中的每一个SUPI范围列表包括500个SUPI范围，然后在每一个第一注册请求消息中携带的NFProfile参数中包含500个SUPI范围，这样，每一个第一注册请求消息和注册响应消息变成了35KB左右的短报文，大小是原来的1/20。注册完成后，可以在NRF实体上查看到20个虚拟NF实体对应的NFProfile参数。可以将第一NF实体发送的每一个第一注册请求消息看成是由一个虚拟NF实体发送的注册请求消息，也就是说，一个第一NF实体对外表现成多个虚拟NF实体，在上面的例子中，一个第一NF实体表现成20个虚拟NF实体。
完成上述注册流程后，第二NF实体使用用户相关参数(即，终端的SUPI)向NRF实体进行服务发现，仍然以上述发现条件SUPI A和SUPI B为例，如图6所示，第二NF实体向NRF实体发送发现请求 消息1，发现请求消息1中携带SUPI A；NRF向第二NF实体返回的发现响应消息1中携带包括SUPI A所在的SUPI范围的NFProfile参数，该NFProfile参数仅包括500个SUPI范围；类似地，第二NF实体向NRF实体发送发现请求消息2，发现请求消息2中携带SUPI B；NRF向第二NF实体返回的发现响应消息2中携带包括SUPI B所在的SUPI范围的NFProfile参数，该NFProfile参数也仅包括500个SUPI范围。这样，每一个发现响应消息均为35KB左右的报文，长度也只有原来的1/20。
本申请对第五预设阈值的具体取值不作限定，例如，每一个第一注册请求消息中携带的配置参数的长度在16KB到128KB之间，例如，可以将第五预设阈值配置成32KB。
仍然以图2中的例子进行说明，在第一NF实体向NRF实体注册时，判断第二注册请求消息中携带的NFProfile参数长度是否小于或等于32KB，如果NFProfile参数的总长度大于32KB，则需要拆分出多个携带的NFProfile参数小于或等于32KB的第一注册请求消息，在拆分过程中必须保证语法的完整性，不能出现参数残缺的情况，也就是说，拆分过程中应该保证NFProfile参数中包含整数个SUPI范围。例如，以NFProfile参数的最大长度配置为32KB的方式进行注册，流程如图7所示，原来约750KB的超长报文被拆分成多个携带小于或等于32KB的NFProfile参数的短报文，并且每发送一个第一注册请求消息后，按照配置的时间间隔等待，然后再发送下一个第一注册请求消息。
本申请对第六预设阈值的具体取值不作限定，例如，每一个第一注册请求消息的长度在16KB到128KB之间，例如，可以将第六预设阈值配置成32KB。
第一注册请求消息中携带的配置参数中包含的范围可以包括以下至少之一：SUPI范围；GPSI范围；用户IPv4地址范围；用户IPv6前缀范围；和TAI范围。
也就是说，在本申请实施例中，第一注册请求消息中携带的配置参数中可以仅包含上述任意一种范围，也可以包含上述两种或更多 种范围，具体携带哪些参数与NF类型有关。
如图8所示，第一注册请求消息中携带的NFProfile参数中同时包含SUPI范围和GPSI范围，此时可以合理地配置每种范围的最大数量，以控制NFProfile参数中包含的范围总数量。例如，配置每个第一注册请求消息中携带的NFProfile参数中包含的SUPI范围和GPSI范围的最大数量均为250，那么当第二注册请求消息中携带的NFProfile参数中包含的SUPI范围或GPSI范围的数量超过250，或者当第二注册请求消息中携带的NFProfile参数中包含的SUPI范围和GPSI范围的数量同时超过250，则拆分出各个第一注册请求消息。假设原始的第二注册请求消息中携带的NFProfile参数包含1万个SUPI范围和1万个GPSI范围，则可以拆分为40个第一注册请求消息，每一个第一注册请求消息携带的NFProfile参数中包含250个SUPI范围和250个GPSI范围。
又如，如果配置每一个NFProfile参数包含的用户IPv4地址范围和用户IPv6前缀范围的最大数量均为300，那么当第二注册请求消息中携带的NFProfile参数同时包含1万个用户IPv4地址范围和1万个用户IPv6前缀范围，则可以拆分为34个第一注册请求消息，前33个第一注册请求消息携带的NFProfile参数中包含300个IPv4地址范围和300个IPv6前缀范围，最后一个第一注册请求消息携带的NFProfile参数中包含100个IPv4地址范围和100个IPv6前缀范围，如图9所示。
第一注册请求消息中携带的配置参数中包含的范围均为第一NF实体所提供服务对应的范围，这里的服务是指对终端的服务。
第一注册请求消息中携带的配置参数中可以包含虚拟NF实体标识，同一第一NF实体发送的不同第一注册请求消息中携带的配置参数所包含的虚拟NF实体标识不同。
例如，可以预先为第一NF实体配置虚拟NF实体标识池，其中包括M个虚拟NF实体标识，第一NF实体每发送一个第一注册请求消息，从虚拟NF实体标识池中申请一个虚拟NF实体标识。
M的具体取值可以视具体情况来定，需要保证虚拟NF实体标识 全局唯一。为了保证虚拟NF实体标识全局唯一，为不同的第一NF实体配置的虚拟NF实体标识池的范围不能相互重叠，也就是说，为第一NF实例配置的虚拟NF实体标识池中的每一个虚拟NF实体标识均是全局唯一。
由于每一个虚拟NF实体标识均是全局唯一，因此，可以将第一NF实体发送的每一个第一注册请求消息看成是由一个虚拟NF实体发送的注册请求消息，也就是说，一个第一NF实体对外表现成多个虚拟NF实体，每一个虚拟NF实体的注册过程与相关技术中的第一NF实体的注册过程相同，区别在于所发送的注册请求消息的长度不同。本申请的虚拟NF实体所发送的第一注册请求消息的长度较短，不会占用过多的网络带宽资源，减少对普通消息的收发的影响，保证链路畅通，并且节约了CPU资源，提高了处理效率。
回到图4，在向NRF实体发送N个第一注册请求消息(即，步骤400)后，在步骤401，接收NRF实体返回的N个注册响应消息，其中，N个第一注册请求消息与N个注册响应消息一一对应。
相对应的第一注册请求消息和注册响应消息中携带的配置参数中包含的范围数量相同。
在本申请中，“第一注册请求消息和注册响应消息相对应”是指注册响应消息是针对第一注册请求消息进行回复的消息。
根据本申请提供的消息处理方法，对需要向NRF实体发送的第二注册请求消息进行拆分得到N个第一注册请求消息，第二注册请求消息为超长报文，拆分得到的每一个第一注册请求消息的长度均小于或等于第一预设阈值，并且相邻两次发送的第一注册请求消息之间的时间间隔大于或等于第二预设阈值，也就是说，将第二注册请求消息拆分成N个短报文，并且将N个短报文在时间上离散地发送出去，使得发送N个第一注册请求消息所占用的网络带宽资源比发送第二注册请求消息所占用的网络带宽资源要少很多，减少对普通消息的收发的影响，保证链路畅通，并且节约了CPU资源，提高了处理效率。
另外，在采用本申请的消息处理方法实现注册过程后，在第二NF实体进行服务发现的过程中，NRF实体向第二NF实体返回的发现 响应消息也变为较短的普通报文，使得服务发现过程中所占用的网络带宽资源也相对变少，减少对普通消息的收发的影响，保证链路畅通，并且节约了CPU资源，提高了处理效率。
本申请还提供一种电子设备，包括：至少一个处理器；以及存储器，存储器上存储有至少一个程序，当至少一个程序被至少一个处理器执行时，实现根据本申请各实施例的消息处理方法。
处理器为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)。
处理器和存储器可以通过总线相互连接，进而与计算设备的其它组件连接。
本申请还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现根据本申请各实施例的消息处理方法。
图10为本申请提供的消息处理装置的组成框图。
参照图10，本申请提供一种消息处理装置，包括发送模块1001和接收模块1002。
发送模块1001用于向NRF实体发送N个第一注册请求消息，其中，N为大于或等于1的整数，对需要向所述NRF实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
每一个第一注册请求消息的信息量均小于或等于第一预设阈值可以包括以下情况：每一个第一注册请求消息中携带的配置参数中包含的范围数量均小于或等于第三预设阈值；或者每一个第一注册请求消息中携带的配置参数中包含的每一种范围数量均小于或等于第四预设阈值；或者每一个第一注册请求消息中携带的配置参数的长度均小于或等于第五预设阈值；或者每一个第一注册请求消息的长度均小 于或等于第六预设阈值。
第一注册请求消息中携带的配置参数中包含的范围可以包括以下至少之一：SUPI范围；GPSI范围；用户IPv4地址范围；用户IPv6前缀范围；和TAI范围。
第一注册请求消息中携带的配置参数中可以包含虚拟NF实体标识，同一第一NF实体发送的不同第一注册请求消息中携带的配置参数所包含的虚拟NF实体标识不同。
接收模块1002用于接收所述NRF实体返回的N个注册响应消息，其中，N个第一注册请求消息与N个注册响应消息一一对应。
相对应的第一注册请求消息和注册响应消息中携带的配置参数中包含的范围数量相同。
上述消息处理装置的具体实现过程与前述消息处理方法的具体实现过程相同，这里不再赘述。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储器、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通 常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本申请的范围的情况下，可进行各种形式和细节上的改变。

Claims (10)

  1. 一种消息处理方法，包括：
    向网络存储功能实体发送N个第一注册请求消息，
    其中，N为大于或等于1的整数，对需要向所述网络存储功能实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
  2. 根据权利要求1所述的消息处理方法，其中，每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值包括：
    每一个所述第一注册请求消息中携带的配置参数中包含的范围数量均小于或等于第三预设阈值；或者
    每一个所述第一注册请求消息中携带的配置参数中包含的每一种范围数量均小于或等于第四预设阈值；或者
    每一个所述第一注册请求消息中携带的配置参数的长度均小于或等于第五预设阈值；或者
    每一个所述第一注册请求消息的长度均小于或等于第六预设阈值。
  3. 根据权利要求2所述的消息处理方法，其中，所述第一注册请求消息中携带的配置参数中包含的范围包括以下至少之一：
    用户永久标识符范围；
    通用公共用户标识符范围；
    用户互联网协议版本4地址范围；
    用户互联网协议版本6前缀范围；以及
    跟踪区域标识范围。
  4. 根据权利要求1所述的消息处理方法，其中，所述第一注册 请求消息中携带的配置参数中包含虚拟网络功能实体标识，不同第一注册请求消息中携带的配置参数中包含的虚拟网络功能实体标识不同。
  5. 根据权利要求1至4中任意一项所述的消息处理方法，其中，在向所述网络存储功能实体发送所述N个第一注册请求消息后，还包括：
    接收所述网络存储功能实体返回的N个注册响应消息，
    其中，所述N个第一注册请求消息与所述N个注册响应消息一一对应。
  6. 根据权利要求5所述的消息处理方法，其中，相对应的所述第一注册请求消息和所述注册响应消息中携带的配置参数中包含的范围数量相同。
  7. 一种消息处理装置，包括：
    发送模块，用于向网络存储功能实体发送N个第一注册请求消息，
    其中，N为大于或等于1的整数，对需要向所述网络存储功能实体发送的第二注册请求消息进行拆分得到所述N个第一注册请求消息，并且每一个所述第一注册请求消息的信息量均小于或等于第一预设阈值，相邻两次发送的所述第一注册请求消息之间的时间间隔大于或等于第二预设阈值。
  8. 根据权利要求7所述的消息处理装置，还包括：
    接收模块，用于接收所述网络存储功能实体返回的N个注册响应消息，
    其中，所述N个第一注册请求消息与所述N个注册响应消息一一对应。
  9. 一种电子设备，包括：
    至少一个处理器；以及
    存储器，所述存储器上存储有至少一个程序，当所述至少一个程序被所述至少一个处理器执行时，实现根据权利要求1至6中任意一项所述的消息处理方法。
  10. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时，实现根据权利要求1至6中任意一项所述的消息处理方法。
PCT/CN2022/082427 2021-04-19 2022-03-23 消息处理方法和装置、电子设备、计算机可读存储介质 WO2022222674A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110416747.5 2021-04-19
CN202110416747.5A CN112822646B (zh) 2021-04-19 2021-04-19 消息处理方法和装置、电子设备、计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2022222674A1 true WO2022222674A1 (zh) 2022-10-27

Family

ID=75863662

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/082427 WO2022222674A1 (zh) 2021-04-19 2022-03-23 消息处理方法和装置、电子设备、计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN112822646B (zh)
WO (1) WO2022222674A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822646B (zh) * 2021-04-19 2021-08-13 中兴通讯股份有限公司 消息处理方法和装置、电子设备、计算机可读存储介质
CN113687878B (zh) * 2021-08-23 2023-12-01 北京京东振世信息技术有限公司 一种信息交互方法、装置、设备及存储介质
CN118175098A (zh) * 2022-12-08 2024-06-11 中国科学院声学研究所 一种信息中心网络网内节点流量控制方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109803242A (zh) * 2017-11-17 2019-05-24 中兴通讯股份有限公司 通过nrf进行nf发现的方法、设备及可读存储介质
US20190230556A1 (en) * 2018-01-19 2019-07-25 Electronics And Telecommunications Research Institute Apparatus and method for network function profile management
WO2020098974A1 (en) * 2018-11-14 2020-05-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for network function selection in 5g for a user
CN112449758A (zh) * 2018-05-21 2021-03-05 瑞典爱立信有限公司 用于针对用户处理切片选择数据的方法和装置
CN112566072A (zh) * 2019-09-26 2021-03-26 华为技术有限公司 一种基于nf的通信方法、设备及存储介质
CN112822646A (zh) * 2021-04-19 2021-05-18 中兴通讯股份有限公司 消息处理方法和装置、电子设备、计算机可读存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106713170B (zh) * 2016-12-30 2019-09-06 杭州迪普科技股份有限公司 一种vsm通道的报文分片方法及装置
JP6787190B2 (ja) * 2017-03-06 2020-11-18 カシオ計算機株式会社 認証装置及びプログラム
WO2019153428A1 (zh) * 2018-02-09 2019-08-15 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109803242A (zh) * 2017-11-17 2019-05-24 中兴通讯股份有限公司 通过nrf进行nf发现的方法、设备及可读存储介质
US20190230556A1 (en) * 2018-01-19 2019-07-25 Electronics And Telecommunications Research Institute Apparatus and method for network function profile management
CN112449758A (zh) * 2018-05-21 2021-03-05 瑞典爱立信有限公司 用于针对用户处理切片选择数据的方法和装置
WO2020098974A1 (en) * 2018-11-14 2020-05-22 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for network function selection in 5g for a user
CN112566072A (zh) * 2019-09-26 2021-03-26 华为技术有限公司 一种基于nf的通信方法、设备及存储介质
CN112822646A (zh) * 2021-04-19 2021-05-18 中兴通讯股份有限公司 消息处理方法和装置、电子设备、计算机可读存储介质

Also Published As

Publication number Publication date
CN112822646B (zh) 2021-08-13
CN112822646A (zh) 2021-05-18

Similar Documents

Publication Publication Date Title
WO2022222674A1 (zh) 消息处理方法和装置、电子设备、计算机可读存储介质
US11463281B2 (en) Managing network packet flows based on device information
KR20090101384A (ko) 네트워크에서의 완전 메시 레이트 트랜잭션
WO2021134446A1 (zh) 一种信息处理方法和通信装置以及通信系统
CN110445723B (zh) 一种网络数据调度方法及边缘节点
CN106686553B (zh) 一种在核心网epc上进行组播的方法和装置
CN111510390A (zh) 应用程序或无线电信息在网络数据包头中的插入和使用
US10136375B2 (en) Method for service data management, apparatus, and system
CN110138730B (zh) 一种协议转换设备的订阅方法、装置及存储介质
CN111901255A (zh) 一种用于网络设备快速包镜像转发的方法和装置
EP2852212A1 (en) Method, system and device for processing data packet
US9838492B2 (en) Data pushing method, apparatus, and system
WO2022206683A1 (zh) 无线通信的方法和装置
CN113965433B (zh) 一种多网络聚合的实现方法
EP3982598A1 (en) Method and apparatus for sending and receiving message, and communication system
WO2021190029A1 (zh) 实现运营商级网络地址转换的方法、装置和系统
US20190273794A1 (en) Method And Intermediate Network Node For Managing TCP Segment
US11671515B2 (en) Methods, network node and client device for acquisition and delivery of resources in a communications network
US20140074956A1 (en) Message sending method and apparatus
US10397978B2 (en) Method and system for signaling optimization of IP connection over a mobile-radio network
US20240163217A1 (en) Apparatuses, methods and non-transitory computer-readable storage mediums for network access to residential gateways
WO2024131514A1 (zh) 内置会话绑定支持功能查询方法及系统
US12120090B2 (en) Residential gateway IP prefix renewal after re-registration
US20240314077A1 (en) Apparatuses, methods and non-transitory computer-readable storage mediums for network access
CN112804716B (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: 22790783

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28/02/2024)

122 Ep: pct application non-entry in european phase

Ref document number: 22790783

Country of ref document: EP

Kind code of ref document: A1