Media data receiving method and apparatus, display terminal, and storage medium

Abstract

The application provides a media data receiving method and device, a display terminal and a storage medium, and relates to the technical field of broadcast television. The method comprises the following steps: sending a first creation resource request message; receiving a first creation resource response message; updating the subscription period of a target operator according to the actual running time of the target operator and the first creation resource response message; sending a search resource request message in response to user login information; receiving a search resource response message, and determining whether to receive and play media data issued by the target operator network according to the search resource response message. The scheme can dynamically update and lock the subscription period of an operator, thereby realizing the simultaneous locking of the subscription periods of different operators while being compatible with media data of different operators, and effectively solving the problem that the customized set-top boxes of different operators in the prior art only support the media data provided by the operator and cannot receive the media data provided by other operators.

Description

Technical Field

[0001] This invention relates to the field of broadcasting and television technology, and more specifically, to a media data receiving method, apparatus, display terminal, and storage medium. Background Technology

[0002] A digital video converter box, commonly known as a set-top box or set-top box, is a device used to connect a television set to an external signal source. In addition to the images and sound provided by analog television, a set-top box can also receive digital content, including electronic program guides and internet web pages.

[0003] Currently, in home and other user scenarios, it is necessary to connect the playback terminal (such as digital TV) to the target network of each operator by using customized set-top boxes provided by different operators in order to receive the media data provided by each operator.

[0004] However, the existing method of receiving media data results in different operators' customized set-top boxes only supporting media data provided by their own operator and being unable to receive media data provided by other operators. Summary of the Invention

[0005] The purpose of this invention is to address the shortcomings of the prior art by providing a media data receiving method, apparatus, terminal equipment, and storage medium, so as to solve the problems that existing custom set-top boxes cannot be used by other operators and that the received digital television content is limited to the single digital program provided by the custom set-top box.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0007] In a first aspect, embodiments of this application provide a media data receiving method, applied to a display terminal, the method comprising:

[0008] Send a first resource creation request message, wherein the first resource creation request message includes: the target operator's contract information and the resource name, and the contract information includes: contract status and contract period;

[0009] Receive a first resource creation response message, wherein the first resource creation response message includes at least one of the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator;

[0010] Update the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message;

[0011] In response to user login information, a resource retrieval request message is sent, wherein the resource retrieval request message is used to indicate the query of the contract status of the target operator;

[0012] Receive a resource retrieval response message, and determine whether to receive and play media data sent by the target operator's network based on the resource retrieval response message. The resource retrieval response message includes: contract period and contract status.

[0013] Optionally, updating the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message includes:

[0014] If the first resource creation response message indicates successful creation, then start a timer to obtain the actual runtime of the target operator;

[0015] Based on the actual runtime of the target operator obtained by the timer and the first creation resource response message, the contract period of the target operator is updated, wherein the value of the contract period is the difference between the contract period in the first creation resource response message and the actual runtime of the target operator.

[0016] Send a first updated resource message, which includes: resource name and contract period;

[0017] Receive a first update resource response message, wherein the first update resource response message includes: update status.

[0018] Optionally, determining whether to receive and play media data sent by the target operator's network based on the retrieved resource response message includes:

[0019] If the target operator's contract status is "signed" and the contract period of the target operator is greater than zero, then the media data sent by the target operator's network will be received and played.

[0020] Optionally, the step of responding to user login information and sending a resource retrieval request message includes:

[0021] In response to user login information, the system obtains the operator network currently connected to the display terminal, wherein the operator network includes at least one of a first operator network, a second operator network, and a third operator network;

[0022] Based on the currently connected operator network, the resource retrieval request message is sent, wherein the resource retrieval request message includes at least one of the following: operator identifier, subscription status;

[0023] The system receives the resource retrieval response message and displays a contract period prompt box, wherein the resource retrieval response message includes the contract period and contract status.

[0024] Optionally, the method further includes:

[0025] In response to user renewal requests, a contract is signed with the target operator's network based on the network address of the target operator's network.

[0026] If the contract is successfully signed, a second update resource message is sent. The second update resource message is used to instruct the first sub-resource corresponding to the target operator to be updated. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0027] Receive the second updated resource response message.

[0028] Optionally, before sending the first create resource request message, the method further includes:

[0029] If it is determined that the network of the operator currently connected to the display terminal is the network of the target operator, a second resource creation request message is sent; the second resource creation request message includes the target operator and authentication information for connecting to the target operator's network;

[0030] Receive a second resource creation response message, wherein the second resource creation response message is used to indicate the status that the second sub-resource corresponding to the target operator has been successfully created;

[0031] Based on the second resource creation response message and the authentication information, a connection is established with the target operator's network. If the connection is successful, the first resource creation request message is sent.

[0032] Secondly, embodiments of this application also provide a media data receiving method, applied to a display terminal, the method comprising:

[0033] Receive the first resource creation request message;

[0034] Based on the received first create resource request message, a first sub-resource of the target operator is created, wherein the first sub-resource includes the following attributes: resource name, contract period of the target operator, and contract status of the target operator;

[0035] Send a first resource creation response message, wherein the first resource creation response message includes the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator;

[0036] Receive a resource retrieval request message, the resource retrieval request message being used to indicate querying the contract status of the target operator;

[0037] Based on the resource retrieval request message, query the contract status of the target operator and send a resource retrieval response message, which includes the contract status and contract period.

[0038] Optionally, the method further includes:

[0039] Receive the first updated resource message, which includes the resource name and contract period;

[0040] According to the first updated resource message, update the contract period of the target operator in the first sub-resource;

[0041] Send a first update resource response message, wherein the first update resource response message includes: update status.

[0042] Optionally, the first resource creation request message includes: the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created;

[0043] The step of creating the first sub-resource of the target operator according to the received first resource creation request message includes:

[0044] Based on the resource type, resource name, and contract information of the requested resource, a first sub-resource of the target operator is created, and the following attributes are created for the first sub-resource: the contract status of the target operator, user verification information, digital resource, contract identifier of the target operator, and contract term of the target operator.

[0045] Optionally, the first sub-resource further includes: a sub-resource policy, used to instruct the notification object to update the value according to the notification content when the monitored object meets the preset value, the sub-resource policy including the following attributes: monitoring object identifier, notification object identifier, and notification content.

[0046] Optionally, querying the contract status of the target operator based on the resource retrieval request message includes:

[0047] According to the resource retrieval request message, query whether the operator identifier of the currently connected operator network is consistent with the subscription identifier of the target operator in the first sub-resource, wherein the resource retrieval request message includes the following: operator identifier, subscription status;

[0048] If so, and the target operator's contract status in the first sub-resource is found to be "signed", then a resource retrieval response message is sent, wherein the resource retrieval response message includes: contract period and contract status.

[0049] Optionally, the method further includes:

[0050] Receive the second updated resource message;

[0051] According to the second updated resource message, the first sub-resource corresponding to the target operator is updated. The second updated resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0052] Send a second update resource response message.

[0053] Optionally, before receiving the first create resource request message, the method further includes:

[0054] Receive the second resource creation request message;

[0055] Based on the received second resource creation request message, a second sub-resource corresponding to the target operator is created, and the following attributes are created for the second sub-resource: the network address of the target operator and the identifier of the target operator;

[0056] Send a second resource creation response message, wherein the second resource creation response message includes at least one of the following: digital resources contracted with the target operator, and the result of the requested resource creation.

[0057] Thirdly, embodiments of this application provide a media data receiving device applied to a display terminal, the device comprising:

[0058] The sending module is used to send a first resource creation request message, wherein the first resource creation request message includes: the target operator's contract information and the resource name, and the contract information includes: contract status and contract period;

[0059] The receiving module is configured to receive a first resource creation response message, wherein the first resource creation response message includes at least one of the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator;

[0060] The update module is used to update the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message;

[0061] The sending module is also used to respond to user login information and send a resource retrieval request message, wherein the resource retrieval request message is used to indicate the query of the contract status of the target operator;

[0062] The receiving module is also used to receive resource retrieval response messages;

[0063] The determination module is used to determine whether to receive and play media data sent by the target operator's network based on the retrieved resource response message, wherein the retrieved resource response message includes: contract period and contract status.

[0064] Optionally, the update module is further configured to:

[0065] If the first resource creation response message indicates successful creation, then start a timer to obtain the actual runtime of the target operator;

[0066] Based on the actual runtime of the target operator obtained by the timer and the first creation resource response message, the contract period of the target operator is updated, wherein the value of the contract period is the difference between the contract period in the first creation resource response message and the actual runtime of the target operator.

[0067] The sending module is further configured to send a first updated resource message, the first updated resource message including: resource name and contract period;

[0068] The receiving module is further configured to receive a first updated resource response message, wherein the first updated resource response message includes: update status.

[0069] Optionally, the determining module is further configured to:

[0070] If the target operator's contract status is "signed" and the contract period of the target operator is greater than zero, then the media data sent by the target operator's network will be received and played.

[0071] Optionally, the sending module is further configured to:

[0072] In response to user login information, the system obtains the operator network currently connected to the display terminal, wherein the operator network includes at least one of a first operator network, a second operator network, and a third operator network;

[0073] Based on the currently connected operator network, the resource retrieval request message is sent, wherein the resource retrieval request message includes at least one of the following: operator identifier, subscription status;

[0074] The receiving module is also used to receive the resource retrieval response message and pop up a contract period prompt box, wherein the resource retrieval response message includes the contract period and the contract status.

[0075] Optionally, the device further includes:

[0076] The contract signing module is used to respond to user renewal information and sign a contract with the target operator network based on the network address of the target operator network.

[0077] The sending module is further configured to send a second updated resource message if the contract is successful. The second updated resource message is used to instruct the first sub-resource corresponding to the target operator to be updated. The second updated resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0078] The receiving module is also used to receive a second updated resource response message.

[0079] Optionally, the sending module is further configured to send a second resource creation request message if it is determined that the operator network currently connected to the display terminal is the network of the target operator; the second resource creation request message includes the target operator and authentication information for connecting to the target operator's network;

[0080] The receiving module is further configured to receive a second resource creation response message, wherein the second resource creation response message is used to indicate the status that the second sub-resource corresponding to the target operator has been successfully created;

[0081] The device further includes:

[0082] The connection module is used to establish a connection with the target operator's operator network based on the second creation resource response message and the authentication information;

[0083] The sending module is further configured to send the first resource creation request message if the connection is successful.

[0084] Fourthly, embodiments of this application also provide a media data receiving device, applied to a display terminal, the device comprising:

[0085] The receiving module is used to receive the first resource creation request message;

[0086] A creation module is used to create a first sub-resource of the target operator based on the received first creation resource request message, wherein the first sub-resource includes the following attributes: resource name, contract period of the target operator, and contract status of the target operator;

[0087] The sending module is used to send a first resource creation response message, wherein the first resource creation response message includes the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator;

[0088] The receiving module is used to receive a resource retrieval request message, which is used to indicate the query of the contract status of the target operator;

[0089] The query module is used to query the contract status of the target operator based on the resource retrieval request message, and send a resource retrieval response message, which includes the contract status and contract period.

[0090] Optionally, the receiving module is further configured to receive a first updated resource message, the first updated resource message including a resource name and a contract period;

[0091] The device includes:

[0092] The update module is used to update the contract period of the target operator in the first sub-resource according to the first update resource message;

[0093] The sending module is further configured to send a first update resource response message, wherein the first update resource response message includes: update status.

[0094] Optionally, the first resource creation request message includes: the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created;

[0095] The creation module is also used for:

[0096] Based on the resource type, resource name, and contract information of the requested resource, a first sub-resource of the target operator is created, and the following attributes are created for the first sub-resource: the contract status of the target operator, user verification information, digital resource, contract identifier of the target operator, and contract term of the target operator.

[0097] Optionally, the first sub-resource further includes: a sub-resource policy, used to instruct the notification object to update the value according to the notification content when the monitored object meets the preset value, the sub-resource policy including the following attributes: monitoring object identifier, notification object identifier, and notification content.

[0098] Optionally, the query module is further configured to query, based on the resource retrieval request message, whether the operator identifier of the currently connected operator network is consistent with the subscription identifier of the target operator in the first sub-resource, wherein the resource retrieval request message includes the following: operator identifier, subscription status;

[0099] The sending module is further configured to, if so, and if the contract status of the target operator in the first sub-resource is found to be "signed", then send a resource retrieval response message, wherein the resource retrieval response message includes: contract period and contract status.

[0100] Optionally, the receiving module is further configured to receive a second updated resource message;

[0101] The update module is further configured to update the first sub-resource corresponding to the target operator according to the second update resource message, wherein the second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period;

[0102] The sending module is also used to send a second update resource response message.

[0103] Optionally, the receiving module is further configured to receive a second resource creation request message;

[0104] The creation module is further configured to create a second sub-resource corresponding to the target operator based on the received second creation resource request message, and create the following attributes for the second sub-resource: the network address of the target operator and the identifier of the target operator;

[0105] The sending module is further configured to send a second resource creation response message, wherein the second resource creation response message includes at least one of the following: digital resources contracted with the target operator, and the result of the requested resource creation.

[0106] Fifthly, embodiments of this application also provide a display terminal, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the display terminal is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the method provided in the first or second aspect.

[0107] In a sixth aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the method provided in the first or second aspect.

[0108] The beneficial effects of this application are:

[0109] This application provides a media data receiving method, apparatus, device, and storage medium. The solution primarily involves the application layer sending a first resource creation request message to the general service layer. The general service layer, based on the received first resource creation request message, creates a first sub-resource of the operator. The attributes of this first sub-resource include: resource name, operator's contract period, and operator's contract status. After successfully creating the operator's first sub-resource, the general service layer sends a first resource creation response message to the application layer. This allows the application layer to dynamically update and lock the operator's contract period based on the operator's actual runtime and the first resource creation response message. When a user logs in again to the mobile digital resource interface provided by the application layer, the application layer responds with the user's login information and sends a resource retrieval request message to the general service layer based on the user's login information. The general service layer uses the resource retrieval request message as a query condition to retrieve data from existing... The system queries the first sub-resource of the created operator to find the subscription status of the operator currently connected to the display terminal's network. The query result (i.e., the retrieval resource response message) is then returned to the application layer. Based on the received retrieval resource response message, the application layer determines whether it can receive and play media data from the same operator's network as the display terminal's current network. This achieves compatibility with media data from different operators while locking the subscription period for each operator, avoiding scenarios where operator A's network provides media data from operator B. This solution enables software support for media data from all three major operators, provided multiple operator networks are available, and avoids the need to purchase multiple customized set-top boxes. It effectively solves the problem in existing technologies where customized set-top boxes from different operators only support media data provided by their own operator and cannot receive media data from other operators. Attached Figure Description

[0110] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0111] Figure 1 This is a schematic diagram of the structure of a media data receiving system provided in an embodiment of this application;

[0112] Figure 2 This is a schematic diagram of the structure of a display terminal provided in an embodiment of this application;

[0113] Figure 3 A flowchart illustrating a media data receiving method provided in an embodiment of this application;

[0114] Figure 4A flowchart illustrating another media data receiving method provided in an embodiment of this application;

[0115] Figure 5 A flowchart illustrating yet another media data receiving method provided in an embodiment of this application;

[0116] Figure 6 A flowchart illustrating another media data receiving method provided in an embodiment of this application;

[0117] Figure 7 A flowchart illustrating yet another media data receiving method provided in an embodiment of this application;

[0118] Figure 8 This is a schematic diagram of the structure of a media data receiving device provided in an embodiment of this application;

[0119] Figure 9 This is a schematic diagram of another media data receiving device provided in an embodiment of this application.

[0120] Icons: 100 - Media data receiving system; 101 - Display terminal; 102 - Carrier server. Detailed Implementation

[0121] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0122] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0123] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0124] First, the framework of the media data receiving system provided in this application will be briefly described through the following embodiments.

[0125] Figure 1 This is a schematic diagram of the structure of a media data receiving system provided in an embodiment of this application. The media data receiving system 100 includes one or more of the following: a display terminal 101, at least one operator server 102, and a network 103. The display terminal 101 and the server 102 of each operator may include processors that execute instruction operations. The terminal device 101 and the server 102 of each operator can be connected to each other through the network 103.

[0126] This solution mainly addresses the interaction between the display terminal 101 and different operator servers 102. The display terminal 101 can be an electronic device such as a projector, used to implement the media data receiving method provided in this application. Specifically, after verification by each operator, the display terminal 101 can obtain media data corresponding to each operator from the different operator servers 102, thus solving the problems in the prior art where customized set-top boxes cannot be used with other operators and digital television content is limited to the single digital programs provided by the customized set-top box.

[0127] Secondly, the structure of the display terminal, the execution subject of the media data receiving method provided in this application, will be briefly described through the following embodiments.

[0128] Figure 2 This is a schematic diagram of a display terminal provided in an embodiment of this application; the display terminal is used to implement the media data receiving method provided in this application. Figure 2 As shown, the display terminal 101 includes: a processor 201 and a memory 202.

[0129] The processor 201 and the memory 202 are electrically connected directly or indirectly to enable data transmission or interaction. For example, the electrical connection can be achieved through one or more communication buses or signal lines.

[0130] The processor 201 can be an integrated circuit chip with signal processing capabilities. The processor 201 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor.

[0131] The memory 202 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0132] The memory 202 is used to store programs, and the processor 201 calls the programs stored in the memory 202 to execute the media data receiving method provided in the following embodiments.

[0133] Understandable. Figure 2 The structure is for illustrative purposes only; the display terminal 101 may also include components that are more advanced than those described above. Figure 2 The more or fewer components shown, or having the same Figure 2 The different configurations shown. Figure 2 The components shown can be implemented using hardware, software, or a combination thereof.

[0134] Before introducing the media data receiving method provided in this application, let's first discuss... Figure 1 This paper introduces the multiple execution layers contained in the display terminal of the Chinese media data receiving system.

[0135] The display terminal includes: Application Entity (AE), Common Services Entity (CSE), and Network Services Entity (NSE). The Application Entity is the user interface.

[0136] In this solution, the display terminal has the functions of a set-top box. The display terminal includes the following functional modules: encoding and decoding functions, network functions, and interactive functions. The display terminal supports obtaining the digital programs corresponding to each operator after verification by each operator. That is, this application manages and interacts with the set-top box-related resources based on the functional modules of existing projection equipment, so as to solve the problems existing in the prior art.

[0137] The media data receiving method provided in this application and the corresponding beneficial effects will be described below through multiple embodiments.

[0138] Figure 3 A flowchart illustrating a media data receiving method provided in this application embodiment; optionally, the execution entity of this method may be the one shown. Figure 1 The display terminal in the middle.

[0139] It should be understood that in other embodiments, the order of some steps in the media data receiving method can be interchanged according to actual needs, or some steps can be omitted or deleted. For example... Figure 3 As shown, the method includes:

[0140] S301, The application layer sends the first resource creation request message to the general service layer.

[0141] The first resource creation request message includes: the target operator's contract information and the resource name. The contract information includes: contract status and contract duration. Additionally, the first resource creation request message may also include the target operator's resource type. The target operator's contract information indicates the contract information of the requested resource, the target operator's resource name indicates the name of the requested resource (e.g., any of the three major operators), and the target operator's resource type indicates the type of resource to be created. See Table 1 below for details of the parameter information included in the first resource creation request message.

[0142] Table 1. Parameter information contained in the first resource creation request message.

[0143]

[0144]

[0145] S302. The general service layer creates the first sub-resource of the target operator based on the received first create resource request message.

[0146] The first sub-resource includes the following attributes: resource name, target operator's contract period, and target operator's contract status. The resource name indicates the name of the resource to be created; the target operator's contract period indicates the contract duration with the target operator, typically set to 365 days; and the target operator's contract status indicates the contract status of the resource to be created, typically set to the "registered" status.

[0147] In this embodiment, the general service layer creates a first sub-resource of the target operator on the general service layer side according to the received first resource creation request message. The attribute information included in the first sub-resource can be seen in Table 2 below.

[0148] Table 2 shows the attribute information included in the first sub-resource.

[0149]

[0150] S303, the general service layer sends the first resource creation response message to the application layer.

[0151] The first resource creation response message includes at least one of the following: a digital resource contracted with the target operator, the result of the requested resource creation, and the contract period with the target operator. For example, the contract period with the target operator could be 100 days.

[0152] In addition, the first resource creation response message may also include: resource name and resource identifier, wherein the resource name indicates the name of the resource to be created, and the resource identifier indicates the identifier of the resource to be created. The parameter information included in the first resource creation response message is shown in Table 3 below.

[0153] Table 3 contains parameter information for the first resource creation response message.

[0154]

[0155] In this embodiment, after the general service layer successfully creates the first sub-resource and creates attributes for the first sub-resource, the general service layer sends a first resource creation response message to the application layer. The first resource creation response message includes: the digital resource contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator, so that the application layer can continue to perform subsequent processing based on the first resource creation response message.

[0156] S304. The application layer updates the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message.

[0157] The actual runtime of the target operator refers to the time elapsed between the start time of the user's purchase of media data provided by the target operator and the current time. For example, the actual runtime of the target operator can be obtained by a timer provided by the application layer, or it can be calculated directly by the application layer based on the start time of the user's purchase of media data provided by the target operator and the current time.

[0158] For every 24 hours of actual operation by the target operator, the value of the target operator's contract period is reduced by 1.

[0159] In this embodiment, the application layer updates the contract period of the target operator in real time based on the actual runtime of the target operator and the first creation resource response message. Whenever the value of the contract period of the target operator is updated, the application layer sends the first update resource message to the general service layer.

[0160] S305, Application layer responds with user login information.

[0161] S306. The application layer sends a resource retrieval request message to the general service layer.

[0162] The resource retrieval request message is used to indicate the subscription status of the target operator.

[0163] Optionally, after the first sub-resource of the target operator is created in the general service layer, when the user logs in again through the display terminal to the mobile digital resource interface provided by the application layer, the application layer responds to the user login information. Based on the user login information, the application layer sends a resource retrieval request message to the general service layer. This resource retrieval request message is used to indicate the query of the target operator's subscription status.

[0164] S307. The general service layer queries the contract status of the target operator based on the resource retrieval request message.

[0165] S308. The general service layer sends a resource retrieval response message to the application layer.

[0166] The resource retrieval response message includes: contract status and contract duration.

[0167] In this embodiment, the general service layer queries the target operator's contract status from the attributes of the first sub-resource that has been created, based on the received resource retrieval request message, to obtain the target operator's contract status and contract term, and then returns the queried target operator's contract status and contract term to the application layer.

[0168] S309. The application layer determines whether to receive and play media data sent by the target operator's network based on the resource retrieval response message.

[0169] In this embodiment, the application layer further determines whether it can obtain media data sent by the target operator network based on the received resource retrieval response message. If yes, it receives and plays the media data sent by the target operator network; otherwise, it cannot receive the media data sent by the target operator network.

[0170] In summary, this application provides a media data receiving method, which includes: sending a first resource creation request message, the first resource creation request message including: the target operator's contract information and resource name, the contract information including: contract status and contract period; receiving a first resource creation response message, the first resource creation response message including at least one of the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator; updating the contract period of the target operator based on the actual runtime of the target operator and the first resource creation response message; responding to user login information and sending a resource retrieval request message, the resource retrieval request message being used to indicate querying the contract status of the target operator; receiving a resource retrieval response message, and determining whether to receive and play media data distributed by the target operator's network based on the resource retrieval response message. In this scheme, the application layer primarily sends a first resource creation request message to the general service layer. Based on the received first resource creation request message, the general service layer creates the operator's first sub-resource. The attributes of this first sub-resource include: resource name, operator's contract period, and operator's contract status. After successfully creating the operator's first sub-resource, the general service layer sends a first resource creation response message to the application layer. This allows the application layer to dynamically update and lock the operator's contract period based on the operator's actual runtime and the first resource creation response message. When a user logs in again to the mobile digital resource interface provided by the application layer, the application layer responds with the user's login information and sends a resource retrieval request message to the general service layer based on the user's login information. The general service layer uses the resource retrieval request message as the query condition to retrieve the first sub-resource of the operator from the already created resources. The system queries the contract status of the operator whose network is currently connected to the display terminal and returns the query result (i.e., the resource retrieval response message) to the application layer. The application layer then determines whether it can receive and play media data from the same operator's network as the display terminal's current network based on the received resource retrieval response message. This achieves compatibility with media data from different operators while locking the contract period of each operator, avoiding scenarios where operator A's network provides media data from operator B. It enables software support for media data from all three major operators, provided multiple operator networks are available, and avoids the need to purchase multiple customized set-top boxes. This effectively solves the problem in existing technologies where customized set-top boxes from different operators only support media data provided by their own operator and cannot receive media data from other operators.

[0171] The following examples will explain in detail how the application layer updates the target operator's contract period based on the target operator's actual runtime and the first creation resource response message in step S304.

[0172] Optionally, refer to Figure 4As shown, step S304 above includes:

[0173] S401. If the first resource creation response message indicates successful creation, the application layer starts a timer to obtain the actual runtime of the target operator.

[0174] In this embodiment, the actual runtime of the target operator can be obtained by a timer provided by the application layer, that is, by starting the timer to count the time.

[0175] In another possible approach, the actual runtime of the target operator can be obtained by a timer provided by the general service layer. The specific implementation method will be described in detail in subsequent embodiments.

[0176] S402. The application layer updates the contract period of the target operator based on the actual runtime of the target operator obtained by the timer and the first creation resource response message.

[0177] The contract duration value is the difference between the contract duration stated in the first resource creation response message and the actual runtime of the target operator. It should be understood that the contract duration value decreases by 1 for every 24 hours of actual runtime of the target operator.

[0178] In this embodiment, the application layer can directly subtract the contract period in the first resource creation response message from the actual runtime of the target operator, and use the difference as the updated contract period for the target operator. For example, if the contract period in the first resource creation response message is 365 days and the actual runtime of the target operator is 100 days, then the updated contract period for the target operator is 265 days.

[0179] S403, The application layer sends the first update resource message to the general service layer.

[0180] The first updated resource message includes: resource name and contract period.

[0181] In this embodiment, after updating the contract period of the target operator, the application layer sends a first update resource message to the general service layer. The first update resource message may further include a resource identifier, which indicates the resource identifier requested to be created. Table 4 below shows the parameter information included in the first update resource message.

[0182] Table 4 contains parameter information in the first updated resource message.

[0183]

[0184]

[0185] S404. The general service layer updates the contract period of the target operator in the first sub-resource based on the first update resource message.

[0186] S405, the general service layer sends the first update resource response message to the application layer.

[0187] The first update resource response message includes: update status.

[0188] Optionally, after receiving the first update resource message, the general service layer updates the contract period of the target operator in the first sub-resource. After updating the contract period of the target operator, the general service layer sends a first update resource response message to the application layer. The first update resource response message includes the update status, wherein the update status is set to success.

[0189] Optionally, the above-mentioned search resource response message includes: contract period and contract status. In step S309, the application layer determines whether to receive and play the media data sent by the target operator's network based on the search resource response message, including: if the target operator's contract status is "signed" and the value of the target operator's contract period is greater than zero, then the media data sent by the target operator's network is received and played.

[0190] Optionally, if the target operator's contract status is "signed" and the contract period of the target operator is greater than zero, then media data sent by the operator network that is consistent with the network currently connected to the display terminal can be received and played. This achieves compatibility with media data from different operators while locking the contract period of each operator, avoiding the scenario where operator A's network provides media data from operator B.

[0191] Optionally, refer to Figure 5 As shown, in step S305 above, the application layer responds to the user login information, including:

[0192] S501, The application layer responds to the user login information and obtains the operator network currently connected to the display terminal.

[0193] The operator network includes at least one of a first operator network, a second operator network, and a third operator network. For example, the first, second, and third operator networks can be a mobile operator network, a telecommunications operator network, and a China Unicom operator network, respectively. That is, the operator network currently connected to the display terminal can be at least one of a mobile operator network, a telecommunications operator network, or a China Unicom operator network. The display terminal can obtain media data corresponding to the user account from the currently connected operator network (such as a mobile operator network, a telecommunications operator network, or a China Unicom operator network) and play the obtained media data.

[0194] S502. The application layer sends a resource retrieval request message to the general service layer based on the currently connected operator network.

[0195] The resource retrieval request message includes at least one of the following: operator identifier and subscription status.

[0196] In this embodiment, when a user logs in again to the mobile digital resource interface provided by the application layer, the application layer responds to the user's login information, obtains the operator network currently connected to the display terminal, determines the operator identifier (ISP) corresponding to the currently connected operator network based on the currently connected operator network, and sends a resource retrieval request message containing the operator identifier and subscription status to the general service layer.

[0197] In addition, a resource retrieval request message may also include: a resource name and a resource identifier, where the resource name indicates the name of the resource to be created, and the resource identifier indicates the identifier of the resource to be created. Table 5 below shows the parameter information contained in a resource retrieval request message.

[0198] Table 5. Parameter information contained in the resource retrieval request message.

[0199]

[0200] S503. The general service layer queries whether the operator identifier of the currently connected operator network matches the subscription identifier of the target operator in the first sub-resource based on the resource retrieval request message.

[0201] S504. If so, and the target operator's subscription status in the first sub-resource is found to be "subscribed", then the general service layer sends a resource retrieval response message to the application layer.

[0202] The resource retrieval response message includes: contract period and contract status.

[0203] In this embodiment, after receiving the resource retrieval request message, the general service layer uses the operator identifier in the resource retrieval request message as the query condition to query whether the operator identifier (ISP) of the currently connected operator network is consistent with the signing identifier (Sign ISP) of the target operator in the first sub-resource. If they are consistent, the general service layer queries whether the signing status (Sign status) of the target operator in the first sub-resource is "registered". If the signing status (Sign status) is "registered", the general service layer sends a resource retrieval response message to the application layer. The resource retrieval response message contains the signing date (Sign date) and the signing status (status), where the value of the signing status (status) is "success".

[0204] In another possible implementation, if the Sign status is unsigned, the general service layer sends a resource retrieval response message to the application layer with the Sign status value set to "same".

[0205] In another possible implementation, if the ISP identifier of the currently connected operator network is inconsistent with the Sign ISP identifier of the target operator in the first sub-resource, the general service layer sends a retrieval resource response message to the application layer with the subscription status value set to "not".

[0206] S505. After receiving the resource retrieval response message, the application layer will display a pop-up message indicating the contract period.

[0207] Based on the above embodiments, after receiving the resource retrieval response message, if the value of the contract status "status" in the resource retrieval response message is "success", the application layer will pop up a contract period prompt box so that the user can determine whether to renew the contract based on the contract period prompt box.

[0208] In another possible implementation, if the subscription status value of the resource retrieval response message received by the application layer is "same", the application layer sends a resource retrieval message to the general service layer. The resource retrieval message includes a resource identifier (Resource ID), and sets the resource identifier (Resource ID) to Root / / locator. It then obtains the network address URL of the operator corresponding to the currently connected operator network and verifies the operator's server based on the operator's network address URL.

[0209] In another possible implementation, if the value of the subscription status "status" in the resource retrieval response message received by the application layer is "not", the application layer will display a network change prompt.

[0210] The following examples will illustrate the process for handling user renewal requests.

[0211] Optionally, refer to Figure 6 As shown, the method also includes:

[0212] S601, The application layer responds to the user's renewal information and signs a contract with the target operator's network based on the network address of the target operator's network.

[0213] S602. If the contract is successfully signed, the application layer sends a second update resource message to the general service layer.

[0214] The second update resource message is used to instruct the first sub-resource corresponding to the target operator to be updated. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0215] In this embodiment, if a user needs to renew their contract, they can perform the required operation through the renewal interface provided by the application layer. The renewal interface includes: an operator selection box, username and password, login and logout options, and a renewal option. Login and logout are existing technologies and will not be elaborated upon here. After the user clicks the renewal option, the application layer responds to the user's renewal information, subscribes to the target operator's network based on the target operator's network address, and completes the renewal with the target operator's network. After the renewal is completed through the target operator's network address, the application layer sends a second update resource message to the general service layer. This second update resource message indicates that the first sub-resource corresponding to the target operator needs to be updated. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period. Table 6 below shows the parameter information included in the second update resource message.

[0216] Table 6 contains parameter information in the second update resource message.

[0217]

[0218] S603, the general service layer updates the first sub-resource corresponding to the target operator based on the second update resource message.

[0219] S604. The general service layer sends a second update resource response message to the application layer.

[0220] Optionally, after receiving the second update resource message, the general service layer updates the contract period in the first sub-resource corresponding to the target operator, and after updating the contract period (Sign date), sends a second update resource response message to the application layer. The second update resource response message includes the contract status of the target operator, and the value of the contract status (status) is success.

[0221] The following embodiments will be used to explain in detail how the general service layer creates the first sub-resource of the target operator in step S302 above, based on the received first creation resource request message.

[0222] Optionally, the first resource creation request message includes: the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created.

[0223] In step S302 above, creating the first sub-resource of the target operator based on the received first resource creation request message includes:

[0224] The general service layer creates the first sub-resource of the target operator based on the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created, and creates the following attributes for the first sub-resource: the subscription period of the target operator, the subscription status of the target operator, user verification information, digital resources, and the subscription identifier of the target operator.

[0225] In this embodiment, the general service layer creates the first sub-resource of the target operator based on the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created. At the same time, the following attributes are created for the first sub-resource: the contract period of the target operator, the contract status of the target operator, the user verification information, the digital resource, the contract identifier of the target operator, and the resource identifier. The attribute information included in the first sub-resource can be seen in Table 7 below.

[0226] Table 7 shows the attribute information included in the first sub-resource.

[0227]

[0228]

[0229] The following embodiments will specifically explain what processing procedures may be included before sending the first resource creation request message in step S301.

[0230] Optionally, refer to Figure 7 As shown, the method also includes:

[0231] S701. If the application layer determines that the network of the operator currently connected to the display terminal is the network of the target operator, the application layer sends a second resource creation request message to the general service layer.

[0232] The second resource creation request message includes: the target operator and authentication information for connecting to the target operator's network.

[0233] In this embodiment, after selecting IPTV on the signal source interface, the user enters the homepage interface, which includes: an operator selection box, username, and password. On the homepage interface, the user selects a target operator and enters the username and password of the selected target operator. The application layer obtains the operator network currently connected to the display terminal and determines whether the operator identifier (ISP) corresponding to the currently connected operator network is consistent with the operator identifier (e.g., China Mobile) of the target operator selected by the user. If they are consistent, the application layer sends a second resource creation request message to the general service layer. If they are inconsistent, a prompt box pops up: the network is not supported.

[0234] S702. The general service layer creates a second sub-resource corresponding to the target operator based on the received second creation resource request message, and creates the following attributes for the second sub-resource: the network address of the target operator and the identifier of the target operator.

[0235] In this embodiment, the general service layer creates a second sub-resource corresponding to the target operator based on the second resource creation request message, and creates the following attributes for the second sub-resource: the target operator's identifier (ISP) and the target operator's network address (URL). In addition, the attributes created for the second sub-resource may also include: resource type, resource name, and resource ID. The attribute information included in the second sub-resource is shown in Table 8 below.

[0236] Table 8 shows the attribute information included in the second sub-resource.

[0237]

[0238]

[0239] S703, the general service layer sends a second resource creation response message to the application layer.

[0240] The second resource creation response message is used to indicate the status of the second sub-resource corresponding to the target operator that has been successfully created. The second resource creation response message includes at least one of the following: digital resources contracted with the target operator, and the result of the requested resource creation.

[0241] In this embodiment, after successfully creating the second sub-resource corresponding to the target operator, the general service layer sends a second creation resource response message to the application layer. The second creation resource response message is used to indicate the status of successfully creating the second sub-resource corresponding to the target operator. The second creation resource response message includes: the digital resource contracted with the target operator and the creation status of the requested resource. The creation status of the requested resource is used to indicate the result of the requested resource. If the creation is successful, the creation status of the requested resource is set to success.

[0242] In addition, the second resource creation response message may also include: resource type, resource name, target ISP identifier, target ISP's network address URL, etc.

[0243] S704: The application layer establishes a connection with the target operator's network based on the second creation resource response message and authentication information.

[0244] S705. If the connection is successful, the application layer sends a first resource creation request message to the general service layer.

[0245] In this embodiment, after receiving the second create resource response message, the application layer establishes a connection with the target operator's network based on the target operator's network address URL in the second create resource response message and the authentication information (such as account and password) entered by the user for connecting to the target operator's network. If the connection is successful, the application layer receives a connection success message and sends a first create resource request message to the general service layer; if the connection fails, the application layer receives a connection failure message and pops up a prompt box with the message: connection failed.

[0246] Optionally, the first sub-resource also includes: a sub-resource policy, used to instruct the notification object to update the value according to the notification content when the monitored object meets the preset value. The sub-resource policy includes the following attributes: monitoring object identifier, notification object identifier, and notification content.

[0247] In this embodiment, the monitoring entity for setting the contract period of the target operator is the general service layer. Therefore, when creating the first sub-resource, a sub-resource policy is also created. The sub-resource policy is mainly used to instruct the notification object to update the value according to the notification content when the actual runtime of the monitored target operator meets the preset value. Specifically, a timer is set in the general service layer to obtain the actual runtime of the target operator. When the actual runtime of the target operator reaches 24 hours, the value of the contract period (sign date) of the target operator is decremented by 1. The sub-resource policy includes the following attributes: monitoring object identifier, notification object identifier, notification content, requested resource name and resource identifier, as shown in Table 9 below.

[0248] Table 9. Attribute Information Included in Sub-resource Strategies

[0249]

[0250]

[0251] The following describes the media data receiving device and storage medium used to execute the media data provided in this application. The specific implementation process and technical effects are described above and will not be repeated here.

[0252] refer to Figure 8 As shown in the figure, a media data receiving device is provided in an embodiment of this application, which is applied to a display terminal. The device includes:

[0253] The sending module 801 is used to send a first resource creation request message, wherein the first resource creation request message includes: the target operator's contract information and the resource name, and the contract information includes: contract status and contract period;

[0254] The receiving module 802 is used to receive a first resource creation response message, wherein the first resource creation response message includes at least one of the following: a digital resource contracted with a target operator, the result of the requested resource creation, and the contract period of the target operator;

[0255] The update module 803 is used to update the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message;

[0256] The sending module 801 is also used to respond to user login information and send a resource retrieval request message, wherein the resource retrieval request message is used to indicate the subscription status of the target operator to be queried;

[0257] The receiving module 802 is also used to receive resource retrieval response messages;

[0258] The determination module 804 is used to determine whether to receive and play media data sent by the target operator's network based on the resource retrieval response message. The resource retrieval response message includes: contract period and contract status.

[0259] Optionally, update module 803 is also used for:

[0260] If the first resource creation response message indicates successful creation, then start a timer to obtain the actual runtime of the target operator;

[0261] Based on the actual runtime of the target operator obtained by the timer and the first creation resource response message, update the contract period of the target operator, where the value of the contract period is the difference between the contract period in the first creation resource response message and the actual runtime of the target operator.

[0262] The sending module 801 is also used to send a first updated resource message, which includes: resource name and contract period;

[0263] The receiving module 802 is also used to receive a first updated resource response message, wherein the first updated resource response message includes: update status.

[0264] Optionally, module 804 is also used for:

[0265] If the target operator's contract status is "signed" and the contract period is greater than zero, then the media data sent from the target operator's network will be received and played.

[0266] Optionally, the sending module 801 is also used for:

[0267] Respond to user login information and obtain the operator network currently connected to the display terminal;

[0268] Based on the currently connected operator network, a resource retrieval request message is sent, wherein the resource retrieval request message includes at least one of the following: operator identifier, subscription status;

[0269] The receiving module 802 is also used to receive the resource retrieval response message and pop up a contract period prompt box, wherein the resource retrieval response message includes the contract period and the contract status.

[0270] Optionally, the device further includes:

[0271] The contract signing module is used to respond to user renewal requests and sign up with the target operator's network based on the network address of the target operator's network.

[0272] The sending module 801 is also used to send a second update resource message if the contract is successful. The second update resource message is used to instruct the first sub-resource corresponding to the target operator to be updated. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0273] The receiving module 802 is also used to receive the second update resource response message.

[0274] Optionally, the sending module 801 is further configured to send a second create resource request message if it is determined that the operator network currently connected to the display terminal is the network of the target operator; the second create resource request message includes the target operator and authentication information for connecting to the target operator's network;

[0275] The receiving module 802 is further configured to receive a second resource creation response message, wherein the second resource creation response message is used to indicate the status of the second sub-resource corresponding to the target operator being successfully created;

[0276] The device also includes:

[0277] The connection module is used to establish a connection with the target operator's network based on the second creation resource response message and authentication information;

[0278] The sending module 801 is also used to send a first resource creation request message if the connection is successful.

[0279] refer to Figure 9 As shown in the figure, a media data receiving device is provided in an embodiment of this application, which is applied to a display terminal. The device includes:

[0280] Receiver module 901 is used to receive the first resource creation request message;

[0281] The creation module 902 is used to create a first sub-resource of the target operator based on the received first creation resource request message. The first sub-resource includes the following attributes: resource name, contract period of the target operator, and contract status of the target operator.

[0282] The sending module 903 is used to send a first resource creation response message, wherein the first resource creation response message includes the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period with the target operator;

[0283] The receiving module 901 is used to receive a resource retrieval request message, which is used to indicate the subscription status of the target operator to be queried.

[0284] The query module 904 is used to query the contract status of the target operator based on the resource retrieval request message and send a resource retrieval response message, which includes the contract status and contract period.

[0285] Optionally, the receiving module 901 is also configured to receive a first updated resource message, which includes a resource name and a contract period;

[0286] The device includes:

[0287] The update module is used to update the contract period of the target operator in the first sub-resource based on the first update resource message;

[0288] The sending module 903 is also used to send a first update resource response message, wherein the first update resource response message includes: update status.

[0289] Optionally, the first resource creation request message includes: the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created;

[0290] Module 902 was created and is also used for:

[0291] Based on the requested resource type, the requested resource name, and the requested resource's contract information, create the first sub-resource of the target operator, and create the following attributes for the first sub-resource: target operator's contract status, user verification information, digital resource, target operator's contract identifier, and target operator's contract period.

[0292] Optionally, the first sub-resource also includes: a sub-resource policy, used to instruct the notification object to update the value according to the notification content when the monitored object meets the preset value. The sub-resource policy includes the following attributes: monitoring object identifier, notification object identifier, and notification content.

[0293] Optionally, the query module 904 is further configured to query, based on the resource retrieval request message, whether the operator identifier of the currently connected operator network is consistent with the subscription identifier of the target operator in the first sub-resource, wherein the resource retrieval request message includes the following: operator identifier, subscription status;

[0294] The sending module 903 is also used to send a resource retrieval response message if, and if the target operator's contract status in the first sub-resource is found to be "signed up", the resource retrieval response message includes: contract period and contract status.

[0295] Optionally, the receiving module 901 is also configured to receive a second updated resource message;

[0296] The update module is also used to update the first sub-resource corresponding to the target operator according to the second update resource message. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period.

[0297] The sending module 903 is also used to send a second update resource response message.

[0298] Optionally, the receiving module 901 is also configured to receive a second resource creation request message;

[0299] The creation module is also used to create a second sub-resource corresponding to the target operator based on the received second creation resource request message, and to create the following attributes for the second sub-resource: the network address of the target operator and the identifier of the target operator;

[0300] The sending module 903 is further configured to send a second resource creation response message, wherein the second resource creation response message includes at least one of the following: digital resources contracted with the target operator, and the result of the requested resource creation.

[0301] The above-described device is used to execute the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0302] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).

[0303] Optionally, the present invention also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, is used to perform the above-described method embodiments.

[0304] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0305] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0306] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0307] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for receiving media data, characterized in that, Applied to a display terminal, the method includes: Send a first resource creation request message, wherein the first resource creation request message includes: the target operator's contract information and the resource name, and the contract information includes: contract status and contract period; Receive a first resource creation response message, wherein the first resource creation response message includes at least one of the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator; Update the contract period of the target operator based on the actual runtime of the target operator and the first creation resource response message; In response to user login information, a resource retrieval request message is sent, wherein the resource retrieval request message is used to indicate the query of the contract status of the target operator; Receive a resource retrieval response message, and determine whether to receive and play media data sent by the target operator's network based on the resource retrieval response message, wherein the resource retrieval response message includes: contract period and contract status; Before sending the first create resource request message, the method further includes: The operator network currently connected to the display terminal is obtained, wherein the operator network includes at least one of a first operator network, a second operator network, and a third operator network; If it is determined that the network of the operator currently connected to the display terminal is the network of the target operator, a second resource creation request message is sent; the second resource creation request message includes the target operator and authentication information for connecting to the target operator's network; Receive a second resource creation response message, wherein the second resource creation response message is used to indicate the status that the second sub-resource corresponding to the target operator has been successfully created; Based on the second resource creation response message and the authentication information, a connection is established with the target operator's network. If the connection is successful, the first resource creation request message is sent.

2. The method according to claim 1, characterized in that, The step of updating the contract period of the target operator based on the actual runtime of the target operator and the first resource creation response message includes: If the first resource creation response message indicates successful creation, then start a timer to obtain the actual runtime of the target operator; Based on the actual runtime of the target operator obtained by the timer and the first creation resource response message, the contract period of the target operator is updated, wherein the value of the contract period is the difference between the contract period in the first creation resource response message and the actual runtime of the target operator. Send a first updated resource message, which includes: resource name and contract period; Receive a first update resource response message, wherein the first update resource response message includes: update status.

3. The method according to claim 1, characterized in that, The step of determining whether to receive and play media data sent by the target operator's network based on the retrieved resource response message includes: If the target operator's contract status is "signed" and the contract period of the target operator is greater than zero, then the media data sent by the target operator's network will be received and played.

4. The method according to claim 1, characterized in that, The step of responding to user login information and sending a resource retrieval request message includes: In response to user login information, the resource retrieval request message is sent according to the currently connected operator network, wherein the resource retrieval request message includes at least one of the following: operator identifier and subscription status; The system receives the resource retrieval response message and displays a contract period prompt box, wherein the resource retrieval response message includes the contract period and contract status.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: In response to user renewal requests, a contract is signed with the target operator's network based on the network address of the target operator's network; If the contract is successfully signed, a second update resource message is sent. The second update resource message is used to instruct the first sub-resource corresponding to the target operator to be updated. The second update resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period. Receive the second updated resource response message.

6. A method for receiving media data, characterized in that, Applied to a display terminal, the method includes: Receive the first resource creation request message; Based on the received first create resource request message, a first sub-resource of the target operator is created, wherein the first sub-resource includes the following attributes: resource name, contract period of the target operator, and contract status of the target operator; Send a first resource creation response message, wherein the first resource creation response message includes the following: digital resources contracted with the target operator, the result of the requested resource creation, and the contract period of the target operator; Receive a resource retrieval request message, the resource retrieval request message being used to indicate querying the contract status of the target operator; Based on the resource retrieval request message, query the contract status of the target operator and send a resource retrieval response message, which includes the contract status and contract period; The operator network currently connected to the display terminal is obtained, wherein the operator network includes at least one of a first operator network, a second operator network, and a third operator network; Before receiving the first resource creation request message, the method further includes: Receive the second resource creation request message; Based on the received second resource creation request message, a second sub-resource corresponding to the target operator is created, and the following attributes are created for the second sub-resource: the network address of the target operator and the identifier of the target operator; Send a second resource creation response message, wherein the second resource creation response message includes at least one of the following: digital resources contracted with the target operator, and the result of the requested resource creation.

7. The method according to claim 6, characterized in that, The method further includes: Receive the first updated resource message, which includes the resource name and contract period; According to the first updated resource message, update the contract period of the target operator in the first sub-resource; Send a first update resource response message, wherein the first update resource response message includes: update status.

8. The method according to claim 6, characterized in that, in, The first resource creation request message includes: the type of resource to be created, the name of the resource to be created, and the subscription information of the resource to be created; The step of creating the first sub-resource of the target operator according to the received first resource creation request message includes: Based on the resource type, resource name, and contract information of the requested resource, a first sub-resource of the target operator is created, and the following attributes are created for the first sub-resource: the contract status of the target operator, user verification information, digital resource, contract identifier of the target operator, and contract term of the target operator.

9. The method according to claim 8, characterized in that, The first sub-resource also includes: a sub-resource policy, used to instruct the notification object to update the value according to the notification content when the monitored object meets the preset value. The sub-resource policy includes the following attributes: monitoring object identifier, notification object identifier, and notification content.

10. The method according to claim 6, characterized in that, The step of querying the contract status of the target operator based on the resource retrieval request message includes: According to the resource retrieval request message, query whether the operator identifier of the currently connected operator network is consistent with the subscription identifier of the target operator in the first sub-resource, wherein the resource retrieval request message includes the following: operator identifier, subscription status; If so, and the target operator's contract status in the first sub-resource is found to be "signed", then a resource retrieval response message is sent, wherein the resource retrieval response message includes: contract period and contract status.

11. The method according to any one of claims 6-10, characterized in that, The method further includes: Receive the second updated resource message; According to the second updated resource message, the first sub-resource corresponding to the target operator is updated. The second updated resource message includes: the name of the resource to be created, the identifier of the resource to be created, and the contract period. Send a second update resource response message.

12. A display terminal, characterized in that, include: The processor, storage medium, and bus are provided, wherein the storage medium stores machine-readable instructions executable by the processor, and when the display terminal is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the method as described in any one of claims 1-11.

13. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which is executed by a processor to perform the method as described in any one of claims 1-11.

Images