WO2018076966A1 - 能力开放实现方法及装置、网元实体及存储介质 - Google Patents

能力开放实现方法及装置、网元实体及存储介质 Download PDF

Info

Publication number
WO2018076966A1
WO2018076966A1 PCT/CN2017/102447 CN2017102447W WO2018076966A1 WO 2018076966 A1 WO2018076966 A1 WO 2018076966A1 CN 2017102447 W CN2017102447 W CN 2017102447W WO 2018076966 A1 WO2018076966 A1 WO 2018076966A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
service
information
network
network device
Prior art date
Application number
PCT/CN2017/102447
Other languages
English (en)
French (fr)
Inventor
谢宝国
李志军
王卫斌
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018076966A1 publication Critical patent/WO2018076966A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • the embodiment of the present invention relates to the field of network communication technologies, and specifically relates to a method and device for implementing capability opening, a network element entity, and a storage medium.
  • the background traffic service (that is, the third-party application and the network perform signaling coordination, and transmit non-real-time large traffic during the idle time of the network, such as video push, software update, etc.) can fully utilize these idle wireless resources, so that the carrier's network can Being fully utilized, while enjoying very cheap traffic for users, it is also beneficial for SP/CP
  • FIG. 1 is a schematic diagram of a 3GPP EPS network capability open architecture (4G mobile network) according to the related art. As shown in FIG. 1, the network architecture may include the following parts:
  • the mobile network and the network element include: a control plane network element such as a Mobility Management Entity/Serving GPRS Support Node (MME/SGSN), which is responsible for signaling control and mobility. Management; user plane network element such as public data network gateway/gateway GPRS support node (PGW/GGSN, Public Data Network GateWay/Gateway GPRS Support Node), responsible for bearer control and session management; data plane network element such as home subscription user server (HSS) , Home Subscriber Server), responsible for user subscription management; policy control network element such as Policy and Charging Rules Function (PCRF, Policy of Charging Rules Function), responsible for user quality of service (Qos, Quality of Service) and billing strategy And issued; and other network elements (Other entities) and so on.
  • PCRF Policy and Charging Rules Function
  • the Capability Exposure Platform (CEP) is used to request network resources and information from the network according to the needs of third parties, providing differentiated services and a better user experience for users.
  • the CEP is connected to the MME/SGSN, the PGW/GGSN, the HSS, and the PCRF through the Tx interface, the Ty interface, the Sh interface, and the Rx interface.
  • the CEP and other NEs can be connected through the Tz interface.
  • Application server used by third parties to provide users with a variety of Internet services.
  • the mobile network uniformly exposes the mobile network information and the open mobile network capability through the capability open platform, and the open objects include third-party applications and operators' own applications.
  • the existing capability open network architecture can provide network capabilities to third-party applications under the 4G architecture.
  • Third-party applications can request to update QoS parameters, billing policy adjustments (such as third-party payment services), and user preferences through the capability open platform.
  • Information acquisition and other services are open, network device-related group access control and group management cannot cooperate with third parties, and third-party requirements related to group management cannot be transmitted to the network. That is to say, if the existing terminal-based signaling interaction is adopted, the effective transmission of various group management information between the third-party application and the network device cannot be realized, that is, the network device cannot implement group-based information. Efficient group management services.
  • the embodiments of the present invention provide a method and an apparatus for implementing the capability opening, which can implement the capability of group management, meet the differentiated service implementation of the third-party application based on the group service, and improve the service experience of the group user.
  • An embodiment of the present application provides a method for implementing an capability, including:
  • the network device obtains the service group information transmitted by the third party service through the capability open platform;
  • the network device performs group management on the terminals in the group according to the group network policy corresponding to the service group.
  • the service group information that is obtained by the third-party service through the capability open platform includes:
  • the network device receives group subscription and management information from the capability open platform;
  • the group subscription and management information includes group network information that the capability open platform maps service group information from the third party service into And group authentication information;
  • the network device generates a network according to group signing and management information from the capability open platform Group signing and management information for the device.
  • the embodiment of the present application further provides a capability opening implementation apparatus, including a first receiving module and a first processing module;
  • a first receiving module configured to be a service group information from a third party service
  • the first processing module is configured to transmit the service group information from the third party service to the network device.
  • the embodiment of the present application further provides a contract management function entity, including an acquisition module and a second processing module.
  • the obtaining module is configured to obtain group signing and management information of the service group according to the service group information transmitted by the third party service through the capability open platform;
  • the second processing module is configured to generate group subscription and management information of the network device according to the group subscription and management information from the capability open platform.
  • the embodiment of the present application further provides an access and mobility management function entity, including a second receiving module and a third processing module, where
  • a second receiving module configured to receive group subscription and management information of the network device from the subscription management function entity
  • the third processing module is configured to generate a group control plane context according to the group subscription and management information of the received network device, and perform access control on the terminal according to the terminal access control parameter in the group.
  • the embodiment of the present application further provides a session management function entity, including a third receiving module and a fourth processing module, where
  • a third receiving module configured to receive group signing and management information of the network device from the subscription management function entity
  • the fourth processing module is configured to generate a group user plane context according to the group subscription and management information of the received network device, and perform session control on the terminal according to the terminal session management policy in the group.
  • the embodiment of the present application further provides a policy management function entity, including a fourth receiving module, a fifth processing module; wherein
  • a fourth receiving module configured to receive group signing and management information of the network device from the subscription management function entity
  • the fifth processing module is configured to generate QoS management and group charging information according to the group network policy of the received network device and the group network policy in the management information, and send the information to the session management function.
  • the network device obtains the service group information that is transmitted by the third-party service through the capability open platform.
  • the network device implements the group network policy according to the service group.
  • the management of the terminals in the group is implemented, so that the capability of group management is opened, the differentiated service implementation of the third party service based on the group service is satisfied, and the service experience of the group user is improved.
  • the network device After the terminal accesses the network in the group mode, the network device implements the terminal access by group, the session management by group, and the unicast/multicast switching by group according to the related service customization parameters.
  • the operation of the mobility management and the like enables the network device and the third-party service to perform the signaling coordination of the group operation in real time, satisfies the differentiated requirement of the third-party service for the network resource, and optionally improves the user experience.
  • FIG. 1 is a schematic diagram of a 3GPP EPS network capability open architecture (4G mobile network);
  • FIG. 2 is a flowchart of a method for implementing capability opening according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of an embodiment of a future 5G system architecture according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of an embodiment of a terminal accessing a network by a group, a third party service download group signing and management information, and performing terminal access and group service control in a group according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of an embodiment of implementing unicast/multicast handover when a third party service performs group communication on different groups according to an embodiment of the present disclosure
  • FIG. 7 is a flowchart of an embodiment of a third party service mobility management of a group according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of a capability open platform according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a composition of a subscription management function entity according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a structure of an access and mobility management function entity according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a composition of a session management function entity according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a structure of a policy management function entity according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a network element entity according to an embodiment of the present disclosure.
  • FIG. 2 is a flowchart of a method for implementing capability opening according to an embodiment of the present application. As shown in FIG. 2, the method includes:
  • Step 200 The service group that the network device transmits according to the third-party service through the capability open platform Information, obtain group signing and management information of the business group.
  • the third-party services in this step include, but are not limited to, third-party service platforms or service providers.
  • the third-party service can manage the corresponding service group according to the requirements and service characteristics of different services.
  • the service group information of the service group includes but is not limited to: a group service identifier, a user service identifier list, a group service policy, and the like.
  • this step may include:
  • the capability open platform creates group subscription and management information on the capability open platform side according to the service group information from the third party service, including: the capability open platform maps the service group information from the third party service into the group network information, and will include The capabilities of the group network information open platform side group signing and management information and group authentication information are sent to the network side to request the network side to create the service group and manage according to the group network policy in the group network information.
  • the network side here refers to the network device that constitutes the network, the device corresponding to the terminal, and the network element entity that can exchange information with the terminal.
  • the mapping may be a translation process between information, or a replacement between information, or a correspondence between information.
  • a correspondence between a service group ID and a network group ID, and a correspondence between a service parameter and a network parameter are stored. Relationship, mapping directly replaces the service ID and parameters of the corresponding service group with the ID and parameters of the network device.
  • the group network information may be part of the group signing and management information on the capability open platform side, and the group signing and management information processing on the capability open platform side includes the group network information, and also includes the identification of the capability open platform and the capability open platform. One or more of the content of the right information.
  • the group network information includes but is not limited to: a group network identifier, a terminal identifier list, a group network policy, and the like.
  • the method further comprises:
  • the network device generates group signing and management information of the network device according to the group signing and management information from the capability open platform, and the group signing and management information of the network device includes but is not limited to: group Network identification, group network policy, terminal network identification list, terminal subscription information, etc.
  • the group network policy includes not limited to: group charging parameters, group QoS parameters, group terminal access control parameters, session control parameters, and the like.
  • the step may include:
  • the capability open platform uses the service group information from the third-party service to update the service group information of the capability-opening platform side of the corresponding service group saved by itself, and maps the updated service group information to the group network information and sends the information to the group network information.
  • the network device requests the network device to update the group network information of the service group and manage according to the updated group policy.
  • the method further comprises:
  • the capability opening platform sends the group signing and management information including the updated group network information to the network device; the network device updates the group signing and management information related to the network device according to the group signing and management information from the capability opening platform.
  • the step may include:
  • the capability open platform deletes the group subscription and management information of the capability open platform side of the corresponding service group saved by itself, and notifies the network device to delete the group network information of the service group.
  • the method further includes: deleting, by the network device, the group subscription and management information related to the network device of the service group.
  • Step 201 The network device performs group management on the group terminals according to the group network policy corresponding to the service group according to the group subscription and management information of the obtained service group.
  • the management of the terminals in the group includes, but is not limited to, management of group terminal authentication, access control, and session control.
  • the network device After the terminal accesses the network in the group, the network device determines, according to the group network identifier carried by the network, that the terminal performs access control and session control according to the group mode, and the network device follows its own
  • the created group signing and management information performs group management functions such as group authentication, group access control, and group service control.
  • the network device requests the service group information from the third-party service through the capability open platform.
  • the method in the embodiment of the present application further includes:
  • the subscription management function entity of the network device downloads the group subscription and management information of the network device to different network functional entities, such as an access and mobility management function entity, a session management function entity, and a policy management function entity.
  • the method of the embodiment of the present application further includes:
  • the access and mobility management function entity generates a group control plane context according to the group subscription and management information of the network device, and performs access control on the terminal in the group according to the group access control policy in the generated group control plane context.
  • the group control plane context includes a group identifier of the network device, a resident intra-group terminal list, a group access control policy, and the like, and performs access control according to the new intra-group terminal.
  • the group access control policy includes, but is not limited to, access restrictions of some terminals in different areas, and the number of terminal accesses.
  • the method of the embodiment of the present application further includes:
  • the session management function entity generates a group user plane context according to the group subscription and management information of the network device, and performs session control on the terminal according to the terminal session management policy in the group.
  • the group user plane context includes, but is not limited to, terminal session context information, group network identifier, and the like.
  • the method of the embodiment of the present application further includes:
  • the policy management function entity generates QoS management and group charging information, such as group QoS parameters and charging parameters, according to the group network signing of the network device and the group network policy in the management information, and sends the QoS parameters and the charging parameters to the session management function.
  • the group's session service performs QoS management and group accounting.
  • the method of the embodiment of the present application further includes:
  • the third-party service advertises the unicast or multicast mode to the service group according to the group communication requirements such as the service feature and the group charging feature, and delivers the group communication customized parameters to the network device through the capability open platform.
  • the network device receives the group communication customization parameters.
  • the group communication customization parameters include, but are not limited to, location area information, a unicast/multicast handover threshold interval corresponding to the location area, a group identity, and the like.
  • the method also includes:
  • the network device requests to establish a multicast bearer and initiate a unicast-to-multicast session switch according to the unicast/multicast handover threshold interval, when the number of unicasts of the terminal in the group exceeds the unicast threshold in a certain location area;
  • the terminal in the group requests to establish a unicast bearer, and initiates a multicast to unicast session switch.
  • the upper limit of the unicast/multicast handover threshold interval is a unicast threshold
  • the lower limit is a multicast threshold.
  • the method of the embodiment of the present application further includes:
  • the third-party service customizes the mobility behavior of the service group based on the group service characteristics, and delivers the mobility service customization parameters to the subscription management function of the network device through the capability open platform, so that the mobility management is performed through the capability open platform and the network device.
  • the method further comprises:
  • the subscription management function of the network device implements the access control and session continuity control of the mobile terminal movement according to the group-defined mobile service mode by using the network element of the network device delivered by the mobility customization parameter.
  • FIG. 3 is a schematic diagram of an embodiment of a future 5G system architecture according to an embodiment of the present disclosure.
  • the network device mainly includes: an access and mobility management module, a session management module, a subscription module, and a policy management module.
  • the network capability of the network device is open to third-party services through the capability open platform.
  • the access and mobility management module is responsible for NAS termination, access authentication, location registration, location update, etc.
  • the session management module is responsible for IP address allocation, session establishment, and session.
  • FIG. 3 is not used to define the future 5G system architecture, but is merely an example.
  • a third-party service groups a terminal belonging to the service according to different services. Groups are re-planned and given different business strategies for different groups. After the service group is re-planned, the network device needs to perform group creation, group update, and the like, and the deleted service group needs to release the group corresponding to the network device.
  • the third-party service initiates a group creation/group update process to the network device through the capability open platform, informing the network device to manage different terminals in a group manner, and sending the new or updated group policy to the network device.
  • Internet equipment In this embodiment, after a terminal accesses a network, a third-party service groups a terminal belonging to the service according to different services. Groups are re-planned and given different business strategies for different groups. After the service group is re-planned, the network device needs to perform group creation, group update, and the like, and the deleted service group needs to release the group corresponding to the network device.
  • the third-party service initiates a group creation/group update process to the network device through the
  • the capability open platform maps the service parameters and policies of the service group to the network parameters and policies of the network device, and delivers them to the contract management function entity of the network device.
  • the contract management entity creates or updates the network group, generates or updates the group subscription and management information of the group on the network device, and then sends the group to the network device network element where the terminal is located to perform group creation, update, and group policy execution. As shown in FIG. 4, it may include:
  • Step 400 The third-party service platform or service provider re-plans the service group according to different services, and assigns different group service policies to different groups. After the service is added, you need to create a new service group for the service. During the service development process, you need to update the service group according to the service requirements. After the service is released, you need to release the group created for the service.
  • the service group information of a service group created by a service includes but is not limited to: a group service identifier (id), a group user id list, a group service policy, and the like.
  • the group service policy includes, but is not limited to, a group QoS and a group charging policy, a mobility policy of the user in the group, and a group The user's session management policy, the access policy of users in the group, and so on.
  • Step 401 The third-party service service platform or the service provider initiates a service group creation or service group update request to the capability open platform, where the request message includes a group service id, a group user identification list, a group service policy, and the like. .
  • Step 402 After receiving the request for creating a group initiated by the service side, the capability open platform creates a group signing and management information on the capability open platform side and saves the group signing and management information on the capability open platform side.
  • the capability open platform maps the group service identifier into a group network identifier, maps the user service identifier list into a terminal network identifier list, and maps the group service policy into a group network policy.
  • the capability open platform receives the request to update the group or release the group, the capability open platform updates or releases the saved corresponding group subscription and management information.
  • Step 403 The capability opening platform sends a group creation/group update request to the subscription management function of the network device, where the request message carries the group subscription and management information created or updated by the capability open platform.
  • Step 404 If it is a group creation request, the subscription management function creates a new network group in the network device, and generates group subscription and management information of the network device for the network group.
  • the group subscription and management information of the network device includes but is not limited to Group network id, group list in the group, group network policy information, and so on.
  • the subscription management function can directly update the related group subscription and management information in the group subscription and management information of the network device.
  • Step 405 The subscription management function sends a group context creation request or an update request to the access and mobility management function of the terminal in the group, where the group network id, terminal list, group network policy and other parameters are carried.
  • Step 406 After receiving the group creation/update request, the access and mobility management function includes the connected intra-group terminal into a newly created group, and generates or updates a group control plane context.
  • the group control plane context includes a group identifier of the network device, a resident intra-group terminal list, a group access control policy, and the like, and accesses the intra-group terminal according to the new group access control policy. control.
  • the group access control policy includes, but is not limited to, access restrictions of some terminals in different areas, and the number of terminal accesses.
  • Step 407 The access and mobility management function sends a group creation/update request to the wireless side, where the group network identifier, the terminal list, the group radio access control policy and the like are carried, and the wireless side creates/updates the group user. Context, the network group identifier is used, and the terminal is restricted according to the group radio access policy.
  • Step 408 The access and mobility management function sends a request for updating the terminal identifier to the terminal, where the group identifier of the network device, the terminal identifier, the group policy, and the like are carried; the terminal adds the group identifier, and performs the connection according to the group policy. Incoming and session operations, and carrying the group identity in subsequent signaling.
  • Step 409 The subscription management function sends a group context creation/update request to the session management function of the terminal in the group, where the group network id, the terminal list, the group network policy and the like are carried.
  • Step 410 After receiving the group creation/update request, the session management function generates a group user plane context, where the group user plane context includes but is not limited to: a group network identifier, a resident group terminal list, and a group Group session management policies, etc.; subsequent session management functions perform session management according to the group session management policy.
  • the group user plane context includes but is not limited to: a group network identifier, a resident group terminal list, and a group Group session management policies, etc.
  • subsequent session management functions perform session management according to the group session management policy.
  • Step 411 The subscription management function sends a group policy creation/update request to the policy management function of the terminal in the group, where the group network id, the terminal list, and the group network policy are carried.
  • Step 412 After receiving the group policy creation/update request, the policy management function creates or updates a group policy parameter.
  • the group policy parameters include, but are not limited to, a total bandwidth limit of the group, a maximum delay limit, and information such as charging based on the group.
  • Step 413 to step 414 The policy management function sends the group PCC policy to the session management function, and the session management function updates the QoS parameter and the group charging parameter of the session according to the group PCC policy, and according to the QoS parameter of the updated session bearer. And the group charging parameters perform corresponding control.
  • the embodiment shown in FIG. 4 mainly illustrates that a third-party service platform or a service provider cooperates with a network device through a capability open platform when creating a group, updating a group, and deleting a group, and the network device will be connected.
  • the terminal accesses the created group, and performs access control, service authorization, and group policy delivery and control according to the group policy.
  • the third-party service platform or the service provider when creating a new group, requests the network device to create a group through the capability open platform, and the capability open platform maps the service parameters to network parameters, such as User ID, group ID, group policy parameters, etc.
  • the network device newly creates a network group in the contract, generates or updates the group subscription and management information, and sends the third-party coordinated group network policy to different management function entities and terminals, so that each entity performs the group policy. Access and session control.
  • FIG. 5 is a flowchart of an embodiment of a terminal accessing a network by a group, a third party service download group signing and management information, and performing terminal access and group service control in a group according to an embodiment of the present disclosure.
  • the group service data based on the third party service is obtained for access authentication and group session control.
  • the group identifier is carried.
  • the network device requests the group-based service from the third party service through the capability open platform.
  • the data information is generated, and the group subscription and management information of the network device is generated based on the group service data of the service side, including group authentication, access control, and service control information.
  • the network device performs group authentication, group access control, and group service restriction on the group terminal according to the group service data of the third party service.
  • Step 500 The terminal initiates a group terminal access request to the access and mobility management function, and the terminal carries the group network identifier and the terminal identifier when accessing the network.
  • Step 501 After receiving the terminal access request, the access and mobility management function requests the group subscription data and the terminal subscription data to the subscription management function, and carries the group network id and the terminal id in the request.
  • Step 502 The subscription management function is actually based on the group network identifier. If there is no corresponding group-related subscription data, or the group subscription data needs to be updated, the group service data request is initiated to the capability open platform, and the group is carried in the change request. The network identifier is mapped to the group service identifier, and then the subscription data of the group service is requested to the third party service, where the group service identifier is carried in the request.
  • Step 503 The third-party service sends the newly-created or updated group service subscription data to the capability open platform according to the group service identifier, and may also access the group user access control parameter, allow the group service identifier list to be initiated, and the like.
  • the capability open platform After the capability open platform receives the group service subscription data, it maps and saves on the capability open platform, and maps the group service subscription data into the group network subscription information and sends the contract to the network device. Management function.
  • Step 504 The subscription management function creates or updates group subscription and management information, including but not limited to group network identifier, group authentication parameter, group access control parameter, group session control parameter (such as group service allowed to be initiated). Identification list) and so on.
  • Steps 505 to 506 the subscription management function sends the newly created or updated group subscription and management information to the access and mobility management functions, and the access and mobility management functions are based on the group authentication parameters and the group access control parameters.
  • the group performs group authentication and access control in a group manner. In this way, the terminals in the group have different access restrictions on the terminals in different location areas, that is, mobility management by group is implemented.
  • Step 507 After the group authentication and access permission, the access and mobility management functions interact with the wireless side and the terminal, and allow the terminals in the group to access the network.
  • Step 508 The terminal of the group initiates a group service session request to the session management function entity to request to initiate a group service, where the group service session request carries a group network identifier, the group Business identity.
  • Step 509 The session management function requests the group subscription and management information from the subscription management function, where the request carries the group network identifier; the subscription management function sends the group service identifier list allowed by the group to the session management. Functional entity.
  • Step 510 The session management function entity determines, according to the group service identifier list allowed by the group, whether the group service initiated by the terminal is allowed. If the initiated group service is in the group service identifier list, the session is allowed to be established. A group service session; if the initiated group service is not in the allowed service list, it is considered to be a terminal service, not a group service, and the group is rejected. At this time, the terminal can only initiate the service in an individual manner. .
  • Step 511 If the group service is allowed, the session management function establishes a group service session for the terminal, and performs bandwidth allocation and group charging according to the PCC policy of the group service.
  • the embodiment shown in FIG. 5 mainly illustrates that if the terminal accesses according to the group mode, the service data of the group needs to be obtained from the third-party service for unified authentication, access control, and session of the group. management.
  • the obtained group service data may include a blacklist that the service provider prohibits access to users in the group, a group service authority and the like, and the use of the information enables access control and service authorization through the network device.
  • the updated group service data is downloaded from the third-party service, and operations such as authentication, access control, group service session establishment, and group PCC policy execution of the group terminal are implemented.
  • FIG. 6 is a flowchart of a method for implementing unicast/multicast handover when a third party service performs group communication on different groups according to an embodiment of the present disclosure.
  • This embodiment describes that a third party service will be unicast/multiple.
  • the broadcast handover threshold interval is sent to the network device through the capability open platform, where the upper limit of the unicast/multicast handover threshold interval is a unicast threshold, and the lower limit is a multicast threshold.
  • a multicast bearer is established for group communication of terminals in the group, and unicast to multicast session switching is performed; when the number of terminals in the group is lower than a multicast threshold
  • the network device establishes a unicast bearer for the group communication of the terminal in the group, and performs multicast to unicast session switching, and multicasts The session is switched to a unicast bearer.
  • the network resources can be optimized, and the requirements for the third-party services to independently select network resources according to service characteristics and charging characteristics can be satisfied. As shown in FIG. 6, it may include:
  • Step 600 The third-party service customizes the unicast/multicast threshold interval of the different location areas according to different service characteristics, such as the hotspot area and the non-hotspot area.
  • the upper limit of the unicast/multicast handover threshold interval is the unicast threshold.
  • the lower limit is the multicast threshold.
  • the unicast threshold and the multicast threshold may be different. For example, in the geographic area A, when the number of terminal accesses in the group exceeds the unicast threshold, for example, 10, the unicast to multicast switching is performed; when the multicast is established, if the multicast is established, if the multicast is established, If the number of terminal accesses in the group of the area A is lower than the multicast threshold, such as 5, the multicast to unicast switching is performed.
  • Step 601 The third-party service sends the unicast/multicast threshold interval of the established group communication to the capability open platform, and the capability open platform adds the location area and the unicast/multicast threshold interval parameter list to the group subscription. Information and save it locally;
  • the capability open platform sends a group communication customization request to the network device subscription management function, such as the HSS, which carries the group service identifier, the location area, and the unicast/multicast threshold interval parameter list;
  • the network device subscription management function such as the HSS, which carries the group service identifier, the location area, and the unicast/multicast threshold interval parameter list;
  • the subscription management function such as the HSS receiving the group communication customization request, updating the subscription information of the group, adding the correspondence between the group location area and the unicast/multicast threshold interval parameter list to the group subscription and management information of the network device. in.
  • Step 602 The subscription management function entity initiates a group subscription and management information update request to the access and mobility management function entity, and the access and mobility management function entity saves the correspondence between the location area and the unicast/multicast handover threshold.
  • Step 603 The terminal in the group requests the access network, where the group network identifier is carried.
  • the access and mobility management function entity allows the terminal to access the network.
  • Step 604 The access and mobility management function entity performs unicast/multicast handover threshold control. According to the location area of the terminal, it is determined whether the number of terminals in the location area exceeds a unicast threshold or is lower than a multicast threshold.
  • the terminals in the group use unicast to perform service interaction with the remote service.
  • Step 605 When the access and mobility management function entity determines that the number of unicast terminals in the group exceeds a unicast threshold, the access and mobility management function initiates a unicast to multicast handover request to the capability open platform, where The handover request carries a parameter value indicating a number of unicast terminals in the location area that exceeds a unicast threshold, a group network identifier, a location area, and the like.
  • Step 606 After receiving the unicast-to-multicast handover request of the group, the capability-opening platform initiates a request for establishing an MBMS multicast bearer to the MBMS server, and carries the group network identifier and the location area in the request for establishing the MBMS multicast bearer. Information and other parameters; the MBMS server establishes a multicast bearer in the location area to provide multicast services for the group.
  • Step 607 After the multicast bearer is established, the capability opening platform notifies the session management entity that the session management entity notifies the terminal to switch from the unicast bearer to the multicast bearer to perform a service session, and then releases the unicast bearer of the terminal in the location area.
  • Step 608 The terminal in the group is detached or removed from the location area.
  • Step 609 The access and mobility management function entity performs unicast/multicast handover threshold control, and determines whether the number of terminals in the location area exceeds a unicast threshold or is lower than a multicast threshold according to a location area of the terminal.
  • the terminals in the group use unicast to perform service interaction with the remote service.
  • Step 610 When the access and mobility management function entity determines that the number of multicast terminals in the group is lower than the multicast threshold, the access and mobility management function initiates a multicast to unicast handover request to the capability open platform.
  • the changeover request carries a parameter value indicating a number of multicast terminals in the location area that is lower than a multicast threshold, a group network identifier, a location area, and the like.
  • Step 611 After receiving the multicast-to-unicast handover request of the group, the capability-opening platform initiates a request to establish a unicast bearer setup in the group to the session management, and carries the group in the request for establishing the unicast bearer of the terminal in the group.
  • the group network identifier, the terminal identifier, and the like; the session management function is that the terminal in the group establishes a unicast bearer in the location area.
  • Step 612 After the unicast bearer is established, the capability open platform notifies the terminal to switch to the unicast bearer to perform a service session, and then notifies the MBMS server to release the multicast bearer of the group in the location area.
  • Step 612 to step 614 When the third-party service updates the unicast/multicast handover threshold interval of the group in different location areas according to the service requirement, the capability open platform sends the updated unicast/multicast handover threshold interval to the network device.
  • the network device re-determines whether the unicast/multicast switching operation needs to be performed according to the unicast/multicast handover threshold interval.
  • the embodiment shown in FIG. 6 mainly illustrates that in a group communication, if a third party service has a unicast/multicast threshold interval requirement for group communication in different geographical areas, the network device performs a single request based on the third party service requirement.
  • the switching of the multicast/multicast is satisfied by the third embodiment of the service characteristics and the charging characteristics of the third party, and the network resources are effectively optimized to avoid unicast resources occupying too many networks.
  • FIG. 7 is a flowchart of an embodiment of a third party service mobility management of a group according to an embodiment of the present disclosure.
  • a third party service delivers a group mobility service customization requirement to a network device through a capability open platform.
  • the contract management function sends the group mobility customization parameters to each network element of the network device to implement mobility management of the service customization. As shown in FIG. 7, it may include:
  • Step 700 The third-party service generates mobility customization information of different groups according to different service requirements.
  • the mobility service customization information includes but is not limited to: a group mobility access control parameter, a mobility service control parameter, a mobility QoS control parameter, and the like.
  • the mobility service customization information of the group customized by the third party service may include three types, the first category. It is a mobility access control parameter, such as specifying that the terminal moves in a fixed area, or does not move, or wide-area moves. When the mobile is out of range, access restrictions are imposed on terminal access and services.
  • the second category is mobility service control parameters, such as session guarantee business continuity, or no session continuity requirements, and third-party services guarantee business continuity.
  • the third category is that under different mobility management requirements, the QoS required for the service is also different. For example, when the hotspot area does not move, the bandwidth/delay demand is high; when the non-hotspot area moves, the QoS requirement can be reduced. When the hotspot area is removed, the general network may be accessed. In this case, the QoS requirements of non-hotspot coverage should be adopted. Therefore, the QoS parameters and charging parameters of the corresponding location area and network type are different.
  • Step 701 The third-party service sends the mobility service customization information of the group to the capability open platform.
  • the mobility service customization information of the group includes but is not limited to: a group service identifier, a mobility access control parameter of the group, and a mobile Sexual business session control parameters, mobility QoS control parameters, etc.
  • Step 702 The capability opening platform maps the group mobility service customization information into the group mobility network customization information, and saves the group subscription information and the management information in the group, and then groups the group mobility network. Customized information is sent to the contract management function entity of the network device.
  • Step 703 to step 704 The group terminal initiates an access request to the access and mobility management function entity of the network device and accesses the network.
  • the access and mobility management function acquires the mobility access control parameter of the group from the subscription management function entity, and defines a condition for the terminal to initiate location update according to the mobility access control parameter, such as performing location update across the base station, across the TA. List for location update, etc.
  • Step 705 Assuming that the location of the group terminal is changed, and the condition for the location update of the terminal is met, the terminal initiates a location update request to the access and mobility management function, where the location update request carries the location information of the terminal.
  • Step 706 The access and mobility management function is based on the group mobility access control policy, and determines whether the terminal is restricted according to the location information of the terminal, for example, the terminal moves the allowed bit. Set the area range.
  • Step 707 The group terminal initiates a session request to the session management function, where the session request carries a group network identifier and a group service identifier, and the session management function establishes a session for the terminal.
  • Step 708 The session management function requests the mobility session service control parameter of the group from the subscription management function.
  • the mobility session service control parameters include, but are not limited to, session control according to the service continuity feature, that is, part of the service does not require service continuity control, and is determined according to the group service identifier.
  • Step 709 When the terminal is updated, the session switching request is initiated to the session management function, where the session switching request carries the location information of the terminal.
  • Step 710 The session management function entity performs session switching management on the terminal based on the mobility session service control parameter. If the service has no service continuity requirement, the service continuity process may not be performed, and the terminal is directly in the new location. The area is newly created by the media plane, and the related session service is re-established and the continuity of the session is guaranteed by the third-party service.
  • Step 711 When the terminal updates the location, the subscription management function updates the mobility policy control policy to the session management function, and pushes the mobility QoS policy control parameter of the group to the policy management function.
  • the mobility QoS policy control parameters include but are not limited to: different location areas adopt different PCC policy parameters, such as different bandwidths, different charging parameters, and the like.
  • Step 712 The policy management function updates the PCC policy of the group and sends it to the session management function for execution.
  • Step 713 The session management function performs QoS update and charging policy update on the session service of the terminal based on the updated PCC policy.
  • the embodiment shown in FIG. 7 mainly illustrates that the third-party service delivers the group mobility service policy parameters customized according to the service requirements to the network device through the capability open platform, and the network device customizes the group mobility service according to the service side.
  • the policy performs access control, session switching, and QoS policy execution when the terminal location is updated in the group, and satisfies the differentiation of the service mobility of the group. demand.
  • FIG. 8 is a schematic structural diagram of a capability open platform according to an embodiment of the present application. As shown in FIG. 8 , at least a receiving module and a processing module are included;
  • a first receiving module configured to be a service group information from a third party service
  • the first processing module is configured to transmit the service group information from the third party service to the network device.
  • the first processing module may be configured to map the service group information from the third party service into group network information, and the capability open platform side including the group network information
  • the group signing and management information is sent to the network device to request the network device to create the service group and manage according to the group network policy in the group network information.
  • the group network information includes, but is not limited to, a group network identifier, a terminal identifier list, a group network policy, and the like.
  • the first processing module may be configured to update the service group on the capability open platform side of the corresponding service group saved by using the service group information from the third-party service.
  • the information is mapped to the group network information and sent to the network device to request the network device to update the group network information of the service group and manage according to the updated group policy.
  • the first processing module may be configured to delete the group subscription and management information of the capability open platform side of the corresponding service group saved by itself, and notify the network device to delete the service group. Group network information.
  • FIG. 9 is a schematic structural diagram of a component of a subscription management function entity according to an embodiment of the present disclosure. As shown in FIG. 9 , at least an acquisition module and a second processing module are included;
  • the obtaining module is configured to obtain group signing and management information of the service group according to the service group information transmitted by the third party service through the capability open platform;
  • a second processing module configurable to be based on group signing and management information from the capability open platform, Generate group subscription and management information for network devices.
  • the group subscription and management information of the network device includes but is not limited to: a group network identifier, a group network policy, a terminal network identifier list, and terminal subscription information.
  • the group network policy includes not limited to: group charging parameters, group QoS parameters, group terminal access control parameters, session control parameters, and the like.
  • the second processing module is further configured to update the group subscription and management information related to the network device according to the group subscription and management information from the capability open platform.
  • the second processing module is further configured to receive a notification of the group network information of the deleted service group from the capability open platform, and delete the group subscription and management information related to the network device of the service group.
  • the subscription management function entity of the embodiment of the present application further includes:
  • the delivery module can be configured to download the group subscription and management information of the network device to different network functional entities, such as an access and mobility management function entity, a session management function entity, and a policy management function entity.
  • network functional entities such as an access and mobility management function entity, a session management function entity, and a policy management function entity.
  • the obtaining module may be further configured to obtain, by using the capability open platform, a mobility service customization parameter of the mobility behavior of the service group customized by the third party service based on the group service feature.
  • the delivery module can also be configured to deliver mobility customization parameters to the access and mobility management function entity and the session management function entity.
  • FIG. 10 is a schematic structural diagram of a structure of an access and mobility management function entity according to an embodiment of the present application. As shown in FIG. 10, the method includes at least a second receiving module and a third processing module.
  • a second receiving module configured to receive group subscription and management information of the network device from the subscription management function entity
  • the third processing module is configured to generate a group control plane context according to the group subscription and management information of the received network device, and perform access control on the terminal according to the terminal access control parameter in the group.
  • the second receiving module is further configured to receive the mobility service customization parameter from the subscription management function entity;
  • the third processing module may be further configured to perform access control on the mobile terminal movement according to the customized mobility service mode according to the received mobility service customization parameter.
  • FIG. 11 is a schematic structural diagram of a session management function entity according to an embodiment of the present disclosure. As shown in FIG. 11, the method includes at least a third receiving module and a fourth processing module.
  • a third receiving module configured to receive group signing and management information of the network device from the subscription management function entity
  • the fourth processing module is configured to generate a group user plane context according to the group subscription and management information of the received network device, and perform session control on the terminal according to the terminal session management policy in the group.
  • the third receiving module is further configured to receive the mobility service customization parameter from the subscription management function entity;
  • the fourth processing module may be further configured to perform session continuity control on the mobile terminal movement according to the received mobility service customization parameter according to the group customized mobility service mode.
  • the third receiving module is further configured to receive QoS management and group charging information from the policy management function entity;
  • the fourth processing module is further configured to perform QoS management and group charging on the session service of the group according to the received QoS management and group charging information.
  • FIG. 12 is a schematic structural diagram of a structure of a policy management function entity according to an embodiment of the present disclosure. As shown in FIG. 12, the method includes at least a fourth receiving module and a fifth processing module.
  • a fourth receiving module configured to receive group subscription and management information of the network device from the subscription management function entity
  • the fifth processing module is configured to generate QoS management and group charging information, such as group QoS parameters and charging parameters, according to the group network policy of the received network device and the group network policy in the management information, and send the information to the session.
  • QoS management and group charging information such as group QoS parameters and charging parameters, according to the group network policy of the received network device and the group network policy in the management information, and send the information to the session.
  • Management function to perform QoS management and group accounting for session services of the group fee.
  • FIG. 13 is a network element entity, which may include a processor 21, a memory 22 storing instructions executable by the processor 21, a communication interface 23, and a connection processor 21, a memory 22, and a communication interface 23. Bus 24.
  • the network element entity 2 may be any one of the foregoing network element entities, for example, a subscription management function entity, an access and mobility management function entity, a session management function entity, a policy management function entity, or Ability to open the platform.
  • the processor 21 may be an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), or a Programmable Logic Device (PLD). At least one of a Programmable Logic Device, a Field Programmable Gate Array (FPGA), a CPU, a controller, a microcontroller, and a microprocessor. It will be appreciated that the electronics used to implement the above described processor functions may be other for different devices.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • DSPD Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • the network element entity 2 can also include a memory 22 that can be coupled to the processor 21, wherein the memory 22 is for storing executable program code, the program code includes computer operating instructions, and the memory 22 can include high speed RAM memory, It may also include a non-volatile memory, such as at least one disk storage.
  • the bus 24 is used to connect the communication interface 23, the processor 21 and the memory 22, and the mutual communication between these devices.
  • the processor 21 can implement the capability opening implementation method provided in the foregoing one or more technical solutions by executing a computer executable program such as a computer program, for example, the implementation of FIG. 2 can be implemented. To the method illustrated in any of FIG.
  • the embodiment of the present application provides a computer storage medium, where the computer storage medium stores executable instructions; the executable instructions may be a computer program or a software application, etc.; After the program is executed, the capability open implementation method provided in one or more of the foregoing technical solutions can be implemented, for example, the method illustrated in any of FIGS. 2 to 7 can be implemented.
  • the computer storage medium may be: a volatile first memory (volatile memory), such as a random access first memory (RAM), or a non-volatile memory.
  • volatile memory such as a random access first memory (RAM)
  • non-volatile memory For example, read-only memory (ROM, Read-Only Memory), flash memory, hard disk (HDD, Hard Disk Drive) or solid state drive (SSD, Solid-State Drive); A combination of memories.
  • ROM read-only memory
  • flash memory flash memory
  • HDD Hard Disk Drive
  • SSD Solid-State Drive
  • a combination of memories Optional for non-transitory storage media.
  • the network device obtains the service group information that is transmitted by the third-party service through the capability open platform.
  • the network device implements the group network policy corresponding to the service group.
  • the intra-group terminal manages, realizes the capability of group-based management, meets the differentiated service realization of the third-party service based on the group service, improves the service experience of the group users, and thus has positive industrial effects and is easy to implement.
  • the characteristics are industrially achievable.

Abstract

本申请实施例公开了一种能力开放实现方法及装置，网络设备通过获取第三方服务通过能力开放平台传递的业务群组信息，网络设备实现了按照业务群组对应的群组网络策略对组内终端进行管理，从而实现了基于组管理的能力开放，满足了第三方服务基于群组业务的差异化业务实现，提升了群组用户的业务体验。本发明实施例提供一种网元实体及计算机存储介质。

Description

能力开放实现方法及装置、网元实体及存储介质
本申请基于申请号为201610958518.5、申请日为2016年10月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及网络通信技术领域，具体涉及一种能力开放实现方法及装置、网元实体及存储介质。
背景技术
随着移动通信技术的飞速发展，人们生活方式、工作方式以及社会的政治、经济等各方面都带来了巨大的影响。人类社会进入高效的信息化时代，各个方面业务应用需求呈现爆发式增长，给未来无线移动带宽系统在频率、技术以及运营等各方面都带来了巨大的挑战。
随着互联网各类应用的丰富，第三方服务商对网络运营商的信息交互及网络个性需求愈来愈强烈，网络能力开放逐渐成为未来网络技术的主流。如目前移动个人用户、行业用户和服务提供商/内容提供商(SP/CP，Service Provider/Content Provider)使用的移动业务中有一部分为对时延不敏感的业务，比如软件更新和下载、音乐和视频下载等业务，而这类业务的数据流量偏大，如果采用正常流量套餐进行传输将会产生比较高的费用。在现网中，移动数据网络在时间和地域方面呈现明显的忙闲不均的特点，使得网络中存在许多空闲资源。背景流量业务(即第三方应用与网络进行信令协同，在网络空闲时段传输非实时的大流量，如视频推送、软件更新等)可以把这些空闲无线资源充分利用起来，使运营商的网络能够被充分利用，同时对于用户来说能够享受到非常便宜的流量，对于SP/CP来说也可以利 用低成本的背景流量通道分发业务和内容，从而促进用户对移动流量的使用，对运营商带来数据收入的增长。
移动互联时代下，运营商开放网络能力已是大势所趋。多年来，管道资源、网络优势一直是运营商的核心竞争力所在。但是，随着4G及5G时代的到来，丰富互联网应用逐渐使运营商成为单纯的管道提供商。因此，构建统一开放的能力，提供平台，合理开放基础业务及信息等能力成为运营商构建未来竞争力的关键所在。
图1为根据相关技术的3GPP EPS网络能力开放架构(4G移动网络)示意图，如图1所示，该网络架构可以包括如下部分：
移动网络及网元(MNE，Mobile Network and Entity)包括：控制面网元如移动管理节点/服务GPRS支持节点(MME/SGSN，Mobility Management Entity/Serving GPRS Support Node)，负责信令控制及移动性管理；用户面网元如公用数据网网关/网关GPRS支持节点(PGW/GGSN，Public Data Network GateWay/Gateway GPRS Support Node)，负责承载控制及会话管理；数据面网元如归属签约用户服务器(HSS，Home Subscriber Server)，负责用户的签约管理；策略控制网元如策略与计费规则功能(PCRF，Policy and Charging Rules Function)，负责用户服务质量(Qos，Quality of Service)及计费策略的制定及下发；及其他网元(Other entity)等。
能力开放平台(CEP，Capability Exposure Platform)，用于根据第三方的需求，向网络请求网络资源与信息，为用户提供差异化的服务及更好的用户体验。如图1所示，CEP与MME/SGSN、PGW/GGSN、HSS、PCRF之间分别通过Tx接口、Ty接口、Sh接口、Rx接口连接；CEP与其他网元之间可以通过Tz接口连接。
应用服务器(APP，Application Server)，用于第三方给用户提供丰富多样的互联网服务。
采用图1所示的能力开放架构，移动网络通过能力开放平台统一对外暴露移动网络信息和开放移动网络能力，开放的对象包括第三方应用和运营商自有应用等。
现有能力开放网络架构可以在4G架构下向第三方应用提供网络能力的开放，第三方应用可以通过能力开放平台请求更新QoS参数、计费策略调整(如第三方为用户付费业务)、用户偏好信息获取等服务。但是，现有技术中缺乏对基于组的能力开放，网络设备对组相关的接入控制及组管理无法与第三方进行协同，第三方对组管理相关的需求无法传导到网络中。也就是说，如果采用现有基于终端进行信令交互的方式，是无法实现第三方应用与网络设备之间各种组管理信息的有效传递的，也就是说，网络设备是无法实现基于组的高效的组管理服务的。
发明内容
本申请实施例提供一种能力开放实现方法及装置，能够实现基于组管理的能力开放，满足第三方应用基于组业务的差异化业务实现，提升组用户的业务体验。
本申请实施例提供了一种能力开放实现方法，包括：
网络设备获取第三方服务通过能力开放平台传递的业务群组信息；
网络设备按照业务群组对应的群组网络策略对组内终端进行组管理。
可选地，所述能力开放平台接收到来自第三方服务的业务群组创建请求时，所述获取第三方服务通过能力开放平台传递的业务群组信息包括：
所述网络设备接收来自所述能力开放平台的组签约及管理信息；所述组签约及管理信息包含所述能力开放平台将来自所述第三方服务的业务群组信息映射成的群组网络信息以及群组鉴权信息；
所述网络设备根据来自能力开放平台的组签约及管理信息，生成网络 设备的组签约及管理信息。
本申请实施例还提供了一种能力开放实现装置，包括第一接收模块、第一处理模块；其中，
第一接收模块，配置为来自第三方服务的业务群组信息；
第一处理模块，配置为将来自第三方服务的业务群组信息传递给网络设备。
本申请实施例再提供了一种签约管理功能实体，包括获取模块、第二处理模块；其中，
获取模块，配置为根据第三方服务通过能力开放平台传递的业务群组信息，获取业务群组的组签约及管理信息；
第二处理模块，配置为根据来自能力开放平台的组签约及管理信息，生成网络设备的组签约及管理信息。
本申请实施例又提供了一种接入及移动性管理功能实体，包括第二接收模块、第三处理模块；其中，
第二接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第三处理模块，配置为根据接收到的网络设备的组签约及管理信息，生成组控制面上下文；根据组内终端接入控制参数对终端进行接入控制。
本申请实施例还提供了一种会话管理功能实体，包括第三接收模块、第四处理模块；其中，
第三接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第四处理模块，配置为根据接收到的网络设备的组签约及管理信息，生成组用户面上下文；根据组内终端会话管理策略对终端进行会话控制。
本申请实施例又提供了一种策略管理功能实体，包括第四接收模块、 第五处理模块；其中，
第四接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第五处理模块，配置为根据接收到的网络设备的组签约及管理信息中的群组网络策略，生成QoS管理及组计费信息并下发给会话管理功能。
在本申请实施例提供的技术方案中，网络设备通过获取第三方服务通过能力开放平台传递的业务群组信息，在需要进行组管理时，网络设备实现了按照业务群组对应的群组网络策略对组内终端进行管理，从而实现了基于组管理的能力开放，满足了第三方服务基于群组业务的差异化业务实现，提升了群组用户的业务体验。
当终端按群组的方式接入网络后，网络设备按照相关业务定制参数实现了终端按群组接入、按群组进行会话管理，按群组进行单播/多播的切换，按群组进行移动性管理等操作，使得网络设备与第三方服务实时进行了群组操作的信令协同，满足了第三方服务对网络资源的差异化需求，可选地提升了用户体验。
本申请实施例的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请实施例而了解。本申请实施例的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
此处所说明的附图用来提供对本申请实施例的进一步理解，构成本申请的一部分，本申请实施例的示意性实施例及其说明用于解释本申请实施例，并不构成对本申请实施例的不当限定。在附图中：
图1为一种3GPP EPS网络能力开放架构(4G移动网络)示意图；
图2为本申请实施例提供的一种能力开放实现方法的流程图；
图3为本申请实施例提供的一种涉及的未来5G系统架构实施例的示意图；
图4为本申请实施例提供的一种群组创建/更新/删除的实施例的流程图；
图5为本申请实施例提供的一种终端按群组接入网络，由第三方服务下载组签约及管理信息，进行群组内终端接入及群组业务控制的实施例的流程图；
图6为本申请实施例提供的一种第三方服务对不同的群组进行群组通信时，实现单播/多播切换的实施例的流程图；
图7为本申请实施例提供的一种第三方服务对群组的移动性管理的实施例的流程图；
图8为本申请实施例提供的一种能力开放平台的组成结构示意图；
图9为本申请实施例提供的一种签约管理功能实体的组成结构示意图；
图10为本申请实施例提供的一种接入及移动性管理功能实体的组成结构示意图；
图11为本申请实施例提供的一种会话管理功能实体的组成结构示意图；
图12为本申请实施例提供的一种策略管理功能实体的组成结构示意图；
图13为本申请实施例提供的一种网元实体的组成结构示意图。
具体实施方式
下面结合附图对本申请实施例的实施例进行说明，需要说明的是，在不冲突的情况下，本申请中的实施例和实施例中的特征可以相互任意组合。
图2为本申请实施例能力开放实现方法的流程图，如图2所示，包括：
步骤200：网络设备根据第三方服务通过能力开放平台传递的业务群组 信息，获取业务群组的组签约及管理信息。
本步骤中的第三方服务包括但不限于：第三方业务平台或服务提供商。
第三方服务可以根据不同业务的需求、业务特征，管理相应的业务群组，业务群组的业务群组信息包括但不限于：群组业务标识、用户业务标识列表、群组业务策略等。
当能力开放平台接收到来自第三方服务的业务群组创建请求时，本步骤可包括：
能力开放平台根据来自第三方服务的业务群组信息创建能力开放平台侧的组签约及管理信息，包括：能力开放平台将来自第三方服务的业务群组信息映射为群组网络信息，并将包括群组网络信息的能力开放平台侧组签约及管理信息以及群组鉴权信息发送给网络侧，以请求网络侧对该业务群组进行创建并按照群组网络信息中的群组网络策略进行管理。这里的网络侧泛指的是组成网络的网络设备，是与终端相对应的设备，是可以与终端进行信息交互的网元实体等。
映射可是信息之间的翻译过程，或信息之间的替换，或信息之间的对应，在能力开放平台，存储有业务群组ID与网络群组ID的对应关系、业务参数与网络参数的对应关系，映射即直接将相应业务群组的业务ID及参数替换成网络设备的ID及参数即可。
群组网络信息可是能力开放平台侧的组签约及管理信息的组成部分，能力开放平台侧的组签约及管理信息处理包括群组网络信息外，还包括能力开放平台的标识、能力开放平台的鉴权信息等内容中的一个或多个。
其中，群组网络信息包括但不限于：群组网络标识、终端标识列表、群组网络策略等。相应地，该方法还包括：
网络设备根据来自能力开放平台的组签约及管理信息，生成网络设备的组签约及管理信息，网络设备的组签约及管理信息包括但不限于：群组 网络标识、群组网络策略、终端网络标识列表，终端签约信息等。其中群组网络策略包括不限于：组计费参数、组QoS参数、组内终端接入控制参数、会话控制参数等。
当能力开放平台接收到来自第三方服务的业务群组更新请求时，本步骤可包括：
能力开放平台利用来自第三方服务的业务群组信息，更新自身保存的对应业务群组的能力开放平台侧的业务群组信息，并将更新后的业务群组信息映射为群组网络信息发送给网络设备，以请求网络设备对该业务群组的群组网络信息进行更新并按照更新后的群组策略进行管理。相应地，该方法还包括：
能力开放平台将包括更新后的群组网络信息的组签约及管理信息发送给网络设备；网络设备根据来自能力开放平台的组签约及管理信息，更新网络设备相关的组签约及管理信息。
当能力开放平台接收到来自第三方服务的业务群组删除请求时，本步骤可包括：
能力开放平台删除自身保存的对应业务群组的能力开放平台侧的组签约及管理信息，并通知网络设备删除该业务群组的群组网络信息。相应地，该方法还包括：网络设备删除该业务群组的网络设备相关的组签约及管理信息。
步骤201：网络设备根据获得的业务群组的组签约及管理信息，按照业务群组对应的群组网络策略对组内终端进行组管理。
本步骤中，对组内终端进行管理包括但不限于：进行群组终端鉴权、接入控制、会话控制等管理。可包括：
当群组内终端接入到网络后，网络设备根据其携带的组网络标识判断出终端是按照群组的方式进行接入控制及会话控制，网络设备按照自身已 创建的组签约及管理信息进行组鉴权、组接入控制、群组业务控制等群组管理功能。
可选地，如果网络设备的签约管理功能实体没有对应该终端的组签约及管理信息，那么，网络设备通过能力开放平台向第三方服务请求业务群组信息。
在网络设备创建了组签约及管理信息之后，本申请实施例方法还包括：
网络设备的签约管理功能实体将网络设备的组签约及管理信息下载到不同的网络功能实体，比如：接入及移动性管理功能实体、会话管理功能实体、策略管理功能实体。
可选地，本申请实施例方法还包括：
接入及移动性管理功能实体根据网络设备的组签约及管理信息，生成组控制面上下文，并根据生成的组控制面上下文中的群组接入控制策略对群组内终端进行接入控制。其中，群组控制面上下文包括网络设备的群组标识、驻留的群组内终端列表、群组接入控制策略等，并按照新的对群组内终端进行接入控制。其中，群组接入控制策略包括但不限于：部分终端在不同区域的接入限制，终端接入数量等参数。
可选地，本申请实施例方法还包括：
会话管理功能实体根据网络设备的组签约及管理信息，生成组用户面上下文，并根据组内终端会话管理策略对该终端进行会话控制。所述组用户面上下文包括但不限于：终端会话上下文信息、组网络标识等。
可选地，本申请实施例方法还包括：
策略管理功能实体根据网络设备的组签约及管理信息中的群组网络策略，生成QoS管理及组计费信息如组QoS参数、计费参数等，并下发给会话管理功能，以对该群组的会话业务进行QoS管理及组计费。
可选地，本申请实施例方法还包括：
第三方服务根据业务特性、组计费特性等群组通信需求，对业务群组定制单播或多播方式，并通过能力开放平台将群组通信定制参数下发给网络设备。这样网络设备，就会接收到所述群组通信定制参数。所述群组通信定制参数包括但不限于：位置区域信息、位置区域对应的单播/多播切换阈值区间、群组标识等。该方法还包括：
网络设备根据单播/多播切换阈值区间，在群组中的终端在某一位置区域的单播数量超过单播阈值时，请求建立多播承载，并发起单播向多播的会话切换；在群组中的终端在某一位置区域的多播数量低于多播阈值时，请求建立单播承载，并发起多播向单播的会话切换。其中，单播/多播切换阈值区间的上限是单播阈值，下限是多播阈值。
可选地，本申请实施例方法，还包括：
第三方服务基于组业务特性定制业务群组的移动性行为，并通过能力开放平台将移动性业务定制参数下发给网络设备的签约管理功能，以使得通过能力开放平台与网络设备进行移动性管理协同。相应地，该方法还包括：
网络设备的签约管理功能将移动性定制参数下发的网络设备的各个网元，实现按照群组定制的移动性业务方式，对移动的终端移动进行接入控制及会话连续性控制。
图3为本申请实施例涉及的未来5G系统架构实施例的示意图，在未来的5G网络架构中，网络设备主要包括：接入与移动性管理模块、会话管理模块、签约模块、策略管理模块组成，网络设备的网络能力通过能力开放平台对第三方服务进行开放。如图3所示，终端接入网络时，由接入与移动性管理模块负责NAS终结、接入鉴权、位置注册、位置更新等管理；由会话管理模块负责IP地址分配、会话建立、会话更新、会话切换、会话策略执行等管理；由签约管理模块负责终端签约及鉴权数据的下发及更新； 由策略管理模块策略参数创建、动态更新等管理。能力开放平台负责开放网络设备的网络能力，将第三方服务的需求传递给网络设备，并协同第三方服务与网络设备的网络能力更新信令协商。需要说明的是,图3并不用于限定未来5G系统架构，只是一个示例而已。
下面基于图3所示的网络架构，结合具体实施例对本申请实施例的能力开放实现方法进行详细描述。
图4为本申请实施例群组创建、群组更新的实施例的流程图，本实施例显示的是，当终端接入网络后，第三方服务根据不同的业务对属于该业务的终端按群组进行重新规划，并赋予不同群组不同的业务策略。当业务群组重新规划后，需要对网络设备进行群组的创建、群组更新等操作，对删除的业务群组需要释放对应在网络设备的群组。在本实施例中，第三方服务通过能力开放平台向网络设备发起组创建/组更新流程，通知网络设备将不同的终端以群组的方式进行管理，并将新建或更新群组策略下发给网络设备。能力开放平台将业务群组的业务参数及策略映射为网络设备的网络参数及策略，并下发到网络设备的签约管理功能实体。签约管理实体创建或更新网络组，生成或更新该组在网络设备的组签约及管理信息，然后再下发给终端所在的网络设备网元进行群组的创建、更新及群组策略的执行。如图4所示，可包括：
步骤400：第三方业务平台或服务提供商根据不同的业务，对业务群组进行重新规划，并赋予不同群组不同的群组业务策略。在业务新增后，需要为该业务创建新的业务群组；业务开展过程中，需要根据业务需求更新该业务群组；当业务释放后，需要释放为该业务所建的群组。
一个业务创建的业务群组的业务群组信息包括但不限于：群组业务标识(id)，群组内用户id列表，群组业务策略等。其中，群组业务策略包括但不限于：群组QoS及群组计费策略、群组内用户的移动性策略、群组内 用户的会话管理策略、群组内用户的接入策略等。
步骤401：第三方服业务平台或服务提供商向能力开放平台发起业务群组创建或业务群组更新的请求，请求消息中包括群组业务id，群组内用户标识列表，群组业务策略等。
步骤402：能力开放平台收到业务侧发起的创建群组的请求后，在能力开放平台上创建一个能力开放平台侧的组签约及管理信息并保存，在能力开放平台侧的组签约及管理信息中，能力开放平台将群组业务标识映射成群组网络标识，将用户业务标识列表映射成终端网络标识列表，将群组业务策略映射成组网络策略。
如果能力开放平台接收到的是更新群组或释放群组的请求，能力开放平台更新或释放保存的相应的组签约及管理信息即可。
步骤403：能力开放平台向网络设备的签约管理功能发送群组创建/群组更新请求，在请求消息中携带有能力开放平台创建或更新的组签约及管理信息。
步骤404：如果是群组创建请求，签约管理功能在网络设备创建一个新的网络组，并为该网络组生成网络设备的组签约及管理信息，网络设备的组签约及管理信息包括但不限于群组网络id、群组内终端列表、群组网络策略信息等。
如果收到的是群组更新请求，那么，签约管理功能就直接在网络设备的组签约及管理信息中更新相关的组签约及管理信息即可。
步骤405：签约管理功能向群组内终端所在的接入及移动性管理功能发送群组上下文创建请求或更新请求，其中携带有群组网络id、终端列表、群组网络策略等参数。
步骤406：接入及移动性管理功能收到群组创建/更新请求后，将已接入的群组内终端纳入一个新创建的群组中，生成或更新群组控制面上下文， 其中，群组控制面上下文包括网络设备的群组标识、驻留的群组内终端列表、群组接入控制策略等，并按照新的群组接入控制策略对群组内终端进行接入控制。其中，群组接入控制策略包括但不限于：部分终端在不同区域的接入限制，终端接入数量等参数。
步骤407：接入及移动性管理功能向无线侧发送群组创建/更新请求，其中携带有群组网络标识，终端列表，群组无线接入控制策略等信息；无线侧创建/更新群组用户上下文，采用网络组标识，并根据群组无线接入策略对终端进行接入限制。
步骤408：接入及移动性管理功能向终端发送更新终端标识的请求，其中携带有网络设备的群组标识，终端标识，群组策略等；终端增加群组标识，并根据群组策略进行接入及会话操作，而且会在后续的信令中携带群组标识。
步骤409：签约管理功能向群组内终端所在的会话管理功能发送群组上下文创建/更新请求，其中携带有群组网络id、终端列表、群组网络策略等参数。
步骤410：会话管理功能收到群组创建/更新请求后，生成群组用户面上下文，其中，群组用户面上下文包括但不限于：群组网络标识、驻留的群组内终端列表、群组会话管理策略等；后续会话管理功能按照群组会话管理策略进行会话管理。
步骤411：签约管理功能向群组内终端所在的策略管理功能发送群组策略创建/更新请求，其中携带有群组网络id、终端列表、群组网络策略等参数。
步骤412：策略管理功能收到群组策略创建/更新请求后，创建或更新群组策略参数。其中，群组策略参数包括但不限于群组的总带宽限制、最大延时限制，基于群组进行计费等信息。
步骤413～步骤414：策略管理功能将群组PCC策略发送给会话管理功能，会话管理功能基于群组PCC策略更新会话承载的QoS参数及组计费参数，并按照更新后的会话承载的QoS参数及组计费参数执行相应控制。
图4所示的实施例主要说明了：第三方业务平台或服务提供商在创建群组、更新群组、删除群组时，通过能力开放平台与网络设备进行协同，网络设备将已接入的终端接入到创建的群组中，并根据群组的策略对终端进行接入控制、业务授权、群组策略的下发及控制。按照本申请实施例提供的技术方案，第三方业务平台或服务提供商在创建一个新群组时，通过能力开放平台向网络设备请求创建群组，能力开放平台将业务参数映射为网络参数，如用户标识、群组标识、群组策略参数等。网络设备在签约中新创建网络群组，生成或更新组签约及管理信息，并将第三方协同的群组网络策略下发给不同的管理功能实体及终端，实现了各个实体按照群组策略进行接入及会话控制。
图5为本申请实施例终端按群组接入网络，由第三方服务下载组签约及管理信息，进行群组内终端接入及群组业务控制的实施例的流程图，本实施例描述终端基于群组接入或进行群组会话请求时，得到基于第三方服务的群组业务数据进行接入鉴权及群组会话控制。当群组终端接入时携带有群组标识，如果终端进行鉴权及接入控制时没有群组签约及管理信息，那么，网络设备会通过能力开放平台向第三方服务请求基于群组的业务数据信息，并基于业务侧的群组业务数据生成网络设备的群组签约及管理信息，包含群组鉴权、接入控制及业务控制信息等。网络设备基于第三方服务的群组业务数据对组内终端按组的方式进行群组鉴权、群组接入控制及群组业务限制。
步骤500：终端向接入及移动性管理功能发起群组内终端接入请求，终端接入网络时携带群组网络标识、终端标识。
步骤501：接入及移动性管理功能收到终端接入请求后，向签约管理功能请求组签约数据及终端签约数据，并在请求中携带有群组网络id、终端id。
步骤502：签约管理功能实根据群组网络标识，如果没有对应群组相关的签约数据，或组签约数据需要更新，则向能力开放平台发起群组业务数据请求，在改请求中携带有群组网络标识；能力开放平台将群组网络标识映射为群组业务标识，然后向第三方服务请求该群组业务的签约数据，在该请求中携带有群组业务标识。
步骤503：第三方服务根据群组业务标识，将新建或更新的群组业务签约数据下发给能力开放平台，还可以将群组用户接入控制参数，允许发起的群组业务标识列表等下发给能力开放平台；能力开放平台收到群组业务签约数据后，在能力开放平台上进行映射并保存，并将群组业务签约数据映射成的群组网络签约信息下发给网络设备的签约管理功能。
步骤504：签约管理功能创建或更新组签约及管理信息，包括但不限于群组网络标识、群组鉴权参数，群组接入控制参数，群组会话控制参数(如允许发起的群组业务标识列表)等。
步骤505～步骤506，签约管理功能将新建或更新的组签约及管理信息下发到接入及移动性管理功能，接入及移动性管理功能基于群组鉴权参数及群组接入控制参数，对该终端按群组的方式进行群组鉴权及接入控制。这样，群组内终端在不同的位置区域会对终端有差异化的接入限制，即实现了按群组进行移动性管理。
步骤507：群组内终端在群组鉴权通过及接入允许后，接入及移动性管理功能与无线侧及终端进行交互，允许该群组内的终端接入网络。
步骤508：该群组的终端向会话管理功能实体发起群组业务会话请求，以请求发起群组业务，在群组业务会话请求中携带有群组网络标识，群组 业务标识。
步骤509：会话管理功能向签约管理功能请求该群组签约及管理信息，在该请求中携带有该群组网络标识；签约管理功能将该群组允许的群组业务标识列表下发给会话管理功能实体。
步骤510：会话管理功能实体根据该群组允许的群组业务标识列表，判断该终端发起的群组业务是否被允许，如果发起的群组业务在该群组业务标识列表内，则允许建立该群组业务会话；如果发起的群组业务不在该允许的业务列表内，则认为是终端业务，不是群组业务，该群组会被拒绝，此时，终端只能以个体的方式发起该业务。
步骤511：如果该群组业务被允许，会话管理功能为该终端建立群组业务会话，并按照群组业务的PCC策略进行带宽分配及进行组计费。
图5所示的实施例主要说明了：如果是终端按照群组方式进行接入，需要从第三方服务获取该群组的业务数据，用于该群组的统一鉴权、接入控制及会话管理。获得的群组业务数据中可能包括服务商对组内用户禁止接入的黑名单，群组业务权限等相关限制，利用这些信息实现了通过网络设备进行接入控制及业务授权。当群组终端接入并进行会话时，从第三方服务下载更新的群组业务数据，实现了对群组终端的鉴权、接入控制、群组业务会话建立、组PCC策略执行等操作。
图6为本申请实施例第三方服务对不同的群组进行群组通信时，实现单播/多播切换的实施例的流程图，本实施例描述的是，第三方服务将单播/多播切换阈值区间通过能力开放平台下发给网络设备，其中，单播/多播切换阈值区间的上限是单播阈值，下限是多播阈值。当在一定位置区域的终端数量超过单播阈值时，为组内终端的群组通信建立多播承载，并进行单播向多播的会话切换；当群组内终端数量低于多播阈值时，网络设备为群组内终端的群组通信建立单播承载，并进行多播向单播会话切换，将多播 会话切换到单播承载上。通过对多播/单播方式的控制，既可以优化网络资源，也可以满足第三方服务根据业务特性及计费特性，自主选择网络资源的需求。如图6所示，可包括：
步骤600：第三方服务根据不同的业务特性，比如区分热点区域与非热点区域，定制不同位置区域的单播/多播阈值区间，其中，单播/多播切换阈值区间的上限是单播阈值，下限是多播阈值。
单播阈值与多播阈值可以不同，比如在地理区域A，当群组内终端接入数量超过单播阈值如为10，则进行单播到多播的切换；当多播建立后，如果地理区域A的群组内终端接入数量低于多播阈值如为5，则进行多播到单播的切换。
步骤601：第三方服务将建立好的群组通信的单播/多播阈值区间下发给能力开放平台，能力开放平台将位置区域及单播/多播阈值区间参数列表加入该群组的签约信息并保存在本地；
能力开放平台向网络设备的签约管理功能如HSS发起发送群组通信定制请求，其中携带有群组业务标识、位置区域，以及单播/多播阈值区间参数列表等；
签约管理功能如HSS收到群组通信定制请求，更新该群组的签约信息，将该群组位置区域及单播/多播阈值区间参数列表的对应关系加到网络设备的组签约及管理信息中。
步骤602：签约管理功能实体向接入及移动性管理功能实体发起群组签约及管理信息更新请求，接入及移动性管理功能实体保存位置区域与单播/多播切换阈值的对应关系。
步骤603：群组内终端请求接入网络，其中携带有群组网络标识，本实施例中，假设接入及移动性管理功能实体允许该终端接入到网络。
步骤604：接入及移动性管理功能实体执行单播/多播切换阈值控制， 根据终端的位置区域，对该位置区域的终端数量是否超出单播阈值或低于多播阈值进行判断。
如果该位置区域内的终端数量未超过多播阈值，群组内终端都采用单播方式与远程服务进行业务交互。
步骤605：当接入与移动性管理功能实体判断出群组内单播终端的数量超过单播阈值时，接入与移动性管理功能向能力开放平台发起单播向多播的切换请求，在该切换请求中携带有表明该位置区域内的单播终端数量超过单播阈值的原因值，群组网络标识、位置区域等参数。
步骤606：能力开放平台收到群组的单播向多播切换请求后，向MBMS服务器发起建立MBMS多播承载的请求，在建立MBMS多播承载的请求中携带有群组网络标识、位置区域信息等参数；MBMS服务器在该位置区域建立多播承载，为该群组提供组播服务。
步骤607：当多播承载建立后，能力开放平台通知会话管理实体，会话管理实体通知终端从单播承载切换到多播承载上进行业务会话，然后释放该位置区域内终端的单播承载。
步骤608：群组内终端去附着，或移出该位置区域。
步骤609：接入及移动性管理功能实体执行单播/多播切换阈值控制，根据终端的位置区域，对该位置区域的终端数量是否超出单播阈值或低于多播阈值进行判断。
如果该位置区域内的终端数量未超过多播阈值，群组内终端都采用单播方式与远程服务进行业务交互。
步骤610：当接入与移动性管理功能实体判断注群组内多播终端的数量低于多播阈值时，接入与移动性管理功能向能力开放平台发起多播向单播的切换请求，在改切换请求中携带有表明该位置区域内的多播终端数量低于多播阈值的原因值，群组网络标识、位置区域等参数。
步骤611：能力开放平台收到群组的多播向单播切换请求后，向会话管理发起建立组内终端单播承载建立的请求，在建立组内终端单播承载建立的请求中携带有群组网络标识、终端标识等参数；会话管理功能为群组内终端在该位置区域建立单播承载。
步骤612：当单播承载建立后，能力开放平台通知终端切换到单播承载上进行业务会话，然后通知MBMS服务器释放该位置区域内该群组的多播承载。
步骤612～步骤614：当第三方服务根据业务需求更新群组在不同位置区域的单播/多播切换阈值区间时，能力开放平台将更新的单播/多播切换阈值区间发送给网络设备；网络设备根据单播/多播切换阈值区间重新判断是否需要进行单播/多播的切换操作，具体步骤如上，这里不再赘述。
图6所示的实施例主要说明了：在群组通信中，如果第三方服务对不同地理区域的群组通信有单播/多播阈值区间的需求，网络设备则基于第三方业务需求进行单播/多播的切换，通过本实施例，满足了第三方业务特性及计费特性的差异化需求，并有效对网络资源进行了优化，避免了在占用过多网络的单播资源。
图7为本申请实施例第三方服务对群组的移动性管理的实施例的流程图，本实施例中，第三方服务通过能力开放平台将群组移动性业务定制需求下发给网络设备的签约管理功能，签约管理功能将群组移动性定制参数下发到网络设备的各个网元，以实现业务定制的移动性管理。如图7所示，可包括：
步骤700：第三方服务根据不同业务需求，生成不同群组的移动性定制信息。其中，移动性业务定制信息包括但不限于：群组的移动性接入控制参数，移动性业务控制参数，移动性QoS控制参数等。
第三方服务定制的群组的移动性业务定制信息可以包括3类，第一类 是移动性接入控制参数，比如规定终端在固定区域移动、或不移动、或广域移动等。当移动超出范围时，对终端接入及业务进行接入限制。
第二类是移动性业务控制参数，比如会话保证业务连续性，或没有会话连续性需求，由第三方服务保证业务的连续性。
第三类是在不同的移动性管理需求下，其业务所需的QoS也是不一样的，比如在热点区域不移动时，带宽/时延需求高；在非热点区域移动时，QoS需求可以减低；当移出热点区域时，可能会接入通用网络，此时，应采用非热点覆盖的QoS需求。因此，对应的位置区域及网络类型，其QoS参数及计费参数是不一样的。
步骤701：第三方服务将群组的移动性业务定制信息发送给能力开放平台，群组的移动性业务定制信息包括但不限于：群组业务标识，群组的移动性接入控制参数，移动性业务会话控制参数，移动性QoS控制参数等。
步骤702：能力开放平台将群组移动性业务定制信息映射为群组移动性网络定制信息，并保存在该群组的群组签约及管理信息中，然后将该群组的群组移动性网络定制信息发送给网络设备的签约管理功能实体。
步骤703～步骤704：群组终端向网络设备的接入及移动性管理功能实体发起接入请求并接入所述网络。接入及移动性管理功能从签约管理功能实体获取所述群组的移动性接入控制参数，根据该移动性接入控制参数定义终端发起位置更新的条件，比如跨基站进行位置更新，跨TA list进行位置更新等。
步骤705：假设群组终端位置发生了变更，符合终端发起位置更新的条件，该终端向接入及移动性管理功能发起位置更新请求，在该位置更新请求中携带有终端所在的位置信息。
步骤706：接入及移动性管理功能基于群组移动性接入控制策略，根据终端的位置信息判断是否对该终端进行接入限制，如终端移动了允许的位 置区域范围。
步骤707：群组终端向会话管理功能发起会话请求，在会话请求中携带有群组网络标识、群组业务标识；会话管理功能为该终端建立会话。
步骤708：会话管理功能向签约管理功能请求该群组的移动性会话业务控制参数。其中，移动性会话业务控制参数包括但不限于：按照业务连续性特性进行会话控制，即部分业务不需要业务连续性控制，根据群组业务标识进行判别。
步骤709：当终端发生位置更新时，向会话管理功能发起会话切换请求，会话切换请求中携带有终端的位置信息。
步骤710：会话管理功能实体基于移动性会话业务控制参数，对该终端进行会话切换管理，如果该业务没有业务连续性需求，那么，可以不执行业务连续性流程，直接为该终端在新的位置区域新建媒体面承载，重新进行相关会话业务并由第三方服务保证会话的连续性即可。
步骤711：当终端发生位置更新时，签约管理功能向会话管理功能更新移动性会话业务控制策略的同时，向策略管理功能推送该群组的移动性QoS策略控制参数。其中，移动性QoS策略控制参数包括但不限于：不同位置区域采用不同的PCC策略参数，如不同带宽，不同的计费参数等。
步骤712：策略管理功能更新该群组的PCC策略，并发送给会话管理功能执行。
步骤713：会话管理功能基于更新的PCC策略，对终端的会话业务进行QoS更新及计费策略更新。
图7所示的实施例主要说明了：第三方服务通过能力开放平台将根据业务需求定制的群组移动性业务策略参数下发给网络设备，网络设备则根据业务侧定制的群组移动性业务策略，执行在群组内终端位置更新时的接入控制、会话切换、QoS策略执行等，满足了业务对群组移动性的差异化 需求。
图8为本申请实施例能力开放平台的组成结构示意图，如图8所示，至少包括接收模块、处理模块；其中，
第一接收模块，配置为来自第三方服务的业务群组信息；
第一处理模块，配置为将来自第三方服务的业务群组信息传递给网络设备。
接收到来自第三方服务的业务群组创建请求时，第一处理模块，可配置为将来自第三方服务的业务群组信息映射为群组网络信息，将包括群组网络信息的能力开放平台侧组签约及管理信息发送给网络设备，以请求网络设备对该业务群组进行创建并按照群组网络信息中的群组网络策略进行管理。所述群组网络信息包括但不限于：群组网络标识、终端标识列表、群组网络策略等。
接收到来自第三方服务的业务群组更新请求时，第一处理模块，可配置为利用来自第三方服务的业务群组信息，更新自身保存的对应业务群组的能力开放平台侧的业务群组信息，并将更新后的业务群组信息映射为群组网络信息并发送给网络设备，以请求网络设备对该业务群组的群组网络信息进行更新并按照更新后的群组策略进行管理。
接收到来自第三方服务的业务群组删除请求时，第一处理模块可配置为删除自身保存的对应业务群组的能力开放平台侧的组签约及管理信息，并通知网络设备删除该业务群组的群组网络信息。
图9为本申请实施例签约管理功能实体的组成结构示意图，如图9所示，至少包括获取模块、第二处理模块；其中，
获取模块，可配置为根据第三方服务通过能力开放平台传递的业务群组信息，获取业务群组的组签约及管理信息；
第二处理模块，可配置为根据来自能力开放平台的组签约及管理信息， 生成网络设备的组签约及管理信息。
网络设备的组签约及管理信息包括但不限于：群组网络标识、群组网络策略、终端网络标识列表，终端签约信息等。其中群组网络策略包括不限于：组计费参数、组QoS参数、组内终端接入控制参数、会话控制参数等。
可选地，第二处理模块，还可配置为根据来自能力开放平台的组签约及管理信息，更新网络设备相关的组签约及管理信息。
可选地，
第二处理模块，还可配置为接收来自能力开放平台的删除业务群组的群组网络信息的通知，删除该业务群组的网络设备相关的组签约及管理信息。
可选地，本申请实施例签约管理功能实体还包括：
下发模块，可配置为将网络设备的组签约及管理信息下载到不同的网络功能实体，比如：接入及移动性管理功能实体、会话管理功能实体、策略管理功能实体。
可选地，获取模块，还可配置为通过能力开放平台获取第三方服务基于组业务特性定制的业务群组的移动性行为的移动性业务定制参数。下发模块，还可配置为将移动性定制参数下发到接入及移动性管理功能实体、会话管理功能实体。
图10为本申请实施例接入及移动性管理功能实体的组成结构示意图，如图10所示，至少包括第二接收模块、第三处理模块；其中，
第二接收模块，可配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第三处理模块，可配置为根据接收到的网络设备的组签约及管理信息，生成组控制面上下文；根据组内终端接入控制参数对终端进行接入控制。
可选地，第二接收模块，还可配置为接收来自签约管理功能实体的移动性业务定制参数；
第三处理模块，还可配置为根据接收到的移动性业务定制参数，按照群组定制的移动性业务方式，对移动的终端移动进行接入控制。
图11为本申请实施例会话管理功能实体的组成结构示意图，如图11所示，至少包括第三接收模块、第四处理模块；其中，
第三接收模块，可配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第四处理模块，可配置为根据接收到的网络设备的组签约及管理信息，生成组用户面上下文；根据组内终端会话管理策略对终端进行会话控制。
可选地，第三接收模块，还可配置为接收来自签约管理功能实体的移动性业务定制参数；
第四处理模块，还可配置为根据接收到的移动性业务定制参数，按照群组定制的移动性业务方式，对移动的终端移动进行会话连续性控制。
可选地，第三接收模块，还可配置为接收来自策略管理功能实体的QoS管理及组计费信息；
第四处理模块，还可配置为根据接收到的QoS管理及组计费信息，对该群组的会话业务进行QoS管理及组计费。
图12为本申请实施例策略管理功能实体的组成结构示意图，如图12所示，至少包括第四接收模块、第五处理模块；其中，
第四接收模块，可配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
第五处理模块，可配置为根据接收到的网络设备的组签约及管理信息中的群组网络策略，生成QoS管理及组计费信息如组QoS参数、计费参数等，并下发给会话管理功能，以对该群组的会话业务进行QoS管理及组计 费。
图13为本本申请实施例提供一种网元实体，可以包括处理器21、存储有处理器21可执行指令的存储器22、通信接口23，和用于连接处理器21、存储器22以及通信接口23的总线24。
在本申请实施例的实施例中，网元实体2可为前述的任意一个网元实体，例如，签约管理功能实体、接入及移动性管理功能实体、会话管理功能实体、策略管理功能实体或能力开放平台。
上述处理器21可以为特定用途集成电路(ASIC，Application Specific Integrated Circuit)、数字信号处理器(DSP，Digital Signal Processor)、数字信号处理装置(DSPD，Digital Signal Processing Device)、可编程逻辑装置(PLD，Programmable Logic Device)、现场可编程门阵列(FPGA，Field Programmable Gate Array)、CPU、控制器、微控制器、微处理器中的至少一种。可以理解地，对于不同的设备，用于实现上述处理器功能的电子器件还可以为其它。
本申请实施例不作具体限定。该网元实体2还可以包括存储器22，该存储器22可以与处理器21连接，其中，存储器22用于存储可执行程序代码，该程序代码包括计算机操作指令，存储器22可能包含高速RAM存储器，也可能还包括非易失性存储器，例如，至少一个磁盘存储器。
在本申请实施例的实施例中，总线24用于连接通信接口23、处理器21和存储器22以及这些器件之间的相互通信。
本实施例提供的所述网元实体，所述处理器21通过计算机程序等计算机可执行程序的执行，可以实现前述一个或多个技术方案中提供的能力开放实现方法，例如，可实现图2至图7任一图示的方法。
本申请实施例提供一种计算机存储介质，所述计算机存储介质存储有可执行指令；所述可执行指令可为计算机程序或软件应用等；所述计算机 程序被执行后能够实现前述一个或多个技术方案中提供的能力开放实现方法，例如，可实现图2至图7任一图示的方法。
所述计算机存储介质可为：易失性第一存储器(volatile memory)，例如随机存取第一存储器(RAM，Random-Access Memory)；或者非易失性第一存储器(non-volatile memory)，例如只读第一存储器(ROM，Read-Only Memory)，快闪第一存储器(flash memory)，硬盘(HDD，Hard Disk Drive)或固态硬盘(SSD，Solid-State Drive)；或者上述种类的第一存储器的组合。可选为非瞬间存储介质。
虽然本申请实施例所揭示的实施方式如上，但其内容只是为了便于理解本申请实施例的技术方案而采用的实施方式，并非用于限定本申请实施例。任何本申请实施例所属技术领域内的技术人员，在不脱离本申请实施例所揭示的核心技术方案的前提下，可以在实施的形式和细节上做任何修改与变化，但本申请实施例所限定的保护范围，仍须以所附的权利要求书限定的范围为准以上所述，仅为本申请实施例的较佳实例而已，并非用于限定本申请实施例的保护范围。凡在本申请实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请实施例的保护范围之内。
工业实用性
本申请实施例提供的技术方案中，网络设备通过获取第三方服务通过能力开放平台传递的业务群组信息，在需要进行组管理时，网络设备实现了按照业务群组对应的群组网络策略对组内终端进行管理，实现了基于组管理的能力开放，满足了第三方服务基于群组业务的差异化业务实现，提升了群组用户的业务体验，从而具有积极的工业效果，且具有实现简便的特点，在工业上可实现性强。

Claims (33)

  1. 一种能力开放实现方法，包括：
    网络设备获取第三方服务通过能力开放平台传递的业务群组信息；
    网络设备按照业务群组对应的群组网络策略对组内终端进行组管理。
  2. 根据权利要求1所述的能力开放实现方法，其中，所所述获取第三方服务通过能力开放平台传递的业务群组信息包括：
    所述网络设备接收来自所述能力开放平台的组签约及管理信息；所述组签约及管理信息包含：所述能力开放平台将来自所述第三方服务的业务群组信息映射成的群组网络信息以及群组鉴权信息；其中，所述组签约及管理信息，是所述能力开放平台接收到来自第三方服务的业务群组创建请求时发送的；
    所述网络设备根据来自能力开放平台的组签约及管理信息，生成网络设备的组签约及管理信息。
  3. 根据权利要求2所述的能力开放实现方法，其中，所述群组网络策略包括：组计费参数、组服务质量QoS参数、组内终端接入控制参数及会话控制参数的至少其中之一。
  4. 根据权利要求2所述的能力开放实现方法，其中，所述群组网络信息包括：群组网络标识、终端标识列表及群组网络策略的至少其中之一；
    所述网络设备的组签约及管理信息包括：群组网络标识、群组网络策略、终端网络标识列表及终端签约信息的至少其中之一。
  5. 根据权利要求1所述的能力开放实现方法，其中，所述获取第三方服务通过能力开放平台传递的业务群组信息包括：
    接收所述能力开放平台发送的将更新后的业务群组信息映射为群组网络信息，并发送给网络设备；所述更新后的业务群组信息，为所述能力开放平台接收到来自第三方服务的业务群组更新请求时更新的；
    所述网络设备根据来自能力开放平台的组签约及管理信息，更新网络设备相关的组签约及管理信息。
  6. 根据权利要求1所述的能力开放实现方法，其中，所述获取第三方服务通过能力开放平台传递的业务群组信息包括：
    接收所述能力开放平台删除业务群组的群组网络信息的通知，其中，所述通知为：所述能力开放平台接收到来自第三方服务的业务群组删除请求时发送的；
    所述网络设备删除该业务群组的网络设备相关的组签约及管理信息。
  7. 根据权利要求1所述的能力开放实现方法，其中，所述网络设备按照业务群组对应的群组网络策略对组内终端进行管理包括：
    当群组内终端接入到网络，所述网络设备根据接入的终端携带的组网络标识判断出终端是按照群组的方式进行接入控制及会话控制，所述网络设备按照自身已创建的组签约及管理信息进行群组管理。
  8. 根据权利要求2所述的能力开放实现方法，其中，还包括：
    所述网络设备的签约管理功能将网络设备的组签约及管理信息下载到所述网络设备的不同的网络功能实体。
  9. 根据权利要求8所述的能力开放实现方法，其中，还包括：
    所述网络设备的接入及移动性管理功能实体根据网络设备的组签约及管理信息，生成组控制面上下文，并根据组内终端接入控制参数对终端进行接入控制。
  10. 根据权利要求9所述的能力开放实现方法，其中，所述组控制面上下文包括：驻留在该接入及移动性管理功能实体的终端接入上下文信息及组网络标识参数的至少其中之一。
  11. 根据权利要求8所述的能力开放实现方法，其中，还包括：
    所述网络设备的会话管理功能实体根据网络设备的组签约及管理信 息，生成组用户面上下文，并根据组内终端会话管理策略对该终端进行会话控制。
  12. 根据权利要求11所述的能力开放实现方法，其中，所述组用户面上下文包括：终端会话上下文信息及组网络标识的至少其中之一。
  13. 根据权利要求8所述的能力开放实现方法，其中，还包括：
    所述网络设备的策略管理功能实体根据网络设备的组签约及管理信息中的群组网络策略，生成组QoS参数及计费参数的至少其中之一，并下发给会话管理功能，以对该群组的会话业务进行QoS管理及组计费。
  14. 根据权利要求1或8所述的能力开放实现方法，其中，该方法还包括：
    接收所述能力开放平台发送的第三方服务定制的群组通信定制参数；其中，所述群组通信定制参数，包括：所述第三方服务根据群组通信需求，对业务群组定制单播或多播方式；
    根据包括上限是单播阈值，下限是多播阈值的单播/多播切换阈值区间，在群组中的终端在某一位置区域的单播数量超过单播阈值时，请求建立多播承载，并发起单播向多播的会话切换；
    在群组中的终端在某一位置区域的多播数量低于多播阈值时，请求建立单播承载，并发起多播向单播的会话切换。
  15. 根据权利要求14所述的能力开放实现方法，其中，所述群组通信定制参数包括：位置区域信息、位置区域对应的单播/多播切换阈值区间及群组标识的至少其中之一。
  16. 根据权利要求1或8所述的能力开放实现方法，其中，该方法还包括：
    接收所述能力开放平台发送的将移动性业务定制参数，其中，所述定制参数是所述第三方服务基于组业务特性定制业务群组的移动性行为制定 的；
    所述网络设备的签约管理功能将移动性定制参数下发的网络设备的各个网元，实现按照群组定制的移动性业务方式，对移动的终端移动进行接入控制及会话连续性控制。
  17. 一种能力开放实现装置，包括第一接收模块、第一处理模块；其中，
    第一接收模块，配置为来自第三方服务的业务群组信息；
    第一处理模块，配置为将来自第三方服务的业务群组信息传递给网络设备。
  18. 根据权利要求17所述的能力开放实现装置，其中，所述第一处理模块，配置为将来自第三方服务的业务群组信息映射为群组网络信息，将包括群组网络信息的能力开放平台侧组签约及管理信息以及群组鉴权信息发送给网络设备，以请求网络设备对该业务群组进行创建并按照群组网络信息中的群组网络策略进行管理。
  19. 根据权利要求17所述的能力开放实现装置，其中，所述第一处理模块，配置为接收到来自所述第三方服务的业务群组更新请求，利用来自第三方服务的业务群组信息，更新自身保存的对应业务群组的能力开放平台侧的业务群组信息，并将更新后的业务群组信息映射为群组网络信息，并发送给网络设备，以请求网络设备对该业务群组的群组网络信息进行更新并按照更新后的群组策略进行管理。
  20. 根据权利要求17所述的能力开放实现装置，其中，所述第一处理模块，配置为接收到来自所述第三方服务的业务群组删除请求，删除自身保存的对应业务群组的能力开放平台侧的组签约及管理信息，并通知网络设备删除该业务群组的群组网络信息。
  21. 一种签约管理功能实体，包括获取模块、第二处理模块；其中，
    获取模块，配置为根据第三方服务通过能力开放平台传递的业务群组信息，获取业务群组的组签约及管理信息；
    第二处理模块，配置为根据来自能力开放平台的组签约及管理信息，生成网络设备的组签约及管理信息。
  22. 根据权利要求21所述的签约管理功能实体，其中，所述第二处理模块，还配置为根据来自所述能力开放平台的组签约及管理信息，更新网络设备相关的组签约及管理信息。
  23. 根据权利要求21所述的签约管理功能实体，其中，
    所述第二处理模块，还配置为接收来自所述能力开放平台的删除业务群组的群组网络信息的通知，删除该业务群组的网络设备相关的组签约及管理信息。
  24. 根据权利要求21至23任一项所述的签约管理功能实体，其中，还包括：
    下发模块，配置为将所述网络设备的组签约及管理信息下载到接入及移动性管理功能实体、会话管理功能实体、策略管理功能实体。
  25. 根据权利要求24所述的签约管理功能实体，其中，
    所述获取模块，还配置为通过所述能力开放平台获取第三方服务基于组业务特性定制的业务群组的移动性行为的移动性业务定制参数；相应地，
    所述下发模块，还配置为将移动性定制参数下发到接入及移动性管理功能实体、会话管理功能实体。
  26. 一种接入及移动性管理功能实体，包括第二接收模块、第三处理模块；其中，
    所述第二接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
    所述第三处理模块，配置为根据接收到的网络设备的组签约及管理信 息，生成组控制面上下文；根据组内终端接入控制参数对终端进行接入控制。
  27. 根据权利要求26所述的接入及移动性管理功能实体，其中，
    所述第二接收模块，还配置为接收来自所述签约管理功能实体的移动性业务定制参数；
    所述第三处理模块，还配置为根据接收到的移动性业务定制参数，按照群组定制的移动性业务方式，对移动的终端移动进行接入控制。
  28. 一种会话管理功能实体，包括第三接收模块、第四处理模块；其中；
    所述第三接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
    所述第四处理模块，配置为根据接收到的网络设备的组签约及管理信息，生成组用户面上下文；根据组内终端会话管理策略对终端进行会话控制。
  29. 根据权利要求28所述的会话管理功能实体，其中，
    所述第三接收模块，还配置为接收来自所述签约管理功能实体的移动性业务定制参数；
    所述第四处理模块，还配置为根据接收到的移动性业务定制参数，按照群组定制的移动性业务方式，对移动的终端移动进行会话连续性控制。
  30. 根据权利要求28所述的会话管理功能实体，其中，
    所述第三接收模块，还配置为接收来自策略管理功能实体的QoS管理及组计费信息；
    所述第四处理模块，还配置为根据接收到的QoS管理及组计费信息，对该群组的会话业务进行QoS管理及组计费。
  31. 一种策略管理功能实体，包括：第四接收模块、第五处理模块； 其中，
    所述第四接收模块，配置为接收来自签约管理功能实体的网络设备的组签约及管理信息；
    所述第五处理模块，配置为根据接收到的网络设备的组签约及管理信息中的群组网络策略，生成QoS管理及组计费信息并下发给会话管理功能。
  32. 一种网元实体，包括：处理器、存储有所述处理器可执行指令的存储器、通信接口，和用于连接所述处理器、所述存储器以及所述通信接口的总线，当所述指令被所述处理器执行时。能够实现如权利要求1至16任一项提供的方法。
  33. 一种计算机可读存储介质，其上存储有程序，应用于终端中，其中，所述程序被处理器执行时实现如权利要求1至16提供的方法。
PCT/CN2017/102447 2016-10-27 2017-09-20 能力开放实现方法及装置、网元实体及存储介质 WO2018076966A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610958518.5A CN107995603A (zh) 2016-10-27 2016-10-27 一种能力开放实现方法及装置
CN201610958518.5 2016-10-27

Publications (1)

Publication Number Publication Date
WO2018076966A1 true WO2018076966A1 (zh) 2018-05-03

Family

ID=62023071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/102447 WO2018076966A1 (zh) 2016-10-27 2017-09-20 能力开放实现方法及装置、网元实体及存储介质

Country Status (2)

Country Link
CN (1) CN107995603A (zh)
WO (1) WO2018076966A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021088660A1 (zh) * 2019-11-07 2021-05-14 华为技术有限公司 通信方法、装置及设备
CN113541981A (zh) * 2020-04-14 2021-10-22 中国移动通信集团浙江有限公司 网络切片的成员管理方法及系统
CN113747436A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 通信系统、服务器、通信方法和装置
CN115174650A (zh) * 2022-09-06 2022-10-11 深圳领筑科技有限公司 开放服务平台、服务响应方法、装置、设备和存储介质
EP4274340A4 (en) * 2021-01-08 2024-01-24 Guangdong Oppo Mobile Telecommunications Corp Ltd WIRELESS COMMUNICATION METHOD, NETWORK ELEMENT AND DEVICE

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113938845B (zh) * 2018-05-21 2023-07-18 华为技术有限公司 上下文管理方法及装置
CN113382370A (zh) * 2018-10-08 2021-09-10 华为技术有限公司 一种通信方法及装置
CN111372103B (zh) * 2018-12-26 2023-05-26 中兴通讯股份有限公司 一种组播方法、装置、设备和计算机存储介质
CN113475039B (zh) * 2019-01-30 2023-02-03 华为技术有限公司 基于开放信息的网络和/或管理功能适配的装置和方法
CN111800734A (zh) * 2019-08-14 2020-10-20 维沃移动通信有限公司 数据传输方法、装置、设备及介质
CN110621032B (zh) * 2019-09-27 2021-06-15 腾讯科技（深圳）有限公司 一种通信的方法、相关装置及设备
CN110809244B (zh) * 2019-11-07 2023-04-18 腾讯科技（深圳）有限公司 一种数据传输方法及相关设备
EP4044614A4 (en) * 2019-11-08 2022-10-19 Huawei Technologies Co., Ltd. METHOD FOR ESTABLISHING A MULTICAST SESSION AND NETWORK DEVICE
WO2023102754A1 (zh) * 2021-12-07 2023-06-15 Oppo广东移动通信有限公司 一种通信方法及装置、通信设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102624926A (zh) * 2012-04-11 2012-08-01 中兴通讯股份有限公司 能力聚合开放的方法和系统
US20150264512A1 (en) * 2014-03-14 2015-09-17 Puneet K. Jain Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system
CN105491557A (zh) * 2014-09-15 2016-04-13 中兴通讯股份有限公司 一种实现能力开放的系统、方法及能力开放平台

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8976722B2 (en) * 2008-12-18 2015-03-10 Qualcomm Incorporated Managing transmission protocols for group communications within a wireless communications network
CN105471611A (zh) * 2014-09-05 2016-04-06 中兴通讯股份有限公司 用户服务提供的处理方法、装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102624926A (zh) * 2012-04-11 2012-08-01 中兴通讯股份有限公司 能力聚合开放的方法和系统
US20150264512A1 (en) * 2014-03-14 2015-09-17 Puneet K. Jain Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system
CN105491557A (zh) * 2014-09-15 2016-04-13 中兴通讯股份有限公司 一种实现能力开放的系统、方法及能力开放平台

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021088660A1 (zh) * 2019-11-07 2021-05-14 华为技术有限公司 通信方法、装置及设备
CN113541981A (zh) * 2020-04-14 2021-10-22 中国移动通信集团浙江有限公司 网络切片的成员管理方法及系统
CN113747436A (zh) * 2020-05-14 2021-12-03 华为技术有限公司 通信系统、服务器、通信方法和装置
EP4274340A4 (en) * 2021-01-08 2024-01-24 Guangdong Oppo Mobile Telecommunications Corp Ltd WIRELESS COMMUNICATION METHOD, NETWORK ELEMENT AND DEVICE
CN115174650A (zh) * 2022-09-06 2022-10-11 深圳领筑科技有限公司 开放服务平台、服务响应方法、装置、设备和存储介质

Also Published As

Publication number Publication date
CN107995603A (zh) 2018-05-04

Similar Documents

Publication Publication Date Title
WO2018076966A1 (zh) 能力开放实现方法及装置、网元实体及存储介质
CN106657194B (zh) 一种网络切片能力开放的方法、装置及系统
US11533401B2 (en) Charging policy information for a packet data unit session in a wireless network
CN114008980B (zh) 用于非公共网络的收费控制方法和系统
WO2018145669A1 (zh) 一种业务分流实现方法及装置
WO2016041344A1 (zh) 一种实现能力开放的系统、方法及能力开放平台
WO2021232897A1 (zh) 中继链接建立、配置信息发送方法、装置和可读存储介质
CN104186023A (zh) 为启用本地内容共享而进行的本地因特网协议接入(lipa)扩展
WO2018059150A1 (zh) 一种能力开放实现方法和装置
KR20120076444A (ko) ＥＭＢＭＳ 채팅 서비스 제공 시스템 및 ＥＭＢＭＳ 채팅 서비스 제공 시스템의 서비스 제공자 서버, ｅＢＭ－ＳＣ 및 사용자 단말의 제어 방법
KR20210055546A (ko) 무선 통신 시스템에서 mbs 서비스 제공에 대한 mbs 서비스 세션의 설정을 위한 장치 및 방법
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
CN101483920B (zh) 资源接纳控制方法、网络装置及网络系统
CN103200534B (zh) 一种集群通信的方法、装置及系统
US11057745B2 (en) Data transmission method and related apparatus
WO2010006493A1 (zh) 动态业务流的处理方法及系统
WO2022127473A1 (zh) 网络切片的选择方法、装置、设备及存储介质
WO2022037341A1 (zh) 通信控制方法、网元及存储介质
CN115734170A (zh) 一种组播/广播会话管理方法及通信装置
US9674844B2 (en) Device and method for distributing WLAN user policy
CN110166503B (zh) 信息交互方法、设备及计算机可读存储介质
CN101720113B (zh) 一种资源控制的方法及系统
KR20210051375A (ko) 가상 id를 이용하여 복수의 pdu 세션들을 처리하는 방법 및 상기 방법을 수행하는 smf
CN112671571B (zh) 网络切片的选择方法、装置、设备及存储介质
WO2022166559A1 (zh) 通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17863465

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17863465

Country of ref document: EP

Kind code of ref document: A1