CN114079974A - Network capability opening method and device, UPF entity and CPE network element - Google Patents

Network capability opening method and device, UPF entity and CPE network element Download PDF

Info

Publication number
CN114079974A
CN114079974A CN202010806192.0A CN202010806192A CN114079974A CN 114079974 A CN114079974 A CN 114079974A CN 202010806192 A CN202010806192 A CN 202010806192A CN 114079974 A CN114079974 A CN 114079974A
Authority
CN
China
Prior art keywords
information
network element
base station
cpe
message
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202010806192.0A
Other languages
Chinese (zh)
Inventor
李志强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
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 China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN202010806192.0A priority Critical patent/CN114079974A/en
Publication of CN114079974A publication Critical patent/CN114079974A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints

Landscapes

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

Abstract

The invention provides a network capacity opening method, a network capacity opening device, a UPF entity and a CPE network element, wherein the method comprises the following steps: and when the CPE network element is accessed to the base station, transmitting the uplink service message information to a first UPF entity connected with the base station through the base station. Correspondingly, the first UPF entity acquires the uplink service message information transmitted by the base station when the CPE network element accesses the base station connected with the first UPF entity; the uplink service message information includes device information of the device accessed to the CPE network element. The first UPF entity can provide the equipment information for other UPFs by acquiring the equipment information of the equipment accessed in the CPE network element, so that the situation that other UPF entities, other network elements or applications with requirements repeatedly acquire the equipment information through the CPE network element which is accessed to the same base station as the first UPF entity is avoided, and the efficiency of acquiring the equipment information of the equipment accessed in the CPE network element is improved.

Description

