CN114339804A

CN114339804A - Service registration method, device, equipment and readable storage medium

Info

Publication number: CN114339804A
Application number: CN202011049010.6A
Authority: CN
Inventors: 刘棠青; 牟彦; 王丹; 李志强
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2020-09-29
Filing date: 2020-09-29
Publication date: 2022-04-12

Abstract

The invention discloses a service registration method, a device, equipment and a readable storage medium, which relate to the technical field of communication and aim to improve the capacity expansion capability of a network element of a control user plane. The method comprises the following steps: and when the user plane service resources need to be added, sending a service adding request to the service function storage entity. The embodiment of the invention can improve the capacity expansion capability of the network element of the user plane.

Description

Service registration method, device, equipment and readable storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a service registration method, apparatus, device, and readable storage medium.

Background

A PFCP (Packet Forwarding Control Protocol) is used for interaction between a 5G core network element SMF (Session Management Function) and a User Plane network element UPF (User Plane Function), a point-to-point architecture is still adopted in the network architecture, an interface between a Control Plane and a User Plane needs to be predefined and statically configured, and network pre-deployment is complex, so that expansion of the User Plane network element UPF needs to be manually configured and intervened.

Disclosure of Invention

The embodiment of the invention provides a service registration method, a device, equipment and a readable storage medium, which are used for improving the capacity expansion capability of a network element of a control user plane.

In a first aspect, an embodiment of the present invention provides a service registration method, which is applied to a user plane network element, and the method includes:

and when the user plane service resources need to be added, sending a service adding request to the service function storage entity.

Wherein the method further comprises:

when the user plane service resources need to be updated, sending an update service request to the service function storage entity; or

And when the user plane service resources need to be recovered, sending a recovery service request to the service function storage entity.

Wherein, the service request for adding or updating carries the service resource information of the user plane;

the user plane service resource information comprises one or more of the following information:

service ID, service name, service location, service IP, service port.

Wherein the method further comprises:

when a coupled service object needs to be created, receiving a first coupled service object creation request and a control plane capability set sent by a control plane network element;

and sending a second request for establishing the coupled service object and a user plane capability set to the control plane network element.

Wherein the method further comprises:

when the coupled service object needs to be updated, sending a request for updating the coupled service object to the control plane network element; or

And when the coupled service object needs to be released, sending a coupled service object releasing request to the control plane network element.

Wherein, coupling service object information is carried in the second coupling service object creating request or the coupling service object updating request, and the coupling service object information includes one or more of the following information:

service object ID, user plane function characteristic, user plane node identification U-NodeID, user plane IP resource information and user plane IP address pool identification.

Wherein the method further comprises:

and when the session service object needs to be created, receiving a request for creating the session service object sent by the control plane network element.

Wherein the method further comprises:

when the session service object needs to be updated, receiving a session service object updating request sent by the control plane network element; or

And when the session service object needs to be released, receiving a request for releasing the session service object sent by the control plane network element.

Wherein the create session service object request or the update session service object request includes a session service object table;

wherein, the session service object table at least comprises a primary table and a secondary table;

the primary table comprises a session identifier, a node identifier, a control plane UP F-SEID, a user plane UP F-SEID, a packet detection rule PDR ID list and a packet data network PDN type;

the secondary table includes: PDR ID, packet probe information PDI.

Wherein the secondary table further comprises one or more of the following information:

forwarding a behavior rule FAR ID, using a report rule URR ID and a Qos implementation rule QER ID and a BAR ID;

wherein the FAR ID includes one or more of the following information: a destination interface, a network instance, an Outer Header Creation, a Transport Level Marking and a Forwarding Policy;

the URR ID includes one or more of the following information: measurement method, report trigger, measurement period, threshold, time threshold;

the QER ID includes one or more of the following information: QER calibration ID, gate status, maximum bit rate, guaranteed bit rate, packet rate;

the BAR ID includes one or more of the following information: the downlink data notification delay, the number of suggested buffer packets.

In a second aspect, an embodiment of the present invention provides a service registration method, which is applied to a service function storage entity, and the method includes:

receiving a service adding request sent by a user plane network element, wherein the service adding request is sent by the user plane network element when user plane service resources need to be added;

and registering the service according to the service adding request.

Wherein the method further comprises:

receiving an update service request sent by the user plane network element, wherein the update service request is sent by the user plane network element when the user plane service resource needs to be updated; or

And receiving a recovery service request sent by the user plane network element, wherein the recovery service request is sent by the user plane network element when the user plane service resource needs to be recovered.

