CN116208964A

CN116208964A - Service transmission and control method and device thereof

Info

Publication number: CN116208964A
Application number: CN202111441015.8A
Authority: CN
Inventors: 曾庆军; 宋起柱; 李爽; 孙苏川; 邸斌; 董浩霖; 焦清文; 张莹莹
Original assignee: China Radio And Television Network Group Co ltd
Current assignee: China Radio And Television Network Group Co ltd
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2023-06-02

Abstract

The application discloses a service transmission and a control method and equipment thereof, which are used for saving resources required to be occupied by broadcast and/or multicast services and avoiding resource waste. The service transmission control method provided by the application comprises the following steps: determining parameters for controlling transmission of broadcast and/or multicast traffic, said parameters comprising service time and/or service area of said traffic; and transmitting the parameters to an access network through at least one network function entity of a core network, so that the access network transmits the service to a terminal according to the parameters.

Description

Service transmission and control method and device thereof

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a service transmission and a control method and apparatus thereof.

Background

The following description of the background art may include an insight, discovery, understanding, or disclosure, or association, of at least some examples of embodiments of the present application, and disclosures not known to the relevant prior art but provided by the present application. Some such contributions of the application may be specifically pointed out below, while other such contributions of the application will be apparent from the relevant context.

The 5G mobile communication system will support multicast broadcast services (Multicast Broadcast Service, MBS) to support transmission of service data such as multicast, broadcast, interactive internet television (IPTV) of internet protocol version 4 (Internet Protocol version, ipv 4) and internet protocol version 6 (Internet Protocol version, ipv 6), or optimize transmission efficiency and network resource usage efficiency of existing other services, for example: group communication, internet of things communication (IoT), internet of things communication (V2X), software download or update, and the like.

The current broadcast area and broadcast time are statically configured by an operator, and in the broadcast area and broadcast time, no matter whether User Equipment (UE) is receiving broadcast, the network side needs to transmit a broadcast signal, which causes resource waste.

Disclosure of Invention

The embodiment of the application provides a service transmission and control method and equipment thereof, which are used for saving resources required to be occupied by broadcast and/or multicast services and avoiding resource waste.

On the core side, for example, on any network function NF entity side of the core side, the service transmission control method provided in the embodiment of the present application includes:

determining parameters for controlling transmission of broadcast and/or multicast traffic, said parameters comprising service time and/or service area of said traffic;

And transmitting the parameters to an access network through at least one network function entity of a core network, so that the access network transmits the service to a terminal according to the parameters.

The method comprises determining parameters for controlling the transmission of broadcast and/or multicast services, said parameters comprising the service time and/or service area of said services; and the parameters are sent to the access network through at least one network function entity of the core network, so that the access network sends the service to the terminal according to the parameters, thereby realizing the transmission of broadcast and/or multicast service in the appointed service time and/or service area, avoiding the transmission of broadcast and/or multicast service at any place at any moment, therefore, the method can save resources required to be occupied by the broadcast and/or multicast service and avoid the waste of resources.

Optionally, the method further comprises:

transmitting a request message for requesting information about the number of terminals receiving the broadcast and/or multicast service to a network data analysis function NWDAF entity;

and receiving a request result sent by the NWDAF entity, wherein the parameters are determined according to the request result.

That is, the method can realize the transmission control of the service according to the actual number of users receiving the broadcast and/or multicast service, so that the actual situation can be combined, and the resources can be saved as much as possible on the premise of meeting the user demand.

Optionally, the method further comprises:

and receiving parameters which are transmitted by another network function entity and are used for controlling broadcast and/or multicast service transmission and are different from the network function entity at the home terminal, wherein the parameters determined by the home terminal are determined according to the parameters transmitted by the other network function entity.

At the core network side, for example, at the NWDAF entity side, a service transmission control method provided in the embodiments of the present application includes:

receiving a request message sent by a first network function entity of a core network, wherein the request message is used for requesting information about the number of terminals receiving broadcast and/or multicast service;