Network capability opening method and device, UPF entity and CPE network element
Technical Field
The invention relates to the field of communication, in particular to a network capacity opening method and device, a UPF entity and a CPE network element.
Background
In a network system in which a client terminal Equipment (CPE) network element accesses a mobile network, if an application needs to acquire device information of a device accessed through the CPE network element, the application needs to collect the acquired device information through client software and report the device information to an application server. If a plurality of applications need to acquire the device information of the device, each application needs to acquire the device information independently and repeatedly, and a related mechanism is realized repeatedly, so that the method for acquiring the device information of the device accessed through the CPE network element is not universal and efficient. On the other hand, by adopting the mode, the mobile network such as a 5G network cannot sense the equipment information of the equipment, and the equipment information cannot be opened to the application with requirements as value-added service capability, so that the value of the network is improved.
Disclosure of Invention
The technical scheme of the invention aims to provide a network capacity opening method, a network capacity opening device, a UPF entity and a CPE network element, so as to solve the problem that in the prior art, repeated acquisition is needed when equipment information of equipment accessed through the CPE network element is acquired.
In order to achieve the above object, the present invention provides a network capability opening method applied to a first user plane function UPF entity, including:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Optionally, the method further comprises: storing the device information, and updating the device information when the device information is updated.
Optionally, the method further comprises:
acquiring a capability calling request sent by a second UPF entity;
sending response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
Optionally, the capability invocation request is acquired and the response information is sent to the second UPF entity by at least one of the following methods:
API interface, SRv6 messages, and IPV6 messages.
Optionally, when the capability call request sent by the second UPF entity is acquired through the SRv6 message and the response information is sent to the second UPF entity, an addressing address, functional information, and parameters carried in the SRv6 message are recorded through a Segment List field in the SRv6 message used for sending the capability call request and the response information.
Optionally, the function information indicates that the SRv6 message is the capability call request through first preset field information, and indicates that the SRv6 message is the response information through second preset field information.
Optionally, the parameter carried by the Segment List field of the SRv6 message is an address of the target CPE to be acquired.
Optionally, the network capability opening method includes:
transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need.
Another embodiment of the present invention provides a network capability opening method, which is applied to a CPE network element of a client device, and the method includes:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Yet another embodiment of the present invention provides a user plane function, UPF, entity, wherein the user plane function, UPF, entity is a first UPF entity, and comprises a transceiver configured to:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Another embodiment of the present invention provides a customer premises equipment, CPE, network element comprising a transceiver configured to:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Another embodiment of the present invention provides a network capability opening apparatus, which is applied to a first user plane function UPF entity, and includes:
a message obtaining module, configured to obtain uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected to the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Another embodiment of the present invention provides a network capability opening apparatus, which is applied to a CPE network element of a client device, and the apparatus includes:
the message transmission module is used for transmitting uplink service message information to a first User Plane Function (UPF) entity connected with a base station through the base station when the base station is accessed;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Another embodiment of the present invention provides a network element, including: a processor, a memory, and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the network capability opening method as described above or implementing the network capability opening method as described above.
Still another embodiment of the present invention provides a readable storage medium having stored thereon a program that, when executed by a processor, implements the steps in the network capability opening method as described above or implements the steps in the network capability opening method as described above.
At least one of the above technical solutions of the present invention has the following beneficial effects:
by adopting the network capacity opening method provided by the embodiment of the invention, the first UPF entity can acquire the equipment information of the equipment accessed in the CPE network element connected with the base station through the base station, and the first UPF entity can provide the equipment information under the first UPF entity for other UPF entities by acquiring the equipment information of the equipment accessed in the CPE network element, so that the problem that different applications repeatedly acquire the equipment information through a server is avoided, the efficiency of acquiring the equipment information of the equipment accessed in the CPE network element is improved, and the utilization rate of network resources is improved.
Drawings
Fig. 1 is a networking topology diagram of the network capability method according to the embodiment of the present invention;
fig. 2 is a flowchart illustrating a network capability opening method according to an embodiment of the present invention;
fig. 3 is a message format diagram of an extension header of SRv6 and IPv6 of the network capability method according to the embodiment of the present invention;
fig. 4 is a second flowchart illustrating a network capability opening method according to an embodiment of the present invention;
fig. 5 is an expanded header diagram of SRv6 of the network capability method according to the embodiment of the present invention;
fig. 6 is a schematic diagram illustrating request and response device information between UPF entities in the network capability method according to the embodiment of the present invention;
fig. 7 is a third flowchart illustrating a network capability opening method according to a third embodiment of the present invention;
fig. 8 is a schematic structural diagram of an implementation manner of a user plane function UPF entity according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of an embodiment of a CPE network element of a client device according to an embodiment of the present invention;
fig. 10 is a diagram illustrating an embodiment of a network capability opening apparatus according to an embodiment of the present invention;
fig. 11 is a second embodiment of the network capability opening apparatus according to the embodiment of the present invention;
fig. 12 is an implementation manner of a network element according to an embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a schematic diagram of a network architecture of a network capability opening method according to an embodiment of the present invention. The CPE network element is connected with a plurality of devices, which may be, for example, user devices or sensors, and the plurality of devices and the CPE network element are connected through a local area network. A base station (shown by gNB in the figure) is connected between the CPE network element and a User Plane Function (UPF) entity, and the UPF entity communicates with the base station through an N3 interface. The CPE network element may transmit the device information of the plurality of devices to the UPF entity through the base station, and the UPF entity may transmit the device information to the server through the N6 interface and the mobile network. And, the UPF entity and the UPF entity can communicate through an N9 interface.
Optionally, the CPE network element may also be referred to as a CPE-like network element.
As shown in fig. 2, which is a schematic flow chart of a network capability opening method according to an embodiment of the present invention, the method is applied to a first user plane function UPF entity, and includes:
s201: acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Before step S201, the CPE network element obtains device information of a device accessed by the CPE network element.
The device information includes, but is not limited to, a Media Access Control (MAC) address, an Internet Protocol (IP) address, a device model, a device runtime, a Central Processing Unit (CPU) utilization rate, a memory utilization rate, a hard disk usage, and a device reboot time.
In step S201, when the CPE network element accesses a base station, the uplink service packet information is transmitted to a first UPF entity connected to the base station through the base station. Correspondingly, the first UPF entity obtains the uplink service message information transmitted by the base station when the CPE network element of the client equipment accesses the base station connected with the first UPF entity.
Wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
By adopting the network capacity opening method provided by the embodiment of the invention, the first UPF entity can acquire the equipment information of the equipment accessed in the CPE network element connected with the base station through the base station, and the first UPF entity can provide the equipment information under the first UPF entity for other UPF entities by acquiring the equipment information of the equipment accessed in the CPE network element, so that the problem that other UPF entities, other network elements or applications with requirements repeatedly acquire the equipment information through a server is avoided, the efficiency of acquiring the equipment information of the equipment accessed in the CPE network element is improved, and the utilization rate of network resources is improved. Optionally, the first UPF entity and the CPE network element may communicate via SRv6 or IPv6 protocols. Illustratively, the uplink service message information is transmitted through SRv6 messages, or through IPV6 messages. That is, the CPE network element transmits the uplink service packet information to the base station through the SRv6 packet or the IPV6 packet, and the base station retransmits the uplink service packet information to the first UPF entity using the same packet (SRv6 packet or IPV6 packet).
In the embodiment of the invention, the CPE network element and the first UPF entity communicate in a diversified communication mode, so that the integrity and the accuracy of the uplink service message information transmitted by the CPE network element can be improved. For example, when the CPE network element transmits the uplink service packet information by using one communication protocol, data loss occurs, and then the CPE network element may transmit the uplink service packet information by using another communication protocol, thereby ensuring the integrity and accuracy of the uplink service packet information.
Illustratively, the device information is carried by a TLV field in an extension header of the SRv6 packet or the IPv6 packet.
SR, Segment Routing, is a source Routing technology, and source Routing is implemented by carrying labels of nodes of a forwarding path in a packet of a head node, SRV6 is an SR based on IPV6 forwarding plane, and IPV6 implements reachability.
Fig. 3 is a message format diagram of an extension header of SRv6 and IPv6 in the network capability opening method according to the embodiment of the present invention. The Next field of the IPv6 header is 43, which indicates that the subsequently carried header is a Routing extension header, and the Routing Type field in the Routing extension header, which identifies the Type of the Routing header, is 4, which indicates that the field is the SR header of SRv 6.
The SRV6 is compatible with IPv6 routing forwarding, connection among different network domains is easier to realize based on IP reachability, and the affinity of SRv6 for IPv6 enables the IP bearer network to be seamlessly fused with applications supporting IPv6, so that more possible value-added is brought to operators through network perception application.
Specifically, the SRv6 and the contents included in the extension header of the IPv6 are as shown in fig. 3.
(1) Segment List: ordered SRv6 Sid list
(2) Number of intermediate nodes Segment Left (SL) that should still be accessed before reaching the destination node: segment Identifier SRv6 (SID) is slit SL. In the forwarding process, the SL is modified, and the SID with the DIP being active is changed to finish the forwarding.
(3) Version: version(s)
(4) Traffic Class: type of flow
(5) Flow Label: flow label
(6) Pload Length: payload length
(7) Hop Limit: hop count limitation
(8) Source Address: source address
(9) Destination Address: destination address
(10) Next Header: the type of header immediately following the SRH is identified.
(11) Hdr Ext Len: length of SRH head.
(12) Last Entry: the index of the last element of the segment list is contained in the segment list.
(13) Flag: some identification of the packet.
(14) Tag: identifying the same group of packets for grouping the packets, a group-based policy may be implemented.
(15) Optional Tlv objects (variable): variable length TLV part
(16) IPv6 Payload: message load
(17) IPv6 Header: IPv6 extension header
(18) SR Header: SR expansion head
Segment routing header type, length, value SRH TLVs (NSH metadata, HMAC TLV, Padding TLV, etc.): a global parameter that can be used in common as the SID of the Segment List.
The SRH TLVs may carry device information such as a MAC address, an IP address, a device model, device running time, a CPU utilization rate, a memory utilization rate, a hard disk usage, and device reboot times of the device.
Optionally, when the CPE-like network element uplink service packet information is accessed to the mobile network, the TLV field of the SRv6 extension header carries the device information such as the MAC address, the IP address, the device model, the device running time, the CPU utilization rate, the memory utilization rate, the hard disk usage, the device reboot times, and the like of the network element downlink device.
When receiving SRv6 equipment information of extension head-carried CPE network element down-link equipment, the UPF entity analyzes SRv6 messages and stores, maintains and ages the carried equipment information.
Optionally, the UPF entity only maintains the device information of the CPE-like network element downlink device accessed through the base station served by the UPF entity, and provides a restful, netconf, or other api interface for the application in need to make the capability request call, and the UPF entity also supports other network elements or applications to make the capability request call through the function defined in an embodiment of the present invention.
For example, the first UPF entity may further store the device information.
Further, the first UPF entity may also update the device information when the device information is updated.
The CPE network element may send device information of one or more devices connected to the CPE network element to the base station, and the base station may send the device information to the UPF entity connected to the base station. The UPF entity may then store this device information.
Further, the UPF entity may also transmit the device information to a server for backup. The first UPF entity may maintain the device information accessed to the CPE and monitor whether the device information changes every time a preset time period elapses, for example, the time period may be 30 minutes or 1 hour or 1 day. When the device information changes, for example, the device information increases or decreases, the device information is updated. By updating the device information when the device information changes, the validity and accuracy of the device information can be improved. The first UPF entity is convenient for other UPF entities or applications to call the equipment information through interfaces by storing the equipment information, so that the other UPF entities or applications are prevented from repeatedly acquiring the equipment information through CPE network elements, and the utilization rate of network resources is improved.
Optionally, the method further comprises:
transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need.
In one embodiment, the first UPF entity may actively report the device information of the device accessed by each CPE network element to the capability openness service platform; in another embodiment, the capability openness service platform may also actively collect the device information of the device accessed by each CPE network element on the first UPF entity, and collect the device information of the device accessed by each CPE network element on each UPF entity. The capability openness service platform can open the equipment information to the network element or application with the equipment information requirement by collecting the equipment information of the equipment accessed on each CPE network element stored on each UPF entity. As shown in fig. 4, a second flowchart of the network capability opening method according to the embodiment of the present invention is shown, and on the basis of step S201, the method further includes the following steps:
s401: the first UPF entity obtains the capability calling request sent by the second UPF entity.
The second UPF entity may send a capability invocation request to the first UPF entity. Accordingly, the first UPF entity may obtain the capability invocation request sent by the second UPF entity.
S402: the first UPF entity sends response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
When receiving the capability calling request sent by the second UPF, the first UPF entity may analyze the capability calling request, and send response information responding to the capability calling request to the second UPF entity according to the analysis result, so that the second UPF entity may obtain the device information of the target CPE network element.
For example, when the second UPF entity needs to obtain one of the pieces of device information of the target device in the first UPF entity, a capability calling request may be sent to the first UPF entity, where the capability calling request includes the piece of device information requested by the second UPF entity, and the one of the pieces of device information may be, for example, a running time of the target device. When the first UPF entity receives the capability calling request of the second UPF entity, the capability calling request can be analyzed, and the device information requested by the second UPF can be sent to the second UPF entity in a response information mode. Therefore, the second UPF entity can directly obtain the running time of the target equipment from the first UPF entity without obtaining the running time of the target equipment through a CPE network element which is accessed to the same base station with the first UPF entity, the running time of the target equipment which is repeatedly obtained through the same CPE network element is avoided, and the utilization rate of network resources is improved.
Optionally, the second UPF entity may also obtain other information in the device information of the target device through the first UPF entity, for example, obtain a device model of the target device. The target device may be one device or a plurality of devices; the device information of the target device may be, for example, multiple information in the device information of one device, such as an IP address, an MAC address, and a memory utilization rate, or may be, for example, the same information in the device information of multiple devices, such as a hard disk usage, or may be, for example, multiple information in the device information of multiple devices.
Next, the manner in which the first UPF entity obtains the capability invocation request and sends the response information to the second UPF entity is described. Illustratively, the capability invocation request is obtained and the response information is sent to the second UPF entity by at least one of:
API interfaces, SRv6 messages, and IPv6 messages.
Optionally, the capability call request may also be acquired through restful or netconf, and the response information may also be sent to the second UPF entity.
Through various interfaces and messages of different types, the first UPF entity can acquire the capability calling request sent by the second UPF entity and send response information to the second UPF entity, and compatibility of the UPF entity is improved.
For example, when the capability call request sent by the second UPF entity is acquired through the SRv6 message and the response information is sent to the second UPF entity, the addressing address, the function information, and the carried parameters of the SRv6 message are recorded through the Segment List field in the SRv6 message used for sending the capability call request and the response information.
SRv6, the extension Header (SRH) is composed of a series of Security Identifiers (SIDs) and an optional TLV (Type-Length-Value), each SID is composed of 128 bits, and the 128 bits are divided into three parts, namely, location identifier, Function and variable alignment, and the Length of each part can be flexibly defined as long as the total Length of the three parts is 128 bits. The Locator is configured to record an addressing address of the SRv6 packet, the Function is configured to record Function information of the SRv6 packet, and the Argumen is configured to record parameters carried by the SRv6 packet. Specifically, as shown in fig. 5, it is an extension header schematic diagram of SRv6 of the network capability method according to the embodiment of the present invention.
Alternatively, one embodiment of the invention uses 32 bits to represent Locator, 32 bits to represent Function (two functions are defined), and 32 bits to represent archive. The acquisition of CPE-like network element downstream device information via SRv6 is achieved by defining 2 functions, one definition of which is shown in table 1:
Figure BDA0002629207170000101
TABLE 1
For example, the function information indicates that the SRv6 message is the capability call request through first preset field information, and indicates that the SRv6 message is the response information through second preset field information.
Specifically, the first preset field may be 0x00000001 as described above, and the second preset field may be 0x00000002 as described above.
For example, the parameter carried in the Segment List field of the SRv6 message is an address of the target CPE to be acquired.
By carrying the address of the target CPE to be acquired in the Segment List field of the SRv6 message, the address of the target CPE can be forwarded as the destination address. Therefore, the first UPF entity can know that the second UPF needs to acquire the equipment information of which CPE network element in the same base station the second UPF accesses, and then sends the equipment information in the target CPE network element to the second UPF entity, so that the accuracy and convenience for acquiring the equipment information of the target CPE network element access equipment are improved.
Further, on the basis of the above embodiments, a process of the second UPF entity acquiring the device information of the target device under the first UPF entity is specifically described next. For convenience of description, the second UPF entity is represented by UPF network element Z and the first UPF entity is represented by UPF network element a.
Fig. 6 is a schematic diagram illustrating request and response device information between UPF entities in the network capability opening method according to the embodiment of the present invention. Assuming that the UPF network element Z needs to acquire the device information of the CPE network element 10.10.10.10 downlink device maintained by the UPF network element a, where the device information of the CPE network element 10.10.10 downlink device is carried by a TLV field of an SRH header, the network element Z executes step S401 and constructs an SRv6 address according to the above-defined Function encoding rule. After receiving the capability call request of the network element Z, the network element a finds that the Function is 2 and the Argument is 10.10.10.10, and further analyzes the TLV field in the SRH header of the message according to table 2, recognizes that the network element Z requests the device information of the CPE network element 10.10.10.10 downlink device locally maintained by the network element a, and executes step S402, so that the network element Z obtains the related information of the CPE network element 10.10.10.10 downlink device. The specific format of the TLV field of the SRH header is shown in table 2:
Figure BDA0002629207170000111
Figure BDA0002629207170000121
TABLE 2
As shown in fig. 7, a third flow chart of the network capability opening method according to the embodiment of the present invention is applied to a CPE network element of a client device, and the method includes:
s710: when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
By adopting the network capacity opening method, when the CPE network element accesses the base station connected with the first UPF entity, the uplink service message information comprising the equipment information of the equipment accessed to the CPE network element can be sent to the first UPF entity through the base station, and then the first UPF entity can acquire the equipment information of the equipment accessed to the CPE network element. The CPE network element transmits the equipment information accessed to the equipment of the CPE network element to the first UPF entity, so that the equipment information under the first UPF entity can be provided for other UPF entities, the problem that different applications repeatedly acquire the equipment information through a server is solved, the efficiency of acquiring the equipment information of the equipment accessed to the CPE network element is improved, and the utilization rate of network resources is improved.
Optionally, in the method for opening network capability, the uplink service packet information is transmitted through SRv6 packets or IPV6 packets.
Optionally, in the method for opening network capability, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Another embodiment of the present invention provides a user plane function UPF entity, as shown in fig. 8, which is a schematic structural diagram of an implementation manner of the user plane function UPF entity according to the embodiment of the present invention, where the user plane function UPF entity is a first UPF entity, and includes a transceiver 810 and a processor 820, and the transceiver 810 is configured to:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Optionally, the processor 820 is configured to: storing the device information, and updating the device information when the device information is updated.
Optionally, the transceiver 810 is further configured to:
acquiring a capability calling request sent by a second UPF entity;
sending response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
Optionally, the capability invocation request is acquired and the response information is sent to the second UPF entity by at least one of the following methods:
API interface, SRv6 messages, and IPV6 messages.
Optionally, when the capability call request sent by the second UPF entity is acquired through the SRv6 message and the response information is sent to the second UPF entity, an addressing address, functional information, and parameters carried in the SRv6 message are recorded through a Segment List field in the SRv6 message used for sending the capability call request and the response information.
Optionally, the function information indicates that the SRv6 message is the capability call request through first preset field information, and indicates that the SRv6 message is the response information through second preset field information.
Optionally, the parameter carried by the Segment List field of the SRv6 message is an address of the target CPE to be acquired.
Optionally, the transceiver 810 is further configured to: transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need.
As shown in fig. 9, which is a schematic structural diagram of an implementation manner of a Customer Premise Equipment (CPE) network element according to an embodiment of the present invention, including a transceiver 910, where the transceiver 910 is configured to:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
As shown in fig. 10, a further embodiment of the present invention provides a network capability opening apparatus applied to a first user plane function UPF entity, including:
a first message transmission module 1001, configured to acquire uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected to the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Optionally, the apparatus further includes a message processing module 1002, where the message processing module 1002 is configured to: storing the device information, and updating the device information when the device information is updated.
Optionally, the message processing module 1002 is further configured to:
acquiring a capability calling request sent by a second UPF entity;
sending response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
Optionally, the capability invocation request is acquired and the response information is sent to the second UPF entity by at least one of the following methods:
API interface, SRv6 messages, and IPV6 messages.
Optionally, when the capability call request sent by the second UPF entity is acquired through the SRv6 message and the response information is sent to the second UPF entity, an addressing address, functional information, and parameters carried in the SRv6 message are recorded through a Segment List field in the SRv6 message used for sending the capability call request and the response information.
Optionally, the function information indicates that the SRv6 message is the capability call request through first preset field information, and indicates that the SRv6 message is the response information through second preset field information.
Optionally, the parameter carried by the Segment List field of the SRv6 message is an address of the target CPE to be acquired.
Optionally, the first message transmission module 1001 is further configured to: transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need. As shown in fig. 11, another embodiment of the present invention provides a network capability opening apparatus, applied to a Customer Premise Equipment (CPE) network element, including:
a second message transmission module 1101, configured to transmit, when accessing a base station, uplink service message information to a first user plane function UPF entity connected to the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
As shown in fig. 12, an implementation manner of a network element according to the embodiment of the present invention is that the network element is a first user plane function UPF entity, and includes: a processor 1201; and a memory 1203 connected to the processor 1201 through the bus interface 1202, where the memory 1203 is used to store programs and data used by the processor 1201 when performing operations, and the processor 1201 calls and executes the programs and data stored in the memory 1203.
The transceiver 1204 is connected to the bus interface 1202 and configured to receive and transmit data under the control of the processor 1201, and specifically, the processor 1201 is configured to read a program in the memory 1203 and execute the following processes:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, in the network element, the uplink service packet information is transmitted through an SRv6 packet, or is transmitted through an IPV6 packet.
Optionally, in the network element, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Optionally, in the network element, the processor 1201 is further configured to: storing the device information, and updating the device information when the device information is updated.
Optionally, in the network element, the processor 1201 is further configured to:
acquiring a capability calling request sent by a second UPF entity;
sending response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
Optionally, in the network element, the processor 1201 obtains the capability invocation request and sends the response information to the second UPF entity by at least one of the following manners:
an API interface;
SRv6 a message; and
IPV6 messages.
Optionally, in the network element, when the processor 1201 acquires the capability call request sent by the second UPF entity through the SRv6 message and sends the response information to the second UPF entity, the processor 1201 is configured to record, in the SRv6 message used for sending the capability call request and the response information, the addressing address, the function information, and the carried parameters of the SRv6 message through the Segment List field.
Optionally, in the network element, the function information indicates that the SRv6 packet is the capability invocation request through first preset field information, and indicates that the SRv6 packet is the response information through second preset field information.
Optionally, in the network element, a parameter carried in a Segment List field of the SRv6 message is an address of a target CPE to be acquired.
Optionally, the processor 1201 is further configured to: transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need.
In another embodiment of the present invention, as shown in fig. 12, the network element is a CPE network element, the transceiver 1204 is connected to the bus interface 1202 and is configured to receive and transmit data under the control of the processor 1201, and specifically, the processor 1201 is configured to read a program in the memory 1203 and execute the following processes:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
Optionally, the uplink service message information is transmitted through SRv6 message, or through IPV6 message.
Optionally, the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
Where in fig. 12 the bus architecture may include any number of interconnected buses and bridges, with various circuits linking together one or more processors, represented by the processor 1201, and memory, represented by the memory 1203. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1204 may be a number of elements including a transmitter and a receiver providing a means for communicating with various other apparatus over a transmission medium. The processor 1201 is responsible for managing a bus architecture and general processing, and the memory 1203 may store data used by the processor 1201 in performing operations.
Yet another embodiment of the present invention provides a readable storage medium having stored thereon a program that, when executed by a processor, implements the steps in the network capability opening method as described above or implements the steps in the network capability opening method as described above.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.