service ID, service name, service location, service IP, service port.

In a third aspect, an embodiment of the present invention provides a service registration method, which is applied to a control plane network element, and the method includes:

sending a service acquisition request to a service function storage entity;

receiving information of available user plane network elements sent by the service function storage entity;

a user plane network element is selected from the available user plane network elements.

Wherein, after selecting a user plane network element from the available user plane network elements, the method further comprises:

when a coupled service object needs to be created, sending a first coupled service object creation request and a control plane capability set to the user plane network element;

and receiving a second service object creation coupling request and a user plane capability set sent by the user plane network element.

Wherein the method further comprises:

when the coupled service object needs to be updated, sending a request for updating the coupled service object to the user plane network element; or

And when the coupled service object needs to be released, sending a coupled service object releasing request to the user plane network element.

Wherein, the first request for creating a coupling service object or the request for updating the coupling service object carries coupling service object information, and the coupling service object information includes one or more of the following information:

service object ID, control plane functional characteristics, control plane node identification C-NodeID, IP address of optional control plane, and recovery timestamp.

Wherein the method further comprises:

and when a session service object needs to be created, sending a request for creating the session service object to the user plane network element.

Wherein the method further comprises:

when the session service object needs to be updated, sending a request for updating the session service object to the user plane network element; or

And when the session service object needs to be released, sending a request for releasing the session service object to the user plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

In a fourth aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a user plane network element, and the apparatus includes:

the first sending module is used for sending a service adding request to the service function storage entity when the user plane service resources need to be added.

Wherein the apparatus may further comprise:

the second sending module is used for sending an update service request to the service function storage entity when the user plane service resources need to be updated; or

And the third sending module is used for sending a service recovery request to the service function storage entity when the user plane service resources need to be recovered.

service ID, service name, service location, service IP, service port.

Wherein the apparatus may further comprise:

the first receiving module is used for receiving a first coupling service object creating request and a control plane capability set sent by a control plane network element when a coupling service object needs to be created;

a fourth sending module, configured to send a second request for creating a coupled service object and a user plane capability set to the control plane network element.

Wherein the apparatus may further comprise:

a fifth sending module, configured to send a request for updating the coupled service object to the control plane network element when the coupled service object needs to be updated; or

A sixth sending module, configured to send a request for releasing the coupled service object to the control plane network element when the coupled service object needs to be released.

Wherein the apparatus may further comprise:

and the second receiving module is used for receiving a request for creating the session service object sent by the control plane network element when the session service object needs to be created.

Wherein the apparatus may further comprise:

a third receiving module, configured to receive a session service object update request sent by the control plane network element when a session service object needs to be updated; or

A fourth receiving module, configured to receive, when a session service object needs to be released, a session service object release request sent by the control plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

In a fifth aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a service function storage entity, and the apparatus includes:

a first receiving module, configured to receive a service addition request sent by a user plane network element, where the service addition request is sent by the user plane network element when a user plane service resource needs to be added;

and the first processing module is used for registering the service according to the service adding request.

Wherein the apparatus may further comprise:

a second receiving module, configured to receive an update service request sent by the user plane network element, where the update service request is sent by the user plane network element when a user plane service resource needs to be updated; or

A third receiving module, configured to receive a service recovery request sent by the user plane network element, where the service recovery request is sent by the user plane network element when the user plane network element needs to recover user plane service resources.

service ID, service name, service location, service IP, service port.

In a sixth aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a control plane network element, and the apparatus includes:

the first sending module is used for sending a service acquisition request to the service function storage entity;

a first receiving module, configured to receive information of an available user plane network element sent by the service function storage entity;

a first selection module for selecting a user plane network element from the available user plane network elements.

Wherein the apparatus may further comprise:

a second sending module, configured to send a first request for creating a coupled service object and a control plane capability set to the user plane network element when the coupled service object needs to be created;

a second receiving module, configured to receive a second request for creating a coupled service object and a user plane capability set sent by the user plane network element.

Wherein the apparatus may further comprise:

a third sending module, configured to send a request for updating the coupled service object to the user plane network element when the coupled service object needs to be updated; or

A fourth sending module, configured to send a request for releasing the coupled service object to the user plane network element when the coupled service object needs to be released.

Wherein the apparatus may further comprise:

a fifth sending module, configured to send a request for creating a session service object to the user plane network element when the session service object needs to be created.

Wherein the apparatus may further comprise:

a sixth sending module, configured to send a request for updating the session service object to the user plane network element when the session service object needs to be updated; or