and determining a request result according to the request message, and sending the request result to the first network function entity, so that the first network function entity determines parameters for controlling the service transmission according to the request result, wherein the parameters comprise service time and/or service area of the service.

Optionally, determining a request result according to the request message specifically includes:

and collecting data from a second network function entity of the core network, and determining the request result by utilizing the collected data and/or data locally stored by a network data analysis function NWDAF entity.

Optionally, the request result specifically includes:

and receiving statistical results and/or prediction results of the number of terminals of the broadcast and/or multicast service in a designated area and/or time period.

On the access network side, the service transmission method provided by the embodiment of the application includes:

receiving parameters which are sent by a core network and used for controlling the transmission of broadcast and/or multicast services, wherein the parameters comprise service time and/or service area of the services;

and sending the service to the terminal according to the parameters.

Another embodiment of the present application provides a computing device including a memory for storing program instructions and a processor for invoking the program instructions stored in the memory to perform any of the methods described above in accordance with the obtained program.

The computing device may be, for example, a device on the core network side or a device on the access network side, and the device on the core network side may be any network functional entity or NWDAF entity.

Furthermore, according to an embodiment, for example, a computer program product for a computer is provided, comprising software code portions for performing the steps of the method defined above, when said product is run on a computer. The computer program product may include a computer-readable medium having software code portions stored thereon. Furthermore, the computer program product may be directly loaded into the internal memory of the computer and/or transmitted via the network by at least one of an upload procedure, a download procedure and a push procedure.

Another embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform any of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is an overall flow schematic diagram of a service control method provided in an embodiment of the present application;

fig. 2 is a specific flow diagram of a service control method provided in an embodiment of the present application;

fig. 3 is a flow chart of a service transmission control method of any NF entity side of the core side provided in the embodiment of the present application;

fig. 4 is a flow chart of a service transmission control method at the NWDAF entity side provided in the embodiment of the present application;

fig. 5 is a flow chart of a service transmission method at the access network side provided in the embodiment of the present application;

FIG. 6 is a schematic diagram of a computing device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a service transmission control device on the core side according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another service transmission control device on the core side according to the embodiment of the present application;

fig. 9 is a schematic structural diagram of a service transmission device according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The method and the device are based on the same application, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.

The terms first, second and the like in the description and in the claims of the embodiments and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The following examples and embodiments are to be construed as illustrative only. Although the specification may refer to "an", "one", or "some" example or embodiment(s) at several points, this does not mean that each such reference is related to the same example or embodiment, nor that the feature is applicable to only a single example or embodiment. Individual features of different embodiments may also be combined to provide further embodiments. Furthermore, terms such as "comprising" and "including" should be understood not to limit the described embodiments to consist of only those features already mentioned; such examples and embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned.

The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G system. For example, suitable systems may be global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE), LTE frequency division duplex (Frequency Division Duplex, FDD), LTE time division duplex (Time Division Duplex, TDD), universal mobile system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide interoperability for Microwave Access, wiMAX), 5G NR, and the like. Terminal devices and network devices are included in these various systems.

The terminal device according to the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with wireless connection functionality, or other processing device connected to a wireless modem. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more core networks via the RAN, and may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in, or vehicle-mounted mobile devices that exchange voice and/or data with the radio access network. Such as personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDAs), and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (access terminal), user terminal device (user terminal), user agent (user agent), user device (user device), and the embodiments of the present application are not limited.

The network device according to the embodiment of the application includes a core network device and may also include an access network device. The access network device may be a base station, which may comprise a plurality of cells. A base station may also be referred to as an access point, or may refer to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be operable to inter-convert the received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (GSM) or Code Division Multiple Access (CDMA), a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station in a 5G network architecture (next generation system), or a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), etc., which are not limited in the embodiments of the present application.

Various embodiments of the present application are described in detail below with reference to the drawings attached hereto. It should be noted that, the display sequence of the embodiments of the present application only represents the sequence of the embodiments, and does not represent the advantages or disadvantages of the technical solutions provided by the embodiments.

Referring to fig. 1, the broadcast control method provided in the embodiment of the present application includes the following steps:

step 1, a Network Function (NF) entity of a Core Network (CN) sends a request message to a Network data analysis Function (Network Data Analytic Function, NWDAF) entity for requesting (or may also be referred to as subscribing to) information about the number of terminals receiving broadcast and/or multicast services, which information includes, for example: statistics and/or predictions of the number of UEs receiving broadcast and/or multicast traffic over a specified area and/or time period.

Specifically, the Request message may be, for example, an NWDAF analysis subscription (nwdaf_analysis subscription_subscriber) service Request, or an NWDAF analysis information Request (nwdaf_analysis info_request).

The NF entity, for example, comprises one or a combination of the following functional entities:

a session management function (Session Management Function, SMF) entity;

A multicast broadcast session management function (Multicast Broadcast Session Management Function, MB-SMF) entity;

a policy control function (Policy Control Function, PCF) entity;

an application function (Application Function, AF) entity.

Optionally, when the NF entity is an AF entity, the AF entity may send the request message through a network capability open function (Network Exposure Function, NEF) in addition to directly initiating the request message to the NWDAF entity.

For example, referring to fig. 2, the step 1 specifically includes:

step 1a-1, the AF entity initiates an analysis result subscription (Nnef_Analytics Exposure_Subservice) service request or an analysis result acquisition (Nnef_Analytics Exposure_fetch) service request to the NEF entity.

Step 1a-2, the NEF entity initiates an nwdaf_analytic description_subscnribe service Request, or an nwdaf_analytic info_request to the NWDAF entity according to the nnef_analytic Exponsure_subsribe service Request, or the nnef_analytic Exponsure_fetch service Request received in step 1 a-1.

Alternatively, the step 1 specifically includes:

step 1b, the AF entity directly sends an Nnwdaf_Analytics subscriber_Subscribe service Request or an Nnwdaf_Analytics Info_Request to the NWDAF entity;

Or when the NF entity is the PCF entity, the step 1 specifically includes:

step 1c, the PCF entity sends an nnwdaf_analytics description_subscience service Request, or an nnwdaf_analytics info_request to the NWDAF entity;

or, when the NF entity is an MB-SMF entity or an SMF entity, the step 1 specifically includes:

step 1d, MB-SMF entity or SMF entity sends to NWDAF entity a nwdaf_analytics description_subscnribe service Request, or a nwdaf_analytics info Request.

Optionally, the request message may carry one or a combination of the following information:

a) Analysis identity (analysis id) =mbs service experience (MBS Service Experience);

the analysis id is used to indicate that the analysis type of the request message request is about MBS service experience;

b) An analysis report objective (Target of Analytics Reporting);

for example, target of Analytics Reporting may be set to a temporary mobile group identity (Temporary Mobile Group Identifier, TMGI) indicating that the request message is to count UEs receiving MBS services of the TMGI identity; wherein, the TMGI contains MBS service identification;

c) Analyzing the filtered information (Analytics filter information);

The Analytics filter information may, for example, comprise: a region of Interest (Area of Interest), and/or a transmission mode (delivery mode);

wherein the region of interest indicates that the request message is to make statistics and/or analysis on UE and/or service of the region;

for example, an Area of interest=mbs service Area (MBS service Area) may be set

The MBS service areas, e.g. one or more tracking areas TA or Cell cells;

the MBS service region corresponds to a specific MBS service (e.g., denoted by TMGI) so as to perform statistics and/or analysis on a situation (e.g., service experience) of the specific MBS service under the MBS service region.

The transmission mode (delivery mode), for example, a multicast (multicast) or broadcast (broadcast) transmission mode, is used to indicate that the request message is to be counted and/or analyzed for multicast or broadcast services.

d) Other information, such as core network element loading level information indication for scheduling MBS services.

And 2, the NWDAF entity collects data from the NF entity of the CN and determines a request result corresponding to the request message in the step 1 by utilizing the collected data and/or the locally stored data.

The locally stored data is, for example, data collected in advance or set locally.

The collected data may include, for example, network data and/or traffic data.

The network data comprises, for example, the number of the UE, the number of the users of the network, the traffic bandwidth, the UE position information, the network element load and performance and the like which receive broadcast in a designated area and/or a time period;

the service data includes, for example, a user subscription number, a service concurrency amount, etc. for receiving the broadcast service in a designated area and/or a time period.

Determining the request result using the collected data and/or the locally stored data, for example, specifically includes:

and (2) analyzing the acquired data and/or the locally stored data based on a specific algorithm, for example, based on a preset big data analysis algorithm such as deep learning, so as to obtain a request result corresponding to the request message in the step (1). The specific algorithm is not limited in this embodiment, and may be determined according to actual needs.

In this step, the NWDAF entity collects data, which specifically includes:

the NWDAF entity initiates a Nnf _eventExponsure_subscore service request to the NF entity of the CN, or sends a subscription (subscore) request to the OAM entity for requesting acquisition of network data and/or service data.

The NF entity of the CN in this step includes, for example: an access and mobility management function (Access and Mobility Management Function, AMF) entity, an SMF entity, an MB-SMF entity, a network storage function (Network Repository Function, NRF), an AF entity, an operation administration maintenance (Operation Administration and Maintenance, OAM) entity, etc.

Referring to fig. 2, the NWDAF entity collects data in this step, including, for example:

step 2a, NWDAF entity sends an acquisition data request (nsmf_eventExposure_subscore) to SMF entity or MB-SMF entity.

Alternatively, the NWDAF entity collects data in this step, including, for example:

step 2b, the NWDAF entity sends a subscription (Subscribe) request to the OAM entity.

step 2c, the NWDAF entity sends a data acquisition request (namf_eventExposure_subscore) to the AMF entity.

Or when the NF entity is the AF entity, the NWDAF entity collects data in this step, which includes:

step 2d-1, NWDAF entity sends a collect data request (nnef_eventExposure_subscore) to NEF entity.

Step 2d-2, the NEF entity sends a collect data request (naf_eventExposure_subscnibe) to the AF entity.

step 2e, the NWDAF entity directly sends a data acquisition request (naf_eventExposure_subscore) to the AF entity.

That is, when the NF entity is the AF entity, except that the NWDAF entity directly initiates a naf_eventExposure_subscore request to the AF entity, the acquisition of service data is requested; the NWDAF entity may also request acquisition of service data from the AF through the NEF entity.

The NWDAF entity requests collected data according to the analysis type, for example, may include: one or a combination of the following information related to MBS service of UE of a designated area:

a) UE location information;

b) Quality of service (QoS) information for broadcast or multicast data flows;

c) State information of the access network or core network functional entity.

Wherein the core network functional entity includes, for example, an MB-UPF (Multicast/broadcast/Broadcast User Plane Function) entity, i.e., a Multicast/broadcast service-specific user plane function;

the status information may include, for example, load and/or performance information.

The specified area includes, for example, a specified Tracking Area (TA), a tracking area list (TA list), or a Cell (Cell).

The MBS service of the UE may be identified, for example, by an Application identification (Application ID) or a TMGI.

It should be noted that, the NF entity involved in the data collection in step 2 (i.e. the NF entity that receives the data collection request and provides the data to the NWDAF entity) may be different from or the same as the NF entity that sends the request message in step 1.

And 3, the NWDAF entity sends corresponding request results (data statistics results and/or analysis results) to the corresponding NF entity according to the request message received in the step 1.

For example, the NWDAF entity sends the collected data and/or the data stored locally in the NWDAF entity to the NF entity sending the request message according to the information carried in the request message, and/or performs analysis and prediction by using the collected data and/or the data stored locally in the NWDAF entity to obtain a prediction result, and sends the prediction result to the NF entity sending the request message.

The NWDAF entity may send a data analysis result service message (nnwdaf_analysis subsystem_notify) to the NF entity, or send a response message to the nnwdaf_analysis info_request service Request, where the response message carries the network data analysis result corresponding to the subscribed or requested analysis type.

When the NF entity is the AF entity, the NWDAF entity may send the request result to the AF entity through the NEF entity in addition to the NWDAF entity directly initiating the service message (or sending the response message) to the AF entity. Referring to fig. 2, the nwdaf entity sends the request result to the corresponding NF entity, which specifically includes:

Step 3a-1, the NWDAF entity initiates an nnwdaf_analytics description_notify service message (or sends a response message to the nnwdaf_analytics info_request service Request) to the NEF entity, where the Request result is carried.

Step 3a-2, the NEF entity initiates an nnef_analytical exposure_notify service message (or sends a response to the nnef_analytical exposure_fetch service Request) to the AF entity according to the received nnwdaf_analytical subscription_notify service message (or a response to the nnwdaf_analytical info_request service Request), where the Request result is carried.

Or, the NWDAF entity sends the request result to the corresponding NF entity, which specifically includes:

step 3b, the NWDAF entity directly initiates an nnwdaf_analysis subdescription_notify service message (or sends a response message to the nnwdaf_analysis info_request service Request) to the AF entity, wherein the nwdaf_analysis subdescription_notify service message carries the Request result.

step 3c, the NWDAF entity sends an nnwdaf_analysis description_notify service message (or sends a response message to the nnwdaf_analysis info_request service Request) to the PCF entity, wherein the nwdaf_analysis description_notify service message carries the Request result.

step 3d, the NWDAF entity sends an nwdaf_analysis subdescription_notify service message (or sends a response message to the nwdaf_analysis info_request service Request) to the SMF entity or the MB-SMF entity, wherein the nwdaf_analysis subdescription_notify service message carries the Request result.

The request result may specifically include: and receiving statistical results and/or prediction results of the number of terminals of the broadcast and/or multicast service in a designated area and/or time period.

For example, the request result includes: in a specified area or location (e.g., a specified tracking area, tracking area list, or cell), one or a combination of the following information related to the MBS service of the UE:

a) UE location information;

b) Statistics and/or predictions about QoS for broadcast and/or multicast data flows;

c) Statistics and/or predictions about the status of the access network or core network functional entity; wherein the core network functional entity, such as an MB-UPF entity;

d) And a prediction result regarding the number of UEs.

The prediction result of the number of UEs may be, for example, a result of statistics of UE location information, a result of statistics of states of an access network or a core network functional entity, and a number of UEs receiving a broadcast service within a certain area and/or a certain time range.

In the subsequent step, the network side can find that only a few users are online in a certain time period and/or a certain region according to the counted number of users, and the network side can decide to stop sending the broadcast information in the time period and/or the region and send the service information to the UE in a unicast mode instead, so that the waste of broadcast network resources is avoided.

In addition, the updated MBS parameters in the subsequent steps do not include the area and/or time information changed into the unicast transmission mode, but define the designated MBS service area and/or service time, so that after the access network obtains the updated MBS parameters, broadcast and/or multicast service data can be sent to the terminal in the designated MBS service area and/or service time, instead of sending broadcast and/or multicast service data to the terminal at any time for all the areas, thereby realizing service transmission in combination with actual use situations and avoiding resource waste.

And 4, when the steps 3a-1 and 3a-2 are executed or the step 3b is executed, namely, the AF entity obtains the request result provided by the NWAF entity, the AF entity updates MBS parameters according to the request result provided by the NWAF entity, and sends the updated MBS parameters to a policy control function (Policy Control Function, PCF) entity.

Wherein, the updated MBS parameters include, for example: MBS service area (MBS service area), and/or MBS service time.

The service time includes, for example, a start time and an end time, or includes a start time and a duration.

Referring to fig. 2, the af entity sends the updated MBS parameters to the PCF entity, which specifically includes:

step 4a-1, the AF entity sends MBS parameter updating information (such as Nnef_ServiceParameter_update service request) to the NEF entity, wherein the MBS parameter updating information carries MBS service/session identification information, updated MBS parameters and the like;

step 4a-2, the NEF entity sends an MBS parameter Update message (e.g. npcf_policy_update service request) to the PCF entity, where the MBS parameter Update message carries MBS service/session identification information, updated MBS parameters, etc.

Or, the AF entity sends the updated MBS parameter to the PCF entity, which specifically comprises:

and 4b, the AF entity directly sends MBS parameter updating information (such as an Npcf_policy authorization_update service request) to the PCF entity, wherein the MBS parameter updating information carries MBS service/session identification information, updated MBS parameters and the like.

Wherein, the MBS service/session identification information includes, for example: one or more of TMGI, MBS service identification (MBS service identifier), MBS session identification (MBS session id), MBS flow description (MBS flow description), application identification (application identifier).

And 5, the PCF entity updates the MBS parameter according to the updated MBS parameter provided by the AF entity (if the step 4 is executed) and/or the request result provided by the NWDAF entity (if the step 3c is executed), and sends the updated MBS parameter to the MB-SMF entity or the SMF entity.

The updated MBS parameters may include, for example: MBS service area and/or MBS service time.

And 6, the MB-SMF entity or the SMF entity updates the MBS parameter according to the updated MBS parameter provided by the PCF entity and/or the request result provided by the NWDAF (if the step 3d is executed), and sends the updated MBS parameter to AN Access Network (AN).

Wherein, the updated MBS parameters may include: MBS service area (MBS service area), and/or service time.

The MB-SMF entity or SMF entity sends updated MBs parameters to AN, including, for example: the MB-SMF entity initiates a Namf_MBSComogic_N2MessageTransferservice request to the AMF entity, wherein the request carries an N2message, and the N2message carries updated MBS parameters. The AMF entity forwards the N2message to the AN. The N2message is a message requesting the AMF entity to deliver AN information response to the AN or UE.

Or the MB-SMF sends the updated MBS parameters to the SMF entity, and the SMF entity sends the updated MBS parameters to the AN. Specifically, the SMF entity may send the updated MBS parameters to the AN by carrying the updated MBS parameters in a Protocol Data Unit (PDU) session establishment/modification, MBS session establishment/modification, UE registration and/or service request, etc. procedure.

And 7, the AMF entity sends the N2 message to the AN, wherein the N2 message carries the updated MBS parameters.

Subsequently, the AN sends service data to the terminal according to the updated MBS parameters. For example, the base station transmits broadcast and/or multicast service data to the UE in a new MBS service area and service time.

In summary, the technical solutions provided in the embodiments of the present application are summarized below from different network entity sides.

On the core side, for example, on any network function NF entity side of the core side, the NF entity, for example, AF, PCF, SMF, MB-SMF, AMF, etc., referring to fig. 3, a service transmission control method provided in the embodiment of the present application includes:

s101, determining parameters for controlling transmission of broadcast and/or multicast service, wherein the parameters comprise service time and/or service area of the service;

such as the MBS parameters described above.

S102, the parameters are sent to an access network through at least one network function entity of a core network, so that the access network sends the service to a terminal according to the parameters.

For example, the method may be that after the AMF entity acquires the parameters sent by the SMF, the AMF entity directly sends the parameters to the access network;

or, after the AF entity obtains the request result sent by the NWDAF entity, the AF entity may determine the parameters according to the request result, send the parameters to the access network through PCF, SMF or MB-SMF, AMF, respectively, and in the process of sending the parameters to the access network through a plurality of network function entities, the plurality of network function entities may further redetermine parameters for controlling broadcast and/or multicast service transmission according to related information (for example, the request result and/or MBs parameters) obtained by the AF entity, and send the parameters to the access network.

Optionally, the method further comprises:

For example, after receiving the parameter sent by the AF entity, the PCF entity re-determines the parameter based on the request result and/or the parameter sent by the AF entity, and sends the determined parameter to the SMF entity. Similarly, the SMF entity may also operate in the same manner, and will not be described in detail herein.

Therefore, the determination manner of the parameter in step S101 may be to directly obtain the parameter; or firstly, a related request is sent, and after a request result is received, the parameter is determined according to the request result; the parameters may be redetermined based on the acquired parameters and/or the request result.

At the core network side, for example, at the NWDAF entity side, referring to fig. 4, a service transmission control method provided in the embodiment of the present application includes:

s201, receiving a request message sent by a first network functional entity of a core network, wherein the request message is used for requesting information about the number of terminals receiving broadcast and/or multicast service;

The first network function entity may comprise one or more network function entities. The first network function entity is, for example, AF, PCF, SMF, MB-SMF, AMF, etc.

S202, determining a request result according to the request message, and sending the request result to the first network function entity, so that the first network function entity determines parameters for controlling the service transmission according to the request result, wherein the parameters comprise service time and/or service area of the service.

The determining is used to control parameters of the service transmission, such as the update MBS parameters described above.

Wherein the second network functional entity may be the same as or different from the first network functional entity.

The second network function entity may comprise one or more network function entities. The second network function entity is for example AF, PCF, SMF, MB-SMF, AMF, etc.

Optionally, the request result specifically includes:

At an access network side, for example, at a base station side, referring to fig. 5, a service transmission method provided in an embodiment of the present application includes:

s301, receiving parameters which are sent by a core network and used for controlling the transmission of broadcast and/or multicast services, wherein the parameters comprise service time and/or service area of the services;

s302, the service is sent to the terminal according to the parameters.

For example, the base station transmits broadcast and/or multicast traffic to the terminals only at the service time and/or service area of the traffic.

The following describes the apparatus provided in the embodiments of the present application, where explanation or illustration of the same or corresponding technical features as those described in the above method is omitted herein.

Referring to fig. 6, a computing device provided in an embodiment of the present application may be understood as any network device, for example, a core network device, an access network device, and the like, where the device includes a memory 520 and a processor 500.

When the device is used to implement the functionality of any NF entity on the core side:

the processor 500 is configured to read the program in the memory 520, and execute the following procedures:

the parameters are sent to the access network by at least one network function entity of the core network through the transceiver 510, so that the access network sends the service to the terminal according to the parameters.

Optionally, the processor 500 is further configured to read the program in the memory 520, and execute the following procedure:

transmitting a request message for requesting information about the number of terminals receiving the broadcast and/or multicast service to the network data analysis function NWDAF entity through the transceiver 510;

the request result sent by the NWDAF entity is received by transceiver 510, and the parameter is determined according to the request result.

the parameters for controlling the transmission of broadcast and/or multicast services sent by another network function entity than the local network function entity are received by the transceiver 510, and the parameters determined by the local end are determined according to the parameters sent by the other network function entity.

When the device is used to implement the functionality of the NWDAF entity on the core side:

receiving, by the transceiver 510, a request message transmitted from a first network function entity of the core network, the request message requesting information about the number of terminals receiving the broadcast and/or multicast service;

and determining a request result according to the request message, and sending the request result to the first network function entity through the transceiver 510, so that the first network function entity determines parameters for controlling the service transmission according to the request result, wherein the parameters comprise service time and/or service area of the service.

Optionally, the request result specifically includes:

When the device, which may be, for example, a base station, is used to implement the functionality of the access network:

receiving, by the transceiver 510, parameters sent by the core network for controlling transmission of broadcast and/or multicast services, the parameters including a service time and/or a service area of the services;

the traffic is transmitted to the terminal through the transceiver 510 according to the parameters.

A transceiver 510 for receiving and transmitting data under the control of the processor 500.

Wherein in fig. 6, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 500 and various circuits of memory represented by memory 520, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

The processor 500 may be a Central Processing Unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA), or a complex programmable logic device (Complex Programmable Logic Device, CPLD).

The following describes the devices corresponding to the above three methods in the embodiments of the present application.

At the core side, for example, at any network function NF entity side of the core side, referring to fig. 7, a service transmission control apparatus provided in this embodiment of the present application includes:

a determining parameter unit 11 for determining parameters for controlling the transmission of broadcast and/or multicast traffic, said parameters comprising a service time and/or a service area of said traffic;

and the sending parameter unit 12 is configured to send the parameter to an access network through at least one network function entity of a core network, so that the access network sends the service to a terminal according to the parameter.

Optionally, the determining parameter unit 11 is further configured to:

At the core network side, for example, at the NWDAF entity side, referring to fig. 8, a service transmission control device provided in this embodiment of the present application includes:

a receiving request unit 21, configured to receive a request message sent by a first network function entity of a core network, where the request message is used to request information about the number of terminals receiving a broadcast and/or multicast service;

and a request result sending unit 22, configured to determine a request result according to the request message, and send the request result to the first network function entity, so that the first network function entity determines, according to the request result, parameters for controlling transmission of the service, where the parameters include a service time and/or a service area of the service.

Optionally, the request result specifically includes:

On the access network side, referring to fig. 9, a service transmission device provided in the embodiment of the present application includes:

a receiving parameter unit 31, configured to receive parameters sent by a core network and used for controlling transmission of broadcast and/or multicast services, where the parameters include service time and/or service area of the services;

and a service transmission unit 32, configured to send the service to the terminal according to the parameter.

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution, in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the method of any of the above embodiments. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The present embodiments provide a computer readable storage medium for storing computer program instructions for use with the apparatus provided by the embodiments of the present application described above, which includes a program for executing any one of the methods provided by the embodiments of the present application described above. The computer readable storage medium may be a non-transitory computer readable medium.

The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), etc.

It should be understood that:

the access technology via which an entity in the communication network communicates traffic may be any suitable current or future technology, such as WLAN (wireless local access network), wiMAX (worldwide interoperability for microwave access), LTE-a, 5G, bluetooth, infrared, etc. may be used; in addition, embodiments may also apply wired technologies, e.g., IP-based access technologies, such as wired networks or fixed lines.

Embodiments suitable for implementation as software code or portions thereof and for execution using a processor or processing function are software code independent and may be specified using any known or future developed programming language, such as a high-level programming language, such as an objective-C, C, C ++, c#, java, python, javascript, other scripting languages, etc., or a low-level programming language, such as a machine language or assembler.

The implementation of the embodiments is hardware-independent and may be implemented using any known or future developed hardware technology or any hybrid thereof, such as microprocessors or CPUs (central processing units), MOS (metal oxide semiconductors), CMOS (complementary MOS), biMOS (bipolar MOS), biCMOS (bipolar CMOS), ECL (emitter coupled logic), and/or TTL (transistor-transistor logic).

Embodiments may be implemented as a single device, unit, component, or function, or in a distributed fashion, e.g., one or more processors or processing functions may be used or shared in a process, or one or more processing segments or portions may be used and shared in a process where one physical processor or more than one physical processor may be used to implement one or more processing portions that are specific to a particular process as described.

A device may be implemented by a semiconductor chip, a chipset, or a (hardware) module comprising such a chip or chipset.

Embodiments may also be implemented as any combination of hardware and software, such as an ASIC (application specific IC (integrated circuit)) component, an FPGA (field programmable gate array) or CPLD (complex programmable logic device) component, or a DSP (digital signal processor) component.

Embodiments may also be implemented as a computer program product comprising a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to perform a process as described in the embodiments, wherein the computer usable medium may be a non-transitory medium.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A traffic transmission control method, the method comprising:

2. The method according to claim 1, characterized in that the method further comprises:

3. The method according to claim 1, characterized in that the method further comprises:

4. A traffic transmission control method, the method comprising:

5. The method according to claim 4, wherein determining a request result according to the request message specifically comprises:

6. The method according to claim 4, wherein the requesting the result specifically comprises:

7. A method for transmitting traffic, the method comprising:

and sending the service to the terminal according to the parameters.

8. A computing device, comprising:

a memory for storing program instructions;

a processor for invoking program instructions stored in said memory to perform the method of any of claims 1-7 in accordance with the obtained program.

9. A computer program product for a computer, characterized in that it comprises software code portions for performing the steps of any of claims 1 to 7 when the product is run on the computer.

10. A computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 7.