Claims (19)

1. A network capability opening method is applied to a first User Plane Function (UPF) entity, and the method comprises the following steps:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
2. The method according to claim 1, wherein the uplink traffic message information is transmitted by SRv6 message or by IPV6 message.
3. The method according to claim 2, wherein the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
4. The method for opening network capability according to claim 1, further comprising: storing the device information, and updating the device information when the device information is updated.
5. The network capability opening method according to any one of claims 1 to 4, wherein the method further comprises:
acquiring a capability calling request sent by a second UPF entity;
sending response information responding to the capability calling request to the second UPF entity; the response information comprises the equipment information of the target CPE network element requested by the capability calling request.
6. The method according to claim 5, wherein the capability invocation request is obtained and the response message is sent to the second UPF entity by at least one of:
an API interface;
SRv6 a message;
IPV6 messages.
7. The method according to claim 6, wherein when the capability call request sent by a second UPF entity is obtained through an SRv6 message and the response message is sent to the second UPF entity, an addressing address, function information, and parameters carried in the SRv6 message are recorded through a Segment List field in a SRv6 message used for sending the capability call request and the response message.
8. The method as claimed in claim 7, wherein the function information indicates that the SRv6 message is the capability invocation request through a first preset field information, and indicates that the SRv6 message is the response information through a second preset field information.
9. The method as claimed in claim 7, wherein the parameter carried in the Segment List field of the SRv6 message is an address of a target CPE to be acquired.
10. The network capability opening method according to any one of claims 1 to 9, wherein the method further comprises:
transmitting the equipment information of equipment accessed by each CPE network element on a base station connected with the first UPF entity to a capability open service platform;
wherein the capability openness service platform is capable of providing the device information to the network element in need.
11. A network capability opening method is applied to a Customer Premise Equipment (CPE) network element, and comprises the following steps:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
12. The method according to claim 11, wherein the uplink traffic message information is transmitted by SRv6 message or by IPV6 message.
13. The method according to claim 12, wherein the device information is carried in a TLV field in an extension header of the SRv6 packet or the IPV6 packet.
14. A user plane function, UPF, entity, wherein the user plane function, UPF, entity is a first UPF entity, comprising a transceiver configured to:
acquiring uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected with the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
15. A customer premises equipment, CPE, network element comprising a transceiver, wherein the transceiver is configured to:
when accessing a base station, transmitting uplink service message information to a first User Plane Function (UPF) entity connected with the base station through the base station;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
16. A network capability openness apparatus applied to a first user plane function, UPF, entity, the apparatus comprising:
a message obtaining module, configured to obtain uplink service message information transmitted by a base station when a CPE network element of a client device accesses the base station connected to the first UPF entity;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
17. A network capability opening apparatus, applied to a Customer Premise Equipment (CPE) network element, the apparatus comprising:
the message transmission module is used for transmitting uplink service message information to a first User Plane Function (UPF) entity connected with a base station through the base station when the base station is accessed;
wherein, the uplink service message information includes the device information of the accessed device on the CPE network element.
18. A network element, comprising: a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the network capability opening method according to any one of claims 1 to 10 or implementing the network capability opening method according to any one of claims 11 to 13.
19. A readable storage medium, characterized in that the readable storage medium has stored thereon a program which, when executed by a processor, implements the steps in the network capability opening method according to any one of claims 1 to 10, or implements the steps in the network capability opening method according to any one of claims 11 to 13.
CN202010806192.0A 2020-08-12 2020-08-12 Network capability opening method and device, UPF entity and CPE network element Pending CN114079974A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010806192.0A CN114079974A (en) 2020-08-12 2020-08-12 Network capability opening method and device, UPF entity and CPE network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010806192.0A CN114079974A (en) 2020-08-12 2020-08-12 Network capability opening method and device, UPF entity and CPE network element

