WO2016131250A1 - 资源共享方法、装置及系统 - Google Patents

资源共享方法、装置及系统 Download PDF

Info

Publication number
WO2016131250A1
WO2016131250A1 PCT/CN2015/089637 CN2015089637W WO2016131250A1 WO 2016131250 A1 WO2016131250 A1 WO 2016131250A1 CN 2015089637 W CN2015089637 W CN 2015089637W WO 2016131250 A1 WO2016131250 A1 WO 2016131250A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
receiving end
initiator
core network
resource sharing
Prior art date
Application number
PCT/CN2015/089637
Other languages
English (en)
French (fr)
Inventor
康望星
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016131250A1 publication Critical patent/WO2016131250A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks

Definitions

  • This paper relates to the field of resource sharing technology, and in particular, to a resource sharing method, device and system.
  • RCS ich Communication Suite
  • RCS is a communication service for information, communication and technology integration of the Internet. It is different from the interconnection at the network level, and the three main entrances of the original calls, messages and contacts in the mobile phone are The carrier's level is directly integrated with the handset, turning into new calls, new messages, new contacts, including converged phonebooks, enhanced messaging, enhanced calls and sharing. RCS enhances user experience and work efficiency. It is a human-oriented application-level integration and collaboration, and is also the mainstream development direction of current communication services.
  • the current RCS sharing is mainly through the direct connection of the transmission layer through Bluetooth, WLAN, etc., to complete screen sharing or file transmission, such as projecting the screen content of one terminal onto the screen of the receiving terminal, or transferring files between the two terminals.
  • the main purpose of the present invention is to provide a resource sharing method, device and system to extend the shared resource range of the RCS shared terminal to meet the requirements of sharing resources across devices.
  • a resource sharing method comprising the following steps:
  • the IP multimedia subsystem IMS core network receives the resource sharing request of the initiator
  • the IMS core network sends the sharable resource list of the receiving end to the initiator.
  • the method before the step of the IMS core network receiving the resource sharing request of the initiator, the method further includes:
  • the IMS core network receives and stores the published message sent by the receiving end, where the published message includes a list of sharable resources of the receiving end.
  • the step of determining, by the IMS core network, whether the initiator is authorized to acquire the sharable resource of the receiving end includes:
  • the IMS core network acquires user information of the initiator
  • the IMS core network queries the sharable user list of the receiving end according to the user information of the initiator;
  • the IMS core network determines that the initiator is authorized to acquire the sharable resource of the receiving end; if the sharable user is at the receiving end If the user information of the initiator is not found in the list, the IMS core network determines that the initiator is not authorized to acquire the sharable resource of the receiver.
  • the method further includes:
  • the IMS core network sends the sharable resource list of the receiving end to the originating end; if the receiving end rejects the resource initiated by the originating end If the request is shared, the IMS core network does not respond to the resource sharing request initiated by the initiator.
  • a resource sharing device includes a session module, a determination module, and a sharing module, wherein:
  • the session module is configured to: receive a resource sharing request of the initiator;
  • the determining module is configured to: determine whether the originating end is authorized to acquire the shareable end of the receiving end Resource
  • the sharing module is configured to: if the determining module determines that the originating end is authorized to acquire the sharable resource of the receiving end, send the sharable resource list of the receiving end to the originating end.
  • the session module is further configured to:
  • the determining module is further configured to
  • the user information of the originating end is found in the sharable user list of the receiving end, determining that the originating end is authorized to acquire the sharable resource of the receiving end; if not found in the sharable user list of the receiving end.
  • the user information of the initiator is determined, and it is determined that the initiator is not authorized to acquire the sharable resource of the receiver.
  • the session module is further configured to: if the determining module determines that the initiator is not authorized to acquire the sharable resource of the receiving end, send the resource sharing request initiated by the initiator to the receiving end Notice;
  • the sharing module is further configured to: if the receiving end accepts the resource sharing request initiated by the initiator, send the shareable resource list of the receiving end to the initiator; if the receiving end rejects the initiator The initiated resource sharing request does not respond to the resource sharing request initiated by the initiator.
  • a resource sharing system includes: a core network server and an initiator, wherein:
  • the core network server includes any of the resource sharing devices described above;
  • the initiator is configured to: send a resource sharing request to the core network server, and receive the sharable resource list of the receiving end sent by the core network server when the initiator is authorized to acquire the sharable resource of the receiving end.
  • the resource sharing system further includes a receiving end, where
  • the receiving end is configured to: send an advertisement packet to the core network server, receive a resource sharing request notification initiated by the originating end sent by the core network server, and accept or reject the resource sharing request initiated by the initiator.
  • a computer program comprising program instructions that, when executed by a core network server, cause the core network server to perform any of the resource sharing methods described above.
  • the IMS core network receives the resource sharing request of the originating end, and determines whether the originating end is authorized to acquire the sharable resource of the receiving end, and if the originating end is authorized, sending the receiving end to the originating end A list of shared resources.
  • the IMS core network sends the list of the shareable resources of the receiver to the authorized RCS user initiator, so that The RCS user can obtain various types of software and hardware resources that can be shared by other terminals, thereby expanding the shared resource range of the RCS shared terminal, and satisfying the requirement of sharing resources across devices, and breaking the related art, only screen content can be projected between devices. Limitations of file transfer.
  • FIG. 1 is a schematic flowchart of a first embodiment of a resource sharing method according to the present invention
  • FIG. 2 is a schematic flowchart of a second embodiment of a resource sharing method according to the present invention.
  • FIG. 3 is a schematic flowchart of a third embodiment of a resource sharing method according to the present invention.
  • FIG. 4 is a schematic flowchart of a fourth embodiment of a resource sharing method according to the present invention.
  • FIG. 5 is a schematic diagram of functional modules of a first embodiment of a resource sharing apparatus according to the present invention.
  • FIG. 6 is a schematic diagram of functional modules of a third embodiment of a resource sharing device according to the present invention.
  • FIG. 7 is a schematic structural diagram of a first embodiment of a resource sharing system according to the present invention.
  • FIG. 8 is a schematic structural diagram of a second embodiment of a resource sharing system according to the present invention.
  • the main solution of the embodiment of the present invention is: the IMS core network receives the resource sharing request of the originating end, and determines whether the originating end is authorized to acquire the sharable resource of the receiving end, and if the originating end is authorized to acquire the sharable resource of the receiving end, Sending a list of receiver shareable resources to the initiator.
  • the present invention provides a solution for the RCS user to acquire various software and hardware resources that other terminals can share.
  • a first embodiment of a resource sharing method of the present invention provides a resource sharing method, where the resource sharing method includes the following steps:
  • Step S10 The IP multimedia subsystem IMS core network receives the resource sharing request of the initiator.
  • the RCS user needs to share the hardware and software resources of other terminals, such as: camera, microphone, screen, storage space, various applications, traffic information, and terminals. Performance, can also be other hardware and software resources.
  • the RCS user terminal sends the subscription message to the IMS core network as the initiator, and subscribes to the directly connectable terminal list of the initiator.
  • the IMS core network sends a notification message to the initiator, where the notification message includes a list of directly connectable terminals of the initiator.
  • the initiator After receiving the notification message, the initiator parses the notification message, and obtains the directly connectable terminal list, and presents the terminal to the initiating end user through the UI interface. The initiating end user selects the terminal that wants to share the resource according to the directly connectable terminal list as the receiving end.
  • the originating end sends a shared resource subscription request message to the receiving end to the IMS core network, requesting to share the shared resource of the receiving end, and the IMS core network receives the shared resource subscription request message of the originating end.
  • the message transmission mode may be wireless transmission, local area network transmission, or WLAN straight.
  • Connection and Bluetooth can also be other methods, which can be flexibly set according to actual needs.
  • the RCS terminal and the IMS core network define different message body formats for the subscription message or the notification message for messages with different subscription or notification content.
  • the initiator end presets the Accept field of the directly connectable terminal list subscription message, and sets the preset message body format corresponding to the directly connectable terminal list for the directly connectable terminal list.
  • the initiator presets the Accept field of the shared resource subscription request message, and sets the preset message body format corresponding to the sharable resource list for the sharable resource list.
  • the message body format of the directly connectable terminal list subscription message is a preset message body format corresponding to the directly connectable terminal list
  • the message body format of the directly connectable terminal list notification message is a list of directly connectable terminals.
  • Corresponding preset message body format; the message body format of the shared resource subscription request message is a preset message body format corresponding to the sharable resource list. It should be noted that the message body format can be flexibly set according to actual needs.
  • the IMS core network includes a presence server and a document management server.
  • the presence server receives the subscription message sent by the RCS user terminal, and sends a notification message to the RCS user terminal.
  • the document management server stores a list of directly connected terminals of the originating end and a list of shared users of the receiving end.
  • the presence server subscribes to the message to the document management server. After the subscription is successful, when the shareable user list of the document management server changes, the document management server sends a notification message including the change information to the presence server.
  • the direct connection terminal list of the initiator includes other terminal user information that the initiator can directly connect to;
  • the shareable user list of the receiver includes the user information of the shared resource authorized by the receiver, and is stored in the form of XML (Extensible Markup Language).
  • the RCS user terminal can create, acquire, modify, and delete XML files on the document management server.
  • Step S20 The IMS core network determines whether the originating end is authorized to acquire the sharable resource of the receiving end.
  • the IMS core network presenting server queries the user-shared user list of the receiving end, and searches for the matching end user information in the user information of the sharable user list, and can know whether the originating end is set to receive and receive by the receiving end.
  • the terminal that shares the resource thereby determining whether the initiator is authorized by the receiving end to acquire the sharable resource of the receiving end.
  • Step S30 If the originating end is authorized to acquire the sharable resource of the receiving end, the IMS core network sends the receiving end sharable resource list to the initiating end.
  • the IMS core network presentation server determines that the initiator is authorized to acquire the sharable resource of the receiver, the IMS core network presentation server sends a sharable resource list notification message to the initiator, where the notification message body format is a preset message corresponding to the sharable resource list. Body format.
  • the sharable resource list notification message includes a list of receivable resources that the receiver can share.
  • the initiator receives the sharable resource list notification message, and obtains the shareable resource list of the receiving end.
  • the shareable resource list includes various software and hardware resources, such as: a camera, a microphone, a screen, a storage space, various applications, traffic information, and terminal performance. Can be other hardware and software resources.
  • the initiator obtains various software and hardware resources that can be shared by the receiving end.
  • the originating end issues a resource sharing request; the IMS core network receives the resource sharing request of the originating end, and determines whether the originating end is authorized to acquire the sharable resource of the receiving end; If the initiator is authorized, the sender can send the list of the shareable resources of the receiver to the initiator; the initiator receives the list of the sharable resources, and the RCS user acts as the initiator, and obtains the software and hardware resources that can be shared by other terminals, and expands the RCS sharing terminal.
  • the scope of shared resources meets the requirements of cross-device resource sharing, which breaks the limitation of only screen content projection or file transfer between devices in related technologies.
  • the second embodiment of the resource sharing method of the present invention provides a resource sharing method.
  • the method further includes:
  • Step S40 The IMS core network receives and stores the published message sent by the receiving end, where the published message includes a list of resources that can be shared by the receiving end.
  • the receiving end organizes the software and hardware resources that can be shared by the receiving end, and sends the published message to the IMS core network.
  • the receiving end expands the published message body, so that the published message carries a list of resources that can be shared by the receiving end, and the list of shared resources includes various software and hardware resources that can be shared by the receiving end, such as: camera, microphone, screen, storage space, and various applications. , traffic information and terminal performance, can also be other hardware and software resources.
  • the IMS core network presentation server receives and stores the published message of the receiving end, and parses the published message to obtain a list of the shareable resources of the receiving end.
  • the authorized initiator sends a list of the shareable resources of the receiving end.
  • the RCS user acts as the shared terminal, that is, the receiving end, and actively takes the IMS core.
  • the network publishes a list of sharable resources, and the IMS core network stores a list of sharable resources.
  • the IMS core network may send a list of the shareable resources of the receiver to the authorized initiator, so that the RCS user in need can obtain various software and hardware that can be shared by other terminals.
  • the resource expands the range of shared resources of the RCS shared terminal, satisfies the requirement of sharing resources across devices, and breaks the limitation of only screen content projection or file transfer between devices in related technologies.
  • a third embodiment of the resource sharing method of the present invention provides a resource sharing method, which is based on any of the foregoing embodiments shown in FIG. 1 to FIG. 2 (this embodiment takes FIG. 1 as an example), step S20.
  • step S20 include:
  • Step S21 The IMS core network acquires user information of the initiator.
  • the shared resource subscription request message carries the initiator user information; the IMS core network presentation server obtains the initiator user information according to the received shared resource subscription request message. It should be noted that the message sent by the initiator carries the information of the initiator.
  • the IMS core network presentation server can obtain the information of the initiator according to the shared resource subscription request message sent by the initiator, or can be obtained according to other messages sent by the initiator. Initiating user information.
  • Step S22 The IMS core network queries the receiving end to share the user list according to the information of the originating end user.
  • the IMS core network presentation server queries the user information of the authorized shared resource in the shareable user list on the receiving end, and matches the user information of the authorized shared resource that is the same as the information of the originating end user.
  • Step S23 If the originating end user information is found in the receiving end shareable user list, the IMS core network determines that the initiating end is authorized to acquire the sharable resource of the receiving end; if the receiving end is shareable The originating end user information is not found in the user list, and the IMS core network determines that the originating end is not authorized to acquire the sharable resource of the receiving end.
  • the IMS core network presentation server determines that the initiator is authorized to acquire the shareable resource of the receiving end.
  • the IMS core network presentation server determines that the originating end is not authorized to acquire the shareable end of the receiving end. Resources.
  • the IMS core network determines whether the originating end is authorized to acquire the sharable resource of the receiving end according to the initiating end user information and the shareable user list of the receiving end, and the IMS core network is authorized.
  • the originating end sends the sharable user list of the receiving end, realizes the rights management of the resource sharing, and prevents the shared resources of the receiving end from being used by the unauthorized originating end, thereby ensuring the security of resource sharing.
  • the fourth embodiment of the resource sharing method of the present invention provides a resource sharing method, which is based on any of the foregoing embodiments shown in FIG. 1 to FIG. 2 (this embodiment takes FIG. 1 as an example), step S20. It also includes:
  • Step S50 If the initiator is not authorized to acquire the sharable resource of the receiver, the IMS core network sends a resource sharing request notification of the initiator to the receiver.
  • the receiving end After the RCS is started, the receiving end sends a subscription message to the IMS core network, and subscribes to the user information that initiates sharing of the terminal resource.
  • the message body format of the subscription message is a preset message body format corresponding to the user information that initiates sharing of the terminal resource.
  • the IMS core network presentation server determines that the initiator is authorized to acquire the sharable resource of the receiver, and the initiator does not currently have the right to acquire the sharable resource of the receiver, the IMS core network presentation server sends a notification message to the receiver, where the notification message includes the user of the initiator.
  • the information and resource sharing request notifies the receiving end that the originating end requests to share its resources.
  • the message body format of the notification message is a preset message body format corresponding to the user information that initiates the sharing of the receiving end resource.
  • the receiving end After receiving the notification message about the initiating end user information and the resource sharing request sent by the IMS core network city rendering server, the receiving end parses the notification message, and obtains the initiating end user information and the resource sharing request, and presents the request to the receiving end user through the UI interface. The user determines whether to accept the resource sharing request of the initiator.
  • Step S60 If the receiving end accepts the resource sharing request of the initiator, the step is: the IMS core network sends a list of the shareable resources of the receiver to the initiator; if the receiver rejects the The resource sharing request of the initiator, the IMS core network does not respond to the resource sharing request of the initiator.
  • the receiving end sends a request message to the IMS core network, and the receiving end can share the user list information in the IMS core network document management server, and join the initiating end in the shareable user list of the receiving end.
  • User Info After the IMS core network document management server learns the modification of the shareable user list, the IMS core network presentation server sends a notification message to the IMS core network presentation server to obtain the modified receiver shareable user list.
  • the IMS core network presentation server After receiving the notification message, the IMS core network presentation server obtains the modified user-shared user list, and finds the originating user information in the modified user-shared user list, and determines that the initiator is authorized to obtain the receiver.
  • the shared resource list is forwarded to step S30, and the IMS core network presentation server sends the receiving end shareable resource list to the initiator.
  • the receiving end user rejects the resource sharing request of the originating end, the receiving end does not perform any processing on the resource sharing request of the originating end, and the IMS core network rendering server does not respond to the resource sharing request of the initiating end.
  • the IMS core network when the originating end initiates the resource sharing request to the receiving end, if the receiving end accepts the resource sharing request of the initiating end and authorizes the initiating end, the IMS core network sends the authorized originating end.
  • the receiving end may share the resource list; if the receiving end rejects the resource sharing request of the originating end, the IMS core network does not respond to the resource sharing request of the initiating end.
  • the resource sharing permission of the initiator is managed by the receiving end, and the resource sharing right of the RCS terminal is flexibly grasped, so that the resource sharing is established on the basis of the authorization of the receiving end, and the originating end arbitrarily occupies the shareable software and hardware resources of the receiving end, and the demand is better.
  • the RCS users provide shared hardware and software resources; they also extend the shared resource range of the RCS shared terminal, which satisfies the requirements of cross-device resource sharing, and breaks the limitation of only screen content projection or file transfer between devices in related technologies. .
  • a first embodiment of the resource sharing apparatus of the present invention provides a resource sharing apparatus, where the resource sharing apparatus includes:
  • the session module 100 is configured to: receive a resource sharing request of the initiator.
  • the RCS user terminal sends the subscription message to the session module 100 as the initiator, and subscribes to the directly connectable terminal list of the initiator.
  • the session module 100 sends a notification message to the initiator, where the notification message includes a list of directly connectable terminals of the initiator.
  • the initiator After receiving the notification message, the initiator parses the notification message, and obtains the directly connectable terminal list, and presents the terminal to the initiating end user through the UI interface. The initiating end user selects the terminal that wants to share the resource according to the directly connectable terminal list as the receiving end. The initiator sends a shared resource subscription request message to the receiving end to the session module 100 to subscribe to the shared resource of the receiving end, and the session module 100 receives the shared resource subscription request message of the originating end.
  • the message transmission mode may be wireless transmission, local area network transmission, WLAN direct connection and Bluetooth, or other methods, which can be flexibly set according to actual needs.
  • the determining module 200 is configured to: determine whether the originating end is authorized to acquire the sharable resource of the receiving end.
  • the determining module 200 queries the receiving end to share the user list, and searches for the matching initiating user information in the user information of the shareable user list, and can learn whether the originating end is set by the receiving end to obtain the receiving end sharing.
  • the terminal of the resource so that the determining module 200 determines whether the originating end is authorized by the receiving end to acquire the sharable resource of the receiving end.
  • the sharing module 300 is configured to: if the originating end is authorized to acquire the sharable resource of the receiving end, send the receiving end shareable resource list to the initiating end.
  • the sharing module 300 sends a sharable resource list notification message to the initiator, where the notification message body format is a preset message body format corresponding to the sharable resource list.
  • the sharable resource list notification message includes a list of receivable resources that the receiver can share.
  • the initiator receives the sharable resource list notification message, and obtains the shareable resource list of the receiving end.
  • the shareable resource list includes various software and hardware resources, such as: a camera, a microphone, a screen, a storage space, various applications, traffic information, and terminal performance. Can be other hardware and software resources.
  • the initiator obtains various software and hardware resources that can be shared by the receiving end.
  • the resource sharing request is sent as the initiator; the session module 100 receives the resource sharing request of the initiator, and the determining module 200 determines whether the initiator is authorized to acquire the receiver. If the originating end is authorized, the sharing module 300 sends the receiving end sharable resource list to the originating end; the originating end receives the sharable resource list, and the RCS user acts as the originating end, and realizes acquiring various software and hardware resources that the other terminal can share.
  • the RCS shared terminal shared resource range is extended to meet the requirements of cross-device resource sharing, which breaks the limitation of only screen content projection or file transmission between devices in related technologies.
  • the second embodiment of the resource sharing device of the present invention provides a resource sharing device.
  • the session module 100 is further configured to
  • the receiving end organizes the software and hardware resources that can be shared by the receiving end, and sends the published message to the session module 100.
  • the receiving end expands the published message body, so that the published message carries a list of resources that can be shared by the receiving end, and the list of shared resources includes various software and hardware resources that can be shared by the receiving end, such as: camera, microphone, screen, storage space, and various applications. , traffic information and terminal performance, can also be other hardware and software resources.
  • the session module 100 receives and stores the published message of the receiving end, and parses the published message to obtain a list of the shareable resources of the receiving end.
  • the sharing module 300 sends the receiving end shareable resource list to the authorized originating end.
  • the RCS user actively publishes the sharable resource list as the shared terminal, that is, the receiving end, and the session module 100 stores the sharable resource list.
  • the sharing module 300 can send the list of the shareable resources of the receiver to the authorized initiator, so that the RCS user in need can obtain the software and hardware that can be shared by other terminals. Resources also expand the range of shared resources of RCS shared terminals, satisfying the need for cross-device resource sharing, and breaking the limitations of only relevant screen content projection or file transfer between devices in related technologies.
  • the third embodiment of the resource sharing apparatus of the present invention provides a total resource
  • the determining module 200 includes: based on the embodiment shown in FIG. 5 above, the determining module 200 includes:
  • the obtaining unit 210 is configured to: obtain the originating end user information.
  • the shared resource subscription request message sent carries the initiating end user information; the session module 100 receives the shared resource subscription request message; the obtaining unit 210 obtains the initiating end user information according to the shared resource subscription request message. .
  • the querying unit 220 is configured to: according to the information of the originating end user, query the receiving end to share the user list.
  • the querying unit 220 queries the user information of the authorized shared resource in the shareable user list of the receiving end, and matches the user information of the authorized shared resource that is the same as the information of the originating end user.
  • the determining unit 230 is configured to: if the originating user information is found in the shareable user list in the receiving end, determine that the originating end is authorized to acquire the sharable resource of the receiving end; if the receiving end can share the user If the originating end user information is not found in the list, it is determined that the originating end is not authorized to acquire the sharable resource of the receiving end.
  • the determining unit 230 determines that the originating end is authorized to acquire the sharable resource of the receiving end.
  • the determining unit 230 determines that the originating end is not authorized to acquire the sharable resource of the receiving end.
  • the determining unit 230 determines whether the originating end is authorized to acquire the sharable resource of the receiving end, and the sharing module 300 is authorized according to the initiating end user information and the receiving end shareable user list.
  • the originating end sends the sharable user list of the receiving end, realizes the rights management of the resource sharing, and prevents the shared resources of the receiving end from being used by the unauthorized originating end, thereby ensuring the security of resource sharing.
  • the fourth embodiment of the resource sharing device of the present invention provides a resource sharing device.
  • the session module 100 is further configured to
  • the source sharing request notification of the initiator is sent to the receiver.
  • the receiving end After the RCS is started, the receiving end sends a subscription message to the IMS core network, and subscribes to the user information that initiates sharing of the terminal resource.
  • the message body format of the subscription message is a preset message body format corresponding to the user information that initiates sharing of the terminal resource.
  • the session module 100 sends a notification message to the receiving end, where the notification message includes the user information and the resource sharing request of the initiating end.
  • the notification receiving end has an originating request to share its resources.
  • the message body format of the notification message is a preset message body format corresponding to the user information for initiating sharing of the terminal resource.
  • the receiving end After receiving the notification message about the originating end user information and the resource sharing request sent by the session module 100, the receiving end parses the notification message, and obtains the initiating end user information and the resource sharing request, and presents the information to the receiving end user through the UI interface, and the user determines whether the user Accept the resource sharing request from the initiator.
  • the sharing module 300 is further configured to: if the receiving end accepts the resource sharing request of the originating end, send the receiving end shareable resource list to the initiating end; if the receiving end rejects the resource sharing request of the initiating end, the receiving end does not respond The resource sharing request of the initiator.
  • the receiving end sends a request message to the session module 100, and the modified receiving end can share the user list information, and the initiating end user information is added to the shareable user list in the receiving end.
  • the determining module 200 obtains the modified user-shared user list, and finds the originating user information in the modified user-shared user list, and determines that the originating end is authorized to obtain the receiving end-shareable resource list, and the sharing module 300
  • the initiator sends a list of resources that the receiver can share.
  • the receiving end user rejects the resource sharing request of the initiating end, the receiving end does not perform any processing on the resource sharing request of the initiating end, and the sharing module 300 does not respond to the resource sharing request of the initiating end.
  • the originating end is not authorized to acquire the sharable resource of the receiving end, and after the session module 100 sends the resource sharing request notification of the originating end to the receiving end, if the receiving end accepts the resource sharing request of the originating end and authorizes the originating end, The sharing module 300 sends the connection to the authorized initiator.
  • the receiving end can share the resource list; if the receiving end rejects the resource sharing request of the originating end, the sharing module 300 does not respond to the resource sharing request of the originating end.
  • the resource sharing permission of the initiator is managed by the receiving end, and the resource sharing right of the RCS terminal is flexibly grasped, so that the resource sharing is established on the basis of the authorization of the receiving end, and the originating end arbitrarily occupies the shareable software and hardware resources of the receiving end, and the demand is better.
  • the RCS users provide shared hardware and software resources, and also expand the shared resource range of the RCS shared terminal, which satisfies the requirements of cross-device resource sharing, and breaks the limitation of only screen content projection or file transfer between devices in related technologies. .
  • a first embodiment of the resource sharing system of the present invention provides a resource sharing system, where the resource sharing system includes: a core network server A and an initiator B, wherein:
  • the core network server A includes a session module 100, a decision module 200, and a sharing module 300.
  • the core network server A receives and processes the received message, and sends a message to the originating end B for signaling processing.
  • the session module 100 receives the resource sharing request of the initiator; the determining module 200 determines whether the initiator B is authorized to acquire the sharable resource of the receiver; if the initiator B is authorized to acquire the sharable resource of the receiver, the sharing module 300 sends the receiver to the initiator B.
  • a list of sharable resources A list of sharable resources.
  • the initiator B is configured to: send a resource sharing request to the core network server, and receive the shareable resource that is sent by the core network server when the initiator is authorized to acquire the sharable resource of the receiving end List.
  • the originating end B includes a direct connection management module B1, a resource sharing management module B2, a session management module B3, and a resource sharing application module B4.
  • the direct connection management module B1 and the resource sharing management module B2 send a subscription message to the core network server A through the session management module B3; the session management module B3 processes the information acquired from the direct connection management module B1 and the resource sharing management module B2 as a subscription message.
  • the subscription message body format is a preset message body format corresponding to the subscription message content.
  • the direct connection management module B1 sends a directly connectable terminal list subscription message to the core network server A through the session management module B3; the session management module B3 receives the directly connectable terminal list notification message. After the direct connection terminal list notification message is parsed, the directly connectable terminal list is obtained, and the session management module B3 sends the obtained directly connectable terminal list to the direct connection management.
  • the module B1; the direct connection management module B1 obtains the list of directly connectable terminals, and notifies the resource sharing application module B4; the resource sharing application module B4 presents the list of directly connectable terminals to the terminal user through the UI interface, and the terminal user according to the list of directly connectable terminals
  • the terminal that wants to share the resource is selected as the receiving end; when the user selects the receiving end, the resource sharing application module B4 notifies the direct connection management module B1; the direct connection management module B1 acquires the receiving end user information.
  • the message body format of the directly connectable terminal list subscription message is a preset message body format corresponding to the directly connectable terminal list.
  • the direct connection management module B1 sends the selected receiving end information to the resource sharing management module B2; the resource sharing management module B2 sends a shared resource subscription request message to the receiving end to the core network server A through the session management module B3. , request to share the shared resources of the receiving end.
  • the message body format of the shared resource subscription request message is a preset message body format corresponding to the sharable resource list.
  • the session management module B3 receives the sharable resource list notification message, parses the sharable resource list notification message, and obtains the list of the shareable resources that the receiver can share;
  • the management module B3 sends the receiving end sharable resource list to the resource sharing management module B2; the resource sharing management module B2 acquires the shareable software and hardware resources of the receiving end.
  • the initiating end B sends a resource sharing request to the core network server A, and the core network server A determines whether the initiating end B is authorized to acquire the sharable resource of the receiving end, and the originating end B is authorized to acquire the receiving end.
  • the resources can be shared, and the core network server A sends the list of sharable resources of the receiving end to the originating end B.
  • the initiator B receives the sharable resource list sent by the core network server A, and the initiator B acquires the sharable resources of the receiver, expands the shared resource range of the RCS shared terminal, and satisfies the requirement of sharing resources across devices, and breaks the related technology.
  • the third embodiment of the resource sharing system of the present invention provides a resource sharing system.
  • the resource sharing system further includes a receiving end C:
  • the receiving end C is configured to: send an advertisement packet to the core network server, receive the initiator resource sharing request notification sent by the core network server, and accept or reject the initiator. Resource sharing request.
  • the receiving end C includes a resource sharing management module C1, an XCAP module C2, a session management module C3, and a resource sharing application module C4.
  • the resource sharing management module C1 sends the advertisement message and the subscription message to the core network server A through the session management module C3.
  • the session management module C3 processes the information acquired from the resource sharing management module C1 into an advertisement message or a subscription message, and publishes the message and
  • the subscription message body format is a preset message body format corresponding to the content.
  • the resource sharing management module C1 organizes the shareable software and hardware resources of the receiving end C, sends the published message to the core network server A through the session management module C3, and the session management module C3 expands and publishes the message body.
  • the published message carries a list of sharable resources of the receiving end C.
  • the list of sharable resources includes various software and hardware resources that the receiving end can share, such as: camera, microphone, screen, storage space, various applications, traffic information, and terminal performance. Can be other hardware and software resources.
  • the resource sharing management module C1 sends a subscription message to the core network server A through the session management module C3, and subscribes to the user information for sharing the resource of the terminal.
  • the message body format of the subscription message is a preset message corresponding to the user information for initiating sharing of the terminal resource. Body format.
  • the session management module C3 After receiving the notification message about the originating end user information and the resource sharing request sent by the core network server A, the session management module C3 parses the notification message to obtain the initiating end user information and the resource sharing request; the session management module C3 sends the initiating end user information and The resource sharing management module sends the resource sharing request to the resource sharing management module C1.
  • the resource sharing management module C1 obtains the initiating user information and the resource sharing request information, and notifies the resource sharing application module C4.
  • the resource sharing application module C4 passes the initiating user information and the resource sharing request through the UI.
  • the interface is presented to the receiving end user, and the user determines whether to accept the resource sharing request of the initiator, and feeds the user judgment result to the resource sharing management module C1.
  • the resource sharing management module C1 sends a notification message to the XCAP (The XML Configuration Access Protocol) module C2 that the user accepts the resource sharing request of the initiator;
  • the XCAP module C2 sends the core network server A Sending a join request message, modifying the shareable user list information of the receiving end C, and adding the initiating end user information to the shareable user list of the receiving end C;
  • the core network server A determines that the initiating end B is authorized to acquire the shareable resources of the receiving end, and initiates End B sends a list of resources that the receiver can share.
  • the resource sharing management module C1 does not respond to the initiator.
  • the resource sharing request, the XCAP module C2 does not respond to the initiator resource sharing request, and the core network server A does not respond to the initiator resource sharing request, and does not perform any processing on the resource sharing request of the initiator; the initiator B does not receive the preset time.
  • the default receiving end B rejects the resource sharing request of the originating end B. or,
  • the resource sharing management module C1 sends a notification message to the XCAP module C2 that the user accepts the resource sharing request of the initiator; the XCAP module C2 sends a join request message to the core network server A to modify the shareable of the receiving end C.
  • the user list information is added to the initiator user information in the non-shareable user list at the receiving end C; the core network server A sends a reject shared resource notification message to the initiator B.
  • the receiving end C sends an advertisement message to the core network server A, and advertises the list of resources that can be shared by the receiving end. If the originating end B is not authorized to acquire the resource shareable by the receiving end, the core network server A notifies the receiving end C.
  • the source B request of the originating end B is judged; if the receiving end C accepts the resource sharing request of the initiating end B, the core network server A sends the list of the shareable resources of the receiving end to the initiating end B, and the initiating end B acquires the shareable of the receiving end C
  • the resource list enables the RCS users to obtain various software and hardware resources that other terminals can share, and expands the shared resource range of the RCS shared terminal, which satisfies the requirement of sharing resources across devices, and breaks the screen content between the devices in the related art. Limitations of projection or file transfer.
  • the embodiment of the invention further discloses a computer program, comprising program instructions, when the program instruction is executed by the core network server, so that the core network server can execute any of the foregoing resource sharing methods.
  • the embodiment of the invention also discloses a carrier carrying the computer program.
  • the IMS core network receives the resource sharing request of the originating end, and determines whether the originating end is authorized to acquire the sharable resource of the receiving end, and if the originating end is authorized, sending the receiving end to the originating end A list of shared resources.
  • the IMS core network sends the list of the shareable resources of the receiver to the authorized RCS user initiator, so that The RCS user can obtain various types of software and hardware resources that can be shared by other terminals, thereby expanding the shared resource range of the RCS shared terminal, and satisfying the requirement of sharing resources across devices, and breaking the related art, only screen content can be projected between devices. Limitations of file transfer. Therefore, the present invention has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种资源共享方法、装置及系统，其方法包括：IP多媒体子系统IMS核心网接收发起端的资源共享请求；判断发起端是否被授权获取接收端的可共享资源；若发起端被授权获取接收端的可共享资源，则向发起端发送接收端可共享资源列表。该技术方案扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。

Description

资源共享方法、装置及系统 技术领域
本文涉及资源共享技术领域，尤其涉及一种资源共享方法、装置及系统。
背景技术
RCS(Rich Communication Suite，融合通信业务)是面向互联网的信息、通信和技术融合的通信业务，区别于网络层面的互联互通，把手机中原有的通话、消息、联系人这三个主要入口，从运营商的层面直接与手机整合，变为新通话、新消息、新联系，包括融合电话薄、增强消息、增强呼叫和共享等。RCS提升了用户的体验与工作效率，是以人为本的应用层面融合与协同，也是当前通信业务的主流发展方向。
当前RCS共享主要是在传输层通过蓝牙、WLAN等方式直连，完成屏幕共享或文件传输，如将一个终端的屏幕内容投射到接收终端的屏幕上，或两个终端之间进行文件的传输。
由于跨设备的资源共享更为快捷便利，使得跨设备资源共享的需求越来越多，然而RCS共享终端之间可共享的资源内容少，屏幕共享以及文件传输已不能满足用户的需求。当用户需使用其他终端可共享的软件应用，或需使用其他终端可共享的硬件设备如闪光灯、音箱等时，当前RCS用户无法获取其他终端可共享的软件资源或其他硬件资源，导致当前RCS不能共享其他终端可共享的各软硬件资源，因此，如何使RCS用户获取其他终端可共享的各种软硬件资源是首先需要解决的问题。
发明内容
本发明的主要目的在于提供一种资源共享方法、装置及系统，以扩展RCS共享终端共享资源范围，满足跨设备资源共享的需求。
为实现上述目的，采用如下技术方案：
一种资源共享方法，所述资源共享方法包括以下步骤：
IP多媒体子系统IMS核心网接收发起端的资源共享请求；
所述IMS核心网判断所述发起端是否被授权获取接收端的可共享资源；
若所述发起端被授权获取所述接收端的可共享资源，则所述IMS核心网向所述发起端发送所述接收端的可共享资源列表。
可选地，所述IMS核心网接收发起端的资源共享请求的步骤之前，该方法还包括：
所述IMS核心网接收并存储所述接收端发送的公布报文，所述公布报文包括所述接收端的可共享资源列表。
可选地，所述IMS核心网判断所述发起端是否被授权获取所述接收端的可共享资源的步骤包括：
所述IMS核心网获取所述发起端的用户信息；
根据所述发起端的用户信息，所述IMS核心网查询所述接收端的可共享用户列表；
若在所述接收端的可共享用户列表中找到所述发起端的用户信息，则所述IMS核心网判定所述发起端被授权获取所述接收端的可共享资源；若在所述接收端的可共享用户列表中未找到所述发起端的用户信息，则所述IMS核心网判定所述发起端未被授权获取所述接收端的可共享资源。
可选地，所述IMS核心网判断所述发起端是否被授权获取所述接收端的可共享资源的步骤之后，该方法还包括：
若所述发起端未被授权获取所述接收端的可共享资源，则所述IMS核心网向所述接收端发送所述发起端发起的资源共享请求通知；
若所述接收端接受所述发起端发起的资源共享请求，则所述IMS核心网向所述发起端发送所述接收端的可共享资源列表；若所述接收端拒绝所述发起端发起的资源共享请求，则所述IMS核心网不响应所述发起端发起的资源共享请求。
一种资源共享装置，所述资源共享装置包括会话模块、判定模块和共享模块，其中：
所述会话模块设置成：接收发起端的资源共享请求；
所述判定模块设置成：判断所述发起端是否被授权获取接收端的可共享 资源；
所述共享模块设置成：若所述判定模块判定所述发起端被授权获取所述接收端的可共享资源，则向所述发起端发送所述接收端的可共享资源列表。
可选地，所述会话模块还设置成：
接收并存储所述接收端发送的公布报文，所述公布报文包括所述接收端的可共享资源列表。
可选地，所述判定模块还设置成
获取所述发起端的用户信息；
根据所述发起端的用户信息，查询所述接收端的可共享用户列表；
若在所述接收端的可共享用户列表中找到所述发起端的用户信息，则判定所述发起端被授权获取所述接收端的可共享资源；若在所述接收端的可共享用户列表中未找到所述发起端的用户信息，则判定所述发起端未被授权获取所述接收端的可共享资源。
可选地，所述会话模块还设置成：若所述判定模块判定所述发起端未被授权获取所述接收端的可共享资源，则向所述接收端发送所述发起端发起的资源共享请求通知；
所述共享模块还设置成：若所述接收端接受所述发起端发起的资源共享请求，则向所述发起端发送所述接收端的可共享资源列表；若所述接收端拒绝所述发起端发起的资源共享请求，则不响应所述发起端发起的资源共享请求。
一种资源共享系统，包括：核心网服务器和发起端，其中：
所述核心网服务器包括上述任意的资源共享装置；
所述发起端设置成：向所述核心网服务器发送资源共享请求，在所述发起端被授权获取接收端的可共享资源时，接收所述核心网服务器发送的所述接收端的可共享资源列表。
可选地，所述资源共享系统还包括接收端，其中
所述接收端设置成：向所述核心网服务器发送公布报文，接收所述核心网服务器发送的所述发起端发起的资源共享请求通知，接受或拒绝所述发起端发起的资源共享请求。
一种计算机程序，包括程序指令，当该程序指令被核心网服务器执行时，使得该核心网服务器可执行上述任意的资源共享方法。
一种载有所述的计算机程序的载体。
本发明技术方案的资源共享方法、装置和系统，IMS核心网接收发起端的资源共享请求，判断发起端是否被授权获取接收端的可共享资源，若发起端被授权，则向发起端发送接收端可共享资源列表。在本发明技术方案中，RCS用户需共享其他终端可共享的软硬件资源时，根据RCS用户发起端的资源共享请求，IMS核心网向被授权的RCS用户发起端发送接收端可共享资源列表，使得RCS用户能够获取其他终端可共享的各类软硬件资源，从而扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
附图概述
图1为本发明资源共享方法第一实施例的流程示意图；
图2为本发明资源共享方法第二实施例的流程示意图；
图3为本发明资源共享方法第三实施例的流程示意图；
图4为本发明资源共享方法第四实施例的流程示意图；
图5为本发明资源共享装置第一实施例的功能模块示意图；
图6为本发明资源共享装置第三实施例的功能模块示意图；
图7为本发明资源共享系统第一实施例的结构示意图；
图8为本发明资源共享系统第二实施例的结构示意图。
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
本发明的较佳实施方式
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
应当理解，此处所描述的具体实施例仅用以解释本发明，并不用于限定本发明。
本发明实施例的主要解决方案是：IMS核心网接收发起端的资源共享请求，判断所述发起端是否被授权获取接收端的可共享资源，若所述发起端被授权获取接收端的可共享资源，则向所述发起端发送接收端可共享资源列表。
由于相关技术RCS共享终端之间可共享的资源内容少，屏幕共享以及文件传输已不能满足用户的需求，RCS用户无法获取其他终端可共享的软件资源或其他硬件资源。
本发明提供一种解决方案，实现RCS用户获取其他终端可共享的各软硬件资源。
参照图1，本发明资源共享方法第一实施例提供一种资源共享方法，所述资源共享方法包括以下步骤：
步骤S10、IP多媒体子系统IMS核心网接收发起端的资源共享请求。
RCS用户在终端使用过程中，由于本机缺乏某个或多个软件资源时，需共享其他终端的各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。此时RCS用户终端作为发起端向IMS核心网发送订阅消息，订阅发起端的可直连终端列表。订阅成功后，IMS核心网向发起端发送通知消息，通知消息中包括发起端的可直连终端列表。
发起端收到通知消息后，解析通知消息，获取可直连终端列表，并通过UI界面呈现给发起端用户，由发起端用户根据可直连终端列表选择想要共享资源的终端作为接收端，发起端向IMS核心网发出针对接收端的共享资源订阅请求消息，请求共享接收端的共享资源，IMS核心网接收发起端的共享资源订阅请求消息。
需要说明的是，消息传输方式可以是无线传输、局域网传输、WLAN直 连和蓝牙，也可以是其他方式，可根据实际需要灵活设定。
RCS终端和IMS核心网针对订阅或通知内容不同的消息，对订阅消息或通知消息定义不同的消息体格式。如：发起端对可直连终端列表订阅消息的Accept字段进行预设的扩展，针对可直连终端列表，设置为与可直连终端列表对应的预设消息体格式。发起端对共享资源订阅请求消息的Accept字段进行预设的扩展，针对可共享资源列表，设置为与可共享资源列表对应的预设消息体格式。在本实施例中，可直连终端列表订阅消息的消息体格式是与可直连终端列表对应的预设消息体格式，可直连终端列表通知消息的消息体格式是与可直连终端列表对应的预设消息体格式；共享资源订阅请求消息的消息体格式是与可共享资源列表对应的预设消息体格式。需要说明的是，消息体格式可根据实际需要灵活设定。
IMS核心网包括呈现服务器和文档管理服务器。呈现服务器接收RCS用户终端发送的订阅消息，发送通知消息给RCS用户终端。文档管理服务器存储有发起端的直连终端列表和接收端可共享用户列表。呈现服务器向文档管理服务器订阅消息，订阅成功后，当文档管理服务器的接收端可共享用户列表发生变化时，文档管理服务器向呈现服务器发送包括变化信息的通知消息。
发起端的直连终端列表包括发起端可直连的其他终端用户信息；接收端的可共享用户列表包括接收端授权共享资源的用户信息，以XML(Extensible Markup Language，可扩展标记语言)的形式存放，RCS用户终端可以对文档管理服务器上的XML文件进行创建、获取、修改和删除的操作。
步骤S20、所述IMS核心网判断所述发起端是否被授权获取接收端的可共享资源。
根据获取的发起端用户信息，IMS核心网呈现服务器查询接收端可共享用户列表，在可共享用户列表的用户信息中查找匹配发起端用户信息，可获知发起端是否被接收端设置为可以获取接收端共享资源的终端，从而判定发起端是否被接收端授权获取接收端的可共享资源。
步骤S30、若所述发起端被授权获取接收端的可共享资源，则所述IMS核心网向所述发起端发送接收端可共享资源列表。
若IMS核心网呈现服务器判定发起端被授权获取接收端的可共享资源，则IMS核心网呈现服务器向发起端发送可共享资源列表通知消息，通知消息体格式是与可共享资源列表对应的预设消息体格式。可共享资源列表通知消息包括接收端可共享资源列表。发起端接收可共享资源列表通知消息，获取接收端可共享资源列表，可共享资源列表包括各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。实现了发起端获取接收端可共享的各软硬件资源。
在本实施例中，当RCS用户需共享其他终端的软硬件资源时，作为发起端发出资源共享请求；IMS核心网接收发起端的资源共享请求，判断发起端是否被授权获取接收端的可共享资源；若发起端被授权，则向发起端发送接收端可共享资源列表；发起端接收可共享资源列表，RCS用户作为发起端，实现了获取其他终端可共享的各软硬件资源，扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
进一步的，参照图2，本发明资源共享方法第二实施例提供一种资源共享方法，基于上述图1所示的实施例，在步骤S10之前，还包括：
步骤S40、IMS核心网接收并存储接收端发送的公布报文，所述公布报文包括接收端可共享资源列表。
接收端在RCS启动后，整理接收端可共享的各软硬件资源，向IMS核心网发送公布报文。接收端扩展公布报文消息体，使公布报文携带接收端可共享资源列表，可共享资源列表包括接收端可共享的各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。
IMS核心网呈现服务器接收并存储接收端的公布报文，解析公布报文获取接收端可共享资源列表。当RCS用户需共享接收端的各软硬件资源时，向被授权的发起端发送接收端可共享资源列表。
在本实施例中，RCS用户作为被共享终端，即接收端，主动向IMS核心 网发布可共享资源列表，IMS核心网存储可共享资源列表。当有需求的RCS用户向IMS核心网发送共享资源请求时，IMS核心网可以向被授权的发起端发送接收端可共享资源列表，从而实现有需求的RCS用户获取其他终端可共享的各软硬件资源，扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
进一步的，参照图3，本发明资源共享方法第三实施例提供一种资源共享方法，基于上述图1至图2中所示任一实施例(本实施例以图1为例)，步骤S20包括：
步骤S21、所述IMS核心网获取发起端用户信息。
发起端向MS核心网发送资源共享请求时，发送的共享资源订阅请求消息中携带发起端用户信息；IMS核心网呈现服务器根据收到的共享资源订阅请求消息，获取发起端用户信息。需要说明的是，发起端发送的消息均携带有发起端用户信息，IMS核心网呈现服务器可根据发起端发送的共享资源订阅请求消息获取发起端用户信息，也可以根据发起端发送的其他消息获取发起端用户信息。
步骤S22、根据所述发起端用户信息，所述IMS核心网查询接收端可共享用户列表。
IMS核心网呈现服务器在接收端可共享用户列表中查询被授权共享资源的用户信息，匹配与发起端用户信息相同的被授权共享资源的用户信息。
步骤S23、若在所述接收端可共享用户列表中找到所述发起端用户信息，则所述IMS核心网判定所述发起端被授权获取接收端的可共享资源；若在所述接收端可共享用户列表中未找到所述发起端用户信息，则所述IMS核心网判定所述发起端未被授权获取接收端的可共享资源。
若IMS核心网呈现服务器在接收端可共享用户列表的被授权共享资源的用户信息中，成功匹配发起端用户信息，则IMS核心网呈现服务器判定所述发起端被授权获取接收端的可共享资源。
若IMS核心网呈现服务器在接收端可共享用户列表的被授权共享资源的用户信息中，未成功匹配发起端用户信息，则IMS核心网呈现服务器判定所述发起端未被授权获取接收端的可共享资源。
在本实施例中，在发起端发送资源共享请求后，IMS核心网根据发起端用户信息和接收端可共享用户列表，判断发起端是否被授权获取接收端的可共享资源，IMS核心网向被授权的发起端发送接收端的可共享用户列表，实现了资源共享的权鉴管理，避免接收端的共享资源被未授权的发起端使用，保证了资源共享的安全性。
进一步的，参照图4，本发明资源共享方法第四实施例提供一种资源共享方法，基于上述图1至图2中所示任一实施例(本实施例以图1为例)，步骤S20之后还包括：
步骤S50、若所述发起端未被授权获取接收端的可共享资源，则所述IMS核心网向接收端发送发起端的资源共享请求通知。
接收端在RCS启动后，向IMS核心网发送订阅消息，订阅发起共享本终端资源的用户信息。订阅消息的消息体格式是与发起共享本终端资源的用户信息对应的预设消息体格式。
若IMS核心网呈现服务器判定发起端被授权获取接收端的可共享资源，发起端当前无权获取接收端的可共享资源，则IMS核心网城呈现服务器向接收端发送通知消息，通知消息包括发起端的用户信息和资源共享请求，通知接收端有发起端请求共享其资源。通知消息的消息体格式是与发起共享接收端资源的用户信息对应的预设消息体格式。
接收端接收到IMS核心网城呈现服务器发送的关于发起端用户信息和资源共享请求的通知消息后，解析通知消息，获取发起端用户信息和资源共享请求，通过UI界面呈现给接收端用户，由用户判断是否接受发起端的资源共享请求。
步骤S60、若接收端接受所述发起端的资源共享请求，则执行步骤：所述IMS核心网向所述发起端发送接收端可共享资源列表；若接收端拒绝所述 发起端的资源共享请求，则所述IMS核心网不响应所述发起端的资源共享请求。
若接收端用户接受发起端的资源共享请求，则接收端发送向IMS核心网加入请求消息，修改IMS核心网文档管理服务器中接收端可共享用户列表信息，在接收端可共享用户列表中加入发起端用户信息。IMS核心网文档管理服务器获知接收端可共享用户列表的修改后，向IMS核心网呈现服务器发送通知消息，通知IMS核心网呈现服务器获取修改后的接收端可共享用户列表。
IMS核心网呈现服务器接收到通知消息后，获取修改后的接收端可共享用户列表，在修改后的接收端可共享用户列表中找到所述发起端用户信息，判定发起端被授权获取接收端可共享资源列表，转入步骤S30，IMS核心网呈现服务器向发起端发送接收端可共享资源列表。
若接收端用户拒绝发起端的资源共享请求，则接收端对发起端的资源共享请求不做任何处理，IMS核心网呈现服务器也不响应发起端的资源共享请求。
在本实施例中，当未被授权的发起端向接收端发起资源共享请求时，若接收端接受发起端的资源共享请求，对发起端进行授权，则IMS核心网向获得授权后的发起端发送接收端可共享资源列表；若接收端拒绝发起端的资源共享请求，则IMS核心网不响应发起端的资源共享请求。发起端的资源共享权限由接收端进行管理，灵活掌握RCS终端资源共享权限，使资源共享建立在接收端授权的基础上，避免发起端随意占用接收端的可共享软硬件资源，更好的为有需求的RCS用户提供共享软硬件资源；同时也扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
参照图5，本发明资源共享装置第一实施例提供一种资源共享装置，所述资源共享装置包括：
会话模块100，设置成：接收发起端的资源共享请求。
RCS用户在终端使用过程中，由于本机缺乏某个或多个软件资源时，需 共享其他终端的各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。此时RCS用户终端作为发起端向会话模块100发送订阅消息，订阅发起端的可直连终端列表。订阅成功后，会话模块100向发起端发送通知消息，通知消息中包括发起端的可直连终端列表。
发起端收到通知消息后，解析通知消息，获取可直连终端列表，并通过UI界面呈现给发起端用户，由发起端用户根据可直连终端列表选择想要共享资源的终端作为接收端。发起端以订阅消息向会话模块100发出针对接收端的共享资源订阅请求消息，请求共享接收端的共享资源，会话模块100接收发起端的共享资源订阅请求消息。
需要说明的是，消息传输方式可以是无线传输、局域网传输、WLAN直连和蓝牙，也可以是其他方式，可根据实际需要灵活设定。
判定模块200，设置成：判断所述发起端是否被授权获取接收端的可共享资源。
根据获取的发起端用户信息，判定模块200查询接收端可共享用户列表，在可共享用户列表的用户信息中查找匹配发起端用户信息，可获知发起端是否被接收端设置为可以获取接收端共享资源的终端，从而判定模块200判定发起端是否被接收端授权获取接收端的可共享资源。
共享模块300，设置成：若所述发起端被授权获取接收端的可共享资源，则向所述发起端发送接收端可共享资源列表。
若判定模块200判定发起端被授权获取接收端的可共享资源，则共享模块300向发起端发送可共享资源列表通知消息，通知消息体格式是与可共享资源列表对应的预设消息体格式。可共享资源列表通知消息包括接收端可共享资源列表。发起端接收可共享资源列表通知消息，获取接收端可共享资源列表，可共享资源列表包括各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。实现了发起端获取接收端可共享的各软硬件资源。
在本实施例中，当RCS用户需共享其他终端的软硬件资源时，作为发起端发出资源共享请求；会话模块100接收发起端的资源共享请求，判定模块200判断发起端是否被授权获取接收端的可共享资源；若发起端被授权，则共享模块300向发起端发送接收端可共享资源列表；发起端接收可共享资源列表，RCS用户作为发起端，实现了获取其他终端可共享的各软硬件资源，扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
进一步的，本发明资源共享装置第二实施例提供一种资源共享装置，基于上述图5所示的实施例，所述会话模块100还设置成，
接收并存储接收端发送的公布报文，所述公布报文包括接收端可共享资源列表。
接收端在RCS启动后，整理接收端可共享的各软硬件资源，向会话模块100发送公布报文。接收端扩展公布报文消息体，使公布报文携带接收端可共享资源列表，可共享资源列表包括接收端可共享的各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。
会话模块100接收并存储接收端的公布报文，解析公布报文获取接收端可共享资源列表。当RCS用户需共享接收端的各软硬件资源时，共享模块300向被授权的发起端发送接收端可共享资源列表。
在本实施例中，RCS用户作为被共享终端，即接收端，主动发布可共享资源列表，会话模块100存储可共享资源列表。当有需求的RCS用户向会话模块100发送共享资源请求时，共享模块300可以向被授权的发起端发送接收端可共享资源列表，从而实现有需求的RCS用户获取其他终端可共享的各软硬件资源，同时也扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
进一步的，参照图6，本发明资源共享装置第三实施例提供一种资源共 享装置，基于上述图5所示实施例，所述判定模块200包括：
获取单元210，设置成：获取发起端用户信息。
发起端向会话模块100发送资源共享请求时，发送的共享资源订阅请求消息中携带发起端用户信息；会话模块100接收共享资源订阅请求消息；获取单元210根据共享资源订阅请求消息获取发起端用户信息。
查询单元220，设置成：根据所述发起端用户信息，查询接收端可共享用户列表。
查询单元220在接收端可共享用户列表中查询被授权共享资源的用户信息，匹配与发起端用户信息相同的被授权共享资源的用户信息。
判定单元230，设置成：若在所述接收端可共享用户列表中找到所述发起端用户信息，则判定所述发起端被授权获取接收端的可共享资源；若在所述接收端可共享用户列表中未找到所述发起端用户信息，则判定所述发起端未被授权获取接收端的可共享资源。
若查询单元220在接收端可共享用户列表的被授权共享资源的用户信息中，成功匹配发起端用户信息，则判定单元230判定所述发起端被授权获取接收端的可共享资源。
若查询单元220在接收端可共享用户列表的被授权共享资源的用户信息中，未成功匹配发起端用户信息，则判定单元230判定所述发起端未被授权获取接收端的可共享资源。
在本实施例中，在发起端发送资源共享请求后，根据发起端用户信息和接收端可共享用户列表，判定单元230判断发起端是否被授权获取接收端的可共享资源，共享模块300向被授权的发起端发送接收端的可共享用户列表，实现了资源共享的权鉴管理，避免接收端的共享资源被未授权的发起端使用，保证了资源共享的安全性。
进一步的，本发明资源共享装置第四实施例提供一种资源共享装置，基于上述图5所示实施例，所述会话模块100还设置成，
若所述发起端未被授权获取接收端的可共享资源，则向接收端发送发起端的资源共享请求通知。
接收端在RCS启动后，向IMS核心网发送订阅消息，订阅发起共享本终端资源的用户信息。订阅消息的消息体格式是与发起共享本终端资源的用户信息对应的预设消息体格式。
若判定模块200判定发起端被授权获取接收端的可共享资源，发起端当前无权获取接收端的可共享资源，则会话模块100向接收端发送通知消息，通知消息包括发起端的用户信息和资源共享请求，通知接收端有发起端请求共享其资源。通知消息的消息体格式是与发起共享本终端资源的用户信息对应的预设消息体格式。
接收端接收到会话模块100发送的关于发起端用户信息和资源共享请求的通知消息后，解析通知消息，获取发起端用户信息和资源共享请求，通过UI界面呈现给接收端用户，由用户判断是否接受发起端的资源共享请求。
所述共享模块300还设置成，若接收端接受所述发起端的资源共享请求，则向所述发起端发送接收端可共享资源列表；若接收端拒绝所述发起端的资源共享请求，则不响应所述发起端的资源共享请求。
若接收端用户接受发起端的资源共享请求，则接收端发送向会话模块100加入请求消息，修改接收端可共享用户列表信息，在接收端可共享用户列表中加入发起端用户信息。
判定模块200获取修改后的接收端可共享用户列表，在修改后的接收端可共享用户列表中找到所述发起端用户信息，判定发起端被授权获取接收端可共享资源列表，共享模块300向发起端发送接收端可共享资源列表。
若接收端用户拒绝发起端的资源共享请求，则接收端对发起端的资源共享请求不做任何处理，共享模块300不响应发起端的资源共享请求。
在本实施例中，发起端未被授权获取接收端的可共享资源，会话模块100向接收端发送发起端的资源共享请求通知后，若接收端接受发起端的资源共享请求，对发起端进行授权，则共享模块300向获得授权后的发起端发送接 收端可共享资源列表；若接收端拒绝发起端的资源共享请求，则共享模块300不响应发起端的资源共享请求。发起端的资源共享权限由接收端进行管理，灵活掌握RCS终端资源共享权限，使资源共享建立在接收端授权的基础上，避免发起端随意占用接收端的可共享软硬件资源，更好的为有需求的RCS用户提供共享软硬件资源，同时也扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
参照图7，本发明资源共享系统第一实施例提供一种资源共享系统，所述资源共享系统包括：核心网服务器A和发起端B，其中：
所述核心网服务器A包括会话模块100、判定模块200和共享模块300。
核心网服务器A接收并处理收到的消息，向发起端B发送消息，进行信令处理。
会话模块100接收发起端的资源共享请求；判定模块200判断发起端B是否被授权获取接收端的可共享资源；若发起端B被授权获取接收端的可共享资源，共享模块300向发起端B发送接收端可共享资源列表。
所述发起端B，设置成：向所述核心网服务器发送资源共享请求，在所述发起端被授权获取接收端的可共享资源时，接收所述核心网服务器发送的所述接收端可共享资源列表。
发起端B包括直连管理模块B1、资源共享管理模块B2、会话管理模块B3和资源共享应用模块B4。
直连管理模块B1和资源共享管理模块B2通过会话管理模块B3向核心网服务器A发送订阅消息；会话管理模块B3将从直连管理模块B1和资源共享管理模块B2获取的信息处理为订阅消息，订阅消息体格式是与订阅消息内容对应的预设消息体格式。
发起端B需共享其他终端的可共享资源时，直连管理模块B1通过会话管理模块B3向核心网服务器A发送可直连终端列表订阅消息；会话管理模块B3收到可直连终端列表通知消息后，解析直连终端列表通知消息，获取可直连终端列表；会话管理模块B3将获取到的可直连终端列表发送给直连管理 模块B1；直连管理模块B1获取可直连终端列表，通知资源共享应用模块B4；资源共享应用模块B4将可直连终端列表通过UI界面呈现给终端用户，由终端用户根据可直连终端列表选择想要共享资源的终端作为接收端；当用户选定接收端后，资源共享应用模块B4通知直连管理模块B1；直连管理模块B1获取接收端用户信息。在本实施例中，可直连终端列表订阅消息的消息体格式是与可直连终端列表对应的预设消息体格式。
选定接收端后，直连管理模块B1将选定的接收端信息发送给资源共享管理模块B2；资源共享管理模块B2通过会话管理模块B3向核心网服务器A发出针对接收端的共享资源订阅请求消息，请求共享接收端的共享资源。共享资源订阅请求消息的消息体格式是与可共享资源列表对应的预设消息体格式。
核心网服务器A向被授权的发起端B发送可共享资源列表通知消息后，会话管理模块B3收到可共享资源列表通知消息，解析可共享资源列表通知消息，获取接收端可共享资源列表；会话管理模块B3将接收端可共享资源列表发送给资源共享管理模块B2；资源共享管理模块B2获取接收端的可共享软硬件资源。
在本实施例中，发起端B向核心网服务器A发送资源共享请求，核心网服务器A收到消息后判定发起端B是否被授权获取接收端的可共享资源，若发起端B被授权获取接收端的可共享资源，则核心网服务器A向发起端B发送接收端的可共享资源列表。发起端B接收核心网服务器A发送的可共享资源列表，实现了发起端B获取接收端的可共享资源，扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
进一步的，参照图8，本发明资源共享系统第三实施例提供一种资源共享系统，基于上述图7所示实施例，所述资源共享系统还包括接收端C：
所述接收端C，设置成：向所述核心网服务器发送公布报文，接收所述核心网服务器发送的所述发起端资源共享请求通知，接受或拒绝所述发起端 的资源共享请求。
接收端C包括资源共享管理模块C1、XCAP模块C2、会话管理模块C3和资源共享应用模块C4。
资源共享管理模块C1通过会话管理模块C3向核心网服务器A发送公布报文和订阅消息；会话管理模块C3将从资源共享管理模块C1获取的信息处理为公布报文或订阅消息，公布报文和订阅消息体格式是为与内容对应的预设消息体格式。
资源共享管理模块C1在接收端C启动后，整理接收端C的可共享软硬件资源，通过会话管理模块C3向核心网服务器A发送公布报文，会话管理模块C3扩展公布报文消息体，使公布报文携带接收端C的可共享资源列表，可共享资源列表包括接收端可共享的各软硬件资源，如：摄像头、麦克风、屏幕、存储空间、各类应用、流量信息和终端性能，也可以是其他软硬件资源。
资源共享管理模块C1通过会话管理模块C3向核心网服务器A发送订阅消息，订阅发起共享本终端资源的用户信息，订阅消息的消息体格式是与发起共享本终端资源的用户信息对应的预设消息体格式。
会话管理模块C3收到核心网服务器A发送的关于发起端用户信息和资源共享请求的通知消息后，解析通知消息，获取发起端用户信息和资源共享请求；会话管理模块C3将发起端用户信息和资源共享请求发送给资源共享管理模块C1；资源共享管理模块C1获取发起端用户信息和资源共享请求信息，通知资源共享应用模块C4；资源共享应用模块C4将发起端用户信息和资源共享请求通过UI界面呈现给接收端用户，由用户判断是否接受发起端的资源共享请求，并将用户判断结果反馈给资源共享管理模块C1。
若用户接受发起端的资源共享请求，资源共享管理模块C1向XCAP(The XML Configuration Access Protocol，XML配置访问协议)模块C2发送用户接受发起端的资源共享请求的通知消息；XCAP模块C2向核心网服务器A发送加入请求消息，修改接收端C的可共享用户列表信息，在接收端C可共享用户列表中加入发起端用户信息；核心网服务器A判断发起端B被授权获取接收端可共享资源，向发起端B发送接收端可共享资源列表。
若用户拒绝发起端的资源共享请求，资源共享管理模块C1不响应发起端 资源共享请求，XCAP模块C2不响应发起端资源共享请求，核心网服务器A不响应发起端资源共享请求，对发起端的资源共享请求不再做任何处理；发起端B在预设时间内未收到核心网服务器A的可共享资源列表通知消息后，默认接收端B拒绝发起端B的资源共享请求。或，
若用户拒绝发起端的资源共享请求，资源共享管理模块C1向XCAP模块C2发送用户接受发起端的资源共享请求的通知消息；XCAP模块C2向核心网服务器A发送加入请求消息，修改接收端C的可共享用户列表信息，在接收端C不可共享用户列表中加入发起端用户信息；核心网服务器A向发起端B发送拒绝共享资源通知消息。
在本实施例中，接收端C向核心网服务器A发送公布报文，公布接收端可共享资源列表；若发起端B未被授权获取接收端可共享资源，核心网服务器A通知接收端C对发起端B的资源共享请求进行判断；若接收端C接受发起端B的资源共享请求，则核心网服务器A向发起端B发送接收端可共享资源列表，发起端B获取接收端C的可共享资源列表，实现了RCS用户获取其他终端可共享的各软硬件资源，扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。
本发明实施例还公开了一种计算机程序，包括程序指令，当该程序指令被核心网服务器执行时，使得该核心网服务器可执行上述任意的资源共享方法。
本发明实施例还公开了一种载有所述的计算机程序的载体。
在阅读并理解了附图和详细描述后，可以明白其他方面。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
工业实用性
本发明技术方案的资源共享方法、装置和系统，IMS核心网接收发起端的资源共享请求，判断发起端是否被授权获取接收端的可共享资源，若发起端被授权，则向发起端发送接收端可共享资源列表。在本发明技术方案中，RCS用户需共享其他终端可共享的软硬件资源时，根据RCS用户发起端的资源共享请求，IMS核心网向被授权的RCS用户发起端发送接收端可共享资源列表，使得RCS用户能够获取其他终端可共享的各类软硬件资源，从而扩展了RCS共享终端共享资源范围，满足了跨设备资源共享的需求，打破了相关技术中跨设备之间只能进行屏幕内容投射或文件传输的局限性。因此本发明具有很强的工业实用性。

Claims (12)

  1. 一种资源共享方法，所述资源共享方法包括以下步骤：
    IP多媒体子系统IMS核心网接收发起端的资源共享请求；
    所述IMS核心网判断所述发起端是否被授权获取接收端的可共享资源；
    若所述发起端被授权获取所述接收端的可共享资源，则所述IMS核心网向所述发起端发送所述接收端的可共享资源列表。
  2. 如权利要求1所述的资源共享方法，其中，所述IMS核心网接收发起端的资源共享请求的步骤之前，该方法还包括：
    所述IMS核心网接收并存储所述接收端发送的公布报文，所述公布报文包括所述接收端的可共享资源列表。
  3. 如权利要求1或2所述的资源共享方法，其中，所述IMS核心网判断所述发起端是否被授权获取所述接收端的可共享资源的步骤包括：
    所述IMS核心网获取所述发起端的用户信息；
    根据所述发起端的用户信息，所述IMS核心网查询所述接收端的可共享用户列表；
    若在所述接收端的可共享用户列表中找到所述发起端的用户信息，则所述IMS核心网判定所述发起端被授权获取所述接收端的可共享资源；若在所述接收端的可共享用户列表中未找到所述发起端的用户信息，则所述IMS核心网判定所述发起端未被授权获取所述接收端的可共享资源。
  4. 如权利要求1或2所述的资源共享方法，其中，所述IMS核心网判断所述发起端是否被授权获取所述接收端的可共享资源的步骤之后，该方法还包括：
    若所述发起端未被授权获取所述接收端的可共享资源，则所述IMS核心网向所述接收端发送所述发起端发起的资源共享请求通知；
    若所述接收端接受所述发起端发起的资源共享请求，则所述IMS核心网向所述发起端发送所述接收端的可共享资源列表；若所述接收端拒绝所述发起端发起的资源共享请求，则所述IMS核心网不响应所述发起端发起的资源 共享请求。
  5. 一种资源共享装置，所述资源共享装置包括会话模块、判定模块和共享模块，其中：
    所述会话模块设置成：接收发起端的资源共享请求；
    所述判定模块设置成：判断所述发起端是否被授权获取接收端的可共享资源；
    所述共享模块设置成：若所述判定模块判定所述发起端被授权获取所述接收端的可共享资源，则向所述发起端发送所述接收端的可共享资源列表。
  6. 如权利要求5所述的资源共享装置，其中，所述会话模块还设置成：
    接收并存储所述接收端发送的公布报文，所述公布报文包括所述接收端的可共享资源列表。
  7. 如权利要求5所述的资源共享装置，其中，所述判定模块还设置成
    获取所述发起端的用户信息；
    根据所述发起端的用户信息，查询所述接收端的可共享用户列表；
    若在所述接收端的可共享用户列表中找到所述发起端的用户信息，则判定所述发起端被授权获取所述接收端的可共享资源；若在所述接收端的可共享用户列表中未找到所述发起端的用户信息，则判定所述发起端未被授权获取所述接收端的可共享资源。
  8. 如权利要求5所述的资源共享装置，其中，
    所述会话模块还设置成：若所述判定模块判定所述发起端未被授权获取所述接收端的可共享资源，则向所述接收端发送所述发起端发起的资源共享请求通知；
    所述共享模块还设置成：若所述接收端接受所述发起端发起的资源共享请求，则向所述发起端发送所述接收端的可共享资源列表；若所述接收端拒绝所述发起端发起的资源共享请求，则不响应所述发起端发起的资源共享请求。
  9. 一种资源共享系统，包括：核心网服务器和发起端，其中：
    所述核心网服务器包括如权利要求5-8中任一项所述的资源共享装置；
    所述发起端设置成：向所述核心网服务器发送资源共享请求，在所述发起端被授权获取接收端的可共享资源时，接收所述核心网服务器发送的所述接收端的可共享资源列表。
  10. 如权利要求9所述的资源共享系统，所述资源共享系统还包括接收端，其中
    所述接收端设置成：向所述核心网服务器发送公布报文，接收所述核心网服务器发送的所述发起端发起的资源共享请求通知，接受或拒绝所述发起端发起的资源共享请求。
  11. 一种计算机程序，包括程序指令，当该程序指令被核心网服务器执行时，使得该核心网服务器可执行如权利要求1-4中任一项所述的资源共享方法。
  12. 一种载有如权利要求11所述的计算机程序的载体。
PCT/CN2015/089637 2015-07-17 2015-09-15 资源共享方法、装置及系统 WO2016131250A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510422830.8 2015-07-17
CN201510422830.8A CN106357592A (zh) 2015-07-17 2015-07-17 资源共享方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016131250A1 true WO2016131250A1 (zh) 2016-08-25

Family

ID=56691929

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/089637 WO2016131250A1 (zh) 2015-07-17 2015-09-15 资源共享方法、装置及系统

Country Status (2)

Country Link
CN (1) CN106357592A (zh)
WO (1) WO2016131250A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107135531A (zh) * 2017-04-21 2017-09-05 努比亚技术有限公司 资源共享方法及装置
CN109861900B (zh) * 2017-11-30 2021-05-28 腾讯科技（深圳）有限公司 实时通信的数据处理方法、装置、计算机设备及存储介质
FI127980B (en) * 2018-02-23 2019-06-28 Nokia Technologies Oy BASE STATION CONFIGURED TO REMOVE DISTANCE FILTER

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068173A (zh) * 2006-06-08 2007-11-07 腾讯科技（深圳）有限公司 一种资源共享的方法及系统
US20080163318A1 (en) * 2006-12-29 2008-07-03 Lucent Technologies Inc Mobile multimedia content sharing application system
CN101924778A (zh) * 2009-06-10 2010-12-22 中国移动通信集团公司 P2p流媒体系统、p2p用户设备及流媒体数据传送方法
CN102082834A (zh) * 2011-03-04 2011-06-01 中国联合网络通信集团有限公司 基于ims的p2p资源共享方法、系统及代理服务器

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10061620B2 (en) * 2012-07-02 2018-08-28 Paypal, Inc. System and method for clustering of mobile devices and applications
CN104125221B (zh) * 2014-07-17 2017-05-24 东北大学 Ims终端设备多软终端资源共享和应用协同装置及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068173A (zh) * 2006-06-08 2007-11-07 腾讯科技（深圳）有限公司 一种资源共享的方法及系统
US20080163318A1 (en) * 2006-12-29 2008-07-03 Lucent Technologies Inc Mobile multimedia content sharing application system
CN101924778A (zh) * 2009-06-10 2010-12-22 中国移动通信集团公司 P2p流媒体系统、p2p用户设备及流媒体数据传送方法
CN102082834A (zh) * 2011-03-04 2011-06-01 中国联合网络通信集团有限公司 基于ims的p2p资源共享方法、系统及代理服务器

Also Published As

Publication number Publication date
CN106357592A (zh) 2017-01-25

Similar Documents

Publication Publication Date Title
KR102166992B1 (ko) 서비스 계층 그룹 동작을 위한 멀티캐스트의 인에이블
US7987360B2 (en) Method for implementing grouping devices and interacting among grouped devices
US7860525B2 (en) System, method, and computer program product for service and application configuration in a network device
EP2863615A1 (en) Method, push system, and relevant devices for setting up push session
CN112073919B (zh) 多播广播业务的通信方法及装置、电子设备、存储介质
US11051078B2 (en) Video distribution method and device
WO2017004894A1 (zh) 一种资源共享方法、终端设备、应用服务器及系统
WO2007076673A1 (fr) Procede, systeme et dispositif permettant de partager des informations de presence
CN110831092B (zh) Pdu会话管理、节点关联和upf发现的方法及设备
EP3447996A1 (en) Resource subscription method, resource subscription device, and resource subscription system
WO2011147371A1 (zh) 一种实现虚拟机间数据传输的方法和系统
US20220116400A1 (en) Authorization in communication networks
WO2016131250A1 (zh) 资源共享方法、装置及系统
CN104994158B (zh) 一种通过集中式网关安全控制家电的方法
WO2008125057A1 (fr) Procédé et système de communication avec un abonné supportant divers services de messagerie
WO2021109134A1 (zh) Mbms信息的获取、发送方法、终端设备及网元设备
CN112243224A (zh) 一种边缘计算网络实现方法及装置
US9049310B2 (en) Data communication
WO2015021842A1 (zh) 访问ott应用、服务器推送消息的方法及装置
WO2021233196A1 (zh) 加入组播广播业务mbs会话的方法及装置
WO2016177103A1 (zh) 一种发现共享资源的方法、系统及装置
WO2019161721A1 (zh) 一种基于互通rcs系统的对应关系处理方法及装置
WO2022033491A1 (zh) 用于鉴权的方法和通信装置
WO2024094105A1 (zh) 消息交互方法、装置、网络功能、相关设备及存储介质
US20230300041A1 (en) Method of Supporting Packet Flow Descriptor Management in a Service Based Architecture Based Telecommunication Network

Legal Events

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

Ref document number: 15882389

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15882389

Country of ref document: EP

Kind code of ref document: A1