A seventh sending module, configured to send a request for releasing the session service object to the user plane network element when the session service object needs to be released.

the secondary table includes: PDR ID, packet probe information PDI.

In a seventh aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a user plane network element, where the apparatus includes a processor and a transceiver:

and the transceiver is used for sending a service adding request to the service function storage entity when the user plane service resources need to be added.

The transceiver is used for sending an update service request to the service function storage entity when user plane service resources need to be updated; or when the user plane service resource needs to be recovered, sending a recovery service request to the service function storage entity.

service ID, service name, service location, service IP, service port.

The transceiver is configured to receive a first coupled service object creation request and a control plane capability set sent by a control plane network element when a coupled service object needs to be created; and sending a second request for establishing the coupled service object and a user plane capability set to the control plane network element.

The transceiver is configured to send a request for updating a coupled service object to the control plane network element when the coupled service object needs to be updated; or, when the coupled service object needs to be released, sending a request for releasing the coupled service object to the control plane network element.

The transceiver is configured to receive a request for creating a session service object sent by a control plane network element when the session service object needs to be created.

The transceiver is configured to receive a session service object update request sent by the control plane network element when a session service object needs to be updated; or, when the session service object needs to be released, receiving a request for releasing the session service object sent by the control plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

In an eighth aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a service function storage entity, and includes a processor and a transceiver:

the transceiver is configured to receive a service addition request sent by a user plane network element, where the service addition request is sent by the user plane network element when a user plane service resource needs to be added;

and the processor is used for registering the service according to the service adding request.

The transceiver is configured to receive an update service request sent by the user plane network element, where the update service request is sent by the user plane network element when a user plane service resource needs to be updated; or, the apparatus is configured to receive a request for recovering service sent by the user plane network element, where the request for recovering service is sent by the user plane network element when the user plane network element needs to recover user plane service resources.

service ID, service name, service location, service IP, service port.

In a ninth aspect, an embodiment of the present invention provides a service registration apparatus, which is applied to a control plane network element, and the apparatus includes a processor and a transceiver:

the transceiver is used for sending a service acquisition request to a service function storage entity; receiving information of available user plane network elements sent by the service function storage entity;

the processor is configured to select a user plane cell from available user plane cells.

The transceiver is configured to send a first coupled service object creation request and a control plane capability set to the user plane network element when a coupled service object needs to be created; and receiving a second service object creation coupling request and a user plane capability set sent by the user plane network element.

The transceiver is configured to send a request for updating a coupled service object to the user plane network element when the coupled service object needs to be updated; or, when the coupled service object needs to be released, sending a request for releasing the coupled service object to the user plane network element.

The transceiver is configured to send a request for creating a session service object to the user plane network element when the session service object needs to be created.

The transceiver is configured to send a request for updating a session service object to the user plane network element when the session service object needs to be updated; or, when the session service object needs to be released, sending a request for releasing the session service object to the user plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

In a tenth aspect, an embodiment of the present invention provides a communication device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; the processor is configured to read a program in the memory to implement the steps in the service registration method according to any one of the above aspects.

In an eleventh aspect, an embodiment of the present invention provides a readable storage medium for storing a program, where the program, when executed by a processor, implements the steps in the service registration method according to any one of the above aspects.

In the embodiment of the invention, when the user plane service resources need to be added, the user plane network element can send the service adding request to the service function storage entity, so that the user plane network element can be found by the control plane network element as required, and the capacity expansion automation capability of the user plane network element is further improved.

Drawings

Fig. 1 is a flowchart of a service registration method provided in an embodiment of the present invention;

fig. 2 is a second flowchart of a service registration method according to an embodiment of the present invention;

fig. 3 is a third flowchart of a service registration method according to an embodiment of the present invention;

FIG. 4 is a fourth flowchart of a service registration method according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a specific process of registering and discovering a user plane service resource according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a process of user plane and control plane coupling service object application and provision according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating application and provisioning of control plane session event objects according to an embodiment of the present invention;

fig. 8 is one of the structural diagrams of a service registration apparatus provided by the embodiment of the present invention;

fig. 9 is a second structural diagram of a service registration apparatus according to an embodiment of the present invention;

fig. 10 is a third block diagram of a service registration apparatus according to an embodiment of the present invention;

FIG. 11 is a fourth block diagram of a service registration apparatus according to an embodiment of the present invention;

FIG. 12 is a fifth block diagram of a service registration apparatus according to an embodiment of the present invention;

fig. 13 is a sixth structural diagram of a service registration apparatus according to an embodiment of the present invention.

Detailed Description

The term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Referring to fig. 1, fig. 1 is a flowchart of a service registration method provided in an embodiment of the present invention, and is applied to a user plane network element. Wherein, the user plane network element mainly refers to UPF. As shown in fig. 1, the method comprises the following steps:

step 101, when the user plane service resource needs to be added, sending a service adding request to a service function storage entity.

On the basis of the above embodiment, the method may further include:

when the user plane service resource needs to be updated, the user plane network element sends an update service request to the service function storage entity; or when the user plane service resource needs to be recovered, the user plane network element sends a service recovery request to the service function storage entity.

By updating the user plane service resources, the corresponding service can be accurately provided for the control plane network element; by recycling the user plane service resources, the utilization rate of the resources can be more sufficient.

service ID, service name, service location, service IP, service port.

Specifically, the user plane service resource information may be defined by the following table 1:

table 1: service upf \ context:

On the basis of the above embodiment, the method may further include:

when a coupled service object needs to be created, a user plane network element receives a first coupled service object creation request and a control plane capability set sent by a control plane network element; and the user plane network element sends a second service object creation coupling request and a user plane capability set to the control plane network element.

On the basis of the above, the method may further include:

when a coupled service object needs to be updated, a user plane network element sends a request for updating the coupled service object to a control plane network element; or, when the coupled service object needs to be released, the user plane network element sends a request for releasing the coupled service object to the control plane network element.

In a specific application, the coupling service object information may be defined by table 2:

table 2: smf \ association \ context:

on the basis of the above embodiment, the method may further include:

when a session service object needs to be created, the user plane network element receives a request for creating the session service object sent by the control plane network element.

Further, the method may further include: when the session service object needs to be updated, the user plane network element receives a session service object updating request sent by the control plane network element; or, when the session service object needs to be released, the user plane network element receives a request for releasing the session service object sent by the control plane network element.

The request for creating the session service object or the request for updating the session service object comprises a session service object table;

the session service object table at least comprises a primary table and a secondary table. The primary table comprises a SESSION identifier (SESSION ID), a Node identifier (Node ID), a control plane UP F-SEID (CP F-SEID), a user plane UP F-SEID, a PDR (Packet Detection Rule) ID List (PDRID List), and a PDN (Packet Data Network ) Type (PDN Type); the secondary table includes: PDR ID, PDI (Packet Detection Information).

Further, the secondary table may further include: one or more of the following information:

FAR Action Rules ID, URR (Usage Reporting Rules) ID, QER (QoS Enforcement Rules) ID, BAR ID.

Wherein the FAR ID includes one or more of the following information: destination Interface (Destination Interface), Network instance (Network instance), Outer Header Creation, Transport Level Marking, Forwarding Policy;

the URR ID includes one or more of the following information: a Measurement Method (Measurement Method), report Triggers (Reporting Triggers), a Measurement Period (Measurement Period), a Threshold (Volume Threshold), a Time Threshold (Time Threshold);

the QER ID includes one or more of the following information: QER calibration id (QER calibration id), Gate Status (Gate Status), Maximum bit Rate (Maximum Bitrate), Guaranteed bit Rate (Guaranteed Bitrate), Packet Rate (Packet Rate);

the BAR ID includes one or more of the following information: downstream Data Notification Delay (Downlink Data Notification Delay), number of proposed buffer Packets (buffered Packets Count).

In practical applications, the primary table can be expressed as shown in table 3, and the secondary table can be expressed as shown in table 4:

table 3: upf \ session \ context

Table 4: upf \ session \ pdr

PDR ID

PDI

FAR ID

URR ID

QER ID

BARID

Wherein, FAR ID, URR ID, QER ID, BAR ID, etc. further included in the secondary table can be represented by the form of a tertiary table, as shown in tables 5-8:

table 5: upf \ session \ far

Table 6: upf \ session \ urr

Table 7: upf \ session \ qer

Table 8: upf \ session \ bar

Referring to fig. 2, fig. 2 is a flowchart of a service registration method provided by an embodiment of the present invention, and the method is applied to a service function storage entity. The service Function storage entity may be, for example, NRF (NF redundancy Function, network element data Repository Function). As shown in fig. 2, the method comprises the following steps:

step 201, receiving a service adding request sent by a user plane network element, wherein the service adding request is sent by the user plane network element when a user plane service resource needs to be added;

step 202, registering the service according to the service adding request.

On the basis of the above embodiment, the method further includes:

a service function storage entity receives an update service request sent by the user plane network element, wherein the update service request is sent by the user plane network element when user plane service resources need to be updated; or, the service function storage entity receives a recycle service request sent by the user plane network element, where the recycle service request is sent by the user plane network element when the user plane network element needs to recycle user plane service resources.

service ID, service name, service location, service IP, service port.

The representation of the user plane service resource information can refer to the foregoing table 1.

Referring to fig. 3, fig. 3 is a flowchart of a service registration method provided in an embodiment of the present invention, and is applied to a control plane network element. The control plane network element may be, for example, SMF. As shown in fig. 3, the method comprises the following steps:

step 301, sending a service acquisition request to a service function storage entity.

Step 302, receiving the information of the available user plane network element sent by the service function storage entity.

Step 303, selecting a user plane network element from the available user plane network elements.

In this step, the SMF may select a user plane cell from the available user plane cells according to a predetermined policy.

On the basis of the above embodiment, the method may further include:

when a coupled service object needs to be created, a control plane network element sends a first coupled service object creation request and a control plane capability set to a user plane network element; and the control plane network element receives a second service object creation coupling request and a user plane capability set sent by the user plane network element.

Further, the method may further include:

when a coupled service object needs to be updated, a control plane network element sends a request for updating the coupled service object to a user plane network element; or, when the coupled service object needs to be released, the control plane network element sends a request for releasing the coupled service object to the user plane network element.

service object ID, control plane functionality Features (CP Function Features), control plane node identifier C-node ID (C-node ID), optional control plane IP Address (Alternative SMF IP Address), Recovery timestamp (Recovery Time Stamp).

In practical applications, the coupling service object information can be as shown in table 9:

table 9: upf \ association \ context:

on the basis of the above embodiment, the method may further include:

and when a session service object needs to be created, the control plane network element sends a request for creating the session service object to the user plane network element. When a session service object needs to be updated, a control plane network element sends a request for updating the session service object to a user plane network element; or, when the session service object needs to be released, the control plane network element sends a request for releasing the session service object to the user plane network element.

The create session service object request or the update session service object request includes a session service object table, and the contents included in the session service object table may refer to the description of the foregoing embodiments.

In the embodiment of the invention, a service interface of a user plane of the 5G core network and a service discovery mechanism of a user plane network element of the 5G core network are redefined, so that the user plane of the 5G core network is unified into a service framework. Specifically, with reference to fig. 4, the service registration method according to the embodiment of the present invention may include the following processes:

step 401, service role definition (not shown): service consumers, service providers, and service function stores. Wherein:

user plane network element (UPF): a service provider. The user plane network element only needs to embed a unique NRF address when being on line.

Control plane network element (SMF): the service consumer. The control plane network element only needs to embed a unique NRF address when being on line.

NRF: storing the service function; the unique service address is deployed and published before all network elements are started.

Step 402, user plane service resource registration and discovery.

Step 4021, the service provider adds service resources to the service function storage.

Specifically, the UPF sends a POST service up context message to the NRF, and the NRF replies 200 OK.

Step 4022, service consumer inquires available service resource to service function storage.

Specifically, the SMF sends a GET service up context message to the NRF, and the NRF replies to a 200OK/service up context.

Step 403, user plane/control plane coupling service object application and provision.

Step 4031, the control plane network element (service consumer) applies for a coupling service object to the user plane (service provider).

Step 4032, the user plane (service provider) provides the coupling service object to the control plane network element (service consumer).

Specifically, the SMF sends POST up/association context to the UPF, and the UPF replies 200OK/up association context to the SMF.

Step 4033, the user plane (service provider) applies for a coupling service object to the control plane network element (service consumer).

Step 4034, the control plane network element (service consumer) provides the coupled service object to the user plane (service provider). Wherein step 4033-4034 is not shown.

Specifically, the UPF sends POST SMF/association context to the SMF, and the UPF replies 200OK/SMF association context to the SMF.

Step 404, the user plane session service object applies for and provides.

Step 4041, the control plane network element (service consumer) applies for a session service object from the user plane (service provider);

step 4042, the user plane (service provider) provides a session service object to the control plane network element (service consumer).

Specifically, the SMF sends POST SMF/session context to the UPF, and the UPF replies 200OK/session context to the SMF.

With reference to fig. 5, a specific process diagram of resource registration and discovery for the user plane service is shown. After completing service initialization, a user plane network element (UPF) immediately requests a new service to be added to the NRF, and carries open service information, such as: locality, service IP, and service port, etc. The NRF stores information about user plane network elements (UPFs). When one control plane network element (SMF) finishes service initialization or finds that the user plane resources are insufficient in the running process, the NRF is immediately requested to acquire an available UPF service list. After the control plane network element (SMF) obtains the resource list of the user plane network element (UPF) returned by the NRF, one or more UPF resources can be selected according to an internal preference principle, and subsequent related resource negotiation is started. Specifically, the method comprises the following steps:

step 501-.

Step 503-.

Step 505-.

In the POST service context message, the definition of the user plane service resource table is shown in table 10 below:

table 10: service upf \ context:

service id

service-name

service-location

service-ip

service-port

……

the UPF may also apply for updating the user plane service resource to the NRF, for example, the UPF sends a PUT service up context message to the NRF, and the NRF replies to 200 OK. Wherein, the resource table definition of the PUT service up context message is shown in table 10.

With reference to fig. 6, a schematic process diagram for user plane and control plane coupling service object application and provision is shown. And the control plane network element (SMF) applies for creating a coupling service object to the user plane network element (UPF) and finishes informing the user plane network element (UPF) of the control plane capability set. The user plane network element (UPF) responds to the request for creating the coupled service object of the control plane network element (SMF), and then the user plane network element UPF also initiates the request for creating the coupled service object to the control plane network element (SMF) and completes the notification of the user plane capability set to the control plane network element (SMF). Specifically, the method comprises the following steps:

step 601-.

Step 603-.

Step 605-.

Step 607-.

Wherein, the definition of the control-oriented user plane coupling service object table is shown in table 11:

table 11: upf \ association \ context:

the definition of the user-oriented control plane coupled service object table is shown in table 12:

table 12: smf \ association \ context:

in the above process, the control plane network element (SMF) may update the coupled service object to the user plane network element (UPF), and the user plane network element (UPF) may update the coupled service object to the control plane network element (SMF).

Specifically, the SMF sends PUT up/association context to the UPF, and the UPF replies 200OK/up association context to the SMF. The information carried in PUT up/association context can be referred to as shown in Table 11. UPF sends PUT SMF/association context to SMF, and UPF replies 200OK/SMF association context to SMF. The information carried in PUT smf/association context can be referred to as shown in Table 12.

Referring to fig. 7, schematic diagrams are applied and provided for the control plane session event object. Specifically, the control plane network element (SMF) applies for creating a session service object to the user plane network element (UPF). The user plane network element (UPF) responds to the request for creating the session service object of the control plane network element (SMF). The session service object is mainly used for the control plane network element (SMF) to issue access control, cache control, flow control rules and charging rules to the user plane network element (UPF). Specifically, the method comprises the following steps:

step 701 and 702, SMF sends POST SMF/session context to UPF, UPF replies 200OK/session context to SMF.

Step 703 and 704, when the session service object needs to be updated, the SMF sends PUT SMF/session context to the UPF, and the UPF replies 200OK/session context to the SMF.

Step 705-.

The definitions of the user plane session service object table carried in POST smf/session context or PUT smf/session context are shown in tables 13-18.

Table 13: upf \ session \ context

Table 14: upf \ session \ pdr

PDR ID

PDI

FAR ID

URR ID

QER ID

BARID

Table 15: upf \ session \ far

Table 16: upf \ session \ qer

Table 17: upf \ session \ urr

Table 18: upf \ session \ bar

Through the above description, the scheme of the embodiment of the invention can achieve the following effects:

(1) in the embodiment of the invention, the service registration and discovery process of the UPF to the service function storage is defined, so that the UPF can be discovered by the SMF of the control plane network element as required, thereby improving the capacity expansion automation capability of the UPF;

(2) in the embodiment of the invention, a service acquisition/access mechanism is used, and a point-to-point static configuration mode between an original control plane network element (SMF) and a User Plane (UPF) is replaced by a dynamic service resource application/use, so that the complexity of the current network deployment is greatly reduced;

(3) in the embodiment of the invention, an RESTFul API is used for redefining an interactive interface between a 5G control plane network element (SMF) and a User Plane (UPF), and the coupling and the session are defined in an object mode, so that the application and the acquisition of the service based on the object are realized;

(4) in the embodiment of the invention, the session negotiation process is defined as the change of the corresponding attribute of the session table object and the change of the attribute of the related sub table (PDR, FAR, URR, QER, BAR) object, thereby realizing the orthogonalization of session interaction information and reducing the signaling information redundancy and channel occupation caused by repeatedly carrying unchanged data by the original PFCP;

(5) in the embodiment of the invention, the process of coupling establishment is divided and defined into two independent processes of coupling object negotiation of a control plane network element and coupling object negotiation of a data plane network element, so that bidirectional notification between a control plane network element SMF and a user plane network element UPF is realized on a service interface framework of RESTFul API.

Therefore, the scheme of the embodiment of the invention can serve and standardize the user plane interface of the 5G core network, and has great propulsion effect on the dynamic expansion and contraction of the user plane and the decoupling and evolution of the control plane and the user plane.

The embodiment of the invention also provides a service registration device which is applied to the user plane network element. Referring to fig. 8, fig. 8 is a structural diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 8, the service registration apparatus 800 includes: a first sending module 801, configured to send an add service request to the service function storage entity when a user plane service resource needs to be added.

Wherein the apparatus may further comprise:

service ID, service name, service location, service IP, service port.

Wherein the apparatus may further comprise:

the secondary table includes: PDR ID, packet probe information PDI.

The apparatus provided in the embodiment of the present invention may implement the method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides a service registration device which is applied to the service function storage entity. Referring to fig. 9, fig. 9 is a structural diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 9, the service registration apparatus 900 includes: a first receiving module 901, configured to receive a service addition request sent by a user plane network element, where the service addition request is sent by the user plane network element when a user plane service resource needs to be added; a first processing module 902, configured to register a service according to the service adding request.

Wherein the apparatus may further comprise:

service ID, service name, service location, service IP, service port.

The embodiment of the invention also provides a service registration device which is applied to the control plane network element. Referring to fig. 10, fig. 10 is a block diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 10, the service registration apparatus 1000 includes: a first sending module 1001, configured to send a service acquisition request to a service function storage entity; a first receiving module 1002, configured to receive information of an available user plane network element sent by the service function storage entity; a first selecting module 1003 is configured to select a user plane network element from available user plane network elements.

Wherein the apparatus may further comprise:

the secondary table includes: PDR ID, packet probe information PDI.

The embodiment of the invention also provides a service registration device which is applied to the user plane network element. Referring to fig. 11, fig. 11 is a structural diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 11, the service registration apparatus 1100 includes: a processor 1101 and a transceiver 1102.

The transceiver 1102 is configured to send a service adding request to the service function storage entity when a user plane service resource needs to be added.

The transceiver 1102 is configured to send an update service request to the service function storage entity when a user plane service resource needs to be updated; or when the user plane service resource needs to be recovered, sending a recovery service request to the service function storage entity.

service ID, service name, service location, service IP, service port.

The transceiver 1102 is configured to receive a first coupled service object creation request and a control plane capability set sent by a control plane network element when a coupled service object needs to be created; and sending a second request for establishing the coupled service object and a user plane capability set to the control plane network element.

The transceiver 1102 is configured to send a request for updating a coupled service object to the control plane network element when the coupled service object needs to be updated; or, when the coupled service object needs to be released, sending a request for releasing the coupled service object to the control plane network element.

The transceiver 1102 is configured to receive a request for creating a session service object sent by a control plane network element when the session service object needs to be created.

The transceiver 1102 is configured to receive a session service object update request sent by the control plane network element when a session service object needs to be updated; or, when the session service object needs to be released, receiving a request for releasing the session service object sent by the control plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

The embodiment of the invention also provides a service registration device which is applied to the service function storage entity. Referring to fig. 12, fig. 12 is a block diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 12, the service registration apparatus 1200 includes: a processor 1201 and a transceiver 1202.

The transceiver 1202 is configured to receive a service addition request sent by a user plane network element, where the service addition request is sent by the user plane network element when a user plane service resource needs to be added;

the processor 1201 is configured to register a service according to the service adding request.

service ID, service name, service location, service IP, service port.

The embodiment of the invention also provides a service registration device which is applied to the control plane network element. Referring to fig. 13, fig. 13 is a block diagram of a service registration apparatus according to an embodiment of the present invention. Since the principle of the service registration apparatus for solving the problem is similar to the service registration method in the embodiment of the present invention, the implementation of the service registration apparatus may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 13, the service registration apparatus 1300 includes: a processor 1301 and a transceiver 1302.

The transceiver 1302, configured to send a service acquisition request to a service function storage entity; receiving information of available user plane network elements sent by the service function storage entity;

the processor 1301 is configured to select a user plane network element from available user plane network elements.

Wherein, the transceiver 1302 is configured to send a first request for creating a coupled service object and a control plane capability set to the user plane network element when the coupled service object needs to be created; and receiving a second service object creation coupling request and a user plane capability set sent by the user plane network element.

Wherein, the transceiver 1302 is configured to send a request for updating a coupled service object to the user plane network element when the coupled service object needs to be updated; or, when the coupled service object needs to be released, sending a request for releasing the coupled service object to the user plane network element.

Wherein, the transceiver 1302 is configured to send a request for creating a session service object to the user plane network element when the session service object needs to be created.

Wherein, the transceiver 1302 is configured to send a request for updating a session service object to the user plane network element when the session service object needs to be updated; or, when the session service object needs to be released, sending a request for releasing the session service object to the user plane network element.

the secondary table includes: PDR ID, packet probe information PDI.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. 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.

Furthermore, an embodiment of the present invention provides a communication device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; the processor is configured to read a program in the memory to implement the steps in the service registration method according to any of the above embodiments.

The embodiment of the present invention further provides a readable storage medium, where a program is stored on the readable storage medium, and when the program is executed by a processor, the program implements each process of the foregoing service registration method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is omitted here. The readable storage medium may be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical memory (e.g., CD, DVD, BD, HVD, etc.), and semiconductor memory (e.g., ROM, EPROM, EEPROM, nonvolatile memory (NAND FLASH), Solid State Disk (SSD)), etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. With such an understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A service registration method is applied to a user plane network element, and is characterized in that the method comprises the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 2, wherein the adding service request or the updating service request carries user plane service resource information;

service ID, service name, service location, service IP, service port.

4. The method of claim 1, further comprising:

5. The method of claim 4, further comprising:

6. The method of claim 5, wherein the second create coupled service object request or update coupled service object request carries coupled service object information, and wherein the coupled service object information includes one or more of the following information:

7. The method of claim 1, further comprising:

8. The method of claim 7, further comprising:

9. The method of claim 8, wherein the create session service object request or the update session service object request comprises a session service object table;

the secondary table includes: PDR ID, packet probe information PDI.

10. The method of claim 9, wherein the secondary table further comprises one or more of the following information:

11. A service registration method is applied to a service function storage entity, and is characterized in that the method comprises the following steps:

and registering the service according to the service adding request.

12. The method of claim 11, further comprising:

13. The method according to claim 12, wherein the adding service request or the updating service request carries user plane service resource information;

service ID, service name, service location, service IP, service port.

14. A service registration method is applied to a control plane network element, and is characterized in that the method comprises the following steps:

sending a service acquisition request to a service function storage entity;

15. The method of claim 14, wherein after said selecting a user plane cell from available user plane cells, the method further comprises:

16. The method of claim 15, further comprising:

17. The method of claim 16, wherein a coupled service object information is carried in the first create coupled service object request or update coupled service object request, and wherein the coupled service object information comprises one or more of the following information:

18. The method of claim 15, further comprising:

19. The method of claim 18, further comprising:

20. The method of claim 19, wherein the create session service object request or the update session service object request comprises a session service object table;

the primary table comprises a session identifier, a node identifier, a control plane UP F-SEID, a user plane UP F-SEID, a packet detection rule PDRID list and a packet data network PDN type;

the secondary table includes: PDR ID, packet probe information PDI.

21. The method of claim 20, wherein the secondary table further comprises one or more of the following information:

forwarding a behavior rule FAR ID, using a report rule URR ID and a Qos implementation rule QER ID and BARID;

the BARID includes one or more of the following information: the downlink data notification delay, the number of suggested buffer packets.

22. A service registration apparatus, applied to a user plane network element, the apparatus comprising:

23. A service registration apparatus applied to a service function storage entity, the apparatus comprising:

24. A service registration apparatus applied to a control plane network element, the apparatus comprising:

25. A service registration apparatus, for use in a user plane network element, the apparatus comprising a processor and a transceiver:

26. A service registration apparatus for a service function storage entity, the apparatus comprising a processor and a transceiver:

27. A service registration apparatus applied to a control plane network element, the apparatus comprising a processor and a transceiver:

28. A communication device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; it is characterized in that the preparation method is characterized in that,

the processor, configured to read a program in a memory to implement the steps in the service registration method according to any one of claims 1 to 10; or implementing the steps in the service registration method according to any of claims 11 to 13; or implementing the steps in the service registration method according to any of claims 14 to 21.

29. A readable storage medium storing a program, wherein the program, when executed by a processor, implements the steps in the service registration method of any one of claims 1 to 10; or implementing the steps in the service registration method according to any of claims 11 to 13; or implementing the steps in the service registration method according to any of claims 14 to 21.