Publications (1)

Publication Number Publication Date
CN114079974A true CN114079974A (en) 2022-02-22

Family

ID=80280313

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010806192.0A Pending CN114079974A (en) 2020-08-12 2020-08-12 Network capability opening method and device, UPF entity and CPE network element

Country Status (1)

Country Link
CN (1) CN114079974A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710810A (en) * 2022-05-31 2022-07-05 新华三技术有限公司 Data transmission method, device and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391940A (en) * 2017-08-02 2019-02-26 华为技术有限公司 A kind of method, equipment and system accessing network
US20200112906A1 (en) * 2018-10-05 2020-04-09 Qualcomm Incorporated Techniques for routing id update
US20200229042A1 (en) * 2019-01-10 2020-07-16 Cisco Technology, Inc. SRv6 User-Plane-Based Triggering Methods and Apparatus for Session or Flow Migration in Mobile Networks
CN111432439A (en) * 2020-03-27 2020-07-17 广州爱浦路网络技术有限公司 UPF data plane extension and system thereof
WO2020151735A1 (en) * 2019-01-25 2020-07-30 Qualcomm Incorporated Secondary cell group configuration in multi-radio access technology-dual connectivity and carrier aggregation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391940A (en) * 2017-08-02 2019-02-26 华为技术有限公司 A kind of method, equipment and system accessing network
US20200112906A1 (en) * 2018-10-05 2020-04-09 Qualcomm Incorporated Techniques for routing id update
US20200229042A1 (en) * 2019-01-10 2020-07-16 Cisco Technology, Inc. SRv6 User-Plane-Based Triggering Methods and Apparatus for Session or Flow Migration in Mobile Networks
WO2020151735A1 (en) * 2019-01-25 2020-07-30 Qualcomm Incorporated Secondary cell group configuration in multi-radio access technology-dual connectivity and carrier aggregation
CN111432439A (en) * 2020-03-27 2020-07-17 广州爱浦路网络技术有限公司 UPF data plane extension and system thereof

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114710810A (en) * 2022-05-31 2022-07-05 新华三技术有限公司 Data transmission method, device and system

Similar Documents

Publication Publication Date Title
EP3585095B1 (en) Method and device for controlling qos, smf, upf, ue, pcf and an
US9503957B2 (en) Low cost mesh network capability
CN113810438B (en) Service computing resource scheduling and requesting method, node equipment and terminal
JP2020515126A (en) Internet of Things communication method, Internet of Things device, and Internet of Things system
US8942212B2 (en) Autoconfiguration system for wireless sensor network and its method, and gateway apparatus for wireless sensor network
EP1542409A1 (en) Protocol for multi-hop ad-hoc networks
US20090319686A1 (en) Communication route selecting method and apparatus
US7532620B2 (en) Routing table synchronization method, network apparatus, and routing table synchronization program
US10148739B2 (en) M2M data querying and invoking methods, querying and invoking devices, and system
CN101621548A (en) Method and system for realizing terminal resource sharing based on peer connection system
WO2009111965A1 (en) Method, device and system of data synchronization
US9021013B2 (en) Ubiquitous web service gateway and method
US20230308346A1 (en) Method for configuring a terminal device
CN116633775A (en) Container communication method and system of multi-container network interface
CN114079974A (en) Network capability opening method and device, UPF entity and CPE network element
JP2023526843A (en) PORT STATE SETTING METHOD, APPARATUS AND SYSTEM, AND STORAGE MEDIUM
CN112714146B (en) Resource scheduling method, device, equipment and computer readable storage medium
CN114500341A (en) Terminal real-time control method and control server under wide area network
CN114461427A (en) Method for sharing computer peripheral equipment by PMS (personal computer) in hotel
JP6858887B2 (en) IP address setting method and device
JP2001036581A (en) Communication band setting system and its method
US8036218B2 (en) Technique for achieving connectivity between telecommunication stations
CN114172965A (en) User service request and processing method, device and medium
CN117014636B (en) Data stream scheduling method of audio and video network, storage medium and electronic device
CN114553965B (en) Scheduling method of intranet equipment, network equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination